I use the code in this topic as developer.nokia.com/community/wiki/Audio_recording_and_playback_options_in_Windows_Phone .
Doing so:
Code:
WasapiAudioComp.WasapiAudio Audio = new WasapiAudioComp.WasapiAudio();
Audio.SetAudioBytes(byteArray);
Audio.StartAudioRender();
Also, the timer is:
Code:
Audio.Update();
In byteArray Wav load file, but it will only play once more and no sound comes. What could be the problem?
Related
Al Credits Goes TO Perceval from Hyrule
Perceval from Hyrule said:
** Currently writing this, please wait !
Hello there,
here is a new tutorial I'm sure you'll like. As usual it took me LOTS of work to get all info and make this to work, so now I share it with you and show how to run custom ROMs within Android SDK Emulator.
Please note it's mainly for XPERIA X10, but process is the same for other Android-powered devices. It will show you the process for Linux.
1. Download the latest Android SDK.
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
3. Go to the SDK folder, then in the folder Tools/. Double-click on Android and choose Run.
4. Go to Available packages, and choose to install (choose at your will !)
Android SDK Tools, revision 8
Android SDK Platform-tools, revision 1
SDK Platform Android {VERSION(S) YOU WANT} (!) You need at least one Platform. For X10, you can download 1.6, 2.1. You can also add 2.2, 2.3.
Once it's done, close the window.
5. Download Xperia X10 add-on for SDK. (?) Read the PDF add-on guide, it is helpful !
Copy the folder (from the archive) XPERIA-X10_r1 inside the folder add-ons of your Android SDK folder ({androidsdk}/add-ons/).
6. Run terminal, go to your Android SDK folder, then in tools folder, and run
Code:
./android list target
.
Note the id number of the Android you want to develop (ie for me, Android 2.3 is
Code:
id: 3 or "android-9"
). (?) You might also want to note the name ("android-X") as it might be useful later.
7. Now, create AVD (a profile for emulator). Usual command (assuming you are INSIDE the /tools/ folder !) is
Code:
android create avd -n NAMEYOUWANT -t {ID}
So, for us, it will be
Code:
./android create avd -n myx10 -t 3
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 160 (correct if I'm wrong ?)
DPad support : no (?)
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 66 (?)
Audio playback : yes
Trackball : no (?)
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 32
RAM : 280
GSM Modem : yes
(?) I recommend you to create one profile for each Android version you want to run (so : you just have to change the ID, and create same profile). If you don't, you won't be able to run custom ROMs using other versions of Android (ie your AVD profile is 2.3 and you run a 2.1 custom ROM).
9. Done ! Take your custom ROM (downloaded, compiled... In this case, files are in {YourAndroidRepoFolder}/out/target/product/generic/. It comes with about 3 files, including a file called system.img. Copy this file into the folder (hidden) .android/myx10{In fact, the name you've chosen earlier "NAMEYOUWANT"}.avd/
10. Run terminal, go to Android SDK folder/tools/ (if you didn't close your current terminal, you're already in and run this command to run emulator WITH your custom ROM :
Code:
./emulator -avd myx10{again the "NAMEYOUWANT" you've chosen before}
Wait and enjoy !
(?) First boot is long - it's NORMAL. Just like on a real device, the OS will be cached and will work faster and faster.
Click to expand...
Click to collapse
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 240
DPad support : no
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 100
Audio playback : yes
Trackball : no
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 64
RAM : 403
GSM Modem : yes
works with the LG O2X roms?
sjcunha said:
works with the LG O2X roms?
Click to expand...
Click to collapse
hasn't been tried yet
Hi all,
can someone tell me how or with what program can I open " lgecs.downloadFile.ldwf "???
I google it but nothing...
Its about Open Source from LG, I downloaded from one of those policy things from the phone and I would like to know what it is about.
Its a file with near 161MB and I'm getting crazy trying to see what is that.
Thanks in advance :good:
I have downloaded the file and it is .zip file .. It has two files that are kernel and platform files >> Good news
Now, I can see all the files for our O4X and everything is clear . We can make modification for it and install it by CWM
I hope you guys all the best with development .
Best regards,
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I advice you to use explorer internet or Google chrome to download the file
The source code ICS. for O4XHD
http://www.lg.com/global/support/ope...delCode=LGP880
Thanks for lightening me ( I don't know why I didn't remember of that...) :good:
I have 3 files, one is a "readme.txt" and says the follow:
"How to build
1. Android build
(1) Get the android base source code.
- Download the original android source code (Android 4.0.3 IceCreamSandwitch)(P880) from http://source.android.com
(2) Overwrite modules that you want to build.
- Untar opensource packages of LGP880_ICS_Platform.tar.gz into downloaded android source directory
- And, merge the source into the android source code(GingerBread)
(3) Merge the below code into android source file(bionic\libdl\Android.mk) at the last line.
##################################################################
# -begin
include $(CLEAR_VARS)
#LOCAL_LDFLAGS := -Wl,--exclude-libs=libgcc.a
LOCAL_SRC_FILES:= libdl.c
LOCAL_CFLAGS := -DLIBC_STATIC
LOCAL_MODULE:= libdl
ifeq ($(TARGET_ARCH),sh)
# for SuperH, additional code is necessary to handle .ctors section.
GEN_SOBEGIN := $(TARGET_OUT_STATIC_LIBRARIES)/sobegin.o
$(GEN_SOBEGIN): $(LOCAL_PATH)/arch-sh/sobegin.S
@mkdir -p $(dir [email protected])
$(TARGET_CC) -o [email protected] -c $<
GEN_SOEND := $(TARGET_OUT_STATIC_LIBRARIES)/soend.o
$(GEN_SOEND): $(LOCAL_PATH)/arch-sh/soend.S
@mkdir -p $(dir [email protected])
$(TARGET_CC) -o [email protected] -c $<
LOCAL_ADDITIONAL_DEPENDENCIES := $(GEN_SOBEGIN) $(GEN_SOEND)
endif
include $(BUILD_STATIC_LIBRARY)
# -end
#################################################################
(4) Run the build scripts.
- You have to add google original prebuilt source(toolchain) before running build scripts.
- Run the following scripts to build android
a) . ./build/envsetup.sh
b) set_hw_ver rev_1_1
b) choosecombo 1 x3_open_eu 1 1
c) make -j4
into the android folder
- If the android is built sucessfully, you will find the outputs in this directory,
"out/target/product/x3".
2. Kernel Build
- Untar using following command at the android folder:
tar xvfj LGP880_Kernel.tar.gz
- change directory to kernel root
cd kernel
- make kernel zImage:
make ARCH=arm CROSS_COMPILE=../prebuilt/linux-x86/toolcahin/arm-eabi-4.4.3/bin/arm-eabi- x3_defconfig zImage"
The other two are:
LGP880_ICS_Platform.tar
LGP880_Kernel.tar
Is this good for something?
Personally I don't know how to manage those files.
My ignorance don't allow me to do nothing with them...
If some devs or someone who knows how to something with it, I'll be very happy for let them know about that.
Thank you for keeping the interest on the O4X HD
If someone want to download the files to see if there's something to work on, here is the link:
http://www.4shared.com/zip/1dX1k0_A/lgecsdownloadFile.html
To decompress them its better use WinRAR, it will arrive to a point when it asks to replace/rename/etc..., better choose rename all.
WinZip gives me some errors...
Thanks once more to those who try to develope on this device :good:
I'm testing the camera flash of my galaxy s advance, but I can only turn the flash in a single brightness level, regardless of the value entered in the command:
# echo 1 / sys/class/camera/flash/rear_flash
# echo 1 / sys/class/camera/rear/rear_flash
I want to know is how the app controls the camera's LED flash to it lights with full power, and if you can do this by controlling terminal emulator. No problem as the burning of the LED, because I have to replace it easily. I am using a CM10 rom, but I can switch to the official 4.1.2 if necessary.
I searched other topics but no topic was answered.
Sorry for my Google Translate english
I have a Moto X (2014). I need to use it in various locations with Cisco APs. The problem I'm having is that after entering a network pass code, the network transitions directly to saved and never actually connects.
Logs on the phone show:
"WPA: CCMP is used, but EAPOL-Key descriptor version (3) is not 2"
The access points aren't mine to control or I'd patch them.
My desire is to disable pmf in /data/misc/wifi/wpa_supplicant.conf, but every time I toggle wifi the file seems to get regenerated with pmf=1 instead of the desired pmf=0.
Any thoughts? Or ideas when we might see a fix ala:
Code:
diff --git a/src/rsn_supp/wpa.c b/src/rsn_supp/wpa.c
index d95c1bd..f8825d2 100644
--- a/src/rsn_supp/wpa.c
+++ b/src/rsn_supp/wpa.c
@@ -1756,6 +1756,9 @@ int wpa_sm_rx_eapol(struct wpa_sm *sm, const u8 *src_addr,
wpa_msg(sm->ctx->msg_ctx, MSG_INFO,
"WPA: Backwards compatibility: allow invalid "
"version for non-CCMP group keys");
+ } else if (ver == WPA_KEY_INFO_TYPE_AES_128_CMAC) {
+ wpa_msg(sm->ctx->msg_ctx, MSG_INFO,
+ "WPA: Interoperability workaround: allow incorrect (should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor version to be used");
} else
goto out;
} else if (sm->pairwise_cipher == WPA_CIPHER_GCMP &&
The patch above isn't mine but I'm not yet 'old enough' to post links to external things. Just FYI, I didn't fix the C code, I just hacked up the overlay conf below.
[solved] PMF workaround for Moto X (2014)
Every single time I go to ask a question it's too soon.
If you have this phone and you're trying to connect to a CISCO AP that you either can't or won't update, here's a work around that should get you online.
Requirements
* Rooted
* Basic ADB use
* Basic linux commands
Code:
adb shell
su
cp /system/etc/wifi/wpa_supplicant_overlay.conf /sdcard/
On your computer
Code:
adb pull /sdcard/wpa_supplicant_overlay.conf .
perl -i -pe 's/pfm=1/pfm=0/' wpa_suplicant_overlay.conf
adb push wpa_supplicant_overlay.conf /sdcard/
Turn off wifi
Back on your phone.....
Code:
adb shell
su
mount -o remount,rw /dev/block/platform/msm_sdcc.1/by-name/system
cp /sdcard/wpa_supplicant_overlay.conf /system/etc/wifi/wpa_supplicant_overlay.conf
sync
Reboot. Once your phone reboots, turn on wifi and you should be able to join if you were having the same problem I was with a few APs.
I'd like to thank /etc/init.qcom.wifi.sh for pointing me in the right direction.
NOTE:
This hack is a dirty, dirty hack. It completely disables pmf which is a fairly nice part of 802.11w
It hasn't reached mass adoption yet, but it's a shame I needed to disable this. A more pragmatic fix would be to fix the wifi driver to fall back as the patch in my first post does.
Awesome conversation I'm having with myself, but hey somebody might use this...
I wrote a stupid app so I could toggle the hack I did on/off for when I'm not using a crippled wifi AP. It's fugly but it works. The apk is at https://neverlight.com/MotoXWifiHack.apk
If you'd rather get the source and build it yourself, and I wouldn't blame you, I put it up here:
https://github.com/jstelzer/MotoWifiHack
Hello
I have problem with BT .My Watch (moto 360) get disconected and its hard to reconect it again ... in the process its need to confirm new paircode.
I thing that this will solwe my problem (its from topic for Sony Xperia Z1).
The soluton is :
Code:
Workaround: create a file named "bluetooth_bdaddr" in /data/etc, write a BT address in there (I used one of the random addresses when I started to turn BT on and off), then change the owner and permissions of the file (Terminal Emulator or any other app):
- chown bluetooth bluetooth_bdaddr
- chmod 0640 bluetooth_bdaddr.
Bluetooth is now working fine for me because it uses always the same address
But i canot create file in that adress ... there is no /data/etc/ folder ...and if i use in terminal : "touch \data\etc\bluetooth_bdaddr" it will not create the file ! (i have start the "su" command before)
Cant somebody to help me how to use this workaround it the CM12.1 Beta 5 for lenovo A7000?
Thanks and sorry for my bad english
Nobody know how to youse this fix in this rom.
Another important stuff.
I have found mallware inside this ROM. His name is "teleyphone" , "com.android.services.teleyphone" .