Develop Bugs

Solutions to issues -- Playfulgod [ROM] [UNOFFICIAL] [12.27.2013] CyanogenMod 11?

PlayfulGod's Kitkat rom is great. That said, I had one problem that was a pain in the neck to fix, so I'm posting the solution here in case anyone else experiences it.
The phone crashed, and when it rebooted, I had these issues: Settings were reset (including the device ID), the home button didn't work, the power menu was missing entries, the quick settings menu was empty, the notifications drawer was empty, and the search app wouldn't launch the chrome browser with the result link.
Settings can obviously be set by hand. But the home button, etc, were a pain. I fixed through two steps, culled from here and here
Part 1:
1. Run adb shell
2. su
3. sqlite3 /data/data/com.android.providers.settings/databases/settings.db
4. “update global set value=1 where name=’device_provisioned’;”
5. Reboot
This fixed everything but the quick settings.
To fix that, part 2:
1. adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
2. Step through the setup again.
I'd note that this appears to be a more general kit-kat issue, likely unrelated to this rom.
Hope this helps someone.
Cheers. Like I said, I love this rom, so many thanks to playful god, who will probably never see this buried in the general forum.

Activating Night Mode through shell no longer works on OOS 4.0.0

Hello everyone,
As of OOS 4.0.0, the Tasker shell method for making an automated night mode switcher no longer works. I have tried both the "settings put global night_mode_enable/d 1" as well as the "settings put secure twilight_mode 1", with or without root access, with or without "su" in front of the command.
There is a method discussed here whereby night mode can be triggered via AutoTools for Tasker, but once you pull the notification panel the setting reverts.
I have also run LogCat for when you activate night mode via the Quick Settings panel, and once when you disable it. I see the services responsible but lack the knowledge to go forth. If somebody has an idea on how to get access to night mode via tasker from the provided logs (or any other means you can suggest for me to test), please feel free to post your suggestions/solutions.
Logs: https://drive.google.com/drive/folders/0Bwu1tuojwUVbUVAzQ2xKeHNGU0U?usp=sharing
PressON is capture when switching nightmode on and vice versa.

Google Assistant

I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
Anyways, I need some testers to see how widespread this is. In android there is a permission set called WRITE_SECURE_SETTINGS. Basically you can create an app with that said permission in it's manifest. Doing so allows the app to be escalated to a 'root user' in order to edit, remove and or manipulate a set of settings Android called Settings.Secure. In this set of settings are three tiers: System, Secure and Global. The app, or anyone with access to ADB, can run a command to add, remove or change the values of some of these settings.
An app currently exists and is available on the Play Store, that edits these settings; Settings Database Editor. I need you to do the following steps for me please and thank you:
1. Download, install the app, but don't edit anything yet.
2. Hook the device up to your PC and open an ADB window.
3. Type and hit enter when done:
Code:
adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
4. Go back to the Settings Database Editor app and tap on the Secure tab.
4. Locate the following three lines, if they exist:
Code:
"alexa_enabled"
"assistant"
"voice_interaction_service"
"voice_recognition_service"
5. Go back to the ADB window. Type each of the commands below, hitting enter after each one. You won't see any reply or messages if the commands are successful:
Code:
adb shell settings put secure assistant com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_interaction_service com.google.android.googlequicksearchbox/com.google.android.voiceinteraction.GsaVoiceInteractionService
adb shell settings put secure voice_recognition_service com.google.android.googlequicksearchbox/com.google.android.voicesearch.serviceapi.GoogleRecognitionService
adb shell settings put secure alexa_enabled 0
If the last command doesn't work, go to the Settings Database Editor app and tap on secure tab. Locate the alexa_enabled setting and tap it. change the 1 to a 0 and save the setting.
6. Open the Google App and go to settings > voice > Configure 'Ok Google" or your Assistant.
The more who confirm this, the better

How can I disable double tap of home button who activates the "voice input", who is no longer avaible as Amazon decided... THANKS THEM

DragonFire1024 said:
I have discovered a way to disable and replace Alexa with the Google Assistant through what you could call a 'privilege escalation.' I don't know anything about the Fire Phone so I don't know if you can hook it up to a PC and run ADB commands to it. Can you even download Google apps (sorry if this sounds stupid)?
The more who confirm this, the better
Click to expand...
Click to collapse
Hi DragonFire1024,
Thanks for this very interesting post I was just wondering by to see if anyone had unlocked the bootloader :laugh:
Problem with the fire phone is probably 98% of users here use one of @ggow custom ROM's LineageOS 11 or the AOSP based SlimKat and Nexus Rom. Those running the Stock ROM are likely not interested in development hence why no reply's.
To be honest I never even gave the Fire OS a chance before rooting and switching to the Nexus ROM. I am not sure our fire OS has Alexa :silly: or at least as we know it today yes you heard correct a Premium Amazon Device and they see fit not push it out to Amazon device owners. In fact they just went one better and removed the voice service altogether. https://forum.xda-developers.com/fire-phone/general/amazon-voice-services-fire-phone-t3681235 Pretty amazoning :laugh
I was kinda hoping it was to make way for Alexa and a Massive OS Update but I guess thats just wishful thinking. :laugh:

