[app] Turbo toast [A solution of Motorola Turbo charger Toast for custom ROM]

rsthdn

New member
Feb 20, 2013
3
2
0
Kathmandu
Turbo toast not working on lineage os 15

This used to work on stock room of moto g5 plus. But it's not working on rooted lineage os 15 for moto g5 plus. Is there a solution?
 

fgl27

Recognized Developer
Feb 27, 2014
3,623
9,418
263
Brazil...South of the south
This used to work on stock room of moto g5 plus. But it's not working on rooted lineage os 15 for moto g5 plus. Is there a solution?
los 15 is not 100% stable are you shore is not a ROM problem?
I need proper logs pull as root, logcat and dmesg after the problem has be manifested, and a detailed description of the test you do to make shore is a app problem...
 

rsthdn

New member
Feb 20, 2013
3
2
0
Kathmandu
los 15 is not 100% stable are you shore is not a ROM problem?
I need proper logs pull as root, logcat and dmesg after the problem has be manifested, and a detailed description of the test you do to make shore is a app problem...
I know los is not 100% stable. But when I clicked Test Toast option, it showed me "Device Model: XT1686 Current Charging type is: Turbo".
 

GTMoraes

Senior Member
Dec 3, 2010
1,553
337
0
Recife
Same issue as stated above. Root works, app detects Turbo, but it doesn't show any toasts.
Running some Oreo ROM I found around. ARM64

We can discuss this further through PM in portuguese if you wish
 

FlavioV

Senior Member
Jan 25, 2013
359
264
83
Same issue as stated above. Root works, app detects Turbo, but it doesn't show any toasts.
Running some Oreo ROM I found around. ARM64

We can discuss this further through PM in portuguese if you wish
Please provide some logs as requested above. There's no stable Oreo ROM for quark just yet so bigs like this are expected but nothing can be done if the dev can't figure out why the toast isn't showing up.
 
  • Like
Reactions: ChazzMatt

GTMoraes

Senior Member
Dec 3, 2010
1,553
337
0
Recife
Please provide some logs as requested above. There's no stable Oreo ROM for quark just yet so bigs like this are expected but nothing can be done if the dev can't figure out why the toast isn't showing up.
Using catlog (which I can't figure how to copy the whole log, like I could years ago), I can only find two logs related to toasts,

Code:
12:32:48.467
777 BroadcastQueue - Warning: Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_CONNECTED flg=0x4000010 (has extras) } to com.bhb27.turbotoast/.TurboToastReceiver

12:32:54.496
777 BroadcastQueue - Warning: Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.bhb27.turbotoast/.TurboToastReceiver
This seems related to when I connected the charger and disconnected, for logging purposes.
It seems the app's not allowed to run on the background. I think I know what's causing this (Oreo's new background activity limiter).
I'll see what I can do here and will report back later
----------------------------------

Can't fix this on my own. It's like this app was "designed for Oreo" so I can't manually dictate how the app background behaviour should be.

Could the dev take a look at this and figure out what's needed to do:
https://commonsware.com/blog/2017/04/11/android-o-implicit-broadcast-ban.html
 
Last edited:

fgl27

Recognized Developer
Feb 27, 2014
3,623
9,418
263
Brazil...South of the south
Using catlog (which I can't figure how to copy the whole log, like I could years ago), I can only find two logs related to toasts,

Code:
12:32:48.467
777 BroadcastQueue - Warning: Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_CONNECTED flg=0x4000010 (has extras) } to com.bhb27.turbotoast/.TurboToastReceiver

12:32:54.496
777 BroadcastQueue - Warning: Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.bhb27.turbotoast/.TurboToastReceiver
This seems related to when I connected the charger and disconnected, for logging purposes.
It seems the app's not allowed to run on the background. I think I know what's causing this (Oreo's new background activity limiter).
I'll see what I can do here and will report back later
----------------------------------

Can't fix this on my own. It's like this app was "designed for Oreo" so I can't manually dictate how the app background behaviour should be.

Could the dev take a look at this and figure out what's needed to do:
https://commonsware.com/blog/2017/04/11/android-o-implicit-broadcast-ban.html
try the attached, uninstall the app if you can't install the attached...
 
Last edited:

thegun02

Member
Feb 12, 2018
6
1
0
FC

Sent from my HWCUN-L6735 using XDA Labs

---------- Post added at 01:55 AM ---------- Previous post was at 01:48 AM ----------

U

Sent from my HWCUN-L6735 using XDA Labs

---------- Post added at 01:57 AM ---------- Previous post was at 01:55 AM ----------

Kx

Sent from my HWCUN-L6735 using XDA Labs
 

meltbanana

Senior Member
Feb 13, 2018
263
119
53
Hi,
I was able to use turbo toast on my xiaomi redmi 4X successfully under under android 7.1.2 32-bit, however it doesn't work now on oreo lineageos 8.1.0 64-bit.
ampere shows I don't get more than ~1300 mAh though I'm using the same motorola fast charger than before.

best regards
 

fgl27

Recognized Developer
Feb 27, 2014
3,623
9,418
263
Brazil...South of the south
Hi,
I was able to use turbo toast on my xiaomi redmi 4X successfully under under android 7.1.2 32-bit, however it doesn't work now on oreo lineageos 8.1.0 64-bit.
ampere shows I don't get more than ~1300 mAh though I'm using the same motorola fast charger than before.

best regards
Just because you are using the same changer doesn't mean it can turbo charger in any device. I say that because a device can't really change OS from 32 bits to 64, so I assume you change the device and not just the OS as you seem to imply.

If the app doesn't show turbo is that simple the device and charger are not syncing, if the device can charger on a higher amperage you may need a proper charger for it.

That is something not really related to this thread, so I recommend you to find a general thread about that device and share that with others owners of that particularly devices, or on the particularly ROM thread of the device if there is one.
 

meltbanana

Senior Member
Feb 13, 2018
263
119
53
Just because you are using the same changer doesn't mean it can turbo charger in any device. I say that because a device can't really change OS from 32 bits to 64, so I assume you change the device and not just the OS as you seem to imply.

If the app doesn't show turbo is that simple the device and charger are not syncing, if the device can charger on a higher amperage you may need a proper charger for it.

That is something not really related to this thread, so I recommend you to find a general thread about that device and share that with others owners of that particularly devices, or on the particularly ROM thread of the device if there is one.
I'm still charging with a motorola turbopower which offers 3A output. what I mean is:
with 32-bit MIUI ROM and turbo toast it worked, now I'm at lineageOS 8.1.0 (oreo) 64-bit and it doesn't.
you think it's device specific or kernel related?
 
Last edited: