Develop Bugs

[Q] Weird Screen Issue After ROM Update

So I've started getting a very weird "ghost touch" on my evo. Rather than try to explain what it is, here's a video (no links for newbs apparently) ###youtube.com/watch?v=0zW934J0UQ8
So you'd think it's a hardware issue but I have this hypothesis that it's some kind of software issue because it happened right after I switched from Fresh 3.1 to Fresh 3.2. It also goes away if you standby and it's somewhat intermittent.
The only problem with the software hypothesis is after it happened, Fresh 3.3 came out so I loaded that up trying to get rid of the problem and then I loaded Ava, and now I'm on Virus and the problem hasn't gone away. I've also switched up kernals a few times with no result. Radio\PRI\Wifi maybe but I don't know how that would affect it. So it may be that's just me not wanting to have to return my phone, but any thoughts would be appreciated before I go back to stock and get a new one.
KB

[Q] DINC Random Reboots

Although I have been doing a lot of reading the last few months, I am new to posting, so please bear with. My DINC just started randomly rebooting about 2 weeks ago and I am trying to figure out why. It was running great before with (rooted) Skyraider 3.0 RC3 Vanilla, kings BFS#5, S-Off, 2.15 radio and HBoot .79. The problems began when I installed Juice Defender, didn't really like it, and then un-installed it. I did not disable anything JD did before un-installing. Now, with the same set-up as before, I get random reboots when I'm on Explorer for a few minutes, when GPS Navigation is on, and then randomly on GChat and the Market. It seems to happen more when the temp is higher, but it's rarely over 100 degrees F. Half of the reboots end up in QualComm debug mode. I have tried a full wipe and reinstalling the ROM, kernel and prior settings. The only thing I can think of is that Juice Defender changed some type of setting, application or system, and now it's having fits. I downloaded aLogCat and had it running during the last reboot and can PM the .txt file if you think that would help. Does anyone know what's going on or how I can fix it? Any help is great appreciated!
Also, the current applications that I have are:
ad-free
advanced task manager
beautiful widgets
setCPU
amazon reader
scorecenter
Mint.com
switchpro
bump
battery indicator
astro
root explorer
rom manager
barcode scanner
facebook
goggles
dspmanager
handcent
linpack
metamorph
mixing
papertoss
pandora
shazam
spare parts
tapatalk pro
titanium backup
weather channel
widget locker

BUMP....anyone?

mjmdmd said:
BUMP....anyone?
Click to expand...
Click to collapse
Are you overclocking? Some phones can't handle much and it's known to cause similar problems. Other than that I'm not sure if anything JD changes would remain once it's un-installed; but if so you might install it again, change everything back to stock, then un-install it. Just a guess, hope you get it figured out

I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.

SynbiosVyse said:
I'm pretty sure the DINC has rebooting problems.
What version do you have, SLCD or LED?
I've had the LED version since it's released and I just started getting random reboots last month or so. Sometimes it goes into fits and just reboots nonstop for a couple hours. I've reverted it back to completely stock (unrooted, S-ON, stock recovery, stock 2.2 ROM) and I still have the same problem. Using stock battery as well. I've always cleared cache, factory reset, clear data, etc. I've done everything I can think of, but I think this phone just has problems that some people encounter even when completely stock (and even people who have never modified their phone at all if you do some searches on google).
It may have to do with the heat, I'm going to keep doing some testing. It seems like it goes into reboot fits when it gets hot or when I'm doing a lot of processing like using GPS and maps. It rarely reboots when it's idle.
Click to expand...
Click to collapse
Same here. Exchanged it with Verizon, almost no questions asked. Got AMOLED refurb, so far so good. Replacement was with OTA installed though, so waiting for new root.

You should revert your phone to fully stock, turn S-ON, unroot, stock ROM, etc. Make it look as legit as possible. If your problems go away then obviously something got screwed up in the flashing process. If your problems remain, then it's something wrong with the actual phone, and since you just made it completely stock you're in the perfect shoes to go exchange it.
In summary, the best measure to take if you're having reboot problems is to exchange it at a Verizon store; that's what most people are doing.
I'm going to exchange mine tomorrow. It should be covered under the 1 year warranty so you should not need insurance to do it.

Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...

