I'm coming to the Evo 4G LTE (stock, not yet rooted) from the OG Evo (rooted, various ROMs, yada yada). I've held off on rooting, just in case I discovered a hardware issue (light leakage, etc.) and needed to swap out the device. So far I've discovered a definite problem, but I don't know whether it's a hardware or software issue, and I'm hoping someone in this forum can help me down the path of figuring out the cause(s).
Specifically, I'm seeing the following things happen, usually all at the same time, but intermittently:
1. Phone heats up, and battery takes a huge hit
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
3. Wi-Fi drops, as does my mobile data connection, so that I appear to lose all connectivity.
4. My app associations get reset. I usually have my URLs set to open with "Dolphin Browser HD", and mail set to open with "Gmail (Compose)", but after this happens they're back to the stock browser and mail app.
5. Can't enter any text. When I enter a text field/control, the keyboard appears (I use Swype, but switching input methods makes no difference), and I can type/Swype away, but no text ever shows up in the field.
This is happening about once a twice a day, on average, and is obviously driving me nuts. I haven't detected a pattern to when/why it happens. And I've been searching the forums, but I haven't seen anyone else reporting this same set of issues. I'm not sure whether it's my device (hardware/lemon), or maybe just a user app behaving very, very badly - I'm not enough of an Android dev to know where to look for clues...?
Any help very much appreciated. I haven't tried a factory reset, but I'm open to that. Also to rooting the phone, and/or contacting Sprint. I just didn't want to blindly do any of those things before asking the Android experts out there for some guidance.
Thanks!!
If it was me, I'd root and flash a new ROM or at least a rooted stock ROM. If that didn't work I'd unroot and exchange it.
I'd say try a factory reset first, but why not root and have it done as a by-product anyway?
Sent from my EVO using xda premium
I agree
If you dont want to root yet just do a factory reset. What is it going to hurt? If you do a factory reset try to just set the phone up with all stock options to see if your problem is fixed.
roachiepoopoo said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
jpbme said:
This happens to me from time to time, if I wait a couple seconds the notifications will usually appear though. But I would do a factory reset as others suggested, just looks like a software glitch. Have you done the software update that was released a few days ago?
Click to expand...
Click to collapse
The same is with me BEFORE rooting, and after root and ota from xda
Look I want to thank you for posting this. I am NOT CRAZY. This has happenend to me from day 1, I returned the first EVO LTE (for other reasons) and it is still happening on my second EVO LTE
I finally got to the point that I was going to root my EVO LTE to fix this issue. I was going to root and flash and reset EVERYTHING. well surprise surprise nothing changed.
I have all the same problems you described but I lose my 3G about 15 times a day (especially when on calls) I have full bars but the 3G icon is gone and it states that I am disconnected. I can't figure this out. Everyone I appreciate your quick responses to this mans question but none of them work.
I have update profile and prl more times then I can remember. Flashed, wiped , reset everything. Help Me!!!!!!!!!
{
"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"
}
Anyone have any new info on this topic? My 3G disconnecting is really annoying!!
Rooted, wiped, and switched to MeanROM - phone now works GREAT!
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
roachiepoopoo said:
So, I held off for a while because I was one of the few people who had Google Wallet working from day one on a stock phone, and by the time I learned that I needed to reset it (from *within* the app!) to ensure I wouldn't break my NFC secure element, I was no longer able to launch the app - not even with the hacks suggested on this site.
Finally, I just figured I'd roll the dice. If the NFC secure element was bricked, I'd revert to stock, then tell Sprint it was the result of a system wipe and make them give me a new phone.
Fortunately, my NFC secure element is working fine. I've got root, S-OFF, TWRP, and MeanROM, and everything (including the latest Google Wallet - which finally supports my VISA card!) is working better than ever.
So, end result is that I may never know exactly what was wrong with my phone. Probably just needed a wipe. But once I had it rooted and wiped, I could hear MeanROM's siren song. For anyone else considering it: TAKE THE PLUNGE. I have no regrets.
Thanks to those who took the time to respond!!
Click to expand...
Click to collapse
NO!
So I flashed the Chameleon Rom, was running it for a while and still had issues. This weekend (during a wedding) I flashed MeanRom. And it is still happening. Does anyone know a real fix for this? :crying:
SilverZero said:
2. When I pull down the notification bar, the screen is blank. I still see the bar at the top of screen, and can pull the shade up and down, but there's *nothing* where any of the notifications would normally be.
Click to expand...
Click to collapse
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
stompkins007 said:
This bug is driving me crazy, and I hadn't seen anyone else having this issue until I found this thread... so I thought I might have bad hardware, though the symptom points to anything but a hardware issue.
I've had this problem with stock... I suspect it may be due to the fact that I use Apex and maybe this functionality was somehow linked to Rosie, and HTC's lame background killer was stupidly killing the task that manages this notification panel. I've now tried numerous versions of MeanROM (now on 3.0), then went CleanROM DE 1.1 for awhile, and now on MeanROM 3.0 (full wipe between every ROM install)... Problem is still occurring. The only different behavior in custom ROMS is that the Notifications/Quick Settings tabs remain, but they are both completely blank. The only way to get them back is to reboot the phone, or collapse the notification and try again later... far less than ideal for a high end device, and a relatively stupid/highly annoying bug.
Click to expand...
Click to collapse
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
slowfncar said:
I have never had any overheating,battery,black pull down issues,nor 3g/wifi disconnects. I guess I am lucky. Honestly I would return it to stock and bring it into sprint if your paying for insurance. It does sound like a software issue,but if a firmware update didn't fix the issue I would definitely swap it for a new one imo
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The issue I was having was only specific to the blank notifications... everything else has been pretty solid... BUT, there appears to be a light at the end of the tunnel. Last night I saw ClearnROM DE 1.4 was released, and had to give it a try. This time around I was very careful to do a full factory reset, Wipe of everything except storage cards via TWRP, Ran Superwipe script, and installed the latest CleanROM DE 1.4. The one thing I did differently after install was be very careful of what items I restored via Titanium Backup (making double certain it was only restoring app store apps, and no potential artifacts from previous ROMs.
Since doing this the phone has been solid. Haven't experienced the blank notifications, and the phone seems considerably more responsive than it was (which is nice, because it even seemed fast before doing this). Anyway, if anyone else is experiencing this, I recommend they do the same.
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
I don't buy Sprint's insurance and have had issues getting them to do warranty replacements, most recently with my EVO 3D's phantom screen touch problem (also 1st gen hardware). Sprint told me to ship it back to HTC and be without a phone for however long the warranty repair took. Really?
KatanaMan said:
Wow, OK, so I'm not crazy. The exact same thing has been happening to me and it makes me nuts. I bought my EVO 4G LTE on the day it was released in stores, so I'm pretty sure I have 1st gen hardware in it. I'm running stock ROM 1.22.651.3 710RD, HTC dev unlocked and rooted using the supersu/busybox method found on this site. Other than that, I've not messed with it. I'd rather keep running stock (because I'm THAT guy) and not go through the pain of a factory reset. So if anyone has any kind suggestions that work, I'll be your best friend.
When the phone has it's 2-3x daily tantrum, it really overheats, gets up to around 120F. Battery indicator shows most of the power going to "Screen" even though it's been off. If no one has any further suggestions, I will try a factory reset even though Cherokee4Life says this does not help.
Click to expand...
Click to collapse
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
KatanaMan said:
Just a quick update on my progress fighting this bug, I've gone a day so far without issues after doing what I think fixed it. I'm not sure which one of these steps helped (if it is fixed, which I hope it is), but it may have been as simple as clearing the dalvik cache, which was part of the process.
Please note, I am using an HTC unlocked bootloader, which is a minimum requirement for this procedure. First I rebooted into the bootloader ("adb reboot bootloader" is my favorite method of doing this). Then I booted from (did not flash because I wanted to keep the stock recovery) TWRP 2.2 to make a nandroid backup of the phone to the external SD card. The syntax was "fastboot boot openrecovery-twrp-2.2.1-jewel.img" I checked everything, all the boxes and made my backup. Then right from within TWRP (can I tell you how much I love this program?), I did a factory reset with cache wipe. I rebooted the phone into factory defaults and again used the bootloader to run TWRP recovery. I restored my nandroid backup, rebooted and was right back to where I was without having the pain of reconfiguring everything. So far, so good, no blank notification, no overheating/battery drain, and no waiting 10 seconds before it will make a phone call.
Interestingly enough when I was messing around in the factory blank version of my phone, I noticed that my SuperSU had maintained itself and I had root access in the stock factory image. I'm far from an expert in these matters, so I don't know if this is typical for a rooted device. I figured factory meant factory. Regardless, the phone has been working like a champ now. If someone else with this bug wants to test a little further and see if just a cache wipe works, it may be an even simpler fix.
Click to expand...
Click to collapse
RE: SuperSU, it lives on the system partition with the ROM so it's protected from a factory reset since that only clears the data and cache partitions (where your user apps are stored).
Sent from my EVO LTE
Just a thought
You cold try ##786# and enter your MSL code for data connection issues. See here to use CDMA Workshop for those that are not rooted (or use MSL Reader from the market for rooted users). Its worth a try at least, before unrooted users decide to root. Keep in mind this will reset your phone to factory so if your going to reset, might as well do this to reset PLI, PRL and other params...
I've been having the overheating/battery drain issue since about a week after first getting the phone. I've tried Meanrom, Viper Rom, and Clean Rom and still come across the same issue with each one. I do complete wipes/factory resets when flashing the new roms and I'm on the latest firmware. When the phone overheats it's pretty much unresponsive. Today, I watched my battery drain from 15% down to 8% in about 10 minutes. I turned the screen off at 8% and went to turn it back on a few minutes later and found that the battery had completely drained by that time. I have no idea why this is happening.
Same here
I've been having this issue as well. It happened while I was stock, it happened after I rooted, unlocked, went S-Off. And it's still happening under MeanROM. Very frustrating!
Related
I'm having a problem with my touchscreen that started happening yesterday after I flashed a new ROM. I flashed Android Revolution HD 1.1.1, and on the lockscreen after the first boot is when it first started acting up. This youtube video shows exactly what my phone is doing: http://www.youtube.com/watch?v=iIrmLOTiUZk
I've nand back to other roms that I've used in the past, and still the same issue. Superwiped and flashed different roms, and it would solve the problem for several hours, but the issue comes back. When the problem happens, a restart will solve the issue for maybe 15 minutes. It seems as if it's a hardware issue, but I don't get why rebooting/wiping and reflashing would solve the issue for a period of time. If anyone has any advice or the same issue with a fix, it would be much appreciated. Thanks in advance.
*Idk if it matters, but I'm hboot 1.4, zagg invisishield screen protector on.
Also, the touchscreen issue only happens at the bottom center of the screen - where the lock ring is located.
Update: I nand backed to stock rom, no issues for about 24 hours, started happening again. Any thoughts anyone??
Might be a hardware issue. If it keeps occurring I'd suggest taking it in to be looked at. Or you could try reflashing your recovery and doing a full data wipe and flash a stock rooted rom and see if that helps. Hope it does. Good luck.
Locked & Loaded
""shooter on Deck""
Thanks, I'll try reflashing my recovery tonight. It seems to be hardware related, but the temporary fix (data wipe and flash Rom) is what confuses me. I just hope I don't have to send it in and get a refurb with hboot 1.5.
Also, when I do super wipe, should it automatically boot into recovery? It just hangs on the white HTC screen, and I have to.pull the battery to get into recovery. And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Well if your doing a super wipe and it still keeps some of your old settings of a prior rom then I'd suggest trying a different wipe method or redownloading the the super wipe zip, you might have gotton a bad download. As far as if it's supposed to boot right into recovery that I don't know because I don't use any wipe method but the recovery. It hs always worked for me. Try reflashing your recovery and wiping with just the recovery options. Wipe data "complete factory" ,cache and davlik-cache. Then try flashing a stock rooted rom. Or if that doesn't work try the official ruu.
Locked & Loaded
""shooter on Deck""
b1gsby_02 said:
And after I install a Rom, why does it keep my some of my same settings, like the wallpaper and ring volume, and not go to the defaults? I am he if the super wipe is actually doing its thing or not.
Click to expand...
Click to collapse
Well it keeps your wallpaper because Google syncs it with your Google account. That's normal. But as for everything else, it sounds like a hardware issue.
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Sent from my PG86100 using Tapatalk
I flashed twrp 1.1.1 over 1.0.3 and did a data wipe, cache and dalvik. Flashed a rom and so far so good. I'll see if I can go more than 24 hrs without an issue. If it's a hardware issue, I don't understand why flashing a new rom temporarily fixes the issue, and since the issue started right after I flashed a new rom. I'll continue to update on here and hopefully the reflashing of recovery helps - thanks laie.
Didn't know wallpaper was synced with google account - thanks gumby
Gumby63 said:
I'm having the same problem on my HTC Flyer and flashing a new ROM or restoring an old backup won't fix it anymore.
Click to expand...
Click to collapse
Did you do anything else to try fix the problem?
b1gsby_02 said:
Did you do anything else to try fix the problem?
Click to expand...
Click to collapse
I'm not sure what else to do. I suppose I'm stuck with contacting HTC about a repair. I've done a little bit of research and some people having similar problems have said that it could be a problem with the digitizer. But most explanations were very vague so I'm still not sure what I'm going to do.
Sent from my PG86100 using Tapatalk
Well you should be good to go. Post back in 24hrs with what's going on. Glad your running ok for now.
Locked & Loaded
""shooter on Deck""
Phone was fine all last night and this morning. Early afternoon it started acting up a little bit. Nothing like it used to, but I notice when I set it down or shake the phone a little, it will trigger the issue. So it's more than likely hardware related. Does anyone know Sprint's policy on fixing a phone that is rooted? I am jw if I should revert back to s-on before I go to a Sprint store to have them look at it. I don't know if they check that or not. Usually the first thing they always do is make sure everything is up to date too. Any insight is appreciated, thanks.
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Rob the plumber said:
I'm in the same boat. Touch screen freaking out, rebooting fixes it for a short time, then it does it again. I'm going to take it in to sprint today and first ask them if they care if it is rooted.
Click to expand...
Click to collapse
Please update us after you talk to Sprint. I am curious to what they say about you being rooted and what the problem may be. My phone has been running fine for awhile now. After I reflashed recovery, data wipe, flashed rom, it acted up for a short while about 12 hours later. It's been almost 24 hours since it last acted up and has been fine so far.
Rob, just wondering if you talked to Sprint yet?
Also, does anyone know if I should go back to 100% stock and S-on before bringing my phone into Sprint? They always seem to update everything, and if there is an update, they usually tell you that's the reason why your phone isn't working the way it should.
UPDATE:
I went back to 100% stock and S-ON following this guide: http://forum.xda-developers.com/showthread.php?t=1194053 Then I went into my Sprint store, told them about the issue, and the first thing they did was asked if I had reset the phone and they checked to see if there's any updates available. The phone started to act up again while they were looking it, luckily, because they have to replicate the issue before they can fix the problem. They said it was probably the screen and they were going to replace it. They had me come back an hour and half later, told me they tried replacing the screen and that wasn't it. They didn't know what was wrong, but concluded it was a bad phone. They replaced my phone with one that someone returned within their 30 days. It's not a refurb, but not a brand new one either. I had to pay $35 for the service charge for fixing my phone. I hope this helps anyone who's having the same issue.
Of course my replacement phone has hboot 1.5.
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Rob the plumber said:
I have not been to sprint yet. I swapped batteries and it had not acted up since. Strange. I had already pulled the stock battery a bunch of times and it would be fine for a half hour or so, then flip out.
Maybe my battery was bad.
Click to expand...
Click to collapse
I have tried a few different batteries, and it didn't seem to matter. Maybe your situation is different. Hopefully that fixes your issue!
My issues have returned. Off to the sprint store!
Rob the plumber said:
My issues have returned. Off to the sprint store!
Click to expand...
Click to collapse
Good luck! Did you revert back to stock and s-on? Or are you going to tell them you're rooted?
I think I'm going to just put a stock ROM on it and ask them first before I hand over the phone.
Is anyone else experiencing these. I've only had the phone a few days but started to notice it once I put infected rom eternity on it not sure if it is a rom issue or a hardware issue
Sent from my PG86100 using XDA App
I'm having random reboots and I haven't even rooted/modded in any way. I got a system update earlier today, but it was doing it before that. It might be one of my apps, but it only happens when the screen is off and I'm trying to turn it back on to use the phone. I've tried factory resets and battery pulls so I figure its an app, or having the social lock screen.
Sent from my PG86100 using Tapatalk
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
mteezey said:
It must be a hardware issue then. I've been looking into it more and it seems to be happening to slit if people on slit of roms. Most of what I found said it was kernel related but if your having it happen and your not rooted I'm not so sure its kernel related then.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
It's definitely hardware. It's the proximity sensor, I believe. I picked up a phone call, and when I put the phone up to my face (I didn't touch my face to the phone, just my ear), the screen didn't shut off, and then rebooted. After it started back up, I called the person back, and when I brought the phone up to my face, the screen shut off as it should, and stayed in the call until I hit end, and it's still on. I received a second call and it had the same behavior. Reboot upon bringing it up to my face the first time, fine the second time. When I try to bring the phone out of standby I thought it was the live unlock screen I had (weather), but it seems to bee the light sensor or proximity sensor... boo..
[EDIT] Just did a factory reset. Market is installing my apps. We'll see how this time around goes.
So far so good. all my apps are re-installed. I have yet to check my games for my data, but I took a phone call and the screen turned off quickly when I brought it up to my face.
That's the same way it happened to me during a phone call but I was on hold for twwenty minutes with it on speaker and once they picked up I put it to my face and ....reboot. like you said boo
Well I got rid of eternity and with new rom(Olympus Trinity XE) and kernel mild anthrax I have not had a reboot yet. Its only been 12 hours but it was happening every few hours before.
Sent from my PG86100 using XDA App
heat
I usually have my E3D in it's Otterbox clipped on my belt, and no problems arise. Last week I went out to a bar and it was very warm in the bar, and the phone was in my pocket. It rebooted once out of the blue. I'll keep it on the belt clip.
Rooted, Stock rom.
I'm planning on getting am otterbox very soon.
As for rebooting, it's still doing it, once when a Words with Friends game wouldn't load and another time while trying to load Paradise Island. I'm now thinking it's the video driver.
I rooted my Intercept and changed the driver. I would rather not root this device if I can't unroot it...
Sent from my PG86100 using Tapatalk
Mines not rooted either and mine just rebooted like literally 3 times in a matter of 30 minutes
Sent from my PG86100 using XDA App
There is a rom to unroot. Its a stock rom once you flash turns your securities back on(s-on). Which is good in case you ever have to take it back to sprint.
Sent from my PG86100 using XDA App
I've only had one reboot with my new kernel. It seems now like its only when its on the charger I set a charging profile now to Max CPU speed of 648mhz with interactive governer gonna see if that helps. If not I'm gonna try a temperature profile.
Sent from my PG86100 using XDA App
From what I can do on an unmodified device, I found this in the "Tell HTC" log.
local_clk_disable_reg: clock 72 status stuck at 'on'
This happens a few times in the log. I've been taking screenshots of the log to post, but I haven't had the time to go through the whole log. The next time I get a chance, the phone has already rebooted 3 times. It's definitely not my app because it's no longer on my system.
Also, I don't know if this goes with it, but I sometimes have to do a PRL update to get out of roaming. I'm in my local, high-signal area... I'm eventually just going to call and get a replacement.
[EDIT]
{
"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"
}
here we go. Here's the error message, then it dumps the memory locations. In a minute I'm going to post a link to an album I have with the log, error to end.
Another oops 17 prempt smp.
Sent from my PG86100 using Tapatalk
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
mteezey said:
you got those errors running on the stock kernel ? Or a custom one?
Shot from my Shoot3Rvo
Click to expand...
Click to collapse
This is all untouched stock from Sprint.
But wait! It gets better! I wasn't using the phone last night, and it kept rebooting every 20 minutes +/-, then it gets stuck in a boot loop (which it's still stuck in). As mentioned before, I have to update the PRL every time I reboot the phone, so could it automatically be routing itself to a bad radio? Not that it matters, I have to factory reset anyway...
I went into recovery to do a factory reset (boo... going to try to adb pull my data, first) and I noticed that during the image check, two of the images are the "wrong" image (PG86DIAG and PG86IMG... something like that). Is this bad? I went from a Samsung Intercept to the Evo 3D so there's some major differences between stock recovery and CM01 heh.
Shooter XC Ship S-On RL
HBOOT version 1.50.0000 (used to be 1.4 and I only did the OTA update and install some apps/games)
eMMC-boot
Sorry for somewhat hijacking this thread, by the way. I just think it's strange to have all these problems on a stock device (though stock isn't great... ever). When I initially came on to search about it I noticed your post and jumped right in lol.
I'm glad I didn't root this thing right off the bat because of the watermark, and because of this stupid page fault.
I think wrong image thing is just your phone searchiibg for update IMG when you open the bootloader I would have to see exactly but its normal for it to check for pcwhateverimg. Whenever the bootkaoder opens. Since you have s on and don't have to worry about losing root access it night not be a had idea to update to the latest radios . Then if you still have the problem try to tIe it back. I haven't been having the problem anymore with a new kernel and new usb cord. Since it seemed to be when I plugged in. But as ling as I don't overclock above 1.6ghz I've has no problems Anymore
Shot from my Shoot3Rvo
I'm going with the acct holder (my bro-in-law) tomorrow to get a replacement. Seems we're not the only ones. There's another thread on here about this very topic...
As for rooting it, I need to read more, but doesn't it leave a mark saying it's been modded if it's 1.5 or greater, thus not returnable? I remember the Intercept doesn't have that so it was no problem switching back and forth, but it was a b***h to get a solid root...
Sent from my PG86100 using Tapatalk
I didn't read everything on hboot 1.5 but I know there is some different steps. I know there is a ROM to flash to get back to s on which is all you need for warranty to not be void I'm sure it says whether or not it works with that hboot.
Shot from my Shoot3Rvo
Awesome to hear there's a work around for the S-On. Looks like I got some reading to do when I get home from work!
Sent from my PG86100 using Tapatalk
Oh, this is so good it has to be fattening!
So I did a factory reboot and it lasted like 8 hours, whoopee...
I bring it in to Sprint and they have the tech look at it, estimating 45 minutes to an hour. Good, I had gift shopping to do. I come back and the girl gives me the (same) phone and asks me to log in. I do, and it updated my contacts, etc. She then said "He reset and updated the software so it should be okay now."
"... so why does it still say I'm roaming?"
"It does? Let me see."
She brings it to the tech, who performs the "magical" PRL update, which I TOLD them I HAD to do after every reset I did. Fine. It's working now, and I have no roaming charges, so not worried about the bill. I go home and enjoy the rest of my time before work. I get into my work parking lot, and the phone resets. Mother ****ers. I'm back in roaming, too!
Looks like I have somewhere to be first thing in the morning and to directly talk to the tech and ask, "Did you really think that a severe page fault that's embedded into the ROM would be cleared by a factory reset? The device needs to be flashed or replaced."
I told the girl straight up that I can fix it in 20 minutes, and that I rooted and modded my Intercept on Virgin Mobile (which they sign contracts at that location for heh) and it cleared up all my problems. Then, that I can't do that with this phone because I can't return it if it screws up again.
Ugh! Why do they release crap like this?! There are thousands of people that have this phone with this rebooting problem... Shouldn't there be a recall? Even on the Sprint customer forums there's posts about it, so Sprint KNOWS of this issue, especially if a manager replaced 8 devices in one day for the same problem.
So anyway, I'm on my way home from work, and I click the phone on to pull Pandora up, and it resets, but it doesn't go back to the home screen. It's stuck in a boot loop again! YES! I removed and replaced the battery and it did it again. I took the battery out and just set it on my desk, waiting for the tech to turn it on. Hooray that it got stuck, so I can rub this in his face. I should be working there, not him. (Sorry for my ranting, I'm just tired of Android problems because of carriers changing the software and locking it up. Google WANTS people to make the software their own!)
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
rigmort said:
Pull your SD card and run without it. If it stops rebooting, format the SD on a pc.
Click to expand...
Click to collapse
I've seen that on another forum. Thank you for the SD card insight. Just as a precaution, I'm just going to pull all the crap off my card and format it with the SD Formatter. I don't remember what the "brand" is but I know it's the right one. Should I back it up and format through the phone, or use the adapter and format the computer way? I'm thinking phone...
I talked directly to the tech today and told her what the log said and that it needs to be reflashed. After the estimated time she gave it back saying that she ran it through every test their system can run and the software has no errors (which my logs say as well), but she reflashed anyway to make sure (I'm still not sure how she logged into my gmail if she reset it...) I have to call corporate for the roaming issue because I'm connecting to the wrong tower, which she doesn't have permission/clearance to change. If, after fixing the roaming, it still does reboot, it will be replaced. I'm still under warranty, so I'm curious as to why they're trying to keep me on, what I believe to be, a defective device... Because they can't detect anything wrong with it...
I have yet to install any apps (minus Tapatalk) and the phone has yet to reboot, and its been in my pocket all day so I would have felt it reboot. Shame because it's one of my paid apps (one out of 6), Paradise Island, Angry Birds (which wasn't opened at all during this, but it was installed), or Words with Friends. I also had ScummVM but the reboots started way before I installed it and the engines. Those are the only apps I installed the last couple times because I'm sick of reinatalling all my apps. Bigger shame because I can't install apps until I'm sure of what the problem is. Why have an amazing phone I can't use a paid app on? I'm just frustrated at this point... I have a lot of back traces to read through and no list of what is what because the phone has been cleared since then... Does the memory map stay the same no matter if it gets reset? I haven't done any Linux kernel programming so I'm learning as I Google which is what it's meant for.
I really want to Update the PRL to see if it will help with my battery life, which it should, but I don't want to change anything, in case it messes up again. It will be proof its defective. Ugh... What to do...
Merry Christmas, to those who celebrate the holiday! Happy holidays to everyone!
Sent from my PG86100 using Tapatalk
...I have a lot of problems typing with a touch screen so I edit a lot to correct things... That and my screen feels my fingertip before it touches the screen...
[EDIT] My SD card has been unmounted for who knows how long! I just remounted it as is to see if it starts rebooting.
Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
flyinjoe13 said:
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
Click to expand...
Click to collapse
There are some versions that lose connectivity/data connection but it's not a borked radio. Most of the time you can restore a working system by just turning off data for a minute and then turning it back on.
I am in the process of downloading the "stable" release from 2013-12-11, but my current nightly of 2013-12-10 hasn't had any hiccups.
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
flyinjoe13 said:
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
Click to expand...
Click to collapse
Ahhh, the 000-000-0000 number. Seriously, pull the battery. Don't shutdown, just pull it out, reseat, and turn on.
BTW, I installed the stable version yesterday and haven't had any problems. Flawless install, all of my apps still work and I didn't lose any data.
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Have you tried running the latest RUU then flashing recovery and restoring? That seemed to solve a random reboot issue I was having, although I've never had radio issues. I have dirtyracun s-off, so it was pretty quick and easy.
flyinjoe13 said:
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Click to expand...
Click to collapse
Do you have system select as automatic or home only? I have that issue when automatic is selected.
Sent from my ADR6425LVW using Tapatalk
I tried both automatic and home with same results. At some point i'll give it another try, but for now i'm going to stick with the Venom ROM because i'm getting tired of having to reset the radio. Some cold winter weekend day when i'm stuck in the house, i'll give it another shot.
Sunday evening, I went through HELL fixing my phone. Once I realized a text wouldn't go through, I tried the data and calling. Only data worked. I've rooted my phones since the Evo 4G and never had this issue before. I called Sprint at 3:30pm, spent an hr which got me nowhere and actually made it worse. She told me to do the ##72786# which shows the MDN and MSID. I've done this in the past for activation sake on previous phones, on the M9 it doesn't allow you to manually change the values which was a major problem. Once i did the reset, both values were the same and incorrect. At this point I was like OH SHIIT, cause I just realized you can't manually input the values. And because those values have to be your number, I knew was screwed...after the restart I lost my LTE as well since Sprint didn't know this was my phone due to no MDN/MSID values. I thought for sure I would have to do a new fresh install which I did NOT want to do as everything with the phone was perfect and a fresh install takes a looot of time to backup everything, reinstall, make sure settings and everything are like before. I told her to activate my S7 and reactivate the M9 to see if that did the trick to force the M9 into hands free activation and push through the MDN/MSID. I wasn't hopeful at all since I activated the M9 BEFORE I rooted it just to be sure and also cause I bought it off ebay so had to make sure all way well.
Once i got off the phone, I started searching on google/xda for a solution. It's quite a specific issue and similar ones were sparse and had a range of reasons for the issue. Mind you, all was well before this, it's basically the stock Venom rom, no major tweaking and this issue just randomly appeared for no apparent reason. I never used Titanium Backup up to this point(1 yr using the phone) or any Rom backups so I was like, might as well since I'm gonna have to start flashing to see if it fixes it. First I flashed the venom rom to see if a fresh flash did the trick...possibly the clean install requests MDN/MSID from Sprint to get the phone working. Didn't fix it. Next, I flashed the stock rooted rom which thankfully I saved when I first rooted the phone. Phone booted up, BINGO! Instant 4g connection. Phew, thank God. Then, I flashed venom again but with a full wipe to see if the stock install carried the MDN/MSID over, didn't fix it. I was so pisssed cause at this point I knew I was screwed.
Mind you, backing up/flashing and at the same time searching and trouble shooting is VERY time consuming! A fresh flash/boot alone takes maybe 10 min. I was also doing some extensive searching for the best SMS/MMS backup out there as I always keep my text records(which I'm making another thread to discuss). It's almost midnight and im PISSSED. My entire Sunday evening wasted and a random stupid problem on my phone that came out of the blue for NO reason. I'm guessing Sprint did some network update and the phone need a Profile/PRL update which it couldnt get. Not sure how that works.
I can't find the thread it was mentioned in, and I searched MANY, but someone mentioned the Sprint PRL patch(for a different issue) in Venom Hub. I didn't think that would do anything as that's preferred roaming list. I had nothing to lose and it was a Sprint specific patch so I tried it. I never used Venom Hub as I mentioned the phone is pretty much stock venom so I didn't know it was there. Prior to this I checked Venom tweaks, nothing of course. Phone restarts, still no data. I go to the settings mainly to see "phone information" and what do you know, "System Updates" is there. I click Update Profile, phone restarts, and BAM we are back online! You have no idea how happy I was! Was able to keep my phone as it was with no wipe/fresh start!
I don't know why software updates was removed in the first place! That's why I NEVER had this issue or data/call/text issues on previous phones, as I would periodically do a Profile/PRL update for good measure. Any1 know why it was removed?!? This is a vital feature to have on the phone! Mind you I never had issues, but you have no other options once you do run into an issue like this other than to do the Profile update. I don't see why they removed it, it's not bothering anything or taking up space/resources/etc. To my understanding from prior phones and years of rooting, it's standard procedure to do Profile/PRL updates from time to time to "sync/update" the phone when network/tower updates are done with Sprint.
I know this post is looong, but I literally spent from 3:30pm to 1:30am this Sunday talking to Sprint, flashing, backing up, researching. I was beyond pissed as the hrs went by with no solution on hand(I did NOT want to start fresh). This is my first post ever and my first time becoming a member for this reason. This issue is rare as I never, ever had an issue like this, but if any1 else out there runs into it, I hope they find this thread!