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.

HELP! Installed rom and now earphone doesn't work (or any other roms installed either

I'm not sure what happened but this morning I installed Codename Android's rom since everyone's been speaking so highly of it. I immediately got reboots right after starting. The screen would freeze and then the phone would reboot. I figured there was something wrong so I formatted data/factory reset, formatted cache and even formatted /system and installed it again. No reboots but the earpiece would not work on phone calls (speaker phone does). I also noticed that the screen doesn't turn off when I hold the phone to my face (so the proximity sensor seems to be messed up too). So I installed another rom: Redemption Rom. Same problem. I installed GummyNex, same problem.
I even unrooted and relocked the bootloader and EVEN THEN the earpiece did not work.
I feel like this is a software issue because it happened after installing a rom AND the proximity sensor doesn't work which seems strange for both that and the earpiece to stop working at the same time...
Is there something else that I haven't tried yet? Any suggestions??
I've only had the phone for a couple days so it could easily be a hardware issue I suppose, but I wanted to check if anyone had anything like this happen to them.*
Thanks guys!

Codename Android....if everyone's so highly speaking of it how come I haven't heard of it?
- Which version of the phone you have? CDMA? I'm assuming?
- What kernel?

Codename Android is one of the most popular roms on Rootzwiki

HeliosAI said:
Codename Android is one of the most popular rom on Rootzwiki
Click to expand...
Click to collapse
This is XDA, not Rootzwiki. I googled it. Answer the rest of the questions.
Have you tried flashing another ROM? Flashing stock images provided by Google?

CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?

I tried a few other roms and the issue was still there as well.

HeliosAI said:
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
Click to expand...
Click to collapse
And you've checked the obvious that the headphones work on another device correct? Tried another headphone on the phone?
If you fully wiped the phone and tried it with another ROM then it's most likely a hardware problem. And maybe it was a coinicidence that it broke right when you flashed the ROM.
Go into your about phone and tell me what it says for "kernel version"

Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.

HeliosAI said:
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
Click to expand...
Click to collapse
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.

zephiK said:
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
Click to expand...
Click to collapse
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1

HeliosAI said:
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
Click to expand...
Click to collapse
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.

zephiK said:
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
Click to expand...
Click to collapse
Yeah very weird. Thanks again man, really appreciate it.

HeliosAI said:
Yeah very weird. Thanks again man, really appreciate it.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck with your new replacement when you get it though.

[Q] Help! NFC broken, cannot access settings

Sorry if this has been covered before, I'm normally good at self diagnosing my problems and fixing them with a simple search but I cannot find my answers to this problem.
I have rooted and rommed my device a few times over (bugless then AOKP currently) and some where along the line I have lost NFC abilities. Even the ability to access the "more" tab in the connections settings. If I click on it all it does is freeze and go black.
Is there any fix to this? Please help
Thank you in advance..

It looks like NFC capability is under 'non-working' list. Try to flash different rom and see what happens.

dcdgoth said:
It looks like NFC capability is under 'non-working' list. Try to flash different rom and see what happens.
Click to expand...
Click to collapse
Really?? Where did you hear that because I'm on aokp and it works just fine.
Link me to where you saw that.
OP just they reflash your current rom and see what happens.

nodstuff said:
Really?? Where did you hear that because I'm on aokp and it works just fine.
Link me to where you saw that.
OP just they reflash your current rom and see what happens.
Click to expand...
Click to collapse
he said he already re-flashed it. if the rom is perfectly fine accordingly, why is he having the problem? do you have any suggestion to fix the issue?

dcdgoth said:
he said he already re-flashed it. if the rom is perfectly fine accordingly, why is he having the problem? do you have any suggestion to fix the issue?
Click to expand...
Click to collapse
He never said he reflashed it, he said he flashed several different roms on it and with his current one his nfc doesn't work.
I know that nfc isn't on the not working list as I have that EXACT rom and it works fine.
So a reflash is the best option, wipe cache, system and dalvik, reflash rom and gapps and kernel and see how it goes.
Ps this is a nexus device, roms are mostly built from aosp so chances of things not working in roms are highly unlikely unless there is a problem with that particular device.
All the drivers etc are released for nexus devices so everything works.

I'm so close to downgrading....

Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.

Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.

Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...

If you updated from 4.1 to 4.2 without a full wipe there's potential for a lot to go wrong. There could be some app running as a service that isn't fully compatible with 4.2 causing your issues.
With that being said, I would try fully resetting the device, no need to re-flash the stock image because it's already in place on the device anyway.
Install apps that are known to work on 4.2 ONLY. Then, you can begin testing to see if it becomes stable. After that, do what you want.

mortenmhp said:
Like everyone else you should try a fresh install of the factory image wiping everything without restoring any data. It shouldn't matter if you are going to downgrade anyway.
We are many who have had no issues at all, so give it a shot.
Click to expand...
Click to collapse
Thanks, I'll give a try!

cymru said:
Lots of threads already on these issues.
Just downgrade now and save us having to listen to more whining...
Click to expand...
Click to collapse
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.

g8who said:
Not all of us have the time to look through all the threads to make sure threads aren't duplicate buddy.
Click to expand...
Click to collapse
Yeah, it's as if someone should add a search button to the forum :silly:

cymru said:
Yeah, it's as if someone should add a search button to the forum :silly:
Click to expand...
Click to collapse
But searching takes time...
And it's not like you can make it through a page in either General or Q&A without tripping over a 4.2 whine thread.