Sounds to me that you have the faulty overheating 3G radio..it is a somewhat documented problem and I believe it's the same problem I have. The only solution is to swap it at a verizon store. I'm afraid other ROMs or anything else you do will not solve the problem.

mjmdmd said:
Just an update: I am still having random reboots after uninstalling Advanced Task Manager and Widget Locker (read in posts these can cause problems). Now even when I use Amazon reader, the phone reboots rather quickly. One thing to note is that when I turn off 3G, it hasn't rebooted. This was one of my thoughts to begin with since approximately all of the reboots occurred when I was using 3G (browser, market, GChat and Nav). Does this narrow down any problems?
Next, I am going to install the new Skyraider 3.0 (ihtfp69 said it should be out first week of Dec.) and install apps one-by-one to see if the rebooting continues. Then I guess I will have to go s-off, unroot, etc. Crossing my fingers...
Click to expand...
Click to collapse
Odds are your radio is failing, which is a relatively common problem. Your symptoms are pretty much a textbook example and something that I experienced firsthand on my previous Incredible. The only fix is a warranty exchange.

That's disappointing. Thanks for the info everyone. I guess it's time to start the process of unrooting...

I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.

Miltos1 said:
I thought I would post my situation/solution here, although it may not have any bearing on the issues that previous posters have mentioned. I got myself a Seidio 3500mAh Extended Life Battery several months ago. The first month was good. The next 1-2 months seemed to bring decreased battery performance - I was just about making it through a day with moderately-heavy use, but this battery should be able to handle that with no problem.
Over the last month I started having random reboots and it was getting more frequent. I don't know why but I just had this feeling that the battery was coming a bit loose and losing contact occasionally, although I couldn't force a reboot by shaking it.
Just a few days ago I decided to put a few layers of paperboard (i.e., box of tissues) between the battery and the case, just to see what happened. I haven't had any random reboots since I did that and the battery life seems markedly improved.
Again, this may not be relevant for some but I thought I would post my experience in case it helps anyone.
Click to expand...
Click to collapse
Interesting. I'm using the big batt too, but my only reboots happen with GPS. As I'm driving (unfortunately) with my Nav on, all of a sudden, I look to see what my next turn is, and I'm on the "HTC Incredible" splash screen! Most annoying thing ever.
I'm still waiting for a fix. I really don't want to unroot, lose everything, and have to exchange for a warranty phone.
By the way, with a fix like this, I feel like my blackberry days again!

[Q] Random Reboots when not on WiFi

My Evo has been rebooting recently when I try to use an app that is data intensive while not on WiFi (Twitter, Facebook, Navigation, etc...). At that point, I get stuck in a bootloop. The phone will reboot and load fine until moments after the SD card is prepared. This will continue on until I reboot my phone will being within a WiFi network I've previously joined. Its a very odd behavior and I can't figure out why its happening.
I've tried wiping everything, multiple kernels and even swapped roms to see if it would help. Nothing seems to work
Phone setup:
CM7.1, 0808 radios, V8 script, Tiamat 4.0.8 SBC, no under/overvolting
Any ideas?

Does your phone get very hot? I'm already thinking a big possibility is hardware. Try a new battery
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702

I have the same problem. Bootloops out of nowhere.

Crossrocker said:
Does your phone get very hot? I'm already thinking a big possibility is hardware. Try a new battery
Click to expand...
Click to collapse
Nope, the phone isn't getting hot at all. I put in my Seido battery today and will see how it goes. This is pretty frustrating.

Just wanted to follow-up on this thread in the event someone else runs into this issue. In short, my Evo is being replaced since this was due to a hardware issue. I unrooted and went to the local Sprint store and they are replacing my phone free of charge.

[Q] Galaxy Nexus keeps crashing randomly

