Develop Bugs

What kernel to fix wi-fi issue?

Hi,
I tried to root my friend's Desire and on 1 day, we had all the problems there could have been with the rooting process, including all kind of bootloops, wrong wipes, using wrong sdk-kit, usb brick, usb-unbrick etc etc... It's just like an season of 24 where all s*** can occur on 1 day
Now, we finally got the usb unbricked again and just went into recovery, flashing MCR3.1 with the online kitchen. Flashing the MCR3.1 went well, but there's 1 probem: the Wifi was broken. It didn't work with the MCR3.1. I remember having the problem too, and I read that it was due to a kernel-problem. So I downloaded the custom kernel: http://android.modaco.com/content/htc-desi...for-htc-desire/ and my Wifi was fixed again.
BUT I tried the same at my friend's Desire, downloading the same kernel, but once booting, I got stuck at the HTC Logo, the one without the 'quietly brilliant'-slogan... I restored the nandroid backup and could boot again, but again, no wifi enabled. Then I tried to flash the same zip on my phone, and my wifi DOES work with that rom. So there's nothing wrong with the rom.
I went to compare the software versions, and the only thing that differs is the kernel, which should be the reason why his wifi is broken:
his desire:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my desire:
So, the solution is to flash a compatible kernel, but like i said before, the one from modaco: http://android.modaco.com/content/htc-desi...for-htc-desire/
doesn't work, the phone just hangs at the htc logo... What's wrong...? And I thought the custom kernel was included into the 3.1 rom?

pina_ said:
Hi,
I tried to root my friend's Desire and on 1 day, we had all the problems there could have been with the rooting process, including all kind of bootloops, wrong wipes, using wrong sdk-kit, usb brick, usb-unbrick etc etc... It's just like an season of 24 where all s*** can occur on 1 day
Now, we finally got the usb unbricked again and just went into recovery, flashing MCR3.1 with the online kitchen. Flashing the MCR3.1 went well, but there's 1 probem: the Wifi was broken. It didn't work with the MCR3.1. I remember having the problem too, and I read that it was due to a kernel-problem. So I downloaded the custom kernel: http://android.modaco.com/content/htc-desi...for-htc-desire/ and my Wifi was fixed again.
BUT I tried the same at my friend's Desire, downloading the same kernel, but once booting, I got stuck at the HTC Logo, the one without the 'quietly brilliant'-slogan... I restored the nandroid backup and could boot again, but again, no wifi enabled. Then I tried to flash the same zip on my phone, and my wifi DOES work with that rom. So there's nothing wrong with the rom.
I went to compare the software versions, and the only thing that differs is the kernel, which should be the reason why his wifi is broken:
his desire:
my desire:
So, the solution is to flash a compatible kernel, but like i said before, the one from modaco: http://android.modaco.com/content/htc-desi...for-htc-desire/
doesn't work, the phone just hangs at the htc logo... What's wrong...? And I thought the custom kernel was included into the 3.1 rom?
Click to expand...
Click to collapse
Ok, if you've been messing around flashing kernels then that's why wifi isn't working. Your kernel and your wifi driver bcm4329.ko need to be from the same kernel build. you can't replace one and not the other.
I would suggest reflashing a complete ROM again.

martinlong78 said:
Ok, if you've been messing around flashing kernels then that's why wifi isn't working. Your kernel and your wifi driver bcm4329.ko need to be from the same kernel build. you can't replace one and not the other.
I would suggest reflashing a complete ROM again.
Click to expand...
Click to collapse
I don't understand because I did not mess around with kernels. The only time I tried to install a new kernel was AFTER wifi was broken. But flashing that other kernel causes the desire not to boot anymore...
And the rom I installed on that desire is exactly the same rom as mine now on my desire. And with that rom, I have the broken wifi on his desire, but not on mine.
Do you suggest me to flash a COMPLETE MCR3.1-rom again instead of a custom one with the kitchen? Because in the complete one, the kernel is included?

bump
please someone help

you sure your doing a full wipe? also check the HBOOT on both desires...

I think you should consider flashing back to stock ROM as that will give you the stock kernel too.
See the bottom of post #4 via this link for details: http://forum.xda-developers.com/showthread.php?t=696189

[Q] Missing Notification Bar

