Related
Use Nook with MIUI. Today apply new theme, and after reboot can't unlock, because control elements of new lock screen (button or else) out of screen.
Can i unlock nook? Via adb may be?
Butuzz said:
Use Nook with MIUI. Today apply new theme, and after reboot can't unlock, because control elements of new lock screen (button or else) out of screen.
Can i unlock nook? Via adb may be?
Click to expand...
Click to collapse
I'be had this problem on multiple occasions and the last time found the best solution. If you use a program like Android Commander on your computer and look through /data, there is a file somewhere called "lockscreen" with no file extension. I can't for the life of me remember the exact location. Anyways, if you rename that file, it'll default back to the system lockscreen. There might be a couple different "lockscreen" files. If one doesn't work, fix it and move on to the next. If I have the chance today ill find the exact location.
Sent from my HERO200 using XDA App
ajrty33 said:
I'be had this problem on multiple occasions and the last time found the best solution. If you use a program like Android Commander on your computer and look through /data, there is a file somewhere called "lockscreen" with no file extension. I can't for the life of me remember the exact location. Anyways, if you rename that file, it'll default back to the system lockscreen. There might be a couple different "lockscreen" files. If one doesn't work, fix it and move on to the next. If I have the chance today ill find the exact location.
Click to expand...
Click to collapse
Android Commander use adb for communicate with, but i don't see nook in list of adb devices. May be USB debugging switched off on my nook. ((
Hello, I have just wasted about a day of my time on this issue.
Problem:
When I root my S4, running Kitkat, or load custom Kitkat ROM - wanamlite in my case, then the auto rotate screen feature stops working.
The problem is not in the HW - the camera app, which rotates labels on the screen based on orientation - kept working through all the trouble.
Details:
- I decided to root my S4, mainly to be able to install xposed/xprivacy and Titanium Backup
- first, I rooted the stock ROM, using the chainfire method. Worked fine
- I did not install custom recovery at this point
- removed few modules in TB
- noticed that the screen auto rotate stopped working
- restored the removed modules in TB, auto rotate still not working
- installed TWRP and Wanamlite. Screen rotation first worked, but after some time ( and my guess is after few reboots ), screen auto rotate failed again.
I was unable to fix this, so I had to go back to stock ROM ( Swiss FNB9 ), to get the phone working again.
Searching on Google, it seems that few of the Samsung devices have this problem of screen auto-rotation not working after rooting....
Before I try rooting again, is this a known problem ? Any fix with a high degree of reliability ?
Thanks for any info, Paul.
paulcc said:
Hello, I have just wasted about a day of my time on this issue.
Problem:
When I root my S4, running Kitkat, or load custom Kitkat ROM - wanamlite in my case, then the auto rotate screen feature stops working.
The problem is not in the HW - the camera app, which rotates labels on the screen based on orientation - kept working through all the trouble.
Details:
- I decided to root my S4, mainly to be able to install xposed/xprivacy and Titanium Backup
- first, I rooted the stock ROM, using the chainfire method. Worked fine
- I did not install custom recovery at this point
- removed few modules in TB
- noticed that the screen auto rotate stopped working
- restored the removed modules in TB, auto rotate still not working
- installed TWRP and Wanamlite. Screen rotation first worked, but after some time ( and my guess is after few reboots ), screen auto rotate failed again.
I was unable to fix this, so I had to go back to stock ROM ( Swiss FNB9 ), to get the phone working again.
Searching on Google, it seems that few of the Samsung devices have this problem of screen auto-rotation not working after rooting....
Before I try rooting again, is this a known problem ? Any fix with a high degree of reliability ?
Thanks for any info, Paul.
Click to expand...
Click to collapse
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Wow, very much appreciated! This worked perfectly for my S4 with KitKat.
Today I noticed my auto screen rotation stopped. I googled around, tried many work-arounds, but none of them helped. A hard reset didn't work, a soft reset didn't work, Bluetooth/GPS/WiFi off didn't help, calibration using an app didn't work, etc.
I rooted my phone (as I had before, but because of the hard reset I had to root it again), installed Root Explorer, and put the libgnustl_shared.so file in the System/lib folder (while mounted R/W). I rebooted and BAM! Auto screen rotation was back again!
jupkeyope said:
Wow, very much appreciated! This worked perfectly for my S4 with KitKat.
Today I noticed my auto screen rotation stopped. I googled around, tried many work-arounds, but none of them helped. A hard reset didn't work, a soft reset didn't work, Bluetooth/GPS/WiFi off didn't help, calibration using an app didn't work, etc.
I rooted my phone (as I had before, but because of the hard reset I had to root it again), installed Root Explorer, and put the libgnustl_shared.so file in the System/lib folder (while mounted R/W). I rebooted and BAM! Auto screen rotation was back again!
Click to expand...
Click to collapse
Glad that fixed your issue mate Have a nice day.
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
That fixed it indeed !! Thanks man ! I had problems pasting the file into that directory but the "root browser" app from the play store could paste it. Then changed permissions, rebooted and ... back is screen rotation !!! Thanks !! :good:
---------- Post added at 04:09 AM ---------- Previous post was at 03:58 AM ----------
BTW, so it seems the problem is that when you uninstall samsung HUB (which I indeed did), it removes that particular file. See: http://forum.xda-developers.com/showpost.php?p=49604191
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
this solves the problem of the motion sensor? My s4 stopped working screen rotation and motion sensor ... stopped after uninstalled some apps by TB
sensor motion
its solve
Hi, Besides hitting the THANKS button, I would like to give following information for other users:
I have PhilzTouch installed and tried to flash the zip file severel times, But everytime after wiping cache part. and dalvik I noticed that nothing changed.
So I did the copy/paste action as described and after rebooting it worked.
Hi All,
I had the same issue when i rooted my device, and lost the rotation and use the method described here to fix the issue.
But after reboot the phone it will keep popping the message " Unfortunately, Samsung Hub has stopped" and it won't go away or let me do anything on the phone, as soon as i hit the OK button it will popup again.
Any possible fix for that, Please !!!
Thank you all.
In English, please...
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Can someone help me with this, please... I have no idea what this means.
1) I downloaded the file
2) The instructions say to move the libgnustl_shared.so file into System>>Lib. When I download the file, libgnustl_shared.so is already in a folder called System>Lib...
3) Someone else said to FLASH via recover or something?? What does that mean? Can someone explain this in straightfoward terms? Thank you.
In that case, you should try to replace the existing file with the new one.
You just need to set up the parameters of the file (permissions into rw r r) as explained before. You can do it with ES Explorer for instance.
No need to do something else, just reboot.
Sent from my GT-I9505 using XDA Free mobile app
HEEELP !!!!!!!!!!!!!!!!!!!!
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Please help if done every thing you said ive flashed it using touched based cwm ive flash my stock files before to unbrick pls help
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
That really works on my S4. But my hand motion sensor(air gesture) still does not work. How 2 fix it?
I followed the instructions to the T and still no luck. What else could it be?
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
dude you're my friggin hero...no joke...
Galaxy S4 Screen Rotation
Repulsa said:
download and flash libgnustl_shared.so via recovery. Or if your phone is rooted , Copy and paste to System>>lib and change permission to rw-r--r-- . Reboot . Have a nice day.
Click to expand...
Click to collapse
Hello,
Still trying to fix my screen rotation. I reinstalled samsung hub but it dod not fix anything.I have gotten the above file into my system here, device storage-download-system-lib-libgnustl_shared.so
It does not open with any apps and under the menu button I show
hidden files
file extension
catagories
or Select directories
I cant find the right place to change permission to rw-r--r--
thanks for your help.
dave
davekane said:
Hello,
Still trying to fix my screen rotation. I reinstalled samsung hub but it dod not fix anything.I have gotten the above file into my system here, device storage-download-system-lib-libgnustl_shared.so
It does not open with any apps and under the menu button I show
hidden files
file extension
catagories
or Select directories
I cant find the right place to change permission to rw-r--r--
thanks for your help.
dave
Click to expand...
Click to collapse
Use a rootexplorer mate. And try again
Sent from my SM-G900F using Tapatalk
changin permission parameters for getting screen rotation
OK, easy, my first question was and has been "how to change the permissions".
And alone, not being an Android Geek, I succeeded !!!
First use Root Explorer, with it copy and paste (or move) the " libgnustl_shared.so" file in the "\system\lib" directory.
Once it's done (always with Root Explorer) apply a finger on this new file, a menu appears and choose "Permissions". Then there, keep only Read on the three lines, and only Write on the first line. Then click on OK.
And reboot your system.
Amazing, it's working, like the first day and before you rooted it...
Thanks again for your solution.
thanks
works great on i9505 kitkat. don't forget to reboot
no permission
im getting this when i try to do it,
"changing permissions was not successful. please note that some file systems do not allow permission changes"
anyone know how to get around this??
cheers
Hi, all
I have a problem with the lockscreen.
It happened when I replacing the files of "bootsamsung.qmg" , "bootsamsungloop.qmg" , "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg" of /system/media to change the bootanimation using the Root Explorer, and then this problem started, I can not lock the screen, but I can turn off the cell phone, it's a thing of function button. When I turn on the cell phone, the bootanimation is in black, that is to say, I don't get the bootanimation.
I tried to go settings>>personalization>>lockscreen to change the settings of active screen and it don't work.
I tried to restore factory settings and wipe data, and it don't work.
I used the downloaded bootanimation with archives that contain "bootsamsung.qmg" and "bootsamsungloop.qmg" and copied to change his names "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg", the download of this bootanimation is in <<http://forum.xda-developers.com/showthread.php?t=2587092>> , the link is "BiosBootAnimation(Made_BY_NimaGL2).zip".
Can someone help me, please?
SAMSUNG GALAXY NOTE 3 SM-N9005
vrootsuser said:
Hi, all
I have a problem with the lockscreen.
It happened when I replacing the files of "bootsamsung.qmg" , "bootsamsungloop.qmg" , "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg" of /system/media to change the bootanimation using the Root Explorer, and then this problem started, I can not lock the screen, but I can turn off the cell phone, it's a thing of function button. When I turn on the cell phone, the bootanimation is in black, that is to say, I don't get the bootanimation.
I tried to go settings>>personalization>>lockscreen to change the settings of active screen and it don't work.
I tried to restore factory settings and wipe data, and it don't work.
I used the downloaded bootanimation with archives that contain "bootsamsung.qmg" and "bootsamsungloop.qmg" and copied to change his names "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg", the download of this bootanimation is in <<http://forum.xda-developers.com/showthread.php?t=2587092>> , the link is "BiosBootAnimation(Made_BY_NimaGL2).zip".
Can someone help me, please?
SAMSUNG GALAXY NOTE 3 SM-N9005
Click to expand...
Click to collapse
Try to set the boot animation all over again and follow every step (don't hurry or panic). Also take a look on the links posted by The dev of the boot animation. If it still didn't work please try to flash the stock boot animation via recovery. At last if everything didn't work put the rom on your sd card backup data and efs (titanium backup 4 example) and do wipe data and cache in recovery. Good luck
vrootsuser said:
Hi, all
I have a problem with the lockscreen.
It happened when I replacing the files of "bootsamsung.qmg" , "bootsamsungloop.qmg" , "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg" of /system/media to change the bootanimation using the Root Explorer, and then this problem started, I can not lock the screen, but I can turn off the cell phone, it's a thing of function button. When I turn on the cell phone, the bootanimation is in black, that is to say, I don't get the bootanimation.
I tried to go settings>>personalization>>lockscreen to change the settings of active screen and it don't work.
I tried to restore factory settings and wipe data, and it don't work.
I used the downloaded bootanimation with archives that contain "bootsamsung.qmg" and "bootsamsungloop.qmg" and copied to change his names "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg", the download of this bootanimation is in <<http://forum.xda-developers.com/showthread.php?t=2587092>> , the link is "BiosBootAnimation(Made_BY_NimaGL2).zip".
Can someone help me, please?
SAMSUNG GALAXY NOTE 3 SM-N9005
Click to expand...
Click to collapse
Did you reset the permission and ownership of each of the files?
4aces said:
Try to set the boot animation all over again and follow every step (don't hurry or panic). Also take a look on the links posted by The dev of the boot animation. If it still didn't work please try to flash the stock boot animation via recovery. At last if everything didn't work put the rom on your sd card backup data and efs (titanium backup 4 example) and do wipe data and cache in recovery. Good luck
Click to expand...
Click to collapse
What if I try to install the files it says on <<http://forum.xda-developers.com/showthread.php?t=2502550>> ? Will be this, the solution?
vrootsuser said:
What if I try to install the files it says on <<http://forum.xda-developers.com/showthread.php?t=2502550>> ? Will be this, the solution?
Click to expand...
Click to collapse
Try it should work
I found where is the problem, is in the permissions of files that have copied, I changed to rw-r--r--, and before when I had the problem was rwxrwx---, was a detail, and wherefore the lockscreen didn't let me that lock the screen.
Thanks, all, now works perfectly.
vrootsuser said:
Hi, all
I have a problem with the lockscreen.
It happened when I replacing the files of "bootsamsung.qmg" , "bootsamsungloop.qmg" , "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg" of /system/media to change the bootanimation using the Root Explorer, and then this problem started, I can not lock the screen, but I can turn off the cell phone, it's a thing of function button. When I turn on the cell phone, the bootanimation is in black, that is to say, I don't get the bootanimation.
I tried to go settings>>personalization>>lockscreen to change the settings of active screen and it don't work.
I tried to restore factory settings and wipe data, and it don't work.
I used the downloaded bootanimation with archives that contain "bootsamsung.qmg" and "bootsamsungloop.qmg" and copied to change his names "bootsamsungmini.qmg" and "bootsamsungminiloop.qmg", the download of this bootanimation is in <<http://forum.xda-developers.com/showthread.php?t=2587092>> , the link is "BiosBootAnimation(Made_BY_NimaGL2).zip".
Can someone help me, please?
SAMSUNG GALAXY NOTE 3 SM-N9005
Click to expand...
Click to collapse
Older thread but wanted to ask what specifically these two files do?
bootsamsungmini.qmg" and "bootsamsungminiloop.qmg
*I know bootsamsung.qmg (plays first at boot after Samsung logo)
*bootsamsungloop.qmg (plays second at boot)
*shutdown.qmg (plays when phone turns off)
But what do the other two do and are they needed??
bootsamsungmini.qmg" and "bootsamsungminiloop.qmg
Thanks,
-Nigel
Ok so I figured out how to change the lock screen wallpapers WITHOUT the use of an app, wallpaper picker or modifying the framework or systemui. It's nothing short of amazing.
PROS:
-NO image quality is lost because of a crappy cropper.
-NO application or modifications to the framework are needed for this to work so you can officially get rid of Amazon Photos
CONS:
-Only one wallpaper at a time
-Requires root. However this is done through /data where it is mounted as R/W. This would't be a problem if you could symlink the /data folder to internal storage or /mnt. I have tried a few ways on the HD 8 with no success.
Instructions:
1. Download your favorite HD wallpaper (as close to 1920x1200 as possible). I have a collection of dozens of stock Android wallpapers from various versions and devices at your disposal.
2. When you have chosen your wallpaper and downloaded it, the file extension should be a .jpg. Please go here and convert it to a .png https://jpg2png.com This should be done for all wallpapers. Changing the file extension is not the same. This web based tool also compresses the file to reduce the loss of image quality.
3. Using a file explorer like Total Commander copy the wallpaper.JPG from your download folder on internal storage to this /data directory:
Code:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
4. Activate your lock screen to see your custom wallpaper. A reboot shouldn't be required.
DragonFire1024 said:
Ok so I figured out how to change the lock screen wallpapers WITHOUT the use of an app, wallpaper picker or modifying the framework or systemui. And it's glorious.
This is done on my rooted HD 10, but there is a huge possibility this does NOT require a rooted tablet. Why? Because it's done through /data where it's writable without root this is so easy I kick myself for not discovering this earlier. So if you have an HD 8, any model or year (NOT on Nougat) I need you test this.
1. Download your favorite HD wallpaper (as close to 1920x1200 as possible). I have a collection of dozens of stock Android wallpapers from various versions and devices at your disposal.
2. Using a file explorer like Total Commander copy the wallpaper.JPG from your download folder on internal storage to this /data directory:
Code:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
3. Activate your lock screen to see your custom wallpaper. A reboot shouldn't be required.
I've only tried this with one wallpaper so you might be able to have several in that directory so it's different every time the lock screen is activated. I look forward to your reports!
Click to expand...
Click to collapse
Trying right now... brb...!
DragonFire1024 said:
Ok so I figured out how to change the lock screen wallpapers WITHOUT the use of an app, wallpaper picker or modifying the framework or systemui. And it's glorious.
This is done on my rooted HD 10, but there is a huge possibility this does NOT require a rooted tablet. Why? Because it's done through /data where it's writable without root this is so easy I kick myself for not discovering this earlier. So if you have an HD 8, any model or year (NOT on Nougat) I need you test this.
1. Download your favorite HD wallpaper (as close to 1920x1200 as possible). I have a collection of dozens of stock Android wallpapers from various versions and devices at your disposal.
2. Using a file explorer like Total Commander copy the wallpaper.JPG from your download folder on internal storage to this /data directory:
Code:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
3. Activate your lock screen to see your custom wallpaper. A reboot shouldn't be required.
I've only tried this with one wallpaper so you might be able to have several in that directory so it's different every time the lock screen is activated. I look forward to your reports!
Click to expand...
Click to collapse
Sorry, I was pulled into something for a bit. And then I became distracted making this lovely new lock screen wallpaper, lol...
Unfortunately, it does not seem we are able to access that folder without root. I tried four different file managers. When I finally typed the direct address verbatim as you provided, the device didn't say the folder did not exist, but said I did not have access. I did however notice a different com.android.systemui folder, which was located at /data/data/ , but also did not have access to this folder.
Screenshots of my attempts to locate/access the folder you described are here if you want to see for yourself.
I just bought a new soldering iron today. I'm about to hardmod root this sucker ✔ ??*???
richaardvark said:
Sorry, I was pulled into something for a bit. And then I became distracted making this lovely new lock screen wallpaper, lol...
Unfortunately, it does not seem we are able to access that folder without root. I tried four different file managers. When I finally typed the direct address verbatim as you provided, the device didn't say the folder did not exist, but said I did not have access. I did however notice a different com.android.systemui folder, which was located at /data/data/ , but also did not have access to this folder.
Screenshots of my attempts to locate/access the folder you described are here if you want to see for yourself.
I just bought a new soldering iron today. I'm about to hardmod root this sucker ?*
Click to expand...
Click to collapse
My beautiful wallpaper will have to wait for now... :crying:
richaardvark said:
Sorry, I was pulled into something for a bit. And then I became distracted making this lovely new lock screen wallpaper, lol...
Unfortunately, it does not seem we are able to access that folder without root. I tried four different file managers. When I finally typed the direct address verbatim as you provided, the device didn't say the folder did not exist, but said I did not have access. I did however notice a different com.android.systemui folder, which was located at /data/data/ , but also did not have access to this folder.
Screenshots of my attempts to locate/access the folder you described are here if you want to see for yourself.
I just bought a new soldering iron today. I'm about to hardmod root this sucker ?*
Click to expand...
Click to collapse
Update: Ultimately however, I was able to set the lock screen wallpaper, using the "Prime Photos" app. This however changed my launcher/home screen wallpaper as well. I then downloaded the standard Google "Wallpapers" app from the Play store and was able to set my wallpaper back to what it had been, and was also able to keep weird cat sweater lady as the lock screen image. So, ultimately same end result, just a tiny bit more effort to make it happen, but not really a big deal.
Updated screenshots in my shared folder.
richaardvark said:
Update: Ultimately however, I was able to set the lock screen wallpaper, using the "Prime Photos" app. This however changed my launcher/home screen wallpaper as well. I then downloaded the standard Google "Wallpapers" app from the Play store and was able to set my wallpaper back to what it had been, and was also able to keep weird cat sweater lady as the lock screen image. So, ultimately same end result, just a tiny bit more effort to make it happen, but not really a big deal.
Updated screenshots in my shared folder.
Click to expand...
Click to collapse
What a shame. Well at least this is a lot easier now rather than taking the time and effort to mod the systemui.
Ok so this is disappointing. I'll have to post a rewritten guide. This one is tough to explain. But I am pretty sure I did this through the Amazon Device Settings application.
I plugged my HD 8 into my PC and opened ADB in an attempt to access the directory. I was able to cd into /data/securedStorageLocation just fine. However I tried to make the directory com.android.systemui and got an error of 'permission denied', but not because of no root, 'the directory already exists'. So it's there, just not totally accessable.
So this has to be exclusive to Amazon, or a result of or a combination of things. I have literally found only two forum posts that mention the directory perfectly. However the website is in Japanese. Thankfully Google translate helped. The good news is, it looks like you can gain entry by symlinking. When I saw this entry, and sdcard was mentioned, I did realize one thing I did yesterday that I've never done before. Optimized the databases. Specifically I used SDmaid (bought full version but I don't think that mattered). So it occurred to me, it likely 'fixed' whatever Amazon took out of the databases. This is a wild guess though.
Reporting on the rom copied Stock ROM reporting that it was possible to download amazon instant video,
and copied /data/secureStorageLocation/com.amazon.avod to each directory / sdcard
· Then the following So evacuate the original and
create a symbolic link (su with adb shell and executed). Once done, restart
cd / data / secureStorageLocation /
mv com.amazon.avod com.amazon.avod.org
ln -s /sdcard/com.amazon.avod com.amazon.avod
Click to expand...
Click to collapse
I went ahead and did a little bit of a rewrite to change the title. Just set up flash to stock and just saw the folder had already been there. I honestly cannot believe it's been there this entire time and I honestly can't believe I've missed it this entire time. Unfortunately this requires root access unless somebody can figure out how to symlink the folder to internal or external storage. though it is located in part of the data that is read and write, the folder is not.
Sent from my Galaxy S4 using XDA Labs
Update:
I just want to add, wallpapers can be in .jpg format, but for best compression, least amount of quality loss and if you have the same wallpaper for both lock screen and desktop, convert your .jpg to a .png for both (this should be done regardless of the wallpapers are the same or not). This handy, web based tool does exactly that, and compresses the file at the same time. This has resulted in my wallpapers being 100% in sync. https://jpg2png.com
I have copied my wall paper in png format to the location (with root access). However, it's not used as the wall paper or lock screen background, even after reboot. What am I missing?
In the meantime, I can use an image browser (Quick Pic) to set it as wall paper. However, it does not last. It may revert without reboot.
redhonker said:
I have copied my wall paper in png format to the location (with root access). However, it's not used as the wall paper or lock screen background, even after reboot. What am I missing?
In the meantime, I can use an image browser (Quick Pic) to set it as wall paper. However, it does not last. It may revert without reboot.
Click to expand...
Click to collapse
Make sure you are in the right directory/folder and all the way to the end of com.android.systemui:
/data/securedStorageLocation/com.android.systemui/ls_wallpaper/0. Your wallpaper goes in the '0' folder. So far as I know no special permissions needed. But it won't hurt to set permissions to:
rw-r--r-- (0644). Make sure you have a lock screen set
# ls /data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
-rw-r--r-- root root 11833019 2018-12-08 16:19 Wallpaper-Florida-Keys.png
So it all looks right. Just not taking effect. I don't know if it depends on some package that might get disabled (I've disabled a bunch).
redhonker said:
# ls /data/securedStorageLocation/com.android.systemui/ls_wallpaper/0
-rw-r--r-- root root 11833019 2018-12-08 16:19 Wallpaper-Florida-Keys.png
So it all looks right. Just not taking effect. I don't know if it depends on some package that might get disabled (I've disabled a bunch).
Click to expand...
Click to collapse
It very well may have been patched on 5.3 or 5.6.3 (whatever it really is)
The good news is that I can just set it using a image viewer. However, they do revert back though it's not clear what triggers revert.
redhonker said:
The good news is that I can just set it using a image viewer. However, they do revert back though it's not clear what triggers revert.
Click to expand...
Click to collapse
Try disabling com.amazon.kindle.kso and deleting it.
I am on the latest 5.6.3.0, and copying to the '0' folder works for me. I had ads removed when I first got the device, so I don't have com.amazon.kindle.kso. So as Dragon said, maybe disabling and deleting will help.
Note that if the image is subsequently deleted from the '0' folder, the "7 cycling wallpapers" return. I don't know if they would return if some other method of setting the lock screen wallpaper is used, like the Prime Photos app.
---------- Post added at 09:55 PM ---------- Previous post was at 09:17 PM ----------
Dragon, with regard to the "7 cycling wallpapers" in your other thread, I was able to use your post 2 to get my own 7 wallpapers to cycle on the lock screen. So even though I wanted your info on how to recover if I screwed up SystemUI.apk, I didn't need it! If you ever get around to it, I'd still like to know how to recover without having to reinstall stock, reroot, etc.
This post really should be put over in that thread, but I didn't know if you were getting notified there, so I continued to write here (and in another thread that I knew you would see). Thanks for your great work!
sga999 said:
I am on the latest 5.6.3.0, and copying to the '0' folder works for me. I had ads removed when I first got the device, so I don't have com.amazon.kindle.kso. So as Dragon said, maybe disabling and deleting will help.
Note that if the image is subsequently deleted from the '0' folder, the "7 cycling wallpapers" return. I don't know if they would return if some other method of setting the lock screen wallpaper is used, like the Prime Photos app.
---------- Post added at 09:55 PM ---------- Previous post was at 09:17 PM ----------
Dragon, with regard to the "7 cycling wallpapers" in your other thread, I was able to use your post 2 to get my own 7 wallpapers to cycle on the lock screen. So even though I wanted your info on how to recover if I screwed up SystemUI.apk, I didn't need it! If you ever get around to it, I'd still like to know how to recover without having to reinstall stock, reroot, etc.
This post really should be put over in that thread, but I didn't know if you were getting notified there, so I continued to write here (and in another thread that I knew you would see). Thanks for your great work!
Click to expand...
Click to collapse
Sometimes it's easier to make a new thread and index them into one as you go along...I sorta have one started. Anyways, if the SystemUI fails when you install it, the tablet will still boot...just without any user interface. So you can just push your back up back to the tablet. It's tricky if you come to it because you have to keep your tablet attached to PC while running a few shell commands.
I have copied my wallpaper in png format to the location (with root-access) and used a website like https://convertx2y.com/png-to-jpg/ to convert between the image formats. Is it a good one?
Background: Really not loving the default New Contact icons and the random colors. Should be easy enough to change. What I tried (and failed miserably...)
MODest ROM 11 (Twiz/stock 6.01-based)
Flashpoint 5 Kernel
Copied SecContacts_M_OSup_Note_Legacy_USA.apk from
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
to my Win7 PC.
Used 7-Zip to unpack the file to a temporary folder.
Found the .qmg files I didn't like.
Found a .qmg that would be a passable replacement for the ones I didn't dig.
Made 11 copies of that image in a working folder.
Renamed each copy to the exact name of each of the 11 files I wanted to replace.
Dragged those 11 files back into the open .apk in 7-Zip
On the Phone, in Root Explorer:
Made a copy of SecContacts_M_OSup_Note_Legacy_USA.apk in the same folder:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
deleted the original
Copied my mod'd apk back into this folder and set the perms.
Rebooted.
No Phone or Contacts on home screen or in Apps
Tried to 'install' the apk from Root Explorer.
Wouldn't install
Tried to delete cache & Dalvik from TWRP.
No Joy.
Tried to do a partial Nandroid restore of Contacts and sec.phone from Titanium (nothing there called /systempriv-app/SecContacts_M_OSup_Note_Legacy_USA)
No Joy.
Nandroid restore from TWRP.
Back to normal.
Okay, what did I do wrong, and how can I change the icons?
Should I have used APKTook instead of 7-Zip, created a new signature, etc?
Should my mod'd apk somehow be flashed from recovery rather than copied to a system folder?
Is this some perverted Samsung-ism that would have worked fine on any other phone on the planet?
Thanks for reading.
ForestCat said:
Background: Really not loving the default New Contact icons and the random colors. Should be easy enough to change. What I tried (and failed miserably...)
MODest ROM 11 (Twiz/stock 6.01-based)
Flashpoint 5 Kernel
Copied SecContacts_M_OSup_Note_Legacy_USA.apk from
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
to my Win7 PC.
Used 7-Zip to unpack the file to a temporary folder.
Found the .qmg files I didn't like.
Found a .qmg that would be a passable replacement for the ones I didn't dig.
Made 11 copies of that image in a working folder.
Renamed each copy to the exact name of each of the 11 files I wanted to replace.
Dragged those 11 files back into the open .apk in 7-Zip
On the Phone, in Root Explorer:
Made a copy of SecContacts_M_OSup_Note_Legacy_USA.apk in the same folder:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
deleted the original
Copied my mod'd apk back into this folder and set the perms.
Rebooted.
No Phone or Contacts on home screen or in Apps
Tried to 'install' the apk from Root Explorer.
Wouldn't install
Tried to delete cache & Dalvik from TWRP.
No Joy.
Tried to do a partial Nandroid restore of Contacts and sec.phone from Titanium (nothing there called /systempriv-app/SecContacts_M_OSup_Note_Legacy_USA)
No Joy.
Nandroid restore from TWRP.
Back to normal.
Okay, what did I do wrong, and how can I change the icons?
Should I have used APKTook instead of 7-Zip, created a new signature, etc?
Should my mod'd apk somehow be flashed from recovery rather than copied to a system folder?
Is this some perverted Samsung-ism that would have worked fine on any other phone on the planet?
Thanks for reading.
Click to expand...
Click to collapse
That apk took me a long time to figure out too. It's one of the apps you I had to modify for multi dpi. The only way I know of is to change the compression when you're putting the app back together and even then it took a couple tries. There's probably a better way but the compression change seems to work well enough.
I don't know if 7-zip has this option, but with winrar you can change the compression to "store". You should know right away whether or not it worked. You'll see the little phone icon in the bottom left of the lock screen. You may still have to do a factory reset to see your changes (probably not though) but the app should work without it.
By the way, you can swap those image files for .png files if you'd like. Just delete the corresponding .qmg or .pio file.
I saw your post in the rom thread about theming TouchWiz. You should check out @supergrobi94's theming threads. He's put together an impressive collection of options for 6.0.1 and 5.1.1 and there's also a [how to] section that uses the vrtheme zip that will modify the res folder of a specific app without having to break it down. I'm not sure how active he is these days but he's always been very helpful with requests and questions in the past if you need it.
Supergrobi94's theming threads:
This one has all the themes
This is the [how to] thread
kevintm78 said:
That apk took me a long time to figure out too. It's one of the apps you I had to modify for multi dpi. The only way I know of is to change the compression when you're putting the app back together and even then it took a couple tries. There's probably a better way but the compression change seems to work well enough.
Click to expand...
Click to collapse
Ah, that makes perfect sense. But I'd never have figured it out myself, lol.
I'll dig into those theming threads, thanks.
kevintm78 said:
☆☆Edge Panel for ModestRom v11☆☆
DOWNLOAD-This will change your Contacts app to the S6 version and the IncallUI app to the Note 7 version because the people stripe will not work with the N4 contacts.
Click to expand...
Click to collapse
OK, this is from the MODest ROM thread, but I think it's germain here.
SO.....
If I want to 'try out' that Edge Panel, is there a way to revert back to the stock apps in question other than restoring a nandroid backup or re-flashing the ROM?
I ask because I'm thinking that, at least in the case of the Note 4 and its well known memory problems, 'bulk' memory writes like ROMs, nandroid retores, etc., stress the device, so I'm trying not to do it more than I have to.
During my last episode(see above) putting the stock apk back in its original folder didn't work.
Is there a standard procedure for either android generically, or touchwiz specifically, for safely reverting back to the stock system apps after experimenting w/ custom stuff?
EDIT: Just tried something. In Root Explorer, went into:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
and simply renamed the .apk to .foo
Rebooted.
No Contacts, as expected, but no Phone either??? Not sure why.
Anyway, back into Root Explorer.
Rename .foo back to .apk
Reboot.
Still no Contacts or Phone, so something bigger at work here.
Before I have to restore Nandroid anyway (unless there's a better way???),
I flashed your EdgePanel.zip in TWRP to see if it would restore the Phone/Contacts apps.
Wiped the cache. Reboot.
Edge Panel is now there, but still no Phone or Contacts. WTF???
Last resort-TWRP- Factory Reset.
Now the Contacts/Phone are back (and all my other stuff is gone, lol)
So is whacking the Data a necessity here?
If so, it makes trying out things related to the phone/contacts a LOT more tedious...
Any workaround???
Thanks again.
ForestCat said:
OK, this is from the MODest ROM thread, but I think it's germain here.
SO.....
If I want to 'try out' that Edge Panel, is there a way to revert back to the stock apps in question other than restoring a nandroid backup or re-flashing the ROM?
I ask because I'm thinking that, at least in the case of the Note 4 and its well known memory problems, 'bulk' memory writes like ROMs, nandroid retores, etc., stress the device, so I'm trying not to do it more than I have to.
Click to expand...
Click to collapse
No, it doesn't look like I ever made an easy way to go back. I had thought I did but I'm either overlooking it or it's not there. Feel free to rifle through my androidfilehost folders if you want to double check. All of my stuff is very organized so it could be buried in there somewhere.
If you still need a recovery zip let me know and I'll get one together. I'm actually going to make one anyway but if you need it right away I can get on it. I didn't realize that there wasn't a way back to stock.
ForestCat said:
During my last episode(see above) putting the stock apk back in its original folder didn't work.
Is there a standard procedure for either android generically, or touchwiz specifically, for safely reverting back to the stock system apps after experimenting w/ custom stuff?
EDIT: Just tried something. In Root Explorer, went into:
/system/priv-app/SecContacts_M_OSup_Note_Legacy_USA/
and simply renamed the .apk to .foo
Rebooted.
No Contacts, as expected, but no Phone either??? Not sure why.
Anyway, back into Root Explorer.
Rename .foo back to .apk
Reboot.
Still no Contacts or Phone, so something bigger at work here.
Before I have to restore Nandroid anyway (unless there's a better way???),
I flashed your EdgePanel.zip in TWRP to see if it would restore the Phone/Contacts apps.
Wiped the cache. Reboot.
Edge Panel is now there, but still no Phone or Contacts. WTF???
Last resort-TWRP- Factory Reset.
Now the Contacts/Phone are back (and all my other stuff is gone, lol)
So is whacking the Data a necessity here?
If so, it makes trying out things related to the phone/contacts a LOT more tedious...
Any workaround???
Thanks again.
Click to expand...
Click to collapse
That is strange that they are not coming back. You may just want to double check your permissions and that there isn't two of the same apps in your folder. At the time of making that Edge zip I was still using other programs to make zips for me and the major downside to that is having to name the new apps the exact same as the old so it would get overwritten so if it doesn't match you'll end up with two active apps in one folder.
Now I think the best way to do that is to use a binary script (osm0sis has great tutorials for this) to change the app getting replaced to a .bak file and then just copy the new app to the system, set perms, and reboot (dalvik cache/ cache needs to be wiped if it's a framework .jar file). But to each their own. If you can get the job done a better way then I would use what you're comfortable with.
My system to test apps isn't much difference than yours. I think the only thing I do differently is change the app to be replaced to .bak instead of .foo although I can't imagine there's much difference. There's been a few apps like the Contacts app that gave me a bunch of trouble when modifying them but I can't remember ever having trouble bringing back the stock app. I wish I had more insight on that situation for you. If push comes to shove I would reflash the rom zip over factory reset only because the factory reset won't correct the system partition problem, if that's what's going on in this case.
kevintm78 said:
If you still need a recovery zip let me know and I'll get one together..
Click to expand...
Click to collapse
First, Merry Christmas!
Thanks very much. No rush on that, I'm OK on the Edge version for the minute.
What would be extremely useful if you have some time/curiousity would be to replicate my steps, ie renaming the untouched apk in a fresh MODest flash (i.e. break the contacts/phone function), and then see if you can get the whole thing working again without a factory reset, or if not, why. I see on xda, you & I are not the first ones to be tripping over this contacts.apk issue.
The other thing that would be telling is after successfully installing the Edge.zip, whether you can modify something (like a picture) within the contacts apk within the zip, reflash the zip and have contacts/phone still working with the change active.
I think there just HAS to be abetter way than Factory Resets.
Thanks so much again for the insights. I really want to become at least minimally competent at hacking my own ROMs together so I don't have to feel like such a noob/mooch on here, but I really do appreciate the help.
What are your weapons/platform of choice, or, if there are better tools for noobs learning the ropes, I'm all ears.
EDIT: Just found this. The last post is interesting...
https://forum.xda-developers.com/galaxy-s5/devs-only/recompile-seccontacts-apk-t3377142/page2
ForestCat said:
First, Merry Christmas!
Thanks very much. No rush on that, I'm OK on the Edge version for the minute.
What would be extremely useful if you have some time/curiousity would be to replicate my steps, ie renaming the untouched apk in a fresh MODest flash (i.e. break the contacts/phone function), and then see if you can get the whole thing working again without a factory reset, or if not, why. I see on xda, you & I are not the first ones to be tripping over this contacts.apk issue.
The other thing that would be telling is after successfully installing the Edge.zip, whether you can modify something (like a picture) within the contacts apk within the zip, reflash the zip and have contacts/phone still working with the change active.
I think there just HAS to be abetter way than Factory Resets.
Thanks so much again for the insights. I really want to become at least minimally competent at hacking my own ROMs together so I don't have to feel like such a noob/mooch on here, but I really do appreciate the help.
What are your weapons/platform of choice, or, if there are better tools for noobs learning the ropes, I'm all ears.
EDIT: Just found this. The last post is interesting...
https://forum.xda-developers.com/galaxy-s5/devs-only/recompile-seccontacts-apk-t3377142/page2
Click to expand...
Click to collapse
I'm not exactly sure what's going on with your contacts app not showing back up. Ever since modestrom v8 (I think) I've been doing the multi dpi on SecContacts_M_OSup_Note_Legacy_USA and every time I would test it doing the same as your way. After a reboot if the modified app was no good, then I would just delete that new app and change the name of the old app back to .apk, reboot and it would work again. I can't remember running in to any problems where I would have to factory reset or reflash the rom to get things working again.
There has been a couple times where I've had to factory reset to get a color change to show up or if you're adding toggles to the QS drop down that also (sometimes) requires a factory reset to show up.
As far as the post you linked, that is exactly how I do it except I use winrar to open the newly compiled app and drag the changes to the original. When I drag the changes over I change the compression method from "normal" to "store". If I don't change the compression the app doesn't work for me. The apps that I've ran into where I had to change the compression are: secContacts, secCamera, secSettings, and framework-res.apk. Any other app that I've worked on can be dragged and dropped without compression changes.
Jar files don't need an original signature though (so long as signature verification has been disabled, which it has in modestrom). They can be decompiled, edited, recompiled, and copied to the system. It does require a dalvik cache/cache wipe though on all framework files except for the framework-res.apk and twframework-res.apk
If you get a chance, you should start using apktool to decompile/recompile. It will make things easier for you in the long run and most of the time if you've made any mistakes in your edits apktool will catch it. If you're not familiar with apktool you can try using Tickle My Android or Advanced Apktool. You may also want to get Apktool by itself. I use all three of them. Android can be fickle and sometimes what works with one app won't work with another. What's nice about TMA and Advanced Apktool is that they'll do the drag and drop method for you, but when the compression needs to be changed that's when I use apktool by itself.
Sorry for the word vomit. Hopefully, this all makes sense.