Database Info

[Guide] Multi User Setup for Kitkat 4.4.4 (for noobs)

This tutorial will show you how to setup your device as admin and configure other user profiles (this is important when you're not the owner). Your device maker disabled multiuser functionality in Kitkat, like on my Lenovo Tab 2 A10-70L? - then this for you. At least, that's where this procedure is tested on. Afaik, this should work on Lollipop too. But will it work for your device? - No clue, you tell us!
Basically it's an accumulation of what I've read here (thanks again) and my personal experience as a noob myself.
So far, this guide is incomplete and I'm hoping for some pro tipps to perfect it. Please help me sort out the unclear parts highlighted in red and I'll update this post accordingly. The sooner the better, because this actually is not my device and someday soon I'll have to pass it over to my mom since it's my present to her, I'm only setting this slab up...
Preconditions:
Android treats the first account created as "owner". Only owner will have root privileges if installed accordingly (=admin).
Root permission and a file manager (e.g. ES File Explorer) are required for this fix so go get that first. For the Lenovo Tab 2 A10-70L, I followed this beautiful guide, besides that, I can't help much here.
Unable/uninstall all bloatware (I was adventurous with Titanium Backup with no probs so far, but some crap remained from looking at new user folders; still in search of a vendor/device-specific "save to remove" list)
Install ALL apps you and the other users suppesdly need. This will avoid the need to redownload and reinstall all the apps for each and every user wasting storage. Think thrice, usually it'll be more than desired, but better you do it instead of a DAU... Each user will be able to install apps later though. Full control over user restrictions can be applied for "guest profile" only.
Steps:
In file explorer, go to /system/ and open build.prop
Check if you have anything like the below text (you shouldn't, otherwise edit accordingly) and add these lines at the end of it:
Code:
# Multi Users
fw.max_users=[COLOR="DarkGreen"]X[/COLOR]
fw.show_multiuserui=1
Replace X with your desired digit (up to 7?)
(I've read somewhere that 7 users is maximum that system can handle, but I haven't tried)
Save, reboot and log in as "owner" (your profile)
Go to Settings>Device and say hello to new item "Users"
Create new users and/or a guest profile (important: write down the order in which you created them!)
All new user profiles are now shown as "new user" no matter what you wrote in the profile properties (only guest will be shown as "guest"). Mind you, this also applies for the lockscreen!
In file explorer, go to /data/system/users/ to find your users' folders containing some system files (what exactly?) Now guess what - the order of the numbered folders and #.xml files match the order you created them. "0" is you, the owner.
Open each .xml file and replace "Owner" with "Your Name" and "New user" with "Username"
Put the device to sleep, trigger lockscreen and log in to each user profile and
Pull down shortcut menu from top right and enable autorotate
Go to Settings>Users>Security, check all settings and note each unlock-code
Disable background services like sync, location, etc. that could potentionally drain battery where applicable
Rinse & repeat 8) for all new profiles
Install "Multi-User App Share" and set apps per user. (Or is there a newer app or more hackish approach without the need for xposed or compiling stuff etc.?)
= DONE =
If you want the user icon in status bar, follow http://forum.xda-developers.com/gal...-users-mod-t3017782/post58659868#post58659868 (haven't tried that ).

Well... build.prop fixes are working, at least for me. It's good alternative to multi-user app from Xposed (we don't want to use Xposed too much...).
Still tried with decompiling & compiling framework for fixing icon problem, and... in framework-res there is not status_bar_expanded_header.xml file, se we are in deep ****.
I am working on: LP

Google daydream home on htc bolt [root\twrp\sd card required]