Hey all,
I did a search and read a few threads and couldn't find an answer. I have managed to lose my notification bar. The phone boots fine, I get notification sounds and can still pull the bar down as though it were there, but it (and anything on it) does not display at all. I have flashed different roms, cleared cache and done factory resets and still cannot seem to recover the top notification bar. Sometimes it shows up for a while, then it is gone again. Anyone have a way to fix this or a way to revert back to system defaults and start fresh?
Also, a recovery from my backup did not resolve this issue. I had though it was just a bad rom flash and was shocked to find I could not resolve the issue with any rom. Any ideas would be helpful, but replies might take a day or so as the issue is intermittent. Thanks.
View attachment 1476591View attachment 1476604View attachment 1476605

About7Narwhal said:
Hey all,
I did a search and read a few threads and couldn't find an answer. I have managed to lose my notification bar. The phone boots fine, I get notification sounds and can still pull the bar down as though it were there, but it (and anything on it) does not display at all. I have flashed different roms, cleared cache and done factory resets and still cannot seem to recover the top notification bar. Sometimes it shows up for a while, then it is gone again. Anyone have a way to fix this or a way to revert back to system defaults and start fresh?
Also, a recovery from my backup did not resolve this issue. I had though it was just a bad rom flash and was shocked to find I could not resolve the issue with any rom. Any ideas would be helpful, but replies might take a day or so as the issue is intermittent. Thanks.
View attachment 1476591View attachment 1476604View attachment 1476605
Click to expand...
Click to collapse
Based on the pic, you have modded the notification bar. Maybe it's a problem with the mod.
Sent from my SPH-L710 using xda app-developers app

Nova launcher has a option to turn it off or on. But I'm betting one of your mods messed it up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from Pluto.

I thought a full wipe and re-flash, with the same rom or another, would clear any mods. Is that incorrect? If it doesn't clear, does anyone have a stock notification zip I can flash or is there some alternative?

I would think a full wipe would as well... idk that's odd.
You could try going back to 100% bone stock.
Sent from Pluto.

Was you running a rom with the center clock mod? I've noticed it happens to some but not all when running the center clock.
Edit: sorry just noticed you said you tried other roms.

How weird. That started happening to me out of nowhere but only sometimes and only on the lockscreen and only after I installed a custom kernel. But it still happens on occasion even when on stock kernel.

freeza said:
How weird. That started happening to me out of nowhere but only sometimes and only on the lockscreen and only after I installed a custom kernel. But it still happens on occasion even when on stock kernel.
Click to expand...
Click to collapse
I had a custom kernel to go with Goodness. But I cannot figure out how to fix this. Maybe a stock kernel flash? It is about the only thing I haven't done.
**EDIT**
After playing around I still have the issue. Using the Modem AIO did not resolve the issue. Running Paranoid Android from the Original Android Development threads did resolve the problem entirely, however. I am honestly at a loss on this one. If anyone has any ideas I would love to have them. I don't have any issues running original ROMs, but there were a few that I was fairly fond of that I would like to move back to if possible.

[Q] My nexus is terribly slow

