First off I hope this is the proper forum..
I'm running the latest version of CM7, and use the built in 'Car Home' app anytime I'm on the road.. The problem I'm having is that it takes several attempts to exit the app.. When it does my original home screen is slow to come back, and my calendar widgets need to be refreshed because they are all blank after exiting 'Car Home'. Has anyone else experienced this? Is there anything that can be done to fix it?
I've tried several other car apps but they all have speedometers and other things built in that I don't want or need.. I just really like how simple the CM7 app is..
Thanks..
Is your phone plugged in while you are in the car? I had a bad charger that would force my phone into car mode whenever I plugged it in.
Sent from my Inspire 4G using xda app-developers app
ddiehl said:
First off I hope this is the proper forum..
I'm running the latest version of CM7, and use the built in 'Car Home' app anytime I'm on the road.. The problem I'm having is that it takes several attempts to exit the app.. When it does my original home screen is slow to come back, and my calendar widgets need to be refreshed because they are all blank after exiting 'Car Home'. Has anyone else experienced this? Is there anything that can be done to fix it?
I've tried several other car apps but they all have speedometers and other things built in that I don't want or need.. I just really like how simple the CM7 app is..
Thanks..
Click to expand...
Click to collapse
Search for NoDock in playstore. App that fixed the issue for me. I would post link but can't.
thenorm89 said:
Search for NoDock in playstore. App that fixed the issue for me. I would post link but can't.
Click to expand...
Click to collapse
Thanks.. Gave it a try and so that looks like it did the trick..
Thanks again..
moutansos said:
Is your phone plugged in while you are in the car? I had a bad charger that would force my phone into car mode whenever I plugged it in.
Sent from my Inspire 4G using xda app-developers app
Click to expand...
Click to collapse
A friend of mine had the same issue after using his Kindle charger on his phone.
Related
Hi,
Since two days I'm a happy and proud Note owner, but there's one thing, that makes me really go crazy:
I installed the program "Widgetlocker", because the standard lockscreen is quite broing. It actually works quite good, but sometimes the standard lockscreen still apears. Not instead of the widgetlocker, but additional. So I always have to unlock two lockscreens.
Does anybody else has got this problem? And how can I fix it?
I tried to find a solution in different forums and in the program configuration, without sucess!
Thanks for help!
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
I turned on root helper and home helper in settings, that fixed it for me. I'm on Stock Rooted XXKK9 if that helps.
Sent from my GT-N7000 using xda premium
I presume you have set the lock screen to "none" in the actual phone settings too?
NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Where? Can't find any option like that....
Thanks for help
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
NZtechfreak said:
I presume you have set the lock screen to "none" in the actual phone settings too?
Click to expand...
Click to collapse
Lol, i accidentaly hit the thanks button. You're welcome!
Sent from my HTC Desire HD using xda premium
drjp77 said:
Hi, chrcad,
Finally, the someone else who's been having the same problem.
It IS really irritating. Sometimes it's OK, but other times it just comes on.
Have turned off the lock screen option, but same thing happens. Someone please help!
Sent from my GT-N7000 using XDA App
Click to expand...
Click to collapse
My widgetlocker works fine. Been using it since day 1. Hmm.. Sorry. Not sure how to help.
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
The_Steph said:
chrcad,
Your problem seems related to the fact that Android is not having enough memory left ans simply closes "useless" apps and considers that WL is part of them. To prevent that to happen, simply check in advanced settings the "refuse to suspend WL" box and Android will look another application than WL to close
Click to expand...
Click to collapse
Thanks @ everybody for the help, but unhappily it's still not working properly.
The problem always apperas, when the phone's sleeping and a gTalk message comes in.... but ONLY, when the gTalk ppop-up is activated......
Any (more) idea?
you are leaving it running all the time aren't you?
I use to have the same problem, very rarely but it was still annoying. I have put a lock on widgetlocker so if I ever close all programs, widgetlocker is still running. It's not happened since but it's only been a few days so I'll see.
chrcad said:
Edit: The error apears mostly when there's a pop-up (gtalk e.g.) or when I plug in the charger....
Click to expand...
Click to collapse
Some pop-ups cause this if they're designed to appear underneath the stock lockscreen rather than dismiss it.
For now:
1) Easy Wake Mode disables the system lockscreen
2) WL Settings > Long-press volume down for Experimental > Aggressive Dismiss stock lockscreen. This should work, but it's not well tested yet so it's off by default.
Ok, first of all I know this is going to sound dumb. The other day when I'd get a text message my phone would tell me with a voice that I've received a message and who it was from. Now it's not doing it. It just started doing it then stopped after a few days Did I turn off a setting or something? I'm stock rooted with Google now and wallet. Any ideas?
That's either driving mode or you messed with the accessibility settings. It's more than likely that you activated Driving Mode which is the notification bar and is very easy to tap accidently.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
That's either driving mode or you messed with the accessibility settings. It's more than likely that you activated Driving Mode which is the notification bar and is very easy to tap accidently.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yup, probably driving mode (although I don't know what driving mode is supposed to do other than announce texts/calls)
demarcmj said:
although I don't know what driving mode is supposed to do other than announce texts/calls)
Click to expand...
Click to collapse
yep, that was it. Thanks
I'd also like to know why they have put in a separate switch for this.. shouldn't it be incorporated into the dock mode?
dbow32 said:
yep, that was it. Thanks
I'd also like to know why they have put in a separate switch for this.. shouldn't it be incorporated into the dock mode?
Click to expand...
Click to collapse
Because not everyone has a dock for their phone when driving.
I had this happen to me when i pressed anything while in chrome. I guess it was "Missed It!" interfering or something. Weird.
T mobile us, rooted unlocked, never put custom Rom on it. I used to be able to tether even when screen shut off, now once the screen shuts off the data stops until I turn the screen back on. Any ideas how to fix this besides leaving screen on?
Not yet.
Sent from my HTC VLE_U using Tapatalk 2
horr1blek1tten said:
Not yet.
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
Bummer.
This actually had me thinking, since google play music is running before the screen shuts off and it constantly draws data, maybe thats why it stays active even when the screen is off. So I am going to have to test this theory by loading a huge webpage on the tethered device to see if you need a constant demand for data for tethering to keep working, I suppose I could just a youtube video.
Edit: My theory panned out and may lead to a fix. This is what I did
1) Turn on FoxFi an make sure screen doesn't time out 2} Tether my Asus Infinity to it making sure the phone screen doesn't time out 3) Start a long youtube video using the youtube app, I tried a 7 minute one. 4) Turn screen off on the phone and I was able to watch the whole video while tethered to my one s
My conclusion is if there is a constant data draw the tether will keep working even when screen is off. So they have enabled a rapid cutoff of wifi if your screen shuts off with no data draw, if there is a draw the data will keep flowing.
Test it out for yourself and share your results, off to try netflix.
Edit 2: Further testing confirms this on my device, This time I used netflix streamed dark of the moon and it continued to allow the tether to work. I dont want to burn my months data out testing this so we need a few more people to try this.
I have the EU rom but I'm experiencing the same issue.
I'm using Airdroid and it stops responding as soon as the screen shuts off. I can confirm that Ready2Mosh is right, since if I turn on the web radio and then shut off the screen Airdroid works flawlessly.
I have never noticed this before 4.0.4 so I'd guess the bug wasn't there. This is a major bug that has to be fixed soon by HTC.
What about 3g connection? Does it shut off too?
Does it do it if you just use the built in tethering app?
I don't think it is really a bug with android per se vs design
that is sleeping the app as backgrounded since screen is off and not being over riden anymore.
You're right. Tethering isn't put to sleep for me.
I can confirm the issue with airdroid and other apps though. I'm going to open a new thread in order not to hijack this one.
I tried airdroid and that works fine for me though.
TheArtiszan said:
I tried airdroid and that works fine for me though.
Click to expand...
Click to collapse
Really?? Thanks for the info.
I opened up terminal emulator, chose menu>activate wake lock and voilà! Everything's working fine for me now!
You can try this out too, who knows!
nor-ric said:
I opened up terminal emulator, chose menu>activate wake lock and voilà! Everything's working fine for me now!
You can try this out too, who knows!
Click to expand...
Click to collapse
Nope data still stops when screen goes to sleep, sucks.
Go to settings tap WiFi hit menu advanced keep WiFi on during sleep set it to always let me know if this works :banghead:
Sent from my HTC VLE_U using xda app-developers app
beccadevin said:
Go to settings tap WiFi hit menu advanced keep WiFi on during sleep set it to always let me know if this works :banghead:
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Nope, still stops.
I have a weird bug/problem. On my nexus 5, whenever i hangup a phone call the end button and screen do not go away. The back button does not work but the home and recent apps does. Any help would be appreciated. I can upload a video of the problem. MODS: sorry if this is the wrong area. please move if necessary.
thepoetlives89 said:
I have a weird bug/problem. On my nexus 5, whenever i hangup a phone call the end button and screen do not go away. The back button does not work but the home and recent apps does. Any help would be appreciated. I can upload a video of the problem. MODS: sorry if this is the wrong area. please move if necessary.
Click to expand...
Click to collapse
Having the same problem! really annoying!!! Was not how Nexus 4 was or any other phone I have used. There have been settings on some dialers of what to do after hanging up, like return to dialer, return to call log or home screen. None on this built apparently.
bjjere said:
Having the same problem! really annoying!!! Was not how Nexus 4 was or any other phone I have used. There have been settings on some dialers of what to do after hanging up, like return to dialer, return to call log or home screen. None on this built apparently.
Click to expand...
Click to collapse
I don't know what happened but mine seemed to either fix itself or was fixed when i erased play store app data.
I have that problem too (see attached photo). It's getting pretty annoying. Any ideas?
thepoetlives89 said:
I don't know what happened but mine seemed to either fix itself or was fixed when i erased play store app data.
Click to expand...
Click to collapse
Had the same issue. This fixed it. Thank you.
Sent from my Nexus 5 using Tapatalk
oldmanwinter said:
I have that problem too (see attached photo). It's getting pretty annoying. Any ideas?
Click to expand...
Click to collapse
Try wiping play store app data.
I tried wiping the just the general play store data before and it didn't fix the issue. Just wiped all play related data: magazine, books, etc and it solved the issue. Thanks
Sent from my Nexus 5 using xda app-developers app
My problem is eve weirder when I call someone it takes me to the homescreen and still makes the call but I can't access the dialer thing where you can hangup and stuff and when I get a call I can't answer it because it doesn't show up it just rings
Sent from my Nexus 5 using XDA Premium 4 mobile app
I have this screen issue too from time to time, exactly like the screenie above...button is just black.
I will try this fix...
Sent from my Nexus 5 using XDA Premium 4 mobile app
3's&7's said:
I have this screen issue too from time to time, exactly like the screenie above...button is just black.
I will try this fix...
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine helped clearing the Google Dialer data.
randomnoob83 said:
My problem is eve weirder when I call someone it takes me to the homescreen and still makes the call but I can't access the dialer thing where you can hangup and stuff and when I get a call I can't answer it because it doesn't show up it just rings
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i had the exact same issue, or more precisely :
I receive or pass a call. then, instead of going to the "in call" screen with the big red "hang up" button, i'm back to the home screen...
now this can happen, if i press the home button, but i don't. And if that was that, then first i would have the small "phone" logo in the upper left notification telling me i'm currently in call, and the "in call" screen would be accessible from the task manager, however the task manager displays absolutely nothing.... just like i wasn't making any call at all, except i can hear the person on the other side in my speaker.
Then i click on the big blue phone logo to get to the dialer screen, but i then get a screen which i never had before, with a black transparent background, proposing me to either use the default keyboard (if i click it i get the keyboard), either to "return to current call", and when i click it, i'm back to the homescreen... so the only way to hang up is to shut the phone down...
it's happened to me twice yesterday, but never before....
PS: just so we might find a common app that would cause the issue, i have installed on my N5 these apps :
dashclock
file manager
prochain bus
ridiculous fishing
sygic
today calendar
vlc
and thats all. Any of you have some apps in common ?
I also had the same issue during the first week or so...but with tym and aftr update the issue vanished!! Since 2014 i nvr faced this issue again!!
Sent from my Nexus 5 using Tapatalk
Different Dialer problem
Hi,
I am rooted running beanstalk. But before flashing had stock rom then Purity.
This problem happened after flashing Purity ROM.
When I make or receive a call, my screen goes blank and I cannot do,anything to wake the phone, unless the other party ends the call and then the screen may wake up if I touch the screen?!
Anyone else, please help.
bagou01 said:
i had the exact same issue, or more precisely :
I receive or pass a call. then, instead of going to the "in call" screen with the big red "hang up" button, i'm back to the home screen...
now this can happen, if i press the home button, but i don't. And if that was that, then first i would have the small "phone" logo in the upper left notification telling me i'm currently in call, and the "in call" screen would be accessible from the task manager, however the task manager displays absolutely nothing.... just like i wasn't making any call at all, except i can hear the person on the other side in my speaker.
Then i click on the big blue phone logo to get to the dialer screen, but i then get a screen which i never had before, with a black transparent background, proposing me to either use the default keyboard (if i click it i get the keyboard), either to "return to current call", and when i click it, i'm back to the homescreen... so the only way to hang up is to shut the phone down...
it's happened to me twice yesterday, but never before....
PS: just so we might find a common app that would cause the issue, i have installed on my N5 these apps :
dashclock
file manager
prochain bus
ridiculous fishing
sygic
today calendar
vlc
and thats all. Any of you have some apps in common ?
Click to expand...
Click to collapse
Exact same issue here. No app in common... Did you manage to fix it ?
Fixed mine by turning off developer options and then rebooting
I saw this issue posted on another forum by someone else with no responses. I know many of you here probably don't have the Facebook messenger app installed/enabled because of the the reports of battery drain but I figured I would try my luck and ask anyway as I have this issue as well now. If you do have the app installed, or are familiar with how it works, there is a quick reply emoticon button (default is thumbs up) to the right of the chat box which you can press once to send the emoticon (or hold the button to make it bigger). Several months ago this stopped working for me on my lollop Sprint Note 5. One day I just noticed the thumbs up icon stopped working. Pressing it makes the button depress action but then does nothing. Holding it to make the thumb bigger does nothing. Changing the emoticon default to something other than a thumb does nothing. Since the app is baked into the OS I can't completely get rid of it without root (to my knowledge). I tried deleting the cache, then the data, then "uninstalling updates," then reinstalling the updates, but the problem remains. I have submitted many feedback reports to Facebook through the app but have received no response. I don't know what else I can do at this point. Is there a way to contact Facebook and actually get a response?Any other suggestions on how I can get this to work?
Yea it doesnt work for me either
Sent from my SM-G928P using XDA-Developers mobile app
infamouzwt said:
Yea it doesnt work for me either
Sent from my SM-G928P using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like this other guy is using AT&T and has the problem as well.... I really wish I could get a response from Facebook. Is there any way to roll back the app to see which version broke it? http://forums.androidcentral.com/fa...cebook-messenger-quick-emoji-reply-error.html
In case anyone has been following this (doubtful) it looks like the issue was caused by something I did in developer options. I don't know which specific option it was that broke that function but when I turned it off and restarted the phone thumb button is now working. I will have to go through the options to see exactly what the problem one was.