The following guide should allow you to run Google Daydream (including the Google Daydream Home Screen) and any Daydream Compatible apps on your HTC Bolt. But of course I can't be held liable for any problems, damage, issues that following this guide may cause you.
- Prerequisites-
* A rooted HTC Bolt with TWRP Recovery installed and an SD card. (I am also s-off, but I don’t know if that helped me achieve this or not...I'm also running Bad Boyz Rom but doubt that changed anything either)
You will need Google Daydream, Google VR Services, and Daydream Keyboard installed beforehand. (even though they won’t be able to work properly yet)
You will also need the app “Root Power Explorer” and “QuickEdit” which are both free from the Play Store.
* You will also need second device running Android that has a gyroscope and Bluetooth capabilities that will be used as your controller. (I used an old Galaxy S4, I will refer to this as the “Controller Device”)
*You’ll likely want a VR viewer of some sort too…but I suppose that’s not really required…
-Guide-
1. Now that you have all of the apps installed the first thing you’ll want to do is open “Root Power Explorer" and navigate to:
/system/etc/permissions/handheld_core_hardware.xml
Now copy the handheld_core_hardware.xml file to your SD card and rename it handheld_core_hardware_original.xml (We do this because in the next step QuickEdit can’t save the file in the root directory even with RW enabled)
2. Open “QuickEdit” and navigate to the SD card and open handheld_core_hardware_original.xml
3. Under “Permissions” will be a list of items… add the following two lines to the bottom of that list:
<feature name="android.software.vr.mode" />
<feature name="android.hardware.vr.high_performance" />
Now save it as handheld_core_hardware.xml to the SD Card. (be sure to keep the original just in case things don't work and you need to use ADB to fix things)
4. Go back into “Root Power Explorer” and navigate to:
/system/etc/permissions/handheld_core_hardware.xml
and delete that file.
5. Now navigate to the SD Card and copy the file you saved at the end of step 3 to:
/system/etc/permissions/
6. Now this step is important. The file you just moved doesn’t have permissions (I think). (If you skip this step your phone will still boot up after a restart but your launcher will promptly close when you launch it.)
Reboot your phone to TWRP Recovery and click “Mount” and check the box next to “System”.
Now go back to the TWRP main menu and go to Advanced and then File Manager.
Navigate to /system/etc/permissions/handheld_core_hardware.xml
Click “chmod 755”and swipe the slider. Now click reboot system.
Now your launcher might close once (mine did) but after that everything should be running normal.
7. Open up Google Daydream and go to settings and tap the*build version 7 times to show the*developer options.
8. Open developer options and check the box “Skip VR Entry Screens”
9. Now you need to set up your “Controller Device” .
This device will need Google’s Daydream Controller Emulator installed on it.
Use the following guide (includes a download of the APK download and how to set it up). https://developers.google.com/vr/daydream/controller-emulator
10. Once your controller emulator is set up on the “Controller Device” and is Bluetooth paired to your Bolt and selected in Google Daydream’s Developer Options” you should be good to go!
-----------------------------------------------------------------
Let me know in the comments if you try this! I'd love to know that my first guide I've ever done actually helped someone!
Also I could definitely use a few like on my account!

Looks interesting...I admit, I know nothing about daydream, guess I need to do some research...

I got it running works pretty good other than the phone getting hot and the controller going in and out. Also if you click the VR button in the daydream app it always force closes, however if you just open the app in daydream library and all your installed VR apps work just fine. I guess you could probably open them independently too just the way I was doing it. Good work around till we get official support,now I'm not as jealous of my brother's pixel.

[ROOT][MOD][HOW TO] Disable Presidential Alert Text Messages EASY METHOD

DISABLE PRESIDENTIAL/ CMAS ALERTS-ALL COUNTRIES
I'd like to say the original post about how to do this is here: https://forum.xda-developers.com/showthread.php?t=1829681
This is an easier, alternative method that only takes a few minutes. Since September 20Th 2018 is closing upon us fast, here is a method to get rid of the emergency broadcasts.
DISCLAIMER:
Always have your phone backed up in TWRP and also for safety one should create a copy of the XML file being addressed. I am not responsible if you brick your phone. (Luckily with this method it is near impossible to do so).
NEEDED:
-Rooted Android
-Quick Edit Text Editor (https://play.google.com/store/apps/details?id=com.rhmsoft.edit)
GUIDE:
-download quick edit and open the application
-in the app, select internal storage
-go to the parent directory "/ "
-go to "data" then "user_de" then "0" then "com.android.cellbroadcastreceiver" then "shared_prefs"
-open the file "com.android.cellbroadcastreceiver_preferences.xml"
-change presidential value to "false" and whatever else you'd like to be changed
-press back button and save changes
-restart your phone
(Some phones may not have the file in that specific directory. If not refer to the original guide).
This method was tested on a Moto Z2 Play US Retail edition running 8.0.
Please keep the ethics of whether one should disable this feature or not out of this forum. Thanks
PICTURES:
https://ibb.co/fNQwqU
https://ibb.co/h16Ec9
https://ibb.co/iue0H9
Also this can be done with an unrooted phone but you'll need to edit the file on the computer and save it that way.

ihateverizon1 said:
DISABLE PRESIDENTIAL/ CMAS ALERTS-ALL COUNTRIES
I'd like to say the original post about how to do this is here: https://forum.xda-developers.com/showthread.php?t=1829681
This is an easier, alternative method that only takes a few minutes. Since September 20Th 2018 is closing upon us fast, here is a method to get rid of the emergency broadcasts.
DISCLAIMER:
Always have your phone backed up in TWRP and also for safety one should create a copy of the XML file being addressed. I am not responsible if you brick your phone. (Luckily with this method it is near impossible to do so).
NEEDED:
-Rooted Android
-Quick Edit Text Editor (https://play.google.com/store/apps/details?id=com.rhmsoft.edit)
GUIDE:
-download quick edit and open the application
-in the app, select internal storage
-go to the parent directory "/ "
-go to "data" then "user_de" then "0" then "com.android.cellbroadcastreceiver" then "shared_prefs"
-open the file "com.android.cellbroadcastreceiver_preferences.xml"
-change presidential value to "false" and whatever else you'd like to be changed
-press back button and save changes
-restart your phone
(Some phones may not have the file in that specific directory. If not refer to the original guide).
This method was tested on a Moto Z2 Play US Retail edition running 8.0.
Please keep the ethics of whether one should disable this feature or not out of this forum. Thanks
PICTURES:
https://ibb.co/fNQwqU
https://ibb.co/h16Ec9
https://ibb.co/iue0H9
Also this can be done with an unrooted phone but you'll need to edit the file on the computer and save it that way.
Click to expand...
Click to collapse
Trying this on my Nexus 5 (Hammerhead D821) and while I can find and edit the file, it looks like the line pertaining to presidential alerts is missing.
Should I edit it in and set it to false?
Also, when I rebooted and checked the Emergency Alerts config in the Settings app, the boxes were still checked/active.

The new values re-enable themselves upon rebooting.
Any thoughts on how to make them permanent?

Update from my previous post: I've used Titanium Backup to freeze Cell Broadcasts and then an su terminal to remove /system/system/priv-app/CellBroadcastReceiver/CellBroadcastReceiver.apk completely. Confirmed the .apk file did not come back after reboot.
Do the XML files still need to be edited? I couldn't find the files in the original path, I had to go elsewhere and unfortunately did not write down where I found them (there were 2 XML preference files.)
Also, fossils-n-dents definitely deserves an answer. I don't mean to try to draw attention away from his/her question.

What ELSE can they do with carrier authorisation for WEA?
We had the "Presidential" Wireless Emergency Alert go USA-wide on 03 October (I'm roaming from Europe so this was a big shock). I'm less concerned with how to disable alert messages than any back door that WEA compatibility might provide carriers to manipulate the phone beyond sending a 90-character text-only message.
Can anyone post evidence that com.android.cellbroadcastreceiver & other service apps don't provide an opportunity for the carrier to control, shut down, commandeer or enable surveillance on the phone? FYI I'm not an Android developer but can read code & comments, I just don't know where to look....

CelticWhisper said:
Update from my previous post: I've used Titanium Backup to freeze Cell Broadcasts and then an su terminal to remove /system/system/priv-app/CellBroadcastReceiver/CellBroadcastReceiver.apk completely. Confirmed the .apk file did not come back after reboot.
Do the XML files still need to be edited? I couldn't find the files in the original path, I had to go elsewhere and unfortunately did not write down where I found them (there were 2 XML preference files.)
Also, fossils-n-dents definitely deserves an answer. I don't mean to try to draw attention away from his/her question.
Click to expand...
Click to collapse
Since you are using titanium Backup, why don't you just backup and uninstall cell broadcasts 9 app?

rphair said:
We had the "Presidential" Wireless Emergency Alert go USA-wide on 03 October (I'm roaming from Europe so this was a big shock). I'm less concerned with how to disable alert messages than any back door that WEA compatibility might provide carriers to manipulate the phone beyond sending a 90-character text-only message.
Can anyone post evidence that com.android.cellbroadcastreceiver & other service apps don't provide an opportunity for the carrier to control, shut down, commandeer or enable surveillance on the phone? FYI I'm not an Android developer but can read code & comments, I just don't know where to look....
Click to expand...
Click to collapse
Cell broadcast receiver has no permission to use anything except (send and receive SMS messages).

[Root] [HD 10 Suez] Remove parental control applications/restrictions [May 2019]

I've tried to complete this mission a few times, each ending in disaster...until now.
Summary:
The parental control applications too are restrictive. Amazon made some slight changes to the Android code which gave these applications full, and in my opinion unnecessary control of the tablets and the security options. Disabling or uninstalling them can and will eventually cause you to reflash stock firmware. That's because they are labeled as "device/profile owner applications". Located in /data/system is 'device_owner.xml'. That file configures the apps as device/profile owners and doing anything to stop them results in a disaster, often unfixable without reflashing stock. The idea was to trick FireOS by switching device owner applications right from under it's nose. It's not easy but it is possible.
This will be along guide. one or two of these steps may not even be necessary but I am going to present them as I did them and was successful. Beyond that you are free to remove steps and try the process at your will. However any deviation from the guide can result in damage to your device. Even this guide may result in damage to your device, because not everyone's results will be the same. From here on out you are on your own and I am not responsible for any damage done to your devices. This will take some time, if you do not have it it is recommended you do not continue until you do. It will not be possible to pause for extended periods through this guide. This WILL REQUIRE a factory reset. You must be rooted or have an unlocked tablet to complete the guide. You must also have the Google play store and related services installed as system applications in priv-app folder. For this it's recommended to flash a pico Gapps package in TWRP.
THIS OPERATION WAS PERFORMED ON A DEVICE THAT WAS DEODEXED ON 5.6.1.0 WITH A 5.3.6.0 (LATEST FIREOS) BOOT IMAGE. This will not likely work on a stock ROM that has not been deodexed.
Instructions:
1. You need to download an application that uninstalls system applications. Any one of them will do so long as it works. You will absolutely need to download an application that does this. Also download a root file explorer.
2. Uninstall the application called 'Managed provisioning.' then open a shell using a terminal emulator or ADB. Then type the commands below.
Code:
adb shell
su
settings put global device_provisioned 0
3. Go to settings > security > device administrator and make sure Google pay is a device administrator. This is very important and you must not miss this step.
4. Using a root explorer, go to /data/system and copy device_owner.xml to your internal storage. If using your PC please use Notepad++, though it's recommended you complete the following tasks on your device.
4b. Go to system/etc/permissions/ and open handheld_core_hardware.xml in a text editor. Find the line that says: <!-- feature name="android.software.managed_users" --> and replace that line with the one below, save the file and reboot:
Code:
<feature name="android.software.managed_users" />
5. Then go to your internal storage and open the file device_owner.xml in a text editor. Replace the lines of text with the text below, making sure the format is NOT changed from the original and save the file:
Code:
<profile-owner package="com.google.android.gms" name="Google Play services" userId="0" component="com.google.android.gms/com.google.android.gms.mdm.receivers.MdmDeviceAdminReceiver" />
6. NOTE: this step CANNOT be done in TWRP. Again Using a root explorer, copy and paste device_owner.xml to /data/system, overwriting the current one (remember to back up the original). Set permissions to rw (0600) and reboot. If there are no errors or popups and your home and recents button still work after rebooting, continue to the next step.
7. Reboot to recovery and clear/wipe cache and dalvik and reboot system. When booted, if no pop errors from anything, open the uninstaller app you downloaded and uninstall Parental Controls and Parental monitoring. Again reboot to recovery and wipe cache and dalvik and reboot system.
8. Again if no errors, reboot to recovery again and this time do a factory reset. This step is very important and cannot be missed. It is absolutely required that the data be wiped on the device or the device and system will recognize it is no longer owner of said device and it will start shutting you out of security and other options on the device.
9. When rebooted, Open the shell in terminal emulator again or ADB and type the following command below. A reboot should not be necessary when done:
Code:
su
settings put global device_provisioned 1
10. Download an activity launcher (I use activity manager and yes you need to pay a slight fee to use the root part of the launcher, but it's worth it.) Scroll settings and search for 'generic lockscreen set' and long press it to open it with root access. All of your lock screen options should be open and available to you even after removing the parental applications. If they are congratulations you have now remove parental applications and the restrictions that came with them from your device. Go back to /data/system and you will also notice that the device_owner.xml is gone. Killing 2 birds with one stone. If any lockscreen options are blocked then you have failed to properly remove the parental applications and the policies that go along with them.
NOTE: You may need to deactivate 'smart lock' and trusted gms as that may interfere with some lock screen options.
I'll let you guys decide, but I think the device is vastly improved in terms of performance and in Internet connectability after removing these applications.

Edit: forgot a step. Can't believe I did that.
Sent from my Amazon KFSUWI using XDA Labs

I must have goofed. I did a factory reset and now my tablet is back to stock. lol
Edit: I take that back. I tap on parental controls and nothing happens lol
Edit2: Yep It's running good. You were right too. It seems like it runs a lot smoother without amazon's parental controls.

Shadow Death said:
I must have goofed. I did a factory reset and now my tablet is back to stock. lol
Edit: I take that back. I tap on parental controls and nothing happens lol
Edit2: Yep It's running good. You were right too. It seems like it runs a lot smoother without amazon's parental controls.
Click to expand...
Click to collapse
Cuz I'm pretty sure without the support of manage profiles, the parental applications actually cut down on a Wi-Fi speed. I don't think it's cutting short the connection, rather the metrics and scripts associated with other apps and configs, cause it to constantly disconnect and reconnect. also fireOS doesn't like when you have more than one network saved at a time, in the same area. You can also delete etc/wifiloglevels.sh if you are on the deodexed rom. Can also set the value of the line in build prop for wifi rssi levels to ""

Shadow Death said:
I must have goofed. I did a factory reset and now my tablet is back to stock. lol
Edit: I take that back. I tap on parental controls and nothing happens lol
Edit2: Yep It's running good. You were right too. It seems like it runs a lot smoother without amazon's parental controls.
Click to expand...
Click to collapse
Add: you Dan probably reinstall the managed provisioning app. It might let you create a work profile I am not sure. I am going to experiment with that more tomorrow.

I'd like to add that I am on the same battery cycle as the other day when I started this process at 65%. I haven't been as aggressive in my use as much as normal this weekend but I haven't had to put it on the charger all well and usually I have to do that a few times a week if I really use it.

I forgot to mention that step 4 and possibly 5 seem jumbled.

Shadow Death said:
I forgot to mention that step 4 and possibly 5 seem jumbled.
Click to expand...
Click to collapse
Are you using the app?

DragonFire1024 said:
Are you using the app?
Click to expand...
Click to collapse
I'm not sure what app you mean. What I meant was this part:
Using a root explorer, go to /data/system and copy device_owner.xml to your internal storage and open it in a text editor. If using your PC please use Notepad++, though it's recommended you complete the following tasks on your device. Open system/etc/permissions/handheld_core_hardware.xml in a text editor.
Click to expand...
Click to collapse

Shadow Death said:
I'm not sure what app you mean. What I meant was this part:
Click to expand...
Click to collapse
I'll fix it tomorrow. Thanks.

DragonFire1024 said:
I'll fix it tomorrow. Thanks.
Click to expand...
Click to collapse
I figured out what you meant but I thought I would point it out just in case others can't.

Shadow Death said:
I figured out what you meant but I thought I would point it out just in case others can't.
Click to expand...
Click to collapse
Worded it a bit better and broke it apart somewhat. I definitely saw where one would get lost right there. Good eyes!

Hi Dragon Fire,
Is it now working ok? I have the HD8 (7th generation) and would like to eliminate the restrictions of the parental control.

masterted said:
Hi Dragon Fire,
Is it now working ok? I have the HD8 (7th generation) and would like to eliminate the restrictions of the parental control.
Click to expand...
Click to collapse
Every thing is working so far as I can see. There is a slight delay with some apps that require a lock screen be activated for them to work. I use a WiFi app my provider provides and it requires a screen lock. It failed to recognize it at first. Clearing the providers app cache and restarting it worked.
Sent from my Droid RAZR M using XDA Labs

Hi guys, I got a couple questions about this process...
Could someone who did it already check to see if it is possible to change the language of the tablet? On my own tablet, I get a message about parental controls being required, however my own tablet was rooted and debloated a different way last year. In my case, I don't care about changing the language, and I'm totally satisfied with the results I got.
I ask because I'd like to do this "stock Android look & feel" process for a friend (they do not even have an Amazon account, nor want one), but they need to be able to switch language between English and Spanish on a regular basis, and I don't want to mess up their tablet with mods that would prevent this.
Thanks for any insights you guys might have on this... really appreciate the hard work and vast knowledge represented here on XDA.

Kids Dashboard free app and free cloud (Basically you are making dashboard kiosk like small mdm).
PLAY STORE LINK : https://play.google.com/store/apps/details?id=com.tabnova.aidashboard
Cloud Login: https://cloud.kidsdashboard.com
Main site : http://www.kidsdashboard.com/
Complet free app enjoy dont waste money

Is there any way to update wpa_supplicant conf in Android 9

Hi All,
My first post here, I am not sure I am posting in the correct section.
I need to update the wpa_supplicant conf of my Andorid 9 phone (an Asus Zenfore Max Pro M1) in order to allow it to connect to a MFP (managed frame protected) network.
I managed to configure my home linux machines to do so but with my Android phone it is a disaster.
From what I know the device needs to be rooted...for this I am just proceding with the proper steps but...I am not sure that the wpa_supplicant.conf to be modified is the one settled in the /etc directory as I ve read that on Android the conf file for the wpa_supplicant service may be different.
Is there any way to understand which configuration files a binary executable is bound with?
What I am trying to do is to set the pmf option in the correct wpa_supplicant.conf file in orded to let the device connect to a MFP network.
Any help will be so much appreciated.
Thanks!

Well...it is nice to discover that Android 9 is not using wpa_supplicant any more and that it will be a nightmare to crosscompile it and configure it as a daemon
This is my last android shxt phone.

A quick search reveals that WifiConfigStore.xml should be the file you want. requirePMF might help, from source for WifiConfiguration.java. I can't find any more documentation than that (opening source files kills my phone browser) but that should be a good start.

Thanks Efreak2004 but have tried that way as well.
Have modified the WifiConfigStore.xml by setting to true the requirePMF option but it did nothing.
My suspect is that the java wrapping useless stuff is not doing anything more than trying to "steer/drive" the native processes preposed to do the job. It has always be this way since the invention of java which was wrapping lib C in any aspect.
I am almost convinced that without the wap_supplicant binary/daemon there is no way to let the java fancy wifi manager do the job by its own.