Hey,
I got my nexus 1,5 months ago and it was pretty fast on 4.1.
Then I updated (OTA) to 4.2 and I got a lot of bugs like
screen doesnt turn on during call (not via turning and not via power button)
switching the phone on (to lockscreen) takes 3 press on power button
camera app takes hours to start
Then I unlocked the bootloader and installed a custom ROM (any 4.2 from xda, don't remember the name)
But it had the same problems.
Then I downgraded to aokp 4.1.
The call problem (phone crashing during call) didn persist but camera was still slow and after one day all the other apps too.
Facebook takes like 10-20 secs to open completely. Same for whatsapp. Even SMS takes 5-15 secs.
I reinstalled everything (after complete) wipe but still the same. I switched to cm 10.0, also the same but now also the phone takes 10 secs to open.
And it crashes sometimes when the screen off and I have to take the battery out.
Is my phone broken somehow?

flash the 4.1.2 google image and see if that helps

You may be suffering from this bug: http://forum.xda-developers.com/showthread.php?t=2029246
From what I've found out, you need to flash a factory image and afterwards flash your favourite ROM. The speed will be back to normal, at least for a short while.

Try to flash Purity 3.1 Rom. Is smoothness and battery saver.
Enviado desde mi Galaxy Nexus usando Tapatalk 2

Install and open this app: eMMC Brickbug Check
(Not to check if you got the eMMC brick bug, but to get your chip type and production date)
If it shows chip type V3U00M, you got this bug.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution without wipe

ph4zrd said:
Solution without wipe
Click to expand...
Click to collapse
The discard and dd/rm method did not work for me and others reported similar results.
The only thing that brought back the speed (at least temporarily) was to flash a factory image.
It's 'sort-of' non wipe as I took a nandroid backup, wrote the factory image and restored the nandroid image.

wkwkwk said:
The discard and dd/rm method did not work for me and others reported similar results.
The only thing that brought back the speed (at least temporarily) was to flash a factory image.
It's 'sort-of' non wipe as I took a nandroid backup, wrote the factory image and restored the nandroid image.
Click to expand...
Click to collapse
This is strange as most users reported positive results using this workaround...
Also, it is the only permanent fix for the bug currently available (if it works for your phone, of course).
Maybe some kernels have disabled the TRIM/ERASE capabilities of the eMMC driver or something similar, which blocks the discard option from working?!
Can you please post your exact eMMC chip type, production date & firmware rev?

Flash Factory image. I had the same problem but after flashing Factory i havent had any issues(2 months ago)
Sent from my Galaxy Nexus using xda premium

ph4zrd said:
This is strange as most users reported positive results using this workaround...
Also, it is the only permanent fix for the bug currently available (if it works for your phone, of course).
Maybe some kernels have disabled the TRIM/ERASE capabilities of the eMMC driver or something similar, which blocks the discard option from working?!
Can you please post your exact eMMC chip type, production date & firmware rev?
Click to expand...
Click to collapse
Interesting idea about the kernel having the trim disabled, I'm using CM10 (4.1.2) with franco kernel 300.
I have enabled the 'discard' option at mount but a few tests revealed that performance is not recovered (I tried even running sync a few times after rm).
I have:
model: V3U00M
date: 10/2012
fwrev: 0xd
hwrev: 0x0
Thanks.

wkwkwk said:
Interesting idea about the kernel having the trim disabled, I'm using CM10 (4.1.2) with franco kernel 300.
I have enabled the 'discard' option at mount but a few tests revealed that performance is not recovered (I tried even running sync a few times after rm).
[...]
Click to expand...
Click to collapse
Checked some kernel sources. Trim should work, at least in CM and franco kernel.
So it must be another problem on your phone...
Btw 'sync' only forces flushing of the filesystem buffers. This is also done at unmount/reboot and automatically as part of normal operation, so it should not be necessary.

Strange. I even rebooted a few times and the phone was still laggy and androbench was reporting between 0.5-1MB/s, sometimes even less.
After writing factory image it jumps to 10MB/s.
Are there any other things I can test?
Another thing, I tried enabling encryption immediately after writing the factory image and the performance dropped instantly, I'm assuming the encryption process writes zeroes (or random data) to fill the whole space.
Thanks.

GPS Fix for ls980 cm11

After an exhaustive search to try to fix the GPS on mySprint LG G2 I think I have finally found a remedy that I have tested on cm11 nightly rom. I have tried all the fixes I could find including putting cardboard under the contacts on the back cover. I still was unable to get any kind of GPS response at all. Now after creating this flash-able fix I can lockon in less than a minute even indoors.
The fix is a combination of files I found during my search for a fix which include some .so files I have been told came from the PAC rom including the GPS confirm file I took from a stock LG G2 rom
This has only been tested by me several times and only on a Sprint LS980 with cm11 nightly. When you upgrade to the latest nightly you must flash this file after upgrade, or at least I did, or you will lose GPS.
I just wanted to share the only fix that has worked for me with the community
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot is from inside my house next to a window of course.
Flash at your own risk! I assume no responsibility for bricking your device.
Those who own a device other than sprint are welcome to try this fix at your own risk and report back.
If this help you please feel free to hit the thanks button.

I couldn't get this to work for me. However flashing my nandroid back to stock and downloading the app GPS lock in the playstore, getting a lock, then flashing back to AOSP helped me get a lock on LP Resurrection. I assume that would also work for CM11. Not that that's new news but just confirming it worked for me.

carnivalrejectq said:
I couldn't get this to work for me. However flashing my nandroid back to stock and downloading the app GPS lock in the playstore, getting a lock, then flashing back to AOSP helped me get a lock on LP Resurrection. I assume that would also work for CM11. Not that that's new news but just confirming it worked for me.
Click to expand...
Click to collapse
Sorry it didn't work for you. I personally think the GPS in this phone sucks. I have heard of people .tot there phones to get GPS signal then re-rooting, installing recovery, and re-flashing the rom. That is just a lot to do for me. Like I said I have tried all the fixes and apps with no luck. I have to re-flash this after nightly updates or I have no GPS at all. Hopefully this will work for some people.

Do you think this might work for LP roms as well?

Williek113 said:
Do you think this might work for LP roms as well?
Click to expand...
Click to collapse
You could try it. Just make sure to make a nandroid first just in case.

who try it on CM12?

I did and it didn't work.

I just installed the latest nightly (CM12) and GPS work just fine.

I stand corrected, tried it on a highway and GPS was NOT working. I think I got fooled by phone locating itself by nearby WiFi APs.

Just an FYI, GPS finally works on latest CM12 nightlies.

GRRemlin said:
Just an FYI, GPS finally works on latest CM12 nightlies.
Click to expand...
Click to collapse
does sprint spark work with CM12 ?

maracuya said:
does sprint spark work with CM12 ?
Click to expand...
Click to collapse
No

You can pull your gps.conf file from your stock rom and override (or rename) the one in aosp/cm. I always do it that way and it works 100% of the time.
You can use root explorer or the like to add it. It's located in system/etc/gps.conf.

Anybody else had some luck with this patch?
I also tried to use the original gps.conf but same result no gps signal.

Please Help: No Signal / "service state: out of service" [With Screenshots]

I would be so grateful if someone more knowledgeable than I helps me troubleshoot this issue.
I bought a used Nexus 5x yesterday, everything worked fine and it was all stock, i checked my sim card and it worked on the phone.
I took it home unlocked the phone and installed a custom ROM, somehow In the process I seem to have done something that has made it so the phone cannot connect to my mobile network. It seems to be able to see the mobile network [ imgur.com/IdpFg0O ] but not connect [ imgur.com/5edM5G6 ]. The phones APN setting [ imgur.com/5J1Ixoy ] appear to match the information provided on various websites.
The SIM status page [ imgur.com/WGWnqSM ] might give some indication as to what the problem is. It lists the network as "unknown" and the service state as "out of service" and mobile network state as "disconnected."
What I have already tried:
Restarted the phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Removed and reinserted the SIM card
Tried another SIM card
Manually set APN settings
Manually set Network
Wiped Phone (factory reset)
Reflashed the same custom ROM
Reflashed another custom ROM
Reflashed the Stock ROM
Could I have maybe somehow screwed up the /EFS partition when I was wiping or installing the new ROM?
I dont really know what else to do to troubleshoot or try to fix the problem. I would be sooo sooo grateful if anyone more knowledgeable than I am could help me troubleshoot this issue, there doesn't seem to be much information out there about this problem. I really don't want to have bricked my phone the day after I bought it, so please, if you can offer any assistance helping me understand and diagnose the problem, I would be so grateful!
All Screenshots: imgur.com/a/sq1JbXF

All rooms require a specific version of radio.img make sure you have the right one otherwise you'll have problems like that check out in the xda thread of your rom what version it requires and then download the factory image and flash the radio.img with fastboot

Hi kastik4,
Thanks for the reply, I appreciate you taking the time to lend a little help.
So if I understand you correctly what you are saying is that each specific ROM has its own radio.img and that a mismatch could potentially be causing my problem?
If so, I'm not sure if this is the problem as one of the troubleshootings steps i've taken is trying to go back to the stock factory ROM following Googles instructions and (I believe) flashing the stock radio.img. However, it is entirely possible that I did something incorrectly in this process so I think I will try to redo the process and make sure I got everything right tomorrow.
Any other ideas as to what could be the issue?

@local5x: you wrote, that you reflashed stock ROM. If you did it via flashall.bat (means you lost /data and root) and error persists, probably your hardware is gone.
Messed efs you can detect easily: IMEI shown in settings and on your contract, must be identical.
Generally is the newest radio-image fine. @kastik4's advice is mostly overdressed.

Hey, did you solve your issue or you still need some help?

kastik4 said:
Hey, did you solve your issue or you still need some help?
Click to expand...
Click to collapse
No, I did not solve the problem. I got a cheap phone in the meantime, but haven't been able to figure anything out with the 5x. Maybe it is a hardware issue, IDK, and I dont really know where else to go in terms of troubleshooting, I'm sorta in over my head here. I wish I could narrow down the problem though, even If it is just to find out that it is a hardware problem and I'm screwed at least I would have a little clarity/closure.

hello I have the same problem my phone says no service and only emergency calls, I followed some solutions nothing yet. I would like to find a solution since it does not detect the available networks