I followed the instructions on the Evervolv Touchpad Development forum to add additional users but ran into a bit of bother...
After entering:
su
setprop fw.max_users=5
at the terminal the 'Users' menu did appear and I then spent about an hour configuring my wife's account. Everything looked good, rebooted only to find that the second user was no longer on the home screen. Bummer.
I checked the build.prop and there was no sign of the fw.max_users=5.
I went ahead and edited the build.prop using an app (build.prop?) and added the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(You can manually edit the build.prop to add a line:
fw.max_users=5
...I didn't feel that comfortable with that)
I rebooted many times since and everything is nice and dandy. And the best bit?, when I rebooted the user I spent an hour adding was still there... class. Using for a while now and seems robust.
Some people are saying this is a bug with the Rom, to me (complete noob) it looks like an issue with rights to edit the build.prop through the terminal.
My Rom: http://evervolv.com/devices/tenderloin (May 11th nightly)
Sent from my Touchpad using XDA Premium HD app
Related
I kept searching for a BIOS boot screen for the Samsung Captivate, but could not find one. So I created my own. I took the energy star logo, format, and android end animation from frysee's Nexus post. So thanks frysee!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is tweaked with most of the information from the Captivate (example: Hummingbird Processor and 512MB RAM).
I know there are multiple ways of installing this, but the way I do it is to save it to a location on your SD card and then use Root Explorer to copy it into your system-media folder. (back up your original bootanimation.zip first!)
I am not responsible for any damage you may do to your phone by using this, but it does work on my phone
Ahem: http://forum.xda-developers.com/showthread.php?t=855068
Search. Remember seeing the one I linked to last week. It is nice to actually get a preview with this one though.
ACK! I swear I searched this forum for that! I think I have issues searching for some reason. Oh well. Man, that would have saved me a lot of time if I was able to find that, hehe.
Haha. Nice work anyway
Thanks. I think I will have to try to work on a modified boot image now.
I run the Bamfs 1.5 debloated rom and hate accessing my widget list menu because there are to many choices. The debloated rom doesn't collapse the widgets for the same app. This app linked below takes care of the problem.
http://forum.xda-developers.com/showthread.php?t=780828
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read instruction. This should help. And remember it doesn't work on the stock sense launcher but works for launcher pro and others like it.
reinbeau said:
You renamed the file (appwidgetpicker.apk), placed it into /system/app, and checked the permissions (sorry for the alignment, it just won't line up for me):
xxxxxReadxxxWritexxxx Execute
User xxX xxxxxX xxxxxxxxo Group X xxxxxxoxxxxxxxx o
Others Xxxxxxx o xxxxxxxxo
(X = checkmark, o = blank)
And then rebooted? That worked perfectly for me using Root Explorer set to r/w.
Click to expand...
Click to collapse
Fyi, if you do this, be sure to NOT "install" the apk after you copy it. If you do, there may be problems. It also takes a reboot to begin working.
Sent from my ADR6400L using XDA App
Thanks for the link.
Sent from Zeus' Thunderbolt
I wasn't sure where to put this so I guess general is good.
I made a quick de-Sense script in Windows Bat format that should work on any Sense ROM.
You can remove parts of Sense or All-Sense. Removing all automatically installs Apex launcher so you aren't left with no launcher.
Let me know of any issues as I made this pretty quickly.
You may need to allow SU for cmd prompt prior to running depending on what ROM you are using.
Option 17 (ALL) removes All-Above-Options.
Hit thanks and give feedback please.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wow, this looks awesome!
kickass !!
Ew, Apex Launcher...
I'll be giving this a run later today.
Sent from my HTC Velocity 4G X710s using XDA Premium App
I might recommend adding an adb reboot recovery before remount. Or telling them to reboot to recovery before running the script. Might make things alot easier for some folks unable to figure out why it isn't working. This was necessary for me stock rooted ics. I was unable to get enabling su before hand to take. Worked great from there though!
So this requires the phone to be rooted, no?
I don't know that I can be terribly specific as whatever I did, I did a long while ago when the touch pad was still new to android. I was running a rom that had an available update, so I selected the automatic update option. I didn't realize my recovery wouldn't handle whatever script it was running after it booted into recovery. Something got interrupted when it shouldn't have. Now anytime the device starts it automatically boots to recovery. I bypass this by holding the volume keys as it boots.
I have reset the device using webos doctor, but the problem persists.
Thanks in advance!
Edit: attached a photo of startup
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my cm_tenderloin using xda premium
Sounds like it's set to boot into recovery all the time.
Get it loaded up in recovery, then using ADB, mount /boot and look in there. If there's a file called moboot.next, delete it. Also, type the following (without the quotes):
"echo CyanogenMod < moboot.default"
That should set your default to CyanogenMod (assuming you have that on your tablet)
My phone security flagged this..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's not by your average and honest XDA Dev. I trust my security. It flagged a wallpaper app couple of months ago. 4 days later Google pulled it for hidden bit coin mining code. This is only other thing it's flagged.....
From my paid for buggy ass XDA app...
Well, this doesn't really belong into the "Xposed General" section as it's about a specific module/app.
I don't trust those virus scanners as much as you do. Anyway, here's a scan: https://www.virustotal.com/de/file/...76ae73ab4c2fc3b1e0c98049/analysis/1402423824/
It needs quite some permissions, including "Send SMS", but then again it has also lots of features which might need them (such as auto-replies). Such scanners can only use heuristics, which are not always correct by definition. To know it for sure, one would have to analyse the complete code line by line. As this is a commerical app, you won't get the code, so you can either trust or uninstall.
Obviously, everything you install is on your own risk and I surely won't give any guaranty that anything but my own files are malware-free.
trust your apps 100%and I'm grateful for your work.
N5