Develop Bugs

WiFi - bcm4329.ko file?

Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks

Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?

KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.

Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.

theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.

you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one

ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?

Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,

ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.

Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.

has anyone fixed this issue where wifi stops working?

wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.

Captivate Glide Recording Failed on Camera

I have looked everywhere before this post so my apologies if this is an incorrect posting, my ATT captivate glide camera says RECORDING FAILED nearly every time i open the camera app, i have tried clearing cache through multiple apps and through the recovery boot, and multiple camera apps like pudding camera, i've uninstalled every app i can think of that may interfere with the camera as well, i have also rooted my device hoping this would help, a reset will not help, a reflash of the rooted rom will not help either, i am open to try anything suggested as i trust the developers in this forum, i posted this as a new thread to see if anyone else has the same problem, thank you for your time and effort, it means a lot to us that are learning

Never seen that and I use the camera pretty regularly. Bum device maybe?

Never had this problem as well, I think you might have got a defective unit.

if you use your external SD card as storage, better check that one. If you use internal SD, you can check if you have a DCIM folder in it, try creating it manually if you do not see any.

i tried the dcim folder idea, now have a folder in usb storage, sd, and external sd, no luck but thank you

I found a thread with a promising solution, i deleted my camera.apk with titanium backup and got a camera mod here http://forum.xda-developers.com/showthread.php?t=1104051 , it's working now, i hope it continues to, i will post an update later if anyone else is having this problem, thanks to all involved

Still not resolved
Sent from my SAMSUNG-SGH-I927 using XDA App

I never had an issue with mine as well I would take it back to where you got it and let them see the issues perhaps they can swap it with another for you.

Can someone upload the original camera.apk and camera.odex from their device please
I can't warranty... rooted...
Sent from my SAMSUNG-SGH-I927 using XDA App

Can't you just put back the original rom.back to stock then warranty. Can't help you with the apk as I am not rooted sorry.
Sent from my SAMSUNG-SGH-I927R using XDA App

i'm waiting on a usb jig to get here to reset my binary download counter... after that i can warranty but until then i would like to solve the problem if i can, i think an app is running commands that are conflicted with the cam... i'm methodically uninstalling apps and clearing cache partition.... it seems to get cam working for a few hours... sometimes

dmw0215 said:
i'm waiting on a usb jig to get here to reset my binary download counter... after that i can warranty but until then i would like to solve the problem if i can, i think an app is running commands that are conflicted with the cam... i'm methodically uninstalling apps and clearing cache partition.... it seems to get cam working for a few hours... sometimes
Click to expand...
Click to collapse
Where did you buy the jig from? Do you know if it is compatible with the Glide? Let us know how it goes.

dmw0215 said:
Can someone upload the original camera.apk and camera.odex from their device please
I can't warranty... rooted...
Sent from my SAMSUNG-SGH-I927 using XDA App
Click to expand...
Click to collapse
Attached
Sent from my SAMSUNG-SGH-I927 using XDA App

Sweet thanks
Sent from my SAMSUNG-SGH-I927 using XDA App

vil33 said:
Where did you buy the jig from? Do you know if it is compatible with the Glide? Let us know how it goes.
Click to expand...
Click to collapse
I got the jig yesterday, tried the one for gs2, no luck, will only put phone in odin mode then says awaiting usb cable...

Need firmware
i checked my firmware using *#34971539# and it displayed null.... i need someone to upload the actual firmware please, or at least tell me what version they have.... thanks

Firmware
OK, here's where I'm at now... someone was kind enough to upload me the firmware, i install it and reboot my device and it works for about 5 minutes then fails again, i honestly think something is running in my device that is interfering with the camera.... if anyone has any ideas they would be appreciated...

