Related
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
Heh, never thought I'd be posting here but I want some ideas before I unroot and bring my phone in :/
For the last I'd say month and a half or so my gps hasn't been working properly. If I'm running an aosp rom (AOSP, CM, my own compiled roms, etc) gps will not get a fix.
I've tried using both the GPS Status app and GPSTest app to reset the 'aiding data/agps data' to no avail.
I've ran the RUU, re-rooted and done a fresh wipe/flash of a rom that I know had working gps for me in the past (an aosp rom again), still nothing.
Just recently today I wiped my userdata, cache, and system partitions via fastboot. Then proceeded to do a clean flash of the Mau5 CM6 rom. - repeated this process for AOSP's, and CM 6.1. All of which had the same results, no gps fix.
As I said for some reason it only seems to be a problem on aosp rather than senseUI. If I flash the stock sprint rom or any of nfx's sense roms for that matter I get a gps fix within a minute. Same goes for the stock RUU.
So my question is this: what other ideas do you guys have for me?? I'm fresh out
Edit: yes i've updated my prl and profile plenty of times, it doesn't help.
kyouko said:
Heh, never thought I'd be posting here but I want some ideas before I unroot and bring my phone in :/
For the last I'd say month and a half or so my gps hasn't been working properly. If I'm running an aosp rom (AOSP, CM, my own compiled roms, etc) gps will not get a fix.
I've tried using both the GPS Status app and GPSTest app to reset the 'aiding data/agps data' to no avail.
I've ran the RUU, re-rooted and done a fresh wipe/flash of a rom that I know had working gps for me in the past (an aosp rom again), still nothing.
Just recently today I wiped my userdata, cache, and system partitions via fastboot. Then proceeded to do a clean flash of the Mau5 CM6 rom. - repeated this process for AOSP's, and CM 6.1. All of which had the same results, no gps fix.
As I said for some reason it only seems to be a problem on aosp rather than senseUI. If I flash the stock sprint rom or any of nfx's sense roms for that matter I get a gps fix within a minute. Same goes for the stock RUU.
So my question is this: what other ideas do you guys have for me?? I'm fresh out
Edit: yes i've updated my prl and profile plenty of times, it doesn't help.
Click to expand...
Click to collapse
alright, you may get pissed but here it is. Turn on navi on your phone, leave it alone for a while (obviously don't do this whilst in a nuclear fallout shelter)
I have had to WAIT (the first time) for gps every time I flash a rom (or a kernel) that's aosp base, usually pick up a signal somewhere between 5 and 10 minutes, then every time I use gps after that it's fine. There was even a guy's post way back in the early november area of deca's kernel thread that said he got a lock around the 30 minute mark on a CFS using gps status.
hope you can get a lock If you already did the gps status fix reset download and waited, then disregard, otherwise try waiting a while, it might work, it did for me. Good luck bro.
il Duce said:
alright, you may get pissed but here it is. Turn on navi on your phone, leave it alone for a while (obviously don't do this whilst in a nuclear fallout shelter)
I have had to WAIT (the first time) for gps every time I flash a rom (or a kernel) that's aosp base, usually pick up a signal somewhere between 5 and 10 minutes, then every time I use gps after that it's fine. There was even a guy's post way back in the early november area of deca's kernel thread that said he got a lock around the 30 minute mark on a CFS using gps status.
hope you can get a lock If you already did the gps status fix reset download and waited, then disregard, otherwise try waiting a while, it might work, it did for me. Good luck bro.
Click to expand...
Click to collapse
I've done the reset, download and waited upwards of 30+ minutes before (I usually have it connected with the wake-lock on so the screen doesn't time out) I've gotten a signal doing that once or twice, but as soon as i close the app using gps, be it either one of the two gps fix apps or google maps, and open it back up, I have no signal again.
Same thing happens if after I wait however long until I get a fix and then later I reset the phone, I don't get gps signal after the boot.
Thanks for the ideas though
Edit: I also want to add I've done the suggested steps from the earlier roms where you boot up a sense rom, get a gps fix, then flash an aosp rom. And I've also tried a few of Deca's kernels. Same deal
Just wanted to add I ran the RUU again and did a nandroid restore of a Darchdroid 2.8 rom that I know had working gps. Same problem.
Sooo.. After finals this week I'm just going to bring it in and see what my options are.
Have you updated to the newest radio and PRL?
dmcaylor said:
Have you updated to the newest radio and PRL?
Click to expand...
Click to collapse
Yes, I've tried 4 radios, and both 60671/60672 for the PRL.
Thanks for the help though
I've tried two things after much research:
1) Using GPS Status to clear cached GPS data.
2) Wiping, going back to CM6 (which picks up a lock in a mere 15 seconds), wiping, and trying the same in CM7. There was a thread on the Aria with these instructions, I figured I'd give it a go.
Anyone have any other ideas? I'm getting pretty pissed at CM7 right about now...
I found a fix! ... of sorts. Maybe the following will help someone else who has the same issue.
I tried a different 2.3 Rom just to see if it'd work. For some reason, the Pure Google Mod works perfectly, but you have to have the 1.15 GHz kernel by wildmonks (as detailed in the Pure Google thread) for it to work.
I thought this was weird so I tried going back to CM7 Stable and flashing that same kernel. GPS wouldn't lock on there... >_<
So I guess Pure Google Mod + the 1.15 GHz kernel by wildmonks = Working GPS.
GPS now takes about 20 seconds to lock, which is slower than Froyo for me, but still reasonable.
Maybe the fix is related to the version of CM that Pure Google is based on? I haven't tried my GPS for a few RC's, so I couldn't tell you if that was the reason. But whatever, I'm enjoying
I had this problem with all version of CM7. Flash back to CM6 and it works. What I tried was installing GPSFix. For some reason I can then acquire a GPS lock after having run this.
Or it was a fluke and the latest nightly build I installed fixed whatever the issue was...
This phone is driving me crazy. I haven't seen this issue reported by anyone else before, so I'll try to sum it up:
I have a Galaxy Mini, with CM 7.1 RC1 installed, which I can no longer update or replace its ROM, no matter what ROM I install(I've already tried CM7.2, Andro-ID and every other ROM that I could get my paws on, it's hopeless; CM9 also seems to work, but it's so buggy, it's unusable), the microphone won't work anymore, even after clearing everything and fixing the permissions, I have to revert to CM 7.1., which is the only release which has a halfway working microphone implementation(it's buggy, to say the least, people just barely hear what I'm saying). There is a patch for libaudio which suposedly fixes the mic, but after installing it, ceases working, so I always have to revert to my CM7.1 Nandroid backup. I would install the vanilla Gingerbread again, because everything was working fine on that, but there is one small issue...the data cable broke not too long ago, so I'm stuck with only a MicroSD card reader, which is not of much help, because I can't flash it with Odin and, as this will be sold next week(the buyer asked me to reflash it with the original firmware), I'm not willing to buy a new one for it either.
My biggest mistake was that I forgot backup the original firmware, which might have been the simplest solution for this problem, so I'd be very grateful if someone could kindly dump and upload his/hers stock ROM backup from cwm, so I can try to restore it and finally get the mic working again. Also, if you know any other solution that might fit in this scenario, I'm willing to try anything.
mihait39 said:
This phone is driving me crazy. I haven't seen this issue reported by anyone else before, so I'll try to sum it up:
I have a Galaxy Mini, with CM 7.1 RC1 installed, which I can no longer update or replace its ROM, no matter what ROM I install(I've already tried CM7.2, Andro-ID and every other ROM that I could get my paws on, it's hopeless; CM9 also seems to work, but it's so buggy, it's unusable), the microphone won't work anymore, even after clearing everything and fixing the permissions, I have to revert to CM 7.1., which is the only release which has a halfway working microphone implementation(it's buggy, to say the least, people just barely hear what I'm saying). There is a patch for libaudio which suposedly fixes the mic, but after installing it, ceases working, so I always have to revert to my CM7.1 Nandroid backup. I would install the vanilla Gingerbread again, because everything was working fine on that, but there is one small issue...the data cable broke not too long ago, so I'm stuck with only a MicroSD card reader, which is not of much help, because I can't flash it with Odin and, as this will be sold next week(the buyer asked me to reflash it with the original firmware), I'm not willing to buy a new one for it either.
My biggest mistake was that I forgot backup the original firmware, which might have been the simplest solution for this problem, so I'd be very grateful if someone could kindly dump and upload his/hers stock ROM backup from cwm, so I can try to restore it and finally get the mic working again. Also, if you know any other solution that might fit in this scenario, I'm willing to try anything.
Click to expand...
Click to collapse
for stock rom is very simple go here http://forum.xda-developers.com/showthread.php?t=1464896 and get this rom flash with CWM and Voila!!! ^^
Hmmm...I wonder why that one isn't in the rom list. Anyway, downloading and reporting back.
well-it sure looks like stock, yet mic is still dead
bump......
Hi guys,
I have now succesfully unlocked, rooted, downgraded from HBOOT 2.02.0002, S-OFF'ed, installed BlackRose 2.02.0002 and a custom ROM.
MIUIv4.0 seemed to have a lot of glitches with apps (Touch Input and Maps) crashing frequently, no mobile network despite entering APN etc (do I need a certain version based on my provider?), and no WiFi. I have then installed Nik's Codename Vivo app, which works well except the WiFi and I have to reapply Swiftkey on boot. Otherwise the experience is incredibly smooth and Google Now seems very promising.
I've learned a lot in the process, and it's been fun flashing both through CMD prompt and through recovery. I was so proud the first time my laptop told my phone to do something hacker-ish. Continuing off the success, I'd like to play more around with the phone so I want your input on what I can/should do next? There's probably a lot of things I don't know that I don't know.
I have been doing some stuff in Tasker, which was fun. I am eg. now reminded of anniversaries and my Spotify app opens whenever I plug in my headphones. What I know that I don't know here is that I'd like to make something cool with Tasker and Ivona, I just don't really know where to start?
Any other ideas? Anything regarding tasker, customization (how does launchers exactly work? i tried a few back in the days and they seemed to slow performance a lot?) , flashing radios (are they any different? if so, how?) and whatever else, really. I'd really like to learn the full limits of what can be done both on an Incredible S and android, before eventually moving to another phone and perhaps WP8 so I can truly appreciate the differences.
I'd also like to take the opportunity to ask if anyone has ideas as to how I get the WiFi to work? I did flash the JB WiFi fix and it didn't work.
Lastly, if anyone is sitting on an Incredible S, have updated the software to the newest version and would like to mess around with it, feel free to ask away though I'm no expert. Also, I bought 4ext for downgrading but used Revolutionary for upgrading. How would I go about making 4ext interface my recovery screen again?
This is quite addictive, and I am now frequently checking for updates from Nik doing Codename on a different kernel, anything on CM10 and other stuff. So I'd also like to say thanks for a great community. Phew, I guess this post is a bit all over the place.
There are lot of stuffs present on Main Android development forum of xda..that will help you..
and for anything else you wanna know Google is your friend...
As for replacing the Revolutionary/CWM recovery with 4EXT Touch, you can simply flash the new recovery image in FASTBOOT USB mode using the command:
fastboot flash recovery [recovery.img file]
Miui v4 is still very buggy at the moment. I run the 2.4.20 GB build which I find far more stable and quicker. No Google now, however.
Never had an issue with Wi-Fi on codename, but found that my data never turned back on after I turned office Wi-Fi.
Have you downloaded Titanium backup yet? A must if you plan on flashing a lot of ROMs. Otherwise SetCPU to overclock your processor, and AdAway to get rid of those adverts in apps.
tpbklake said:
As for replacing the Revolutionary/CWM recovery with 4EXT Touch, you can simply flash the new recovery image in FASTBOOT USB mode using the command:
fastboot flash recovery [recovery.img file]
Click to expand...
Click to collapse
Thanks I'll try that out, downloading the recovery file now
Edit: Worked, cheers!
CyanideJack said:
Miui v4 is still very buggy at the moment. I run the 2.4.20 GB build which I find far more stable and quicker. No Google now, however.
Never had an issue with Wi-Fi on codename, but found that my data never turned back on after I turned office Wi-Fi.
Have you downloaded Titanium backup yet? A must if you plan on flashing a lot of ROMs. Otherwise SetCPU to overclock your processor, and AdAway to get rid of those adverts in apps.
Click to expand...
Click to collapse
Sweet. Well, the WiFi just never really boots up. I press "on" and it just starts loading, eventually the indicator will be switched to on, though with no colour filling (usually ON is highlighted in cyan)
I have an app called AdFree - is it any different from AdAway? I've yet to try overclocking, so I'll make sure to check it out, thanks!
Also,
For ur current rom, y dont u use nik project x? It has literally no bugs and it is android 4.0.3 and sense 4.0...
As for radios, they control all the bluetooth, wifi and gps signals, so if u flash a custom radio, u can get either really good reception or really bad. That depends on the radio. Beware as flashing a custom radio has a high chance of bricking so flash only if confident.
Have Fun!
(Insert Disclaimer)
Sent from my HTC Incredible S
Piccilino said:
Also,
For ur current rom, y dont u use nik project x? It has literally no bugs and it is android 4.0.3 and sense 4.0...
As for radios, they control all the bluetooth, wifi and gps signals, so if u flash a custom radio, u can get either really good reception or really bad. That depends on the radio. Beware as flashing a custom radio has a high chance of bricking so flash only if confident.
Have Fun!
(Insert Disclaimer)
Sent from my HTC Incredible S
Click to expand...
Click to collapse
Thanks a lot for your reply!
I flashed Codename because it was a jellybean ROM and because to my understanding getting as close to pure android as possible would enhance the performance of my phone. Though I guess with a custom rom (Codename) it's not pure android anyway.
If the radio controls WiFi and GPS, can my WiFi problems be due to a suboptimal radio in the codename rom?
I won't be able to use Google Now with Project X, will I?
Splintre said:
Thanks a lot for your reply!
I flashed Codename because it was a jellybean ROM and because to my understanding getting as close to pure android as possible would enhance the performance of my phone. Though I guess with a custom rom (Codename) it's not pure android anyway.
If the radio controls WiFi and GPS, can my WiFi problems be due to a suboptimal radio in the codename rom?
I won't be able to use Google Now with Project X, will I?
Click to expand...
Click to collapse
Codename is pure android 4.1 JB with a few tweaks on top.
The majority of bugs in all the JB based ROMs are due to the fact that we don't have the right kernel for jellybean ROMs available for our devices yet. People far smarter than me are working on it, but it's slow going.
As far as I'm aware Google now didn't come with Project X.
AdAway is the same as AdFree, but is better in my opinion.