my phone has this really weird thing going on. sometime when im using the phone or watching videos it suddenly vibrate and is like its being tap. can any help me or give any sort of explanation ?
MonsterMonsteur said:
my phone has this really weird thing going on. sometime when im using the phone or watching videos it suddenly vibrate and is like its being tap. can any help me or give any sort of explanation ?
Click to expand...
Click to collapse
Your getting a message? Tapping the Hard/Soft Keys? Tapping an option which has vibration to it? Receiving a notification?
penguin449 said:
Your getting a message? Tapping the Hard/Soft Keys? Tapping an option which has vibration to it? Receiving a notification?
Click to expand...
Click to collapse
there is no message.did not touch the phone at all.no notification .i am starting to hate my phone now.
Which ROM are you using ?
Sent from my HTC Desire C using xda app-developers app
TheRedHunter said:
Which ROM are you using ?
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
MiniProvisionMOD V2. but it also happen on Darkbreed IIl and Miui v5
that probably looks like a digitizer problem btw r u hooked up to charger or connected to pc/lappy when this happens ? coz if that is so then its probably excessive charge on ur digitizer , either ways disconnect if connected to charger usb etc power down pull out the battery and wipe ur display with a sightly damp cloth and leave d device for abt half an hour then try bootin and c if d problem persists good luck!
lead3r1 said:
that probably looks like a digitizer problem btw r u hooked up to charger or connected to pc/lappy when this happens ? coz if that is so then its probably excessive charge on ur digitizer , either ways disconnect if connected to charger usb etc power down pull out the battery and wipe ur display with a sightly damp cloth and leave d device for abt half an hour then try bootin and c if d problem persists good luck!
Click to expand...
Click to collapse
my phone was not connected to anything . so how do i fix it?
If you have a terminal emulator and root permissions, try running logcat and see if it picks anything up. You can continue doing whatever you're doing, just make sure the emulator icon stays in your notifications.
How often does this happen?
as long as no options dont get selected when d phone randomly vibrstes maybe u shuld try disablin vibrate on touch option in setrings/sounds and see if it persists
soupmagnet said:
If you have a terminal emulator and root permissions, try running logcat and see if it picks anything up. You can continue doing whatever you're doing, just make sure the emulator icon stays in your notifications.
How often does this happen?
Click to expand...
Click to collapse
i could get a logcat but i don't know how.
it does not happen often but when it happen it keeps happening on and on
MonsterMonsteur said:
i could get a logcat but i don't know how.
it does not happen often but when it happen it keeps happening on and on
Click to expand...
Click to collapse
Just search for 'how to logcat' on XDA or google. there are a lot of guides on that
MonsterMonsteur said:
i could get a logcat but i don't know how.
it does not happen often but when it happen it keeps happening on and on
Click to expand...
Click to collapse
Download and install Android Terminal Emulator or similar app from the Play Store. When you start the app, it stays active until you explicitly close it (an icon will be seen in your notifications to indicate that it's running). While it's running, you can have several terminal sessions open simultaneously and you can use this feature to compare results from different commands that run in real-time.. You will need root permissions, so for every terminal session window, you'll need to enter the command 'su'.
There are several things you can do to try and pinpoint the source of the problem:
1) In a terminal window (with root permissions) enter 'logcat' and let it run. You can copy and past the output of logcat to Pastebin or similar website and share the link (don't paste it in the forum as it is extremely annoying for most users). Also, if you do post your output for everyone to see, logcat has the potential of recording sensitive activities so I would suggest not looking at porn, doing anything illegal, or anything you wouldn't want to be known to the general public that could be used against you.
2) Entering the command 'top', will give you a real-time view of top running processes. By itself, it probably wouldn't do you much good, but it can help you identify apps or processes that are running but don't show up in your running apps list under settings.
3) The 'dmesg' command is used to write kernel messages to standard output and can (in some cases) give you an idea of what apps/programs are requesting access to the phones hardware such as the vibrator. The output can be extremely long and usually won't all fit in the terminal's history but by piping it into the 'less' command, as such: 'dmesg | less', it will give you a page by page view of it's output. Alternatively, using 'cat /proc/kmsg' will give you the same results, but is continually updated as with the 'top' or 'logcat' commands.
If I were to guess, I would say that whatever app you are using to watch videos, may have a haptic setting feedback enabled, but that's just a wild guess and wouldn't explain why it would happen when you're making calls as well. I would suggest trying to use the tools that are available to try and find the source of the problem, and run through your settings once or twice to see if anything looks out of the ordinary.
Here's a good simple app to grab logcat's: https://play.google.com/store/apps/details?id=org.jtb.alogcat
Sent from my One X
Also turn on "pointer location" in the developer options of settings. If the screen is showing random touches then you got a problem :bad:
Sent from my Nexus 4 using xda app-developers app
Related
so i come from a server background, in fact i support a document management system on servers across the world. we've got a microsoft tool we use called perfmon, performance monitor, that we use all the time, in fact we made our own counters. is there something like this for our phones? i'm curious to see what causes my phone to lag at times.
You can use "Log Collector" on the device or just adb logcat from a computer to see what is going on while the phone is lagging.
Those are probably your two best bets.
Stigy said:
You can use "Log Collector" on the device or just adb logcat from a computer to see what is going on while the phone is lagging.
Those are probably your two best bets.
Click to expand...
Click to collapse
does it show it in a graph? or it's just text logging?
marty22877 said:
does it show it in a graph? or it's just text logging?
Click to expand...
Click to collapse
It is just a log of what is going on in the phone at the time.
Might not be EXACTLY what you are looking for, but it should be a start to at least determine what is running at the moment that is causing your phone to lag.
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
lean7 said:
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
Click to expand...
Click to collapse
this work with zeus?
Yep, I've 6.31n and work good.
lean7 said:
Yep, I've 6.31n and work good.
Click to expand...
Click to collapse
doesn't work. just blink once, then off.. what's wrong?
---------------
maybe doesn't work with 6.31o..
Used it once, in february...its not this good
But does the job
Sent from my LG-P970 using Tapatalk
This app is known here. There already was a discussion with it.
From the app in Google play:
"We are aware of the issues with Optimus Black since the 2.3.4-update"
ciplukzz said:
doesn't work. just blink once, then off.. what's wrong?
---------------
maybe doesn't work with 6.31o..
Click to expand...
Click to collapse
You were right! It's not working now :S
Thankyou for sharing this app!
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out:
http://www.mediafire.com/?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
If you want the source my build directory is hosted here: http://www.mediafire.com/?hmx5wpbwx00c47l
brownowski said:
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out (sorry for the format, can't post links yet - please remove the spaces):
Code:
www . mediafire . com / ?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
Click to expand...
Click to collapse
Good aproach! Take into account that is normal that the kernel switch off leds on battery... think in the leds allways on... I have had some kernel-related atempts to correct this... but atm no luck.
Regards!
When the screen is off and the device is on battery it is doing some sort of polling every few seconds to check and reset the LEDs rather than just a trigger when the screen turns off and that is what makes the app not work.
I tried a few different ways to reset the LEDs but the only way that would work is to force them off by writing a 0 into led_onoff followed immediately by a 1 into led_onoff. It wasn't enough to just echo 1 > led_onoff, I had to do a 0 first. However, with power connected, just the echo 1 > led_onoff was all I needed.
As far as I could tell, the led_onoff seems to only part of the 970 device code. I'm guessing that the other devices don't have an issue because they don't have to activate the LEDs in that way.
One other thing I tried was removing all write privileges to those files after turning on the LEDs to see if the system was writing a value into them to turn them off. They were still turned off so I kind of figured it's something in the kernel itself manually resetting things.
this should be good if work in customs ROM...to notify us for new message and etc
have a problem
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
lean7 said:
You were right! It's not working now :S
Click to expand...
Click to collapse
anguszhou said:
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
Click to expand...
Click to collapse
read the first page pls. it isnt working with 2.3.4 we know that.
anguszhou said:
:laugh:
look like some problems
can not running on V20F ver
the led just flashing one time.
Click to expand...
Click to collapse
Did you try the one I posted in post 9? http://forum.xda-developers.com/showpost.php?p=28571222&postcount=9
It sort of works in blink mode (best with repeating non-fading pulse with a lit time of 2000ms).
I'm using it in Zeus v6.35 at the moment.
lean7 said:
Hello guys!
I've downloaded this app a few days ago and it's very usefull, here I share the info of Google Play:
[...] This application uses the touch LED buttons to show if there is any missed notifications by turning them on and off. It is enabled by default and will autostart on boot but has to be run once after installation to start the service [...]
More info and download Here
Click to expand...
Click to collapse
My only wish is that it was all 4 lights instead of just search, but who cares, in a month Ill probably prefer just search and be happy
Thanks for this find, I was desperate for it
brownowski said:
I've been checking out this program and it's source code. The problem seems to be some sort of power management that turns the leds off after about 2 seconds when the screen is off and the phone is on battery.
The kernel exports some files to /sys/bus/i2c/devices/2-001a/ that can be used to control the leds. One file in particular is led_onoff. I've found that while on battery, if I do "# echo 0 > led_onoff; echo 1 > led_onoff" from a console, it will reset the leds and turn them on before the system turns them off after about 2 seconds when on battery. Everything seems to work as expected while on charge.
I'm not sure how to troubleshoot too much further than that. It looks to be something either in the kernel or android system files but I'm not about to start cooking my own kernel just to check it out. It's probably also a bit beyond my whole understanding of the code.
But, I've been able to implement a fairly bad hack to get it working in the 'blink' mode. Basically it just adds in some code to reset the leds before starting the next cycle which is enough to get it going (same as the command above). It has the side effect of making all the leds flash for a split second when they come on and uses a timer to control the blink so the phone will constantly waking every few seconds to control the leds and I'm not sure how that will affect the battery. Also works best with a blink time of 2 seconds on obviously because power management turns them off after then anyway.
Download it below if you want to try it out:
http://www.mediafire.com/?ez9rxjr8od9gouc
If you have the old version installed you will need to remove it first as this has a different signature.
Click to expand...
Click to collapse
Still not working on 2.3.4
working on ics?
New version of LG Notifications
jn83 said:
Still not working on 2.3.4
Click to expand...
Click to collapse
Hi, please test the attached APK. For now I have worked exclusively on the mode "repeat fading pulse". Please unintall the application if you have it already installed.
I used it for 2 days now and it seems to work for me, so report bugs, but only for the mode repeat fading pulse if have problems. I will try to fix also the other modes, when I have time.
PS: of course all credits go to the original creator of Lg Notification application. I only try to fix this to work on Lg Optimus Black on Gingerbread.
Dan
danfizesan said:
Hi, please test the attached APK. For now I have worked exclusively on the mode "repeat fading pulse". Please unintall the application if you have it already installed.
I used it for 2 days now and it seems to work for me, so report bugs, but only for the mode repeat fading pulse if have problems. I will try to fix also the other modes, when I have time.
PS:
Dan
Click to expand...
Click to collapse
There is a problem with repeat fading pulse. It eats too much battery. Constant light it is much battery friendly.
Go to System\usr\idc and open file clear_ped.idc with a text editor
look for the line
#Pressure
touch.pressure.scale=0.2
I changed to 0.1, save and close,
Secondly go to System\usr\idc and open file clearpad.idc
look for the line touch.filter.level = 2
I changed the level = 2 to level = 4
Reboot and enjoy.
My touchscreen now works flawlessly and I hope this fix works for others please test and report back your findings.
Remember to hit thanks if I helped you in any way.
You can try other settings, You can change the 4 , from 1-7 1 being most sensitive, not always best and 7 being the least. Each device will be different and vary in results. I wouldn't recommend going to 7 though as your touchscreen might become unresponsive.
I found 4 was the best on my handset,. Good luck.
I did that and I think it's a bit better now...
Sent from my C6903 using Tapatalk
How would I do this? I got a rooted xperia z1 but not sure what to do next.
Cheers
Dark-Skript said:
How would I do this? I got a rooted xperia z1 but not sure what to do next.
Cheers
Click to expand...
Click to collapse
You need a file manager such as Astro Manager, then just follow the instructions given here... go to System\usr\idc in the file manager.
TagEHeuer said:
You need a file manager such as Astro Manager, then just follow the instructions given here... go to System\usr\idc in the file manager.
Click to expand...
Click to collapse
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
What Rom and Kernel are you on
Dark-Skript said:
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
Click to expand...
Click to collapse
What Rom and Kernel are you on, I think some 4.3 ROMs still have an issue with the system being read only, I'm by no means a dev and you would need to read about this on whatever ROM you have thread, once you gain access to system being read, write you will have no issue saving.
Try other settings
ArashMiniStar said:
I did that and I think it's a bit better now...
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
You can try other settings, You can change the 4 , from 1-7 1 being most sensitive, not always best and 7 being the least. Each device will be different and vary in results. I wouldn't recommend going to 7 though as your touchscreen might become unresponsive.
I found 4 was the best on my handset,. Good luck.
Dark-Skript said:
After trying to edit the file it refuses to save. I have tried 2 different file managers now, Is it read only or something?
Click to expand...
Click to collapse
I'm sorry I'm really not sure why it's like that, as other post said depending on your ROM, it's best to contact the developer who made it. If you're using stock, then reply to me and I'll try and help further
TagEHeuer said:
I'm sorry I'm really not sure why it's like that, as other post said depending on your ROM, it's best to contact the developer who made it. If you're using stock, then reply to me and I'll try and help further
Click to expand...
Click to collapse
Well i thought id give CyanogenMod a shot, but bricked my phone haha.. I did not mind if the camera was not working as long as I could use the rest of the things.. Anyway whats happened is the Screen backlight is on but its on a grey screen
I can't turn the phone off to enter recovery mode either.
Dark-Skript said:
Well i thought id give CyanogenMod a shot, but bricked my phone haha.. I did not mind if the camera was not working as long as I could use the rest of the things.. Anyway whats happened is the Screen backlight is on but its on a grey screen
I can't turn the phone off to enter recovery mode either.
Click to expand...
Click to collapse
Try pressing and holding power button and volume up until it vibrates 3 times, after you've rebooted the phone.
If that doesn't work:
Best thing to do is link it up to PCCompanion and reset the phone to all it's factory settings. Try that?
Edit, best we talk here: http://forum.xda-developers.com/showthread.php?p=49018376#post49018376
TagEHeuer said:
Try pressing and holding power button and volume up until it vibrates 3 times, after you've rebooted the phone.
If that doesn't work:
Best thing to do is link it up to PCCompanion and reset the phone to all it's factory settings. Try that?
Edit, best we talk here: http://forum.xda-developers.com/showthread.php?p=49018376#post49018376
Click to expand...
Click to collapse
Thank you soo much, for all the help. This fixed the issue!!
Dark-Skript said:
Thank you soo much, for all the help. This fixed the issue!!
Click to expand...
Click to collapse
It's a pleasure, always happy to help.
Hello guys! I came here to show you this video:
[Search Youtube for XPERIA Z1 タッチ切れ再現法 The method of reproduce] Sorry, new users can't post links it seems. But please check the video out.
I wanted to ask if any of you could give a reasonable explanation of it. If this is a software issue - how could it be reproduced in such a manner, by touching the metal frame of the phone? The video shows it pretty well. I also managed to reproduce the bug like this on my Z1. It has been in service for about 20 days now. I am worried that they might just 'mask' a hardware issue with software filtering. My initial assumption is that this is due to bad grounding? Why else would human contact trigger it? You can see it can be reproduced on-demand like this.
Thanks for reading! I hope someone can explain it.
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
水攸月羽 said:
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
Click to expand...
Click to collapse
Agree.
eclyptos said:
Agree.
Click to expand...
Click to collapse
video demonstrates that a touch is being registered when touching the frame. It's kinda weird since why did the screen reacted to the touched frame. I have done that also and it's the same with me. But even after touching the frame and screen registered the touch, still screen fails to produce a continuous touch.
Sometimes it produces phantom touches which can be the cause of the random zooming and highlighting when browsing
Also tried changing the touch filter and failed to save. I think it needs root access
Im also facing such issue like I touched in sketch app & locked phone with other finger.Unlocked it while keeping the finger at same spot,then scolling the finger missed the touch
Also after playing GTA SA for about 30 min the touch sometimes stop responding.Any solutions
I tried above method but nothing works.I don't want to give this phone as I got it in replacement regarding yellow hue issue.
One issue after another emerges
Sent from my C6902 using XDA Premium 4 mobile app
RISHI RAJ said:
Im also facing such issue like I touched in sketch app & locked phone with other finger.Unlocked it while keeping the finger at same spot,then scolling the finger missed the touch
Also after playing GTA SA for about 30 min the touch sometimes stop responding.Any solutions
I tried above method but nothing works.I don't want to give this phone as I got it in replacement regarding yellow hue issue.
One issue after another emerges
Sent from my C6902 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is really a widespread problem across the globe. even Z1s owners are plagued by this problem and most likely even the z1 compact.
@Banwell13 I've not tried this as my touchscreen problem seems to have fixed itself? Strange.
But i'll definitely be keeping this thread in mind if it re-occurs.
Thanks for your efforts m8, appreciate it.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
水攸月羽 said:
Actually,you don't have to touch the metal frame!
Just put Z1 on a desk,wait for 30 seconds,touch screen and the bug will happen !
Click to expand...
Click to collapse
Think what he ment was if you hold the frame then the issue doesn't occur, well that's what happens on mine at least, putting it down on a desk usually makes the bug show it's face. Holding the frame fixes it.
@dladz, @brapicoco, Guys, we said this 20 times, the issue don't show on our devices in the same mode.
as many of you know i dont believe the knock on not working is a hardware failure.
i am pretty sure i figured out or am really close to figuring out what the problem is
i was doing many tests to try and figure out what the cause could be.
i put phone in airplane mode and location settings to off
i put almost all settings to disabled like wifi scanning in background
power saving features for wifi to disabled
all gestures to disabled besides knock on
almost anything that could be disable that could affect the knock on i disabled and guess what
knock on is repeatably working right now on this phone where it shouldnt be
i have did 2 tests runs of over 20mins each and knock on works perfect each time
this time starts from where i do a knock off
before i couldnt get knock on to work after 3mins
it would jump around under that where it would sometimes work and sometimes not but after 3mins from a knock off i couldnt get it to work ever
so i like i said i think its power saving issue
that would be kernel wouldnt it?
Are there a lot of people having knock on issues?
en11gma said:
as many of you know i dont believe the knock on not working is a hardware failure.
i am pretty sure i figured out or am really close to figuring out what the problem is
i was doing many tests to try and figure out what the cause could be.
i put phone in airplane mode and location settings to off
i put almost all settings to disabled like wifi scanning in background
power saving features for wifi to disabled
all gestures to disabled besides knock on
almost anything that could be disable that could affect the knock on i disabled and guess what
knock on is repeatably working right now on this phone where it shouldnt be
i have did 2 tests runs of over 20mins each and knock on works perfect each time
this time starts from where i do a knock off
before i couldnt get knock on to work after 3mins
it would jump around under that where it would sometimes work and sometimes not but after 3mins from a knock off i couldnt get it to work ever
so i like i said i think its power saving issue
that would be kernel wouldnt it?
Click to expand...
Click to collapse
mulhiny said:
Are there a lot of people having knock on issues?
Click to expand...
Click to collapse
After a long voyage into the security error disaster. I finally got my phone back working but I have lost knock on. And It is already frustrating as I use it all the time. .So I would like to see a solution to this.
Tomv5314 said:
After a long voyage into the security error disaster. I finally got my phone back working but I have lost knock on. And It is already frustrating as I use it all the time. .So I would like to see a solution to this.
Click to expand...
Click to collapse
Which ROM are you using?
Tomv5314 said:
After a long voyage into the security error disaster. I finally got my phone back working but I have lost knock on. And It is already frustrating as I use it all the time. .So I would like to see a solution to this.
Click to expand...
Click to collapse
Here is your solution. Read Post #28 & #29:
http://forum.xda-developers.com/showpost.php?p=54049249&postcount=28
waingro808 said:
Here is your solution. Read Post #28 & #29:
http://forum.xda-developers.com/showpost.php?p=54049249&postcount=28
Click to expand...
Click to collapse
I have been trying this for 2 hours now. I put apk system app rw-r-r rebooted went back checked it took there is also a Verizon hidden menu and Verizon hidden menu odex in there . all set at rw-r-r. go to terminal emulator put in su. terminal emulator granted su permission then command I keep getting error see attached I have been in the original thread all this time. Some people get it working. Some talking about Going back to original stock. After spending many hours getting my phone unbricked the thought of doing a KDZ is not pleasant. Do not know what I am not doing that you did
edit: Fixed. Furnace control Free in play store can upgrade touch firmware.
Tomv5314 said:
I have been trying this for 2 hours now. I put apk system app rw-r-r rebooted went back checked it took there is also a Verizon hidden menu and Verizon hidden menu odex in there . all set at rw-r-r. go to terminal emulator put in su. terminal emulator granted su permission then command I keep getting error see attached I have been in the original thread all this time. Some people get it working. Some talking about Going back to original stock. After spending many hours getting my phone unbricked the thought of doing a KDZ is not pleasant. Do not know what I am not doing that you did
edit: Fixed. Furnace control Free in play store can upgrade touch firmware.
Click to expand...
Click to collapse
I looked at your screenshot. Why are you typing HIDDENMENU in all caps? It needs to be HiddenMenu. Type it exactly the same.
waingro808 said:
I looked at your screenshot. Why are you typing HIDDENMENU in all caps? It needs to be HiddenMenu. Type it exactly the same.
Click to expand...
Click to collapse
I do see the very last hiddenmenu is . (HiddenMenu not HIDDENMENU) capitol H capitol M . Any ways Savoca Furnace Kernel Control app solved it for me. . Thanks for your help..
What I would like to have happen is have the clock go into night mode when: wirelessly charging, connected to a specific wifi network, and to start and end at specific times.
I've been messing around with this and can't figure it out for the life of me. Any help is greatly appreciated.
Thanks
Larzzzz82 said:
What I would like to have happen is have the clock go into night mode when: wirelessly charging, connected to a specific wifi network, and to start and end at specific times.
I've been messing around with this and can't figure it out for the life of me. Any help is greatly appreciated.
Thanks
Click to expand...
Click to collapse
where exactly are you stuck at?
Basically the whole thing... I created a profile called night mode to turn on and off at certain hours.
In the tasks tab, I've tried to set up the wifi network, but don't see a variable for specifying being connected to it, nor do I see anything for the battery charging wirelessly.
A couple you tube videos later and I'm scratching my head harder.
Larzzzz82 said:
Basically the whole thing... I created a profile called night mode to turn on and off at certain hours.
In the tasks tab, I've tried to set up the wifi network, but don't see a variable for specifying being connected to it, nor do I see anything for the battery charging wirelessly.
A couple you tube videos later and I'm scratching my head harder.
Click to expand...
Click to collapse
so for the Wi-Fi part:
- there is the state 'Wi-Fi connected' to activate when you are connected
- you can use 'test net' to store ssid to a variable, then check it for a match with certain ssid, with which you want the profile to react to - only do when connected to certain Wi-Fi.
I don't have wireless charge so I cannot say anything here, but if I remember correctly, recent update of Tasker has included detection of this, so too should bff able to sound something useful in those states or events.
Then finally, in the clock app, you can either try to use intent or simulate taps to switch it to night clock.
After that, hopefully you will be happy with the result
Thank you sir. I will give those a shot
Light dawns on marble head! I got it to work, 98% of what I envisioned.
Is there a way to make this work without having to wake the phone up first? A lot of times, I just place it on the charger.
Larzzzz82 said:
Light dawns on marble head! I got it to work, 98% of what I envisioned.
Is there a way to make this work without having to wake the phone up first? A lot of times, I just place it on the charger.
Click to expand...
Click to collapse
what is your solution so far?
for connecting to Wi-Fi, sometimes it does not connect without screen on though, and I still have not figured that out.
Rather than try to explain it, these are my set ups.
Didn't seem to work as I wanted until I added the the, If lines to tasks 2and 3.
Still gotta unlock the phone to start the process though.
Larzzzz82 said:
Rather than try to explain it, these are my set ups.
Didn't seem to work as I wanted until I added the the, If lines to tasks 2and 3.
Still gotta unlock the phone to start the process though.
Click to expand...
Click to collapse
did you check to use root in the run shell commands?
Sadly I don't have a solution for the unlocking part.
I did use root. Had to add the if statement at the bottom for. Both tasks are the same aside from the input tap x y numbers
PS.. If I remove the pattern lock, it will work the way I want(ed) it to. Not worth it to do that IMO.
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
I did use root. Had to add the if statement at the bottom for. Both tasks are the same aside from the input tap x y numbers
PS.. If I remove the pattern lock, it will work the way I want(ed) it to. Not worth it to do that IMO.
Click to expand...
Click to collapse
ah the pattern lock! now I see the pattern
do you have Xposed? maybe try to allow clock app over lock screen?
No exposed. Is it out for 7.1.1?
Sent from my Nexus 6 using Tapatalk
Larzzzz82 said:
No exposed. Is it out for 7.1.1?
Click to expand...
Click to collapse
oh naah....
Seems to stop after the battery is charged... Gotta figure out how to latch the power till the end of the task.