hello
after a year of great health, my nook began having problems with the touchscreen.
first, it began with some phantom touches, but its frequency quickly increased until it reached the point of making it totally nonresponsive.
here is a video of my nook to show how bad this is
http://youtu.be/nnDSP__GEhc
- tried cleaning the screen, and nothing
- tried the ADB method to recalibrate the screen, once it worked for a couple of days and happened again. so i tried to recalibrate again without success
- i have a screen protector since day one
- tried restoring and old nandroid (with clockworkmod), nothing
- upgraded CM7 to the latest version: 242, nothing
after recalibrating i issue a dmesg to the shell and i get the following messages:
Code:
<4>max8903_charger_enable: B&N USB CHARGER(500mA) Detected!
<4>MAX8903: Charging is now enabled!
<6>kxtf9 1-000f: IRQ TILT [1]
<6>kxtf9 1-000f: IRQ TAP1 [2]
<6>kxtf9 1-000f: IRQ TAP1 [8]
<6>kxtf9 1-000f: IRQ TAP2 [1]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP2 [8]
<4>ttsp_forcecal_store: Forcing TP calibration NOW.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Starting Touch panel Calibration: Switch to System Information mode.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Touch Panel is now in System Information Mode.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Touch Panel Calibration was successful.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Returning to Operational mode.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Initializing Gesture Setup.
<6>cyttsp-i2c 2-0022: cyttsp_calibrate() - Power state is ACTIVE
<6>kxtf9 1-000f: IRQ TAP2 [1]
<6>kxtf9 1-000f: IRQ TAP2 [20]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP2 [2]
<6>kxtf9 1-000f: IRQ TAP2 [8]
<6>kxtf9 1-000f: IRQ TAP1 [1]
which seems to show that the touches are still happening
then, in clockwork recovery, i hit the key test option, and it continually shows keysrokes with codes 103 and 108 (even when i'm not touching anything) is this normal??????
so, the question is.... does anyone have an idea that i could try??? should i begin searching for a replacement ?
........ and FWIW, today i tried creating a bootable SDcard using verygreen's image.
booted and the touchscreen was responding fine. so, i booted again from the emmc, and now it seems to be working again....... does this have any sense????????
if the solution persists, i'll update this thread as solved
and the problem happened again..... i think i lost it
Considering you got a year out of it, could you try removing the screen protector? Maybe it's getting brittle or something.
Remove the charger.
Sent from my PC36100 using Tapatalk
selection16 said:
Considering you got a year out of it, could you try removing the screen protector? Maybe it's getting brittle or something.
Click to expand...
Click to collapse
mmm, worth a try, when i get home i'll try that
jerrykur said:
Remove the charger.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
all described behavior is when disconnected from the charger
don_ernesto said:
all described behavior is when disconnected from the charger
Click to expand...
Click to collapse
ignore this
selection16 said:
Considering you got a year out of it, could you try removing the screen protector? Maybe it's getting brittle or something.
Click to expand...
Click to collapse
i tried this, and didnt work, thank you anyways for the idea.....
BTW, i had never used the nook without a screen protector.... it looks gorgeous!!! if this would work again, i doubt i'll put the protector back
I'm curious......is it OVERCLOCKED?
If so, set it back to normal and try it. I'm seeing some strange things when I overclock.
rampart51 said:
I'm curious......is it OVERCLOCKED?
If so, set it back to normal and try it. I'm seeing some strange things when I overclock.
Click to expand...
Click to collapse
it is not overclocked.... but thanks for the suggestion
i think the next step is to hit it with a hammer and see what happens
Dude I've had the phantom touches on both of my nooks. I've had he problem on stock no root cm7 stock rooted, and and currently on miui. It's not as bad on my second nook but it still happens once in a while.
Sent from my NookColor using Tapatalk
Related
Hello,
Is there a possibility to disable the delay that I have from the moment I press the unlock button to the moment the screen turns on?
At the moment I have 2.5 seconds delay from the moment I push the button until the screen turns on.
Am I the only encoutering this delay? didn't see a similar post anywhere on the web
larry200ro said:
Am I the only encoutering this delay? didn't see a similar post anywhere on the web
Click to expand...
Click to collapse
My phone has the same behaviour and the "problem" (if you want to call it a problem) is also described in some german forums - so no, it seems that this is absolutely ordinary.
I had the chance to compare it with a I9000 and the I9000 will outperformance the I9001 at this point, but nonetheless for me it is not really disturbing or so.
any updates on this one? Can someone please help? It's driving me crazy
Hy
I've read about the same problem on a hungarian forum, but I don't have it, mine turns on in less then a secound.
I think if this is such a common problem, Samsung will fix it. Maybe write them a mail.
When the screen has been turned off for a long time, the first unlock takes a lot longer than the following unlocks. For me, I think the 'cold' unlock is 2.5 seconds while a 'warm' unlock is just 1 second.
But yeah, this clearly is a standard problem. Let's hope Samsung brings out a firmware update soon to fix issues like these.
Mine has same "problem". It seems that the phone is in somekind of sleep.
i believe that problem is fixed in 2.3.4. Try flashing that and i hope you won't have that problem...i mean this is how it works:
1. I9000 uses SGX540 which uses less ram for its vram so you have around 250mb+ free ram
2. I9001 uses Adreno 205 which uses a lot of ram for its vram so that you have about 120mb left only
3. Try using no frills CPU app using root and set the minimum frequency to 245 mhz or maybe higher...and you won't get any delays..
Unfortunately it is not fixed with 2.3.4 as I still have the issue.
I will try your suggestion with the CPU frequency
shad0wboss said:
3. Try using no frills CPU app using root and set the minimum frequency to 245 mhz or maybe higher...and you won't get any delays..
Click to expand...
Click to collapse
The standard value for the minimum frequency is 245mhz! But it would be stupid to set it higher, because this will of course drain more battery.
I set my minimum frequency to 122mhz (scaling: on demand) and I noticed no differences regarding the delays (like I said before, I do not have a problem with a delay of 2,5sec) - but I have a better battery lifetime without charging.
I will give both ways a try, but to be honest the 2 + sec delay is anoing for me.
Edit:
Even with 1.4Ghz as frequency there is a delay, not that long but still about 1,5 sec.
reneph said:
The standard value for the minimum frequency is 245mhz! But it would be stupid to set it higher, because this will of course drain more battery.
I set my minimum frequency to 122mhz (scaling: on demand) and I noticed no differences regarding the delays (like I said before, I do not have a problem with a delay of 2,5sec) - but I have a better battery lifetime without charging.
Click to expand...
Click to collapse
yup it will...then you should wait for a better custom rom with all those JIT and ram compress tweaks enabled and then you can enjoy the speed.
To be honest if you guys want your problems to be fixed, do support the devs as much as possible in this thread
Psyco_01 said:
I will give both ways a try, but to be honest the 2 + sec delay is anoing for me.
Click to expand...
Click to collapse
Yeah but in my opinion setting up the minimum frequency is not an option, because it is a more battery draining setting.
reneph said:
Yeah but in my opinion setting up the minimum frequency is not an option, because it is a more battery draining setting.
Click to expand...
Click to collapse
mate, you can never have performance with battery conversations...it's inversely proportional.
1. Set maximum value to 1 ghz with minimum of above 245
2. Do a hard reset from going into settings -> privacy -> factory reset because i just did it recently and my phone's running much faster.
Just had a chat with a guy from samsung support and he said that there is nothing they can do.
There must be a tweak or something to decrease this delay
larry200ro said:
Just had a chat with a guy from samsung support and he said that there is nothing they can do.
There must be a tweak or something to decrease this delay
Click to expand...
Click to collapse
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
shad0wboss said:
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
Click to expand...
Click to collapse
I did, one day it shut down on me twice. It turned out like you turn it off, but then I couldn't turn it back on, just after battery reset. Never happaned again since then.
You mean factory data reset by hard reset?
Csapi007 said:
I did, one day it shut down on me twice. It turned out like you turn it off, but then I couldn't turn it back on, just after battery reset. Never happaned again since then.
You mean factory data reset by hard reset?
Click to expand...
Click to collapse
you mean battery caliberation will fix it? i mean my battery doesn't drain or anything, it just turns off by itself sometimes...
hard reset = factory data reset xD
shad0wboss said:
you mean battery caliberation will fix it? i mean my battery doesn't drain or anything, it just turns off by itself sometimes...
hard reset = factory data reset xD
Click to expand...
Click to collapse
No, I mean getting the battery out and then putting it back.
shad0wboss said:
mine reacts instantly...just did a hard reset that's why
[Q]Anyone facing random phone shutdown?
Click to expand...
Click to collapse
Interesting....what version of android do you have (also kernel)
Mine reacts slower if I leave it longer. (samsung explanation "It is because the phone is entering in some kind of sleep state"). When I said that Galaxy s2 reacts instantly the answer was that Galaxy S2 has a better microprocesor and has a different platform.. hmmm
If you find this useful, press the Thank you button
Csapi007 said:
No, I mean getting the battery out and then putting it back.
Click to expand...
Click to collapse
well, i've done that a couple of time already without knowing it being a fix for random shutdowns...but really it's a bit annoying, it just turns off by itself..
The original topogigi thread is getting very long. I thought maybe it would be helpful to post some type of FAQ in a separate thread. I will not keep this updated, but I will start the thread by posting the instructions for overclocking with the OC deamon (which is a very frequently asked question in the original thread):
in /etc/andrev_oc you've got 6 files:
- sleep_gov to indicate which governor to use during sleep mode
-wake_gov: same for awake state
-sleep(or wake)_max: max frequency allowed
-sleep(or wake)_min: min frequency allowed.
Open ES File explorer (pre-installed with ROM) and go to settings. Make sure you have [x] Root Explorer and [x] Mount File System
Open etc/andrev_oc as text document, edit the value as you desire and save. A reboot and it's done.
Here are the authorized values:
1408000
1216000
1100000
1015000
800000
503000
389000
216000
Have fun !
Undervolt
To Undervolt _________________________________
Edit 'echo 0,0,0,0,0,0,0,0' UV values via:
volt_scheduler in /system/xbin/volt_scheduler
(i.e. a value of 50, 50, 50, 50, 0, 0, 0, 0 undervolts the top 4 frequencies by 50mV each.)
GPS bug
Don't know if this will work for everyone, but...
Originally Posted by fire3d
i tested this three times now, wipe everything on the phone,
I'am from Germany (if this is relevant for GPS)
install 1.6
do the Setup
install 1.8
enter hidden menu and add the Nokia Supl for GPS
supl.nokia.com
7275
cert = NULL
TLS = on
select nokia and shut down the phone, start it again
After that i get a fix outside nearly instant, indoor it tooks 2-3 sec's,
best GPS ever seen on this Phone.....
Click to expand...
Click to collapse
Found something that could be of help to the ones with gps fix problems like myself in 1.8.
When I start my O2X with GPS off and I set GPS on when phone is booted, I couldn't get a normal fix (just the "1 sec bug")
But I start start my O2X with GPS on, I can get a normal fix.
Maybe this can help Topogigi crush this bug.
Reboot a dozen times with GPS OFF: No Fix, at all or loosing it directly and not coming back
Reboot a dozen times with GPS ON: Fix, and keeps it
I think there's something wrong with initializing GPS when (re)booting with GPS OFF
You describe a method for increasing the voltage, and as it lowered. Than monitoring the current voltage???
I can get the GPS to lock outside it takes a while. The problem is subsequent locks take just as long. So if I go back inside it'll never lock. The GPS on this phone sucks!
http://forum.xda-developers.com/showpost.php?p=18146527&postcount=2126
FAQ by Topogigi, its in the ROM thread.
My TP running CM9 often randomly reboot itself in the middle of the night. It never reboot itself when I use it. But I often find that the recent app list is cleared indicating a reboot happened. And about once a week I'm waken up by the bright boot animation. Anybody has the same problem?
How do I go about find out what's causing the reboot? Thanks.
simollie said:
My TP running CM9 often randomly reboot itself in the middle of the night. It never reboot itself when I use it. But I often find that the recent app list is cleared indicating a reboot happened. And about once a week I'm waken up by the bright boot animation. Anybody has the same problem?
How do I go about find out what's causing the reboot? Thanks.
Click to expand...
Click to collapse
Hard to help if you don't take the time to give us details like which version you're running and CPU settings and such
Sent from my CM9 TouchPad using TapaTalk 2
simollie said:
My TP running CM9 often randomly reboot itself in the middle of the night. It never reboot itself when I use it. But I often find that the recent app list is cleared indicating a reboot happened. And about once a week I'm waken up by the bright boot animation. Anybody has the same problem?
How do I go about find out what's causing the reboot? Thanks.
Click to expand...
Click to collapse
Try running the latest nightly. There are several good apps in the playstore (antutu, no frills, set cpu). Use one to set your minimum cpu speed to 384. Hope this helps. Good luck.
chicle_11 said:
Try running the latest nightly. There are several good apps in the playstore (antutu, no frills, set cpu). Use one to set your minimum cpu speed to 384. Hope this helps. Good luck.
Click to expand...
Click to collapse
As chicle_11 says but don't worry about changing CPU speed as the minimum is already set to 384 with the latest nightly and has been for a while . You can check what yours is set to by going into settings then then performance followed by processor .
Hope this helps .
Are you using a touchstone dock for charging at night? I had this same issue running CM7 Alpha 2 but only when the TP was on the dock. It hasn't recurred after a complete wipe and then install of CM9.
simollie said:
My TP running CM9 often randomly reboot itself in the middle of the night. It never reboot itself when I use it. But I often find that the recent app list is cleared indicating a reboot happened. And about once a week I'm waken up by the bright boot animation. Anybody has the same problem?
How do I go about find out what's causing the reboot? Thanks.
Click to expand...
Click to collapse
My TP does the same as well.
It doesn't bother me too much though, what I did was switch the stock CM9 boot animation to a darker one.
The TP will reboot itself at least three times a week for me, but I just let it go.
khoikn said:
My TP does the same as well.
It doesn't bother me too much though, what I did was switch the stock CM9 boot animation to a darker one.
The TP will reboot itself at least three times a week for me, but I just let it go.
Click to expand...
Click to collapse
in the /proc/last_kmsg on the device there's dmesg output from the previous boot, so after your devices crashes there should be the reason. if you have terminal app installed you can enter it and run "cat /proc/last_kmsg" or if you have android sdk installed on PC you can always connect the device to the pc via usb and run "adb shell /proc/last_kmsg" and post the result.
btw. what nightly do you use? is it recent one?
I don't have a last_kmsg, but a last_klog.
That one shows a Kernel panic.
Those are the last few lines in the log (do you need the whole?):
Code:
Suspending console(s) (use no_console_suspend to debug)
<3>wm8994-codec wm8994-codec: AIF1_CLOCKING_1 value 0x11<3>wm8994-codec wm8994-c
odec: AIF2_CLOCKING_1 value 0x0<3>wm8994-codec wm8994-codec: - MEOW wm8994_suspe
nd
<3>wm8994-codec wm8994-codec: AIF1_CLOCKING_1 value 0x10<3>wm8994-codec wm8994-c
odec: AIF2_CLOCKING_1 value 0x0<3>wm8994-codec wm8994-codec: - MEOW wm8994_suspe
nd
<7>lm8502_mod_brightness: set LED2 brightness (0) percent
<7>lm8502_mod_brightness: set LED1 brightness (0) percent
<7>lm8502_mod_brightness: set LED1 brightness (0) percent
<7>lm8502_mod_brightness: set LED2 brightness (0) percent
<3>msm_wm8958_shutdown_power: codec power shutdown
<3>wm8994_ldo_power: Power down the WM8994 LDOs
<3>wm8994 4-001a: - MEOW wm8994_device_suspend
<6>btuart_pin_mux: off
max8903b_suspend: suspend
<6>PM: suspend of devices complete after 36.913 msecs
power_suspend_late return 0
<6>PM: late suspend of devices complete after 0.824 msecs
Disabling non-boot CPUs ...
<4>gic_show_resume_irq: 48 triggered<4>gic_show_resume_irq: 119 triggered<4>msm_
gpio_show_resume_irq: irq 293/gpio 37 triggered wake
<5>msm_timer_set_next_event(12) clock dg_timer, alarm already expired, now 241ad
898, alarm 241ad8a0, late -8
<5>msm_timer_set_next_event(12) clock dg_timer, alarm already expired, now 241ad
90c, alarm 241ad915, late -9
<4>CE: dg_timer increased min_delta_ns to 5000 nsec
<6>PM: early resume of devices complete after 0.385 msecs
<0>Kernel panic - not syncing: Watchdog bite received from Q6! Rebooting.
[<8004bab0>] (unwind_backtrace+0x0/0x164) from [<8054e24c>] (panic+0x6c/0xe4)
[<8054e24c>] (panic+0x6c/0xe4) from [<8008e5f0>] (q6_fatal_fn+0x28/0x30)
[<8008e5f0>] (q6_fatal_fn+0x28/0x30) from [<800c65c8>] (worker_thread+0x168/0x1f
4)
[<800c65c8>] (worker_thread+0x168/0x1f4) from [<800ca250>] (kthread+0x78/0x80)
[<800ca250>] (kthread+0x78/0x80) from [<8004634c>] (kernel_thread_exit+0x0/0x8)
evlog: beg
evlog: end
<0>Rebooting in 5 seconds..<5>Going down for restart now
pato
I have reboots in CM quite often too, never in webOS 3.0.5 to be honest, not sure what's causing it. I don't use CM too much on my TP anyway.
Anyone find a fix yet?
Seems to be caused by the sound card driver. This has been quite a hack to get it to work at all. I'm not sure if I prefer to have sound + crashes or no sound at all.
Also see: http://code.google.com/p/cmtouchpad/issues/detail?id=682
Hey!
My Girlfriend is using an Galaxy S Plus, and recently i tried to flash it with some of the Images posted here... but somehow, every Image has major issues with the lock screen... to me it seems that the device isn't waking up properly.
The screen looks a bit dim, and the touchscreen won't work at all... after 5-6x pushing the power button, the device sometimes wakes up again.
To me it seems that every image here has the same problem... or am i doing something wrong in the flashing process?
Please help!
Tho
Tho-kun said:
My Girlfriend is using an Galaxy S Plus, and recently i tried to flash it with some of the Images posted here... but somehow, every Image has major issues with the lock screen... to me it seems that the device isn't waking up properly.
The screen looks a bit dim, and the touchscreen won't work at all... after 5-6x pushing the power button, the device sometimes wakes up again.
Click to expand...
Click to collapse
I have read some people mentioning that it can be related to the CPU governor used - try to use another governor.
PS: I have had the same issue with CM9 builds and smartassv2 governor. Since I'm using CM10 I haven't had that issue anymore.
Since upgrading to Lollipop, both Xperia Z and Xperia Z3 stutter on audio playback over bluetooth. It works fine for a minute or so and after it starts stuttering, UI becomes unresponsive and FC, and many times I had to reboot in order to properly use the phone.
I need someone to point me in the right direction with this kernel issue. SysCtl doesn't make too much sense to me.
[WORKAROUND 1 in the second post]
[UPDATE] After more digging I found out that the Bluetooth Stuttering issue is Kernel related and it affects other brands like LG, Motorola. Governor on BT headset/receiver, while streaming jumps from normal 384 Mhz minimum FQ to 702 Mhz locking on that Frequency and that's why I didn't notice any stuttering on the BT receiver. As soon as I changed the min Fq to 384 (as it should be) the choppiness began as soon as I turned off the screen.
>>So, Bluetooth Receiver on BT version 3.0+EDR - on normal conditions (Governor Interactive - min 384 max 1512) stutters on screen off;
>>Bluetooth Speaker on BT version 4.0 - on normal conditions stutters even more aggressive (1 second of music every 3 seconds of nothing) and crashes the UI and renders the phone barely usable until reboot.
>>Another Issue is with an app (music or bluetooth share) that on the first run changes the governor, and with the kernel policy on sleep mode.
??? A fix might be in Kernel policy or sysctl???
[UPDATE 2] I think I'm looking at the issue completely wrong. I don't think the CPU needs to be forced to keep cores active in sleep states but I think the bluetooth driver (must be in devices/platform) must be kept hogging resources in screen off. Anyone with a brilliant idea? I just discovered where the cpu settings are so not much I can do.
[UPDATE 3] [Workaround 2] Disabling MPDecision will keep all 4 cores running with no excessive battery drain - I had no stutter in 2 hours of playback and also The Min FQ didn't change. So now, when I go out, I either turn on the Partial Wakelock or temporary disable the MP Decision. I've got some help from kernel devs and I'll try playing with the hotplugs sometime next week and maybe come with a real fix. If anyone with enough knowledge of kernel wishes to participate I'd be really grateful.
I have very limited knowledge on Kernel and I really need help - I'm now learning stuff. But, I'll compare KitKat SysCtl to Lollipop SysCtl to see if I find something that might help understand the issue and maybe come up with a fix. On KK I never had this kind of issues. If anyone can help me on this please PM.
Maybe this help
Hello
I can remember that is had a lot of stuttering on bluetooth with a speaker or with music regularly what is did, was let the phone run a default 468 Mhz instead of 384 Mhz, after that the problems were over.
I dont know of this will fix it but you can try it
Sovjet-Command said:
Hello
I can remember that is had a lot of stuttering on bluetooth with a speaker or with music regularly what is did, was let the phone run a default 468 Mhz instead of 384 Mhz, after that the problems were over.
I dont know of this will fix it but you can try it
Click to expand...
Click to collapse
I noticed this yesterday while I was playing with the governor. On xperia Z governor settings were jumping to min FQ of 702Mhz which has a huge impact on battery. Even on trickster settings wont stick for long. So far the issue isn't related to SND_Soc audio mapping, it's the crappy kernel implementation on multiple devices running 5.02 (LG, Motorola etc).
Workaround 1
The cause is the kernel after all or at least as far as I know.
The workaround is about creating a Partial Wakelock so the cpu stays active after screen off with this app.
It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance (for the Z3 mostly). The partial wakelock should work especially on bluetooth headphones. I also found an app that ads partial wakelocks here's the link : https://play.google.com/store/apps/d...arken.wl&hl=en
SysCtl diff between KK; LL
These are Kernel differences discovered in the SysCtl file - comparison made betwen Kitkat (KK) and Lollipop (LL) are these of any help?
Fs.epoll.max_user_watches KK 169642 LL 164219
Fs.file-max KK 183359 LL 181926
Kernel.dmesg_restrict KK 1 LL 0
Kernel.msgmni KK 877 LL 851
Kernel.threads-max KK 28653 LL 28429
Bump
Sent from my SPH-L900 using Tapatalk
Bump any fix made?
superspeedz32 said:
Bump any fix made?
Click to expand...
Click to collapse
Well, I worked around the issue so further investigation wasn't really necessary since it would take a lot of time.
Here is what I know so far:
Bluetooth streaming works flawlessly with aptX devices
It's kernel related - and mp decision
This is my daily driver for music http://forum.xda-developers.com/gen...h-receiver-t3212201/post63021706#post63021706 which now works flawlessly.
MP-Decision, while music streaming, upscales the min cpu fq to 702mb which means the CPU will drain a lot of battery. So, with Trickster or the cpu app of your choosing, lock the min fq to 384.
To avoid the stuttering (if you're using interactive governor), set the hispeed_freq @ 1134mb and go_hispeed_load of anywhere between 85-90 % default values are too power hogging and what i'm usually trying is to find a ballance between decent performance and battery saving.
In my experience interactive has the tendency to overheat the device much faster, which is why I'm now using the ondemand governor, but since now i'm using an aptx receiver I hardly have any issues with stuttering.
Anyway, feel free to PM me for more infos.
App name
Sebi673 said:
The cause is the kernel after all or at least as far as I know.
The workaround is about creating a Partial Wakelock so the cpu stays active after screen off with this app.
It works. No more stuttering. As for speakers that require high sample rate I just switched the cpu governor to performance (for the Z3 mostly). The partial wakelock should work especially on bluetooth headphones. I also found an app that ads partial wakelocks here's the link :
Click to expand...
Click to collapse
What was the name of the app ? It´s not on the store anymore. Thx in advice
Tenshinryu said:
What was the name of the app ? It´s not on the store anymore. Thx in advice
Click to expand...
Click to collapse
Wake lock power manager. Although I don't have that problem since the last fw update. Package Name eu.thedarken.wl
It helped me a lot so feel free to try it
Sebi673 said:
Wake lock power manager. Although I don't have that problem since the last fw update. Package Name eu.thedarken.wl
It helped me a lot so feel free to try it
Click to expand...
Click to collapse
Thanks I have installed it, but maybe one of you could help me with this idea: I would like to have Tasker execute the Partial_Wake_Lock via the Wake Lock Power Manager when Bluetooth is connected
I have come so far that Tasker starts the Wake Lock Power Manager, but I don´t know how to execute certain routines within the started app. Any ideas ?
Maybe someone at least knows how to start functions within a app with Tasker ?
Thanks in advance
UPDATE: I´ve managed it by myself
For those of you interested how - here´s what you need: Root, Tasker, Execute Locale App :
In Tasker
> Set Profile Bluetooth Connected
Task :
1.Run Application Wake Lock
2.Input > Trackball > Down, 5
3. Plugin > Execute Locale > !Input keyevent 66
That´s it.
Tenshinryu said:
Thanks I have installed it, but maybe one of you could help me with this idea: I would like to have Tasker execute the Partial_Wake_Lock via the Wake Lock Power Manager when Bluetooth is connected
I have come so far that Tasker starts the Wake Lock Power Manager, but I don´t know how to execute certain routines within the started app. Any ideas ?
Maybe someone at least knows how to start functions within a app with Tasker ?
Thanks in advance
UPDATE: I´ve managed it by myself
For those of you interested how - here´s what you need: Root, Tasker, Execute Locale App :
In Tasker
> Set Profile Bluetooth Connected
Task :
1.Run Application Wake Lock
2.Input > Trackball > Down, 5
3. Plugin > Execute Locale > !Input keyevent 66
That´s it.
Click to expand...
Click to collapse
ha awesome dude. you basically manually started the activity. but automatically ))))
Sebi673 said:
ha awesome dude. you basically manually started the activity. but automatically ))))
Click to expand...
Click to collapse
Yeah, I dunno, but I didn´t like the thought of doing that manually all the time I´m using Bluetooth frequently
But, maybe I found another solution to my BT stutter / disconnect problem: I installed Proximity Fix and couldn´t test in my car or my speakers, but my Gear Fit didn´t disconnect until now, like it did before
Update: No, no, no didn´t fix my problem. Wether the proximity fix nor the Wake Lock solution. I also did a factory reset.. I´m really eager to reroll to 5.1.1.