brotherswing
Android Expert
While Ben is quite correct (42 is the meaning of life) it is not yet known what the question is. Age, however, is a state of mind.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][WIP] BACKside ROM (CM7) + Green Machine Theme
- Thread starter JerryScript
- Start date
-
- Tags
- lg optimus v
JerryScript
Android Expert
I believe that converter package only works with W7 without service pack-1.I found these instructions. Downloaded boot_screen_log_creation_package. Created my image in Corel PhotoPaint and saved as png. Put it in the RLE folder. Open command window in RLE folder and convert_image_to_rle.bat logo.png. And always get this error.
I'm trying to use this for my boot image. Sized to 320x480
Does it have to be saved as a png with any special parameters? Does this converter work with win 7 64? What is the meaning of life? Am I asking too many questions?
When you create your png images, you need to set them to 16 colors, and no other options at all (no comments, no layers, no transparency of course). In Gimp, I first set to RGB, then set to indexed at 16 colors. Then you have to convert it to RAW format using ImageMagick. Then you convert it to RLE using to565.
I have complete instructions for Ubuntu in the building your own rom thread at AC forums. If you don't want to use WiBu (the easiest way to use Ubuntu with W7 without partitioning), ask LeslieAnn for details on using W7.
Atma
Extreme Android User
In Gimp, I first set to RGB, then set to indexed at 16 colors. Then you have to convert it to RAW format using ImageMagick. Then you convert it to RLE using to565.
Gimp .. check
ImageMagick..check
to565..check
Thanks.
brotherswing
Android Expert
I can of course Slackify said Ubuntu directions. I have both OS's available, which do you recommend?
JerryScript
Android Expert
For the new-to-linux crowd, I recommend WiBu. It's a simple Windows installer that creates a virtual partition rather than truly partitioning your hd. Installing and un-installimg is as simple as any Windows program, so even someone who can barely turn on a computer can at least try out Ubuntu via WiBu.
Once they get a taste for it, and if they decide they like it, they can migrate to a permanent installation via partitioning and dual-booting. I keep it on most of my Windows boxes, just in case my main box is busy compiling, or I'm not near any linux boxes, and I need to do something in a linux environment.
And you can build Android from source using a WiBu installation, I posted directions in the Building Your Own ROM thread at AC. Just be sure to set the virtual space as large as possible on your machine. If you can't set it to at least 50gig, I would recommend editing the config files so you can (google it).
JerryScript
Android Expert
Take the battery out, put it back in, try to boot again.
If it does the same thing after this, pull the battery again and put it back in, but this time reboot into recovery. Wipe cache and under advanced wipe dalvik cache. Go into mounts and format boot, data, system, and cache. Then reflash the ROM and gapps zip files. Then reboot.
If you still have the same issue, you have a bad download of the ROM. If that's the case, I will assume you did not check the posted md5sum before flashing. Redownload the ROM on your PC, check the md5sum, connect via ADB, push the ROM to your sdcard while in recovery mode, wipe and format everything again, and then reflash with the good download.
If you don't want to use ADB, then you will have to restore a backup in recovery (I hope you made one).
benslgdroid
rockstar
For the new-to-linux crowd, I recommend WiBu. It's a simple Windows installer that creates a virtual partition rather than truly partitioning your hd. Installing and un-installimg is as simple as any Windows program, so even someone who can barely turn on a computer can at least try out Ubuntu via WiBu.
Once they get a taste for it, and if they decide they like it, they can migrate to a permanent installation via partitioning and dual-booting. I keep it on most of my Windows boxes, just in case my main box is busy compiling, or I'm not near any linux boxes, and I need to do something in a linux environment.
And you can build Android from source using a WiBu installation, I posted directions in the Building Your Own ROM thread at AC. Just be sure to set the virtual space as large as possible on your machine. If you can't set it to at least 50gig, I would recommend editing the config files so you can (google it).
I did a full install of ubuntu on a couple old pc's I've had.
edit never mind figured it out
cdunkle584
Member
Oh good. I was having problems with the battery icon. I will check out the new version immediately.
Edit: OK, still having the same problem. The battery icon is replaced with an android bug. This may be due to my older style screen, I am really not sure. I can provide a screen shot if it will help any.
Going back to Green for now.
Edit: Decided to stay blue (I like blue!), just changed the Battery Status Style from Icon to Percentage. That works.
cdunkle584
Member
I am on the most recent build of JerryScripts BACKside, currently running the gm blue theme. It has been working fine until just a few minutes ago. Note that I just flashed the gm blue (after clearing cache and dalvik cache).
I run entirely on wifi, the phone is not activated.
I am sitting right in front of my wireless router, showing a full set of bars on my wireless. In settings, it shows connected.
Nevertheless, my browser crashes when opened, Marketplace insists there is no connection, so does Appbrain and GetJar. I tried rebooting, no change. I am going to try going back to Green Machine. Will post an update.
Any help greatly appreciated.
c
I run entirely on wifi, the phone is not activated.
I am sitting right in front of my wireless router, showing a full set of bars on my wireless. In settings, it shows connected.
Nevertheless, my browser crashes when opened, Marketplace insists there is no connection, so does Appbrain and GetJar. I tried rebooting, no change. I am going to try going back to Green Machine. Will post an update.
Any help greatly appreciated.
c
benslgdroid
rockstar
Icon should work without problems. Percentage is basically the same though.
Theme should not affect that at all. Try resetting your wireless router.
Also, the most recent build meaning the 1/20 build? 1/18 had a faulty wifi kernel
cdunkle584
Member
You are correct inasmuch as the theme *should* not affect that at all. In fact, the problem arose right after flashing the new theme, and when I went back to Green Machine everything worked fine. I always check the last thing I did before it stopped working, and usually that is the problem.
My suspicion is that the theme was developed for the later version of the OV. Too bad, really. I do like blue. The Green Machine is great though, I haven't found anything I like better in terms of layout and design. JerryScript did as great a job on that as he has the BACKside ROM. Great work all around.
The theme cannot be created for a later version of the phone. It doesn't matter in UOTkitchen. Maybe you had a bad flash? or a bad d/l?
83thomas
Member
Jerry -
Are you going to add the changelog to the BacksideUpdater app? (I haven't used it yet, so it might already be there...)
It would be nice to see what's changed within the app without having to check this forum post.
I updated to the latest rom yesterday. HUGE improvement in speed (I think my last rom upgrade screwed up something that slowed down my phone).
Everything seems to be working perfectly. Keep up the good work.
Are you going to add the changelog to the BacksideUpdater app? (I haven't used it yet, so it might already be there...)
It would be nice to see what's changed within the app without having to check this forum post.
I updated to the latest rom yesterday. HUGE improvement in speed (I think my last rom upgrade screwed up something that slowed down my phone).
Everything seems to be working perfectly. Keep up the good work.
JerryScript
Android Expert
Yes, the changelog is already a part of BacksideUpdater.
JerryScript
Android Expert
I found these instructions. Downloaded boot_screen_log_creation_package. Created my image in Corel PhotoPaint and saved as png. Put it in the RLE folder. Open command window in RLE folder and convert_image_to_rle.bat logo.png. And always get this error.
I'm trying to use this for my boot image. Sized to 320x480
Does it have to be saved as a png with any special parameters? Does this converter work with win 7 64? What is the meaning of life? Am I asking too many questions?
You may want to hold off for a bit. Blarf just added PNG support to the bootlogo function. I'm going to pull the change in for my next build.
https://github.com/inferiorhumanorg...mmit/10d08bdc705c86e9ad263f1b9db0dd2f90046f10
Blarf is still the man!
Atma
Extreme Android User
Thanks for the heads up and thanks to Blarf!
I really like your Backside Updater. What is the possibility in a future build to have it check the MD5 checksum after downloading and alert if there is a problem?
JerryScript
Android Expert
That's near the top of my todo list for the updater
To Do:
-Add downloads as internal feature using async so as not to lock up the gui
-Add md5sum check to insure against corrupt downloads
-Add list of IHO ROMs and available versions, plan on using simple github text page for manifest
-Add option to wipe/flash automatically
-Add menu options such as show current changelog, show update history, etc
-Make it look nicer
brotherswing
Android Expert
Very nice. I look forward to more refinements in the updater.
NoPartyHats
Lurker
I've got an issue when I try to launch the ROM.
I flashed it and whatnot, it installed apparently, and when it gets to the green android guy with the circle thing, it'll just loop a bit then freeze.
I'm not sure what to do, really. I'm new to this.
I flashed it and whatnot, it installed apparently, and when it gets to the green android guy with the circle thing, it'll just loop a bit then freeze.
I'm not sure what to do, really. I'm new to this.
JerryScript
Android Expert
Sounds like one of the following happened:
-- You are coming from a different ROM, and you forgot to format boot, system, data, and cache
-- You got a bad download of the ROM and forgot to check the md5sum first
-- There was a problem during flashing (it can happen)
Solution: Go back into recovery, wipe cache and dalvik cache, under mounts format boot, system, data, and cache, then flash the ROM, then flash gapps, then reboot.
If you still get stuck with a frozen bootanimation, then the issue was most likely a bad download of the ROM. In that case, you'll have to use ADB to push a good copy of the ROM to your sdcard (check the md5sum), then do the above.