Atma
Extreme Android User
The BACKside updater will download the update for you and it will check the MD5 checksum to make sure the download isn't corrupt. You will still need to go through the steps of flashing yourself. Recovery, wipe cache, etc.
-
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
The BACKside updater will download the update for you and it will check the MD5 checksum to make sure the download isn't corrupt. You will still need to go through the steps of flashing yourself. Recovery, wipe cache, etc.
Aha, thanks for clearing that up for me!
It's quite simple. Just click BACKside updater and if a newer version of the ROM is out there will be an option to download. Once you download just check the md5 sum in the updater and if it says it matches you can press the reboot into recovery button. It's very simple and intuitive. Jerry made it painfully easy.
Edit: I guess I should have refreshed earlier and seen that your question was answered haha
benslgdroid
rockstar
Also it can't be stickied as it is unique to backside. Thanks to Jerry for all his hard work
Atma
Extreme Android User
I forgot to tell you. It will download it to the download folder on your phone. When you select 'choose zip to install', that's where you need to look.
I wanted to report back with another curious issue I ran into. For some reason, my phone wasn't charging today while at work. I swapped out cables, moved between USB ports and a wall charger, and also verified other devices charged properly. Out of curiosity, I rebooted the phone while carefully making sure not to move anything. Lo and behold, the phone booted up and started charging and hasn't had any issues since. Not sure if anyone else is experiencing similar issues, but I wanted to throw it out there in case someone else ran into it. Now that I know I can just reboot if I run into the problem again, it shouldn't be a big deal.
JerryScript
Android Expert
On the screen freezes due to rotations, I may have to remove the ICS rotation animations till they work the bugs out of the Gingerbread port. Till then:
-- Settings>>Display>>Auto Rotate (uncheck)
-- Settings>>ADW Launcher>>System Preferences>>Home Orientation>>(Don't choose Auto/sensor)
If you choose to keep these enabled, and your screen freezes:
-- Short press the power button to lock screen (it may not appear locked)
-- Perform your usual unlock gesture, be it with the slide rings, unlock pattern, or actual gestures.
-- When you feel the haptic feedback for unlocking, rotate your phone 90 degrees then back.
If CM doesn't have a working fix by the end of the week, I'll remove them altogether.
-- Settings>>Display>>Auto Rotate (uncheck)
-- Settings>>ADW Launcher>>System Preferences>>Home Orientation>>(Don't choose Auto/sensor)
If you choose to keep these enabled, and your screen freezes:
-- Short press the power button to lock screen (it may not appear locked)
-- Perform your usual unlock gesture, be it with the slide rings, unlock pattern, or actual gestures.
-- When you feel the haptic feedback for unlocking, rotate your phone 90 degrees then back.
If CM doesn't have a working fix by the end of the week, I'll remove them altogether.
DonMiguel
Newbie
Ok I updated to the newest version from the previous. Quick question, how come I went from having 101mb of internal storage free to only have 30mb? Also It seems this is effecting the speed of my phone as some apps are now loading slower and swiping through homepages is choppy/sluggish.
JerryScript
Android Expert
Read the previous two pages for details on why you have less space.
It shouldn't cause your apps to run any differently, and swiping should smooth out once the phone is fully booted (first two bootups are rebuilding dalvik cache files, so it takes a good 10 minutes and a couple of reboots to smooth things out). If you continue to have issues after a reboot or two, let us know.
brotherswing
Android Expert
Not much new work done on my apk themes these past few days, but someone...
Might let me get back to work. Don't let the smile fool you, he's never a happy baby.
Might let me get back to work. Don't let the smile fool you, he's never a happy baby.
JerryScript
Android Expert
Well of course he's not. He's up late being a ladies man, so he's always grumpy!Not much new work done on my apk themes these past few days, but someone...
Might let me get back to work. Don't let the smile fool you, he's never a happy baby.
But at least these are the days he wont hold a grudge more than a few seconds, enjoy them!
JerryScript
Android Expert
Edit: didn't work yet 
DonMiguel
Newbie
Read the previous two pages for details on why you have less space.
It shouldn't cause your apps to run any differently, and swiping should smooth out once the phone is fully booted (first two bootups are rebuilding dalvik cache files, so it takes a good 10 minutes and a couple of reboots to smooth things out). If you continue to have issues after a reboot or two, let us know.
Ok the swiping is good to go now, and I guess the apps running slower was all in my head or that smoothed itself out as well. I read that I will loose 40mbs internal storage with the update but why did I loose around 70mbs?
New member. I just wanted to thank Jerry and everyone who has contributed for providing this fantastic resource. I have successfully flashed BACKside on my OV and couldn't be happier. Thank you for all of the time you have spent on this project and making it available for everyone to enjoy. Cheers!
benslgdroid
rockstar
It's based on the amount of apps and how they allocate memory like lib file size app size, dalvik, all that stuff. So there is no set amount what you will lose because the memory is handled differently now.
Atma
Extreme Android User
DonMiguel
Newbie
Sounds like a maps issue, since it's happening to you on both 2.2.1 and 2.3.7, so you might want to report it to Google Maps. They are responsive. I reported an issue with a single 1/2 mile pedestrian path not being recognized as a bike route (in Nevada, all pedestrian paths are legal for bikes and e-bikes). It took them about two weeks to respond, but they did acknowledge the issue, and about 5 months later, they emailed me to let me know the issue was resolved. Pretty good support for a single 1/2 mile stretch of trail that isn't even used that often!
Edit: Let me know if the next build (coming shortly) makes any difference. There's the possibility it is related to the screen rotation bug, which there is a fix for in the new build. Though the fact it happens on 2.2.1 makes me think it's Maps.
Yeah, thanks, I thought so, too... so I actually did report it about 5 days ago. That *is* pretty impressive, and good to know.
Well, I've got nothing but bad news here, I'm sorry to say. Both issues still exist for me in 02122012, and I have also noticed 3 apparently random reboots since the upgrade. For giggles, I flashed the Quicksilver theme - full animation and screen rotation both on - no more screen issues. Just had another random reboot a few minutes ago, however, and I happened to be looking at the screen. Suddenly it went dark and threw a message like "Shutting down." But I wasn't even touching it; I had set it down a minute prior.
JerryScript
Android Expert
If you are overclocking, try backing it down a notch.Yeah, thanks, I thought so, too... so I actually did report it about 5 days ago. That *is* pretty impressive, and good to know.
Well, I've got nothing but bad news here, I'm sorry to say. Both issues still exist for me in 02122012, and I have also noticed 3 apparently random reboots since the upgrade. For giggles, I flashed the Quicksilver theme - full animation and screen rotation both on - no more screen issues. Just had another random reboot a few minutes ago, however, and I happened to be looking at the screen. Suddenly it went dark and threw a message like "Shutting down." But I wasn't even touching it; I had set it down a minute prior.
Otherwise, the option to fix permissions in TitaniumBackup or in recovery usually clears those types of issue up.
nitestalkr
Android Enthusiast
GUI still gets stuck at times, but not as often as previous build, there are a few performance issues in this build, freezes and force closes occur more often than last 3 or 4 builds, virtual keyboard doesn't stretch in landscape mode sometimes(only happens with non-native keyboard app i believe.if this happens, re-enable selected keyboard, or uninstall and reinstall keyboard. ) had a few random reboots(haven't seen that in a few months), average battery drain has been noticeably increased(for me at least, even though I have decreased my phone usage). And I believe that's about all I have to report for this build.
JerryScript
Android Expert
Thanks for the feedback!
Sounds like you might be at a point where fixing permissions will help. I do it in Titanium Backup, but you can also do it via recovery. Usually clears up FCs and random reboots not caused by overclocking.
nitestalkr
Android Enthusiast
Thanks for the feedback!
Sounds like you might be at a point where fixing permissions will help. I do it in Titanium Backup, but you can also do it via recovery. Usually clears up FCs and random reboots not caused by overclocking.
Thanks for the fixing permissions tip, I will do so via recovery, and report back if I notice any difference.
brotherswing
Android Expert
Major update to Quicksilver, incorporating suggestions from the community. Much more elegant, I'm very happy with how it turned out this time.
rooter1
Well-Known Member
Jerry, could you please elaborate on how to do this via Titanium Backup? I'm running the pro version of 4.7.7.1 and can't seem to find a fix permissions option? Thanks!