I have bought this phone new about 10 days ago, and I had used official ICS, Cyanogen 10.1.3 and I switched back to stock ICS again. Cyanogenmod had problem with games for me. When I put it on ICS again, besides random reboots, sometimes phone just turned off and when I pulled the battery and put it back to turn on the phone, a red screen appeared, like red halo or something, and it dissapears over time, also when that happens the battery falls down drasticaly. It was turned off for like 15 minutes and when I turned it on the battery went from 100% to 83%. Should I return it since it is under warranty? Or is this another issue with ICS?
kirov37 said:
I have bought this phone new about 10 days ago, and I had used official ICS, Cyanogen 10.1.3 and I switched back to stock ICS again. Cyanogenmod had problem with games for me. When I put it on ICS again, besides random reboots, sometimes phone just turned off and when I pulled the battery and put it back to turn on the phone, a red screen appeared, like red halo or something, and it dissapears over time, also when that happens the battery falls down drasticaly. It was turned off for like 15 minutes and when I turned it on the battery went from 100% to 83%. Should I return it since it is under warranty? Or is this another issue with ICS?
Click to expand...
Click to collapse
Sounds like a hardware defect to me. Just make sure it is 100% stock for the warranty.
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Sounds like a hardware defect to me. Just make sure it is 100% stock for the warranty.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I have found some threads where people said they had that red screen issue on official ICS. But since I have returned to Gingerbread (though rooted one) it seems that issues have gone away. Well the warranty is 2 years so I have some time to decide Thanks for reply...
The issue is because the phone go on deep sleep but start overheating... So when you pull the battrry thr screen is already hot..
Happen here a lot of time with different phone( i'm at my 4th phone under waranty)
Sent from my Nexus 7 using xda app-developers app
Trying to revive the dead...
Hello friends..
I have owned a LG Nitro HD since April 12. From 7- 8 months since owning the phone (after upgrading to official ICS), one fine day got a dark red screen (sort of a halo). After that started getting different design patterns on the phone. But the phone used to start even after that. This occurred few more times and the phone refused to boot at all.
Since the phone was in warranty, got it replaced.
Fast forward to September-13 with the replaced phone. I had rooted the phone and had tried different ROMS too. The phone was working fine.
Again, one fine day, I saw that dreaded red screen halo......and thats the end of it. Since then the phone has not booted. When trying to boot, it shows the LG logo, but then the screen just fades away. However i am able to go to the factory reset screen using the volume and power key.
Took the phone to ATT, they said it seems to be an hardware issue. And the phone was out of warranty, so bad luck...
I tried using the unbricking methods mentioned, but since the phone is not detected on PC nor able to do anything from the phone, so I have lost any hopes to revive.
Wanted to post since about a month, but was reluctant. Just saw this thread and thought of seeking if there is any sort of solution to this.
Here is the one of the pattern screen that i see on my phone.
{
"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"
}
>>>>Abi
Related
I'm not sure if this is a phone problem or a ROM problem. I'm on CM6.1.1 for 2 weeks already. Recently the phone starts to present symptoms of sleeping beauty where it dies off and only way to wake it up is removing battery.
Situation:
I put recurrent alarm to ring at 8.30am, the phone dies at 8.00am. Happened twice within this week already...
Today:
{
"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"
}
2 days ago
The alarm rang while not charging.
The day before:
The alarm rang while charging.
The day before:
As you can see I woke up at 10am when the alarm failed to go off.
The sleeping beauty syndrome happened a few times within the first week of having the phone and never occurred again, so I brushed it off as breaking in period. But this is too much.
The phone is about one month old now.
Anything I can do before sending it off for warranty claims?
even after gingerbread update this problem continues, and mine is not a rooted. this type of unreliability for a smartphone is completely unacceptable. has htc any answer to it? a 500 euro device that just dies on you haphazardly?
jinxman said:
even after gingerbread update this problem continues, and mine is not a rooted. this type of unreliability for a smartphone is completely unacceptable. has htc any answer to it? a 500 euro device that just dies on you haphazardly?
Click to expand...
Click to collapse
lol that's a bit of an overreaction... This definitely isn't a wide spread issue man. If your phone is messing up, you should send it in for replacement.
OP, are you underclocking or using a screen-off profile? There could be any number of things that're causing your phone to lock up and crash while sleeping.
on another note, any specific reason why you're still running CM6? CM7 has been in stable for several months now...
no cm6 or cm7, like I said, its unrooted. there are quite a few threads in other forums regarding this problem. its just crappy hardware sold expensively, that's the sad part. even heard of people exchanging the hardware and still facing this problem, one reason why I don't think that its worth bothering to send it for repairs
jinxman said:
no cm6 or cm7, like I said, its unrooted. there are quite a few threads in other forums regarding this problem. its just crappy hardware sold expensively, that's the sad part. even heard of people exchanging the hardware and still facing this problem, one reason why I don't think that its worth bothering to send it for repairs
Click to expand...
Click to collapse
I know you're unrooted. And that's why I said that you should request a replacement phone... and if that replacement has the issue, replace it again! that's why they replace it when its broken.
And like I said, no matter how many forum posts you see about the issue, it really isn't as widespread as you think.
***SOLUTION***
Buy a 10 dollar alarm clock that plugs into the wall. Never be late for work again.
SuperDave81 said:
***SOLUTION***
Buy a 10 dollar alarm clock that plugs into the wall. Never be late for work again.
Click to expand...
Click to collapse
Thissssss. I know custom ROMs are stable, and stock ROMs are supposed to be even more stable, but ffs I'd never rely on one as my only alarm clock.
Try turning gps off tell me what happens.... reason is I'm currious if that's the issue I have similar problems when my gps is on and never have any issues with it off.
Sent from my HTC Vision using XDA App
I have been rooted for a while and successfully flashed a few Roms/Kerenels using rom manager. I was flashing the newest version of Myn and one of the "warm" kernels that it offered with it. Everything was going normally the rom loaded fashed the rom and kerenel the phone was reseting then out of nowhere i got the image of the white box and android guy with an arrw as if to say "android taken out of box" I left it like that for about 5 min then took the batt out and tried to reset it. I got the same image then i tried vol. up & power it vibrated 3x and did nothing. My buddy had the same problem yesterday and he got it workin. I called him and he said all he did was pull batt/restart over and over till it booted normally. I tried that about 10x then it would not turn on again. Plugged it in, no response no led light up.
Am I bricked past the point of no return, and if not what can I do to get back in business
Try volume down + power..
also if you have a spare battery on hand try that
Ive tried all button combos ect. nothing I have tried has gotten me ANY sort of response from the phone
dnicholsokp said:
Ive tried all button combos ect. nothing I have tried has gotten me ANY sort of response from the phone
Click to expand...
Click to collapse
can u get it to turn on to splash screen?
at the risk of sounding ignorant what is that/ how would i get it up because I cannot get it to do ANYTHING but sit here off with no display no led light not led when charging its almost as if it wasnt recieving power or something
can you turn it on at all?
Can you get into the phones boot loader?
Take the battery out and plug the phone into the charger let it sit for like 1 min then put the battery back in while on the charger still. Wait for the led and then
Vol down + power
Go into wipe section and wipe everything
Do you already have updated radios?
Sent from my PC36100 using XDA App
following the steps mentioned above the LED never came on I still have not gotten it to do ANYTHING... do you think that if i brought it to a tech center they would swap it out because there is no way to get it on and if they cant get it on there is no way they could tell that it was routed.. right? also in regaurds to the antennas i believe it did i think myn made me do that as part of the kernel change/rom flash
dnicholsokp said:
following the steps mentioned above the LED never came on I still have not gotten it to do ANYTHING... do you think that if i brought it to a tech center they would swap it out because there is no way to get it on and if they cant get it on there is no way they could tell that it was routed.. right? also in regaurds to the antennas i believe it did i think myn made me do that as part of the kernel change/rom flash
Click to expand...
Click to collapse
First yeah they should just exchange it at a sprint corporate store.
Second myn didn't make you do anything, he made a suggestion.
Third now I know what you did wrong, which was obviously pulled the battery while the radio was updating.
Fourth, you have no choice but to turn it into sprint as there are several documented occasions where ppl have done the exact same thing and had to exchange their phone..
Fifth get a good nights rest and head to sprint first thing in the morning!
Sent from my PC36100 using XDA App
I agree with craig... sleep on it.
Sent from my PC36100 using Tapatalk
that is the reason Why I don't flash roms.
Yea dude being that I just went through 4 evo's before I finally got it right ik the pain but you gotta just suck it up and bring the poor thing back to sprint
Sent from my PC36100 using XDA App
you pulled the battery while it was updating the radio, didnt you.
{
"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"
}
Just smash the phone on the floor,tell Sprint you droped it. Pay the $100.00 insurance and walla! New EVO!
Possible Fix
Last night I decided to flash Calkulin's Radio, WiMAX, PRI & NV combo..something I have done several times. Only this time I was discharging my battery and I forgot that the low battery warning had come on. So, long story short, I ended up with the little box and the android guy. I did a search and came to this thread. Anyway, out of desperation to do something, I connected my phone to fastboot commander and since I couldn't put my phone into fastboot mode the phone was not recognized. So I switched it to the system settings. No sooner than I connected it than the the progress bar started initializing under the android guy. The screen dimmed and came back on and then went to the splash sceen and booted up. I don't know if this is a fluke or what, but I'm pretty damn happy with myself for solving my own problem. Maybe this will help someone.
UPDATE: I tried to flash Calkulin's Radio, WiMAX, PRI & NV combo again to make sure everything flashed properly and the same thing happened. I connected my phone to fastboot commander and it worked again.
Trial and Error brotha Trial and MuthaF'n Error
dkdude36 said:
you pulled the battery while it was updating the radio, didnt you.
Click to expand...
Click to collapse
Yup only thing I could think of
I have had the Sprint Epic 4G Touch since launch day and today everything on my screen turned into a deep shade of red for a couple of minutes and I thought it was a dead screen I would have to return to Sprint and then the normal color returned out of nowhere. Does anyone know if this is something I triggered or was this just a glitch? The home button, screen off/on, changing screens did not fix this problem. All functions were working from what I could tell and I could make everything out on the screen and it was bright but everything was a shade of red.
My phone is stock and I have Go Launcher running on it with many Go Widgets. I had about 50% battery from what I remember. I may have had the Words With Friends application running at the time if anything. I have a few emulators and ROMs on my external sdcard that were not running but everything else on my phone is normal.
Thos happened to me also. i am rooted with stock kernal. was weird. i rebooted and hasnt done it since then.
Sent from my SPH-D710 using xda premium
it happened to me once since I got my phone but hasnt since. It reminds me of the red render effect in CM 7. That's the best way to describe it.
It's similar to this, not exact but similar..
{
"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"
}
Mine turned red when I went into the camera ,a light red I exited the camera locked ulocked whent to cam anc it was normal. This only happened once
Sent from my SPH-D710 using XDA App
I have had that but not red , Just green. It was when i was opening everything trying to kill my battery and played fruit ninja
dmbatson said:
I have had that but not red , Just green. It was when i was opening everything trying to kill my battery and played fruit ninja
Click to expand...
Click to collapse
Same color for me but when I was opening the web browser
Sent from my SPH-D710 using xda premium
this also happened to me once for a few minutes...freaked me out...went back to normal and not since
Since a screen shot was made
Its probably a bug sammy overlooked
If we blast sammy's twitter about they will be forced to give us that update
Why you ask
Because the other variants of the gs2 hasnt come out yet and if they wait super long to give us these updates chances are less ppl will buy the gs2 for t mobile and att
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
Since a screen shot was made
Its probably a bug sammy overlooked
If we blast sammy's twitter about they will be forced to give us that update
Why you ask
Because the other variants of the gs2 hasnt come out yet and if they wait super long to give us these updates chances are less ppl will buy the gs2 for t mobile and att
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
then lets blast away!! consumers shouldn't sit aside with faulty products because a company is too big to admit to its faults
graffixnyc said:
it happened to me once since I got my phone but hasnt since. It reminds me of the red render effect in CM 7. That's the best way to describe it.
It's similar to this, not exact but similar..
Click to expand...
Click to collapse
This is extremely close to how it looked on my screen. I tried recreating it but couldn't. I'm glad I'm not the only one. Like I said everything was functional I just thought the screen took a nose dive on me. I'll blast sammy's twitter also.
I've had the same strange red shade. Thought maybe it was a hardware problem; glad to see it wasn't just me.
I've had another weird screen mode issue - "safe mode." No idea what this meant, but didn't notice any limitations. Just had a little shaded rectangle at the bottom left of the screen no matter what I did. Had to restart the phone to make it go away.
I've also had a warning that I was overheating the battery by flying through Manhattan in Google Earth with 3D rendering turned on. Not a bug - just didn't think it would be possible to pull that off when the phone is in an environment of standard room temperature.
See the attached screenshots.
I got a refurb S3 through a GeekSquad Black Tie warranty for a cracked screen. Since I had my initial S3 for about a year and LOVED how it worked since day 1, I never rooted it or put any aftermarket ROMs on it. I'd had my phone "just the way I like it" and ran my business on it so I didn't want to have ANY issues. I tried about 20 different ROMs on my Epic4G over the previous 2 years and LOVED the flexibility, so that tells you how much I liked the S3 stock.
When I got my refurb phone, I instantly rooted and put the newest LiquidSmooth on it since I was starting from scratch anyway. After a couple hours, I noticed that my data was TERRIBLE (all I ever got was "1x" unless wifi was connected... and I have a beautiful shiny new 4G tower about 1000 feet from my house) and that my battery would stay frozen at 100% until it would just die. I have since flashed back to Stock (rooted) and the data problem seems to have taken care of itself, but the battery still never drains.
I feel like an absolute idiot for not verifying full functionality of the phone before I flashed it, but is it likely that the phone is bad?
I never "charge" my phone (and never have with this phone). I have 2 identical batteries that I charge on a battery charger that I've been cycling evenly since the day I bought it. Am I missing a key step for calibrating the batteries with the new phone?
Sorry if this is a repeat n00b post, but after about 10 minutes of Googling, I got nothing.
FYI, I tried the Battery Calibration app from the market, but it didn't seem to do anything.
Thanks in advance!
Question go in Q&A not general.
But your saying that you run the phone all day and the battery can die but the phone reads full 100% all the time?
Sent from the future via Tapatalk 4
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNM
Ah, I hadn't seen the question, just the fact that it was moved.
Yes! The battery says it's 100% all the time until it dies. It did this with LiquidSmooth and after I went back to stock, Since the phone isn't aware that it's about to die, it just shuts off without going through the chime/vibrate/shutdown process and it can go unnoticed for quite some time if I'm working.
Any ideas?
{
"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"
}
Flash it back to stock and take it back.
Sent from the future via Tapatalk 4
edfunkycold said:
Flash it back to stock and take it back.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Agreed. I would triangle away it (to get rid of flash counters) then Odin back to stock and take it back.
------------------------
Sprint Galaxy S3
Need Help? PM
Hit the "Thanks" button if I helped!
Is it even possible that it's a hardware issue? The fact that it's a refurb isn't alarming at all? I flashed it back to the stock rom and then tried a different kernel after a couple days (as far as I can tell).
I only say this because it takes a day or 2 to get the phone "just how I like it" and get all my stuff copied back over.
Not being the super-savvy user, where are the stock sprint Odin files? I installed the stock rom (clearly the wrong one) through CWM.
Thanks again.
Exactly why I said flash it back to stock triangle away to 0 and take it back. There's something wrong with the device itself.
here you can flash this and it does it all in one shot returns the stock rom, triangle away and stock recovery. http://forum.xda-developers.com/showthread.php?p=31981341 and you do it all from custom recovery.
Sent from the future via Tapatalk 4
edfunkycold said:
Exactly why I said flash it back to stock triangle away to 0 and take it back. There's something wrong with the device itself.
here you can flash this and it does it all in one shot returns the stock rom, triangle away and stock recovery. http://forum.xda-developers.com/showthread.php?p=31981341 and you do it all from custom recovery.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Thanks for pointing me in the direction of the proper link. Just got the ball rolling on another replacement through Best Buy, but will certainly try this now!
Ive had two refurbs from Best Buy and both of them have rebooted like crazy and done all kinds of other odd things. Im on my second one now.. picked it up last night, its going back today.
So for awhile now my battery percentage has been acting funny. The majority of the time, it displays 0% regardless of the actual charge. Sometimes it will display as the real charge but then it will remain displaying that level even after the charge has dropped. I have tried formatting and flashing different roms, it doesn't seem like the ROM is the issue. Currently using one of the CM11 builds from last week. You can see from my screenshot that regardless of being charged it shows 0% across the board for the last 2 days.
{
"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 know what's up with this? My gut is telling me to open up the case and check the battery connection, but I'm wary of cracking my backplate when prying it open. I heard its quite fragile.
CHiSEEN said:
So for awhile now my battery percentage has been acting funny. The majority of the time, it displays 0% regardless of the actual charge. Sometimes it will display as the real charge but then it will remain displaying that level even after the charge has dropped. I have tried formatting and flashing different roms, it doesn't seem like the ROM is the issue. Currently using one of the CM11 builds from last week. You can see from my screenshot that regardless of being charged it shows 0% across the board for the last 2 days.
Anyone know what's up with this? My gut is telling me to open up the case and check the battery connection, but I'm wary of cracking my backplate when prying it open. I heard its quite fragile.
Click to expand...
Click to collapse
Sometimes after flashing a ROM the battery stats will act weird. Charge to 100% and use the battery calibration app and you should be back to normal.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Thanks I'll try that. I've never had to recalibrate my battery after flashing with any of my other devices. Hopefully this fixes it!
Sent from my Nexus 5 using Tapatalk
CHiSEEN said:
Thanks I'll try that. I've never had to recalibrate my battery after flashing with any of my other devices. Hopefully this fixes it!
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Doesn't seem like the calibration app is doing anything, it thinks the charge is at 0% as well. Also when I boot into recovery (TWRP), there is no battery charge displayed. On my phone it displays the charge next to the time.
so glad to have come across your msg because I've been having the same issue for the past week.
I owed a Nexus 7 2013 unrooted which I'm running with the latest version 4.4.2.
I've been googling all weekend and came across several msg on the issue.
My issue is that tablet been shutting off at 40% as if my tablet is seen 0%. Just before it shut down a msg appear saying low battery and the tablet shut off but problem is the per engage show 40% and this started since this past weekend.
I've try to recharge my tablet by closing it and charging it to no avail. I also read on different board that those app calibrate a myth and does nothing to solve the issue. The only thing I haven't done is factory rest my system because again I've read that the issue still persisting.
Also each time that I'm charging my tablet I notice that it stay a long time on 100% but the moment it reach 40% it shut down as if is 0%.
I'm hoping other users can come by and confirm if they experiencing the same issue.