I'm gonna try this again, camera still only working intermittently (about 10%).... in the service menu my cam firmware is null, a phone to cam fw write just reboots my device, i put the rs_m5ls.bin in the root of my SD card before write, not sure if i am doing this correctly, if i do a cam to phone fw dump i get a m5mo_dump.bin in the root of my SD card as well, I've formatted cache, data, system and reinstalled ICS ROM by jayjayjoker, I've flashed the stock GB firmware from samfirmware via Odin, and tried the firmware write every way i could think of each time... can anyone please explain how the firmware works with the ROM and driver, maybe i will understand it better or even detailed steps on the correct installation of firmware, I'm sure I'm missing something and the only info i can find is all spread out and not necessarily clear when i do find it, if any of you devs have any ideas please help.... thanks for your time, this is very frustrating

Hi can anybody assist me please I am trying to install the new camera all onto my Samsung glide, I have read that I use Root Explorer go to system/app and rename camera.apk and install the new file in its place.
But my problem is root explorer says that the system file is read only and cannot be renamed how do I get round this rather than using the Odin for my computer.
My issue with the camera is when in landscape it works perfect but when I switched to portraits the screen goes blank.
Many thanks.

pgunning1 said:
Hi can anybody assist me please I am trying to install the new camera all onto my Samsung glide, I have read that I use Root Explorer go to system/app and rename camera.apk and install the new file in its place.
But my problem is root explorer says that the system file is read only and cannot be renamed how do I get round this rather than using the Odin for my computer.
My issue with the camera is when in landscape it works perfect but when I switched to portraits the screen goes blank.
Many thanks.
Click to expand...
Click to collapse
I have the same problem with root explorer, let me know if you figure that out... and what exactly is "Camera All"... Thank You

[GUIDE/FIX] For GPS issues in AOSP CM7 MIUI Roms

Since about January, all the CM7 based roms have had flaky GPS for me. Basically it loses the signal after about 5 minutes. A quick GPS on/off cycle usually fixes the problem. However, I really don't like the distraction
(and the danger) of messing with the gps when driving 70 mph.
I spent quite a bit of time searching for a solution on this and other forums, but found nothing helpful. Yesterday, I got the idea to try out one of the Sense GPS drivers in the AOSP roms. I extracted the attached file from one of the Stock roms and replaced the AOSP driver.
The good news is it appears to work. In the 4 times I've driven I didn't have to do any GPS cycling.
Steps:
1) Extract the attached gps.glacier.so.zip file.
2) Using Root Explorer or ES File Explorer (with the root option checked) copy the attached gps.glacier.so file into your system/lib/hw directory replacing the current file.
3) Reboot.
4) You may want to clear out the A-GPS state using the GPS status app, but I don't know if this is necessary or not.
or
1)Use clockworkmod to install the GPS_Fix.zip file.
Anyway, I hope this helps someone else. I am thinking of developing zip you can flash if there is interest in it. But in the meantime I wanted to post the fix, since I know there have been other people with the same problems I had.
I hope this helps!
EDIT-
I have also added the gps_update.zip that has the gps.conf file, the supl.root.cert and the gps.glacier.so all put together by tnpapadakos

testing now
have you tried the gps.conf by crypted? the gps lock is way quicker/better than the stock/aosp gps.conf file
just wondering if you tried it

tnpapadakos said:
testing now
have you tried the gps.conf by crypted? the gps lock is way quicker/better than the stock/aosp gps.conf file
just wondering if you tried it
Click to expand...
Click to collapse
No, I haven't tried it. My lock time hasn't been bad... I usually have a lock in the time it takes me to pull out of my garage. That being said, I am always tweaking things so I will definitely give it a try.

Gadianton said:
No, I haven't tried it. My lock time hasn't been bad... I usually have a lock in the time it takes me to pull out of my garage. That being said, I am always tweaking things so I will definitely give it a try.
Click to expand...
Click to collapse
use this one
these work for glacier but are in other threads, you'll notice
in any case, this is the one to use if you wanna save yourself some reading
also, the guy's a fricking genius or something, open up the file in that zip and see what he's doing...he's hosting his own gps servers