Hey guys, i need some advise here!
For weeks, i anxiously waited for the mailman to bring my my GNex and for a few days im very happy with it. Unfortunatly, the major plus of android, it never freezes, isnt true for my brand spanking new Gnex!
Seeming randomly, the phone freezes, refusing all input from the screen and the On/Off button. This happens about every 20 hrs.
Ususally i advise people with this problem to exchange their phone with a different one, but im afraid i wont get a stock 'yakju' build back in return, so want to try to fix (or at least determine) the problem first.
Can you guys give me some tips on how to get to the bottom of this?
Thanks in advance!
Info:
Model: Galaxy Nexus (GSM)
Android version: 4.0.1
Smalbandversion: I9250XXKK1
Kernel: [email protected] #1
Build: ITL41F (yakju)
And again, it's all stock

...
i had a lot of problems with the 4.0.1 fw, have you tried updating the phone to 4.0.2 it solves a lot of bugs!

I tried to update the phone through the system update menu in the settings, but it listed my phone as 'up to date'. I find this is odd, since i have a Nexus ánd the Google build
Is there a way of updating the phone without a lot of hassle?

I looked into it, in the Netherlands the 4.0.2 update should roll out in a few days. If it isn't, I'm going to flash it myself! Were your problems with 4.0.1 similar to mine e.g. crashes and freezes?
Sent from my Galaxy Nexus using XDA App

In my experience most of the time when that happened was caused by 3rd party apps that weren't ics optimized.
Sent from my Galaxy Nexus using XDA App

Well freezes and crashes maybe, but the whole phone unresponsive? Isn't there a try/catch somewhere which prevents this kind of 'dirty code' to crash the whole OS, anyway there should be.
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Sent from my Galaxy Nexus using XDA App

Same problem
Panatella said:
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Click to expand...
Click to collapse
That exact thing happened to me yesterday as well (running 4.0.1). I pulled down the notification bar, clicked on the email notification, and when the notifybar started collapsing again, the animation stopped, sound was caught in a loop, and two seconds later my phone rebootet with a clicking sound (I hope that it was just the speaker reacting strangely to the sudden signal loss...!)
The same day, the Nexus kind of crashed while I was streaming internet radio to my bluetooth speaker. The music kept on playing fine, but I wasn't able to turn on the screen. Even holding the vol+/- and power buttons only shut the phone down, but I couldn't restart before I removed the battery.
I really hope this is gonna be fixed with the 4.0.2 / 4.0.3 firmwares. This thing is crashing a little too often right now, for my taste

I'm getting the same problems as noted above. I've just picked up the nexus to move away from Apple's iPhones, but I'm left wondering I've made a serious mistake in doing so. An added problem is that the crash has also occurred when I've been recharging the battery while asleep- so the alarm I set did wake me.
Honestly, it's an unreliable product. I'm a customer, not a Samsung lab rat.

Got the same issue. 2 crashes in 4 days. Not a huge problem for me yet, but 4.0.3 better fix it.

Well most of my problems went away when i updated my phone. You should definitely try to update. Personalty I went straight for 4.0.3. The best ROM i've tested is definitely Android Open Kang Project :http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-13/
Everything just went so smooth and bugfree as far as i can tell. And i love the quick setting he put in notification bar.
You can see how to unlock your phone here using the gn toolkit :
http://forum.xda-developers.com/showthread.php?t=1392310

I had those kinds of crashes, too. My phone would crash maybe once every 3-4 hours on 4.0.1... doing anything. Whether it be idle, with no extra services (factory reset), or while composing messages. Anything would do it.
Anyway, I rooted the phone and I've been on Bigxie's ROM since V1 (AOSP 4.0.3) and the issue stopped, for the most part, except for an idle reboot every 18-28hrs. Suspecting it was kernel related, I swapped out the Apex kernel and threw on Franco's... since then, my phone can run for almost two days (of moderate usage) without a charge.

Any of you guys enabled 'force 2d hardware acceleration'? I don't know how relevant it is, but all my problems went away when I stopped to use this function.
Sent from my Galaxy Nexus using XDA App

Uv'ing too low can crashes also.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???

dhruvraj said:
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
Click to expand...
Click to collapse
U sure it's not a software u installed recently? For me changing back to the stock music player fixed the random crashing.
In general, I can say some apps are not stable at all.

