Related
OK, now I have a problem.
If I turn my xoom off and then on again the touchscreen will not respond to any input, only hardware buttons work.
If I hold volume up and power button to restart, it restarts and everything works OK. I can but it to sleep and wake it up and still everything works. Everything works until I turn it off and on again, then the problem returns and I need to hold volume up and power button to restart it again to get the touch screen working.
I searched the net but didn't find anything similar.
Any ideas?
is it still stock or you rooted / update kernel ?
errevi said:
is it still stock or you rooted / update kernel ?
Click to expand...
Click to collapse
Its complitly stock wifi only Xoom, bought from US about two weeks old.
I tried Factory reset, it didn't change anything.
Strange thing is that volume up and power reset fixes it every time. And it works fine until i turn it off again. What does this volume up and power button command do exactly, soft reset? If soft reset fixes it, it can't be a hardware problem or can it?
If I were you I would return it cuz to me that sounds like a defect with your xoom. But if u messed with it (rooting/unlocking) they won't even touch it.
Motive101 said:
If I were you I would return it cuz to me that sounds like a defect with your xoom. But if u messed with it (rooting/unlocking) they won't even touch it.
Click to expand...
Click to collapse
Like i already said, i haven't messed with it, it's completely stock.
About returning it... The problem is that i'm in Europe and i bought my Xoom from US, so i'm not really excited about sending it back.
Is it somehow possible to install the current android 3.0.1 rom again? Without unlocking and rooting?
I do not know if it works on the xoom but other tablets have a calibration ini file that you can place on the root of your SD card and reboot letting it recalibrate the touch screen? Let me know and I can send that to you?
poisike said:
Like i already said, i haven't messed with it, it's completely stock.
About returning it... The problem is that i'm in Europe and i bought my Xoom from US, so i'm not really excited about sending it back.
Is it somehow possible to install the current android 3.0.1 rom again? Without unlocking and rooting?
Click to expand...
Click to collapse
gysgtusmc said:
I do not know if it works on the xoom but other tablets have a calibration ini file that you can place on the root of your SD card and reboot letting it recalibrate the touch screen? Let me know and I can send that to you?
Click to expand...
Click to collapse
Thanks for trying to help! I'm not sure i want to mess with this yet. I talked to Motorola about my problem and the seemed very interested in my problem, so i will wait and see what they suggest.
Any news from there? I have a similar situation here (malfunctioning touchscreen, and I'm from Europe).
You can read my story here http://forum.xda-developers.com/showthread.php?t=1036009
My malfunctioning is slightly different from yours, but I'm interested in what Motorola says for a problem like this.
Ieracos said:
Any news from there? I have a similar situation here (malfunctioning touchscreen, and I'm from Europe).
You can read my story here http://forum.xda-developers.com/showthread.php?t=1036009
My malfunctioning is slightly different from yours, but I'm interested in what Motorola says for a problem like this.
Click to expand...
Click to collapse
They are still thinking how they can help me, there is no solution yet, I will let you know when I get a solution from them.
And yes, my problem seems different from you. No one have reported anything similar to my problem.
I have seen a few threads similar to your problem.
poisike said:
And yes, my problem seems different from you. No one have reported anything similar to my problem.
I have seen a few threads similar to your problem.
Click to expand...
Click to collapse
Really? I haven't seen anything like my problem in forums, and everyone told me that my problem is "strange" :S
However, just in case, have you thought about how to return the Xoom from Europe to US? Or are you directly talking with Motorola to file a RMA practice? After all, we should have one year of international warranty by Motorola, isn't it?
Ieracos said:
Really? I haven't seen anything like my problem in forums, and everyone told me that my problem is "strange" :S
However, just in case, have you thought about how to return the Xoom from Europe to US? Or are you directly talking with Motorola to file a RMA practice? After all, we should have one year of international warranty by Motorola, isn't it?
Click to expand...
Click to collapse
In fact someone from Motorola US contacted me and offered help, so I can't really say anything bad about Motorola, they are really friendly and helpful. They offered to replace my Xoom, but later discovered that i'm not in US and suggested that I should be able to get a replacement from europe.
Before I was contacted by Motorola US, I sent a email to Motorola UK and they also apologized for the problems I had and offered to replace my Xoom, only problem is that they don't have any in stock at the moment, so I have to wait about two weeks.
As my Xoom works great after I force reboot it, it's not a problem for me to wait, I can use my Xoom until I get a replacement.
I would like to thank Motorola for the great support that they have offered me and I will update this thread when my issue is resolved.
But back to your problem, I suggest that you contact your nearest Motorola office, i'm sure they will try to help you.
poisike said:
But back to your problem, I suggest that you contact your nearest Motorola office, i'm sure they will try to help you.
Click to expand...
Click to collapse
I'm trying to do it right now
A little update.
I have been using my faulty Xoom for over two weeks now. I didn't turn it off so it worked until today. Today i tried to install a app from Market and My apps crashed, so i tried to stop it and this caused Launcer to FC (Does Launcer FC cause a automatic reboot?). The screen went black and in about 20 seconds it did show me the lock screen and i had no touch screen control. So i force rebooted it and now it doesn't even start up anymore, it's stuck on boot animation.
So it's starting to get really frustrating... I'm even considering to buy another Xoom, but this really isn't a solution, i have no use for two (if i ever get a replacement).
Has anyone any ideas? Why is it now stuck on boot animation, doesn't this look like a software problem? Is there any way to push clean images to it without unlocking? I understand that unlocking will void my warranty?
Is it possible to flash the official stock images without unlocking?
Ok, i got it to boot up again. I did Wipe data/factory reset and now it boots up again, but still no touch control.
And it seems that i have confirmed that doing too many force reboots will mess up the system.
BTW, there is a way to get into Android recovery on WIFI only Xoom, i wish i had known this before, "adb reboot recovery" works.
Can someone please answer my question, is it possible to flash the official stock images without unlocking? Maybe that will fix my touch screen control problem...
I've having this same issue but mine is worse.. the touchscreen is not working AT ALL.. only the power button works..
I can restart the xoom with the volume up power button but after it restarts still no response from the touchscreen!
What can I do to fix this?
Any help would be appreciated..
Something similar (as in not exactly) posted in the Desire forums, but with no answers so I'm posting here too.
Every now and then when I unlock the phone, the volume will go from where ever it's set at when I unlock down to vibrate without me doing anything. I turn it back up without a problem, but it's kind of annoying. Anyone else have anything like this happening or any idea as to why?
Thanks in advance.
cookw24 said:
Something similar (as in not exactly) posted in the Desire forums, but with no answers so I'm posting here too.
Every now and then when I unlock the phone, the volume will go from where ever it's set at when I unlock down to vibrate without me doing anything. I turn it back up without a problem, but it's kind of annoying. Anyone else have anything like this happening or any idea as to why?
Thanks in advance.
Click to expand...
Click to collapse
By chance, do you have the option in the Sound menu called "Quiet ring on pickup" checked?
I unchecked it. I don't think that's the problem because it doesn't happen when I have incoming calls, but we'll see. Thanks!
I had the same.issue. i re rooted and everything works now. Dont know if this helps but g/l anyway
cookw24 said:
Something similar (as in not exactly) posted in the Desire forums, but with no answers so I'm posting here too.
Every now and then when I unlock the phone, the volume will go from where ever it's set at when I unlock down to vibrate without me doing anything. I turn it back up without a problem, but it's kind of annoying. Anyone else have anything like this happening or any idea as to why?
Thanks in advance.
Click to expand...
Click to collapse
I have this problem too. The volume gets quiet for no reason, and then "levels" back up. Would like to know what's causing this. I'm running CM7.
Just wondering if this was resolved
Sent from my Desire HD using XDA Premium App
hello xda members
i have install froyo fx06 bundle here
my problem is sometimes the phone freeze. i read the entire post to find the solution to fixed that. then i found the only solution is to install init at here . can someone make a tutorial how to install that. i mean the step by step tutorial.
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
R^7Z said:
Have you any idea as to how to use ADB or terminal? If you do, then you are pretty much done, with the exception of executing those commands in that post. If not, you'll have to wait till it gets committed like the rest of us Or just wait till someone that does know, comes across your thread! That thread is mainly there for people who know how to do this already.
Click to expand...
Click to collapse
i don't know how to use ADB or terminal. actually this is my first time heard that. hehe
Some say it isn't that difficult while others have a difficult time trying to understand English, much less speak/type it(like myself ). If you feel up to it, you can start by reading HERE. Unless someone else has this simplified elsewhere. If that were the case and I knew of it, I woldn't be pointing you in this direction.
Thank you for trying to help me.
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
hotsmusic said:
today i have install [RIL + ROOTFS] on my device after found this thread http://forum.xda-developers.com/showthread.php?t=950383
but the problem still same. i have read that [RIL + ROOTFS] is to fixed freeze because 3g problem i think. but i think my problem is not about 3g.
my problem i think is about my device sometimes not showing display, it happen if i put my phone in standby mode then when i want to on back it will not show the display. but i can tell that my phone is working and not freeze, only it have blank screen.
please help me..!!
Click to expand...
Click to collapse
and i think it's not because flax cable because this problem only happen when i use froyo fx06.
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
R^7Z said:
Honestly, I've never had any real problems with FroYo freezing on boot. Just the SoD issue due to partial panel collapse. Supposedly, that (modified rootfs) only fixes the freezing on boot issue. Unfortunately, there is no way I can reproduce the issue you are experiencing on my end to help troubleshoot. Some blame it on the operator/service provider and others think it's the build itself. As for me, well I'm not sure what to think because it doesn't seem to affect me much. Have you tried Gingerbread yet? Might be something to play around with till the issue gets fixed.
Click to expand...
Click to collapse
Thank you for trying to help me. actually i have try to set my phone in airplane mode to test if the problem because operator/service provider , but the problem still the same. it's not freeze because i still can fell it vibrate when i touch the screen only the display not show up.
about gingerbread. i have read that gingerbread is android 2.3 and froyo is 2.2 right? but why many people like to use froyo then gingerbread? if gingerbread have any problem. sorry if i asking to many question.
I'm not 100% on this but I think it has something to do with the fact that the porting is still in alpha phase for our devices. If anything, this can be looked at as good or bad. Good, that we have gotten this far and it seems our devices are pretty much stable. Bad, that this might be as good as it gets for a while. You have to weight the options of a faster port(in terms of stability) but less complete(in terms of functionality) or a more complete port but not quite as fast. I remember when we first got FroYo, it seemed like a complete mess. It took till the third release (FRX03) for stability to take place(noticable) because the devs were trying to figure out what caused the instability. When it's all said and done, the end user experience is all that most are looking for. When this is the case, it's difficult to say what should be done. Wait till it becomes more stable or try to come up with work arounds. Troubleshooting can get you so far until you require more understanding of what affects what. Hopefully, I have bored you out of your mind and that this makes things clearer as to what you can do to help!
thank you for your kind to help me. i have change to gingerbread but it have same problem like froyo. then i tried to hard reset then reinstall froyo and change the kernel. now it working great without problem except camera not working . maybe because i change the kernel htc-msm-linux-20110214_200559-package.tar . but it's ok for me. i will wait till new release.
You must have the similar issues some others have (on foreign carriers/other than USA based) Now, I'm not saying this is the problem just that others that have a similar issue, are on those carriers. There have been updated kernel packages that include the camera fix but I would suggest a little more reading into what you need to do, to ensure that you aren't causing the issue you are experiencing now.
This has been an ongoing problem for... oh pretty much as long as I can remember. Every time I plug my phone in, the screen stays on. I've dealt with it, I've created a Tasker profile to take care of it... but it's just gone on long enough. I have no clue what mod I flashed to create the problem, but it's high time I figured it out.
The problem? I have no idea how to read a logcat or what I'm looking for. I've also tried attempting to figure it out via BetterBatteryStats (wake locks and what not), but still don't really know what I'm looking at.
Below is a logcat. I cleared it, then plugged in, then let it sit for 5 seconds and promptly dumped the logcat to a file. If anyone could help me figure this out, I'd be greatly eternal!
If there is anything else I need to do to help you help me, let me know. Thanks guys.
ridethisbike said:
This has been an ongoing problem for... oh pretty much as long as I can remember. Every time I plug my phone in, the screen stays on. I've dealt with it, I've created a Tasker profile to take care of it... but it's just gone on long enough. I have no clue what mod I flashed to create the problem, but it's high time I figured it out.
The problem? I have no idea how to read a logcat or what I'm looking for. I've also tried attempting to figure it out via BetterBatteryStats (wake locks and what not), but still don't really know what I'm looking at.
Below is a logcat. I cleared it, then plugged in, then let it sit for 5 seconds and promptly dumped the logcat to a file. If anyone could help me figure this out, I'd be greatly eternal!
If there is anything else I need to do to help you help me, let me know. Thanks guys.
Click to expand...
Click to collapse
Are you saying that every time you plug your phone in to a USB to charge it, the screen stays on?
Really stupid question, but you don't have "Stay Awake" enabled under your Development options do you?
Hope you're ready for a really stupid answer... Iiiii'm dumb...
oh my ****ing god.... I can't believe I missed that.... I don't remember ever turning that on.
I really want to delete everything about this thread so I don't have to be reminded of how stupid I can be sometimes... Maybe someone else will learn from it...
Thanks man. I appreciate the help.
As it turns out, the option keeps getting enabled every time I reboot. No clue how to fix that. any ideas?
ridethisbike said:
As it turns out, the option keeps getting enabled every time I reboot. No clue how to fix that. any ideas?
Click to expand...
Click to collapse
I presume that you must be running a custom ROM. Have you fixed the permissions in recovery - maybe one of the files is set to read-only, so you can change the setting, but it isn't saved? Failing that it might be worth asking on your device forum to see if anyone there has an idea.
Tried fixing permissions already. No dice. All the research I've done points me no where. Either people don't notice it's happening or it's only happening to me. The closest I could find is a bunch of people saying that they are having a problem actually keeping the phone awake when plugged in. Quite the opposite of my issue.
I would have posted this in the inspire forum originally, but it seemed like it could be a universal thing (common file in Android). I'll post it in inspire forum anyways. Maybe a dev knows where the setting is kept in the system and can point me in the right direction.
Until then, I've set Tasker to change the setting upon boot, which is way better than what I had it doing before lol.
Thanks for the help, though.
Is there any reason why this would happen?
Another one here experiencing the same issue
Another one here experiencing the same issue.
It didn't happen to my device until I upgraded to 4.0.4 Android and HTC Sense 4.1 (Spanish Orange network HTC One S version 2.38.75.4).
When it switch on while on a pocket it is very annoying as the phone "tries" to make an emergency call.
Faulty power button?
Sent from my locked, tampered ville
jaywhy13 said:
Is there any reason why this would happen?
Click to expand...
Click to collapse
This will say:
AirPush Detector. You find this app on the Play Market.
usaff22 said:
Faulty power button?
Sent from my locked, tampered ville
Click to expand...
Click to collapse
Only detected after a firmware update? I don't think so.
I was flashing the new Viper on my nieces phone and didn't quite get everything set up the way she likes it before she had to go home so I had to restore her nandroid of Viper ICS and now she is texting me telling me she is having this issue. Can anyone tell me if they ever had this issue and resolved it and if so i guess i might resolve it when i see her next weekend by reflashing the ROM? Or is it a serious issue or maybe one she can resolve? thanks for any info pertaining to this, my niece is quite picky and i am sure any of us crackflashers here know what it is like when you promise a woman the best for her phone then screw it up for her, never hear the end of it! lol. thanks for any help!
LibertyMonger said:
I was flashing the new Viper on my nieces phone and didn't quite get everything set up the way she likes it before she had to go home so I had to restore her nandroid of Viper ICS and now she is texting me telling me she is having this issue. Can anyone tell me if they ever had this issue and resolved it and if so i guess i might resolve it when i see her next weekend by reflashing the ROM? Or is it a serious issue or maybe one she can resolve? thanks for any info pertaining to this, my niece is quite picky and i am sure any of us crackflashers here know what it is like when you promise a woman the best for her phone then screw it up for her, never hear the end of it! lol. thanks for any help!
Click to expand...
Click to collapse
All i can really think of is that in the viper rom you have the option under tweaks to let the screen turn on when a message arrives. Mine used to do the same thing every once in a while but it was somehow connected to my data connectivity jumping all over the place so i re-flashed and wiped caches which did the trick.
Hope you get the problem resolved for your nieces sake!
I'm having the same issue with my Evo LTE
The same problem with SGS2 / ICS 4.0.3. Any idea how to fix that please ? It is VERY annoying, cuz it drains my battery !!!
aquinoe said:
Only detected after a firmware update? I don't think so.
Click to expand...
Click to collapse
In my original post I was talking to the OP.
It's not a software problem on the One S, look at everyone else with the same problem.
Sent from my HTC One S using Tapatalk 2
jaywhy13 said:
Is there any reason why this would happen?
Click to expand...
Click to collapse
If there are still people with this kind of issue,
I would recommend to check for "wakelock" usage.
As third-party apps can use "wakelock" to turn on the screen, there might be some buggy app which is using the feature improperly.
I had the same case before, turned out that "Naver Mail" app was using Screen wakelock to turn the screen on randomly.
As a solution, there is an app in Google Play called "Wakelock detector" which has a feature to show statistics of Screen wakelocks.
GooD luck
Random Screen On caused by faulty power adapter
I changed my power adapter for charging, and the problem went away immediately. I assume it was the result of either drawing too much power, or not enough to charge the phone. Anyway, there you go. Hope it helps! :silly: