I've been trying multiple JB ROMs over the past few days and have been unable to get the GPS working. Specifically I've tried AOKP(4/7), Cyanogen10.1 (4/4 and 3/22), and codefireX SR19.
I've tried with and without the inspiremod+gpsfix. The GPS works on stock 2.3.3 so it isn't HW. I've tried swapping out the gps lib with other versions including from the stock rom.
I'm beginning to suspect the radio though other users seem to be using it with success (12.69a.60.29_26.17.14.11). I tried flashing another radio using the bootloader with PD98IMG.zip on the SD card, but the file either ditches instantly or hangs while parsing (I suspect this is a safeguard in the bootloader?). My device is not S-OFF (I arrived a bit late to that party), however I've read conflicting reports that you can do this without S-OFF using that method.
Everything is great, if I can just get the damn GPS to work. I've burned 8 hours running through options and I'm coming up empty. Hopefully one of you has some magic you can sprinkle on this issue.
In a last ditch effort I tried JellyTime 4.2 R6.1 and had some success. GPS works now. Perhaps it's a kernel issue. I am curious as to why that might be. This seems to be 4.2.1 instead of 4.2.2 so perhaps that has something to do with it.
Related
Hey all,
I picked up a cracked screen Sensation for my son and discovered it also had funky wifi/BT. It was bone stock running 4.0.3.
I unlocked the boot loaded, S-OFF'd, rooted and updated firmware to 3.33.
Did my research here and determined my issue was HDW related. So I order a new digitizer and LCD flex (the later includes the wifi chip).
While I waited for my kit to arrive I flashed CM10, 8/4 build I think.
Well yesterday I did my repairs and fired up the phone only to see wifi stuck at turning on - and the phone rebooting every so often. BT, however was now working fine.
So here is the twist.
I restored my stk 4.0.3 rooted nandroid and wifi works fine!:good:
But if I do a clean install of CM10 - again wifi does not work
I have read about the issues with wifi and being S-ON, but I am S-OFF.
Any thought s on how to get CM working?
micl9 said:
Hey all,
I picked up a cracked screen Sensation for my son and discovered it also had funky wifi/BT. It was bone stock running 4.0.3.
I unlocked the boot loaded, S-OFF'd, rooted and updated firmware to 3.33.
Did my research here and determined my issue was HDW related. So I order a new digitizer and LCD flex (the later includes the wifi chip).
While I waited for my kit to arrive I flashed CM10, 8/4 build I think.
Well yesterday I did my repairs and fired up the phone only to see wifi stuck at turning on - and the phone rebooting every so often. BT, however was now working fine.
So here is the twist.
I restored my stk 4.0.3 rooted nandroid and wifi works fine!:good:
But if I do a clean install of CM10 - again wifi does not work
I have read about the issues with wifi and being S-ON, but I am S-OFF.
Any thought s on how to get CM working?
Click to expand...
Click to collapse
Sometimes ROMs have problems with wifi, I had similliar problem with another ROM.
Some users with HTC Amaze report builds prior to April 5 had Wifi problems. Did you try CM10.1/2? For me there is no problem with wifi at all, worth a shot.
Maybe try a different ROM?
I have also experienced some wi fi issues with some of the CM 10.1/10.2 ROMS. Since there is not really an "official" CM 10.1 ROM for the sensation, you sort of have to accept that there may be some bugs. I would suggest trying CM 9.1 and see if that works for you. Since you seem to be doing a complete wipe and format before the upgrades, the only other problem could possibly be some sort of hardware issue. However, I suspect that since it worked well on a previous ROM that the problem is ROM related. I would suggest you try all the various ROMs to see if the problem goes (mostly) away on one of them. I'm current running a 10.2 ROM and have noticed intermittent problems with connecting to Wi fi, but, on the most part, things work fine.
Good luck!
This has happened to me several times and I am seeing that other people are running into this problem with no fix found.
Everytime I try to install CM10.2 onto my xt926 I can never get past the unlocked bootloader warning screen after a reboot. I can still access CWM which is the recovery I'm using. I have tried clearing cache, data, factory reset, fixing permissions, reflashing the rom. The only way to get a working phone again is to flash stock 4.1.2 using RSD.
Then I remembered seeing an article a while ago saying that their were two versions of an OTA update for Razr HDs because for some reason their were slight differences between some phones, hardware wise.
Could this be the reason for these random phones not accepting CM10.2 installs?
Also if anyone has any ideas to get past this. I read someone had luck toggling bluetooth on and off for some reason but it didn't help me. I'm at a loss here and would love to play with Android 4.3 but I guess its just not in the cards...
ive got the same problem to i finally decided to get rid of safestrap and unlock my phone. now im stuck on stock rom because no roms will work after a reboot. theres two diferent stock 4.1.2 firmware files. one says mr4 the other one says mr2 anyone know the diference?
Not sure. I just use the RazrHD Utility 1.21 for that, its a lot easier. Also I have heard that 10.1 may work for us, just not 10.2 for whatever reason
I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
lesmorton said:
I'm hoping for some friendly advice - I have a Desire S which was rooted last year and I installed CM10 to try out JB. All has been working well )part from the occasional reboot) however couple of days ago the battery started draining quickly, the phone became very hot and the wifi stopped working. After various wiping of caches and rebooting I decided to try some other ROMs (Fallout Evolution V5, Miui, IceDS) and although they all installed OK I still have no wifi and now the mobile network won't work.
It worked on Fallout at first but when the wifi wasn't working I wiped and re-installed and it hasn't worked since. It does see the O2 network although the phone hd previously been unlocked to work with Vodafone, so I think I may have rolled back the radio somehow.
At this stage I'm not entirely sure if it is a software or hardware problem, and I din't know how to test the hardware.
The phone is currently as follows:
UNLOCKED
Saga PVT ship s-on RL
HBOOT -2.02.0002
Radio -3831.19.00.110
eMMC -BOOT
July 31 2012>15.41.32
Do I need to update the radio? If so, which version should I use? And do I need to s-off the phone first?
Any other help would be appreciated.
Click to expand...
Click to collapse
Did You tried installing stock rom again in your mobile
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
lesmorton said:
No I haven't. I assume this would re-install the correct radio?
Not sure where to get the stock ROM, or which one was shipped with the phone.
If I did get it can I flash it through recovery - I'm using 4EXT?
Click to expand...
Click to collapse
Boot into bootloader and run following command
fastboot get cid
Than you can know which ruu to flash. But don't forget to downgrade your misc version before fishing ruu
No ruu are flashed from PC
Sent from my HTC Desire S using xda app-developers app
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
lesmorton said:
OK, I have managed to get the phone back to it's stock ROM which is O2 in the UK.
I had previously unlocked the phone but it now won't accept anything other than an O2 SIM. When I scan for networks only O2 is seen. I still have the unlock code but when I put a Vodafone SIM in it doesn't prompt me for the unlock code. I'm just getting a Limited Service display.
Is there any way of forcing the unlock code prompt screen - say with keyboard numbers or via Fastboot?
Click to expand...
Click to collapse
do i understand things as they are?
do you intend to use simcards of another operator?,
well... that`s what branding stands for,
to make sure
you`ll not use any sim from different carrier...
is your phone simlocked as well,
or is it only a branded rom ?
..but why bothering to flash the phone with branded RUU,
(when there are quite a few generic ones, still floating around,..)
except, when one wants to claim a warranty..may be...
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
lesmorton said:
I flashed the O2 ROM as it was what was on the phone when I bought it and I was trying to get back to a radio that would work.
I have since managed to get the phone working OK with the Asda/Vodafone SIM but I am still having problems with the wifi (this is where it all started!). whenever I switch the wifi on it scans and then reports that it is unable to scan for networks, after 2-3 attempts the wifi switches itself off.
I'm still trying to find out if it is a software or hardware problem. Other than that all is working well on the Fallout v5 ROm I have flashed - although it does make the phone run hot.
Click to expand...
Click to collapse
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
asgardr said:
make backup (CWM)
try to find, and flash another kernel- custom,
..that may be a possible fix, for wifi issues,
as that is very often caused by,
not efficient, or completely missing drivers (0kb file size)....
...depending on the RUU version- flashed,
you might be interested in:
http://forum.xda-developers.com/showthread.php?t=1845039
otherwise, try to look for < unity > or < endymion > kernel.....
..Heat might be caused either
by battery,
or CPU - struggling with heavy flaw of graphics, (like < Google Earth >+< Browser >+<anything one prefers > )
or a nasty app ( or several ), constantly trying to consume, most of its resources...
..both quite simple to eliminate...
..and...undervolting, it helps to reduce heat - too...
Click to expand...
Click to collapse
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
lesmorton said:
I changed the ROM to IceDS v8 which seems to run cooler. I think part of the problem was with Titanium Backup running and the wifi kept searching for a network.
I am still having the wifi problem as it displays 'unable to scan for networks'. Having searched the internet extensively and tried a few different so called fixes I have come to the conclusion it is a hardware problem. When I get time I'll see if I can strip the phone and see if I can find the cause.
Click to expand...
Click to collapse
Well I stripped the phone and checked what connections I could but still no wifi.
I have used the RUU to get back to stock ROM and everything is fine except the wifi not working. Does anyone know if the wifi hardware is on the PCB, and if so where it would be in the phone. As the phone is in excellent condition I am thinking of getting a cheap phone with broken screen and just cannibalising it with my phone and building one good phone. It's just knowing what part of the phone contains the wifi hardware.
Any help would be appreciated.
OK, so last weekend I managed to get my HTC One X (Evita) rooted, but not S-OFF. I made it once successfully through the entire Facepalm process, but the phone remained S-ON for some unknown reason. It was said to me that I may try to flash a custom ROM and then try again, so I flashed to the most recent CleanROM. Since that time, I've had great problems getting my cell service to stay active, and all further attempts to use the Facepalm/S-OFF method have proven useless because I simply can not ever under any circumstance get past the dreaded "device not found" from the command prompt. I should further note that I read about a LOT of people needing to add a few layers of tape to their SIM in order for their service to stay on with this particular phone...so I've already successfully done this and it did not resolve my dropped service issue.
At this point, I don't know which direction to go. Could the ROM be why my service is dropping? I've not done any sort of "radio" update on this phone yet...can that be an issue? I see RUU's listed on the index thread...would flashing to one of those help? If so, is the procedure same as flashing a custom ROM? And how in the world can I get passed the "device not found" error so that maybe, someday, possibly, I can have my S-OFF?
Any help would be greatly appreciated...
OK, so I've done a couple MORE hours of reading, and I've learned this:
1. The signal drops (as well as the occasional reboots which I didn't mention earlier) are consistent with people whose kernel or radio need to be updated to something that appropriately matches the ROM they're running.
2. I'm not imagining things...rooting/updating THIS particular HTC phone is indeed trickier than the other 3 I've rooted in the past...in the sense that following the directions won't always yield you the same results as the next guy. I'm seeing this sentiment in forum posts (even from ROM developers/etc.) quite a bit today, so, if nothing else, I know I haven't lost my mind lol.
So anyways, it seems as though I need to figure out which "kernel" to flash. I've not flashed ANY kernels on this phone so far, and it came stock running Android 4.0. I ultimately want to be running the latest stable version of Android with Sense on this phone. It appeared the answer for me would be the latest CleanROM, which is 4.2.2. and Sense 5. It's been running on my phone for almost a week now and I like it, except for the signal dropping/rebooting.
I don't know if I've added ANY info that will help someone give me good advice, but....anyone?
...and even MORE reading led me to the xda thread for the latest CleanROM, which is littered with folks having the exact same problem as me.
So yeah, I was here thinking all these problems were brought on by me just not "getting it"...but it just so happens that the first ROM I flashed had these issues for folks with not-so-current radios.
I've got several threads pulled up now that will supposedly get me fixed up, but I can't flash a kernel without S-OFF, so I'm back trying to figure out how to get past this stupid "device not found" issue.
Flash a different ROM to get s-off, Android 4.0 or 4.1 will be best. Once you have s-off you can either upgrade to the 2.15 firmware or flash the Beastmode kernel, either of these methods will stop the signal loss issues you've experienced on Cleanrom. Also, please search before posting, the signal loss issue is plastered all over the Cleanrom thread, you can't read more than two or three pages without seeing it mentioned along with the fix.
Sent from my Evita
Hi, I was previously running Android 4.1.1 Venom XL ROM. I saw 4.2.2 Venom XL and decided to upgrade. The upgrade went smoothly, but I have two problems
GPS:
As soon as I reboot the phone everything works. After a few hours, suddenly the GPS will not work anymore. When you bring up programs that require GPS like Maps/Waze, it will not even look for satellites (no GPS icon shown). Once I reboot, things will be ok for a little while. I tried installing the GPS Status & Toolbox App and even when I open that App, it is the same behavior. It works after a reboot, but the GPS lookup does not happen after a few hours. It is big problem for me since I moved to a new state only 4 weeks back and have been highly dependent on the GPS to take me around. Anyone face this problem and have any suggestions? I tried the different options the GPS Status & Toolbox offered but none of them helped. Thanks for your help. Never had any issues with 4.1.1.
Weak signal:
I have seen suggestions of installing BeastMode Kernel or update the firmware to fix this problem and am yet to try this. Do I need to be S-OFF to install the kernel?
My HTC One X is rooted and I have supercid, but it is S-ON.
Thanks for any help in this regard.
sadlee said:
Do I need to be S-OFF to install the kernel?
Click to expand...
Click to collapse
No, you do not. The kernel solution is a good option, if you do not have S-off.
Although you should consider s-off, as its easy to do (especially if you already have adb set to go) and gives you more options for recovering (if you are SuperCID and S-on, a Jellybean RUU will brick you). As long as your understand that s-off means all security checks are off (and you therefore need to be careful of what you flash) s-off can be a very good thing to have.
Also, your GPS issue may be related to the signal issue, so kernel or 2.15 firmware fix might solve this as well as your weak signal issue.
Thanks. I did S-OFF, installed the new firmware, reflashed viper xl 4.2.2 rom and I am back in. So far so good. I hope GPS works ok. I was trying to download the latest 4.2.2 beastmode kernel form the following link:
https://www.dropbox.com/s/m53u563v2ql3818/beastmode_tester2.zip
posted on http://forum.xda-developers.com/showthread.php?p=45089267
Is this the official BeastMode kernel for 4.2.2? It says tester and that is why I ask. Also, I see no specific instructions of how to flash it. Is it just as easy as copy to sdcard and use recovery to flash? Can anyone please confirm?
EDIT: Found the updated link http://nosroms.com/?developer=Evita. But, if someone could still confirm the way to flash the kernel, that would be great.
Wipe cache/dalvik and flash kernel via recovery.
Sent from my One X using XDA Premium 4 mobile app
Thanks. All set now. Looks like my GPS is working great :victory:
I hope that my the kernel does its thing and no signal drops.
Thanks for the help.