Related
To my knowledge, there is no thread dedicated to the new numerical releases of CM. Let us start with the newest, CM 6.0.2.
Please post your anecdotal data, including benchmarking scores, bugs, and glowing experiences. Perhaps this will serve as an unofficial repository for issues that prove consistent.
Note: After modifying my WiFi settings, specifically disabling sleep mode while the screen is off, I've encountered no related instability.
Mail FC Fix: http://forum.xda-developers.com/attachment.php?attachmentid=394316&d=1283500340
Systemic issues yet to be addressed:
-LEDs do not work save for charging
-Outgoing calls initially drop before reconnecting
-Lockups or reboots, likely stemming from SetCPU
-OS does not recognize internal storage
Does this version fix the wifi not staying on?
Did you change your settings to Never sleep for wifi and just left the wifi on? Thanks...I want to try different settings and see if I can eliminate reboots/shut downs.
are we waiting for the nightly for the newest fixes like LEDs or is there gonna be a new release like .3?
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
seanmcd72 said:
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
Click to expand...
Click to collapse
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I would have to second the issue with SetCPU. As soon as I overclocked it and began using the rom I noticed the phone would get hot abnormally fast and would reboot a few times within the first few hours. Not sure what is going on here as it worked fine on the RC.
Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I didn't even notice setcpu till you said that. Phone was back to 998mhz
Sent from my INCREDIBLE using XDA app
My phone doesn't vibrate when I receive an incoming call when the phone is set to vibrate.
Has anyone else noticed the keyboard lag when using the Messaging app? Browser and this xda app seem to work fine with no lag..
Other than that, smooth.
dnoyeb said:
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
Click to expand...
Click to collapse
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
I get random reboots and freezes every thirty minutes if so on a fresh wipe of 6.0.3 I tried with setcpu and without but always with the built in hotspot running. Same issue since RC3
LED notifications dont work. LauncherPro Plus FCs on every reboot, other then those things im good with it, great wallpapers , great rom
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Panda Fuzz said:
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Click to expand...
Click to collapse
And you know the issue is the kernel because...?
mp3sum said:
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Click to expand...
Click to collapse
actually if you read the thread, you'll see koush himself is in there dealing with 6.0.2, offering up kernels and fixes...
he just hasn't updated the topic title.
Okay this may be a stupid question but how do I apply the mail fix?
mp3sum said:
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
Click to expand...
Click to collapse
Battery life was down to 81% 11 hours later, and the phone had been placed in Airplane mode while running Gentle Alarm and a few widgets (no auto task killer).
Breakdown:
System 0.6%
System Processes 0.3%
System Panel 0.3%
android.process.acore 0.1%
Plus several honorable mentions with 0.0%. I have yet to perform this experiment with Ruby or ID.
Is Airplane mode supposed to be on all the time?
Has anybody found a good wi-fi fix yet (lots of on/off when I take it out of sleep)?
I have an app that says it can't be played on an unstable platform, any idea why?
Is there an alternative to SetCPU for CM7 that works?
Thanks everyone
buffnutz1 said:
Is Airplane mode supposed to be on all the time?
Has anybody found a good wi-fi fix yet (lots of on/off when I take it out of sleep)?
I have an app that says it can't be played on an unstable platform, any idea why?
Is there an alternative to SetCPU for CM7 that works?
Thanks everyone
Click to expand...
Click to collapse
NO.
Not that i know, Some people have problems some don't
No idea. What app? I will try it on mine.
I have not hear of anyone using one, but there are several CPU tuners on the
Market try some out and let us know.
Someone reported success with "CPU tuner" from market (free). I did not try it yet myself. Note that CM7 has most of SetCPU functionality built in, the only thing missing in profiles support.
buffnutz1 said:
Is Airplane mode supposed to be on all the time?
Has anybody found a good wi-fi fix yet (lots of on/off when I take it out of sleep)?
I have an app that says it can't be played on an unstable platform, any idea why?
Is there an alternative to SetCPU for CM7 that works?
Thanks everyone
Click to expand...
Click to collapse
I turn airplane mode on, as a matter of fact.
Go into Settings > Wireless & Networks > Wi-Fi Settings > hit Menu > Advanced > Wi-Fi Sleep Policy > set to Never. This keeps Wi-Fi on, but it doesn't shut off every time the screen goes off or appears to the system to be idle.
Which app?
For now, I just use CM7 to set my governor to Conservative. Not having policies does suck, but I can deal with it for now. CM has much bigger fish to fry at this point.
My airplane mode is on all the time but my Wifi always works. Are you running nightly 8 or later? 12 is pretty good. Wifi does not seem to lag coming out of standby at all.
What app do you have that thinks you are unstable? It is probably possible to spoof it into thinking it is on a Nexus or something.
I am 99% sure that someone involved in CM development said explicitly not to install SetCPU, because CM has an internal clock speed controller. I can verify that it does scale the processor up and down on it's own but beyond that I do not have details.
The app is Homerun Battle 3d. My favorite game, but it just won't work.
Apparently I really fell behind, because I'm on Nightly 6. When I upgrade to the latest, what upgrades should I expect besides better Wifi?
Hi,
I am having an issue where the screen takes a solid 1-2 seconds to power on after the phone has been sleeping/idling. Sometimes it's not so bad but it's becoming quite annoying, and sometimes I think the screen turns off again before it can show the lockscreen and I have to pull out the battery to fix it!
Cm7.1 stable w/cm7 kernel. Was happening on stock too.
Does anyone know a way around this? Widgetlocker doesn't seem to fix it
Thanks.
i am having a similar issue on Topogigi's v1.9, no issue on his 1.4 version, very annoying!
noticed with Topogigi's ROM since v1.9:
This issue is even worse when a call comes in: The fon will vibrate about 4-5 seconds before the screen turns on to shows the caller. Until then you can not see whos calling.
On Horsepower rc1 kernel and topo 1.9 I can't say I have noticed this issue.
Used fon was already running on v2.0 with RC1 kernel.
Also did a clean flash of the rom again to eliminate possible issues of other apps running. But this has no effect on the problem. It still persists: When a call comes in, the fon vibrates up to 5 seconds before the screen turns on. Even then, you first see the unlock screen and about a second later the screen with the incomming call. Reproducability 10/10 times. Notice that vibration for incomming calls has to be set as "always on" in settings to reproduce problem!
Extremely annyoing because call can not be answered or dismissed while fon keeps ringing! Already missed calls because called hung up before screen unlocked.
Don't know if its a kernel or rom issue...
Advice
The best way for you not to have troubles is to pick a stable rom and flash it!
If you are on Topogigi ROM, This has already been explaine in the FAQ.
Topogigi said:
Ladies and gentlemen, guys and gals, experts and noobs, here you will find a F.A.Q. collection for our ROM. Hope it will help.
Q6.But I'm still experimenting lags with overclock daemon on wakeup: how can I tune it to fit my needs at best?
A6.One of the best features of overclock daemon is that you can tune it as you like. If you don't want to see lags on wakeup, just raise a little the max frequency for sleep profile. If you want to mock SGS2 owners with astonishing Quadrant scores, raise the frequency to the max for wake profile and your phone will turn into a raging bull. It's up to you. Your interest is raising? Let's see how to do it:
Fire up ES file explorer (you will find it in my rom beginning with v. 1.6 release), open settings and check "Use Root Mode" and "Mount Filesystem" (you need to do it only once). Then exit settings and hit the highest icon on the left: you will be in the root directory of your phone. Navigate to /etc/andrev_oc, you will find six files there:
-sleep_gov: indicates which governor to use during sleep mode ("performance" or "powersave")
-wake_gov: governor for awake state ("performance" or "powersave")
-sleep(or wake)_max: max frequency to allow during sleep or wake (see frequencies below)
-sleep(or wake)_min: min frequency to allow during sleep or wake (see frequencies below)
Here there are the frequency values available on current kernel (Neoblaze 28092011):
1408000
1216000
1100000
1015000
800000
503000
389000
216000
Make your changes to the files listed above and save them.
Since overclock daemon is already up and running and it monitors these files at every screen state change, it should be enough to hit the sleep button, wait some seconds, and hit it again to wake your phone. Your new settings will be applied immediately.
You may want to check the actual CPU frequencies by using OS Monitor or SystemPanel App (download the freely from the Market).
Click to expand...
Click to collapse
Look in my signature. Download the Andrev OC app.
Set asleep maximum frequency to 800 or 1016.
Problem solved.
There is also an app for the Topogig ROM http://forum.xda-developers.com/showthread.php?p=18273457#post18273457
---------- Post added at 08:22 PM ---------- Previous post was at 08:21 PM ----------
Hahaha, same timing
Problem solved here like described. Thank you guys!
p.s.: I really appreciate the work of topogigi and spica for roms and kernel. They run 1000x better than the stock roms so I would never follow an inappropriate advice to fall back on those. Must be the urge to reach the amount of 10 posts for some ppl to get access to the dev area...
Q&A for [KK 4.4.4][ROM]Mackay ROM 4.9.13 (11-Oct-2014)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Thnx
Thankyou kasper,
I have update without problem.
Work like a charm.
Battery Life
I just installed this ROM, and previously I had the CM11 that was too slow for me. It's not incredibly fast on my I9000 but works fine, the only problem is the battery lifespan that compared to the original gingerbread 2.3.6 it's really less (10 hours almost)
Hi Kasper
I was wondering if there is going to be an update soon as the m12 has just rolled out with security fixes
Thanks for all your hard work
Hi peeps.
Just a quicky..
Is there anyway of changing screen DPI on this ROM.. If so how.??
(I have used kernel tweaker DPI function & two other DPI changing apps - but of no luck)
# sent from a blazing slim SGSi9000 using tapatalk 2 #
Profile & sound settings
Hello,
First of all, I wish to thank you, karsper_h. Your 4.9.14 ROM has given a real rebirth to my old SGS.
Unfortunately, I encounter a small problem with your rom: I am using the profile feature of CM to automatically switch setting (wifi, sounds, etc...) depending on where I am (or should I say when I am, since this is time based).
In settings/sound, I can change the ring volume all right.
However, The setting which is recorded in the profile does not get applied.
Assume the ring volume is set to the maximum. Then I have a profile called "work", where the ring volume is set to a low value.
Switching to the "work" profile does not modify the ring volume.
This was working on CM10 & CM11.
For the record, my phone went from stock 2.3.6 (factory reset) to CM10.1.3 to CM11-M12 to MacKay 4.9.14. I did not wipe the phone when going from CM12 to MacKay, considering the two roms are exactely at the same verion level.
I do not have experienced other problem: this rom is actualy fast and stable.
Is someone else experiencing this problem ?
remap bluetooth earphone buttons
Is there a way to remap the earphone bluetooth buttons ? Actually long pressing volumes up redial the last call, and long pressing volume down launch a voice recognition app that doesn't understand a word I say
thanks
Texdroider has always worked for me. It's in the store.
battery duration
How long is the battery duration with the i9000 whit this ROM (MACKAY 4) ?
james3Italy said:
How long is the battery duration with the i9000 whit this ROM (MACKAY 4) ?
Click to expand...
Click to collapse
It heavily depends on your usage of the phone.
If I leave my I9000 alone, with wifi and data off, the battery consumption can get below 1%/hour.
In my normal usage, it's about 2%/hour on average, giving easily more than one day of autonomy.
If your battery doesn't last that long, then something is preventing your phone to go into deepsleep state when idle.
To find out what is causing this, I suggest you install the application BetterBatteryStats, available on f-droid (no ads) and the playstore (with ads).
Hope this will help you.
Problem with Google Apps
Hi kasper_h
I want to say thank you for this ROM. Really vgood and probably the best rom for our GT-I9000.
Regards
elhennig
Try PICO MODULAR PACKAGE - Proper DPI Play Services (recommended) from: http://forum.xda-developers.com/showthread.php?t=2397942
I have no any problem since I start use it on cm-Mackay_ROM_4.9.14. On the new ...999 also works flawlessly.
Hello Kasper
First thankyou for this awesome rom,
I have a question for overclock,
I go to performace and to CPU frequency i select 1200MHz, but after usin phone with overclock restart automatically.
Can anyone tell me what is problem??
Your phone is designed to work at 1GHz frequency, perhaps 1.2GHz is too taxing for your phone.
Errors over and over!!!
any Crash Error that you can think about appear in my phone since yesterday! i was using this rom for months but these problems started annoying me from yesterday! it even doesn't let me check my sms messages and answer them! or even can't use dialer! etc.!
Errors:
Unfortunately, the process android.process.acore has stopped!
Unfortunately, process com.google.process.gapps has stopped!
Unfortunately, Trebuchet has stopped!
and ...
the errors show after another over and over! specially when i connect to internet(turning wifi on)
Even sometimes desktop does'nt load!! :| :| :|
Is there any solution!!??
* I don't want to lose any data and applications,sms, etc!
Problem with touch-input
Special thanks for the creator of this ROM for his efforts.
I have a question concerning a bug I am experiencing. Often I am not able to make any touch-command on the right wing of the screen, about 1cm, this is especially annoying when it happens during typing. I experienced the same bug on CM11, but not on the original firmware, I believe. The occurence is not bound to any special app, it even happens on the Home screen.
Is this a known bug and is anyone experiencing the same? Any suggestions what causes this?
Sometimes after rebooting i dont seem to be able to get my SIM card recognized and so have no mobile network.
does anybody else have this?
I think that this rom is the best of the best and i think the best rom must have the best splash screen so i prefer to change the splash screen
Hey i think you must re-install the rom and i think it will work
Sent from my GT-I9000 using XDA Free mobile app
Mackay ICS for i9000 which one?
Please could you gently tell me which is the Mackay ICS ? On the link I found 4 files
cm-Mackay_ROM_2.999_Final.zip
cm-Mackay_ROM_3.9.9_Final.zip
MackayROM_CM9_galaxysmtd_2014_1.7.zip
Mackay_ROM-1.9.0-cm10-full.zip
Hi Kasper,
I want to thanks you a lot for your ROM I use from 1.xx to 4.99 and my SGS go fine and smoth, Very Excellent Work!!! You are Great!!!
I am very happy that you are working on a ROM based on LP
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.