• 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

I had to reboot my phone to get the time to update.

@Jerry - Could the updater also handle themes?

Interesting. I have BeWeather widget on my homescreen, it had the correct time, but my status bar clock was off. Rebooting the phone fixed it. I am not sure why the widget got the right time without checking the phone.
 
Might be how the app polls the time signal from the network. A weather widget will communicate with it's servers to get current weather conditions, and thus display the correct time. The clock, on the other hand, would only poll the network when the phone is first started. Therefore the clock might have missed the change when the weather widget caught it. I honestly don't know, I'm trying to reason it out....
 
i wanna install this on my old OV. its not a new one i think. I bought it a month or so after it launched originally. its running Xionia CWMA 1.2518.6.
i havnt touched the phone since the MT came out. do i have to put a new clockwork to install backside?
 
i wanna install this on my old OV. its not a new one i think. I bought it a month or so after it launched originally. its running Xionia CWMA 1.2518.6.
i havnt touched the phone since the MT came out. do i have to put a new clockwork to install backside?
The best recovery for the BACKside right now is the VM670NH_recovery.img, also known as the Bob Zohme modified CWMod recovery. You can find it in the All Thing's Root Guide.
Since you have a Novatek screen you might want to put the Xionia recovery v1.2518.4 in a zipped form on the root of the SD card in case you ever get into a recovery loop. It has an option in the Advanced section to fix a recovery loop. It can be found in the Root Guide as well.
 
I am about to change the recommendation for recoveries. Drewwalton's touch recovery is an amazing piece of porting. I've been using it for a week now, and haven't found any bugs. All reports are that it works fine on old and new screens.

It makes things easier imho, and I like the blue. ;)

Edit: anyone who wants a sneak peak at the new BacksideUpater, and is willing to test and report bugs quickly (I'm posting a new build tomorrow). here it is, download and then:
Code:
adb remount
adb push PATH_TO_DOWNLOADED_FILE /system/app/BacksideUpdater.apk
Or root capable file manager - move the file manually.

Then test it out. Couple of new goodies in the menu. ;)
 

Attachments

I'll let you know how it works!
Thanks, a few notes:

--once you select a version, it's changelog and other variables (md5, url, name, size, etc, etc) are loaded into the system for all other functions

--recovery flashing error messages are non-sensical, at least in the way they are returned to the app, so bear with me ;)

--the easter egg has bugs, so it's disabled (actually removed) for now
 
I really like the change log viewer, but the green on black is a bit much to look at. I have 20/20 vision and it makes my eyes squirrelly after a few lines.

Other than that, it's brilliant.
 
Hey Jerry. i have a few questions. Do you use Java to "edit" this ROM? And i want to become a programmer. I have some knowledge on Visual Basic and C#. What language do you stronly suggest i learn? I want to develop Desktop Applications but i dont really want to continue with Visual Basic and C# because it is not multi-platform.
 
After having running the 1-31 build flawlessly for a few weeks, a few problems came up. The phone would not stay overclocked if I rebooted it. No matter what settings I put it at or whether or not I checked "apply on boot." I was also getting a ton of freezes that required a battery pull to fix. I finally got annoyed enough today to update to the most current rom. Everything is back to working perfectly. Thanks jerry!
 
The best recovery for the BACKside right now is the VM670NH_recovery.img, also known as the Bob Zohme modified CWMod recovery. You can find it in the All Thing's Root Guide.
Since you have a Novatek screen you might want to put the Xionia recovery v1.2518.4 in a zipped form on the root of the SD card in case you ever get into a recovery loop. It has an option in the Advanced section to fix a recovery loop. It can be found in the Root Guide as well.

What if you have the Hitachi screen? Is there a way to prevent boot loops?
 
Hey Jerry. i have a few questions. Do you use Java to "edit" this ROM? And i want to become a programmer. I have some knowledge on Visual Basic and C#. What language do you stronly suggest i learn? I want to develop Desktop Applications but i dont really want to continue with Visual Basic and C# because it is not multi-platform.
Java is a good point to start for desktop apps, from there, it will depend upon the application in question which language you should use.

The most important thing is to get a good handle on the programming concepts. They are carried through most languages in one way or another. Once you do that, it's just a matter of learning the syntax for each language, and getting a grip on the individual languages oddities. Most programmers don't consider themselves a programmer of a specific language, though they may focus on one or two. We all have our cheat sheets and idiot books for looking up what we need on-the-fly, and this gives us freedom from being stuck to a single languages. For example, android develpment requires both java and c, though most of my work is concentrated on the java side, while the kernel devs work with c. ;)
 
I figured java would be a good starting point, since it's basically "diet C++." Half the trash collection, same great syntax! Almost everything you learn in java directly applies to C and C++.
 
What if you have the Hitachi screen? Is there a way to prevent boot loops?

Best way to prevent is not do something dumb, like I did using factory reset in privacy menu and wrong recovery. :D Old age, what can ya do.

Best way to get out of it, put this Xionia recovery 12518.6.zip on your sd card. Guard it with your life. It may save your buttocks some day if you're stuck in a recovery loop. (like it did mine) If you're stuck at a black screen, find AndyOpie's tut for using Droid@screen.
 
Java is a good point to start for desktop apps, from there, it will depend upon the application in question which language you should use.

The most important thing is to get a good handle on the programming concepts. They are carried through most languages in one way or another. Once you do that, it's just a matter of learning the syntax for each language, and getting a grip on the individual languages oddities. Most programmers don't consider themselves a programmer of a specific language, though they may focus on one or two. We all have our cheat sheets and idiot books for looking up what we need on-the-fly, and this gives us freedom from being stuck to a single languages. For example, android develpment requires both java and c, though most of my work is concentrated on the java side, while the kernel devs work with c. ;)

Thanks a million! Java it is!
 
Back
Top Bottom