Related
hey all,
so i was working with TF late at night, and i conveniently pushed the power button to suspend it (not turning it off), and the next morning, it just refuses to light up. I have the keyboard dock as well, but I was not using it at that time, and when i dock it, nothing happens.
any ideas? it starts to make me worry, since i had it for just 3 days.
thnx
Mine does that a lot.
First, plug it into the wall to make sure you've got some battery life.
Then try holding down the power button for a long time, maybe a minute. Then I push it a couple more times and it always comes up.
Just keep pushing that power button!
agreed sounds like the same issue that many of us have experienced (I've had it a dozen times or more). Each time just hold the power button for 10-12 secs, release then turn on as normal and it mysteriously comes back to life. Plenty of posts on this forum about it.
And unfortunately this problem persists for me even after the recent OTA update...
If the Samsung Tab 10.1 had a microsd slot, I think my Transformer would be on eBay right now.
Getting tired of unpaid beta testing.
Sorry for re-posting a common issue. On a side note, I was on the latest OTA firmware too.
I am off to work will try again in the evening.
Also, when it happens, does it also drains battery? Or is it just a not powering up issue
thanks for all the responses
It depends... Sometimes I get it to wake up and it says it has battery life. (Most of the time actually.)
Someone was saying that if you turn of the wifi new notifications option sometimes that helps. (I think that was the option...)
Please also refer this thread: http://forum.xda-developers.com/showthread.php?t=1070343&page=7
SOD
I have the SOD problem with the official rom (asus), not rooted, at the last version.
I have the problem even if wifi is off prior to put it to sleep (power off, no shutdown). If it stay docked with keyboard, i have no problem. It looks like i always have the problem without dock, after about 20 minutes, it no longer resume and have to press power button for 10 secondes and then it restart to boot like if has been shutdown.
Is there a log file somewhere ?
I did not notice this problem the first few day i had my tf, only since yesterday.
Maybe one of the installed program is causing the problem ?
Adobe Flash Player 10.3
androidVNC
Angry Birds
Angry Birds (another one)
Angry Birds Rio
Artillery
Barcode Scanner
BBC News
BlastMonkeys
BreakTheBricks
Bubble Blasts 2
CNet News
CNN
Cordy
Drag Toilet paper
Earth
wBuddy
ElectroDroid
f1.Com 2011
FreeCell
Google Sky map
GPS Test
How to Tie a Tie
Klondike
Labyrinth
Mahjong
Maps
msnbc.com
Pinball Classic
Pinball Deluxe
Pyramid
Revision 3
Satellite AR
Skype
Slots Royale
Spades!
Spider
Stupid Zombies
SurvivalGuide
Talking Gina
Talking Roby Free
Talking Santa
Talking Tom
Tank Hero
TegraZone
Terminal Emulator
Tic Tac Toe
the ones i have installed lately :
Amazon kindle
Adobe reader
HW Solitaire
bang Bang racing
reckless Racing lite
I hope they can solve the problem soon, cause that make no sens to have to always reboot (take ~15 sec)
Only the programs that are currently running not installed programs.
If you have a mini HDMI cable try to hook it up to a tv or monitor to see if that works. I had the same SOD issue but it's not really a screen of death. What happened to mine was just the back light died. If you have good eyes and are in a dimly lit area try turning it on and see if you can see the lock screen. I was able to see the lock screen, enter my pin, and actually vaguely see the home screen. Also if it hooks up to the monitor and you have adb access, chances are the back light is dead. Let me know how it goes.
Sent from my Nexus One using XDA Premium App
bleclair said:
And unfortunately this problem persists for me even after the recent OTA update...
If the Samsung Tab 10.1 had a microsd slot, I think my Transformer would be on eBay right now.
Getting tired of unpaid beta testing.
Click to expand...
Click to collapse
Seems to be alot of peoples sentiments.
Theres not even a chance of a dongle right ?
Asus transformer is turning into a very strange device with its combination of demand and HW problems.
don't know if this will help for you, but i fixed the sleep of death problem by removing my lockscreen to a normal unsecured login. prior, i set up a lockscreen pattern code.
it fixed my sleep of death problems when i was having it the first couple of days and i haven't had any since day 1.
sod
I do not have any password, only the default lock that you have to move out of circle.
Last night, i left it on sleep (power off but no shutdown) with no running application (had just reboot previoulsy) and in the morning i had to press power 10 seconds to make it reboot, the power on was not working.
just got back home, as for lock pattern, i had none, just plain honeycomb locking mechanism. I will try the 10sec power button trick right away though.
it worked! thanks all.
karlr30 said:
I have the SOD problem with the official rom (asus), not rooted, at the last version.
I have the problem even if wifi is off prior to put it to sleep (power off, no shutdown). If it stay docked with keyboard, i have no problem. It looks like i always have the problem without dock, after about 20 minutes, it no longer resume and have to press power button for 10 secondes and then it restart to boot like if has been shutdown.
Is there a log file somewhere ?
I did not notice this problem the first few day i had my tf, only since yesterday.
Maybe one of the installed program is causing the problem ?
Adobe Flash Player 10.3
androidVNC
Angry Birds
Angry Birds (another one)
Angry Birds Rio
Artillery
Barcode Scanner
BBC News
BlastMonkeys
BreakTheBricks
Bubble Blasts 2
CNet News
CNN
Cordy
Drag Toilet paper
Earth
wBuddy
ElectroDroid
f1.Com 2011
FreeCell
Google Sky map
GPS Test
How to Tie a Tie
Klondike
Labyrinth
Mahjong
Maps
msnbc.com
Pinball Classic
Pinball Deluxe
Pyramid
Revision 3
Satellite AR
Skype
Slots Royale
Spades!
Spider
Stupid Zombies
SurvivalGuide
Talking Gina
Talking Roby Free
Talking Santa
Talking Tom
Tank Hero
TegraZone
Terminal Emulator
Tic Tac Toe
the ones i have installed lately :
Amazon kindle
Adobe reader
HW Solitaire
bang Bang racing
reckless Racing lite
I hope they can solve the problem soon, cause that make no sens to have to always reboot (take ~15 sec)
Click to expand...
Click to collapse
You touch on something here. I do wonder if it's some app that's causing issues. Looking at your list above, I do not have most of the apps you list, and my TF has never encountered the SOD. I have a dock as well, both updated to the latest firmware, and still no issues.
I really wonder if it's something running in the background that just doesn't want to let the device start back up.
I'd suggest to people encountering the problem to first (as much as it sucks) do a factory reset and then be sure the firmware is up to date. Then install only a few applications - just the core ones you use the most frequently - preferably only a couple at a time. Then use the sleep mode and see what happens.
I'll add this as well - I had an Archos 101 that had a SOD problem. I figured out that it happened a lot if the screen off timeout was exceeded. Meaning, if I had the screen timeout set to 2 minutes, and I put it into sleep for more than 2 minutes, a lot of the times, it encountered the SOD.
Right now, my TF is set to keep the screen on. Perhaps this is a factor as well?
If anyone would like to test either or both theories above, try only one at a time. If you change too many things and then fix a problem, it's a lot harder to tell which action resolved the problem.
still sof
I still have the problem. And it is not a dim problem.
nothing on the screen.
Have to press 10 seconds o the power to have it to boot.
Isn't Asus going to do something about it ?
karlr30 said:
I still have the problem. And it is not a dim problem.
nothing on the screen.
Have to press 10 seconds o the power to have it to boot.
Isn't Asus going to do something about it ?
Click to expand...
Click to collapse
May I know which version you are using now?
Version no
Here are the version number :
Version android : 3.0.1
GPS : 1.2.4
Wifi : 5.248.35
Bluetooth : 6.12
kernel : 2.6.36.3-00004-g069b8b5
build : HRI.US_epad-8.2.3.13-20110511
Dock : EP101-0209
Language
I dont know but maybe i have something... i did'nt remembered but i think i started to have that problem when i changed the language of my tf to "french (canada)". Now i have reverted it back to "English US", and so far it doesn't look like i have the problem anymore... i'll continue to test that way and i will report back.
I have rebooted after changing the language, or else i still had the problem.
I've been doing the whole in dash tablet thing for a few years now. I've used the nook color, HTC flyer, and other gingerbread based tablets. I bought a Galaxy Tab 2 p3113 and was super stoked about it- but have run into a major obstacle that so far cannot be solved somehow. I've spent months trying to figure this one out with no success.
CM9 or any ICS rom for that matter, at a lcd density of 160 on a 7 inch tablet is uncomfortably small, especially in a car. 240 has always been great in the car on GB roms. But considering the Tab 2 has no hard keys, at 240 the soft keys not showing correctly renders the tablet useless. Market apps like soft keys for root and gesture controls are a joke flying down the highway.
I've read and used some local.prop entries with no success. I'm stuck with either squinting at a screen or jumping through hoops to navigate around it. This seems so easy, yet a Google search brings up next to nothing. All I want is my car tablet to stay in tablet mode above a density higher than 160. Simple right? It was simple to do in ginger bread.
Agreed. I'm in the same boat. I have searched for hours and have come up with nothing.
i never really messed around with cm9 but in aokp(would assume they have some of the same things) u can change the nav bar stuff around have u guys tried any of that?
I'm using CM10 on my OG Galaxy Tab 7, on screen navigation enabled, and LEFT Navigation enabled (240 DPI of course).
Works great.
I bought a Galaxy Tab 2 to do the same setup with, but couldn't get the CM10 Developers to help me get the left navigation going, but it DID work just fine at 240 DPI.
I've been using this setup in my car for a year and a half.
Tablet mode is cute and all, but the bigger navigation in phone mode is better in my opinion. Also, the quick widgets in phone mode are much easier to use while driving in my opinion.
I tried CM10 a week ago or so and had the same problem as CM9 and the buttons messing up. Even when the bar shows to the right, the buttons go from left to right, instead of top and bottom. It is very strange. AOKP did nothing better either.
Since I have the thread open, I've had a few other minor issues that you guys may know something about: I set up Tasker to script wifi/bt/gps/sync on and off with power as well as screen timeout and wake lock on charge. This is to shut down everything with ignition off and wake it all back up with the ignition. For some reason this only works about 80% of the time. It almost seems like a deep sleep or an embeded task killer is destroying the scripts that Tasker is trying to run. There is really no rhyme or reason to it. Tasker just fails sometimes and either I go out to a dead tablet or a tablet that wont stay on.
zavien3 said:
I've been doing the whole in dash tablet thing for a few years now. I've used the nook color, HTC flyer, and other gingerbread based tablets. I bought a Galaxy Tab 2 p3113 and was super stoked about it- but have run into a major obstacle that so far cannot be solved somehow. I've spent months trying to figure this one out with no success.
CM9 or any ICS rom for that matter, at a lcd density of 160 on a 7 inch tablet is uncomfortably small, especially in a car. 240 has always been great in the car on GB roms. But considering the Tab 2 has no hard keys, at 240 the soft keys not showing correctly renders the tablet useless. Market apps like soft keys for root and gesture controls are a joke flying down the highway.
I've read and used some local.prop entries with no success. I'm stuck with either squinting at a screen or jumping through hoops to navigate around it. This seems so easy, yet a Google search brings up next to nothing. All I want is my car tablet to stay in tablet mode above a density higher than 160. Simple right? It was simple to do in ginger bread.
Click to expand...
Click to collapse
I'm looking to get this SGT2 7" to put in my car dash. I'm not clear exactly what the issue is not having one yet, can anyone post screenshots of the issue or how the keys look? Or let me know if this is no longer an issue? I have not looked into various custom ROMs yet, just figuring out if this is going to work for my car at this point.
If your nav buttons are whats giving you trouble, get rid of them and use lmt launcher.
So I thought id share some of the things i have learned about my Ouya that makes life a little easier:
1: Double Tap Ouya button = Home
2: To get an Xbox360 dongle to work with multiple controllers follow these steps:
2A - Power on Ouya WITHOUT xbox dongle attached
2B - Boot into Ouya and have the light lit on your Ouya Controller
2C - Plug Xbox360 controller dongle in and pair your xbox controllers.
2D - Activate within app (N64 emu it is in settings/input and then hit the on switch for each. Then go ahead and set it to the xbox360 controller profile and when you play the game hit multiplayer setup and follow the instructions. Each emulator is different.
3: To turn off your Ouya completely hold the power button on the Ouya until the standard Android popup appears and then use the controller to hit Yes
4: Root Explorer (Paid) can mount Dropbox as a partition within the app saving you the step of having to use the official Dropbox app which sucks.. BUT you can only open Root Explorer through Nova or another launcher. Fails through Ouya Launcher. You can also mount a SMB partition as well. Just makes sharing that much easier.
5: Never leave your Xbox dongle plugged in on boot. It screws with things. For instance I cannot start certain games because it is seeing my Ouya controller incorrectly and wont accept button inputs
Hope these tips help some people
6) Pressing 'Y' and then "powering off OUYA" doesnt really power it off. A large portion of the android framework is still running, including pretty much every service in init. Dalvik, zygote, adb, internet, etc are all still there, and still doing whatever they want to do. Apparently the only part of it that does power down is the video output.
7) Certain triggers make the ouya "power back on" (even though it never really powered off). One of these is getting a signal over HDMI cable. some TVs send this when you select an input, some of them send it when they power on.
8) OUYA has the option enabled to kill apps when they're no longer in focus. This is good since there's no "recent apps" button where you could normally kill running apps that you no longer wanted to be running. This is bad in that it makes some apps act wonky. For example, if you find a video in TVPortal and select it to watch, you will see the video in your video app like mxplayer. When you are done watching it and go back to TV portal, it will start all over from the beginning of the app.
gianptune said:
8) OUYA has the option enabled to kill apps when they're no longer in focus. This is good since there's no "recent apps" button where you could normally kill running apps that you no longer wanted to be running. This is bad in that it makes some apps act wonky. For example, if you find a video in TVPortal and select it to watch, you will see the video in your video app like mxplayer. When you are done watching it and go back to TV portal, it will start all over from the beginning of the app.
Click to expand...
Click to collapse
Nova's recent apps shortcut doesn't even work.
Sent from my SCH-I535 using Tapatalk 2
gianptune said:
8) OUYA has the option enabled to kill apps when they're no longer in focus. This is good since there's no "recent apps" button where you could normally kill running apps that you no longer wanted to be running. This is bad in that it makes some apps act wonky. For example, if you find a video in TVPortal and select it to watch, you will see the video in your video app like mxplayer. When you are done watching it and go back to TV portal, it will start all over from the beginning of the app.
Click to expand...
Click to collapse
You can change this in Developer options and deselecting the Dont Keep Activities option on the bottom. Netflix requires this in fact
altimax98 said:
You can change this in Developer options and deselecting the Dont Keep Activities option on the bottom. Netflix requires this in fact
Click to expand...
Click to collapse
Netflix requires you have that unchecked? I haven't run into any problems with it and I keep it checked.
The main reason it's checked is because if you let Android do it's thing like a phone, it'll take up too much RAM and slow down the bigger games, such as shadowrun. Leaving this checked is the best way to run it as a video game console.
The powering off by the Y button puts it to sleep much in the same way your phone goes to sleep when you hit the power button to turn off the screen. It puts it in a low power state mode and Wifi does go to sleep, but it does still stay connected at a very low level. For all purposes (since this is an android device) this should not affect the longevity of the product.
One thing to add is the difference between holding down the button on the OUYA until the shut down dialog pops up vs holding it down until the system goes off is that using the dialog makes sure everything is saved while holding it down is, essentially, like a battery pull. It shouldn't hurt the phone, but there's a small chance some data could be lost.
Hi, all...
There are several apps available, like AdAway, franco.Kernel updater, Flash Image GUI and Flashify (for root users) that offer, upon completion of their appointed task, to reboot the Nexus 7.
These 'app initiated reboots' shut down the tablet INSTANTLY... unlike, when you shut down the Nexus 7 normally, via the power button, it takes a good half minute or so.
I get a sense that the normal shutdown procedure is closing down apps, and doing some cleanup before turning off the tablet completely.
So my question is this... do these 'fast, instantaneous app driven shutdowns' cause harm, or have the potential to cause data corruption?
The reason I ask is as follows...
For six months, prior to the arrival of Jellybean 4.3, I had a CyanogenMod Jellybean 4.2.2 Custom ROM installed on my Nexus 7, which provided me with an Advanced Power Menu... offering Power Off, Reboot, Reboot into Recovery, Reboot into Bootloader options.
Along with the AOSP browser (which is now available without root), this feature was invaluable, given the frequency of my booting into the Bootloader or Recovery.
Now on Jellybean 4.3, I really have no interest in Custom Roms, preferring to stay stock, but this app, Quick Boot (Reboot), from PlayStore, offers similar functionality as the Advanced Power Menu I mentioned above. And it performs as described.
But (and here, finally, I come to the crux of my point)... the reboot/shutdown options in this app occurs INSTANTLY... not over a few seconds, with a spinning wheel, with the words, 'shutting down' next to it as you would expect to see shutting the tablet down normally.
I would like to use this app on a routine basis, for booting into TWRP or the Bootloader... or sometimes just plain rebooting the Nexus 7. But the rapidity of the shutdown makes me nervous... like it's not 'ending stuff' properly.
----------------------------------------
I hope that somebody understands my question, and has some insight between the differences of a fast app initiated shutdown... and the normal shutdown procedure.
Thanks in advance for reading, and whatever light you can shed on this matter.
Rgrds,
Ged.
I think you're right in that is definitely a different 'type' of reboot. Can't remember what I was doing the other day but was viewing a log (can't remember if it was on n7 or s4) but had used either 'holo reboot' app or 'quick boot' prior to this and noticed a reference to a 'dirty reboot'. So the system definitely knows the difference. Not sure if it's any more harmful than a normal reboot.
Sent from my Nexus 7 using xda app-developers app
I could be mistaken, but I believe its like a force shut down similar to holding the power button on a laptop to force off instead of letting it power down. There shouldn't be any harm caused, I always use terminal emulator for rebooting rather than advanced power menu due to the fact it's faster and I don't like waiting for the whole power down procedure. And my tab has never given me any problems.
Sent from my Nexus 7 using xda premium
My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.
Double tap to wake works for me with Google Now launcher and Nova (free version). Double tap to sleep (lock) doesn't work with either. Works fine both ways with the stock Idol launcher. Looks like you may have discovered a work around.
stl1859 said:
My apologies if this is a repeat post.
It has been mentioned before that the double-tap-to-wake does not working with anything but the stock launcher. Actually technically the *wake* should work with any launcher. I just installed Apex (my regular launcher), and it is still working just fine. What does not work is the *lock*. Apex has its own double-tap gesture definition, and lock isn't one of the options. So to get around that, you can go to the Play Store and download, install and activate "Screen Off and Lock" . One option on the Apex double-tap setting is to launch any other app. You can now configure it to launch this app. Once you do that, when you double tap while in Apex, it will lock the screen. When you double tap again, it will unlock ( I do not think that has anything to do with Apex anyway ) .
Apex is my favorite launcher and I have been looking for a way to get back to it without losing the double tap. Now I can change themes, make my drawer look better and set up many other gestures. Hopefully this trick can work in any other launcher you want to use. And at the minimum , the double tap to wake should work regardless.
Click to expand...
Click to collapse
Nova Launcher has an identical gesture/setup. [ which I'm using in same way with the "Screen Off" app since the phone auto locks when the screen goes blank. ]
I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.
JJ2525 said:
I have experienced the inconsistency with dt2w. I kept deactivating/activating it and it's been working adequately (~60% of the time, still sucky but much better than before). Like others have said, it works much better if the phone is sitting on a desk as opposed to attempting it while in your hand. I really hope the reliability of dt2w gets improved in the next OTA update.
Using Nova and a double tap gesture that activates a screen lock app works perfectly for me.
Click to expand...
Click to collapse
Same here, NOVA launcher premium
My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.
maddog497 said:
My dt2w works flawlessly to turn screen off. It only works 50% of the time to get it on.
Click to expand...
Click to collapse
Exactly the same situation here.
Borghi said:
Exactly the same situation here.
Click to expand...
Click to collapse
I'm spoiled with the G3 and the Zenfone 2. They both work flawlessly.
Hopefully this gets fixed in an update.
Sent from my LG-D852 using Tapatalk
Thank you very much dude, I'm hoping to root ASAP still haven't found a reliable way to. I wish this device had a bit more ram but pretty good so far. I hate not being rooted just because I can erase anything on the external SD and hopefully with a custom Tom the screen Issues with the phone not waking gets fixed
You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Shodan5150 said:
You don't have to be rooted to delete files on the external drive. There's a thread here that covers that. I'll post the link when I'm on the PC.
Sent from my Alcatel OneTouch Idol 3 using Tapatalk
Click to expand...
Click to collapse
Sorry it took so long fopr me to get back here to post the link. I had PC issues and had to install Windows and then the hardware drivers for the AMD card gave me a fight. But you prolly already found the thread but the thread is below.
http://forum.xda-developers.com/idol-3/help/install-to-sd-card-root-access-t3119374
New discovery
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.
stl1859 said:
Some of you may have already discovered this - but this is certainly new for me. What I am noticing about the double-tap-to-wake - is that it always works - BUT - what is happening is that often it is slow - and I mean really really slow sometimes. Most of us would perceive that as not working - and try it again. And double-tap, on top of double-tap just makes matters worse. What I did was - tried double-tapping once - and when the screen did not come back on, just let it be for about 10+ ( probably more than that at times ) seconds - and it eventually came back on. Even under normal circumstances, the screen wakeup is slow . It looks like sometimes it just takes forever, creating the impression that it is not working. I am not trying to suggest that we can say that this behavior qualifies as 'working' - but at least we know what exactly the problem is.
I hope Alcatel pushes a fix for this. Till that time - I will have to continue to rely on single-tap to wake ( aka the power button ) if double tap to wake does not work.
Click to expand...
Click to collapse
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.
maddog497 said:
I have tried waiting for the screen without it coming on. Putting it on the desk and trying it and leaving it there, with no response. After a reset or disabling then enabling the function would work for a brief while. After that nothing seemed to help. If I used the power button to activate the screen and then try the DTTW, it would work but as soon as the phone went idol, so did the DTTW. As much as I liked the phone for the most part, I was not prepared to go past my return date without even one update coming from Alcatel.
Click to expand...
Click to collapse
Since the time I arrived at this theory, I have tested it again and again - and I can confirm that it is always doing it. You just have to be really really patient to see this in action. Forget what I said about 10 seconds ; sometimes you have to wait for more than a minute. It is weird - you double tap - then just stare at the phone for ages and suddenly out of nowhere the screen lights up.
If D2W is important for you , then my discovery does nothing for you - It is still broken. So you did the right thing in returning it. As far as updates go, again if that is important for you, then you did the right thing. Honestly I do not expect many ( if at all ) updates from TCL. From what I understand, they do not have the kind of software development infrastructure that Asus does . And that is evident from the extent of skinning that Asus did on top of Lollipop whereas the Idol3 was mostly a stock experience. IMHO - right now - more than updates from TCL, we need root , so that developers can do their own thing with the phone.
I have since installed a proximity sensor based wave-to-unlock app. Not only does it work very well, it also allows me to lock the screen back, from the lock-screen itself, something that is missing in the default D2W setup. The only downside is the additional power consumption by the proximity sensor. Since it is supposed to use only 3 mA , I am hoping it is not going to be too bad, but I will watch out for it. If the battery performance does not degrade too much, then I think I can kiss D2W goodbye.
I sent an email to Altatel Tech Support about a week ago and asked them if they are aware of the DTTW issues and working on a fix. I received a reply stating that they are aware and are working on an update. My guess is that they will try to combine multiple fixes into a single update. It may take a little longer and it is too bad that Alcatel is not better at communicating with its customers. It would make no sense for Alcatel to ignore all of the customer complaints here, on Amazon, and in various reviews and do nothing. They are spending cash marketing this phone and they must be smart enough to know that their sales will tank if they ignore the issues.
Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
japhule said:
Hey guys, just thought I'd let you know of a solution that appears to fix the double tap to wake issue everyone is having. Like most of you, I've been annoyed that this only works like 50% of the time. I've noticed in the G4 forums of people having issues with their double tap to wake not working as well also (only 80% of the time, still much better than idol 3). One of their fixes is to download SGS Screen Booster from the Play Store. Using the Super Optimized preset, I can say that double tap to wake works 10 out of 10 times in my testing.
https://play.google.com/store/apps/details?id=br.shop4apps.touchscreenbooster.com&hl=en
Click to expand...
Click to collapse
I tried this app and it seems to improve lag time when you open an app too! Great find!
OTA
An official OTA update has just been announced to fix the DTTW
Borghi said:
I tried this app and it seems to improve lag time when you open an app too! Great find!
Click to expand...
Click to collapse