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.
Related
Hey guys, is anyone else getting these random reboots? Its happened several times now and I got the phone on Friday morning. Last time it happened ( 10 min ago), i was in XDA app. When it reboots the red charging LED comes on for a second. I have no idea why its doing this.
Return it.
Are you sure I should return it already? I was wondering if maybe it was common among many people.
Sounds like a faulty phone, simply go get another one. Sprint knows there is going to be issues and will be happy to replace them. I nor my friends have had a problem with it yet.
yeh sounds defective...i haven't had a single non-initiated reboot since wednesday...
CAxVIPER said:
Sounds like a faulty phone, simply go get another one. Sprint knows there is going to be issues and will be happy to replace them. I nor my friends have had a problem with it yet.
Click to expand...
Click to collapse
Ehh alright i really didn’t want to have to return it or anything. Guess I'll take it to sprint later this week
At least do a clear storage first. Then see. That's probably the first thing they would do... and then they would tell you to come back if the problem continues. This way, you have at least eliminated that as a possibility. Also, what all did you install? This could be an app doing it.
Yuppers...no reboots here. Not since the Hero days I'd say its an app or your phone.
-- Sent from my 3VO Shooter --
Hmm true, Im guessing an app is eating my ram because I constantly.have over 50% used
edufur said:
At least do a clear storage first. Then see. That's probably the first thing they would do... and then they would tell you to come back if the problem continues. This way, you have at least eliminated that as a possibility. Also, what all did you install? This could be an app doing it.
Click to expand...
Click to collapse
Shot from my L96A1
I just got a random reboot while using speedtest.net app. I ran like 4 in a row, then suddenly it shut down and booted up. I am pretty sure I'll be returning mine, as I've had a slew of other random bugs/issues going on. I was trying to determine if it's just buggy software, or if there is a problem with the phone.
What other issues do you,have? I noticed one otjer thing that htcs task.manager and the built in running services from the settings app show different amounts of memory and amt used/free. I'm betting this is just software issue. I really dont want to have return and resetup my phone
k2buckley said:
I just got a random reboot while using speedtest.net app. I ran like 4 in a row, then suddenly it shut down and booted up. I am pretty sure I'll be returning mine, as I've had a slew of other random bugs/issues going on. I was trying to determine if it's just buggy software, or if there is a problem with the phone.
Click to expand...
Click to collapse
Shot from my L96A1
Have you taken the ota's
Bussin Caps from my 3D shooter
I had a random reboot before I did any updates, and now no issues that I didn't cause with my own ignorance so far
Bussin Caps from my 3D shooter
Yeah, iv only had one reboot after otas
ktrotter11 said:
Have you taken the ota's
Bussin Caps from my 3D shooter
Click to expand...
Click to collapse
Shot from my L96A1
Get all the updates and then do a factory reset and see how it works after that.
I had the random reboots. I tried hard reset without any apps and without setting up email and I'd still get the reboots randomly. I exchanged it for another one at Bestbuy and I haven't had a single reboot since. Even with all my apps, email, and calendars setup. I'd return it! Also, I did not install the updates on either phone. I just tried the speedtest.net app four times in a row and I did not get any reboots. Let me know if you want me to check out anything else.
I was having the same problem before and after otas. I was also getting a blank screen once in a while too. I got mine wed and probably pulled the battery about 20 times. Finally broke down and did a factory reset by holding the volume key down when powering on and selecting factory reset. Its been fine so far. I also wiped 16gb sd card from evo, formated it in phone and only copied media files over.
dmacias said:
I was having the same problem before and after otas. I was also getting a blank screen once in a while too. I got mine wed and probably pulled the battery about 20 times. Finally broke down and did a factory reset by holding the volume key down when powering on and selecting factory reset. Its been fine so far. I also wiped 16gb sd card from evo, formated it in phone and only copied media files over.
Click to expand...
Click to collapse
I did the same as you too. It seemed better at first but then it started again. I also found that after erasing the sd card with the phone I had folders that where inaccessible after android created the new ones. I ended up formatting the card with windows and deselected the quick format option. That fixed the problem with the sd card. Note all this stuff was with my first phone. The replacement has been flawless.
I'm gonna hold out another week, if I get any reboots in that time, it's back to sprint for a new one.
I got mine on Friday, then all of a sudden out of no where I started getting random reboots last night about every 10 minutes, then when I was able to get it to stay on for a while the screen would just go black and the buttons stay lit up though. Oddly enough it was doing that all last night and all this morning, until about 9 this morning and since then it's been running fine. I was able to track down my problem somewhat at least, for some reason it kept trying to sync my exchange account and it was unable to sync, and every time i tried to open up that email account to delete it, the screen would go blank. Even though everything is working know I'm still going to the sprint store today to see if they will exchange it.
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!
I started having this issue about 4 or 5 days ago. randomly my phone will pop up SIM card removed, please restart. I restart the phone has no signal, I reboot once more and all is right with the world. It's starting to get annoying though. I've tried this with PA and SB and it happens in both. Additionally recently my GPS has been having one heck of a time locking when it used to take 10 seconds and with SB it won't even acknowledge that the GPS is even turned on. I don't remove my SIM card at all, the phone isn't dropped or treated harshly. Is this a hardware issue and should I contact Samsung for a replacement? I haven't flashed back to stock yet, but I think that might be my next step as if nobody has any ideas.
Any thoughts?
Current config:
Rooted, SlimBean 2.9.0, Radio UCFL6 Kernel 3.0.49-cyanogenmod-g00e92fa
Thanks
Theoriginalgiga said:
I started having this issue about 4 or 5 days ago. randomly my phone will pop up SIM card removed, please restart. I restart the phone has no signal, I reboot once more and all is right with the world. It's starting to get annoying though. I've tried this with PA and SB and it happens in both. Additionally recently my GPS has been having one heck of a time locking when it used to take 10 seconds and with SB it won't even acknowledge that the GPS is even turned on. I don't remove my SIM card at all, the phone isn't dropped or treated harshly. Is this a hardware issue and should I contact Samsung for a replacement? I haven't flashed back to stock yet, but I think that might be my next step as if nobody has any ideas.
Any thoughts?
Current config:
Rooted, SlimBean 2.9.0, Radio UCFL6 Kernel 3.0.49-cyanogenmod-g00e92fa
Thanks
Click to expand...
Click to collapse
I am having these issues as well that have suddenly surfaced. I have tried different Roms and other radios all with the same results. I recieve a pop up when for some reason it can't find a mobile network and wants me to reinsert my sim card. Data seems to work but no phone calls or txt msgs. Sometimes I'll have to reboot serveral times to get it back to operating normal. It's almost like something happens to my APN settings because I am unable to look at them when this happens, it just kicks me out.
itbull said:
I am having these issues as well that have suddenly surfaced. I have tried different Roms and other radios all with the same results. I recieve a pop up when for some reason it can't find a mobile network and wants me to reinsert my sim card. Data seems to work but no phone calls or txt msgs. Sometimes I'll have to reboot serveral times to get it back to operating normal. It's almost like something happens to my APN settings because I am unable to look at them when this happens, it just kicks me out.
Click to expand...
Click to collapse
It could very well be your APN settings. When unapproved flags are address, the network has the ability to knock you off of a custom APN to the high-priority APN profile. If your APN profile has the "Hipri" flag, which marks it as the default, and your network kicks you off of it, it will keep trying to connect using the bad profile. Which is why you shouldn't use that flag for custom APNs.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Jamesyboy said:
It could very well be your APN settings. When unapproved flags are address, the network has the ability to knock you off of a custom APN to the high-priority APN profile. If your APN profile has the "Hipri" flag, which marks it as the default, and your network kicks you off of it, it will keep trying to connect using the bad profile. Which is why you shouldn't use that flag for custom APNs.
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Click to expand...
Click to collapse
That makes some sense as it isn't a set amount of time before it happens, and it happens in different ROMS. But I'm using the APN that's in those ROMs, and it only seems to happen when my phone is idle. I haven't migrated my phone to Stock yet, but when it happens again, I think I just might.
Any Other thoughts?
Theoriginalgiga said:
That makes some sense as it isn't a set amount of time before it happens, and it happens in different ROMS. But I'm using the APN that's in those ROMs, and it only seems to happen when my phone is idle. I haven't migrated my phone to Stock yet, but when it happens again, I think I just might.
Any Other thoughts?
Click to expand...
Click to collapse
I'm in the same boat as you. Yesterday was unbearable. I must have rebooted my phone < 20 times during the course of the day. I've been through my devices with various roms over the years and this just stinks. I'm starting to think it's a hardware problem at this time or a faulty sim card.
itbull said:
I'm in the same boat as you. Yesterday was unbearable. I must have rebooted my phone < 20 times during the course of the day. I've been through my devices with various roms over the years and this just stinks. I'm starting to think it's a hardware problem at this time or a faulty sim card.
Click to expand...
Click to collapse
Have you attempted to replace your SIM or return the phone all the way to prerooted setup? My phone has been behaving the last couple of days (said it was no better than an Iphone, seemed to have taken it to heart), so I haven't tried wiping back to factory setup. It seemed to get really bad there for a while for me, I rebooted as much as 8 or 10 times a week or so ago, this week seems better. This week will be a good test because it's a holiday and a lot of people will be on their phones and we can see if it's an APN thing or a hardware thing. From my testing it's either hardware or network interfacting, not ROM unless it's Kernel, but if it were kernel a whole lot more people would be having these issues.
Theoriginalgiga said:
Have you attempted to replace your SIM or return the phone all the way to prerooted setup? My phone has been behaving the last couple of days (said it was no better than an Iphone, seemed to have taken it to heart), so I haven't tried wiping back to factory setup. It seemed to get really bad there for a while for me, I rebooted as much as 8 or 10 times a week or so ago, this week seems better. This week will be a good test because it's a holiday and a lot of people will be on their phones and we can see if it's an APN thing or a hardware thing. From my testing it's either hardware or network interfacting, not ROM unless it's Kernel, but if it were kernel a whole lot more people would be having these issues.
Click to expand...
Click to collapse
I haven't tried to revert back as of yet or replace the sim card. Had 2 issues so far today and I couldn't take it anymore so I ended up taking out my sim and brushing the contacts with an old toothbrush. I then cut a small piece of paper and slid it in with the card on the back of it. Its in there tight and making great contact now. Pretty sad that this is what its gotten to but I haven't had any issues yet. Will keep everyone updated though.
Sorry to dig up an old thread of mine, but I figured it would be better than opening a new one. The issue has changed a little. I'm still running into the issue of the network not connecting, but now seems to occur only when I reboot. I've rebooted my phone probably 30 or so times today and my network hasn't returned. I did notice something though. While I'm having this issue, I attempted to access my APNs list and it dumps back to settings. Anyone having these issues as well? Also anyone have any idea which service the APN/phone system rely on? maybe all that it needs is to be for stopped, cleared and restarted?
Thanks guys.
Galaxy Note SIM card removed please reboot
I'm getting this all of a sudden. I've been using a stock original ROM for 8 months, and 3 weeks ago I woke up one morning with this message. Every couple of days I was getting this message. I then went to the AT&T corporate store and got a replacement SIM card. This had no effect. So I thought, I'll try a new ROM and see if that helps, I backed up with online Nandroid, and loaded "[STOCK ROM] IML74K.UCLD3 for SGH-I717" loaded perfectly, and all functions seem to work so far. However, since I did this last night I've had to reboot the phone like 10 times. I've reseated the SIM card, but still get the error message.
Any ideas as to what could be causing this? I've read this thread and see the APN issue, but from what I've read here that seems to be part of the ROM loaded...
Back story, I tried the kies update around 8 months ago, and while it did update, all the icons would disappear from the notification bar, and then reload, every few minutes. If I was on a call during this, the call would be dropped. Since I couldn't undo the change through kies, I came here and went with what seemed to be the original stock ROM for the Note, but Kies no longer recognized it as a supported firmware. So when this issue happened I came back here to upgrade.
Fyrebaugh said:
I'm getting this all of a sudden. I've been using a stock original ROM for 8 months, and 3 weeks ago I woke up one morning with this message. Every couple of days I was getting this message. I then went to the AT&T corporate store and got a replacement SIM card. This had no effect. So I thought, I'll try a new ROM and see if that helps, I backed up with online Nandroid, and loaded "[STOCK ROM] IML74K.UCLD3 for SGH-I717" loaded perfectly, and all functions seem to work so far. However, since I did this last night I've had to reboot the phone like 10 times. I've reseated the SIM card, but still get the error message.
Any ideas as to what could be causing this? I've read this thread and see the APN issue, but from what I've read here that seems to be part of the ROM loaded...
Back story, I tried the kies update around 8 months ago, and while it did update, all the icons would disappear from the notification bar, and then reload, every few minutes. If I was on a call during this, the call would be dropped. Since I couldn't undo the change through kies, I came here and went with what seemed to be the original stock ROM for the Note, but Kies no longer recognized it as a supported firmware. So when this issue happened I came back here to upgrade.
Click to expand...
Click to collapse
this is a software issue i have finally gotten it fixed.
I had JB 4.1.2.
You will need to download ODIN and flash here are the firmwares for your specific phone.. http://forum.xda-developers.com/showthread.php?t=1771687
I used ICS and the problem has gone. Make sure you do a factory reset through stock recoveryt mode after the phone reboots from installing the new software. To get to this screen press volume up, home and power and let go when blue print comes at the top.
Is not software issue , is Note model issue. The way to fix it is making a paper with the size of the SIM and put the SIM and the paper together into SIM place. The Galaxy Note SIM card place is little more bigger than others phone and SIM is not contacting good there. I just tried on some phones , on all them working but on NOte the SIM was moving and it gaves the error. Here I add a photo of how is my Note looking, just to say my SIM card is white.
ShiftShapa said:
this is a software issue i have finally gotten it fixed.
I had JB 4.1.2.
You will need to download ODIN and flash here are the firmwares for your specific phone.. http://forum.xda-developers.com/showthread.php?t=1771687
I used ICS and the problem has gone. Make sure you do a factory reset through stock recoveryt mode after the phone reboots from installing the new software. To get to this screen press volume up, home and power and let go when blue print comes at the top.
Click to expand...
Click to collapse
i'm with Rogers in Canada, rogers isnt listed can i use the others safely?
dicecuber said:
i'm with Rogers in Canada, rogers isnt listed can i use the others safely?
Click to expand...
Click to collapse
See what I wrote some posts before
Enviado desde mi GT-N7000 usando Tapatalk 4
herna said:
See what I wrote some posts before
Enviado desde mi GT-N7000 usando Tapatalk 4
Click to expand...
Click to collapse
can you post a video of what you did? the pic doesn't work for me
dicecuber said:
can you post a video of what you did? the pic doesn't work for me
Click to expand...
Click to collapse
{
"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"
}
Enviado desde mi GT-N7000 usando Tapatalk 4
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
"HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
Press key to choose Dload Mode/Reboot/Fasatboot.
1) Vol up : Dload mode.
2) Vol Down : Reboot.
3) Power : Fastboot
If you choose Dload Mode,
Please do the following action.
1) Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Dubug App
3) Send email to contact point or [email protected]
--------------------------------------------------"i was very careful to press the Vol Down button...hell, i even looked at the button cause i was a bit off put by this funky screen. well it seems to have received a Vol Up command and replied with:
"Vol Up is pressed : Jump to Dload Mode."
I tracked down and installed the QPST 2.7 but am unable to get it to detect my phone. So I guess i'm off to BestBuy in a few minutes. joy.
thought i'd share this in case it's of any use to anyone. i'm not a developer nor a programmer. but i've mucked about with Android for a while and have not seen such a screen in the past...nor have i come across something i couldn't eventually undo/back out of. but i can't pull the battery...i've pressed all buttons...i've pressed both Vol+/Vol- at the same time...can't get the phone to reboot. damn non-removable battery.
edit: holding down pwr button for more than a few seconds resolved it. yes, i freaked out a bit.
Did you hold the power button in for 20 seconds to force a shut down and then just turn it back on?
DraginMagik said:
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
"HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
Press key to choose Dload Mode/Reboot/Fasatboot.
1) Vol up : Dload mode.
2) Vol Down : Reboot.
3) Power : Fastboot
If you choose Dload Mode,
Please do the following action.
1) Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Dubug App
3) Send email to contact point or [email protected]
--------------------------------------------------"i was very careful to press the Vol Down button...hell, i even looked at the button cause i was a bit off put by this funky screen. well it seems to have received a Vol Up command and replied with:
"Vol Up is pressed : Jump to Dload Mode."
I tracked down and installed the QPST 2.7 but am unable to get it to detect my phone. So I guess i'm off to BestBuy in a few minutes. joy.
thought i'd share this in case it's of any use to anyone. i'm not a developer nor a programmer. but i've mucked about with Android for a while and have not seen such a screen in the past...nor have i come across something i couldn't eventually undo/back out of. but i can't pull the battery...i've pressed all buttons...i've pressed both Vol+/Vol- at the same time...can't get the phone to reboot. damn non-removable battery.
Click to expand...
Click to collapse
Like Whiteguypl just said... thats all you have to do. Just hold power off for 20 seconds and it will turn off. Then you reboot it. It will boot up fine.
It was just a HW crash.
My phone has had it happen quite a few different times and its still running.
Jhoopes517 said:
Like Whiteguypl just said... thats all you have to do. Just hold power off for 20 seconds and it will turn off. Then you reboot it. It will boot up fine.
It was just a HW crash.
My phone has had it happen quite a few different times and its still running.
Click to expand...
Click to collapse
The demigod screen I had said watchdog bark detected, it also registered vol dn as vol up. Wouldn't boot and went into dl mode when connected to charger, had to use lgnpst to fix it.
thank you guys. in my concern i guess i wasn't holding down the power button long enough. i was doing a 10count in my head...which was prolly more like 5 or 6 seconds given how my mind was like "awww crap".
Also, for future reference, most of the debug screens seem to swap volume up and volume down. And I got this screen once, but never have had it again.
Sent from my LG-E970 using xda app-developers app
SnowLeopardJB said:
Also, for future reference, most of the debug screens seem to swap volume up and volume down. And I got this screen once, but never have had it again.
Click to expand...
Click to collapse
well that is just ...
{
"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"
}
Eh, vol up... Vol down... Same difference.
Sent from my LG-E970 using Tapatalk 2
I've been meaning to ask about this, but since I'm a noob, I didn't want to get flammed. I've been getting a similar crash screen on average of twice a day ever since I unlocked the OG. Everything is the same as your HW crash screen, except that it says "Kernel Crash" instead. After realizing the volume buttons were switched I've just been restarting with the power button.
Anyone else getting that crash? It's getting annoying especially since if it happens when it was supposed to be asleep in my pocket, the screen being on will suck down my battery. Fortunately, since it's a new toy, it doesn't stay in my pocket long, but at some point this could be trouble.
In case it matters, I unlocked using the FreeGee app (TWRP recovery) and am currently running The Base 0.7.3 and KernelSk8 2.2, but it did it back when I just had the stock ROM and kernel as well. Any insight would be appreciated. I may be a noob, but I've spent hours on this forum reading up on this phone, and that has helped me immensely, but this is the first issue I've come across that hasn't been addressed until this thread.
Sent from my Nexus 7 using Tapatalk HD
DraginMagik said:
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
"HW reset was detected!
---------------------------------------------------
DemiGod Crash Handler : HW reset was detected!
Press key to choose Dload Mode/Reboot/Fasatboot.
1) Vol up : Dload mode.
2) Vol Down : Reboot.
3) Power : Fastboot
If you choose Dload Mode,
Please do the following action.
1) Dload Mode. Please connect USB
2) Get the ram dump image using QCT's Memory Dubug App
3) Send email to contact point or [email protected]
--------------------------------------------------"i was very careful to press the Vol Down button...hell, i even looked at the button cause i was a bit off put by this funky screen. well it seems to have received a Vol Up command and replied with:
"Vol Up is pressed : Jump to Dload Mode."
I tracked down and installed the QPST 2.7 but am unable to get it to detect my phone. So I guess i'm off to BestBuy in a few minutes. joy.
thought i'd share this in case it's of any use to anyone. i'm not a developer nor a programmer. but i've mucked about with Android for a while and have not seen such a screen in the past...nor have i come across something i couldn't eventually undo/back out of. but i can't pull the battery...i've pressed all buttons...i've pressed both Vol+/Vol- at the same time...can't get the phone to reboot. damn non-removable battery.
edit: holding down pwr button for more than a few seconds resolved it. yes, i freaked out a bit.
Click to expand...
Click to collapse
Off topic but how did you get your Ingres activation code? I've been trying for over a month with no success.....
Nastybutler said:
In case it matters, I unlocked using the FreeGee app (TWRP recovery) and am currently running The Base 0.7.3 and KernelSk8 2.2, but it did it back when I just had the stock ROM and kernel as well. Any insight would be appreciated. I may be a noob, but I've spent hours on this forum reading up on this phone, and that has helped me immensely, but this is the first issue I've come across that hasn't been addressed until this thread.
Click to expand...
Click to collapse
i'm rooted/unlocked running TWRP & TheBase .7.3. used the FreeGee app as well.
have you tried reflashing TheBase and not using Sk8's kernel?
if it happens with TheBase and Sk8's kernel...then i'd post the question and error in that thread.
if it happens with TheBase and either kernel...then i'd try posting in TheBase thread.
don't be afraid of getting flamed. we all ask dumb questions from time to time and we are all weak on some topics...just try not to come off sounding rude or belligerent and most folks will do as they can to help.
Yamahar6riding said:
Off topic but how did you get your Ingres activation code? I've been trying for over a month with no success.....
Click to expand...
Click to collapse
every day i'd enter my email addy on the ingress.com website. took me a while as well. sadly, i got no invites to pass on to folks.
DraginMagik said:
i'm rooted/unlocked running TWRP & TheBase .7.3. used the FreeGee app as well.
have you tried reflashing TheBase and not using Sk8's kernel?
if it happens with TheBase and Sk8's kernel...then i'd post the question and error in that thread.
if it happens with TheBase and either kernel...then i'd try posting in TheBase thread.
don't be afraid of getting flamed. we all ask dumb questions from time to time and we are all weak on some topics...just try not to come off sounding rude or belligerent and most folks will do as they can to help.
Click to expand...
Click to collapse
Thanks DM. My kernel crashes have occurred with the stock ROM and kernel, then also after I flashed TheBase but kept the stock kernel. So I thought I'd try Sk8's kernel to see if that would stop the crashes, but no such luck. The frequency didn't really vary after any particular step, and the only constant has been the FreeGee unlocking and TWRP. I guess I can try CWM, but then I won't be able to make backups (I believe that's still an issue with CWM, right?).
Sent from my Nexus 7 using Tapatalk HD
I had it happen when the volume got to high and the ear damage warning popped up, then a few seconds later BAM Demigod screen.
Nastybutler said:
Thanks DM. My kernel crashes have occurred with the stock ROM and kernel, then also after I flashed TheBase but kept the stock kernel. So I thought I'd try Sk8's kernel to see if that would stop the crashes, but no such luck. The frequency didn't really vary after any particular step, and the only constant has been the FreeGee unlocking and TWRP. I guess I can try CWM, but then I won't be able to make backups (I believe that's still an issue with CWM, right?).
Click to expand...
Click to collapse
not sure about CWM. i've been hesitant to use it since my early days with my EVO4G, there were a couple tasks it didn't do quite right. haven't read up on it much since.
i'd try to get someone like Sk8 or another low level developer to see and ponder your issue. if that's not the case, perhaps document how often it happens and contact LG or ATT for a device replacement. it's well beyond my limited knowledge. although, sometimes a well timed threat with a ball peen hammer can help.
I will upload my source compiled kernel after I have a few more cups of coffee. I have been on it since Dec. 6th without a single issue. I also should mention I updated my TWRP in Goo Manager and I have backed up and restored dozens of times on my external SD. My music is there, init.d works so I added a zipalign script. Rock solid...give me a little while. Team Nov is using it in their latest release until they start bringing some flamethrower kernels
Edit..kernel compiled by Shabbypenguin. Check his resumé if you haven't heard of him. He's legit
Sent from my LG-E970 using Xparent ICS Tapatalk 2
Hi folks, new here, been lurking a while, yadda yadda. Hardly the place for intros.
Anyhow, I am having this problem as well, usually multiple times a day. Stock firmware/rooted/unlocked. Phone is the earliest revision (have there been hardware revisions?); it was a pre-order. As stated, it's been happening since unlocking with Freegee; however, even before rooting my phone would randomly reboot and on a couple of occasions simply power off while in my pocket as has been mentioned in other threads.
Has anyone made any headway with this? I get that the reset procedure is simple, but it's hard to take phone calls when your phone's had a panic attack.
Spot-on text dump on the first post; I grabbed a picture of the screen my crashed phone for the record.
xcmartin said:
Hi folks, new here, been lurking a while, yadda yadda. Hardly the place for intros.
Anyhow, I am having this problem as well, usually multiple times a day. Stock firmware/rooted/unlocked. Phone is the earliest revision (have there been hardware revisions?); it was a pre-order. As stated, it's been happening since unlocking with Freegee; however, even before rooting my phone would randomly reboot and on a couple of occasions simply power off while in my pocket as has been mentioned in other threads.
Has anyone made any headway with this? I get that the reset procedure is simple, but it's hard to take phone calls when your phone's had a panic attack.
Spot-on text dump on the first post; I grabbed a picture of the screen my crashed phone for the record.
Click to expand...
Click to collapse
For whatever reason the frequency of my kernel crashes has dropped way down. Not sure what I did to make it so. Hasn't happened to me at all in about a week.
I just got on ingress and just got my first yellow sod...wonder if it's related.
DraginMagik said:
so i had been listening to the Lord of the Rings during breakfast..played a lil Need for Speed...jammed to a lil Pandora radio. was heading home and thought i'd hack a few Ingress portals. all went well until i attempted to deploy my first XMP doohickie. my phone froze and hung there for a minute...then it rebooted..no worries right? but it came up into some sickly yellow screen with yellow text.
L
Click to expand...
Click to collapse
Sent from my Xoom using xda app-developers app
You are getting that screen because of the kernel from freegee. Normally your phone would just reboot.
Over here from the Sprint Optimus G forum. We're seeing all these freezing/kernel crash/HW reset issues on Stock locked unrooted and everything base off of it. We are also seeing this with custom kernels as well.
Thinking this is not an Ingress issue but an LG issue as jokersax and I have found a number of things broken from the kernel level on up.
EDIT: As a point of note. I've tried to duplicate any of these issues on a Hero, Evo Shift, HTC View, Original Galaxy Tab (wifi & Sprint), Atrix, Photon, Photon Q, Nexus One, GNex and Nexus7. Except for the obvious, like the Hero lagging really bad, none of these devices are anywhere near as unstable as the Optimus G.
I was in class today and my phone vibrated a few times notifying me of text messages. I checked the phone when I got outside and was greeted by this screen
http://i.imgur.com/WFQ33Rf.jpg
Not my phone, but the same problem!
I've been running the same CM 10 rom for months now. I can't remember if it was a stable or RC but it was good enough that I didn't feel the need to mess with my phone for perhaps the last 5 or 6 months. It's been a while.
Details:
The phone still vibrates and receives messages. I know this because I'm confirming with google voice online that messages are coming in when its vibrating. I can turn the screen on and off, but I'm just greeted by this screen. I can force the phone to reboot by holding the power button, but even the starting animations won't show. It turns on immediately to this. During the start-up animation, it usually has a point where the screen brightens and then dims and even this occurs. The buttons and everything are all doing what they need to do. I can unlock the screen and everything as I can feel the feedback. The volume rocker works and reacts properly. Everything is working except the screen.
Any ideas?
I'd like to apologize if this is a common problem and the solution is posted somewhere as I have not frequented these boards recently and am currently at work so I can't spend much time searching.
Yeah, see my post about the confetti. It went confetti very soon after it went contrast. I run stock CPU speed with stock voltage.
Ironic that yours happens just as mine did. I'm using the phone now. I have the screen turned on to never go to sleep now so that I don't have to try and wake it up. Then I may get that screen and to prevent that? Turn it off, turn it on, turn off, turned on and eventually I'll get the lock screen.
I run meanbean rom with the 1.19 hboot, s-on. I'm going to return it to stock then take it back to sprint. Provided I can keep the phone functional long enough to do this.
This will be my second phone to do this. First 1 did it last September.
Sent from my EVO using xda app-developers app
It's a shame. I've had this since launch and haven't had a single problem with it. Unfortunately, no matter how many times I turn the screen on and off, I can't get it to the lock screen.
Edit: I have a feeling this isn't going to be an easy fix. I'm gonna switch to my brothers old Evo 3D as soon as I get home
http://forum.xda-developers.com/showthread.php?p=38160970 is my original post (first)
I would like to add the screen freezes when the battery gets to a full charge. Unplug it and it recovers almost instantly. Interesting I'd say.
Sent from my EVO using 2 kidneys and a rock.
Yeah, I went through your post. I can see that no one really had any idea for you either which was kinda disheartening. I'll have to play around with it when I get home tonight, but I'll be forced to switch to an older phone as I won't have enough time to fix this on my own right now
Sprint exchanged the first one because the grfx chip went bad according to them. My concern is that it was not that long ago and now I have the same issue. How old is your phone?
Sent from my EVO using xda app-developers app
My concern is that they won't exchange it unless I can get it back to stock, but I'm assuming there's no way for them to know considering they can't access anything on the screen?
I've had the phone since June. Never had a problem with it
I think the screen might show via the hdmi feature but I'm not going to force the issue. You should be able to answer incoming call via bluetooth adaptor. I can also listen to Pandora via bluetooth through my head unit in my truck. Also make phone calls through my head unit to but I'm not going go to the car in the phone calls unless I'm in it.
If your proficient with voice commands via bluetooth or Google Voice you maybe able to get some functionality of the phone for a little bit more time. I would like to see if other folks have this issue also.
Sent from my EVO using xda app-developers app
http://code.google.com/p/androidscreencast/
I found a link to this program which allows you to access your phones screen that I think may be helpful! I'm going to use this to get what I need off the phone, get it back to stock, and return it to the store tomorrow. I'll update this post later tonight when I get home
The only time this happened to me is when my voltages were too low. I would boot into recovery and reflash your ROM or the voltage increase script in thick lizards dev host folder.
If you can get to recovery which shouldn't be a problemyou can fix this easily.
Sent from my EVO 4G LTE using xda premium
So I'm back to stock using racun's soff procedure. I still has pixy dust issues. Will look into the thicklizzard angle tomorrow.
Zori said:
I was in class today and my phone vibrated a few times notifying me of text messages. I checked the phone when I got outside and was greeted by this screen
http://i.imgur.com/WFQ33Rf.jpg
Not my phone, but the same problem!
I've been running the same CM 10 rom for months now. I can't remember if it was a stable or RC but it was good enough that I didn't feel the need to mess with my phone for perhaps the last 5 or 6 months. It's been a while.
Details:
The phone still vibrates and receives messages. I know this because I'm confirming with google voice online that messages are coming in when its vibrating. I can turn the screen on and off, but I'm just greeted by this screen. I can force the phone to reboot by holding the power button, but even the starting animations won't show. It turns on immediately to this. During the start-up animation, it usually has a point where the screen brightens and then dims and even this occurs. The buttons and everything are all doing what they need to do. I can unlock the screen and everything as I can feel the feedback. The volume rocker works and reacts properly. Everything is working except the screen.
Any ideas?
I'd like to apologize if this is a common problem and the solution is posted somewhere as I have not frequented these boards recently and am currently at work so I can't spend much time searching.
Click to expand...
Click to collapse
Have you tried getting into the bootloader?
Sent from my EVO using xda premium
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
aFoodStampBaby said:
Have you tried getting into the bootloader?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Zori, is your evo S Off? Then you can flash individual kernels I think. If it is, then take a CLOSE look at unlimited.io/jewel.htm because most of that procedure is remote terminal. If you do it via ubantu, I'm thinking you can push the proper package onto the phone and update it that way.
The hardest part will be getting to recovery from the hboot screen and BAM!
{
"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"
}
The bootloader screen:
At the very least it can get you to the point of getting to stock I think. My phone seams to have recovered a bit at stock. I briefly see the confetti when I wake it. I can imagine that it would be an under volt condition while powering on. You can do it mate the force is strong.
---------- Post added at 06:23 AM ---------- Previous post was at 06:08 AM ----------
vipermod looks relevant to our issue. I will need to do some reading while the bosses are not looking.
Zori said:
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Click to expand...
Click to collapse
The online esn swap always prompts you to change plans for some reason now..have to call or chat.
Sent from my EVO using Tapatalk 2
Well my phone went all confetti, all the time. Got a new one today.
Zori said:
I tried using android screencast, but I don't think it's possible to get it running without interacting with the phone. I can't even connect the phone to my computer and use it as a storage device because I don't remember exactly where the buttons are. At this point, I'm considering flashing cm10 onto another device so that I can see where everything is and replicate the location of the screen presses on my LTE to try the voltage trick or reflashing the rom.
I'm very likely going to take it in as is and hope they don't have any way to see if its rooted or not and just give me a replacement.
Yeah, but it still gives me the same screen.
Edit: I can't even switch to my Evo 3D because it says I need to switch my plan. This is just another sprint headache considering my plan is fine for the LTE it should be fine for the 3D. I'm gonna wake up at 4am to talk to chat since they're not currently open
Click to expand...
Click to collapse
How did you make out with this issue? The same thing happened to me today. Running 10.1. Cant even see revovery.
Answer to confetti screen issue
My phone did this exact thing on Saturday. I took it in to the Sprint store, and the tech there (the only one I've ever run in to who really knows his stuff, Phil in Westminster), explained that there is a cable between the battery and screen that is "kinked" and loses contact. If you squeeze the phone really hard just above the back button the screen will come back on for a bit. They did agree to send me a new phone (I am rooted, and running a custom ROM, they did not care). I've been able to get enough functionality out of it to get by for about two days, but as of last night the screen only stays on the "confetti", and won't come back at all.
Anyway, hope that helps a bit!
crapid said:
My phone did this exact thing on Saturday. I took it in to the Sprint store, and the tech there (the only one I've ever run in to who really knows his stuff, Phil in Westminster), explained that there is a cable between the battery and screen that is "kinked" and loses contact. If you squeeze the phone really hard just above the back button the screen will come back on for a bit. They did agree to send me a new phone (I am rooted, and running a custom ROM, they did not care). I've been able to get enough functionality out of it to get by for about two days, but as of last night the screen only stays on the "confetti", and won't come back at all.
Anyway, hope that helps a bit!
Click to expand...
Click to collapse
Yup.. mine started doing the same thing couple of days back..
I instinctively started pressing the screen and it came back on.. must be the same prob like ur sprint guy said..
I'm thinking of going to sprint store but I don't have their insurance or total equipment protection plan.. so, any clue on if they will replace? Do u guys have the TEP?
Edit: Let me add that I have noticed that the screen fuzziness happens whenever i put the phone in my pocket... have started carrying it around in my hand now!!
Sent from my EVO using xda premium
[email protected] said:
Yup.. mine started doing the same thing couple of days back..
I instinctively started pressing the screen and it came back on.. must be the same prob like ur sprint guy said..
I'm thinking of going to sprint store but I don't have their insurance or total equipment protection plan.. so, any clue on if they will replace? Do u guys have the TEP?
Edit: Let me add that I have noticed that the screen fuzziness happens whenever i put the phone in my pocket... have started carrying it around in my hand now!!
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I didn't think I had insurance, and they were going to charge me $50 for a replacement. After they looked at my account it turned out I did have insurance on this line, so no charge.
Unfortunately, I got the replacement last night, and sound doesn't work on this one! Getting yet another replacement on Friday.