Related
I was unable to find any setting to allow the screen to remain on while the phone is charging.
It would be nice to have for the Home and Car apps
It's under "development" where you turn on and off usb debugging.
Sent from my SGH-T959 using XDA App
on a side note, as slow as the phone charges, it will barely keep up with screen on running a live wallpaper.... i was watching voltages and temps this morning...
CM needs to up charge voltage like he did on the g1
Now that it's updated to Froyo, how do you keep the screen on while charging? Especially hate it wen on G-maps and it keeps shutting off.
I think there are widgets but I thought you had to enable them first before running any other app.
Thanks guys for all the knowledge.
I am running into this also, I know that there was an option to keep the display on always while charging but that option is gone the way of the dodo...
Currently running
2.2
Kernel 2.6.32.9
Build is FROYO.UVKB5
If you can list a widget or even a change to the build.prod that could be changed or added that would be great.
Any change of getting a build.prod from an eclair build maybe there is a difference that could be found, maybe this functionality could be added back in or made accessible.
try screebl from the market.
mine is under development
On my phone, it's under development also.
Sent from my SGH-T959 using Tapatalk
This option is not available on some roms. I had it in eclair.ji6. I'm running stock froyo.uvka6, not there anymore.
I now use Widgetsoid ($1.46) which has a widget to toggle screen always on.
https://market.android.com/details?id=com.jim2&feature=search_result
I searched the market and there appears to be a utility just for keeping the screen always on. I haven't tried it, just posting it in case you want to try it.
Screen On (free)
https://market.android.com/details?id=gr.androiddev.ScreenOn&feature=search_result
Screen Suite Lockscreen also has an option to keep screen always on.
Screen Suite Lockscreen ($1.99)
https://market.android.com/details?id=com.appsbeyond.android.screensuite&feature=search_result
I found a bug about BLN.
My phone gets freeze when i have more than one missing calls. Somebody gave me two or more calls while i didn't notice my phone. When i noticed it, i can't switch on the phone but doing a battery pull.
It's not related to other mods such as BLD, TW, too low min cpu freq, live OC, deep idle and undervolted. Because i've switched all options on and off respectively under the same scenario when the problem occurred.
Finally i turned off the Blink Status (status can be switched on though), my phone can be able to have more than one missing calls without the problem.
My settings are as follows:
ROM: IMM26 4.0.4 port form ns4g by evilisto
Kernel: Air Kernel v3.4.5
Maybe some devs can solve the problem
kwokyu127 said:
I found a bug about BLN.
My phone gets freeze when i have more than one missing calls. Somebody gave me two or more calls while i didn't notice my phone. When i noticed it, i can't switch on the phone but doing a battery pull.
It's not related to other mods such as BLD, TW, too low min cpu freq, live OC, deep idle and undervolted. Because i've switched all options on and off respectively under the same scenario when the problem occurred.
Finally i turned off the Blink Status (status can be switched on though), my phone can be able to have more than one missing calls without the problem.
My settings are as follows:
ROM: IMM26 4.0.4 port form ns4g by evilisto
Kernel: Air Kernel v3.4.5
Maybe some devs can solve the problem
Click to expand...
Click to collapse
I can also confirm something similar like this. Also AirKernel v3.4.5, 4.0.4 PixelRom (even tho I think I had this on 4.0.3 roms, too). Buttons blink, but can't turn on my screen. Even music went till the end of song, didn't go to next song, and then I removed battery. No LiveOC nor OC, no DeepIdle...
Sent from my Nexus S using xda premium
Doesn't happen here:
Left 3 missed calls in my cellphone, buttons blink as they should, and phone wakes up as it should.
BLN Pro, but didn't happen in the free version either.
robrob777 said:
Doesn't happen here:
Left 3 missed calls in my cellphone, buttons blink as they should, and phone wakes up as it should.
BLN Pro, but didn't happen in the free version either.
Click to expand...
Click to collapse
What rom and kernel do you use?
kwokyu127 said:
What rom and kernel do you use?
Click to expand...
Click to collapse
This is my setup:
http://forum.xda-developers.com/showthread.php?p=22328954#post22328954"
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
adamsilver1987 said:
Currently running timurs rom but it crashes a lot. Are there other roms that allow fast charge, sleep/wake with power, on screen volume etc.
Any help greatly appreciated
Click to expand...
Click to collapse
I've been running Timur's ROM as well and I really want an alternative as well as I've been facing issues with the ROM, and it looks like Timur has discontinued development on the 2012 model.
From what I've seen so far though CM11 should support USB DACs so I'm keen to try that out.
Some notes:
Fast charge - that's a kernel setting so any custom kernel should allow that.
Sleep/Wake on power - After many months of usage, sleep or even firm sleep has been a hit or miss for me. When it works, it works really well but sometimes a some random app might cause a wakelock, draining the battery. Even otherwise, there are many other issues such as USB audio doesn't resume. Plus the battery tends to drains quicker + looses health because of being in a hot car.
So instead, what I'm planning to do, is to just completely shutdown/boot up a tablet on power. Some notes:
- Bootup time is fairly quick - about 30 seconds, upto a minute, which is acceptable for me. You can reduce the startup time even further by using apps like BootManager to prevent unnecessary apps from starting up. Perhaps we can slim down the ROM further by deleting unnecessary apks etc.
- Fresh start is always a better option - you don't want your tablet to crash while driving right? I've had to reboot many times before or during driving, and it annoys me to say the least.
- USB audio always works fine when booted (well, with Timur's ROM anyways, need to test with CM11/others)
- No battery drain due to device standby or wakelocks
- No overheating and loss of battery health
- For shutdown on power loss, we can use Tasker. Maybe make a script to first turn the screen off, and after say 10 minutes of idle turn off the device completely (this will give us a chance to resume quickly in case we stopped the car for some reason).
- For startup on power, we can use the fastboot oem command to make the device automatically power up
On-Screen Volume: From daily usage, this hasn't been very practical in reality. I mean if you're driving, you really shouldn't be looking at the screen and trying to aim at the tiny buttons. Instead, a better option would be to use gestures to control the volume. There are heaps of apps for this, eg: All In One Gestures, Tasker, Gesture Navigation, GMD GestureControl, etc. You could use a single-swipe down and swipe-up to increase the volume up/down. Swipe left/right to change tracks. Two finger swipes to switch between apps. Just use your imagniation.
Might seem like a lot of work initially, but IMHO it'll be worth it, at least to get a stable ROM which is updated regularly (not to mention, you get to use the newest GApps!).
My only concern is to get the DAC working on startup. Might have to look into Timur's startup scripts to see how he does it - maybe even port the FHD scripts over to 2012 if necessary.
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
adamsilver1987 said:
do you have a link to any fast charge kernels ? all i can find is Timurs ?
thanks
Click to expand...
Click to collapse
Kang-aroo kernel.
http://forum.xda-developers.com/showthread.php?t=2558717
Supports fastcharge, OTG, hotplug DAC, firm sleep, multiboot and more.
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
adamsilver1987 said:
thanks. this may sounds stupid ( im new to this rooting thing etc ) i am running paranoidandroid ROM. seems to run smoothly. i have flashed/installed that kernel and nothing is different. no extra settings etc? am i doing something wrong ?
thanks again
Click to expand...
Click to collapse
Use a kernel tweaking app, like TricksterMod.
ok downloaded that and it means nothing to me im afraid. how would i turn on fast charge for example or OTG host mode, firm sleep etc ?
only thing i can find where i assume you can set things is the " SysCtrl Editor" but it jsut comes up with a huge list of stuff that i have no idea about.
i assume i need to find fast charge in sysctrl and change it from 0 to 1... but cant find anything under the search. not a clue what id be looking for
starting to think Timurs rom was simple compared to this. haha
thanks for the help
Use PowerEventManager:
http://forum.xda-developers.com/showthread.php?p=50265682#post50265682
i saw that, but yet again. dont know how to use it ? where do i place it on the tablet. it doesnt show up in recovery mode
You have to install it. Copy it to your device and then use a file manager to open and install it. It will create an icon in your drawer. When you open it, you'll have options to configure firm-sleep etc.
Done. Worked at first but now I've reverted to timurs rom. The tablet froze loads. Wouldnt open some apps at all and power on/off with ignition wasn't reliable. Sometimes it woke, sometimes it didnt. Will give it another go when i habe more time i think.
On a related note, I haven't had much luck with getting my DAC to work with other ROMs - even with Kang-aroo kernel. I'll have to try CM11 with _crue_'s USB audio patches and Netfluke's kernel this weekend and see how it goes.
Edit: No luck. Maybe because it's I'm on tilapia. Even with cm11, Netfluke's latest kernel, and _crue_'s updated audio patches for cm11, couldn't get it to work. And it's a Fiio E17, which I've had no issues with on Timur's ROM.
And no, I'm not going back to Timur's CM10 - it's old. I can't use any of the newer GApps on it, and the ROM is buggy.
I think I'll swap my tilapia with my 2013 deb and use that as a car device instead. It looks like Timur just updated his kernel to v1.0 which fixes a lot of bugs - at least it's being actively developed. As for my tilapia, I'll switch to a more stable/mainstream ROM like Omni and forget about USB audio for now.
Where did u get timurs updated kernel? Cant find a link
adamsilver1987 said:
Where did u get timurs updated kernel? Cant find a link
Click to expand...
Click to collapse
Oh, you'll have to donate for now, but it should be made public soon.
How much and where?
Thanks
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
Hi everyone,
I've got a very annoying problem with my S5, but I think it was already there with the S4...
The thing is: When my phone is in "standby", then I often don't get notified if a new Hangouts message or email arrives. This is happening on CM 12.1, but I'm pretty sure it was also happening on official Samsung 5.0 ROM. I thought it might be my Pebble (or rather it's corresponding app) that caused this, but I now have a Sony SmartWatch 3, and it seems the problem is still there. If does not always happen, sometimes it can be OK for a day, but then it's back the next day. Sometimes it takes 5 Minutes for the Notification to appear, somtimes 1-2 hours. Sometimes all the backlogged notifications get pushed to the phone when I leave house and the WiFi connection changes over to LTE, sometimes it triggers when I turn on the screen, and occasionally I have to turn on the S5, unlock, open Hangouts, select a conversation thread, wait a minute, and then the backlogged messages will appear.
It seems, that Android randomly decides "not to bother" looking for new incoming messages. It just collects them on the server, but doesn't push them to the phone.
This completely erratic behaviour is driving me nuts, and I have no idea how to fix it. I'm not using any batterysaver, RAM-wiping or other potentially interfering apps, no "Priority mode" or anything. The problem has persisted more or less unchanged through several OS transitions and factory resets.
I'd be eternally grateful for any help!
Thanks!
Do you use which S5 version? G900F?
Yes, 900F
Go to the advanced wifi options and check such settings named like "wifi standby" or "wifi sleep".
Wifi is "always on" in standby. At least that's what the setting says.
Ok and you use a custom rom or stock?
Currently CM12.1 latest nightly, but pretty sure it happened on Stock as well.
I use a custom kernel and can change the governor. After that change the notifications comes without an delay. Is that an option for you?
If you want you can change the governor without a custom kernel. You have to install this app: Trickster Mod
Enable root in the developer options from CyanogenMod. Trickster Mod needs root.
Thanks. I'll try that. What Hovernor do you use? I liked Intelliactive when I ran custom kernel.
I use the Boeffla kernel. In this kernel the zzmoove governor is available. That's the best gov in my opinion.
The Interactive gov is a good option too or the intelliactive how you said.
Damn. Kernel was already on Interactive ...
Than change it to another. Do you have some more options?
I'll try that. I just used an app to check for problems with connectivity, but that came up with nothing. The phone does not lose connection (app checks every minute to ping a certqin server) , the notification service simply seems to pack up.
Maybe I'll revert to TouchWizz and see how it goes there... Oh dear... I hate TouchWizz...!
TW is crap. Try another governor and give me a short feedback.
Here you can read more about all govs:
http://forum.xda-developers.com/showthread.php?t=1767797
I know about governors, but don't have any decent ones in CM at the moment. I'll look for a custom kernel.
Flash the Boeffla kernel. Boeffla at its best! Take the newest test kernel and not the stable, because the stable is not stable [emoji6]
Ok, I'll give it a go. I sort of doubt it'll be the answer, because this feels more like a problem buried somewhere in CM than a Kernel issue, but I might get lucky. It's really extremely annoying!!!
The strange is that nobody has such problems like you with original CM kernel. I used the original kernel 2 weeks and there was no problems with the notifications.
I found a promising lead, something about a new Wifi optimizasion (arp offloading) that could be turned off in KK but no longer in LP and causes problems like this. Trying to turn it off manually now. Also, apparently there are problems with IPv6, so I'll try to turn that off as well if I can find out how...
OK please let me know when you find it and if it works or not [emoji3]