Related
I wonder if other people are having these issues, story follows.
I was trying to install the updated ADW.launcher via the adb install command and was getting errors such as "/sbin/sh pm not found". This led to an investigation and it turns out that all the standard applications used to install stuff under android are in /system/bin BUT... The path in the CM6 rom does not have /system/bin in the PATH variable. The only path element as far as I can tell is /sbin. So the solution I came up with was to copy over all the tools from /system/bin to /sbin and this worked.
So here is the real question. How do I change the path on the android device? I have already tried export PATH=$PATH:/system/bin but this does not stick after I close the adb shell.
Update: oh great when you reboot the phone all the copied tools disappear and you have to do it all over again to install another file. Did not expect that one. This makes my need to change the path even more urgent.
Update2: I found it easier to just push the new file over top of the old one in /system/app. This will work for system apps and if I need to install other apps I can just load them from the sdcard.
Is there a reason you are not installing it from market? ADW is the default launcher in CM6, so the one from market is not the same, but they can coexist.
so the one from market is not the same, but they can coexist.
Click to expand...
Click to collapse
Yea I was not really sure about that so I felt it was safer to download the one for CM6. If that works I will do that in the future. I ended up just doing a push over the older version in /system/app, this worked fine.
Is there a reason this rom does not have /system/bin in its path? Is it to avoid toolbox?
anika200 said:
Yea I was not really sure about that so I felt it was safer to download the one for CM6. If that works I will do that in the future. I ended up just doing a push over the older version in /system/app, this worked fine.
Is there a reason this rom does not have /system/bin in its path? Is it to avoid toolbox?
Click to expand...
Click to collapse
It is in the path.
# echo $PATH
/sbin:/system/sbin:/system/bin:/system/xbin
#
Can you help me to change the path? Mine is only /sbin for some reason.
Normal export command did not work for me. Thanks
Maybe its baked into the boot.img? What about the init scripts? Any clues where to start? Maybe I will just flash on a new nightly, would that over write the existing path info?
Ok, I found some clues. A document on the android init scripts describes the path settings. I will poke around in there and see what I can muck up. http://www.netmite.com/android/mydroid/1.6/system/core/init/readme.txt
Sent from my Liberty using XDA App
Answered my own post.
To change the path you need to edit init.rc and add the correct path.
For some reason the nightly I was using had the wrong path in there and would not let me use adb install correctly. I would get an error back "/sbin pm not found". The adb installer was looking for a tiny program (a shell script really) named "pm" but it could not find it because pm is located in /system/bin which was not in the search path. Probably would have caused other problems too.
On a side note, why could I not get an answer to this simple question on a developement thread. Seems like rom creators/moders would know this second hand. Not complaining just makes me wonder.
Sounds a lot like a complaint to me.
I've been busy working on issues that are not isolated to a bad nightly, such as why we can't read telnos and contacts from the sim card.
/system/bin/sysinit gets pulled in from the cm6 repository, so things on nightlies are very fluid - I never know what to expect. Looking at my build, there is no way I could answer your question in any definitive way that would explain the discrepancy. Since I could not verify the problem, I deemed it a non-issue and moved on.
That did sound like a complaint, sorry. It was not really directed at you as I assume there is more than one developer on this site. I got it solved no problems. Maybe this will help someone else down the road. I have seen a few of these posts around and never saw a concrete answer.
I am surprised the phone ran so well with the path mangled so bad. I am also a little surprised that init.rc gets touched at all on a nightly cycle. One of those things I guess.
anika200 said:
I am also a little surprised that init.rc gets touched at all on a nightly cycle. One of those things I guess.
Click to expand...
Click to collapse
I was a little surprised as well.
This is not a guide, a how-to, or help request thread, specifically. I am looking for any new info regarding how the stock boot animation is formatted and called by the system in my new HTC One M8. I am also familiar with creating boot animations, and am willing to share any information I can in exchange, so I encourage all discussion on the subject.
I've been doing animations for a few years for my old phone and those of others. I've never dealt with an HTC phone or KitKat, personally, so that is probably where I need the most help. I know the desc.txt basics and have familiarized myself with the addition of a few new details, with the newer versions of Android. My other sources for understanding boot animations and the desc.txt are here and here, along with my own knowledge from experimenting on my phones. Here's some observations that I've made with my new Verizon HTC M8, as well as questions regarding what I can't yet understand. My important questions are in red below, if you are anxious to help, but don't want to read all the crap. Answers are in green.
Installation - Boot Animation: Part 1
There are stock hTC_bootup_one.zip and hTC_downanimation.zip in /system/customize/resource. I am familiar with this location from dealing with others' phones. There is also a vzw_bootup.zip, which is basically Verizon's logo added to the HTC animation. When I made my first new boot animation for this phone, it was standard for me, except I was making it x1280 px, to scale up to the new 1080x1920 screen. I don't want to play along and rename my animations, so I first placed my bootanimation.zip in /system/media and it played just fine. My next step was to add sound, which required that I learn about the /system/customize/CID/default.xml. I moved the animation to /system/customize/resource, along with the sound (mp3|ogg works fine), and the /sys.../cus.../CID/default.xml was used to point to both files, without having to replace the stock animation. At this point, everything was working great, and despite new hurdles, I hadn't had any issues... yet!
Installation - Shutdown Animation: Part 1
I researched to understand the particulars about a shutdown animation, and made my first, about 7s in length, and named it downanimation.zip, and it played fine from /system/customize/resource, along with my boot animation and sound. I am really enjoying my phone at this point, and loving s-off, root, custom splash screen, etc., all within a couple of weeks of purchase. My last phone was the original Moto Droid, so unlocked bootloaders and root is all I know. I'm a spoiled brat, really. I have more on this subject coming up as well, so stick around.
Adding Sound to Shutdown Animation
I've made numerous boot animations for my old phone with sound. You know I'm itching to have audio on my shutdown animation, too. The first step is the desc.txt edit, obviously. Check. Then I placed it in the same location as the bootani+sound, but it wouldn't play the downani audio, whether I put them (downanimation+audio) in /system/media, /data/local, or placed just the audio in /system/media/audio/notifications or etc. With each move, I edited the default.xml to point to the audio file's location and each time I was met with a silent animation or even black screen. At this point, I conceded some research was in order. I knew I'd seen enough to know it was possible to have a shutdown animation with sound, but I didn't read the details until I had no other options. First question(s), is it true, as it has become apparent to me, that it is not possible to add sound to a shutdown animation without major modification (e.g., by merely adding a path to audio in the /system/customize/CID/default.xml, as works with the boot animation)? (nope, not true--see next Q) If it is possible, how? (answered by Pacattack, here) I have seen some sort of mods before, to add audio to shutdown animation, but I think it played .mp4, rather than being in a standard format.
Installation - Boot & Shutdown Animations: Part 2
There's a few simple steps I haven't tried yet, when it comes to installing a boot/shutdown animation, on this phone, that might clear up other issues.
Primarily, I haven't replaced the stock animations by name, hTC_bootup_one.zip and hTC_downanimation.zip. At first, I simply wanted to retain the stock animations in place, without renaming, plus I wanted to keep the "bootanimation.zip" I've used for years. Despite my stubbornness, I know this could help avoid issues. Foremost, this requires no editing of the /system/customize/CID/default.xml. Modifying this file from the phone can lead to easy errors, of which I've performed many, and many of which result in black screens, AOSP Android boot animation, or a simple "shutting down" text notification. If modifying this file, I recommend edits made next to a backup with a text comparison editor, like WinMerge, to be able to verify the only edits are the intended ones. Does anyone know an easy way to modify the default.xml file from a computer? I'm thinking Linux users probably use cli txt editors via adb session? Maybe busybox/vi after adb shell? What other proven benefits or limitations does this have over naming animations the standard bootanimation.zip and downanimation.zip?
I also haven't tried using PNG files, as opposed to JPGs. I figured out JPGs worked just fine, when working on my first animation, weeks after I got my first Android phone. It provides for much smaller animations, which was crucial with my old phone, and I still don't want to let go of that. That said, is this the key to more stable boot or down animations? I ran into a key issue when working on my shutdown animation. On my first try, I used 720x1280 frames, and used the desc.txt to scale it up to 1080x1920, the same as my boot animation. However, it refused to scale it up, leaving a 720x1280 animation playing in the top left corner, with unused space (360 px on the right and 640 px on the botton.) surrounding. Perhaps, just on the down animation, scaling might work with PNG, which require less decoding than JPG? I'm guessing not. Even though the ShutdownConfiguration section of the default.xml requires image_png="/path/to/downanimation.zip," JPGs work just fine.
I have tried modifying the ShutdownConfiguration section to say "image_jpg=" and (to match BootConfiguration section) "animation=" (can't remember if I tried "downanimation=") without success. I also mentioned above, I tried to add "audio="/path/to/audio.mp3|ogg" without success. Other failures include removing the path, leaving only the filename, and removing the entire BootConfiguration and ShutdownConfiguration sections, which I thought I saw in use on a custom rom for another device.
If I remember right, I used to install my animations on my Droid, from recovery, mounting /system rw and using adb to move and set permissions, avoiding the failed shutdowns/restarts and having to clear dalvik/cache. I don't remember the reasons exactly, but I've encountered numerous black-screens and quick starts when modifying the default.xml or replacing the animations, despite setting permissions, and when using archives that I know are formatted properly and worked before testing my latest creation. This is followed by entries made to the /system/dirty_file_record, which I don't remember having to bear before. I think I've read mounting system and/or sdcard, while in recovery, and interfacing with adb is not yet possible? Anyone know differently?
What has changed with KitKat?
{
"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"
}
What wizardry is this?
When looking inside the stock animations, with RE, you can see the android folder is listed twice, with different timestamps. The contents are identical, and only one folder is visible when viewed on my pc. Is this Linux-related? Is this a bug in RE? Is this something unique to HTC's modifications? Is this somehow a feature of KitKat enhancements? The vzw_bootup.zip does not have this. The desc.txt for the hTC_bootup_one.zip doesn't offer any clues with its familiar formatting:
Code:
1080 1920 20
c 1 60 android
Looking at the desc.txt inside vzw_bootup.zip animation shows possibly a new feature I'm not familiar with:
Code:
1080 1920 15
c 1 1 android
c 1 1 vzw
n 999 1 progress
My best source thus far to explain the desc.txt has indicated,
Jelly Bean (4.1.*) did bring a few small changes. Up til now the first character of an animation section (ie. a "part") line had to be the "p" letter. From now on it can be any letter. If it's a "c", then the given part will be played (at least once) to it's end despite of the state of the boot process. If it's not a "c", then it'll behave like it did in earlier versions with the "p" letter ... i.e. it'll stop the animation when the boot process finishes.
Click to expand...
Click to collapse
That means the "n" should play like a "p" has in the past, but why use "n"? Obviously, stated to play only 999 times, they are scared of an infinite loop (0), but why not "p"? Does "n" utilize a new KitKat feature?
Another point I want to understand, with all of the stock animations, they've abandoned the use of "p" in favor of "c," I assume, because they don't want to risk your phone starting before you get to witness the beauty of their logos. Why do all parts pause/hold on at least one frame? Is this a design thing, to guarantee seemless play between parts, i.e., pause on last frame while the next part is found? I've never seen a black screen creep in-between parts, but then I've never use a white background on an animation.
I first wondered if this might also act to "kill" the part after a pause, as in pause for x number of frames, then move on or exit. Backstory: If you view your animation from your phone by opening Terminal Emulator and typing "bootanimation," your boot animation will play, in full, without rebooting your phone. Yay! I used to do this with my Droid. Oh wait, no, don't do that! The animation will pause on the final frame and not close, leaving you without a way to return to your desktop (unless you have USB debugging enabled, and can adb shell, top, then kill the process-- is there an easier way?) The safe way I know to do this is adb shell, then bootanimation, and ctrl+c when the animation is over and poof, it's gone. :TheEnd I haven't tried this with one of the stock animations or having a pause value in my animation to test if it would exit safely on its own. I assume this is dependant on the version of the bootanimation binary and Android.
Issues With Custom Animations
When I finalized my first shutdown animation, I sent it to a friend to test on his HTC One (M7). I helped him make the default.xml edit and it played fantastic. Of course, his first response was, how about sound? I spent the next 2 nights trying to get sound to play, not having done much research, but I ended with a lot of reading, which left me skeptical about my chances of getting it to work. Having tried numerous default.xml edits and downanimation.zip repacks, I also ended up skeptical about getting my shutdown animation to work cleanly, without inconsistencies. Bear with me, this will take some explaining.
The first boot animation for my M8 was quick and easy. It took me about 1-2 hours, from a 30s, 720p video to working on my phone. It was 720x1280px frames, scaled to 1080x1920 and playing at 24fps, with the desc.txt. When I first created the shutdown animation, I used the same desc.txt, and simply replaced the part folder. This played successfully, however as I mentioned earlier, it would not scale fullscreen. My second attempt used larger images, 1080x1920, and kept the 24fps, which, I thought, had just a tiny bit of lag. Next, I cut the frames in half, but I forgot to edit the desc.txt to play at 12fps, yet the animation played perfectly, I guess because I had also modified the default.xml to reflect 12fps. I've tried multiple times to get the animation working, with 12fps in both desc.txt and default.xml, without success. My only success, being the only animation I've tried so far, had the desc.txt formatted incorrectly. None of the files trip the dirty_file_record, and yet it refuses to play. Can anyone explain that?!?
As I've said, I have some more tests I can run, but it gets old after 20-30 attempts and several late nights without success. My first one was blind luck, but after work settles down, and maybe with the help of XDA, I'm going to get this process down. :laugh:
This post is to collect my questions, for easy replying by you tapatalkers.
1) First question(s), is it true, as it has become apparent to me, that it is not possible to add sound to a shutdown animation without major modification (e.g., by merely adding a path to audio in the /system/customize/CID/default.xml, as works with the boot animation)? If it is possible, how?
2) Does anyone know an easy way to modify the default.xml file from a computer? I'm thinking Linux users probably use cli txt editors via adb session? Maybe busybox/vi after adb shell? What other proven benefits or limitations does this have over naming animations the standard bootanimation.zip and downanimation.zip?
3) Perhaps, just on the down animation, scaling might work with PNG, which require less decoding than JPG? (I had noticed my shutdown animation would not scale up to fullscreen.)
4) When looking inside the stock animations, with Root Explorer, you can see the android folder is listed twice, with different timestamps. The contents are identical, and only one folder is visible when viewed on my pc. Is this Linux-related? Is this a bug in RE? Is this something unique to HTC's modifications? Is this somehow a feature of KitKat enhancements? The vzw_bootup.zip does not have this.
5) Regarding desc.txt in the (Verizon) HTC One M8's stock Verizon boot animation, the "n" should play like a "p" has in the past, but why use "n"? Obviously, stated to play only 999 times, they are scared of an infinite loop (0), but why not "p"? Does "n" utilize a new KitKat feature?
6) Another point I want to understand, with all of the stock animations, they've abandoned the use of "p" in favor of "c," I assume, because they don't want to risk your phone starting before you get to witness the beauty of their logos. Why do all parts pause/hold on at least one frame?
Some interesting stuff and questions, a bit out of my league though, I'm also trying to learn all these things. For editing I just run to Notepad++ :victory: for almost everything and .xml should be easy in it, I'm a noob what can I say lol
I'll subscribe to this thread, might get some interesting info :good:
BerndM14 said:
Some interesting stuff and questions, a bit out of my league though, I'm also trying to learn all these things. For editing I just run to Notepad++ :victory: for almost everything and .xml should be easy in it, I'm a noob what can I say lol
I'll subscribe to this thread, might get some interesting info :good:
Click to expand...
Click to collapse
NP++ is a fantastic app. I use it almost like a web browser, since I document everything for myself in txt files at home and work. I've actually made my xml edits a couple of times in np++ to get a better view of the file, but when the xml quits working, it's time to get some better comparison tools. Actually, I wouldn't be surprised if np++ has a plugin or similar feature actually built in. That app has endless features. Also, it's the best way to make desc.txt edits, if you are trying to maintain the unix line breaks on a windows box. I haven't actually had a boot animation not play because of windows/dos linebreaks, but most good tutorials tell you not to use them. Notepad doesn't acknowledge the unix linebreaks, hence the all-on-one-line appearance. If you want to revert a windows desc.txt to unix format, open in NP++ and go to Edit> EOL Conversion> UNIX/OSX Format. Unfortunately, this didn't help me in any of my animations for this phone. All of my boot/down animations with unix-formatted desc.txt files resulted in animations that black-screened (boot audio even played, but no pictures.)
Something else I forgot to mention in my late night posting, the Verizon boot animation, vzw_bootup.zip, is called using some other method than the /system/customize/CID/default.xml, so does anyone know how? I've seen other threads where other carriers have customized the boot animation, and probably in the same way? By the way, having made so many modifications, I can no longer play the verizon stock animation, I think. When I restore the default.xml to before I modified the zip path, it simply plays the hTC_bootup_one.zip, if I remember correctly. I may have to double-check that.
To illustrate the xml edits I keep referring to, here's the stock default.xml sections for boot and shutdown animations,
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/hTC_bootup_one.zip" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/hTC_downanimation.zip" image="" fps="10" />
</ShutdownConfiguration>
and here's my current config,
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/system/customize/resource/audio.mp3" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" image="" fps="12" />
</ShutdownConfiguration>
I haven't figured out the usage of "image=" in the shutdown section. I think I tried to somehow force scaling by image="1080 1920", image="1080x1920", or image="jpg" and I also tried removing that reference, all with black-screen results, using my only working animation. I haven't tried image="1080,1920" or another separator, not that I'd expect it to work. Muzso explains how to learn the inner workings of the bootanimation code and even provides the code to the different versions, up to Jelly Bean. See the attachments, here. I just wish I was a programmer so I could "read" it. Also, has no dev ever sought to provide a modded or working replacement for the /system/bin/bootanimation binary itself, so that we could have more options built in?!? Shutdown audio, maybe a direct apk interface, so that we could customize it from within a gui? It's open source, so get on it wanna-be-famous devs, immediately!
I had a small breakthrough last night that may explain some of the issues I've had testing shutdown animations. As I made adjustments to the quality (fps) and attempted to add sound, I somewhere along the way made my first working animation quit working. I've had it "installed" for a couple of weeks now, but it would not play. All I was getting was a "shutting down..." popup message.
I've been meaning to compare it to the stock file on a bigger screen and finally got around to it. Using Notepad++, the only difference, other than my edits, was that the document was encoded as "ANSI as UTF-8" or UTF-8 BOM, versus the stock UTF-8 (without BOM). From Wikipedia, "the Unicode Standard neither requires nor recommends the use of the BOM for UTF-8. The presence of the UTF-8 BOM may cause interoperability problems with existing software that could otherwise handle UTF-8." Some Windows programs, including notepad will add the byte order mark at the beginning of any UTF-8 document, which I assume happened with WinMerge. I've only edited the file with Root Explorer > text editor, Notepad++, and possibly WinMerge.
So, having converted in NP++, Encoding > Encode in UTF-8 without BOM > save, I copied over to phone, rebooted into TWRP, mounted /system/, then replaced /system/customize/CID/default.xml. I'm not exactly sure what is necessary, though I also went into terminal from TWRP, chown to root, chmod to 644, then wiped Dalvik and cache. I've done all of those steps in the past, trying to fix things, so I'm fairly certain the encoding is to blame. The next reboot confirmed it worked, and my shutdown animation is restored.
This was mod I did on a ICS Sense 3.6 rom with no shutdown animation or sound ..
As Down anmiation does not use the desc.txt
The size of the images(animi) had to match the screen res.( this is not the case with Boot anim.. )
The frame rate and any sound has to be added to Default.xml in CID folder.
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/shutdown.mp3" useAudio="1" image="" fps="14" />
</ShutdownConfiguration>
Hope this Helps
mine is similar and I have been doing it this way since htc evo
Code:
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/audio_out.mp3" image="" fps="10" />
</ShutdownConfiguration>
and
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/system/customize/resource/android_audio.mp3" />
</BootConfiguration>
and have never had a problem with sound on boot or shut down sound
Pacattack said:
This was mod I did on a ICS Sense 3.6 rom with no shutdown animation or sound ..
As Down anmiation does not use the desc.txt
The size of the images(animi) had to match the screen res.( this is not the case with Boot anim.. )
The frame rate and any sound has to be added to Default.xml in CID folder.
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/shutdown.mp3" useAudio="1" image="" fps="14" />
</ShutdownConfiguration>
Hope this Helps
Click to expand...
Click to collapse
Thanks so much for the info! I knew the desc.txt wasn't being used, and assumed there was some sort of default.xml edit (if available) but was unable to find that info in my searches. Obviously, this has been around for a while. I was able to find mention of this from over 3 years ago... so easy to find, NOW :laugh:
I must have tried at least 20 different configurations trying to find the hidden switch to enable audio. I know I tried something similar to this, but I definitely did not have "useAudio" with cap in it.
dased14 said:
mine is similar and I have been doing it this way since htc evo
Code:
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/audio_out.mp3" image="" fps="10" />
</ShutdownConfiguration>
and
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/system/customize/resource/android_audio.mp3" />
</BootConfiguration>
and have never had a problem with sound on boot or shut down sound
Click to expand...
Click to collapse
This (shutdown audio) is working for you without the use of useAudio="1"? Yours was the first config edit I tried for my phone (HTC One M8) and did not work. Are you on an older HTC phone?
Yep has worked flawless on every phone i have used (using a sprint m8,m7 at the moment)
Sent from somewhere
dased14 said:
Yep has worked flawless on every phone i have used (using a sprint m8,m7 and lg g2 at the moment)
Sent from somewhere
Click to expand...
Click to collapse
I don't know why my verizon phone would be different (other than V likes to troll its customers.) Adding the path to audio, just as with the boot animation was the most obvious solution, but didn't work with the audio file located in the same directory. I also tried other locations, including /data/local/ and /system/media/, with no success.
I had a friend testing for me as well, and this didn't work on his Verizon M7.
I'll try again, without "useAudio=1" to be sure, as I was having some formatting issues from editing with Root Explorer > text editor. I figured out SwiftKey was at the root of those issues, due to auto-entry throwing random trash in the file when I tapped inside the txt file to choose where to edit. No telling how many of my blackscreen issues were due to trash characters in the file. I had to use Notepad++ twice to figure out where the unwanted characters had been thrown in there.
Edit: Ah, just saw your edit
djakrse said:
I don't know why my verizon phone would be different (other than V likes to troll its customers.) Adding the path to audio, just as with the boot animation was the most obvious solution, but didn't work with the audio file located in the same directory. I also tried other locations, including /data/local/ and /system/media/, with no success.
I had a friend testing for me as well, and this didn't work on his Verizon M7.
I'll try again, without "useAudio=1" to be sure, as I was having some formatting issues from editing with Root Explorer > text editor. I figured out SwiftKey was at the root of those issues, due to auto-entry throwing random trash in the file when I tapped inside the txt file to choose where to edit. No telling how many of my blackscreen issues were due to trash characters in the file. I had to use Notepad++ twice to figure out where the unwanted characters had been thrown in there.
I thought only HTC used the /system/customize/resource location for boot/shutdown animations, or the default.xml?
Click to expand...
Click to collapse
are you only changing that line in the default xml or both it and the vzw one
(because I'm curious to know what is the differences in sprint,vzw,att,tmo)
dased14 said:
are you only changing that line in the default xml or both it and the vzw one
Click to expand...
Click to collapse
I left the verizon and htc animations alone, and simply placed my own and modified the /system/customize/CID/default.xml.
This is my current, working animation with "useAudio=1"--my words about previous failed attempts were identical, but without the useAudio bit. I've had the animations working and sound working with the boot, but the shutdown audio was my last issue there.
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/system/customize/resource/audio.mp3" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/audio_down.mp3" useAudio="1" image="" fps="12" />
</ShutdownConfiguration>
djakrse said:
I left the verizon and htc animations alone, and simply placed my own and modified the /system/customize/CID/default.xml.
This is my current, working animation with "useAudio=1"--my words about previous failed attempts were identical, but without the useAudio bit. I've had the animations working and sound working with the boot, but the shutdown audio was my last issue there.
Code:
<BootConfiguration>
<BootAnimation animation="/system/customize/resource/bootanimation.zip" audio="/system/customize/resource/audio.mp3" />
</BootConfiguration>
<ShutdownConfiguration>
<ShutdownAnimation image_png="/system/customize/resource/downanimation.zip" audio="/system/customize/resource/audio_down.mp3" useAudio="1" image="" fps="12" />
</ShutdownConfiguration>
Click to expand...
Click to collapse
how many xmls are in your CID folder?
dased14 said:
(because I'm curious to know what is the differences in sprint,vzw,att,tmo)
Click to expand...
Click to collapse
For one, I'm aware that Verizon (ATT also) has a custom boot animation, which is not called by the default.xml. Verizon's is identical to the stock animation, hTC_bootup_one.zip, but adds an infinite loop with animated verizon logo, some flare on it, named vzw_bootup.zip.
dased14 said:
how many xmls are in your CID folder?
Click to expand...
Click to collapse
Just the default.xml, originally, but I have kept the stock, named "default.xml.stock," and most recent edit, "default.xml.bak" made by Root Explorer. So, technically 1 .xml files and 2 other files.
djakrse said:
For one, I'm aware that Verizon (ATT also) has a custom boot animation, which is not called by the default.xml. Verizon's is identical to the stock animation, hTC_bootup_one.zip, but adds an infinite loop with animated verizon logo, some flare on it, named vzw_bootup.zip.
Click to expand...
Click to collapse
never mind I see
dased14 said:
never mind I see
Click to expand...
Click to collapse
Yeah I never had any other files. I've wondered how the Verizon animation was called.
Sent from my Tapatalk-abusing M8
is what's in stock rom
Sent from somewhere
dased14 said:
is what's in stock rom
Sent from somewhere
Click to expand...
Click to collapse
Interesting. I assume Verizon has another way to call the animation, or perhaps I have similar files in a different location.
Sent from my Tapatalk-abusing M8
I have a Eonon GA2114 (Android 4.4.4 RK3188 KLD) ROOTED car stereo.
I have searched this forum and cannot find what I am looking for so hoping someone can help or point me in the right direction?
I don't have many apps installed, but it seems as though the latest updates to Google, Maps, Sygic, etc. has resulted in an "insufficient storage" alert. I am quite happy with the stock ROM and don't really want to update to some of the custom ROMs that are available, but I do have a very technical background and have only ever owned Android devices.
Does anyone know or can point me towards instructions to change the system partition size? The system ships out with more than 8GB of internal space that I do not use and so would like to either repartition to a single large partition or reverse the size.
Thanks
I think you mean the /data (userdata) partition, and i'm pretty much in the same seat.
Got a brand new 16gig device that ships when a lousy 1gig of /data to store apps on, talk about drunken monkeys making the rom
got about 10 gig on the internal_sd that i'm guessing could be used instead.
I might try to remap that later, i guess you could root it and then either make a symblink there or look at the fstab and see if you could just remount it.
Could also flash Malaysk rom with gives you 2 gigs of userdata, not much more but alot better than 1gb
Yes, I mean the /data (userdata) partition and I checked, while driving to work, I actually have 13GB of userdata. I haven't used this space, but knew it was there when exploring the system when I first got it and for some reason I remembered 8GB. Regardless of the size, it's a waste of space if not utilised.
The system is already rooted.
I have considered Malaysk ROM, but I quite like the stock ROM, especially after installing my preferred launcher. I have already decreased the dpi from 240 to 180 so a lot better looking and a lot more screen space. Have got rid of bloat and so have a stock ROM to my liking.
These systems are well known for their mic troubles and I have taken this up with the manufacturer as I do work in the computer industry, but identifying electrical components and soldering is not something I am too confident with. The manufacturer did however, send me an updated update.img file. I've installed this and it made some improvement, but nothing so significant that I have actually started using the mic. It also has a new wallpaper and noticed that the default apps have been updated, but not sure how?
Anyway, if I don't like Malaysk I can revert back using the update.img file the manufacturer gave me, but 2GB still isn't enough. Hence, wanted to know how to do this myself.
Found this post: http://forum.xda-developers.com/gal...od-increase-partition-size-t3011162?nocache=1 by gsstudios
Obviously, connecting my system to a PC is not as easy and was wondering if anyone would know a bulletproof method of applying the instructions to my system given that it is a stereo with different hardware to a phone?
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
I also found a way to choose where the apps get installed, google a bit for "adb shell pm set-install-location" I belive #1 would be the right choice here.
If that works to redirect everything to the big partition it would be a wonderfull solution.
Download a terminal for the rom and type in there instead of having to connect a computer to the HU etc etc.
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
I would prefer rickthecabbie's solution, but in order to unpack the IMG file, I would need a Linux system (I have tried on Windows and couldn't do it). If all else fails, I'll dual-boot my PC or get a VM if that works? I would be really grateful if you can point me towards a tutorial/instructions if you know any or get the time, but appreciate your help as at least I've got somewhere to start my "Googling"
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
lotherius said:
Wish I had done this. All I wanted was the larger partition, and going with malaysk opened up a whole new set of issues. For example, my single din unit has a separate led display that shows the radio station when the screen is closed. Since flashing Malaysk, it is stuck showing "Init" which is what it shows during bootup. I'm sure the stock rom had been modified by the OEM to update the display, and that's not present in the base Malaysk used. I will probably never have that display working again.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I asked the guys I bought the stereo from; if they had released an updated ROM or if they can provide me a download for the existing ROM. Their customer service so far, has been excellent; their English is not great and it can take a little extra time sending and waiting for messages, but they gave me a link.
At least, I know that if I mess things up, but haven't bricked it, I have got something to revert to.
You could try asking the seller/manufacturer for a link to the stock ROM?
rickthecabbie said:
In the firmware we are using the partition we are discussing is determined by a "Parameter" file. These devices use a Rockchip processor.
In order to change this file I had to "Unpack" the IMG file, find the "Parameter" file and replace it with one from Malaysk firmware.
Then I was able to repack the firmware into a new IMG file, and flash my head unit. After that I did a Factory reset,
and the partition was reset to the new size. A Google search for Unpack Repack Rockchip Firmware will be helpful here if you are feeling adventurous,
or look around for DSA's factory rooted rom, He has included an expanded Parameter file in most of his builds.
Click to expand...
Click to collapse
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
tariqkhan.co.uk said:
Do you know the name and location of the parameter file? And do you happen to still have the parameter file from Malaysk firware?
Thanks for the help.
Click to expand...
Click to collapse
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Hey rickthecabbie, that would be awesome.
Do you have the parameter file by any chance?
I recently made a change to the screen density. I have an 800x600 system and you can only fit 2 rows of icons across the screen so changed the build.prop file to 180dpi and now it looks much like a normal tablet. Having restored the system after making this change; it restored with my changes to the build.prop file intact. I was thinking, could I possibly do the same? I can modify the parameter file using ES Explorer/Terminal and then restore the system, which should update the partitions?
Saves on all the packing and unpacking and mainly; installing dual-boot/debian on my Windows PC.
tariqkhan.co.uk said:
Hey treech, thanks for the help. Sounds simple, so had a go over the weekend, I installed Terminal Emulator for Android by Jack Palevich and run the command "adb shell pm setInstallLocation2", which provided me with a long list of commands I could use and think the command executed successfully? Previously tried "adb shell pm setInstallLocation1", which produced an error stating device not found. Still getting the "insufficient storage" error so presume it has not worked, but will continue looking into this.
Click to expand...
Click to collapse
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
treech said:
Well, pretty sure you'll need a space between setInstallLocation and 0/1/2 or whatever you choose to test, haven't tried it myself yet due to lack of time.
Click to expand...
Click to collapse
Yep, thought it would be something simple. Do you know of a command which would print which partition 0 and 1 and 2 is?
Don't really want it to set the install location to a partition that I wouldn't want it set to. Also, some apps are not movable so I don't think this would solve the issue right?
Not sure, you'll have to google it
And well best is to install a few bigger apps and see what happens i guess.
rickthecabbie said:
The Parameter file is simply called "parameter" .
It is located in the ROOT of the IMG file when I unpacked the IMG using "RK3066 IMG Mod Tool" I had to remame the IMG from update.img
to wendal.img and place it in the tool directory. After running the tool Unpack, the files from the IMG were located in the newly created Temp directory of the tool folder. I replaced the file "parameter' in Temp with the one from DSA's firmware which I unpacked with the same tool (in a different folder on my desktop, to prevent confusion). Then I ran the "Pack" function in the tool and it created a file called "update_new.img" this was the modified firmware I flashed to my head unit.
I will edit this post later to a step by step tutorial for those who might be confused.
Click to expand...
Click to collapse
I don't mean to bug you and do appreciate the advice so far, if you haven't got time to do the tutorial, do you know of a link to an existing tutorial?
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
jbleasdale said:
Rick wrote up a superb step by step tutorial here:
http://forum.xda-developers.com/and...torage-fix-t3257827/post64037230#post64037230
Click to expand...
Click to collapse
Thanks for the link.
Gave it a go and didn't work for me; I'm sure I've made a simple mistake somewhere although I tried twice.
As my system had already been wiped, I thought I would give DSA ROM a go and for anyone looking for a stock ROM, this is perfect. Any MODS included are a necessity in my opinion and some you will probably not even notice, but it has the 2GB system partition.
Overall I love the Pixel XL, but with all of my previous Android phones having Root access, I have always run Viper4Android, and in my opinion the sound quality output of the stock Pixel is awful by comparison. So, my primary reason to use the awesome work done by those who brought us bootloader unlock and Root, is to be able to use Viper4Android.
With the changes to Pixel partitions and overall structure, as well as the method of Root, so far I have not been able to get Viper4Android working. This thread will be a place for us to discuss what we have tried, learned, and hopefully figure out a solution! I do think that what ever needs to be done to get it working will be the same for both the Google version of the Pixel (XL) and the Verizon version, as the method of Root is the same for both as well as the overall structure for the partitions and images.
So far, after unlocking bootloader, and then using the Root method, I have not gotten Viper4Android to even detect root. This was with stock kernel, and no other changes to any audio files or other settings. I did install a couple of apps (Titanium Backup, Solid Explorer) to validate Root was working. I also tried installing BusyBox, which seemed to install just fine, but no change to Viper.
I am not very up to speed yet on how systemless root may be a factor in this, the Pixel XL is the first device I have had with it. Anyway, I will keep plugging away at some things and post what I learn.
once there is a custom recovery, it will be very easy to flash packages that will make viper work..
search XDA for the Arise Sound mods
What error are you getting? I'm getting a bad BusyBox error. I fixed the I/O error by renaming audio_effects.conf.
Sent from my Pixel XL using Tapatalk
sionicion said:
What error are you getting? I'm getting a bad BusyBox error. I fixed the I/O error by renaming audio_effects.conf.
Click to expand...
Click to collapse
Viper4Android cannot detect root. See screenshot.
mrhds said:
Viper4Android cannot detect root. See screenshot.
Click to expand...
Click to collapse
I got that error when viper was in priv-app, make sure you set the kernel to permissive. I do it by going into the terminal app and entering the commands su, to gain root, setenforce 0, to switch to permissive, getenforce, to make sure it's permissive.
Sent from my Pixel XL using Tapatalk
To make viper work we have to use the same trick that is used for adaway but with all the files needed by viper which is:
- Move the files to /su
- Make copies of the files viper needs to change, make the changes and copy the modified ones to /su
- Create a /su/su.d/60viper with mount binds on all the files
Or have a modified version of Viper that could read from /su or /system_root instead.
exadeci said:
To make viper work we have to use the same trick that is used for adaway but with all the files needed by viper which is:
- Move the files to /su
- Make copies of the files viper needs to change, make the changes and copy the modified ones to /su
- Create a /su/su.d/60viper with mount binds on all the files
Or have a modified version of Viper that could read from /su or /system_root instead.
Click to expand...
Click to collapse
That's nothing I can figure out but it does confirm my thoughts that viper is having trouble because there is no /system and instead a /system_root. I guess we'll have to wait it out until someone patches viper. Or someone figures out that trick and posts a guide for it.
Sent from my Pixel XL using Tapatalk
I did it! I can't believe it! Viper is working!
So I was googling manual installs of Viper and came across Arise, somebody said you just have to paste the contents to system if you can't flash. That's what I've been doing kinda but it wasn't working before. Anyway I got Arise and went into the zip and into the Leviticus folder and pasted the contents where I believed they belonged. I got some errors so I had to use FX and ES File Explorer together, to rename files, copy files over, etc. I copied over the files to the folders underneath /system_root/system/, except su and su.d. su is just /su in my file apps. Although I think the permissive script is in the wrong spot since I still had to manually run the setenforce 0 command.
Doing it manually this way avoids Viper wanting to install a driver, it's just ready to be powered on, avoiding I/O and busybox errors. Leviticus 1.3 is what I used from the Arise website since I couldn't find any other download and it was on the header of the website.
Now if I could just figure out how to increase sound output. The mixer_paths.xml is different slightly, the digital volumes are like digital mix volumes, and changing their values doesn't seem to have an effect. I still have to play around with that, I might just wait for someone else to discover what values alter the headphone sound output. But at least I made progress! Hope this helps some people out.
Sent from my Pixel XL using Tapatalk
Viper is working!!
@Mentalmuso posted his work on a script that takes care of permissive, busybox issues, etc.! Thanks a ton! I downloaded the zip package, ran the script and it works! Here is the link:
http://forum.xda-developers.com/pixel-xl/themes/mod-weta-audio-t3491179
@sionicion: I was about to test out your route as it looked promising, but then noticed the other post
quick question... (this may be stupid)
If you root - get viper working
can you then unroot and be good as far as safetynet and stuff?
Or does viper ALWAYS need root?
I'm trying to warm up to the idea of not rooting this phone and maybe doing android pay.
So much stuff that I used to use root for isn't needed anymore (culminating with the "autotools" addon for tasker)
But I just don't know if I can live without viper, it makes such a huge difference.
Thanks,
I've learned to live without it. It's tough as Viper is really good but I really grew tired of coming up with workarounds for an app that isn't even maintained anymore. Fiddled around with the stock eq in Play Music for awhile before I was satisfied.
Yea, I really miss Viper too but not sure if I want to root anymore. The only reason I use Viper is for the volume boost for my BT earbuds when watching mkv files in MX Player. For some, all mkv files play at a pretty low volume. Viper is able to increase it substantially. I sitll haven't found a non-root substitute for this problem yet. If anyone can advise on an app that does volume boost for BT headsets, that would be greatly appreciated.
Hi everyone,
I have a Nook GlowLight 3. I don't like the default screensavers, so I'd like to delete them and (optionally) put in some new ones. Is this possible?
Maybe it's just a matter of getting into the Nook's file system and replacing their image files with my own (with the same filenames)?
This Nook is new. I don't mind voiding the warranty, but I'd rather not unless I know it will be worthwhile. Otherwise, I would try it myself. So I'm hoping some kind soul who has a NGL3 that they have already broken into would be willing to take a look at it for me.
Please let me know if I can help! Thank you!!
Robert
I've got too many Nooks and I'm far removed from stock.
Do you have a directory /data/sleep/
That used to have PNGs for some standby images.
Do you currently have the old, creepy authors?
I have not rooted it or anything yet, just plugged it into my Mac and looked at the default directories it comes with. There is basically nothing there– I even had to research online and experiment how to just create a directory where I could sideload a PDF. So, no, I haven't seen any directory like you mentioned. And I'm not sure what you mean about the old authors(?). The screensavers I have are Symbols and Quotes. In any case, this is my first Nook, and it's less than a week old.
So, do you think there is a good chance I could make changes to the stock screensavers?
The "old, creepy authors" were the screensavers that made the Brontë sisters look like the witches out of Macbeth.
These images are all packed away in /system/priv-app/partner.apk in res/drawable-mdpi-v4/
Code:
artboard_1.png
artboard_2.png
artboard_3.png
artboard_4.png
artboard_5.png
artboard_6.png
artboard_7.png
artboard_8.png
alexander_pope.png
chinese_proverb_00.png
cicero.png
jane_austen.png
john_wilson.png
lady_mary_montagu.png
louisa_alcott.png
robert_southey.png
thomas_jefferson.png
thomas_kempis.png
The list of images is in res/values/arrays.xml in quotes_imgs and symbols_imgs
The actual screensaver mechanism is com.nook.partner.screensaver.ScreenSaver (in partner.apk).
If you repack that all it won't have a B&N signature
I'm not sure how much that will break things.
In worst case you could resign everything.
I think that I'd just rewrite ScreenSaver to fetch PNGs from a directory like /data/sleep
That way, changing the collection would be easier.
Oh, and another thing...
As always, the sloppiness of B&N gets to me.
Those "quote" image files are ten times the size of the "symbol" image files.
Why? Because they have a very subtle dithering to the backgrounds.
It's nothing that you can see even on a regular LCD monitor, let alone on a black & white eInk panel with 16 shades.
So the file is basically trying to compress random noise. That doesn't work out well.
Below is what you get when you use the fill tool (red) in MS Paint on the image.
It leaves holes because the adjacent pixels aren't exactly the same value.
Oh, yes: I remember those goofy portraits.
OK, thank you– I really appreciate your help! I am excited to try this out when I can snag some free time. I will try to post what happened, too.
OK, I was able to pull that partner.apk file to my Mac, and unzip it. The images are there. Awesome!
So, I'm temped to create my own B&W/greyscale pngs, with the same dimensions, and give them the same file names. Then put them in the same locations, rezip (with an apk extension), and push it into place. I know it will have a different file size, etc, but do you think that will be a problem? Normally I'd just try it, but I'm trying to err on the side of caution.
Thanks!
Newtham said:
rezip (with an apk extension), and push it into place.
Click to expand...
Click to collapse
Yes, it should work.
There doesn't seem to be any problem with signatures.
I modified all my images for fun and it didn't break anything.
(Although, I've hacked so much stuff on this that the screensaver never activate. This is not my primary reading device.)
It must have some signature (the originals will do) or it won't be acknowledged as an APK.
Make sure that you keep the original file as a backup.
I'm still new to this, so basic question: what is a signature (in this case) and how do I create or modify it?
Thanks!
Newtham said:
What is a signature...
Click to expand...
Click to collapse
Signatures are the three (or more) files in the META-INF directory in the zip (apk).
If they are there, that's fine.
To learn about apk signing Google it.
@Newtham
Oh! I figured something out. I looked through the code.
If you just want to have one screensaver of your own (which you could manually change).
All you have to do is change some undocumented settings.
File: /data/data/com.nook.partner/shared_prefs/screen_saver_preference.xml
Code:
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
[color=red]<boolean name="pref_key_screen_saver_from_sdcard" value="true" />
<string name="pref_key_screen_saver_from_path">/sdcard/sleep.png</string>[/color]
<boolean name="pref_key_screen_saver_low_power" value="false" />
<int name="key_screensaver_img_index" value="8" />
</map>
OK, awesome, thanks!
About a week ago, I tried just modifying the image files, rezipping & renaming to apk, and pushing into place, but I didn't modify the signatures. So now I'm stuck on the boot screen. (I forced it off in the meantime, but since it's e-ink, its still showing the boot screen.)
I can still see it on the command line via adb, but I no longer have write permission so I can't push the original apk back into place. So that's my next task. I haven't had time to play with it since then. It's fun playing with this, I just wish I had more time.
Newtham said:
I no longer have write permission...
Click to expand...
Click to collapse
Well, you did it once, it's just a question of making /system rw:
Code:
# mount -o rw,remount /system
One of the silly things that B&N did was making the "screensaver" and the "wallpaper" the same thing.
I'll have to write some code to make them separate things.
Lol! As I dived into this I realized that I had been all over this ground before.
The stuff I wrote in https://forum.xda-developers.com/showpost.php?p=79994025&postcount=11 about using settings to disable the B&N wallpaper is true but not necessary.
You can disable all that silliness with:
Code:
# pm disable com.nook.partner/.daydream.DayDream
You can set a simple white wallpaper using my Wallpaper.apk app available in the signature
The wallpaper only appears as a background to a launcher (or any app that has no background).
The Glow3 4.7 & Glow4 5.0 both broke the Wallpaper, you need a separate patch for that, see below.
I had previously made a patch to cycle through user supplied PNGs as a lock screen.
That patch is available in the signature as nook45patch.zip
Code:
C:\> adb pull /system/framework/android.policy.jar
C:\> apktool d android.policy.jar -o AP
C:\> mergesmali /v \AP\smali Screen.smali
C:\> apktool b AP -o android.policy.jar
Then replace android.policy.jar and delete/backup/rename/whatever android.policy.odex
Then stuff your PNGs in /data/sleep
Erm, I think this mostly applies to Glow2 4.5
I'll look more closely at Glow3 4.7
glow45patch.zip works fine on the Glow3 4.7 & Glow4 5.0
So, the nook45patch.zip works fine on the Glow3 4.7
I kind of confused myself, strange things happen if you have no images in data/sleep.
I'll look into that too.
The Glow3 & Glow4 have this problem where B&N stole the functionality of wallpaper for sleep screen.
The background on launchers appears black even though the Wallpaper API changes /data/system/users/0/wallpaper correctly.
I should be able to solve this one too.
There was a minor bug in the old patch.
It would barf if you didn't have any user images.
The new glow45patch.zip is in the signature under mergesmali.
The aforementioned glow45patch.zip is a valid patch for Glow3 4.7 too.
There is also the issue of the black Wallpaper on Glow3 4.7 when using a stock Launcher.
Does anybody else have this/notice it/care?
With 4.7 B&N got rid of /system/priv-app/SystemUI.apk and put it all into /system/priv-app/partner.apk
This necessitated a change in the WallpaperManager since it's all a different package.
The actual ImageWallpaper.DrawableEngine.drawFrame() is a bit complicated.
I couldn't (be bothered to) figure out how it was supposed to work and where it was failing.
To my taste, anything other than solid white wallpaper on an eInk device is just distracting.
I wrote a small patch to make drawFrame() just drawColor() instead of scaling and rotating Wallpapers.
Is there any interest in that?
I have been working on this, but I can't get write access via adb anymore. I have tried everything I can think of, including your suggestion above. I can log in to the adb shell and run as root and make changes there. But anytime I try to push anything with adb, it tells me it is read-only. When I run rootnook.sh, it tells me I'm already rooted, but no superSU found (and then roots again, with no different results). adb root doesn't work, either.
The only major thing that's changed recently is that I installed the latest nook update, which I thought would be a good idea before I start hacking. Maybe that messed it up.
I'm stumped (which is not difficult to do...). Any suggestion on how to get back in there?
Thanks!
You probably de-rooted yourself.
Does adb shell give a # prompt?
Does the shell command "id" tell that you are root?
Does the shell command "mount" tell you that /system is rw?
Does the shell command "getprop ro.secure" say 0 (security is off)?
When in doubt, push to sdcard and then copy (cp) to where it should be.
Thanks! Moving it to sdcard did the trick.
I unpacked the apk with apktool, edited the images directly (didn't change the file names), repacked it with apktool, and then (finally, by using the sdcard directory) got it back to the Nook. And then copied it into place. But I still get the same results: the GUI gets stuck on the boot screen.
So, do you think this has to do with signing the apk file? I did a lot of research on it, but mostly what I found was how to sign your own file, not someone else's. Do you have any tips on how I can do this (if that's what's needed)? Thanks!!
(P.S. Thanks for the info on the glow45patch. I haven't had a chance to look at it too closely yet, but it looks interesting. I'd still like to mod the actual pics, though, if I can.)