g8who said:
Having upgraded to 4.2.x now for about a month I have nothing but fustrations about the upgrade. I've had probably 5-6 random reboots where as on 4.1.x I had none. The phone has had problems connecting to data where the only remedy was to reboot. I've also had problems connecting with GPS AND bluetooth where only a reboot would fix things. The OS studders much more than before and (it could be my imagination) it seems some apps run slower than before. With that said if I have to reboot one more time this week I will be downgrading.
BTW I'm stock with bootloader unlocked on yakju.
Click to expand...
Click to collapse
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.

jpildave said:
if you're on the VZW Galaxy Nexus, then i strongly recommend getting the mmuzzy rom. i think it's made specifically for that carrier/model only. it's been great for me so far. so smooth, no issues thus far!
i don't know how much experience you have with swapping roms, but you should use the Super Wipe utility that mmuzzy recommends.
Click to expand...
Click to collapse
This guy is correct MMuzzy has been the most stable for Vzn Gnex. I only have a qualm with the GPS, but that's every phone
Sent from my Galaxy Nexus using xda premium

Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1

Only bluetooth problem
LeBaldi said:
Most of people that have problemas... solve with a clean install... i dont know why dont try before back to 4.1
Click to expand...
Click to collapse
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again Also... sometimes when the phone goes into sleep mode it disconnect the connection with handset... It never happen in 4.1.
I downloaded the factory image of 4.2.1 from Google and flash it... still the same. I saw people saying a clean install... Should I do another kind of install other than I did?
Can someone please tell me if got this kind of bluetooth problem and have solved it? How?
Thanks

abcorp said:
Hi.
I only have problems in bluetooth in 4.2.1... Sometimes I turned it off and I cannot turn it on again
Click to expand...
Click to collapse
i have also encountered that behaviour, gets greyed out while "Turning off".

[Q] Sprint LG G2 GPS issues with 4.4.2

I recently flashed to cyanogenmod 4.4.2 now my GPS is totally inaccurate. Anyone got any ideas what went wrong?

Himay85 said:
I recently flashed to cyanogenmod 4.4.2 now my GPS is totally inaccurate. Anyone got any ideas what went wrong?
Click to expand...
Click to collapse
I've had the same problem when flashing to cm11. The only way I could get it to work properly was to flash back to my stock backup and get a gps lock, then reflash cm11 again and try locking with gps. People recommend running an app called GPS status too, it shows the number of satellites available and the number of satellite connections.

roper15 said:
I've had the same problem when flashing to cm11. The only way I could get it to work properly was to flash back to my stock backup and get a gps lock, then reflash cm11 again and try locking with gps. People recommend running an app called GPS status too, it shows the number of satellites available and the number of satellite connections.
Click to expand...
Click to collapse
Thank you I'll give it try. I'll have to find the stock ROM for my phone. I didn't back it up like a newb

I have been reading that the GPS issues are hardware related and it can be due to the lack of contact on the connector which is causing this issue. Most people were able to fix it by opening up the phone and putting some electrical tape to make a nice contact on the connectors.

ericdabbs said:
I have been reading that the GPS issues are hardware related and it can be due to the lack of contact on the connector which is causing this issue. Most people were able to fix it by opening up the phone and putting some electrical tape to make a nice contact on the connectors.
Click to expand...
Click to collapse
I don't think it's primarily hardware related when most of us didn't have issues before 4.4.2.

I've tried numerous roms for the Sprint LG G2 that did not have GPS, but I think I've found a sort-of solution to it... I basically stole the gps ".so" files from the only rom that I know had working GPS... Paranoid Android. This was over a month ago however, and I've been reusing the same files over CM and Mahdi ever since, so I'm not sure if their updates could have broken GPS, but if that's the case I can share the files that I've been using with CM. Not sure how to make it into a flashable zip however, so they have to be replaced manually.

Hakukoru said:
I've tried numerous roms for the Sprint LG G2 that did not have GPS, but I think I've found a sort-of solution to it... I basically stole the gps ".so" files from the only rom that I know had working GPS... Paranoid Android. This was over a month ago however, and I've been reusing the same files over CM and Mahdi ever since, so I'm not sure if their updates could have broken GPS, but if that's the case I can share the files that I've been using with CM. Not sure how to make it into a flashable zip however, so they have to be replaced manually.
Click to expand...
Click to collapse
Can you share these files? Would they work on a stock based ROM?

ledvedder said:
Can you share these files? Would they work on a stock based ROM?
Click to expand...
Click to collapse
I don't mind sharing them, but not sure if they work on a stock based ROM as I haven't tried it. All the ROM's I've been testing have been AOSP-based... CM/PA/Mahdi/Omni/PAC/etc. I don't claim to know or understand how or why it works... but if it works for you too, great! If not, please don't blame me if it causes a brick or something.
Additionally, I don't know how to make this flashable... my method has been to extract the files, then reboot into Phil's CW Recovery and manually copy the files over with the Aroma File Manager. I included a GPS.conf file that I've modified to improve gps for my region, you may wish to exclude it.
[Edit] If this "does" work, be sure to thank the Paranoid Android team for whatever voodoo they did to make GPS work on their ROM.

Hakukoru said:
I don't mind sharing them, but not sure if they work on a stock based ROM as I haven't tried it. All the ROM's I've been testing have been AOSP-based... CM/PA/Mahdi/Omni/PAC/etc. I don't claim to know or understand how or why it works... but if it works for you too, great! If not, please don't blame me if it causes a brick or something.
Additionally, I don't know how to make this flashable... my method has been to extract the files, then reboot into Phil's CW Recovery and manually copy the files over with the Aroma File Manager. I included a GPS.conf file that I've modified to improve gps for my region, you may wish to exclude it.
[Edit] If this "does" work, be sure to thank the Paranoid Android team for whatever voodoo they did to make GPS work on their ROM.
Click to expand...
Click to collapse
Thanks, but it didn't work. Gave me a bootloop