• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root *BACKside ROM Themes* Post your BACKside ROM themes here!

What color theme would you like to see created?


  • Total voters
    44
Where? Sorry... I seriously have a hard time keeping up with everyone's links or where they keep screenies and downloads.

Just an FYI for anyone interested; you can put up a small web site on Dropbox that includes your screenies and downloads. Here is an example of how I did my guilds policies web site on my Dropbox. As long as you don't require any databases and you have html/css skills, a web site on Dropbox is a breeze. This way you can just give out your link in your posts.


Wherever I posted the link is where the screens are
 
Corsair

A blue variant of my Agent Orange theme (with some slight tweaks), by request. I have plans for this theme, and it will continue to evolve as I update it for future builds.
As always, feedback is welcome.

Screenies

screenshot-1323835069742.png


screenshot-1323835116129.png


screenshot-1323835078547.png


Wallpaper and icons from y0rk's Blue ADW theme, widget is Fancy Widgets with the Ice Cream Sandwich skin by NYkrinDC.

Download
Corsair
Corsair 0417
 
  • Like
Reactions: G19
Quick note to whom ever tried Agent Orange, I messed up the location of the boot animation. If you have installed the original version, you will need to use Root Explorer (or something of that ilk) and go to /data/local to delete bootanimation.zip if you want to change it. Flashing a new theme will not fix this. I'm re building Agent Orange with the correct location, just wanted to give fair warning and the fix.
 
Thanks so much! How hard is it to make one of these themes?
Dead simple, really. Just go here, and have fun with it. I'm pretty excited because I just learned how to cook up boot animations from scratch. Now I'm trying to hack them into a UOT theme. If it works, I won't be as limited in my options. :D My inner nerd is giddy right now!

Edit: Yup, figured out how to stuff my own boot anims into UOT themes. Future builds are gonna get pretty wild!
 
Dead simple, really. Just go here, and have fun with it. I'm pretty excited because I just learned how to cook up boot animations from scratch. Now I'm trying to hack them into a UOT theme. If it works, I won't be as limited in my options. :D My inner nerd is giddy right now!

Edit: Yup, figured out how to stuff my own boot anims into UOT themes. Future builds are gonna get pretty wild!

Thank you for the info. I have been playing with it but cannot find systemui.apk. Where do I find this file?

I was able to find framework-res.apk on my sd card under system, but cant find systemui :/

EDIT:: Update:: Found it!
 
I save all my settings.uot files, if you'd like to take a crack at a remix of one of my themes, just let me know. Can't wait to see what you cook up.
 
That sucked... Got a SHTF error. All that *work* for nothing

UOT-12-14-05-38-1

Thats my fail.. lol
 
Quick status update on the theming mods:

-- Status Bar Color Chooser: Only changes color on reboot, transparency only takes effect when other things change the status bar, getting close to a fully working mod

-- Overscroll & Edge Glow: Seems to be working fine, but needs extensive testing due to bug reports on other phones that use a similar mod, almost done testing

-- Custom Carrier Label: done and in latest build

-- Center Status Bar Clock & Choose Color: done and in latest build

Please let me know what other theming options you would like, and I'll do my best to build them into the ROM. Since ICS is coming, I don't feel the need to keep inline with CyanogenMod anymore. Time to make BACKside our own. ;)

Why are these taking so long? -- The debugging process is slow! You get a flashable build (if lucky), test it, find a bug. Go back to the code and search for the bug, fix it, build again, flash it, test it, find another bug. Each time you build takes from 45 minutes to 1 1/2 hours. Then once everything seems to be working, you have to do a clean build just to make sure everything is kosher. So to fix a single misplaced comma in a line of code could take a total of over a day of debugging and rebuilding.
 
Quick note to whom ever tried Agent Orange, I messed up the location of the boot animation. If you have installed the original version, you will need to use Root Explorer (or something of that ilk) and go to /data/local to delete bootanimation.zip if you want to change it. Flashing a new theme will not fix this. I'm re building Agent Orange with the correct location, just wanted to give fair warning and the fix.

