S2W Phone Call Disabler
If you have sweep2wake enabled, you may notice the touchscreen is active while the screen is blanked during phone calls. This app will disable sweep2wake and doubletap2wake during phone calls and re-enable them with your previous settings after the call is finished. I couldn't find a way to do it reliably in the kernel, so I made this companion app. It will work with any Nexus 6 kernel that has sweep2wake.
It requires no configuration, just install it, and run it once. After that, it will automatically work, even after rebooting.
There is one option in the app. Since this app only needs to be opened once, you can click a check box that will remove this app from your app drawer. If you change your mind and want it back in the app drawer, you will have to uninstall and reinstall the app.
This app shouldn't use many resources. It runs an intent service when the phone state changes. That means the app wakes up, does its thing, and then stops itself. In other words, it is not always running in the background.
This app requires root!
Download:
S2WPhoneCallDisabler.apk
Please consider a donation to support ongoing development
Many thanks to those who have donated!
Thanks wanted to run your kernel but kept having issues in call.
My so glad to be able to run your kernel been with Vzw m8 for last year... an this app has worked great for me all day. An also I just wanted to throw out I'm on .24 an having zero call issues
3rd!
Works great thanks man
This issue bugs the crap out of me. I'm testing now. Thanks flar.
Nexus 6
I assume it's working good for everyone?
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Ngo93 said:
Working good for me I think I've had maybe 1 or 2 instances where the wake gestures didn't turn back on after a phone call, but it was probably just a fluke.
Click to expand...
Click to collapse
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Will do!
flar2 said:
I assume it's working good for everyone?
Click to expand...
Click to collapse
You have no idea. This app is pure genius.
Nexus 6
Not sure why but my copy doesn't have the option yo hide from the app drawer.
Great idea for this app, I'm surprised that there isn't greater call for it, or maybe I'm alone in having major screen issues when in a call with 2t2w enabled.
My issue is that it never turns double tap back on after a call. I'm using LK with it set up through lkconfig. Anyone know a solution to this? Thanks
Sent from my Nexus 6 using XDA Premium HD app
In fact I've experienced the same once or twice with ElementalX Kernel. I'm going to observe if it is happening again on my next call.
Edit: Tried it twice, no problems, so false Alarm. Everything working as it should be!
Thanks for the app, Flar2! I wrote a guide for this on my website (here), and also made a video tutorial:
https://www.youtube.com/watch?v=bHjN6jUdgzs
Feel free to use either, and thanks again for the great work!
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
datajosh said:
Suddenly seems to be happening for me a lot lately but I can't find a particular sequence of events that does it yet.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah it's been happening a few times over the last couple days, but nothing major.
Nexus 6
Great!
Works perfectly, and removed from the app drawer. Screen is completely unresponsive (as it should be) when on a call with the prox sensor covered.
Thanks for this!
Hey @flar2 ... I think I may have found a sequence that keeps disabling dt2w and s2w. It seems if I get a call and swipe to ignore the call within a second or two that it's disabling those two features, they only come back on after I re-enable them in your ElementalX app.
flar2 said:
Keep an eye on that and try to remember the exact sequence of events where it's not coming back. I don't talk on the phone much so it doesn't get much real world testing.
Click to expand...
Click to collapse
I've been getting this behavior lately where it would disable itself but it seems completely random to me.
Related
Ok so i am trying to determine what my problem is.. here are the symptoms. When i try and end a call i sometimes have to press multiple times or deliberately press and hold the end button and sometimes it doesn't respond pretty much at all. Also i am using go launcher and when i press icons that are in the dock bar they have the same issues. I also have similar issues when i text it's really annoying so is anyone else have similar issues?
Sent from my VS910 4G using XDA App
Same here. I've noticed that to hang up it takes a deliberate double tap. Also, the screen will sometimes become inoperable requiring a reboot. This has happened three times since first getting it. One note if that out happened twice stock, and once with decrapped 1.1
Any body else seen this?
Sent from my VS910 4G using XDA Premium App
I haven't seen it anywhere else, but I have seen the double tap on the end button to end a call. Seems to happen frequently. A "feature?"
Either way, it's annoying.
Running Go Launcher as well.
To me, it seems like it takes the screen a really long time to wake up from being off, in all cases - for example, dial voicemail and put the phone to your ear. When you get the prompt to put in your PIN, take it away and the screen comes on, try to punch the dialpad button immediately and it just won't work. I tried it as I was writing this and had to triple tap the button.
Same thing with the lockscreen (still on the stock lockscreen for now). The screen will wake up and it takes a second or two to even start to register finger swipes. It's really annoying...
Speaking of phone lockup, I received a call a few days ago and the phone froze - I couldn't answer the call, or do anything, all the while the phone just kept ringing. Had to pull the battery. I'm still on the stock ROM.
Me too! I had a call and it froze. Battery pull as well. Also, forgot to mention I am using open home launcher.
Sent from my VS910 4G using XDA Premium App
Yep it's a bug either in LG's function to turn on and off the screen in Android, or the kernel drivers that enable/disable the touchscreen. There is about a 1 second delay to it.
I discovered this lovely bug while porting the AOSP lockscreen mod.
I'll run some more tests to see whether it's an android bug or a kernel bug. I'm betting it's android (something like the screen being turned on before the touch controller has had time to reinitialize itself, or something more complicated like a race condition of some kind...)
Either way, with cm7 around the corner, I don't think it's that big of a bug
thecubed said:
Either way, with cm7 around the corner, I don't think it's that big of a bug
Click to expand...
Click to collapse
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
AndroidCraig said:
Errrr Are you sure the Revo is getting CyanogenMod 7? Where did you hear this and more importantly when will we get it?
Click to expand...
Click to collapse
Since he is the one working on getting it ported over, I think he has the best idea, and the only rule of cm is no asking for etas ;-)
Sent from my VS910 4G using XDA Premium App
5 times over the last few days my phone has called the last dialed contacts while sitting in my phone. I think it's something to do with removing the headphones (stock) while Spotify is playing as the last two times that's when it happened but it may be a coincidence as I can't replicate it.
Has anyone had this happen or heard of something similar?
Sent from my HTC One using Tapatalk 2
I had a similar problem that unlocked the lockscreen with just tapping the screen anywhere. Could it be that your phone is doing the same?
alonso_91 said:
I had a similar problem that unlocked the lockscreen with just tapping the screen anywhere. Could it be that your phone is doing the same?
Click to expand...
Click to collapse
I have that with my phone i can tap anywhere on the screen to unclock it, it doesnt matter what lockscreen i use^^
How do i get it back so its drag to unlock?
Wafflez_SE said:
I have that with my phone i can tap anywhere on the screen to unclock it, it doesnt matter what lockscreen i use^^
How do i get it back so its drag to unlock?
Click to expand...
Click to collapse
I'm not too sure what makes the lockscreen behave like that as I couldn't diagnose the problem properly.
Here's what i did just before the phone stopped doing it:
First I completely turned off the phone by long pressing the power button until the timer ran outThen I pressed the VOL- key while still holding the power button to go into bootloaderOnce in the bootloader I simply booted into recoveryFinally from recovery just held down power until phone booted up againI'm not sure which step fixed it for me if bootloader, recovery or simply completely turning off the phone but after i did that the lockscreen went back to normal.
I suggest you try every one of the steps once in order to better evaluate which step fixes this (if it fixes them at all)
Let me know how you get on
Tried those steps, unfortunately my lockscreen is acting as it did before. But thank you for your help
HTC One via Tapatalk 2
Wafflez_SE said:
Tried those steps, unfortunately my lockscreen is acting as it did before. But thank you for your help
HTC One via Tapatalk 2
Click to expand...
Click to collapse
No problem, sorry it didn't work like it did for me
I wonder why the lockscreen does that and if we are the only ones that have the problem
Arival said:
5 times over the last few days my phone has called the last dialed contacts while sitting in my phone. I think it's something to do with removing the headphones (stock) while Spotify is playing as the last two times that's when it happened but it may be a coincidence as I can't replicate it.
Has anyone had this happen or heard of something similar?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Are sure your not pressing play/pause on your headset twice . That dials the last number.
alonso_91 said:
No problem, sorry it didn't work like it did for me
I wonder why the lockscreen does that and if we are the only ones that have the problem
Click to expand...
Click to collapse
A factory reset fixed the problem
Skickat från min HTC One via Tapatalk 2
Wafflez_SE said:
A factory reset fixed the problem
Skickat från min HTC One via Tapatalk 2
Click to expand...
Click to collapse
Thanks for the tip its good to know, hopefully someone will find some other way to fix it without losing apps and data
If you're experiencing the bug where pressing anywhere on your One's lockscreen causes it to unlock, you've prolly got an app installed that has an Accessibility Service component to it. If you have any Accessibility Service enabled, it will cause this bug. (Light Flow and the Pebble smartwatch apps are 2 common apps that use an Accessibility Service).
On your phone go to Settings: Accessibility and look under Services. If anything there is enabled, disable it and that should stop the lockscreen from behaving this way.
This bug will also cause the phone to answer any incoming call if you press anywhere on the lockscreen while your phone is receiving a call.
ranphi said:
If you're experiencing the bug where pressing anywhere on your One's lockscreen causes it to unlock, you've prolly got an app installed that has an Accessibility Service component to it. If you have any Accessibility Service enabled, it will cause this bug. (Light Flow and the Pebble smartwatch apps are 2 common apps that use an Accessibility Service).
On your phone go to Settings: Accessibility and look under Services. If anything there is enabled, disable it and that should stop the lockscreen from behaving this way.
This bug will also cause the phone to answer any incoming call if you press anywhere on the lockscreen while your phone is receiving a call.
Click to expand...
Click to collapse
Thank you for that now I finally know what causes the bug, any way to fix it? Or are there any Roms with the bug fixed?
alonso_91 said:
Thank you for that now I finally know what causes the bug, any way to fix it? Or are there any Roms with the bug fixed?
Click to expand...
Click to collapse
I'm not aware of any way to fix it, unfortunately. Wish I knew a way, believe me, because this issue is keeping me from using the full functionality of my Pebble smartwatch with my HTC One. :crying:
I've actually mentioned this bug to a couple of HTC employees in a thread on Reddit here:
http://www.reddit.com/r/Android/comments/1d6we1/hello_from_htc/?limit=500
and one of them has already brought this to the attention of some HTC engineers, so hopefully it will be fixed with a future update!
ranphi said:
I'm not aware of any way to fix it, unfortunately. Wish I knew a way, believe me, because this issue is keeping me from using the full functionality of my Pebble smartwatch with my HTC One. :crying:
I've actually mentioned this bug to a couple of HTC employees in a thread on Reddit here:
http://www.reddit.com/r/Android/comments/1d6we1/hello_from_htc/?limit=500
and one of them has already brought this to the attention of some HTC engineers, so hopefully it will be fixed with a future update!
Click to expand...
Click to collapse
Cheers, it's almost certainly the pebble doing it then; it's seemingly happening whenever I pull out headphones that have a microphone and button, while music is playing through Spotify and my pebble is connected.
Sent from my HTC One using Tapatalk 2
thanks for the info, this has been driving me crazy as well.
i have found that killing the lockscreen with a task killer will revert it back to pull to unlock for a while for some reason.
As most of us know our beloved Note (1) doesn't have the "notifications LED" present in so many dumber and older phones.
After completely breaking the power button from just checking if there's any notification I've got a new phone and I'm on a quest for finding some alternative notification.
So, it seems that in order to actually GET that there's some notification you need to have talkback enabled and that's buggy (you get this spooky voice when doing certain tasks). FINE, I disabled (freeze) both samsung and google TTS (although I didn't really wanted, but OK). Then I get a hand icon in the notification area with "talkback activated". Ok, FINE. I'm using Flashlight Notifier (which flashes the camera LED) and it seems to be somehow working, except that it leaves the (camera) LED turned on continuously!!!
I seems that there's some other option to flash the soft buttons backlight but it needs some very old (I think GB) ROM and I'm not going there. For what is worth I'm on a stock new JB with speedmod kernel.
In short, any solution that "just works", getting extremely frustrated with all the stupid problems I run into? I need notification for gmail, hangouts, sms, missed calls, nothing fancy.
Whats wrong with vibrate and message/ring tone?
This is question. So should be in Q and A thread
a. vibrate/ring disturbs people around (especially when there are at least 10-20+ notifications coming every day)
b. you might step out briefly and you might not take the phone (all the time...) with you to WC and such. Yes, some applications allow for repeat rings (like the default SMS app) but that only makes (a.) worse
I think it is good to be able to just look at the phone and see that you don't want to turn the screen on as opposed to turning the screen on, see you don't need anything from there, turn it off.
If a mod wants to move the thread please and thank you.
https://play.google.com/store/apps/details?id=com.itsme4ucz.screenoff
Thanks, interesting but not at all what I want. Just want something to blink reliably ...
There's a whole cohort of software that does that but is usually geared towards making the "real" notification LED blink in various colours and also it usually shares the talkback (samsung) bug (but I'm willing to work around it).
d210 said:
Thanks, interesting but not at all what I want. Just want something to blink reliably ...
There's a whole cohort of software that does that but is usually geared towards making the "real" notification LED blink in various colours and also it usually shares the talkback (samsung) bug (but I'm willing to work around it).
Click to expand...
Click to collapse
try NoLed from play store, there is a thread for the same in XDA too.
d210 said:
Just want something to blink reliably ...
Click to expand...
Click to collapse
Fork this, modify it any way you like, compile and bob's your uncle.
treacherous_hawk said:
try NoLed from play store, there is a thread for the same in XDA too.
Click to expand...
Click to collapse
Thanks. Is it a warlock...
Sent from my GT-N7000 using xda premium
dsmas said:
Thanks. Is it a warlock...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
did not get you. warlock (literal meaning?, some user?).
none that dont cause severe wakelock lol
Sent from my GT-N7000 using Tapatalk 2
Typo error. Sorry.
Sent from my GT-N7000 using xda premium
NoLED seems to be fine (I was thinking for a long time that on OLED it might be a good idea to have some "few pixel" notifications, although I understand there is still significant power consumption even with OLED and few pixels on).
The device still deep sleeps (at least without notification) but of course this is the type of thing liable to kill the battery overnight.
Still, it works great and for most notifications I need it doesn't even need talkback (that's a big plus because I don't have to freeze TTS). And it looks great! Will report later or tomorrow how things go, with my luck I'll run into some issues in no time.
wow
treacherous_hawk said:
try NoLed from play store, there is a thread for the same in XDA too.
Click to expand...
Click to collapse
I was looking something like this. (It has many options / choices).
Thanks.
baz77 said:
none that dont cause severe wakelock lol
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
The battery drain was extra 2-3% while me and the phone were sleep from 10pm to 6am. Acceptable. Good. With setting - noled always on and battery % while charging on.
Thanks.
Sent from my GT-N7000 using xda premium
lol, maybe they obtimized it, that is good news if true. The wakelock occurs when not charging btw.
Thank you everyone!
NoLED is great for now, battery life is good, it catching all I want (maybe except hangouts) without enabling accessibility and is better than I dreamt.
Maybe, maybe a little concerned with display life now (it looks like there is still some kind of backlight, not only the small icons) but overall it looks good!
Maybe some option to blink the camera LED would still be good but you can't have everything.
I love this device but it has a couple of issues. I thought it would be helpful to list bugs in this first release of the software. I'm not rooted. These are mine:
Haptic feedback on menu keys sometimes stops
Air Command has stopped working. Its intermittent.
Sound controls sometimes don't allow me to make changes (right now I can't change notification sound level)
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Another annoying bug is that AVRCP 1.3 does not seem to be implemented properly.
Song/Media metadata does not get properly sent via bluetooth to receiving devices. This has been seen as not working at all to song information getting stuck on display and not changing when tracks change.
I'm definitely looking forward to a big fix for this one.
This has been seen on ATT, Tmobile, and Sprint variants.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Gary02468 said:
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Click to expand...
Click to collapse
You have to edit some code to allow video call on LTE. changing a 0 to a 1. Google to learn how. Can be fixed
wdkingery said:
You have to edit some code to allow video call on LTE. changing a 0 to a 1. Google to learn how. Can be fixed
Click to expand...
Click to collapse
But the workaround requires rooting, doesn't it? (For me, the disadvantages of rooting at this point outweigh the benefit of Hangouts via LTE.)
Gary02468 said:
I myself have not encountered the haptic-feedback, air-command, or sound-control problems.
The one problem I've found is that Google Hangouts won't do video calls via LTE. It pops up a message saying a WiFi connection is required instead. (The Note 2 used to have the same problem on ATT, but it was fixed about a month ago.)
Click to expand...
Click to collapse
Edit. Just saw you dont wanna root
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Gary02468 said:
But the workaround requires rooting, doesn't it? (For me, the disadvantages of rooting at this point outweigh the benefit of Hangouts via LTE.)
Click to expand...
Click to collapse
Whats the disadvantages to rooting?
The only bug that I have noticed is sometimes when I get an email notification from the stock email app, it appears in the status bar and then disappears within a couple of seconds. I've seen this a couple of times.
I guess we have to expect some issues since this is the first device out of the box with 4.3.
I really wish they would allow the widgets on the lock screen while having a pin for security. At least read only.
Unhived__Mind said:
What['re] the disadvantages to rooting?
Click to expand...
Click to collapse
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
screen and sound
has anyone noticed occasional brightness flickering? I thought it might be adaptive display or something like that, and i disabled it all, but I still see it.
also, I'm not sure what in the world happened, but my phone started randomly playing music. the music player didn't open, I had air gestures, off, and it wasn't ringing. I turned off wifi and the music stopped. In fact, i don't even think I have the song that was playing saved to my phone.
nespid said:
has anyone noticed occasional brightness flickering? I thought it might be adaptive display or something like that, and i disabled it all, but I still see it.
also, I'm not sure what in the world happened, but my phone started randomly playing music. the music player didn't open, I had air gestures, off, and it wasn't ringing. I turned off wifi and the music stopped. In fact, i don't even think I have the song that was playing saved to my phone.
Click to expand...
Click to collapse
Ghost in the machine....
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Gary02468 said:
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
Click to expand...
Click to collapse
Rooting any device voids warranty. It does not trip the flash counter or Knox. Just flash back to stock or supersu unroot.
As for the other stuff, no issues here. Phone is as stable as it was on stock. Runs even better because debloated it myself.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Gary02468 said:
Some of the disadvantages are:
* If I screw it up, I could brick the phone, or at least make the phone unavailable while I have to spend a lot of time fixing it.
* Rooting will wipe my existing setup, requiring more time than I want to spend to re-initialize my phone.
* There may be security, stability, or performance problems that have not been discovered yet.
* If my phone exhibits any subsequent problems, even if they're not actually due to rooting, I won't have any easy way of knowing whether that's the case.
* I don't know whether rooting may interfere with subsequent OTA updates (unless I go to the trouble of flashing back to stock first).
* No one can rule out the possibility that rooting will void the phone's warranty.
Click to expand...
Click to collapse
Good summary!
Sent from my SAMSUNG-SGH-I317
Using Google Music over headphone aux cable, setup eq the way you want, listen for a sec and slide the track knob to another part of the song. The eq turns off. If you go in to the eq settings, it is showing on. Toggle off and on and you will hear the difference.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I don't have any of the bugs being list here. However, when I have S Voice on for wake up when the screen is off, it will sometimes turn on randomly even when nothing is said. Happened in a movie theater for me and it was embarrasing. That feature is now off.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Anyone else having problems using whatsapp with pen window?
It seems that when I minimise it from a conversation I then can't open it again or move the icon around on the screen.
Works normally if I press back to the conversation window first though
S voice gets weird with me too. Had it in hands free mode and it kept telling me something about my safety while it simultaneously read my text out loud. it kept getting stuck in that loop for any new messages.
lax_22 said:
Anyone else having problems using whatsapp with pen window?
It seems that when I minimise it from a conversation I then can't open it again or move the icon around on the screen.
Works normally if I press back to the conversation window first though
Click to expand...
Click to collapse
Same here
Screen brightness and
Screen brightness issue: occasionally, when brightness is set low (not auto), when phone is turned on, screen turns on at full brightness for a split second then go to low setting level. Happens about 25% times.
Haptic feed back when screen off: after I turn screen off, if I move phone, I get a haptic feed back once. Doesn't repeat until I turn screen on and off again.
Edit: this is caused by 'smart alert'. Under Controls -> Motions. It vibrates when you pick up the phone and you have a notification and the screen is off to let you know there is something you missed.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Anyone having internet problems? When I'm on wife or 4G lte, the stock browser will get halfway through loading a Web page, then it will just hang there for a little.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Does anyone know how to completely remove setspu files? I have tried to wipe it, unstall it and for some reason whatever it does to modify the hardware is still there. I am having issues with incoming calls with this app. The diealer doesnt show up when i get an incoming call.
Thanks
stas333 said:
Does anyone know how to completely remove setspu files? I have tried to wipe it, unstall it and for some reason whatever it does to modify the hardware is still there. I am having issues with incoming calls with this app. The diealer doesnt show up when i get an incoming call.
Thanks
Click to expand...
Click to collapse
uninstall setcpu, its been a long time since its been updated. last time it was updated was in april of 2013! it doesnt work right with lollipop nor with the nexus 6. there are many cpu control apps that work with lollipop and the nexus 6, setcpu is not one of them.
simms22 said:
uninstall setcpu, its been a long time since its been updated. last time it was updated was in april of 2013! it doesnt work right with lollipop nor with the nexus 6. there are many cpu control apps that work with lollipop and the nexus 6, setcpu is not one of them.
Click to expand...
Click to collapse
thanks. but unstalling it doesnt make things better. the dialer still doesnt show up.
stas333 said:
thanks. but unstalling it doesnt make things better. the dialer still doesnt show up.
Click to expand...
Click to collapse
did you try rebooting? when you have an incomming call, how do you know?
simms22 said:
did you try rebooting? when you have an incomming call, how do you know?
Click to expand...
Click to collapse
yup. it rings and vibrates but the screen stays dark or if its on, the dialer doent pop up. After pressing the power button, i get the missed call notification
stas333 said:
yup. it rings and vibrates but the screen stays dark or if its on, the dialer doent pop up. After pressing the power button, i get the missed call notification
Click to expand...
Click to collapse
are you wearing a screen protector or a case? try taking the case off then have someone call you. its a known issue when wearing certain cases.
simms22 said:
are you wearing a screen protector or a case? try taking the case off then have someone call you. its a known issue when wearing certain cases.
Click to expand...
Click to collapse
not a screen protector issue. had it on for about 2 weeks without issues. installed setcpu last night and not im having issues. doing a factory reset resolves the issue but then im too lazy to download all my apps and set it all up. so, im looking for the files that setcpu modifies or adds so i can delete/edit them.
Figured it out. I simply had to reset app preferences. somehow installing setcpu caused them to get all messed up
stas333 said:
Figured it out. I simply had to reset app preferences. somehow installing setcpu caused them to get all messed up
Click to expand...
Click to collapse
nice
and try trickstermod instead.
simms22 said:
nice
and try trickstermod instead.
Click to expand...
Click to collapse
I like SetCPU because I can make profiles. For example, my kernel is set 300-1247 with screen is of, another setting is when the phone is in call, and full speed when screen is turned on.