Related
Creating your own boot animation is an easy process. Here is a short guide showing you how:
You must create a series of .png files. There are many programs out there to do so. There are basic ones like Easy Gif Animator. Or more professional ones like Adobe After Effects.
__________________
The package you will create is made up of two main parts:
The first part is the text file:
The 'desc.txt' file tells your device how to play the sequence of images. It will look something like this:
Code:
1282 802 30
p 1 20 folder1
p 0 0 folder2
In the example above the files will be stretched to fit the screen, will play at 30fps, folder1's contents will play once, then wait 20 frames, then folder2's contents will play infinitely, until the device has booted.
The '1282 802' figures are the resolution you wish the files to be displayed at. The screen is obviously 1280x800 but I've found that if you set it to that resolution you get a border of coloured pixels around the extreme edge of the display, so I suggest you set it to 1282 802 to make sure your animation looks fine.
The '30' is the frames per second (fps), the speed at which you would like your animation to play.
p = a break in the text file to show a new command will be issued.
In the next column the '1' means it plays that sequence once (setting it to '0' means it plays infinitely), with the '20' meaning it will wait 20 frames before it continues onto the next line of the file (if set to 0 it doesnt pause at all).
folder1 and folder2 are the names of the folders containing your PNG images. You can use multiple folders if you wish, or just one folder. It doesnt matter what you name the folders, as long as you specify their names in the desc.txt file properly.
The second part are the actual images you have created:
The files must be named in a progressive numerical format, e.g. 0.png, 1.png, 2.png, 3.png, etc. and placed in a folder.
If there is a gap in the numbers or any missing, the animation will look jerky, or if you are just testing via ADB it will just fail altogether.
When you are satisifed with your files, they all need to be packaged up into a zip file. Use any program like Winzip or Winrar to do this. You need to name your file 'bootanimation.zip' and make sure it's not compressed, so choose the 'store' or 'not compressed' options when you are creating your final file.
To test your file works nicely follow the 'How to Install' guide I made HERE.
If you wish to upload so others may use your creation, you can use THIS handy site to upload to multiple sites at once for free.
------
Tips:
Creating a series of images 1280x800 will result in a massive zip file. You're better off scaling down your images (e.g. 640x400). They will be stretched to fit the screen so don't worry about that. Also a max of about 100kb each is advisable for a series of up to about 100 images total.
Depending on the length of your animation you may need to scale your images down or reduce their quality so that the end files will play properly. Total size shouldn't really exceed about 8mb (the TF can still play the files if they are larger in size, but they don't run nearly as well). A 1.5mb sized package seems to play best however. The original TF animation package is about this size.
------
Troubleshooting:
If your sequence doesn't play on your device, make sure you have done all of the following:
Sent the file across properly using ADB.
Saved the zip file with no compression.
Renamed it bootanimation.zip.
Included the desc.txt file.
Make sure there is an extra blank line at the end, inside the desc.txt file.
------
I've included an example .zip file below with the basics in it. It's not a full animation file, but an example so you can familiarise yourself with the settings/structure. If you want to download and check out some fully compiled sample files you can do so in my thread [url="http://forum.xda-developers.com/showthread.php?t=1101535]HERE[/url].
____________________
Any questions? Have I missed something? Comment below...
____________________
Thanks for the guide. I have found this works fine for a single folder setup, but all my double folder attempts have failed, using your exact guide and ensuring consecutive numbers between folders. The terminal says "alloc iovmm" and terminates shell when I get to the second folder. I was hoping to have a "start up" sequence, with just part of the animation looping until the end of start up, but no joy.
--Jak
You need to make sure there are no hidden files inside the folders, so make sure (if you are using windows) that everything is set to show up in your file manager/explorer. Sometimes there are hidden files like 'thumbs.db', etc. You also need to make sure that the folder1 and folder2 lines, are on separate lines in the 'desc.txt' file.
any chance on audio support for boot animations? I remember it working in 2.2, but haven't really messed with it since then.
Thank you very much for this detailed tutorial.
I've noticed that if you change the image from RGB mode to indexed the size of the file will drastically decrease without much of change to the picture.
thank you very much for the info....you rock man !!!
Awsome
As soon as I read your post, went to testing, took an image and edited in MSPaint, created the zip, 480x800, and it works perfectly, as long as the FPS is set to 24 for my LG Optimus Black.
Forgot to look at the size of the archive, it turns to be 27MB, but the thing just works. Thanks, man!
Boah.. will try this some time. Thanks for posting!
would someone mind taking a look at my animation and tell me where i've gone wrong? im feeling pretty thick as this should be an easy procedure and i just cant get it working.
when i try running it with adb it runs through folder0 then stops and says 'segmentation fault' in my command prompt. when i reboot it just shows a black screen after running through folder0.
thank you!
jimmygoska said:
would someone mind taking a look at my animation and tell me where i've gone wrong? im feeling pretty thick as this should be an easy procedure and i just cant get it working.
when i try running it with adb it runs through folder0 then stops and says 'segmentation fault' in my command prompt. when i reboot it just shows a black screen after running through folder0.
thank you!
Click to expand...
Click to collapse
Instead of folder0 and folder1 try renaming them to part0 and part1
baseballfanz said:
Instead of folder0 and folder1 try renaming them to part0 and part1
Click to expand...
Click to collapse
That's actually what I had them named as originally, also tried p0 and p1.
thanks though.
jimmygoska said:
That's actually what I had them named as originally, also tried p0 and p1.
thanks though.
Click to expand...
Click to collapse
Try here, it's a recent bootanimation discussing thread.
http://forum.xda-developers.com/showthread.php?t=1537798
baseballfanz said:
Try here, it's a recent bootanimation discussing thread.
http://forum.xda-developers.com/showthread.php?t=1537798
Click to expand...
Click to collapse
Cheers, going through it now.
How to enable boot sound. What will i edit?
Sent from my GT-S5670 using xda premium
There is no boot sound that I am aware of...no device I've ever booted had sound (until it booted completely)..there may be a way to enable it but thus far I haven't found one.
I have just made a stupid mistake!
I connected my NST to my laptop with USB and deleted the "screensavers" folder, and now:
1. the NST will show a whole black screen while it sleeps
2. I can NOT open the "Screen" setting now
The worse thing is I used my own screen saver and I forgot the folder name of my own screen saver, so I could not make my "screensavers" folder restored!
How can I make the screen saver back? Any comments are welcome!
Well, the best place to put screensavers in my opinion is in:
/system/media/screensaver/authors
That's because there are hardwired paths in the B&N software and this is the only way to get rid of the Bronte sisters without going black.
From a Linux perspective the user screensavers are in /media/screensavers
Mounting the Nook over the USB this appears as /screensavers
If you copy an image to /screensavers/Bogus/boring.png it will be selectable as Bogus on the screensaver setting.
Renate NST said:
[...] and this is the only way to get rid of the Bronte sisters without going black.
Click to expand...
Click to collapse
I was tinkering with the default screen saver images, trying to get rid of the girls. It does seem that that first default image is hardcoded to that specific image. A few tries at moving and renaming files didn't work.
I'm relieved to hear that "going black" is the only consequence of removing the default screensavers. I was concerned I'd get a bootloop or similar annoyance by breaking the images in there. Knowing that, I'm going to try a few more adventurous changes to the system.
---------- Post added at 10:12 AM ---------- Previous post was at 10:08 AM ----------
flyisland said:
[...] How can I make the screen saver back? Any comments are welcome!
Click to expand...
Click to collapse
The device still shows up on your PC when you plug it in, right? You should be able to recreate the screensaver folder. I don't have the file handy to confirm, but I believe you can find the original folder in one of the B&N update .zip files, extract it and just copy it over the NOOK (internal) folder when your device is mounted.
If you had it set to a non-default folder, it may still cause problems, but perhaps that folder being present will be enough to show the option again.
Good luck with it!
I believe bobstro is correct, it appears that the default image is hardcoded somewhere to /system/media/screensaver/authors/Bronte_Sisters.png. However, any image with this name will end up being the default image.
So get or create the image you want to be your default screensaver.
Connect to your nook using adb.
remount /system as read/write (mount -o remount rw /system)
copy the image you want to be your "default" screensaver over the /system/media/screensaver/authors/Bronte_Sisters.png (make sure the name of your image is /system/media/screensaver/authors/Bronte_Sisters.png).
After a reboot, the nook will display your new image as the default screensaver.
I'd like to change the wallpaper on the root u-tube home screen, but I don't see how one can access the internal folders. I'd like to be use adb push but I don't know the path for the 'Picture', or 'Wallpaper gallery Home' that are possible locations for adding the images.
You do mean the desktop wallpaper?
I'm boring. I just changed the default wallpaper to solid white.
In /system/framework/framework-res.apk
Replace /res/drawable-mdpi/default_wallpaper.png
To answer your original question: I don't know.
Thanks for the information; however being a complete beginner that does help me get a little bit closer to what I'd like to do but there is still much that I don't really understand. How do I access that location? And should I add my new image to the subfolder with a totally differently name, or should I rename the my image to that of the default.png and replace the old image?
If I adb push to the nook my image renamed to match the old wallpaper image, will that work?
still trying to replace home image in rooted Nook ST
I have a question for someone who knows more than I about android systems. Thanks to Thank Meter 78 who pointed out the file I need to change in order to replace the home image is in
/system/framework/framework-res.apk
and that I need to replace in that apk
/res/drawable-mdpi/default_wallpaper.png
Will the following procedure work properly without screwing up my newly rooted Nook?
Using Root Explorer I copied the 'framework-res.apk', and saved it to my Nook sd card. Then copied that apk file to my windows xp computer and changed the extension to 'zip' and unzipped it. The png file thus is available for replacement by another image of identical size and name.
Will it be correct for me to rename the modified .zip extenson file containing a new default_wallpaper.png file back to its original .apk extension, copy/paste it to the sd card, insert the sd card into the Nook, and the using Root Explorer to copy the apk file and paste it back to the drawable-mdpi folder where it will replace the nook apk (being sure that I change the r/o to r/w permission for the folder, and change it back after the replacement)?
Could there be adverse effects of the replacement?
My friends all call me Renate...
Yes, that procedure works, correcting for your typo.
Unzip, replace PNG, zip, copy back to /system/framework/framework-res.apk
You don't need to set it back to r/o. It's better/easier to just reboot, preferably with ADB.
You should always backup at reasonable intervals and before major changes.
Heck, I've bricked my Nook a dozen times.
Thanks Renate!
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Renate NST said:
Ok, the actual answer is:
The gallery uses the mediastore images database.
The crawler can't find anything even if it's right under its nose.
The databases are stored in /data/data/com.android.providers.media/databases
There's internal.db and another db for each unique SD card inserted.
The crawler is equally lame finding MP3's also.
That's why both Music and Gallery say "no media".
Click to expand...
Click to collapse
1) I thought the original question was about u-tube (I guess "Youtube" ;-))
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
The Media Scanner service is what scans.
Normally it is activated on insertion of an SD card.
It does not run continuously.
It ignores directories with file in it called ".nomedia"
The MediaScannerConnection can be used to request scanning of a single file.
Level 8 API (we're 7) can request scanning of multiple files.
It seems to turn its nose up at files and not put them in its database.
ajislav said:
2) ad gallery - I was always wondering how to make it see the JPGs I had as screensavers... Would you have any ideas how to fix this (i.e. make the crawler work)? Or maybe the other way round, how often is the crawler running? Would battery be improved if it was turned off/killed?
Click to expand...
Click to collapse
Are you asking about having your own pics as screensavers?
I did that by connecting my NST to the PC, and creating a folder (one word name) under screensavers/ and copying the pics into that folder. It then shows up in the screensavers menu, and you can select it. The location from within the nook is /media/screensavers
--
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Renate NST said:
The emulator's MediaScanner works fine, the Nook's appears broken.
You can manually enter images into the MediaStore:
(This requires sqlite3 installed or pull the database and do it on your desktop.)
Code:
sqlite3 /data/data/com.android.providers.media/databases/internal.db
insert into images (_data, mime_type) values('/media/myphoto.png', 'image/png');
.q
Call up Gallery.
You will see a blank thumbnail because one has not been generated yet.
Click on that.
Click to expand...
Click to collapse
Isn't their any way to repair the nooks MediaScanner? like, re-install it, clear the app data, copy another one in from another android 2.1 device? I don't understand why it isn't working, or why it can't be fixed. I've tried backing up the app and re-installing it, deleting the external db's, running media scan apps. Disabling it, re-enabling it...
hi there
is there a way to change the boot logos ?
Michael
megasounds said:
hi there
is there a way to change the boot logos ?
Michael
Click to expand...
Click to collapse
Yes, but I didn't tested this yet
-W_O_L_F- said:
Yes, but I didn't tested this yet
Click to expand...
Click to collapse
just give it a try !
how ?
thx m
Registry edit to change logo to "Samsung"
Code:
[HKEY_LOCAL_MACHINE\SYSTEM\Shell\BootScreens]
"WPBootScreenOverride"= "\Windows\System32\mologo_OPEN_Common.bmp" (String)
I did change path and now got both of them, Samsung one and custom because file : mologPEN_Common.bmp is not even displayed. Must be in other location.
Code:
C:\Data\Users\Public\Bootlogo\logo.bmp
Yeah, it'll be different depending on where the phone comes from. Just check your System32 directory first for logo images, then set the one you want. Or upload your own to the phone and use that path...
I looked on all mologo bmp files and none of them looks like the one while booting. So now I got WP, Samsung and the custom one on the end. Is wasting time I believe
true
djtonka said:
I looked on all mologo bmp files and none of them looks like the one while booting. So now I got WP, Samsung and the custom one on the end. Is wasting time I believe
Click to expand...
Click to collapse
TRUE
in my case i do not want to see any boot logo ...i do not know if you can switch it completely off ...:fingers-crossed:
so first we want to know : WERE are the default logo's stored in the filesystem ???
what is the location of the default logos ?
M
megasounds said:
TRUE
in my case i do not want to see any boot logo ...i do not know if you can switch it completely off ...:fingers-crossed:
so first we want to know : WERE are the default logo's stored in the filesystem ???
what is the location of the default logos ?
M
Click to expand...
Click to collapse
the first boot logo is Most likely stored in the bootloader it self ( so no way too Change that one)
Once you have complete file system access, just place one in Windows\System32 and name it "mologo_custom.bmp" for easier reference and save it as a 24bit BMP file. I have the original bootscreen and 2 custom ones for you to choose from, attached below:
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?