Related
Does anyone else have a problem with holding down the power button?
When I hold down the button my Nexus only registers it as pressing it and letting go and usually just turns off the screen. It's quite frustrating when I need to turn off my N1 or set airplane mode, and usually takes half a dozen tries before it actually registers as holding down the button and not just pressing it.
I fear it may be a hardware issue and I will have to return it.
I got the same issue. Not sure if it is soft- or hardware related. Also having problem with waking up. Works well with the track ball so I guess it's the hardware.
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
andythefan said:
I'm really dreading having to send this back to HTC. Everything else on this device has been working normally, but I also have an unlocked bootloader. I'm reluctant to trade it in.
Click to expand...
Click to collapse
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
I will say that I've been using a Desire2Nexus port ROM and it definitely happens more with this ROM than the CM-based ROMs, but that could also be due to the laggy/sluggishness of SenseUI.
I was seeing the same problem in both ROMs of recent generation though. So my gut tells me it's a hardware issue. Flashing to stock and testing it out will be a dead giveaway, though.
HTC has historically been pretty good about replacing known hardware malfunctions. I also bought SquareTrade coverage just in case, though, so I will be getting my money back one way or another.
maxawesome said:
Mine is doing the same thing.
Here's a good test.
Do a nandroid backup, and then flash back to the stock ROM. I haven't done this yet, and am planning to do so this weekend.
If you flash back to stock and the power button works normally, well there you go.
If not, it's a hardware issue.
Click to expand...
Click to collapse
I've wiped and flashed the last stable CM version. The issue persists. Also, it happens when I'm in recovery as well, so I'm afraid it may be a hardware related issue.
Can I still send this in for replacement if the bootloader is unlocked? When I be charged repairs in that regard?
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
LibertyMarine said:
upload it on youtube and post the link.
And something else. Make a factory reset again and then don't install any apps. Does the error also occure?
Click to expand...
Click to collapse
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
anibjoshi said:
Im new to XDA forums and hence the site does not allow me to post URLS. However I have uploaded the video to youtube.
If you put 'HTC One screen problem Aniruddha Joshi ' in the youtube search box, you will find my video.
Im sorry I couldnt think of any other way
I did not install anything out of the ordinary. Just updated the existing google apps and installed facebook, twitter and whatsapp! No crazy apks or unknown apps.
Also, once I factory reset the phone, it starts working perfectly and there is no way to know the time after which it starts giving problems again. Once it was 3 hours, once it was a week.
So I don't have any way to check if some app is causing the problems.
Click to expand...
Click to collapse
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
anibjoshi said:
Hey guys,
I bought an HTC One about 15 days ago. Within 2-3 days of using it, I started getting problems with the display screen. I suppose this problem was seen by few people who owned the HTC One X but I couldnt find any useful solutions in those formums hence im posting here.
This is what happens:
1. Whenever I receive a call, the screen goes black and doesnot turn on until I hang up the call. This effectively makes the device useless as a phone, as I can't see who is calling and also during call I cannot access the screen.
2. Sometimes, there is a delay with the power button. When I press the power button, the touchscreen becomes responsive but the display doesn't turn on.
The problem is, if I factory reset the device, it starts working perfectly again!! Again after about 2 days it starts the same problems.
So I thought it was a software issue and so, I got s-off and installed the GPE Rom on the device. 7 days passed, no problems. On the 8th day, the same problem occured again. And as earlier, factory resetting solved the problem.
Is this a software issue, hardware issue or something else I dont know about?
I have taken a video of the device malfunctioning, but I don't know if I can post it as an attachment.
Thanks in advance!
Click to expand...
Click to collapse
Try flashing a Sense ROM, like ARHD or MaximusHD?
Enviado de meu HTC One usando Tapatalk
LibertyMarine said:
after seeing your video, I am even more confused. I really don't know what could cause this problem. But the fact, that I didn't have this issue and almost no other person too, makes me think about a hardware defect. But the randomness and that it only occures after several days don't support this theory. So the only thing we can do about his is basic troubleshooting.
- 1) Try to flash Cyanogenmod and try this mod for several days
- 2) Try another Rom, for example: Omni Rom
- 3) Try to use a different Kernel for GPE stock.
- 4) Use a RUU that matches for you
Sorry, I don't have any other ideas left! But after this troubleshooting we may get new information or gain some knowledge that allows us to determine the cause of this error more exactly!
Click to expand...
Click to collapse
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
IINexusII said:
well its clearly something youre installing if it is occuring after a few days, a root app which controls your sensor or brightness probably, do you have apps of that nature?
Click to expand...
Click to collapse
No I rooted the device but did not install any root apps...i unrooted the device to install the GPE Rom(not necessary i know, but it seemed like a proper way) and found that it started giving problems immediately. Can non-root regular apps also cause such problems? I had installed only a limited number of apps anyway, updated the pre installed apps, facebook, twitter, whatsapp, some games..thats it..nothing wierd..
Might be a Screen-Off max. frequency issue. Like the phone gets only 500Mhz in sleep mode at maximum. Which is to low for an incoming call. Could you install a app like Android Tuner or Trickster Mod to check your Screen-Off Max frequency. If it`s that low, set it to ~1000Mhz.
anibjoshi said:
The original device shipped with sense Rom. I flashed GPE to check if it was a software fault. But no luck. It gave the same problem although significantly later(about a week after I flashed it).
One more thing, I hope this gives some more information..
One time, I had rooted the device and installed a custom recovery. The phone was then working perfectly for about 4-5 days. and then later when I went ahead and unrooted the device, it immediately started giving problems. So I rooted it again hoping that the problem will go away, but no luck...the problem persisted. So, I had no option than to factory reset again, at which point it started working perfectly again.
This is all so bizarre, I have never seen something like this happen
This is just a theory, but is it possible that there is a problem with the hardware which gets triggered only on certain conditions, like some interrupt, or flag or something like that?
So until those conditions are not met, the device runs perfectly, and when they are, it starts giving issues.
Thats all i can think of as the reason.
Click to expand...
Click to collapse
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
LibertyMarine said:
That is very stange indeed. As I don't know any other causes for this error than:
Underclocked CPU or/and GPU on screen off
Root application that controls the brightness
Hardware issue(But what would cause this???)
I can only advice you:
Since you are S OFF, take a RUU, and follow this guide and ****ing set back your device back to stock! Don't root it! Don't use custom kernels. Don't install any strange apps that may control your display brightness. SERIOUSLY! Don't install an app that controls brighness even if it works on a friends phone! Just don't!
And if you still get this issue: It is a hardware issue! If you followed step by step the instruction and if you did everything I told you to do, it HAS to be a hardware issue! The fact that the error didn't appear on GPE that fast is caused by the lower performance requierement by GPE! So I seriously have doubt that this issue is caused by a hardware defect. But it isn't impossible for sure. I just have the impression that you changed some system files and you didn't know what you were doing. This is NOT against you, but it seems to be a reasonable possibility because a factory doens't reset the /system partiton.
P.S.
I'd be very kind if you hit the thanks button since we, the community, are really trying to help you.
Click to expand...
Click to collapse
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Yup try installing kernel and custom rom.
Remove the case and try ( i know this is stupid thing but can give it a try)
Jvov said:
Agreed, trying following the guide and if it doesn't work make it s-on and send it to HTC for them to give a look.
Sent from my HTC One
Click to expand...
Click to collapse
Thanks for your help buddy! I really appreciate it!
anibjoshi said:
I will definitely follow your guide and try to troubleshoot the problem. I hope its not some hardware defect and I dont have to send the device to HTC. I've heard those guys are poor at customer service
Thanks a lot, you've been a great help!
Btw, I was trying to find that Thanks button since the first day, I just couldn't figure out where it was. I just did.
Thanks again
Click to expand...
Click to collapse
Thanks ! That's awesome and gives so much motivation! If you find out that you have a hardware defect and that you have to send it to HTC, I'll give you some information how to deal with those guys that you get your warranty.
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
No one? I guess this really is a tough one.
Kirbs82 said:
Regarding: Samsung Galaxy S3 Mini GT-I8190 - SIM unlocked version
Hello eveyone.
I'm having one of the strangest problems I've encountered with a phone before and I just can't seem to track down the problem. Please read this thread with an open mind as from what I can tell this is a unique issue that sounds like normal issues.
The main problem is that the phone keeps rebooting. From the get go this sounds like a normal issue with either the battery or power switch but here is the weird part...
It only happens when the phone is fully charged!
IBackground
I have had the phone since release and I have only ever used the stock rom that came with the phone. I don't really use phones much n general except for using it for calls texts and BBC news. I didn't even have a SD Card in it until after the problem started. Everything was running great, I never had any battery problems at all, and then a couple of weeks ago my phone contract expired with Orange and I decided that I would get a SIM only plan with EE.
While waiting for the SIM card to arrive in the post I charged my phone up one day and noticed that I had to power on the device. The phone seemed to power on fine, I could use all features of the phone, but when I turned the screen off for more then 5 or 6 seconds the phone would restart. There would give no indication that it had turned off or that it had powered off in anyway. It would simply just be blank, I'd press the power switch, and it would vibrate once and begin its start up procedure as if it had been turned off completely.
Here is where it gets weird, the phone will keep cycling on its own like this until the battery drains itself through constant reboots until about 85% juice, at which point it begins to operate functionally.
I heard that some people say they had problems with the power switch. I figured that if it was the power switch it then the problem would be consistant and would continue giving me problems when the battery was below 85%. I think I can rule out the power switch as faulty. Naturally I came to the conclusion it must be software, perhaps an APP installed which was incompatible. I tried all sorts of things, regardless I came to the conclusion it needed to be factory reset. Factory reset didn't do anything, still does it. My next thought was Firmware, it must be the firmware that was corrupt. I went through tutorials and rooted my phone, installed recovery software and ended up installing Cyanogenmod 11 (Which looks really beautiful btw, wish I had done that sooner) and buying an SD Card too do so. Still the problem persists! I read that some people had problems with swelling batteries, I replaced the battery completely just incase. £10 wasted, still does it.
At this point I'm starting to get confused. I started thinking perhaps it was the cable providing too much charge to the device, over charging somehow. Tried a different cable and a different power source. Still the poblem persists. I made sure there was no dirt in any of the connectors incase that was causing something. No joy.
So to summerize:
1. Factory Reset
2. Replaced Battery
3. Changed power leads
4. Cleaned device
5. Flashed to completely new firmware
I've completely run out of ideas on what it could be. Why would the phone operate absolutely fine under 85% power? Its just weird! I'd appreciate any help some one could provide me. I've not seen any one else with this problem on the internet. Please let me know what you guys think.
Thanks
Craig.
Click to expand...
Click to collapse
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Sn0wdune said:
Sorry to hear about this man!
I am completely stumped on this one! You've basically done all the basic solutions but to no avail. I had a problem similar to this where my device would reboot randomly, whenever it wanted to and in my case, the solution was to buy a new battery and that actually worked. I've had the battery for almost 2/3 months now and it's still going strong.
Back to your problem, I honestly don't know of a solution. I really wish I could be of help but as I said, you've already tried the basic solutions.
Again, sorry to not be of much help!
Click to expand...
Click to collapse
I think I have the same problem as you did. After suddenly dropping and rebooting, my battery level jumps back up when the phone starts, and again, and again. The phone is functioning normally only when plugged in. I also presume that it is a battery problem, but the fact that the battery level rises back after dropping, makes me wonder.
EDIT: Problem solved with buying a new battery.
Sorry to jump in, just curious, did you solved this? If you do, hope to hear your solution, might help others in future
SGs3n SlimKat9.0(Android-Andi)
I've had rooted HTC devices (Hero, EVO 3D) and then rooted Samsung Galaxy S3, Note 8.0 tablet and Note 4 which was my last device before this one. So this is my first unrooted device basically since I rooted my first Android device and I feel like I have no idea what I'm doing. I looked at my Note8 last night to find it in SAFE MODE. This phone has not been activated because I've been using the free WiFi hotspot on my rooted Note 4 to provide internet to my PS4 because the WiFi in the nursing home I'm temporarily in cuts out a lot and I got the Note8 on 9/15 so I'm assuming I'm going to be in trouble with Sprint when I call about now being in default to see if I can fix that before they charge me every penny I'll have for the next 2 years and cut ties with me forever. I've only ever had Sprint. If anyone can give me any tips on what to say when I call about that it would be appreciated. Anyone know how big of a deal it is to be in default like this for a few months? They never told me I was even in default. I figured it out. They haven't been charging me for the lease, not once.
Anyway, this unactivated Note8 has not been updated at all either. I haven't installed anything in the last couple of days prior to safe mode starting, that I recall. Samsung stock apps are constantly updating though. Can anyone point out the stupid thing that I did or didn't do that probably caused this? And can anyone help me? Please? I'm good with this stuff. Usually. lol
Edit: I forgot to say that in an attempt to fix it, I rebooted the phone more than once. I used the thing that shows up in the notifications to get it out of safe mode and I also just held the power button down and tapped reboot when it popped up. No change. I powered it off then left it off for 2 minutes and powered back on with no change. I have had a major issue with the volume rocker since I got the phone. Like it really never moved. I had to get an app to control the volumes and use Tasker to control the profiles in the app. Once in a while, I could get it to work but then it would act as if I was holding it in which I wasn't. Maybe 2 days before it went into safe mode, I pressed down hard on the volume up button and it snapped. Ever since it would make a sound at random times like the volume button was being pressed even though the phone was just sitting and the screen was usually off at the time. After it went into safe mode, I messed with it enough that the sound stopped and I did get the volume rocker to move in each direction though now that it seems to be in a neutral position I don't want to mess with it at all. I tried to reboot to see if it would come out of safe mode after that but there was no change.
Christina
died4u525 said:
I've had rooted HTC devices (Hero, EVO 3D) and then rooted Samsung Galaxy S3, Note 8.0 tablet and Note 4 which was my last device before this one. So this is my first unrooted device basically since I rooted my first Android device and I feel like I have no idea what I'm doing. I looked at my Note8 last night to find it in SAFE MODE. This phone has not been activated because I've been using the free WiFi hotspot on my rooted Note 4 to provide internet to my PS4 because the WiFi in the nursing home I'm temporarily in cuts out a lot and I got the Note8 on 9/15 so I'm assuming I'm going to be in trouble with Sprint when I call about now being in default to see if I can fix that before they charge me every penny I'll have for the next 2 years and cut ties with me forever. I've only ever had Sprint. If anyone can give me any tips on what to say when I call about that it would be appreciated. Anyone know how big of a deal it is to be in default like this for a few months? They never told me I was even in default. I figured it out. They haven't been charging me for the lease, not once.
Anyway, this unactivated Note8 has not been updated at all either. I haven't installed anything in the last couple of days prior to safe mode starting, that I recall. Samsung stock apps are constantly updating though. Can anyone point out the stupid thing that I did or didn't do that probably caused this? And can anyone help me? Please? I'm good with this stuff. Usually. lol
Edit: I forgot to say that in an attempt to fix it, I rebooted the phone more than once. I used the thing that shows up in the notifications to get it out of safe mode and I also just held the power button down and tapped reboot when it popped up. No change. I powered it off then left it off for 2 minutes and powered back on with no change. I have had a major issue with the volume rocker since I got the phone. Like it really never moved. I had to get an app to control the volumes and use Tasker to control the profiles in the app. Once in a while, I could get it to work but then it would act as if I was holding it in which I wasn't. Maybe 2 days before it went into safe mode, I pressed down hard on the volume up button and it snapped. Ever since it would make a sound at random times like the volume button was being pressed even though the phone was just sitting and the screen was usually off at the time. After it went into safe mode, I messed with it enough that the sound stopped and I did get the volume rocker to move in each direction though now that it seems to be in a neutral position I don't want to mess with it at all. I tried to reboot to see if it would come out of safe mode after that but there was no change.
Christina
Click to expand...
Click to collapse
Okay, so let me get this straight. You got the phone through the Sprint Lease Program, but you never activated the phone? Did you get the insurance for the phone?
Easy fix, if you are within the 14 days of owning it, take it back and get a new one. If you have insurance, file a claim.
Other then that you could see if it boots to download mode and try to flash the firmware for it. Everything will be gone but it should fix the issue.