tnpapadakos said:
use this one
these work for glacier but are in other threads, you'll notice
in any case, this is the one to use if you wanna save yourself some reading
also, the guy's a fricking genius or something, open up the file in that zip and see what he's doing...he's hosting his own gps servers
Click to expand...
Click to collapse
Thanks. I just finished reading through his notes.

tnpapadakos said:
use this one
these work for glacier but are in other threads, you'll notice
in any case, this is the one to use if you wanna save yourself some reading
also, the guy's a fricking genius or something, open up the file in that zip and see what he's doing...he's hosting his own gps servers
Click to expand...
Click to collapse
Do you flash this in recovery?
Sent from my HTC Glacier using XDA

Supamike88 said:
Do you flash this in recovery?
Sent from my HTC Glacier using XDA
Click to expand...
Click to collapse
The gps.conf by crypted file can be flashed in recovery. You can also just open up the zip and copy it using root explorer, etc.

Gadianton said:
The gps.conf by crypted file can be flashed in recovery. You can also just open up the zip and copy it using root explorer, etc.
Click to expand...
Click to collapse
somtimes I just add it to the rom before flashing, and you have to also add the SuplRootCert to system/etc, but if he comes up with an update in between roms, i just flash from recovery....

Gadianton said:
Since about January, all the CM7 based roms have had flaky GPS for me. Basically it loses the signal after about 5 minutes. A quick GPS on/off cycle usually fixes the problem. However, I really don't like the distraction
(and the danger) of messing with the gps when driving 70 mph.
I spent quite a bit of time searching for a solution on this and other forums, but found nothing helpful. Yesterday, I got the idea to try out one of the Sense GPS drivers in the AOSP roms. I extracted the attached file from one of the Stock roms and replaced the AOSP driver.
The good news is it appears to work. In the 4 times I've driven I didn't have to do any GPS cycling.
Steps:
1) Extract the attached zip file.
2) Using Root Explorer or ES File Explorer (with the root option checked) copy the attached gps.glacier.so file into your system/lib/hw directory replacing the current file.
3) Reboot.
4) You may want to clear out the A-GPS state using the GPS status app, but I don't know if this is necessary or not.
Anyway, I hope this helps someone else. I am thinking of developing zip you can flash if there is interest in it. But in the meantime I wanted to post the fix, since I know there have been other people with the same problems I had.
I hope this helps!
Click to expand...
Click to collapse
Don't forget to check the permissions on the file. I am not sure if it was because I backed up the old one first and copied in the new one after, but I had to change the permissions to rw-r--r--.
This, I learned the hard way. I always forget something...

G8351427 said:
Don't forget to .....change the permissions to rw-r--r--.
Click to expand...
Click to collapse
definitely....i always check the permissions of the file i'm replacing and match that on a new file, or, if i'm inserting one thats not there, i look at the permissions of the surrounding similar files, and match it to those
otherwise, rw-r--r-- is usually the fallback

Yea I have noticed that the best GPS experience I have had was when the phone was completely stock the GPS worked great, locked on quickly, and never lost signal. After I flashed it and such the GPS has been a pain to get lock when I needed it the most.

I've found that any of the radios after the official Froyo version causes the GPS to fail after a few minutes as described by the OP. However, with some of the newer ROMS I've found that the newest radio doesn't completely lose the GPS signal but it does still seem to temporarily lose it but it then it comes back by itself (causes navigation to get stuck at a location for a minute or two every now and then).
I tried the driver and agps mod from this thread. At first it completely killed my GPS then someone posted about the required permission changes which fixed that. I haven't tried navigation so I can't say whether it prevents the temporary position loses, but it does seem to still be pretty slow to lock on and after it does lock on may take several minutes before the accuracy gets to a useful level.
I think I'm going to go back to the Froyo radio as that one seems to work the best for GPS and I'm not convinced it makes much of a difference for voice/data. Perhaps the Froyo radio with these mods would be the best?

tmagritte said:
I've found that any of the radios after the official Froyo version causes the GPS to fail after a few minutes as described by the OP. However, with some of the newer ROMS I've found that the newest radio doesn't completely lose the GPS signal but it does still seem to temporarily lose it but it then it comes back by itself (causes navigation to get stuck at a location for a minute or two every now and then).
I tried the driver and agps mod from this thread. At first it completely killed my GPS then someone posted about the required permission changes which fixed that. I haven't tried navigation so I can't say whether it prevents the temporary position loses, but it does seem to still be pretty slow to lock on and after it does lock on may take several minutes before the accuracy gets to a useful level.
I think I'm going to go back to the Froyo radio as that one seems to work the best for GPS and I'm not convinced it makes much of a difference for voice/data. Perhaps the Froyo radio with these mods would be the best?
Click to expand...
Click to collapse
I have noticed the "stuck position" before. I haven't paid attention to that with this mod before. I'll have to keep an eye out for it.

I have updated the OP to include a CWM flashable GPS_Fix.zip file. It worked for me, but if anyone wants to test it, I'd appreciate it.
The thing I am most curious about is if the file is copied with the correct permissions.
thanks.

Gadianton said:
I have updated the OP to include a CWM flashable GPS_Fix.zip file. It worked for me, but if anyone wants to test it, I'd appreciate it.
The thing I am most curious about is if the file is copied with the correct permissions.
thanks.
Click to expand...
Click to collapse
I flashed the update and after that the GPS locked on pretty quick. I haven't tested for navigation yet.

here's one with the gps.conf file, the supl.root.cert and the gps.glacier.so all put together if anyone would like to test it
quick satellite fixes and continuous GPS lock
(hopefully)

It worked on MIUI... Thanks...Its been losing signal for the longest time and now it locked in and never lost it again...
THANK YOU!!!!!!!!!!

spyderman33 said:
It worked on MIUI... Thanks...Its been losing signal for the longest time and now it locked in and never lost it again...
THANK YOU!!!!!!!!!!
Click to expand...
Click to collapse
I'm glad it helped you out!

Thanks best thing we needed yet. Works perfect wit miui.us.
Sent from my HTC Glacier using xda premium

I updated the OP to include the gps_update.zip put together by tnpapadakos and updated the thread title to include MIUI.

HOW TO: Install FXP113 Custom ROM on Xperia Play R800x

When installing FXP113 to my phone, I found that on bootup I would get an error on the phone process and I had no service. After trying a few different things, I finally found the solution: Install FXP112 first, then install FXP113 over it without wiping data. Here is a step by step tutorial on installing FXP113 on the R800x. It probably would work the same for all Xperia Plays.
Required: Rooted Xperia Play and unlocked bootloader.
Needed Files: FXP112 as modified by Chevyowner
FXP113 as modified by Chevyowner
Replacement build.prop file for R800x
Fastboot - Fastboot+ADB+Fastboot_Drivers.zip
Sony Drivers
Recommended: Boot into recovery and make a Nandroid backup before continuing.
1. Copy the files for FXP112 and FXP113 to your sdcard. You will need to access these from recovery.
2. Install Fastboot. Unzip the file into C:\fastboot.
5. 2. Extract the boot.img of your choice to the fastboot directory. You may use the one in FXP113, or DarkForest3.img or DarkForest4.img (available here.)
5. Enter into Fastboot Mode. - Turn off phone. Hold search button down. Plug in USB cable. The power light should be blue The first time you do this, you will be prompted for the fastboot drivers. They will be in C:\fastboot\fastboot drivers.
6. To flash the new boot image, go to a command prompt and change to the c:\fastboot directory. Then use the following command:
fastboot -i 0x0fce flash boot boot.img <----- the name of your boot image.
7. When finished, remove the usb cable. Power on the phone and enter into Recovery. On some kernels, you will press repeatedly the volume down button; on others, you will press repeatedly on the back button or possibly the search button.
8. You MUST clear Data, Cache and Dalvik Cache. It is also recommended by some people to clear the battery stats.
9. Install zipfile from sdcard. Select the FXP112 file first. Allow it to install and then reboot the phone. (I usually clear data, cache and dalvik again just to be sure.)
10. Activate your phone on the Verizon network.
11. Now shut down and reboot into Recovery again.
12. This time, clear ONLY cache and dalvik cache. Do NOT clear data.
13. Install zipfile from sdcard. Select the FXP113 file this time. Allow it to install and then reboot the phone.
14. Copy the build.prop file into /system. You may want to rename the current one first.
15. Reboot and enjoy! You should be up and running with full data, wifi access now.

