Related
Guys, I had someone here talk me through rooting my nexus one with froyo and I'm running into some problems but I didn't know if it had something to do with rooting it or not and the reason is, I got it rooted the same day I received it so I hadn't tried those functions before I got it rooted.
I got it rooted so I could buy this program that makes the fonts larger and it required a rooted phone.
Well, today I was going to try to use it as a hot spot or wifi router and when I tried to enable it, it just says error.
Also, when trying to call and talk to people today, they could barely hear me and I had a hard time hearing them (not sure if this was temporary or not because later, although in a different area, it sounded fine).
When trying to reply to some e mail (online email/godaddy) when I clicked where the text/body goes, I could not type anything 'cause the keyboard wouldn't come up. If I clicked in the email or subject areas, the keyboard came up but not in the body text area.
Any ideas?
I guess I could reset it to default settings to see what happens but it took almost two hours to get it rooted so I really would like to avoid that.
Thanks
George
This should be in Q&A!
Not dev related.
To solve your problem:
looks like a bad boot.img for me.
I always had "Activiating Wifi"... "Error" with bad boot.img.
MOD: move to Q&A
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
guiri_too said:
Thanks. I wasn't sure about where to put it and thought there was possibly bigger chance of a reply here. Thanks for moving it.
So, considering I have NO idea what I'm doing and someone else helped me, is the answer to my next question short and simple or not?
What do I do about it?
No, I have no idea what a boot image is.
Should I try to get hold of the guy who helped me root it or see if someone else can talk me though how to fix it?
Thanks
George
Click to expand...
Click to collapse
Im not a Mod, I did not move your thread.
The boot.img is part of a ROM.
But I don't know what ROM you're using, what build (FRF50/72/85B/91) nor the kernel etc.
I cannot tell you more right now.
Just try a new rooter update.zip because yours might have broke your WiFi.
See Cyanogen's or re-flash a pre-rooted rom.
Actually, I noticed it wasn't moved yet but anyway, I think I have the 72 but still, not sure, I'll have to investigate 'cause I like this phone and I would LIKE it to work for me. Especially since I can apparently use it on tmobile and att.
THanks
The hunt continues
George
no rooting in general does not harm your phone or cause problems in any way. however it is possible to mess something up, maybe install something or screw up settings or similar that could cause problems. you can always flash back to factory ROM, or hard reset, to get your phone working again.
even better, since you are rooted, you should be creating nand backups. and anytime something goes wrong, you restore to a working nand backup to a state that you know your phone was working good.
Yeah, now I have to figure out how to do this but thanks for the replies
George
I got my Galaxy tab yesterday and, incidentally, I'm TOTALLY loving it!!!! Anyway, I rooted it (using z4root) so that I could use Titanium backup and regularly backup my apps/data.
I didn't try recording video before I rooted, so I don't know if rooting has caused the problem, but it's been suggested that it may have done.
Basically, when I start to record video I get about 5 seconds and the app force closes. I don't have any problem taking pictures - just video.
Has anyone come across this issue or know of anything that may explain or (preferably) help solve it??
It's not the end of the world if I can never use it to record video, but I'd like to be able to if possible.
Thanks guys.
Edit: Problem solved! See this post for the answer
johncmolyneux said:
I got my Galaxy tab yesterday and, incidentally, I'm TOTALLY loving it!!!! Anyway, I rooted it (using z4root) so that I could use Titanium backup and regularly backup my apps/data.
I didn't try recording video before I rooted, so I don't know if rooting has caused the problem, but it's been suggested that it may have done.
Basically, when I start to record video I get about 5 seconds and the app force closes. I don't have any problem taking pictures - just video.
Has anyone come across this issue or know of anything that may explain or (preferably) help solve it??
It's not the end of the world if I can never use it to record video, but I'd like to be able to if possible.
Thanks guys.
Click to expand...
Click to collapse
Hi, firstly congrats on your new Galaxy Tab, welcome here
I have never faced these problems on a stock unrooted ROM (which i am on) and have never rooted my TAB before. Perhaps try flashing a different ROM and see how it goes. Or since your TAB is fairly new and has few customizations you may want to try a master clear?
Cheers
Thanks for the congrats. It's a BEAST and I love it
I did do a hard reset, but I was dubious as to whether or not it had actually done a hard reset as it seemed to retain some of my settings. It didn't solve my problem, either way.
I don't want to go down the custom ROM route for now as I'm happy with the stock ROM (after replacing the launcher with Launcher Pro).
I know it's a clutch at straws, but I'm hoping that someone knows of a fix for this problem. If someone can tell me how to do a 100% factory reset then I'd happily give it a go, but the method I used was not successful (power off and then hold volume up and power on - follow the menu to factory reset).
Hi, do you (try to) record to your GT SSD or to SD card?
I had the same problem first due to a very bad class 2 microSD card.
Video recording crashing, but only after 2 to 5 seconds recording.
Formating it didn't fix the problem, replacing it did. Maybe a hint.
Also try to switch to standard quality, no audio settings.
And try another free video capture app.
johncmolyneux said:
Thanks for the congrats. It's a BEAST and I love it
I did do a hard reset, but I was dubious as to whether or not it had actually done a hard reset as it seemed to retain some of my settings. It didn't solve my problem, either way.
I don't want to go down the custom ROM route for now as I'm happy with the stock ROM (after replacing the launcher with Launcher Pro).
I know it's a clutch at straws, but I'm hoping that someone knows of a fix for this problem. If someone can tell me how to do a 100% factory reset then I'd happily give it a go, but the method I used was not successful (power off and then hold volume up and power on - follow the menu to factory reset).
Click to expand...
Click to collapse
yeh it's awesome!
I think you could refer to the user manual it nay teach you how to hard reset? i don't know how to do that either :S
Or like the above member stated,the memory card may be an issue... what memory card are you on? i'm on the default Samsung 16GB (Class 6)? card - no issues here.
johncmolyneux said:
I know it's a clutch at straws, but I'm hoping that someone knows of a fix for this problem. If someone can tell me how to do a 100% factory reset then I'd happily give it a go, but the method I used was not successful (power off and then hold volume up and power on - follow the menu to factory reset).
Click to expand...
Click to collapse
Full Reset :
*2767*3855# - from the dialer
no issue here = micro sd 16GB cass 2
try to use OneClickRoot - for MAC or SuperOneClickv1.7-ShortFuse for Windows next time ! works for me better!
Thanks for the comments and suggestions guys, and thanks for the alternative method of factory resetting, ovigt71.
Unfortunately, I was still rooted after doing that. Seems strange that the rooting is persisting after a factory reset, but that's what's happening!
Anyway, unless someone comes up with a brainwave I'm just gonna live with the fact that I can't record video. It's not a major biggie as I have a HD2 which has a better camera anyway, so I'll always use that. I just like everything to work the way it should.
johncmolyneux said:
Thanks for the comments and suggestions guys, and thanks for the alternative method of factory resetting, ovigt71.
Unfortunately, I was still rooted after doing that. Seems strange that the rooting is persisting after a factory reset, but that's what's happening!
Anyway, unless someone comes up with a brainwave I'm just gonna live with the fact that I can't record video. It's not a major biggie as I have a HD2 which has a better camera anyway, so I'll always use that. I just like everything to work the way it should.
Click to expand...
Click to collapse
...hm...most probably you got a wrong version of Z4 root....but, in my personal opinion, better reflash with PIT file the firmware (if you like using the stock, then you root with SuperOneClickv1.7-ShortFuse and everything should go back to normal. or better you follow the guide and install Overcome, which is already prerooted! hope it help!
ovigt71 said:
...hm...most probably you got a wrong version of Z4 root....but, in my personal opinion, better reflash with PIT file the firmware (if you like using the stock, then you root with SuperOneClickv1.7-ShortFuse and everything should go back to normal. or better you follow the guide and install Overcome, which is already prerooted! hope it help!
Click to expand...
Click to collapse
Nah, I'm gonna stick with the stock ROM for now. It's only a few days old so I'm not interested in flashing anything to it. And I got z4root off here ages ago. It's sitting on Dropbox with a bunch of other apk files that I use on new devices (I was changing ROMs on my HD2 at an alarming rate at one point!)
Thanks for the help.
johncmolyneux said:
Nah, I'm gonna stick with the stock ROM for now. It's only a few days old so I'm not interested in flashing anything to it. And I got z4root off here ages ago. It's sitting on Dropbox with a bunch of other apk files that I use on new devices (I was changing ROMs on my HD2 at an alarming rate at one point!)
Thanks for the help.
Click to expand...
Click to collapse
mate, if i were you, you might as well get the problem sorted now, before it's too late. You may aswell try unrooting it if you can, test if the video works. if it doesn't take it back to your retailer, tell them your problem, and the may replace your TAB with a new one. You may aswell get it done early rather than waiting a while and they won't do anything for you ad suspect it was self invoked. I personally do not face any problems but as i say i have a unrooted tab + stock 16gb sd card and it works fine.
good luck, hope u get it sorted.
johncmolyneux said:
Nah, I'm gonna stick with the stock ROM for now. It's only a few days old so I'm not interested in flashing anything to it. And I got z4root off here ages ago. It's sitting on Dropbox with a bunch of other apk files that I use on new devices (I was changing ROMs on my HD2 at an alarming rate at one point!)
Thanks for the help.
Click to expand...
Click to collapse
[email protected] is correct! as long as you have the Tab under warranty you should try to make it work.....until is not yo late!
Yeah, that's good advice, and probably what I'd say to someone in my position. I'll get in touch with Orange and take it from there.
Cheers guys.
Problem solved!!!
There was nothing wrong. Rooting hadn't caused the problem, and there's nothing wrong with the tab (thankfully). I'd set the lcd density to 180 because I like to have lots of small icons, rather than just a few big ones. As soon as I restored my backup of build.prop I could record video.
Seems the cam app doesn't like different lcd density settings.
I can live with that - at least it's not the tab.
Edit: In case anyone finds this and wonders, I just set the lcd density to 200 and video recording still works. Things aren't that much bigger than at 180, so I can live with that.
Edit: It works at 190. I've not tried the other 9 values between 180 and 190 though. 190 looks great
johncmolyneux said:
Problem solved!!!
There was nothing wrong. Rooting hadn't caused the problem, and there's nothing wrong with the tab (thankfully). I'd set the lcd density to 180 because I like to have lots of small icons, rather than just a few big ones. As soon as I restored my backup of build.prop I could record video.
Seems the cam app doesn't like different lcd density settings.
I can live with that - at least it's not the tab.
Edit: In case anyone finds this and wonders, I just set the lcd density to 200 and video recording still works. Things aren't that much bigger than at 180, so I can live with that.
Edit: It works at 190. I've not tried the other 9 values between 180 and 190 though. 190 looks great
Click to expand...
Click to collapse
thanks for pointing out the settings glad you got your 'problem' foxed, now you can enjoy the full power of the Galaxy TAB !!
P.S - were your video settings set to saving to the SD cad or internal memory?
At least one person has reported that the camera works at 182 and above, so that might be the number to shoot for if you want to continue.
@johncmolyneux
thanks for the tip! I'm using density at 200....I wasn't think about that! LOL good to know!
olyloh6696 said:
were your video settings set to saving to the SD cad or internal memory?
Click to expand...
Click to collapse
I've tried both, and it makes no difference. This was definitely down to the LCD density setting.
student.driver said:
At least one person has reported that the camera works at 182 and above, so that might be the number to shoot for if you want to continue.
Click to expand...
Click to collapse
Thanks for that. I've got used to it at 190 now, but good to know I can go lower if I fancy it.
ovigt71 said:
@johncmolyneux
thanks for the tip! I'm using density at 200....I wasn't think about that! LOL good to know!
Click to expand...
Click to collapse
Thanks for the thanks - glad it helped mate
At a certain point on my screen, the phone thinks I am touching it.
I dont know how else to explain it but a 'phantom touch'.
Its repetitive and very annoying.
It seemed to start after I flashed some custom ROMS.
I flashed back to stock (2.3.5) in the hopes of it being fixed but it seemed to follow me.
Has anyone had this issue/knows how to fix it?
Thanks
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
dr. xp55 said:
It was completely fine before flashing the custom roms? try re-flashing stock rom, don't root, do factory data wipe from the settings. If its still following you, it might be a hardware issue. and if that's the case, you might need to send it in. It should be covered from the 1 year samsung warranty. make sure you don't have the triangle
Click to expand...
Click to collapse
It seems to have just gone away on its own. Cheers for the help anyway, would have done this if I still had the problem.
It seems to come back when I flash a ROM.
I flashed the German ICS official ROM (which is great btw), and it seems to have come back.
Hopefully, someone can provide me with a solution, perhaps its a corrupt system file?
Still, it goes away when the phone is charging.
Any ideas at all?
I'm not sure if this is helpful, but I faced the same issue when I flashed ParanoidAndroid yesterday. In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive). It was then that these phantom touches started. I set it to 100(max, least sensitive) and I couldn't get the touchscreen to register any touches at all. The Spen worked in both cases, so I just used that to reset it.
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Hi, I think this seems to be the trick.
I was unable to find the code to access the settings menu you described.
However, I installed TouchScreenTune, and that seems to be working for the moment.
Will post my results in a few hours or so.
Thanks
bloodyhippo said:
In Settings>Device settings, there is an option of "screen sensitivity". I set that to 10 (the minimum, ie, the most sensitive)....
Anyhow, I believe that this menu is accessible via a key code on stock roms. I'm not sure of it, but it should be. Look around in the tips and tricks thread, all secret codes for the Note are listed over there. Then just change sensitivity to 20.
Click to expand...
Click to collapse
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
novastorm17 said:
Also, If you are able to remember/get the code that would be great.
I found a list of the codes but none look like they'll be what you mentioned.
Thanks again
Click to expand...
Click to collapse
You're right, I couldn't find one that'd help either. Hmm.
Do you still have the problem?
It hasn't gone away, but I think the frequency at which it occurs has reduced
Any other ideas/any other way to do your previous method?
Cheers
Okay so here is all the information I have.
No matter which ROM I flash, the issue of the random touching continues.
Ive tried without root, and tried a complete reinstall (by formatting all data and storage)
I found a CWM restore I made 6 months ago (long before the issue started). That didnt work either.
Things that DO work:
TouchScreenTune seems to greatly reduce the frequency at which at occurs by decreasing the sensitivity of the screen, however, it makes it harder to use the phone.
Plugging in USB stops it completely, but when its removed, the issue comes back.
I thought since it is following me through different ROMs it is a hardware issue.
Does ANYONE know a fix/heard of this before?
At the moment Ive resorted to using my old IDEOS (oh god) and have begun working towards a warranty rectification.
Thanks anyone who can help
Update from Samsung:
Issue due to motherboard/touchscreen
Cheers for your help
Hi there,
Noticed today when I went to show someone a picture on my phone that all my camera photos are not there anymore. Nobody but myself has had access to the phone and I certainly didn't delete them or transfer them anywhere. Anyone else had this or know why it might have happened??
It's bog stock sim free phone running 4.3.
Also had an issue the other day where I went to have a quick go on Angry Birds to find it was no longer installed. It's been OK since I reinstalled it but don't know how it could suddenly have been uninstalled for no reason.
Cheers
Dazza
Could be a manufacturing defect. How old is the phone? If you just bought it then it probably is. But if its been like a few months maybe it's due to a software defect and you could try doing a wipe.
Good luck and hit me up with a thanks if I helped
Sent from my HTC One using xda app-developers app
I've had it since May.
Doing a wipe and reinstall isn't going to bring my pictures back or tell me what caused them to be deleted which is what I want to find out.
Other than that, the phone works great.
Dazza
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.