I experience random crashes too, although they coincide with the sudden loss of signal, as described in these threads:
http://forum.xda-developers.com/showthread.php?t=1390816
http://forum.xda-developers.com/showthread.php?t=1387943
http://forum.xda-developers.com/showthread.php?p=20816554
I have started to make some logs to try to identify the cause of this problem. I use Log Collector for making a log and No Signal Alert to obtain a time stamp when the signal drops. What I see in the logs is that just before the signal drops I notice an entry in the log something like "process:com.lookout has died". Could this have something to do with the Lookout app I have installed or is it just coincidence that the app and a certain Android process have the same name?
By the way, does anybody know if there are websites or people who can analyze the logs I have created? Most of the content is mumbo jumbo to me and a knowledgeable person might be able to shed some more light on what happens inside the phone and what might trigger this problem.
I just upgraded to 4.0.2 on Thursday, but the problem persists.
Android version 4.0.2
Baseband Version: I9250XXKK6
Kernel Version: 3.0.8-gaaa2611
[email protected]#1
Build Number: ICL53F
ICS stock; non-rooted

Well i guess you tried already to remove the lookout app right?

My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.

b4cksl4sh said:
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
Click to expand...
Click to collapse
Are you sure it's the OS not some buggy/incompatible apps? I've had the phone since launch and it never froze even once. Stock 4.02 too.
And you should try out different OS. Then you will know what suits you.

Lost My IMEI & Serial Number - How I Fixed It

I ran a couple of searches on Google( and in this forum) to try and find the original thread about this issue, however I didn't find it so I'm posting here in case anyone else can be saved by this fix.
First, some background:
I have been running CM10 Nightlies for almost a month now, also using the leaked Jelly Bean radio version T999UVLI2 with absolutely no problems. Everything was working great, data, ROM, etc. (Prior to that I was on Stock ICS, rooted. Had not run any custom ROMs whatsoever).
I noticed after flashing the latest CM10 Nightly (Oct. 14) that my phone had started acting a little weird - nothing drastic mind you, just a few glitches here and there. The weird thing was, all of the previous nightlies I had flashed pretty much worked flawlessly for me, minus a volume issue when in-call which was a known bug. I had done a clean flash as I always do, so I attributed the glitches to a possible bug or two in the latest Nightly and figured it would probably be resolved in the next release. No big deal.
Yesterday afternoon, after reading a thread that is tracking all available T-Mobile radios by region (to see what works best in your area) I saw someone who posted that the T999UVLI3 radio gave them the best speeds, and they happened to live in the same exact city as I do here in Southern California. So I decided to flash the new radio using Team Sonic's Modem flasher, which I used in the past to flash the LI2 radio that I was currently on. I flashed the T999UVLI3 radio and found that it did indeed provide better data speeds than the LI2 radio, so I was pretty happy about that. Used my phone all day/all night with no problems, everything was great.
I always leave my phone plugged in at night so that I have a fresh charge in the morning - this morning I turned off my phone while it was still plugged in as I leave it off during the drive to work to save a little battery before I start my day. Typically I unplug it first and then turn it off, but not always. So nothing really out of the ordinary there.
I get to work and turn on my phone, and all of the sudden I notice that I have no bars - at all. It doesn't say "T-Mobile" at the bottom of my lock screen. I figured it was just taking it's time booting up, which would be very weird as it never does that, but I waited. And waited. Nothing. Now I'm starting to get a little worried.
Went into settings and checked "About Phone" and it said my Baseband version was "unknown". Oh crap. IMEI, unknown. Serial number, unknown. GREAAAAT
For the life of my I couldn't imagine how this could happen when I didn't even do anything from last night to this morning. I started going over everything I had done recently to my phone.. the power off while plugged in, the nightly update to the Oct 14 build, then it hit me.. the new radio version. Maybe that was it
In a desperate attempt I booted into recovery and ran Team Sonic's Modem Flasher and flashed back to T999UVLI2. Rebooted the phone and... BAM! Back to normal. W...T...F..?
If anyone loses their IMEI, before going through the entire injection fix process, try reflashing a radio. Worked for me!
Any theories on why this happened? Many people have been using the T999UVLI3 radio, I believe without any issues.. but I could be wrong. Anyone flashed that radio and lost their IMEI?