re
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this

FPlusPS3 said:
So for step #10 do u get charged from verizon to activate ur new roms data?
And for #14 do u just copy it via root explorer to /system?
Thanks for taking time to write this
Click to expand...
Click to collapse
#10 There is no charge to activate the phone if you already have service. It's like dialing *228 and choosing option 1, only the system does it for you.
#14 Yes, you can just copy it to \system, but don't forget to change access to RW before pasting. You may also want to rename the old file first as a backup, although I never have.
Sent from my R800x using XDA

my phone gets stuck at the android screen after i flash fxp112

johnboyjr said:
my phone gets stuck at the android screen after i flash fxp112
Click to expand...
Click to collapse
What kernel did you use?
Did you clear data, cache and dalvik cache before you installed FXP112?
If yes, just for kicks, go clear it again.
Also, remember, the first boot after a clean install takes longer than normal.
Sent from my R800x using XDA

yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing

johnboyjr said:
yes i cleared them and and i tried DarkForest4 and fxp112
i waited over 15 min still nothing
Click to expand...
Click to collapse
OK. Well, if it were me, the next thing I would do is to flash back to totally stock and get that working. Then try it again.
Sent from my R800x using XDA

What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.

crono141 said:
What changes are in your build.prop? I've been running fine (except for one or two small problems) with the standard build.prop from FXP112.
Click to expand...
Click to collapse
I think it was just edited to identify the phone properly as an R800x. PaxChristos told me to use it when he helped me install FXP111 and I have used it ever since. I haven't had any issues at all with it, so you might give it a try if you're on Verizon.
Sent from my R800x using XDA

That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA

*22899 is the shortcut for activating service in case anyone wanted to just store it for future reference
-and you can also use flashtool to flash back to stock or flash a new kernel

*228 worked fine for me. semcsuite.apk won't show up in my app drawer. I moved it to /system/app and fixed permissions. Still not there.
Sent from my R800x using XDA

Wallrunner said:
That was only needed the first time Chevy made FXP111 work, he missed some things in the build.prop that created graphical artifacts in menus and such. All of his builds after that have the correct build.prop now.
Sent from my R800x using XDA
Click to expand...
Click to collapse
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA

re
Does Psxperia or XPERIA GAMEPAD games even work on cm9

For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.

FPlusPS3 said:
Does Psxperia or XPERIA GAMEPAD games even work on cm9
Click to expand...
Click to collapse
From what I have read... no. That is why I have not jumped ship to CM. Otherwise I would be there right now. So until they get the touchpads working I will wait, although I have also read they are working on creating from scrathc their own drivers for the touchpads as the current drivers now require SE framework...... so cross your fingers.

Nighty0 said:
For some reason, trying use videocall in gtalk worked fine at first, but changing to rear camera made gtalk fc. After that no camera works at all.
GPS only works on maps (no on gps status, or any other app), since my wifi neighbours are all on the google database i'm not sure if the true gps is really working.
And have another annoying things.
I'm hacking all my phones since android 2.1, and I cant consider this release as an true release candidate. Its more beta.
I have a r800i.
Click to expand...
Click to collapse
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in