I downloaded the original one and cannot seem to find the file you're talking about to delete.

I'm using the file manager that's built into the rom to search the folders. If this is not going to work is there a free alternative I can download from the market?
 
Time to make BACKside our own. ;)
You Rock!

Why are these taking so long? -- The debugging process is slow! You get a flashable build (if lucky), test it, find a bug. Go back to the code and search for the bug, fix it, build again, flash it, test it, find another bug. Each time you build takes from 45 minutes to 1 1/2 hours. Then once everything seems to be working, you have to do a clean build just to make sure everything is kosher. So to fix a single misplaced comma in a line of code could take a total of over a day of debugging and rebuilding.
And that's why I don't do any real coding!
 
I downloaded the original one and cannot seem to find the file you're talking about to delete.

I'm using the file manager that's built into the rom to search the folders. If this is not going to work is there a free alternative I can download from the market?
I used ES File Explorer (note, you need to go into settings in ES to enable root access.) I use this one because it can browse LAN shares, a must have for me. After you get root with ES, tap the star in the tool bar. Select "phone", now instead of starting in the root of your SD card, you're looking at the root of the file system. I'm sorry you got caught by my mistake, but I'll help you fix it.
 
I used ES File Explorer (note, you need to go into settings in ES to enable root access.) I use this one because it can browse LAN shares, a must have for me. After you get root with ES, tap the star in the tool bar. Select "phone", now instead of starting in the root of your SD card, you're looking at the root of the file system. I'm sorry you got caught by my mistake, but I'll help you fix it.

Thank you. Got it deleted.
 
What settings(if any) do you guys change on the "file upload" tab?

Got them figured out after many failed attempts. Got my first theme made up. I'll upload one of my themes sometime when I think it's worthy.
 
I don't mess with that, aside from changing the preview to MDPI. Glad you fixed the Agent Orange gaff. My download stats showed only two user had downloaded that version, and I knew you were one. I just hope the other user who downloaded it sees the post with the fix. My mistake was I had the ROM type set for a Sense ROM, not Cyanogen. Like Jerry pointed out, one little oversight can lead to many hours of troubleshooting. It took me about two hours to figure out what I'd done wrong, and how to fix it.
 
  • Like
Reactions: G19
One thing I like to keep at HDPI is the lockscreen mods. I presonally don't like the MDPI lockscreen icons being so small inside the rings. Using the HDPI setting makes them fit much better inside the rings IMHO. ;)
 
I don't mess with that, aside from changing the preview to MDPI. Glad you fixed the Agent Orange gaff. My download stats showed only two user had downloaded that version, and I knew you were one. I just hope the other user who downloaded it sees the post with the fix. My mistake was I had the ROM type set for a Sense ROM, not Cyanogen. Like Jerry pointed out, one little oversight can lead to many hours of troubleshooting. It took me about two hours to figure out what I'd done wrong, and how to fix it.


Thanks for doing all the trouble shooting and for helping me with the fix.
 
One thing I like to keep at HDPI is the lockscreen mods. I presonally don't like the MDPI lockscreen icons being so small inside the rings. Using the HDPI setting makes them fit much better inside the rings IMHO. ;)

I left everything as hdpi. I thought that's the type of screen we have. guess I was wrong. I was wondering why the unlock screen sliders appear so large
 
wow you guys, this thread's been popular lately :D Quick question for you other themers: after you download your freshly made theme, do you replace the update-binary file of the theme with the update-binary file from the corresponding BACKside build before calling it done and uploading it? If this sounds completely nuts to you, I'll explain:
The 1st time I ever made something in the kitchen (i think it was my 1st statusbar transparency mod), I tried to flash it and got that "error 0" or "status 0" or whatever that error is. Went to the kitchen page, and it suggested replacing the update-binary, which I did, and it worked. Everytime since then, I've assumed I would get the error unless I did it, so rather than flash every theme just to find out, I automatically replace it. I've never seen anyone mention this extra step, so I stated thinking "gee, maybe I don't need to do this anymore"...but I don't want to cause errors for ppl using my themes.

