Hi! Anyone using nova launcher on their xiaoxin tablet? Whenever my tablet wakes after long sleep, say overnight or longer, it launches in the multitasking pane instead of home screen. Not a big deal but a little annoying. Anyone else seen this?
I'm using the chineese stock rom btw.
I've never seen that and I also use Nova. But it might be because I've got mine set to go to sleep at 11:30pm everyday so it doesn't have a long sleep?
Never does it in the day though.
mardon85 said:
I've never seen that and I also use Nova. But it might be because I've got mine set to go to sleep at 11:30pm everyday so it doesn't have a long sleep?
Never does it in the day though.
Click to expand...
Click to collapse
Thx, I will try to turn that function on.
Related
I understand that there are a couple of topics opened for this but I wanted to have a new one with the title showing that a solution has been found as I want to help other who are experiencing the problem.
I'm not sure if this would resolve the issue for you but it did for me so please don't blame me if it didn't work for you, I say this because the solution requires an install of a paid app.
So I've had my transformer for 2 weeks and the SOD has been happening since day 1, it would happen every time I left my transformer asleep for more than 2-10 minutes (WIFI on or off). I've tried everything but could not resolve the issue. The only time the SOD didn't happen is when I had it plugged into the charger.
Solution: WidgetLocker, it's an SOD killer
All I did was install it and left everything as is, I also made sure that the stock lock screen is disabled.
I dont think it's widget locker that fixed the problem its disabling the stock lock screen. I had the sleep issue the first few days I had the xformer but after disblong the lock screen it went away.
Sent from my Transformer TF101 using XDA Premium App
I had SOD issues when I had Juice Defender installed. I knew it was causing the problem because it started happening right after it was installed. Haven't had one SOD occurrence since I removed it.
I had te stock lock screen disabled for days but the problem never went away until I installed widgetlocker.
I don't want to be a Debbie Downer, but I think you'll find the SOD will reappear when you least expect it. Mine didn't do it for well over a week after I fiddled with all the suggestions offered on this forum, and now it's just as random as ever. I hope 3.1 fixes this, but it sounds a lot like a Transformer issue rather than a HC issue, since you don't hear the Xoom or Iconia owners complaining about the same thing.
Anyone else tried this?
Thanks
the SoD is probably caused by the big frequency/voltage jump when you wake the system up. This is probably what's freezing the system. Someone with a rooted transformer that's having the issues should get the netformer kernel and sit minimum frequency to something higher (400~600 MHz) and see if they still get the problem.
FYI: We had the same problem with the HTC hero when some hero's would lock up when asleep when you set the minimum frequency too low which meant they made a big frequency jump when the screen got turned on.
I've got the acer and this happens all the time with it. I notice it also will randomly turn the screen on just sitting there. Wonder if it's just a 3.0 issue and not something just the asus has.
L0$t$0ul said:
I've got the acer and this happens all the time with it. I notice it also will randomly turn the screen on just sitting there. Wonder if it's just a 3.0 issue and not something just the asus has.
Click to expand...
Click to collapse
I don't think we've had the screen waking up issue.
It's been over 24 hours and not a single SOD since installing WL. I used to get it SOD every time I left my ASUS unused for few minutes.
If I use dock I never have that problem only without dock.
Glad to hear the wake issue isn't happening here. It's really annoying. Just had my acer not wake up again though. Happens at least once a day.
seshmaru said:
I don't think we've had the screen waking up issue.
Click to expand...
Click to collapse
Sorry bit I've only just found this thread. I too am suffering with the SOD after 5-10 mins of standby. But I also have the random "waking up" when in standby -sometimes after a couple of seconds, sometimes after a couple of minutes. Seems you can't rely on it doing what it is supposed to do i.e. sleep until woken !
steftymo said:
Sorry bit I've only just found this thread. I too am suffering with the SOD after 5-10 mins of standby. But I also have the random "waking up" when in standby -sometimes after a couple of seconds, sometimes after a couple of minutes. Seems you can't rely on it doing what it is supposed to do i.e. sleep until woken !
Click to expand...
Click to collapse
3.1 update fixed this for me and no Widgetlocker is needed.
I have an employee who we purchased a TF700 and dock back a few months back. Worked fine up till recently. After the JB update he seems to be having a strange issue, where the TF700 seems to be always running while docked even when closed and the tablet is supposedly asleep. The dock is hot to the touch on the bottom where the battery is, and the battery is competely depleted when he goes to use it the next morning. The screen does go into sleep mode, but something seems to be running constantly and depleting the battery. This does not happen when undocked. Any ideas what it could be or what he could try. Is there a keyboard firmware update for after JB.
Not sure where to start.
Thanks
Michael
guitar1969 said:
I have an employee who we purchased a TF700 and dock back a few months back. Worked fine up till recently. After the JB update he seems to be having a strange issue, where the TF700 seems to be always running while docked even when closed and the tablet is supposedly asleep. The dock is hot to the touch on the bottom where the battery is, and the battery is competely depleted when he goes to use it the next morning. The screen does go into sleep mode, but something seems to be running constantly and depleting the battery. This does not happen when undocked. Any ideas what it could be or what he could try. Is there a keyboard firmware update for after JB.
Not sure where to start.
Thanks
Michael
Click to expand...
Click to collapse
Try to freeze the Map app if you rooted and have Titinium installed, if you go to settings -> app --> uninstall the Map update. Let me know if this helps.
buhohitr said:
Try to freeze the Map app if you rooted and have Titinium installed, if you go to settings -> app --> uninstall the Map update. Let me know if this helps.
Click to expand...
Click to collapse
Thanks. Actually he took it home and deleted a bunch of apps he wasn't using and a wallpaper and then rebooted the unit and the problem worked itself out. We don't know which app was the culpret, but now it seems to be behaving fine. If he has any more issues I will tell him to look into the map update. He doesn't have the unit rooted though.
Thanks,
Michael
I always left my Galaxy S4 on all night long with an orbiting clock, dimmest screen, as my bed side clock. Obviously that's much more optimal with an OLED screen where the black area is actually off. On the Nexus 5, the whole panel has to be on all night long.
Anyways, using Dock Clock Plus to dim the screen all the way and orbit the clock to avoid screen burn in, I have been using the Nexus 5 the same way. On all night long as my clock. It worked fine for a few weeks but the last two nights I've woken up to see the screen all distorted and crazy looking.
I have to unplug the phone and turn the screen off and then it comes back mostly ok. A reboot fixes it 100%...though other factors may be involved. See the attached pictures of my screen.
So...is my phone defective? It works perfectly phone all day long after this happens...I'm not sure what triggers the problem but SO FAR, it doesn't seem to affect me.
Is it simply that an LCD panel cannot be left on all night like this? Thoughts, suggestions, RMA, live with it, etc.??
Thanks!
I don't think you have to worry about screen burn on the N5. I do the same except I just leave the click and widgets in one place. I don't see this issue but I think it may be software.
Also it may be the widgets you ate using for the daydream thing as well as any custom launchers which maybe caching the screen incorrectly.
obsanity said:
I don't think you have to worry about screen burn on the N5. I do the same except I just leave the click and widgets in one place. I don't see this issue but I think it may be software.
Also it may be the widgets you ate using for the daydream thing as well as any custom launchers which maybe caching the screen incorrectly.
Click to expand...
Click to collapse
Thanks for the feedback.
I am using Nova Launcher Prime and the clock is Dock Clock Plus. Never had this issue with the same setup on my Galaxy S4.
Any thoughts on how I can test out your theory if I leave it on again tonight and trigger the same occurrence?
Thanks
jeffreii said:
Thanks for the feedback.
I am using Nova Launcher Prime and the clock is Dock Clock Plus. Never had this issue with the same setup on my Galaxy S4.
Any thoughts on how I can test out your theory if I leave it on again tonight and trigger the same occurrence?
Thanks
Click to expand...
Click to collapse
Yeah,
For the launcher theory, right after you get this in the morning, go to Nova advanced settings and hit the restart Nova option.
For the widget, just try a different one. Maybe the default built-in clock.
obsanity said:
Yeah,
For the launcher theory, right after you get this in the morning, go to Nova advanced settings and hit the restart Nova option.
For the widget, just try a different one. Maybe the default built-in clock.
Click to expand...
Click to collapse
Thanks for your ideas. I think Nova is, in fact, responsible.
When it happened again last night, I opened and restarted Nova and it fixed it 90%. Another restart and 100%. I think tonight I will try to launch Dash Clock Plus from the GEL launcher and see if that makes a difference...if not, I'll try downgrading Nova from the beta to the latest stable release. Lastly, if that doesn't work, then it might be Dock Clock Plus and I'll have to try another Dock Clock.
Thanks again!
jeffreii said:
Thanks for your ideas. I think Nova is, in fact, responsible.
When it happened again last night, I opened and restarted Nova and it fixed it 90%. Another restart and 100%. I think tonight I will try to launch Dash Clock Plus from the GEL launcher and see if that makes a difference...if not, I'll try downgrading Nova from the beta to the latest stable release. Lastly, if that doesn't work, then it might be Dock Clock Plus and I'll have to try another Dock Clock.
Thanks again!
Click to expand...
Click to collapse
No problem. Based on your test I really think that if you just reinstall Nova it will fix your issues.
obsanity said:
No problem. Based on your test I really think that if you just reinstall Nova it will fix your issues.
Click to expand...
Click to collapse
So no issues at all last night after launching Dock Clock Plus from GEL launcher instead of Nova Prime.
Tonight I downgrade Nova Prime from beta to stable and test again, not using GEL.
If that works fine, I will try to replicate my problem by simply installing the beta again and seeing if it comes back tomorrow night.
obsanity said:
No problem. Based on your test I really think that if you just reinstall Nova it will fix your issues.
Click to expand...
Click to collapse
So not quite what I expected last night.
I uninstalled Nova Beta and installed the stable release. I turned on Dock Clock Plus and went to bed.
I woke up in the middle of the night and noticed it was distorting again...not what I expected.
Even worse, though, once I turned it on, it totally locked up. I spent 20 minutes trying to get it to clear itself up. Several reboots, crashes, freezes, still no dice. I could not get it stable. I even managed to uninstall Nova completely and get to the GEL launcher and still nothing.
The distortion/freezing/crashing was happening even during bootup, to the Google logo...I got into recovery/bootloader and STILL it was distorting/freezing/crashing. I thought my phone was done because half the time I turned it on, it would distort until the entire screen was frozen and I'd have to hard reset.
Finally, the only cure that I found was time. Turn it off and leave it off for a few minutes and it worked better...though after a few minutes of use it distorting.
I think that somehow, something is overheating internally and causing the issue. I'm not sure if it could possibly be Nova that's causing that...but I now know that getting away from Nova does not actually FIX it. Also, the "blame it on the beta" idea is out the window as well.
If I'm brave, I'll try again tonight to just use the GEL launcher instead of either Nova and see what happens, though I'm scared at this point. Thinking about an RMA.
jeffreii said:
So not quite what I expected last night.
I uninstalled Nova Beta and installed the stable release. I turned on Dock Clock Plus and went to bed.
I woke up in the middle of the night and noticed it was distorting again...not what I expected.
Even worse, though, once I turned it on, it totally locked up. I spent 20 minutes trying to get it to clear itself up. Several reboots, crashes, freezes, still no dice. I could not get it stable. I even managed to uninstall Nova completely and get to the GEL launcher and still nothing.
The distortion/freezing/crashing was happening even during bootup, to the Google logo...I got into recovery/bootloader and STILL it was distorting/freezing/crashing. I thought my phone was done because half the time I turned it on, it would distort until the entire screen was frozen and I'd have to hard reset.
Finally, the only cure that I found was time. Turn it off and leave it off for a few minutes and it worked better...though after a few minutes of use it distorting.
I think that somehow, something is overheating internally and causing the issue. I'm not sure if it could possibly be Nova that's causing that...but I now know that getting away from Nova does not actually FIX it. Also, the "blame it on the beta" idea is out the window as well.
If I'm brave, I'll try again tonight to just use the GEL launcher instead of either Nova and see what happens, though I'm scared at this point. Thinking about an RMA.
Click to expand...
Click to collapse
Definitely positively get it RMA. From what you just posted it looks like the screen connection is being affected by heat. Just get your data off of it before it goes dark completely.
Running kitkat stock, with nova launcher, I've noticed that if I try trigger Ok Google voice search while my phone is charging, it will only actually trigger and launch the search after I unplug the phone from charging.
Has anyone heard or read of this behavior before? It's very strange and I can't pinpoint when it started happening.
Thank you
Bump! Still looking for some help.
To summarize, Ok Google is not working while charging. Works fine when not charging. Use stock Kitkat 4.4.4 with Nova Launcher.
maybe its a nova launcher issue
I've noticed when charging, the phone will wake/activate Ok Google about 1/10 times. When not charging, it's pretty consistent.
At this point in testing, it's random for charging vs non-charging.
Is anyone here using Nova Launcher that can chime in?
I don't think it has anything to do with charging. I will say "Ok Google" and nothing will happen, then I turn on the screen and it pops up. I think it has to do with the screen being off and the device being in deep sleep or something. After I wake it up and turn it back off though, it will wake up the screen with the hotword.
EDIT: After re-reading, I'm now thinking you mean it wont work at all even with the screen on?
Just tested, and off the charger/on the charger doesn't matter, it's for sure a screen on/off issue.
This is odd, as it used to work on my charger at night, screen off, responding to "Ok Google", now it will only work with the screen on. Just confirmed this with 10 tests w/ screen on vs screen off.
Mysticodex said:
Just tested, and off the charger/on the charger doesn't matter, it's for sure a screen on/off issue.
This is odd, as it used to work on my charger at night, screen off, responding to "Ok Google", now it will only work with the screen on. Just confirmed this with 10 tests w/ screen on vs screen off.
Click to expand...
Click to collapse
Google has been updating and changing this feature quite a bit.
Sent from my Nexus 5 using XDA Free mobile app
G1ForFun said:
Google has been updating and changing this feature quite a bit.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Randomly yesterday while screen off and charging. OK Google woke up my phone. I am very confused at what could be getting into the way at this point.
I have disabled Xposed Framework, which includes GravityBox, and will continue testing.
The issue boils down to this, on or off the charger, it is delayed response to OK Google. Any ideas?
Has anyone else experienced this? It's kinda hard to explain, but often times when I press the back button, the phone either 1. ignores the press (though I can confirm the press is registered because it vibrates and I have "show taps" enabled) or 2. there's quite a bit of delay before the action happens.
Unfortunately I can't figure out a pattern when this happens or what triggers it. I don't have a screen protector. Is there any way to fix/change this? I am rooted.
I've been using gestures for a year. I was surprised at how quickly I got used to it and wondered why I resisted for what seemed like so long. I know it's not for everyone, but I don't notice this issue with the gestures. I've even implemented a few custom gestures through Nova Launcher Prime.
roirraW edor ehT said:
I've been using gestures for a year. I was surprised at how quickly I got used to it and wondered why I resisted for what seemed like so long. I know it's not for everyone, but I don't notice this issue with the gestures. I've even implemented a few custom gestures through Nova Launcher Prime.
Click to expand...
Click to collapse
I try to like gestures with every new phone. This time I completely forgot and I guess I'll give them a shot again but man they really don't click with me.
NSD said:
I try to like gestures with every new phone. This time I completely forgot and I guess I'll give them a shot again but man they really don't click with me.
Click to expand...
Click to collapse
Maybe they'll fix whatever the other issue is and you can go back to them eventually. Try them again after each month's firmware update (first Monday of each month, normally - some exceptions for holidays).