Realme X2 & Tasker

Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people

bino_mat said:
Hi All,
Anybody using Tasker on Redmi X2 - Recently migrated from MIUI and facing lot of iffuce in the is color OS 6..1- Want to check for similar mind people
Click to expand...
Click to collapse
Tasker is running fine on my X2 EU version. No problems up to now

Note4Addict said:
Tasker is running fine on my X2 EU version. No problems up to now
Click to expand...
Click to collapse
That is is interesting !! - 2 problems I encountered are
1.Tasker toasts are working only with in Tasker context - I mean if open the tasker and a do a flash message ,it flashes the message- But when on a normal working (Tasker is in background) - no toast message appears.
2.Even if I enable all of the permission,when Tasker tries to switch on the WIfi with in Tasker context as window popes out asking Tasker want to switch on Wifi - Allow or Prohibit -
If Tasker is in background,this window can't appear and nothing happens.
Finally ,I went to Developer options,Disabled the permission monitoring(last option) s- that this started working
Can you please confirm on these 2 points?

Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.

Note4Addict said:
Confirm that! I had exactly the same problem with wifi on/wifi off and had to disable permission monitoring to get it working. It was the same for the initial adb permission command you need to get Tasker up and running. Unfortunately, at the moment I haven't got the chance to look into it but from version 5.9.2 Tasker has the new adb wifi commands which give it almost root like power. Perhaps one of these would be able to overcome the permission monitoring problem so that we can keep it active. Try it if you can, I would be very interested to hear if you managed to get that working.
Click to expand...
Click to collapse
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that

bino_mat said:
Sorry I didn't get some part of your message _"It was the same for the initial adb permission command you need to get Tasker up and running" - Can you pl elaborate?
" Try it if you can..." - it means the ADB wifi commands ?I couldn't locate any permission disabling commands with adb wifi.
One good news is that I tried out Tasker in Android 10- COlor OS 7 and I see that Toast functionality is working in that
Click to expand...
Click to collapse
Good news that Tasker works well in Color OS 7 which will get around March it seems. Regarding the initial ADB permission, I meant the message you get when you first install Tasker on a non-rooted device. In that case you need to execute a specific permission command via ADB to get Tasker up and running correctly.
What I meant with "Try if you can..." is that If you have the opportunity you may want to check if perhaps one of the new ADB wifi commands would be capable of setting wifi on and off despite permission monitor being active instead of disabled as we're doing now. Hope that will work so we can keep permission monitor active.

Guess ,it is more of Color OS issue , with the battery saved enabled,Tasker is missing the Alarm - I did a simple experiment of logging of BAttery level to a file in every 10 minutes.
If I look at the file now ,either the logging is not continuous or stopped after sleeping for one or hour or so !!! -- But this is not the case with MIUI - It's sharp on time with battery saver or not.
More importantly one thing I noticed is that when battery saver is on ,you can't lock the application in memory - Flip side , with battery saver on ,if I invoke recents and clear the memory ,evrything will be wiped and even when battery saver is off,the applications which you want to be in memory in normal condition will not be there!!!

Bluetooth problems with Android 10:
With my Realme X2 and Realme Ui 1.0 (Android 10) i can not start Bluetooth because my smartphone always asks with an popup for an permission ("Tasker needs the following permission: set Bluetooth on/off"). My desktop links give me the error code "action bluetooth failed".
How can i disable this popup asking for an permission? Or can i made tasker to click on yes itself?

Disabling vibrations on Android 11

Is there a way to completely silent the phone without ANY vibrations? I can do that when I was on MIUI 11 and xiaomi.eu version. I want to use lineageos rom because it's lightweight and it has a dark mode.
I have a fear of vibrations, to the point that I think that I'm going to die, so I really want to remove it.
I found out disabling vibrations using adb but only for specific apps and it goes back when reinstalled.
cmd appops set <package> VIBRATE ignore
But with this I have to loop through all of the packages and run the command, when there's a new app installed, I need to run the command again.
Is there a way to remove the vibration using an app or at least an easier to execute command?
My phone is rooted, if that can help. Please help me.