SO, has anyone else needed to do this, or do I just waste alot (well, not alot really) of time?
 
Quick status update on the theming mods:

-- Status Bar Color Chooser: Only changes color on reboot, transparency only takes effect when other things change the status bar, getting close to a fully working mod

-- Overscroll & Edge Glow: Seems to be working fine, but needs extensive testing due to bug reports on other phones that use a similar mod, almost done testing

-- Custom Carrier Label: done and in latest build

-- Center Status Bar Clock & Choose Color: done and in latest build

Please let me know what other theming options you would like, and I'll do my best to build them into the ROM. Since ICS is coming, I don't feel the need to keep inline with CyanogenMod anymore. Time to make BACKside our own. ;)

Why are these taking so long? -- The debugging process is slow! You get a flashable build (if lucky), test it, find a bug. Go back to the code and search for the bug, fix it, build again, flash it, test it, find another bug. Each time you build takes from 45 minutes to 1 1/2 hours. Then once everything seems to be working, you have to do a clean build just to make sure everything is kosher. So to fix a single misplaced comma in a line of code could take a total of over a day of debugging and rebuilding.


Overscroll color Chooser?
Scrollbar color Chooser?
Font Chooser?
 
wow you guys, this thread's been popular lately :D Quick question for you other themers: after you download your freshly made theme, do you replace the update-binary file of the theme with the update-binary file from the corresponding BACKside build before calling it done and uploading it? If this sounds completely nuts to you, I'll explain:
The 1st time I ever made something in the kitchen (i think it was my 1st statusbar transparency mod), I tried to flash it and got that "error 0" or "status 0" or whatever that error is. Went to the kitchen page, and it suggested replacing the update-binary, which I did, and it worked. Everytime since then, I've assumed I would get the error unless I did it, so rather than flash every theme just to find out, I automatically replace it. I've never seen anyone mention this extra step, so I stated thinking "gee, maybe I don't need to do this anymore"...but I don't want to cause errors for ppl using my themes.

SO, has anyone else needed to do this, or do I just waste alot (well, not alot really) of time?


I never have. I've been so busy lately I haven't been able to update my themes
 
Ok, Next question: How many of you are using the stock lock screen, as opposed to WidgetLocker or similar?

If you are using the stock mlocker, which style are you using? I prefer ring myself...

I'm trying to decide if I want to include the lockscreen in my next theme, but if no one uses it, i won't bother. Likewise, if there is a style no one really uses, I don't really see a point in making it pretty.


(i was going to make this the next poll, but....erm....I can't exactly figure out how to take the existing poll down....if anyone wants to point me in the right direction, that would be much appreciated.)
 
wow you guys, this thread's been popular lately :D Quick question for you other themers: after you download your freshly made theme, do you replace the update-binary file of the theme with the update-binary file from the corresponding BACKside build before calling it done and uploading it? If this sounds completely nuts to you, I'll explain:
The 1st time I ever made something in the kitchen (i think it was my 1st statusbar transparency mod), I tried to flash it and got that "error 0" or "status 0" or whatever that error is. Went to the kitchen page, and it suggested replacing the update-binary, which I did, and it worked. Everytime since then, I've assumed I would get the error unless I did it, so rather than flash every theme just to find out, I automatically replace it. I've never seen anyone mention this extra step, so I stated thinking "gee, maybe I don't need to do this anymore"...but I don't want to cause errors for ppl using my themes.

SO, has anyone else needed to do this, or do I just waste alot (well, not alot really) of time?

In the multiple themes I've made since last night I've always had to replace that file.
 
In the multiple themes I've made since last night I've always had to replace that file.

Ah, so I'm not the only one! I wonder if it would be better (or i guess even possible) to use the Amend scripting option instead of Edify, since it says right there to use Amend if you are getting 'error 0'? I wonder if that would cause problems elsewhere? I really have no clue about different types of scripting and what have you....
 
Back
Top Bottom