agraceful said:
Not to be rude or by any disrespect but how isn't it a "true" release? A release is a release..being that it's in beta status doesn't mean it's any less, cm is always changing and improving so there is no hey this is the final version kind of thing..CDMA isn't even supported by cm at all so the fact we have cm9 before verizon gives it to us is amazing. Just to point out, this isn't hacking by any means, android is open source..it's like going into an open store and saying you're breaking in
Click to expand...
Click to collapse
Yes, giving their release to us is amazing, but saying that camera works on changelog, and not even the basic apps like gtalk and camera works, this barely can be considered as working.
As a software engineer I label as a beta, not RC anything. beta is to fix stopper bug like this, RC is for the little annoyances lonely.
For example, my work friend installed another rom on their htc sensation, labeled as beta and all features works, with jagged areas here and there.
And yep, I know the Team FreeXperia is a one guy team
I'm happy with all this releases, only frustrated because the thing is being labeled as working, when not. So I made a report here to make sure another person doesn't make the same mistake as me.

netizenmt said:
Thanks! Good to know, and one less thing to screw with in the future!
Sent from my R800x using XDA
Click to expand...
Click to collapse
actually this build.prop works better it lets Plants Vs Zombies and Asphalt 6 RUN and work

How do install install the custom rom and set up fastboot?

[Guide] Sound on F240 on CM11 E980 rom

Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
$> su
#> alsa_amixer
It throws some error but It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,

nice catch man...anybody with f240 already tested this?
will try to download cm11 roms and definitely going to try this one...

Thank you!
notohp said:
Issue: You flash e980 CM11 rom on F240 devices and get absolutely no sound.
Solution: I remember reading and trying somewhere that skvalex' Alsamixer app brings back sound with e980 rom on F240. Problem was, same app did not work with 4.4.2.
1. So I grabbed the files introduced by that app and copied them in their respective places.
2. chmod -R 755 /system/xbin/alsa* (Change permissions of alsa_ctl, alsa_aplay, alsa_mixer to rwxw-xr-x). I did that from adb. I guess it can be done through root-explorer too.
3. Open terminal:
prompt> alsa_amixer
It throws some error about module not found or something. It's okay.
And voila! let there be sound...
Why this works: It was obvious that alsa driver for the sound card was not being loaded by default in CM11_e980. skvalex' alsamixer enables this for lot more devices because he wants his app CallRecorder to work on all those devices.
I am sure there's a more convenient method of doing this by editing alsa cards list for your device or something instead of dirty hack. If you know, please share.
Issues:
- This is not persistent. Every time you reboot your device, you got to run alsa_amixer again (or you can do it through some init scripts).
- I have only tested music and notifications. Not sure about calls.
- Not sure about compatibility issues as I just picked these files and copied them to 4.4.2 tree.
- You tell me...
I have attached the files here.
skvalex is the one deserving credit for all the work. I just used his work to our convenience.
EDIT:
I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine,
Click to expand...
Click to collapse
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!

esaintor said:
That is what I wanted. I was searching this for few weeks. I will test it today! oolay... by the way did you mean that Step 3 by this "Open terminal: prompt> alsa_amixer" ??? Can we just flash it after flashing ROMs? Thank you!
Click to expand...
Click to collapse
Yes just that. You can flash it right after flashing roms. :good:

no luck.
notohp said:
Yes just that. You can flash it right after flashing roms. :good:
Click to expand...
Click to collapse
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?

esaintor said:
I flashed it after flashing omni. And wrote on terminal as you suggest " alsa_amixer ". But it shows me error amixer: mixer attach default error. No such file or directory. So I rebooted my phone. Still no sound? What do I do now?
Click to expand...
Click to collapse
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.

Still...
notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?

notohp said:
Ignore that error. You should have sound soon after you execute that command. Don't reboot. Just check it in settings > sound. Let me know how it goes.
Click to expand...
Click to collapse
I tried on omni but no success
I executed this command didn't restart still no sound

esaintor said:
I wrote the command. I waited so long. 30mins. No sound comes to me. I replaced all files to flashable ROM. And flash it from CWM. Now I am waiting the sound. Could you upload the ROM you had installed successfully?
Click to expand...
Click to collapse
Okay I will test it with omni rom once I am back home. Could you point me to the link?

here is the link
notohp said:
Okay I will test it with omni rom once I am back home. Could you point me to the link?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2562998

GOT IT!!!
esaintor said:
http://forum.xda-developers.com/showthread.php?t=2562998
Click to expand...
Click to collapse
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.

esaintor said:
I figured it out how to make it successful. You forgot something to mention that ONE LINE before the command alsa_amixer.
$ su
# alsa_amixer
This is it. SU command makes the terminal rooted. So it can do whatever I want. Now we have to give a command alsa_amixer.
I have installed AOSP for E988. Sound is working fine. Thank you for your replies and cares.
Click to expand...
Click to collapse
Glad you got it worked...may be this line ..."I just replaced the original with a flashable zip. After flashing this, you still need to run step 3 as root after every reboot. I tried on CM11 rom and SlimKat. Works fine," had a brief mention but anyway...I will edit the OP...:good:

i have sound already but it reboot when make a call, maybe kernel is not compatible with F240

nguyenthienqui said:
i have sound already but it reboot when make a call, maybe kernel is not compatible with F240
Click to expand...
Click to collapse
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.

esaintor said:
Yeap, that's right. I have faced this problem yesterday. I restored stockish. Also CM11 for F240S drains my battery. Never find good ROM.
Click to expand...
Click to collapse
i had same problem with my f240k Android OS drained alot of battery so I switched to Mokee 4.4.2, its AOSP so like 99% CM
battery problem is fixed so is sound....get around 4 hours of SOT
try it if you like:
http://forum.xda-developers.com/showthread.php?t=2639469

Tested of F240L
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.

mudu8 said:
Just tried this using the CM11 E980 nightlies it worked on my F240L.
Its incompatible with the voice calls however as phone reboots upon dialing a number.
Good Work though as the sound issue had been driving me nuts trying to figure out.
Click to expand...
Click to collapse
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.

notohp said:
Actually the problem of calls not going through is not an issue for me. I am an avid music listener and am always on earphones. The problem with rebooting on calls is because of proximity sensor.
So basically, if you're on earphones, then you proximity sensor doesn't come into play and you can make/receive calls.
If I find a fix for this one that doesn't involve flashing another kernel, I will post it here. Actually there's a trick but that involves hacking sensors file in the kernel and would render proximity sensor useless. I have used it once as I don't care about that sensor anyway. But it causes little inconvenience in my flashoholicism.
EDIT:
May be someone can try this (http://forum.xda-developers.com/showthread.php?t=2436999? Am at work and only have my work device with me currently.
Click to expand...
Click to collapse
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.

mudu8 said:
Thanks but i think the least involving method would be to extract the kernel from this CM11 am running it on my phone got it on a chinese site.
Here's the link http://pan.baidu.com/share/link?shareid=802794836&uk=1392791443 password is "yxnj" to enable download of the file.
It works on F240L but i think also S/K are supported but it comes with lots of chinese bloatware so if we could get the kernel.
We could just flash it on top of E980 Nightlies directly from CM themselves bypassing the chinese bloat and also keep up to date with new bug fixes and updates.
Click to expand...
Click to collapse
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.

notohp said:
Yeah that's the quickest way and I have tried that kernel. But for my usage, I find CM kernel more stable. Also, I want to try other kernels (present and future) that are out there for E980. With CM11 converging on a stable release for E980, I sure want to use that with it's kernel. But, again, that's a personal preference.
Click to expand...
Click to collapse
I'm not very conversant with the methods of kernel extraction etc.
I reckon you could compare the chinese CM11 Kernel to the stock CM11 one and see which files need manipulating in order to get it working and also what differences exist between the E98X and F240x models.
No pressure though it just my opinion.
It seems F240 models get little support around here, so if we could figure this out it would be great.