I have installed Ubuntu Touch on my Nexus 7 and after the March 28th daily build update, my device will not shut down. I hold down the power button, it shuts down and powers back on by itself. The only way it shuts off completely is when the battery drains out. Even after updating as recently as yesterday still hasn't fixed the problem. I'm kind of afraid to ruin my Nexus 7 tablet now. Is anyone else experiencing this problem?
1roxtar said:
I have installed Ubuntu Touch on my Nexus 7 and after the March 28th daily build update, my device will not shut down. I hold down the power button, it shuts down and powers back on by itself. The only way it shuts off completely is when the battery drains out. Even after updating as recently as yesterday still hasn't fixed the problem. I'm kind of afraid to ruin my Nexus 7 tablet now. Is anyone else experiencing this problem?
Click to expand...
Click to collapse
Today i installed the latest build to this date( June 6) and noticed the same problem , theres no power off/shutdown option, so what i do i just hold power+volume up+volume down and boot back in bootloader.
After that if i want to shutdown the tablet i do so or boot back in recovery to boot in another rom.
Of course you need MultiRom to boot back in another rom
Good Tip
jonathanxx1 said:
Today i installed the latest build to this date( June 6) and noticed the same problem , theres no power off/shutdown option, so what i do i just hold power+volume up+volume down and boot back in bootloader.
After that if i want to shutdown the tablet i do so or boot back in recovery to boot in another rom.
Of course you need MultiRom to boot back in another rom
Click to expand...
Click to collapse
Thank you for this idea. I didn't think about that. Now I can keep testing Ubuntu Touch without fear of messing up my device.
Bug in powerd
1roxtar said:
I have installed Ubuntu Touch on my Nexus 7 and after the March 28th daily build update, my device will not shut down. I hold down the power button, it shuts down and powers back on by itself. The only way it shuts off completely is when the battery drains out. Even after updating as recently as yesterday still hasn't fixed the problem. I'm kind of afraid to ruin my Nexus 7 tablet now. Is anyone else experiencing this problem?
Click to expand...
Click to collapse
There was a bug in powerd 0.11, where they added proximity sensor support for the Galaxy Nexus and Nexus 4, where it would segfault when it didn't find a proximity sensor (as in the Nexus 7). This was fixed in powerd 0.13, which is available part of the daily images now or upgradable using apt-get.
mhall119 said:
There was a bug in powerd 0.11, where they added proximity sensor support for the Galaxy Nexus and Nexus 4, where it would segfault when it didn't find a proximity sensor (as in the Nexus 7). This was fixed in powerd 0.13, which is available part of the daily images now or upgradable using apt-get.
Click to expand...
Click to collapse
If it was fixed I doubt so.
The build from yesterday still had the same issue on my nexus 7
Sent from my Nexus 4 using xda app-developers app
jonathanxx1 said:
If it was fixed I doubt so.
The build from yesterday still had the same issue on my nexus 7
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
What build number are you using? I have 153 on my Nexus 7 and powerd isn't segfaulting anymore. I can suspend the OS with the power button, though the screen backlight cycles on and off constantly when it's suspended. But I was told this is a separate issue from powerd.
Fixed
After the 153 build I am no longer having the same problem. My N7 now goes to sleep and shuts down again. I am now updating to 156.
mhall119 said:
What build number are you using? I have 153 on my Nexus 7 and powerd isn't segfaulting anymore. I can suspend the OS with the power button, though the screen backlight cycles on and off constantly when it's suspended. But I was told this is a separate issue from powerd.
Click to expand...
Click to collapse
I downloaded the latest one today the 158 and still i have problems, i cant connect to my wifi because when i want to type the keyboard doesnt appear.
The calculator app seem to work on that build btw.
Build 158
I updated to Build 158...very frustrating. Everything I click on just takes me to a blank white screen. The keyboard is even buggier than before. It's completely unusable on my Nexus 7 and the update was over 300 megabytes.
I've been able to get Ubuntu touch to work on my nexus 7 , but like the poster above me said I had issues with white screen and no keyboard.
All that was fixed by updating and flashing the latest app collection on my computer with Ubuntu 13.04.
There's still issues like the location is wrong even I'd I flashed the timezone.
It fixed the time but not the location.
Also the weather app, I'm not able to add a location.
Sent from my Nexus 7 using xda app-developers app
Updated To Build 160
Just made the update and everything seems functional again. I finally got to play around with terminal for a bit. I would like to see if I can install any apps from the PPA Collection. If anyone knows how, please let me know. Thanks.
1roxtar said:
Just made the update and everything seems functional again. I finally got to play around with terminal for a bit. I would like to see if I can install any apps from the PPA Collection. If anyone knows how, please let me know. Thanks.
Click to expand...
Click to collapse
i suggest you to read this page if you want to flash the latest apps: https://wiki.ubuntu.com/Touch/ReleaseNotes#Upgrades
Related
Just wondering if everyone else typically get presented with the shutdown menu when waking the tablet up? I've experienced this on TnT Lite, Vegan and Zpad. Is it just me, is there a fix and does this annoy the pi$$ out of anyone else?
My tablet tends to just shut completely down after a couple of minutes of being in standby. Not sure why. Haven't found a solution...though I admit that I haven't really looked all that hard either.
scsione889 said:
My tablet tends to just shut completely down after a couple of minutes of being in standby. Not sure why. Haven't found a solution...though I admit that I haven't really looked all that hard either.
Click to expand...
Click to collapse
I have the same problem even on the stock TnT w/OTA update. I called support and they told me it was normal, but I don't believe it. I'm on my second g tab, and the first one I had didn't have this problem (I returned it because the WiFi would show error most of the time).
It's annoying enough to me that I'm thinking of exchanging it.
Mine does it on cmb4
Mine does it sometimes, but I noticed the you can avoid that by waking the tab by pressing the volume keys insead of power button.
Regards,
Rayan
Same problem here. Will try volume keys.
-=Sent from my ViewSonic G Tablet (Zpad 2.2) using Tapatalk=-
Yeah I got that issue too.
I would assume that the code that puts the device to sleep and wakes it up doesn't cancel the keypress from propagating to the rest of the system, so the system responds to the press of the power key with a shutdown menu, and wakes up.
I ended up exchanging mine yesterday. I just ran a quick test completely stock out of the box and the sleep seems to work properly, though it's fairly sluggish after waking (no OTA updates applied yet).
The bonus was that Sears had it on sale for $349 so I got a few bucks back.
With the Vegan Rom theres no problem talking there tablet in or out of sleep mode, maybe it's got something to do with the standard slide to unlock android feature, but it works great all the time.
Cheers,
Rayanmx
Sent from my Nexus One using XDA App
I get it maybe half the time. Noticed it on tnt lite and vegan both.
I am having the same issue on my stock tablet. I am almost positive this started after the December 10 OTA update (3053).
I have this problem every time I set g tab to sleep, I will ask for an exchange.
I wonder if this is something kernel related. Anybody know?
It seems like after 5 minutes or so it just completely turns off rather than staying in standby. Not cool. Highly doubt its anything hardware related.
scsione889 said:
I wonder if this is something kernel related. Anybody know?
It seems like after 5 minutes or so it just completely turns off rather than staying in standby. Not cool. Highly doubt its anything hardware related.
Click to expand...
Click to collapse
I have this same issue. My gtab seems to shut down with inactivity, rather than stay in sleep/standby.
katmandu421 said:
Just wondering if everyone else typically get presented with the shutdown menu when waking the tablet up? I've experienced this on TnT Lite, Vegan and Zpad. Is it just me, is there a fix and does this annoy the pi$$ out of anyone else?
Click to expand...
Click to collapse
Same problem here with vegan 5.1. Does anyone have a solution?
I'm still seeing that menu from time to time.
I can't reproduce the behaviour at will, it just happens totally at random. Except of course if I keep pressing the power button on purpose.
For me, that's the only Gtab annoyance right now.
Sent from my Nexus One using XDA App
Rayan said:
I'm still seeing that menu from time to time.
I can't reproduce the behaviour at will, it just happens totally at random. Except of course if I keep pressing the power button on purpose.
For me, that's the only Gtab annoyance right now.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I was just reading this thread and testing the behavior, and my device just shutdown on me after putting it to sleep!
I was originally going to say that I've seen the shutdown appear from time to time on various ROMs. I think CM7 was the only one I didn't see it as often on.
I pushed the power button to put it to sleep after trying a couple things. Then I read your post above, and when I went to pick it up again, it was already off. I think the tablet has powered off by itself about 3 times since I got it a week ago.
I'm currently on Caulkins v1.1.
this annoyance has been mostly eliminated/greatly reduced.
http://forum.xda-developers.com/showpost.php?p=12754698&postcount=9
pershoot said:
this annoyance has been mostly eliminated/greatly reduced.
http://forum.xda-developers.com/showpost.php?p=12754698&postcount=9
Click to expand...
Click to collapse
Thanks, I haven't used your kernel yet, as I haven't wanted to deal with the modules. Since you brought it up though, do I have to run insmod on each bootup, or only the first time (assuming I wanted it at that moment)? I know most modern linux distributions can autoload kernel modules, which is why I ask. Can this kernel autoload modules on bootup? Does android even support that?
Phoenix84118 said:
Thanks, I haven't used your kernel yet, as I haven't wanted to deal with the modules. Since you brought it up though, do I have to run insmod on each bootup, or only the first time (assuming I wanted it at that moment)? I know most modern linux distributions can autoload kernel modules, which is why I ask. Can this kernel autoload modules on bootup? Does android even support that?
Click to expand...
Click to collapse
they need to be inserted at every boot (whichever you need).
the app(s) you're using may pre-insert them for you.
you can dload gscript, and with one click, insmod everytime you reboot.
you can also stick a script in init.d to do it for you at boot.
Did anybody here experience on SK17i that when you install an APK coming from say, a file explorer or even the "Application Installer", then you click on the program you want to install, you can't click the "Install" button?
I mean you can click it but it won't register. And there's nothing you can do about it, unless power cycle the phone, and randomly experience the issue again.
I am pretty sure that this is not a hardware problem as the touch screen works everywhere, only in Installation this problem comes up.
I noticed this on the stock .335 firmware, and now that I flashed the .368 I thought it was fixed, still there sometimes, randomly.
But when it works (immediately after a power cycle), it works just as normal.
Installations coming directly from Android Market does not have this problem.
I don't install/uninstall apps regularly so its not much of a big deal but I really find this strange. As I am not fond of doing reboots and waiting for phone to start up just to find out it has that issue again, what I do is just install using "adb install" when connected to my laptop.
Any similar experience, and how is this resolved?
i was .335 now .368 but i don't have this issue sorry.
I'm curious when you say reboot do you turn off the phone completely or you have an app.
in the market Fast Reboot closes all app but keeps phone still on. maybe that can help in some strange way instead of turning off the phone, if thats what you mean.
thanks for the response. like i said its rare i encounter this, but at some random instance it happens. if i had no choice i power cycle the phone (sorry i mentioned reboot in the 1st post), but it is power cycle. i know the "Fast Reboot" application, but what that does is just kill all apps, not really reboot
btw, a program that really reboots the phone on one click is "Reboot Control Widget", which I have installed (rarely used though) and it needs root.
Same issues have happened here randomly. I am running the .368 firmware with google market automatically updated to the newer version (the windows phone 7 like).
Nope. Didn't have this problem
Sent from my SK17i using XDA App
Could that be because the installation file is corrupted or invalid?
^ Not so, because after a power cycle, its almost 95% the error disappears and you can install it normally. Strange huh...
I have this issue sometime,which the version is 4.0.A.2.364
and will try the 2 'reboot' app mention in this post,thanks.
2 days ago my phone totally lost responsiveness of touch screen. As in touch screen dead. I'm sending it back today for seller to replace. Good thing I bought a cheap arc yesterday.
What's evident here now, is this issue could be telltale signs that eventually the touch screen will die so arrange for backup and warranty.
Sent from my LT15i using Tapatalk
jtdc said:
2 days ago my phone totally lost responsiveness of touch screen. As in touch screen dead. I'm sending it back today for seller to replace. Good thing I bought a cheap arc yesterday.
What's evident here now, is this issue could be telltale signs that eventually the touch screen will die so arrange for backup and warranty.
Sent from my LT15i using Tapatalk
Click to expand...
Click to collapse
Or you had a dud phone
Sent from my ST15i using xda premium
Yes that may be the case. In any case, because of that event, I was able to get a cheap Arc. Now i'm thinking which do I keep when the SK17i gets back.
Sent from my LT15i using Tapatalk
Just an update on this matter.
It seems the app "Screen Filter" which helps reduce the brightness contributes as one of the cause or maybe the main cause of this issue. I happened to observe it on Xperia Arc on rare occassions. When I turn off the app, Install clicking works afterwards.
My auto rotate stop working. I have it checked under settings. I tried to download compass and labrynth and its still not working.
When I open the camera and YouTube it rotates to landscape.... but the goes back to portrait.
What am I missing?
Sent from my Transformer Prime TF201 using xda premium
Anybody?
Sent from my Galaxy Nexus using xda premium
Had this problem yesterday after installing sportcaster, that is a portrait only app. After I rebooted, it worked fine.
Sent from my Transformer Prime TF201 using xda premium
Did a factory reset and it still isn't working.
Any other suggestions?
Will be returning it if I can't get it too work.
Sent from my Galaxy Nexus using xda premium
I hate to ask, so forgive me if you've tried, but you don't have screen rotation locked do you?
Nah, its clicked on but doesn't rotate.
I'm losing hope. It doesn't work anymore.
Sent from my Galaxy Nexus using xda premium
That's weird, my autorotate doesn't work either. The other thing I did recently was install he latest update that was released today.
MisterBao said:
That's weird, my autorotate doesn't work either. The other thing I did recently was install he latest update that was released today.
Click to expand...
Click to collapse
Same here.
It worked fine before.
Those that updated - Can you guys check your auto rotate and report back?
Thanks.
Sent from my Galaxy Nexus using xda premium
Mine is still working fine after the update.
Okay I powered it down completely then fired it back up and now everything works. Tested all the sensors via the phone tester app. Before, none of the sensors were working for me.
I hadn't noticed but mine wasn't working after the update either. Rebooted and it's working again.
Mine isn't working after a reboot.
Sent from my Galaxy Nexus using xda premium
Anybody else experiencing auto rotate not working?
Before I take it back....
Sent from my Galaxy Nexus using xda premium
Mine hasn't been working either. I haven't installed the new update yet but I will see if that changes anything. Mine has been on and off since I got it. It would work half the time and then sometimes not at all even after a reboot or a hard reset. If this update does not fix this problem I will be asking for an exchange.
kunp21 said:
Mine hasn't been working either. I haven't installed the new update yet but I will see if that changes anything. Mine has been on and off since I got it. It would work half the time and then sometimes not at all even after a reboot or a hard reset. If this update does not fix this problem I will be asking for an exchange.
Click to expand...
Click to collapse
I really think its the update because mine was good before all this.
I can't use my camera either because my camera update always fails. It says you must update your camera firmware.
Damn, my auto brightness stopped working also. Can't believe this mess.
I had a perfect transformer... damn you ASUS!
I still have the receipt but they are out of stock. I'm going to keep it until the 12th and see if ICS fixes everything. I can't let go of you Prime.
Sent from my Galaxy Nexus using xda premium
Had this issue. Updated my firmware last night. Closed out of all my apps. Didn't do anything. Followed it up with a reboot. Started working fine.
So I updated the tablet last night and it did not seem to help. Using the app elixir I checked to see the status of the sensors, and none of them are responding when this problem occurs. I also noticed that if I turn the auto-rotate feature off and turn it back on in 10 - 15 min it starts working again. I have tried everything to figure out what is wrong, but have no idea. I will be going to Bestbuy this Friday and asking for an exchange, but it will more than likely be a return because of stock. Till then i'll be on the forums hoping for a solution.
I just got my tablet last night, and I'm having the same issue Nothing seems to work to fix it, like rebooting it or resetting it to factory. I've never had it work, but I didn't test before I installed the Firmware update. Has anyone talked to Asus about the issue? Figure I'll give them a call tonight and see what they say before I have to try to exchange it through Amazon (and who knows when I'll get the tablet back...). My first Android tablet, really makes me feel frustrated with it.
Qamel said:
I just got my tablet last night, and I'm having the same issue Nothing seems to work to fix it, like rebooting it or resetting it to factory. I've never had it work, but I didn't test before I installed the Firmware update. Has anyone talked to Asus about the issue? Figure I'll give them a call tonight and see what they say before I have to try to exchange it through Amazon (and who knows when I'll get the tablet back...). My first Android tablet, really makes me feel frustrated with it.
Click to expand...
Click to collapse
So you didn't notice if it was working before you updated?
Yeah, this sucks. My auto rotate and auto brightness use to work.
Let us know what ASUS tells you.
Has anyone experience some form of lag/delay/unresponsiveness for the GS5? I had to sometimes wait more than 10 secs for the lock screen to load or hold down the power/wake button to get the screen to show up. Please let me know if I should get my GS5 replaced! Thank you!
AzumaKazuma said:
Has anyone experience some form of lag/delay/unresponsiveness for the GS5? I had to sometimes wait more than 10 secs for the lock screen to load or hold down the power/wake button to get the screen to show up. Please let me know if I should get my GS5 replaced! Thank you!
Click to expand...
Click to collapse
I noticed this started to happen when I started using the fingerprint. Also if you turn off the lock screen just as it coming on or if you turn it on just as it is going off. Seem to get confused and can take time to respond and yes 10 seconds sounds about right of me as well.
I realized when it started doing it was when the AutoProtect was enabled and My Magazine enabled and Geo News enabled. It's been 24 hrs since I turned it off and it seems to have stopped!
I think it's AutoProtect that caused the lock screen lag. Let me know if it stopped doing it for you!
yes i have this problem, i play alot of music and alot of times the tracks dont change and they will change a minute later, the lag seems ramdom.
i remove my magazine and geo news since i dont use either and will test it
thanks for the tips because this was driving me crazy
Don't forget about Autoprotect, It's been 18 hours since I turned it off and I haven't had the lock screen problem.
AzumaKazuma said:
Don't forget about Autoprotect, It's been 18 hours since I turned it off and I haven't had the lock screen problem.
Click to expand...
Click to collapse
Where is auto protect exactly?
Sent from my SM-G900F using XDA Premium 4 mobile app
i cant seem to find where it says autoprocted
this is driving me crazy, coming from the note 3 this phone laggy lockscreen is driving me nuts
most of the times skipping tracks works but other times i press it 3 or 4 times and nothing happens and 30 seconds later 4 tracks are skipped
any other suggestions?
i remove my magazine and geo news
am rooted and have xpose frameworks installed
help i have 6 more days left to return it, if i decide to get my note back
losplatanos said:
i cant seem to find where it says autoprocted
this is driving me crazy, coming from the note 3 this phone laggy lockscreen is driving me nuts
most of the times skipping tracks works but other times i press it 3 or 4 times and nothing happens and 30 seconds later 4 tracks are skipped
any other suggestions?
i remove my magazine and geo news
am rooted and have xpose frameworks installed
help i have 6 more days left to return it, if i decide to get my note back
Click to expand...
Click to collapse
Are you running ART? If so try switching back to Dalvik. I have seen reports that ART is causing some people issues with their lock screen.
philow said:
Are you running ART? If so try switching back to Dalvik. I have seen reports that ART is causing some people issues with their lock screen.
Click to expand...
Click to collapse
nope regular dalvik
never experience that before with the note 2 or note 3
the bad thing is random
I had the same thing on the GS4 and I've had it happen once or twice on my S5. It usually only happens when I've left the phone asleep for a while. I think it's most likely a software issue though, so I wouldn't bother replacing it.
11 9966644
I just switched mine from ART to dalvik and it worked!!
Where is this auto protect and how do I turn it off.
Couldn't find anything on Google.
I would like to know where this auto protect is too
Sent from my HTC One S using XDA Premium 4 mobile app
AzumaKazuma said:
Don't forget about Autoprotect, It's been 18 hours since I turned it off and I haven't had the lock screen problem.
Click to expand...
Click to collapse
It won't let me disable Geo News and Autoprotect. It let's you do it?
Sent from my SM-G900T using Tapatalk
I can't even find auto protect.
Where is that?
Sent from my SGH-M919 using XDA Premium 4 mobile app
alliance rom and a custom kernel have seen to solve the problem....haven't had any issues last 4 days......i like the gs5 again
I've never had none of these issues with the phone. Seems to be user errors or modifications done by user. I see a lot of post about xposed causing disruptions in system. Just cause u can do it doesn't mean its worth tinkering with.
Sent from my SM-G900T using XDA Free mobile app
tea_dub84 said:
I've never had none of these issues with the phone. Seems to be user errors or modifications done by user. I see a lot of post about xposed causing disruptions in system. Just cause u can do it doesn't mean its worth tinkering with.
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Agreed, after a while users install so many things they can forget What's causing it
Sent from my SM-G900T using XDA Free mobile app
Enter the trolls.
tea_dub84 said:
I've never had none of these issues with the phone. Seems to be user errors or modifications done by user. I see a lot of post about xposed causing disruptions in system. Just cause u can do it doesn't mean its worth tinkering with.
Sent from my SM-G900T using XDA Free mobile app
Click to expand...
Click to collapse
Yes, since I don't have the problem it must be the users. Always love people who can't help but have to try to defend the phone manufacturer. The Black screen is a real problem for more than a few folks, you can google it if you don't believe me. I run a stock phone, and have made no changes, maybe I have four games on it, and have disabled some of the bloat. Recently and quite randomly, the screen will refuse to come on. Everything on the phone continues to run and it will even ring when you call it, but still the screen remains black until I pull the battery. I read that AT&T has resolved the issue and is sending out a fix as I type this. Don't know if the other carriers will follow suit or not.
It is a inconvenience to say the least but many users have tried all the known methods available to no avail. Seems to work fine for a undetermined period and then starts acting up again. I am notifying TMO tomorrow and see if they are going to be releasing the patch. If not, I guess it will be time to jump, Again.
Not sure if this is the root cause or not but seems to have done the trick for me so far..... I turned off auto brightness, and so far have not been able to replicate the problem, not sure though, my Note 3 would never let me use the auto brightness feature, when I would enable it on that phone the screen would always be way to bright. This one was the opposite. Could it be bad proximity sensors or the firmware that controls it? Need more people with the problem to test and report.
I too have had the black screen issue and the only fix is pulling the battery. It has happened 2x now, once completely stock and once since I rooted!
There's is another thread about screen issues but I don't think I'm having the same problem.
Since about Feb, my venue 7 screen freezes up when it sleeps or use the button to screen lock. I can see the unit has not frozen up, as apps will still update in the background. However, the screen is completely unresponsive. My only fix is to reboot the device.
I have done a complete wipe at least 4x and tried updating firmware a couple times without luck.
Any suggestions or advance trouble shooting tips would be appreciated.
Pro
Sent from my HTC One using XDA Free mobile app
prosonik said:
There's is another thread about screen issues but I don't think I'm having the same problem.
Since about Feb, my venue 7 screen freezes up when it sleeps or use the button to screen lock. I can see the unit has not frozen up, as apps will still update in the background. However, the screen is completely unresponsive. My only fix is to reboot the device.
I have done a complete wipe at least 4x and tried updating firmware a couple times without luck.
Any suggestions or advance trouble shooting tips would be appreciated.
Pro
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
My Venue 8 is doing the same thing. The screen will freeze while the app continues. After a few calls to Dell, they are asking for me to return the tablet and they'll "fix" it. Hopefully they can as I really like the tablet.
I received a replacement unit, which I then destroyed by dropping it. They never asked me to ship the original back, so I thought I'd have another run at fixing it.
I was hope a complete wipe would help but not so far.
Sent from my HTC One using XDA Free mobile app