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.
Related
Hi all. I seem to have the same recuuring issue at least twice a day with my kaiser.
For no apparant reason it keeps freezing on me, and each time always displays the same fuzzy graphics on the title bar (see attachment).
Has anybody come accross this issue? What shall I do?
Thanks in advance.
new rom =\...master reset..idk
Novice Gadget Boy said:
Hi all. I seem to have the same recuuring issue at least twice a day with my kaiser.
For no apparant reason it keeps freezing on me, and each time always displays the same fuzzy graphics on the title bar (see attachment).
Has anybody come accross this issue? What shall I do?
Thanks in advance.
Click to expand...
Click to collapse
Do you have a custom rom or a stock rom?
What rom are you using?
What radio are you using?
Can you tell us the available memory you have?
Do you have a task manager installed, and are you making sure everything is closed prior to opening new programs?
That information will be helpful in figuring out what's going on. Let us know, thanks! =)
If you don't have one of the newer custom roms, you're pretty much guaranteed to get an answer of "install hardspl / new radio / rom".
If you have a stock rom from HTC... you're gonna hear "reflash the phone with the stock rom, and if it still does it.. return the phone, or flash it with a custom one".
How much warranty do you have left?
Can you also give us a list of what programs you have installed, and which ones are usually running?
Pictures part 1
Thanks for the quick response. There are a lot of questions so i took a bunch of screen shots. Hope this helps. Let me know if you need anymore detail.
See second post as i am unable to post all pics in one post.
Thankyou
Pictures part 2
I am also running battibar in the background.
Well, from what i gather from the screenshots you posted everything should be working fine. There's no reason it should be freezing up, unless there is some sort of conflict, or corrupt program.
Have you noticed that it happens after opening a certain program, or is it really random?
Oh, I take it that's a stock rom right? You never flashed the phone, you just installed individual cab files, right?
nimda0 said:
.....
....Have you noticed that it happens after opening a certain program, or is it really random?
Click to expand...
Click to collapse
It seems to be random but then on the other hand ive noticed that it usually happens when its been sitting on the charger and idle (for example, i'll pop it on the charger before bed, and when i wake up in the morning its frozen). Also it happens at work when its connected to my pc via activesync and after i havent been doing anything for a while.
nimda0 said:
Oh, I take it that's a stock rom right? You never flashed the phone, you just installed individual cab files, right?
Click to expand...
Click to collapse
Yes, thats correct.
Novice Gadget Boy said:
It seems to be random but then on the other hand ive noticed that it usually happens when its been sitting on the charger and idle (for example, i'll pop it on the charger before bed, and when i wake up in the morning its frozen). Also it happens at work when its connected to my pc via activesync and after i havent been doing anything for a while.
Click to expand...
Click to collapse
Well... it could be overheating. If that's the case it's gotta go back. How much warranty do you have left on the phone before it ends?
Novice Gadget Boy said:
Yes, thats correct.
Click to expand...
Click to collapse
Well, just like I posted above. Everything seems fine... and since you are using the stock rom you only have a few choices. You can start uninstalling programs 1 by 1... (noting which ones you uninstall so you can put them back on). Go 1/2 a day, and see if you still have the problem after uninstalling each program. That will help narrow down the theory about corrupt programs or conflicts.
Another option, is reloading the stock rom from HTC... and don't install anything. See how that works for a day... if it's fine, then you can start installing programs.... then if the problem occurs, you know it's got to be something with one of the program you've put on there.
Then you could always just uninstall everything, reset everything, and send it back and get a new phone.... but if it's the software causing the issue, and you put the same software back on the new phone.. you'll just be right back in the same situation again.
If you have warranty time left, i'd uninstall everything, and demand a new phone because of teh issues you are having. Onec you get it, then i'd flash with a custom rom... just make sure you do it right. =)
EDIT: Hell even if you don't have any warranty left, i'd STILL flash with a custom rom. I can't even begin to tell you how much better my phone runs now that it's flashed compared to before. I was using the stock ROM before from HTC, i had some issues... it was a bit laggy... so i reflashed with the stock rom, limited the software i put on it.. etc. etc.... still ran like dog piss... so i flashed, and well..... you get the picture. It's awesome now.
nimda0 said:
Well... it could be overheating. If that's the case it's gotta go back. How much warranty do you have left on the phone before it ends?
Click to expand...
Click to collapse
10 months. But i dont feel any heat whatsoever, and the other day i was using it at work all day connected via activesync and it didnt freeze up. its only when i leave it idle on the charger.... Last weekend i kept getting messages from friends all during the night while it was on the charger (i was reading messages) and it didnt freeze.
So if it's sitting still for a long time without activity.. it freezes. Hmm... well i could give you a dozen things to try, but they'd just be bandaid fixes anyway. If it's freezing something isnt right.
Read my first post on page 2 of this thread you started and that should give you your options. FLASH!!
Why my LG Optimus 2X freezes and/or reboot?
Most of us have the same problem, we are trying to find a solution. In the meanwhile we can solve only removing battery.
Is it related to baseband version?
It does not seem related to baseband version. The problem is present in last baseband versione too:
1035.21_210110405
FRG83G
V10b
Is it related to ROM Version?
Apparently it happens on both stock and custom ROMS
I read that it is due to wall charger problem
Some of us have the same problem recharging both from USB PC and Wall Charger
I read this is due to overheat problem
Some of us still have the problem in standby mode with battery under 25° C.
LG told me to ask for a replacement
Some of us did it and had the same issue on the replaced phone.
I read it is due to hidden menu/car navigation/ecc. ecc.
There are no prooves about it.
Could it be a ROOT problem?
No. Same thing happens on both rooted and original phones.
I got it. It's a SD problem
Some of us has this problem both with or without SD card
So it's a HW problem
We are not sure about it. Most of us (me too) think this is a SW related issue. Some other thinks about a HW one.
Anyway it looks like a Nvidia/Tegra related problem.
It happens on Motorola Atrix too:
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
So: what can I do?
Follow this thread and partecipate
Try to install latest version v10b and do a full reset.
Try to uninstall the "Any cut" application.
Try removing your SD.
NOTE: These are temporary solutions while we wait to understand something more.
Nothing else?
Sure, you can add informations here to keep updated the FAQs.
What about contacting LG?
It looks like something is moving and a new update will be released soon:
http://translate.google.com/transla...alligevel-problemer-med-optimus-2x,lid.15324/
Hey, new V10C is available. Does this solve?
Not sure yet. Some of us still have problems, but some others solved with this upgrade.
How can I help?
You can sign this petition on line
http://www.petitiononline.com/LGO2XPrb/petition.html
Last updated: Tue 7th July 2011
Mine has now shut down 3 times while i was in a call, battery pull on each occasion to rectify the problem
Added in the first question that pulling off the battery temporary solves.
1 week ago I do faced 2 time reboot each after receive sms during standby mood.
Dont know what happen.
Later I remember the reboot problem started after I had installed "Any cut" sw and started to activate the hidden menu.
Then I uninstall it and now haven facing any reboot no more.
Already 1 week pass and no reboot at all. I also never restart my O2X yet and seem everything is OK, no lag or etc on the system.
Hope this help.
Was using the original lg rom only for a good day and had one shutdown. Switched to custom rom and didnt have a reboot or shutdown yet in over a week. Appears to be software related.
Sent from my LG-P990 using XDA App
Useful topic, thanks!
My experience in 15 days of use.
with stock rom V10a and external sd:
- 1 time screen locked black in a warm day during standby
with stock rom V10a without external sd:
- many times screen locked black just after a notification (almost always after sms incoming notification)
with official rom V10b without hard reset and without external sd:
- 1 time reboot after pressing power button to exit from standby
- 2 times screen locked black the day after I've changed the useragent setting from the hiddenmenu and installed "AutomateIt" app
with official rom V10b after a hard reset 2 days ago and without external sd:
- no problem till now (2 days of use)
All the time I used both original charger (at home) and a generic usb adapter with an output current of 1mA (at office).
This is the sort of stuff that should be sent to LG to deal with. Not the idiots at call centres but the people who made the phone and get them to work on it.
Problem with these phone guys, they make a phone and then just stick out to the salesman and then when things like this happen to everyone we get no support or real contact.
It's always send it for repair. The phones are like a month old and that is really a valid response?
Time LG were held accountable (as well as other company's)
Ok, added some "Possible solutions"
Good thread, will hopefully cut down on some of the idle speculation that has been going on!
I believe that it is a software bug, namely in Nvidia's cpufreq-dvfsd driver. I saw this process misbehaving when doing a 'top' command via an ADB shell after it froze, and I'm not the only person to have witnessed that. I've posted that info over at MoDaCo.
As kholk is the only person other than Paul I know around here who might be familiar with a Linux kernel, I've asked him to take a look. Not sure what will come of that, if anything.
And just to add fuel to my argument that this is a Tegra/Nvidia issue, and *not* necessarily an LG one, check this out (from Moto Atrix forums):
http://forum.xda-developers.com/showthread.php?t=969974
http://forum.xda-developers.com/showthread.php?t=1009510
Read from the postings that, for charger-specific reboot/lockup problem, it might be better charging from a computer USB port or a charger with lower current output (I think someone is using as low as 350mA).
Fyi, I've never had AnyCut installed and I've had these problems.
Yup, we do not have still found THE cause, but some events.
We are trying to understand if they are related to the issue.
I am reporting infos from the other thread and from this one to help people ti find a partial solution.
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
follo said:
Very interesting withoutwings
A problem related to tegra system could explain why LG can't solve anything?
Checking all of the messages I can see that the problem is one ( phone locking/restart) but the symptoms are very different and almost always unrepeatable.
Is also strange that many people have a lot of apparently casual restart/lock and many other people have no problems. If a part of source code is corrupted I think the problem should occurs for all the phone.
Click to expand...
Click to collapse
Not necessarily. In embedded/real-time systems, timing is crucial and in some components varies according to manufacture tolerances, heat, etc. Also everybody's phone has different apps and they do things at different times so you can't say that everybody's phone is just "the same" as everyone else's.
And this bug could well be one that only happens for some very specific condition that the original developer didn't forsee when he wrote that code or tested it. But the law of chance means that so many of us are seeing it - some more than others, and some days worse than other days.
So this would explain why people think that doing something like switching launcher or taking out an SD card might be solving or making the problem worse, because every action can and does change the likelihood of this specific condition occurring by changing how the phone behaves overall, workload, sleep time, etc etc. And why all these "solutions" that people are posting are so random and unrelated but each person is convinced that theirs is the one that works!
Basically, we need more evidence from logs to see what is really going on...
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
mikeyd85 said:
Fyi, I've never had AnyCut installed and I've had these problems.
Click to expand...
Click to collapse
Im not an expert, but its work for me. I will keep you all updated if reboot happen again.
Edit: just having my FB hang in 15 second and force to close. This definately due to sw problem.
Sent from my LG-P990 using XDA App
i will believe only when i will see one
spawndk said:
LG Denmark has just announced that they have acknowledged the problems and found a fix for it - they are currently sending out an update to correct it as we speak
Should be available OTA soon (how soon depends on each carrier)
http://www.mobilsiden.dk/nyheder/lg-alligevel-problemer-med-optimus-2x,lid.15324/
Click to expand...
Click to collapse
they said that gingerbread update will be on 18 april to and didnt
They said jun/jul. Check out dk site.
lmerega said:
They said jun/jul. Check out dk site.
Click to expand...
Click to collapse
Well thats the most realistic schedule
Hi All
New to the forum.
I did search this topic but didn't find anything finite.
I have had my Note for 3 weeks now.
In that time there has been 2 occasions in which my phone seems to have shut down while asleep.
There was a brief mention in another topic about it being the TWlauncher or an SD card problem.
I'm just really looking for any advice as to whether there is any settings i could change to stop this happening.
Thanks
Edit:
I am on Stock Rom 2.3.6
Do you have installed any anti virus apps?
What apps do you have installed?
Does it shut down when it's in your pocket or just leaving it alone on the table?
Edit:
Maybe you can upload a logcat output?
I have the same problem. But I do not remember what the phone was doing at the time. But I will be back if this happens again .
I had that kind of problem with an HTC Desire some time ago and HTC changed the motherboard , problem was solved.
I had this problem with my Galaxy Note but I was never able to locate the cause because it also happens on a stock firmware, There were a couple of similar posts before but they were never solved, same deal at a local forum a few people had the issue custom ROM or stock. When I started to use RevoNote HD with V3 I think these 'Sleep of deaths' stopped AFAIK.
Army92 said:
Do you have installed any anti virus apps?
What apps do you have installed?
Does it shut down when it's in your pocket or just leaving it alone on the table?
Edit:
Maybe you can upload a logcat output?
Click to expand...
Click to collapse
- I do have antivirus installed (AVG)
- I have many apps installed (the list would be too big to put here)
- It shut down whilst on the table
- Sorry but i am not aware how to view a logcat output
Well, I read in a german forum that anti virus programs can cause those shutdowns/reboots. I personally don't believe this but you can try to uninstall it.
You can find logcat here:
https://market.android.com/details?id=com.nolanlawson.logcat&feature=search_result&hl=en
Just install it and let it run. Wait for the problem to occur and then reopen this app, save the log and put it up here.
It also can be "just" a black screen.
So that the phone is awake but the screen is black, so it seems like it's down.
It can help to push the power button again.
(For example this problem sometimes occurs at CM9.)
Thanks for the help.
I have download CatLog. Fingers crossed that i wont have to use it
I had read about the black screen problem and that it could be linked to a lock screen issue so I have downloaded WidgetLocker as an alternative to see if that makes any difference (I don't hold too much hope for this as it is only ever running on top of the touchwiz lockscreen but i may aswell try)
i just got my note a few weeks ago and have been suffering this problem as well. it has happened twice now where the note has switched itself off, and my morning alarm has not gone off! which is quite tragic as i rely on it to get to work.
i wonder if this is a software or a hardware problem...
any other owners facing the same problem?
I've had my Note around three weeks and in the first week I had this happen to me twice. I cannot say what caused it (I'm on Stock Rom), as I went a bit app happy and downloaded all sorts of apps when I first got it. After the first week I cleaned up a lot of the apps (Which included AVG, GoLauncher) and I've only had it happen one time since.
I was using the app "My Country" or "Airport City" and I think it was being slow, so spammed it with commands - causing it to reboot. Which is probably unrelated to the previous problems, I have however looked into CatLog - so if it happens again, I will post some details up here :]
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
Background info: I've had my Xperia Z1 only for two to three weeks now. I've been enjoying every part of it, but I've come across three particular gripes I have to mention.
First, random app crashes. One time the Album crashes, the other time System crashed. It appears to be random, not based on anything you were or weren't doing at that moment. I don't think I'm the only one with this though.
Secondly, and here's where it gets weird: my on-screen buttons disappeared. I believe I was just closing GTA: San Andreas. Suddenly, the buttons were gone. I could scroll through the app drawer perfectly, still. That's the odd thing. I should've taken a screenshot if I realised this earlier. I will next time it happens, so let's hope I don't have to. After a while, the phone froze and I decided to reset it, after which everything returned to normal. I guess that's one part where hardware buttons beat software - they don't magically disappear (I hope..).
Lastly, I opened the camera and it looked like it lagged. I pressed the Home button twice or thrice, but then the entire device froze and it kept vibrating like hell! I don't particularly enjoy 5" vibrating devices so I decided to reset it as quickly as possible. No way that could've been good for the device.
Have you experienced one of the last two issues I've had? Or have you had something similar yet different?
Let me know below!
i
Hermantje said:
Background info: I've had my Xperia Z1 only for two to three weeks now. I've been enjoying every part of it, but I've come across three particular gripes I have to mention.
First, random app crashes. One time the Album crashes, the other time System crashed. It appears to be random, not based on anything you were or weren't doing at that moment. I don't think I'm the only one with this though.
Secondly, and here's where it gets weird: my on-screen buttons disappeared. I believe I was just closing GTA: San Andreas. Suddenly, the buttons were gone. I could scroll through the app drawer perfectly, still. That's the odd thing. I should've taken a screenshot if I realised this earlier. I will next time it happens, so let's hope I don't have to. After a while, the phone froze and I decided to reset it, after which everything returned to normal. I guess that's one part where hardware buttons beat software - they don't magically disappear (I hope..).
Lastly, I opened the camera and it looked like it lagged. I pressed the Home button twice or thrice, but then the entire device froze and it kept vibrating like hell! I don't particularly enjoy 5" vibrating devices so I decided to reset it as quickly as possible. No way that could've been good for the device.
Have you experienced one of the last two issues I've had? Or have you had something similar yet different?
Let me know below!
Click to expand...
Click to collapse
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
x102x96x said:
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
Click to expand...
Click to collapse
I'm sorry, what?
It's pretty important to not lose the three main on-screen buttons, not to mention having a device that doesn't vibrate like you-know-what.
What would repairing the firmware do? The phone is still new. There couldn't be anything wrong with the firmware, not solvable by flashing the same firmware over it again, I reckon.
x102x96x said:
these are not important problem
>> repair ur phone firmware by PCcompanion
:good:
Click to expand...
Click to collapse
That's not an answer, even a solution tho. Please be friendly, respect the other.
Sent from my C6903 using Tapatalk
i
Hermantje said:
I'm sorry, what?
It's pretty important to not lose the three main on-screen buttons, not to mention having a device that doesn't vibrate like you-know-what.
What would repairing the firmware do? The phone is still new. There couldn't be anything wrong with the firmware, not solvable by flashing the same firmware over it again, I reckon.
Click to expand...
Click to collapse
yeah these are problems and easily can be solved
by PC companion.
even more issue can appear on new phone.
these are bugs on ur ROM
when u repair firmware, PC companion will download latest firmware (available for ur region) and install it on ur phone.
That can solve ur problem.
-
if repairing by PCC didn't help u should download Flash-Tool for Xperia & firmware of another region and flash it.
u can find useful information about it here.
Source
:good:
omegahanggara said:
That's not an answer, even a solution tho. Please be friendly, respect the other.
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try repair is really the first thing to do with ROM dependent error, so there is nothing wrong with the answer.
harfot said:
Try repair is really the first thing to do with ROM dependent error, so there is nothing wrong with the answer.
Click to expand...
Click to collapse
How can this be a ROM dependent error when I just had my Xperia Z1 for a couple of weeks and updated to official Android 4.3 Jelly Bean through an Over The Air update? My Android firmware is as official and up-to-date as it gets right now.
EDIT: Actually, I wasn't even asking for a solution. I was purely wondering if anyone else had these specific issues as well.
Hermantje said:
How can this be a ROM dependent error when I just had my Xperia Z1 for a couple of weeks and updated to official Android 4.3 Jelly Bean through an Over The Air update? My Android firmware is as official and up-to-date as it gets right now.
EDIT: Actually, I wasn't even asking for a solution. I was purely wondering if anyone else had these specific issues as well.
Click to expand...
Click to collapse
Because any update (especially an OTA) might fail and because these errors (mentioned, i think, for the first time here) are ROM dependent.
So first thing I would do is trying the repair.
I'm aware that you only asked for similarities, but as the are annoying errors, we just wanted to help with a possible solution.
Are you running a 4.3 stock ROM?
Do you use bluetooth/have it turned on?
If yes to both, it is a bug in the 4.3 roms related to bluetooth. Only solution I am aware of is to restart the phone whenever it happens and if you can leave bluetooth off
footyfanatic said:
Are you running a 4.3 stock ROM?
Do you use bluetooth/have it turned on?
If yes to both, it is a bug in the 4.3 roms related to bluetooth. Only solution I am aware of is to restart the phone whenever it happens and if you can leave bluetooth off
Click to expand...
Click to collapse
Yes & no.
I never use bluetooth actually.