I know have multiple user accounts is a feature for Lollipop but seems to have been removed from Samsung. Anyone know how to enable to feature or an a workaround?
The code is in the firmware; you need to edit your build.prop. You'll see the user tab in Settings and user icon on top right of pull-down and quick toggles screens.
Add the text at bottom to end of build.prop; leave one blank line at bottom of build.prop, but no spaces in margin to right as shown if you copy all lines to paste. Alternately, you can use a root browser to do this manually or use a prop editor like this one below:
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Be careful. Consider at your own risk; you can potentially harm your phone's performance or even prevent it from booting-up, requiring you to restore the original build.prop in TWRP file manager or a full TWRP restore. Make an unmodified backup up both build.prop and full TWRP backup image to be safe.
Reboot to apply after build.prop edit. You can use less users, if preferred.
# Add extra personal user accounts
fw.max_users=5
fw.show_multiuserui=1
fw.show_hidden_users=1
fw.power_user_switcher=1
Sent from my SM-N910P using Tapatalk
Related
*Pretty please make a NANDROID backup before you do this. I know you just recently installed the ROM, so if you don't have much on there and don't mind to flash in the event that something goes wrong, then no worries. Still, it wouldn't hurt!!*
Basically, what we are doing here, is giving you the app, installing it on the phone and then copying the APK file from /data/app to /system/app. I don't know much about the Fassy, but the file system structure should be close.
There are two ways to do this. You can use ADB to execute the commands, or use a file explorer (I use Root Explorer) to move the APK file. I also picked a free APN app .
APN Manager Pro
Throw this on your external SD card. Once you have it on there, open up your File Manager.
Navigate to your external SD card(should be /mnt/sdcard/external_sd or something similar, we have already established our phones are slightly different, ha ha).
Find the file ale.android.apnmanagerwithanimation-1.apk and long press it. You should get a list of options. You want to select move.
Navigate back to your root directory.
Go to /system/app. Once you get there, depending on your file manager, you should have the option to set the permissions as r/w (read/write). By default, Root Explorer is always set to r/o (read only) on my phone.
Paste the APK file.
Long press the APK file and select permissions.
- You have three sets of privileges: Read/Write/Execute
- You have three sets of groups: Owner/Group/Others
- - Make sure Owner, Group and Others have checks under Read.
- - Make sure Owner has checks under Write.
- - There should not be any checks under Execute.
- - There should not be any checks on any of the special permissions.
Hit OK.
Click on the APK file and select install.
Once the install has completed (should be almost instantly) reboot the phone.
Now you have an app that is capable of setting APN information.
When the phone has booted back up, open the app and select Backup & Restore. Make a backup. If the new APN doesn't work properly, you will have a backup you can fallback to.
Enter the information and hit save. Once you have done that you can select the APN and set it as the main. If you lose functions then restore the backup.
I hope this works out!!
What's the information u have to input?
jaysmi32 said:
What's the information u have to input?
Click to expand...
Click to collapse
what company do you need the info for
Boost mobile!
I just recently moved to ICS on my Samsung Galaxy S2 (Epic 4g Touch) and I can't seem to get all fonts in all locations system/apps to change to the new font.
Up until now, I have always used rom toolbox pro to flash my fonts with my Gingerbread roms and everything has always been themed in the chosen text (all apps/menus/text on websites/text in facebook ect).. Love the patronne font. So I upgraded my phone to the Blue Kuban ICS rom built off of FF18. I downloaded romtool box pro to change my fonts like I have always done in the past. I select the font and then install. After the reboot from the fonts being updated, the system menus updated and anything that shows regular (non bold, non italic) fontsdisplays as the new patronne font.
Anything within apps that have bold or italic fonts does not appear as patronne. They appear as the regular system fonts. So i go into the font installer preferences within the rom tool box app and cloctopia.tff and roboto-Regular.tff are selected.
I have tried to select (enable) the roboto-bold and the roboto-italic with no success. the phone will not boot after rom toolbox pro messes with those files.
I restored the default fonts. Then installed the rosemary and a few other flipfonts that are all apks that do not require a reboot/flash. Now the system font is updated (not anything with the clock widget) and italic fonts are now showing the installed apk but bold fonts still show system default font and not new themed text. This is the same case with other fonts that I have tried to install as well.
I have listed some apps below that are not consistent on displaying the themed font. Probably due to which roboto its referencing???
Patronne font from rom toolbox
System menus - patronne
RSS Demon - Feed list - system default, article list system default, article Patronne
Touchdown Exchange - Email list (read and unread emails), appointment/calendar, and contacts show default font
Facebook feed text - System default
XDA app - Forum list - system default, thread list - system default, article (user text) typed text is patronne and quoted text is system default.
APK - Flip fonts (rosemary, sony sketch ect)
System menus - does reflect new themed text
RSS Demon - Feed list - system default, article list reflects installed themed font, article displays in installed themed font
Touchdown Exchange - Email list (unread email - shows bold - shows system default and read emails show in themed font), appointment/calendar system default, and contacts show themed font
Facebook feed text - System default
XDA app - Forum list - themed, thread list - themed, article (user text) typed text is themed and quoted text is themed.
I am guessing that ICS handles things differently with fonts than GB. Is there anything that I can do to get all text displaying the themed text?? I am at a loss on what else to try in order to get all text being themed and not partially.
I was hoping that someone with more experience on fonts/themes would be able to tell me how to fix or what to change so all text appears the same.
Found a solution to the incomplete font themeing
Well after some trial and error I finally figured out what was going on with the fonts. ICS is way more picky on the font files than GB was. None of the font changing programs (romtoolbox Pro, flipfont ect) work 100% or even without at times causing boot loops. This is because the apps themselves do not update the metadata to match the font name. GB never checked the meta data or I guess didn’t care if it matched. ICS does and if it doesn’t match, you get boot loops.
The installable APKs do a better job but would still miss updating Bold and/or Italic fonts.
This is what I did to get 100% themed font without boot loops. Unfortunately it is a manual process.
*****Now for the disclaimer: You must have some technical know how in order to successfully do this. I am not responsible for any boot loops that may result in doing this. Please make sure to have a nandroid of your phone before proceeding.*******
Obviously the phone needs to be rooted to complete all of these steps.
Have your desired font in regular, bold, italic, bolditalic.
You will need a font editor. ( I used FontCreator – Free 30day trial)
The process on how to edit the classifications on whichever font editor you are using.
You need a file explorer app ( I used root explorer)
**backup of your phone (nandroid)**
So take your desired font files on your PC and rename them accordingly
Regular font ==> Roboto-regular.ttf
Bold font ==> Roboto-Bold.ttf
Italic font ==> Roboto-Italic.ttf
Bolditalic font ==> Roboto-BoldItalic.ttf
Now you will need the font editor program for the following steps.
Open each of your newly renamed files and change the classifications to represent what the actual font will be used for.
If you use FontCreator you will need to go to Format menu ==> settings menu to check the general tab for the classification there as well as metrics tab to make sure they represent bod, regular, italic ect
Once you have updated all the classifications, save them and copy them to your SD card.
Now we need to update the permissions of the files. Now you can copy the permissions exactly from the /system/fonts folder if you want. I just used rw-rw-rw for the four font files. You will need to copy the font files to the phone inorder to change the permissions. I created a folder in the /data/app folder with the name of my font “patronne” and placed the four files in there. I then changed all of the permissions on the files.
Now make sure you copy the original files listed below in the /system/fonts folder to another folder in case you want to return the font to the default font.
Roboto-regular.ttf
Roboto-Bold.ttf
Roboto-Italic.ttf
Roboto-BoldItalic.ttf
Once you have backed up the four files, now copy (make sure to enable R/W in root explorer) your new fonts into the /system/fonts folder and you will be prompted to overwrite the existing files. Press ok.
Now at this point the phone may lock up and/or you get cryptic characters on your screen since you just replaced files that may have been in use, so you need to reboot it. I just pulled the battery out and put it back in.
Then boot up your phone and should have all themed fonts that correctly display for regular,bold,italic ect.
If your phone bootloops then just restore from the Nandroid and check all the files for proper settings and try again..
Hope this helps anyone that has run ir is running into this. I just like having all my text be the same font and not 90% of it.
Thats waaay too complicated. Do you think there can be an easy way of doing this for flipfont apk's?
I am not experienced with what all the flip font apks do or how to update them to be 100% successful in converting all fonts. However in my experience I have had to take the font file out of the apk do these edits I described and then copy them over as the apks still didn't update 100% of what I seen on the phone. If you install an apk and it changes everything to your liking then your good. If it doesnt then the only way I have been successful with fonts is to do what I outlined. Its somewhat complicated but works and doesnt cause boot loops if you do it properly ... maybe someone with better understanding of how to update the apks could chime in how to go that route. I am sure there will be edits and possibly complicated per say to update them so you have an easy install.
Sent from my SPH-D710 using xda premium
I've always been able to change the scenario values in the Note 2's MDnie to sharpen up the screen (from "0" to "1") but I haven't been able to do that on the 3. I see that the folder is setup differently in the 3. When I attempt to change the values in some of the files, when I save and exit, it tells me that it creates a backup of the original but the change is never made. It feels as if there some sort of write protection on some of the files.
I use root explorer as I always have so I know to change to RW mode before navigating to the folder. Not sure if anyone else here knows about changing MDnie from root access but the path is:
sys/class/mdnie/mdnie/ in there, I'm able to change a few files but one that I think I need to change, simply won't;
mdnieset_user_select_file_cmd
Not sure if there's another file or location I should be using.
Sent from my SM-N900T using xda app-developers app
Nihonno said:
I've always been able to change the scenario values in the Note 2's MDnie to sharpen up the screen (from "0" to "1") but I haven't been able to do that on the 3. I see that the folder is setup differently in the 3. When I attempt to change the values in some of the files, when I save and exit, it tells me that it creates a backup of the original but the change is never made. It feels as if there some sort of write protection on some of the files.
I use root explorer as I always have so I know to change to RW mode before navigating to the folder. Not sure if anyone else here knows about changing MDnie from root access but the path is:
sys/class/mdnie/mdnie/ in there, I'm able to change a few files but one that I think I need to change, simply won't;
mdnieset_user_select_file_cmd
Not sure if there's another file or location I should be using.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
sys/class/mdnie/mdnie/scenario first byte change to 3. But changes go to default 0 by other apps.
alexhc18 said:
sys/class/mdnie/mdnie/scenario first byte change to 3. But changes go to default 0 by other apps.
Click to expand...
Click to collapse
I've tried that, unfortunately. The changes never stick. Root explorer would say that it's saving a backup but nothing ever happens. I am also mounted as RW. Tried it in different ROMS and phones (different note 3s)
When I try to edit the build.prop as soon as I start to add the following entries it starts underlining red. When I try and save it says that there was an error. I have root explorer turned on. Any ideas?
This is from the SOKP thread:
to fix the red border bug add the following lines to your build.prop using your favorite explorer:
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
I saw this in the SOKP thread. Not sure why that is necessary as that option is actually a part of dev tools at least in every rom I've seen to date. I'd first try Settings>Developer Options though i believe the issue is that Strict Mode is persisted and adding or editing buil.prop will be needed. Worth a try. Let us know if you can here and/or on the SOKP thread if you can post to dev forums if the dev options is all it takes.
Also many file explorers will allow you to view certain root folders, typically the root ("/") of the phone only but will not allow any write operations until several conditions are met. Of course you have to have working full root and SuperSU/Superuser installed and supersu binary updated for one. Second many explorers leave device root, /system (where your build.prop file should be) and pretty much everything other than internal and external storage, mounted -ro by default. Take for example CM's Filemanger. CM builds (official at least) come with supersu and Superuser injected in the build. This of course makes the 1st step i listed unnecess. However upon first opening CM File Mgr, access to the root of the device is restricted and no operations can be performed by the user directly at the root level. This is of course easily solved by going into the app settings and changing the mode that it operates. By default to prevent dangerous & unintended operations to sensitive files and partitions, CM File Mgr defaults to "Safe Mode". As far as File Mgr goes you have two other choices "Prompt" and "Root" modes that will allow you write access to things like build.prop at which time you will get a superuser popup to grant or deny root privledges to the app. And Just because you have recieved the superuser popup does not mean your file explorer/root browser is operating in Root mode. I recommend using root browser by jrummy,or ES File Explorer. ES is an example of a browser that requires you to elevate its privileges, root browser does not and they are both widely used.
Now I know that seems like a long answer but the idea is the same whether it CM's File Mgr or the two I just mentioned, just a little insight to common issues. This is not a fix all. Partial or buggy SELinux/SEAndroid builds will require more attention as /system stays mounted -ro except when commanded by root level apps invoked through busybox and The SELinux Contexts and other properties determine who gets access to what. Dont worry you don't have to know what any of that is just hope this helps.
First off this a modified version of the LG G3 F400K10G build prop. Main attempt of this is to enable BOTH LED with individual Text Message tone in the stock Contacts app. IF done correctly it will allow use of message tone notifications for each of your contacts. Be warned when the mesagging app is open I think the default notification noise is used, not sure why this is but this is a temp fix really to enable this feature on the LG G3 F400K10G. I imagine it would work for most fo the F400 models but I cannot confirm as my wife only has the F400K model. This will also enable the 4G LTE icons commonly found on US phones in the status bar it also does away with the dual clock on lock screen and Roaming setting in the settings. The features are there but region specific, so on to the directions.....
1------>Device must be compatible with build prop LG G3 F400K10G recommended
2------>Device must be ROOTED and have R/W access to /system folder because this is where the build prop is located
3------>You must be able to set permissions properly or you device will not boot, usually rw-r--r-- or owner-> Read, Write Group-> Read only Others->Read Only
4------>Know what you are doing and how to restore phone from TOT or mod thru ADB just incase. I am not responsible for YOUR phone(mistakes)!!!
5------>Back up exist build prop as you see fit for example name it build.prop.bak or even copy it to SD card or PC.
6------>Download and extract the build.prop from the zip folder. ZIP Folder is NOT Flashable!
7------>Use your preferred Root Explorer to copy and paste and set permissions and back up as needed.
8------>Once you are sure everything is completed from Step 7 the reboot your phone and verify changes
9------>Feel free to mod the build prop to meet your needs for those advanced users.
Enjoy!