• 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

  • Market issues fall into three categories:

  1. Insufficient space -- You can use links2sd, apps2sd, TitaniumBackup's dalvik integration feature (not free, but very good), remove 01mvdalvik and wipe market cache and reboot, or backup seldom used apps and restore them only when needed
  2. Signing errors -- Most often caused by various *2sd scripts not being reverted before flashing the ROM. Can be solved by either following the appropriate *2sd instructions for upgrading a ROM, or flashing gapps each time you flash a new ROM build.
  3. Invalid Package errors -- Most often associated with updates, can be anything from a bad download to an app having been installed on a previous ROM and restored to the current one. Try uninstalling then redownloading and installing the newest version.

  • @nitestalkr:I will look into the font idea, however, it's easier said than done. Resource files such as fonts are compiled into the build, changing them may be harder than just linking to them, especially without a performance hit


  • @Prometheus: I don't like the arrows on the lockscreen rings either. I'll probably revert to the clean ones in the next build. I mean really, what's the point? BTW- they were added by CM, not IHO. ;)


  • @brotherswing: I was blown away by that shot by Cassini. I wish there was a HD video recorder on board with a high framerate. Imagine some of the screen-grabs, the visuals would be awe inspiring. Of course, transmitting would take years, and leave no bandwith for science, so I'm just happy they got lucky with that shot!
 
hey jerry, i have a nice lil suggestion for a future build, if its possible that is, the ability to scan the sd card for font packs, and using said font as the system font. the ability to be able to change system font, throughout the phone, would be a nice feature.loving the new update, although my phone has froze twice, and then rebooted itself.. something that i havent experienced since an early september build.. not that big of a deal, it hasnt happened since. keep up the good work, and hope you give my suggestion a little thought.
Try:
https://market.android.com/details?id=net.pixelpod.typefresh&hl=en ;)
 
I have the Hubble Space Telescope app. It's got some incredible pics that are mind blowing.


You sir, have piqued an interest in me that has gotten buried beneath working 6 days a week and the stresses of having a new apartment on my own. I downloaded that app and have been staring at the images on my tablet lol. They are very mind blowing indeed, especially the one with hundreds of galaxies in one shot. I love astronomy. I can't thank you enough lol :)
 
Sometimes the top notification bar won't load. Even if I drag it down, it remains invisible. The date does appear when I drag it down however.

Also, anyone know if there's a way to make Link2SD auto-link when I restart my phone, so I don't have to do a UI restart.
 
Sometimes the top notification bar won't load. Even if I drag it down, it remains invisible. The date does appear when I drag it down however.

Also, anyone know if there's a way to make Link2SD auto-link when I restart my phone, so I don't have to do a UI restart.
For the notification bar, did you flash Green Machine? No theme? A different theme?

In link2SD, click menu-more-recreate mount scripts, then reboot.
 
For the notification bar, did you flash Green Machine? No theme? A different theme?

In link2SD, click menu-more-recreate mount scripts, then reboot.

I have no added theme.

Also, when I try to re-create the mount script it says...
"Mount script can not be created. mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: Device or resource busy."
 
ok so I have horrible battery life 1-2 weeks after an update. somebody on here mentioned an app that keeps track of battery usage but I can't seem to find it. would somebody mind posting a link?
 
I have no added theme.

Also, when I try to re-create the mount script it says...
"Mount script can not be created. mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: Device or resource busy."
You, my dear friend, have a bad SD card. You could try putting the card into a PC, copying everything over, then repartition the card. Copy everything back, then try again. Or just try a different card. I'd upload a spare for you if technology would allow....
 
Or if you know anyone with a Mac, there are very good tools available to attempt to repair your sdcard. Windows has some options too, but not nearly as good, and though I'm sure Linux has even better tools, I'm not familiar enough with them to say.
 
Or if you know anyone with a Mac, there are very good tools available to attempt to repair your sdcard. Windows has some options too, but not nearly as good, and though I'm sure Linux has even better tools, I'm not familiar enough with them to say.
True statements on all points, but the thing is, those tools are best used to retrieve valuable data from a dying card. When a card starts losing blocks that way, it typically gets progressively worse. SD cards are cheap enough, even in this economy, you can find them for around ten US dollars. You can just use some good disk utilities to revive the card. You should invest in a new one. I am not a commissioned salesperson. ;)
 
You, my dear friend, have a bad SD card. You could try putting the card into a PC, copying everything over, then repartition the card. Copy everything back, then try again. Or just try a different card. I'd upload a spare for you if technology would allow....

Or if you know anyone with a Mac, there are very good tools available to attempt to repair your sdcard. Windows has some options too, but not nearly as good, and though I'm sure Linux has even better tools, I'm not familiar enough with them to say.

I can still link apps, can still use them, I just need to do a soft reset after a hard reset.
 
Also, when I try to re-create the mount script it says...
"Mount script can not be created. mount: mounting /dev/block/vold/179:2 on /data/sdext2 failed: Device or resource busy."
Wait a second,.....(House moment)...it's not the card. It's something locking access to the device, not a write failure. Try clearing up the 2nd partition, followed by wiping link2sd's cache. After that try recreating the mount scripts.
 
Wait a second,.....(House moment)...it's not the card. It's something locking access to the device, not a write failure. Try clearing up the 2nd partition, followed by wiping link2sd's cache. After that try recreating the mount scripts.
in terminal or adb shell,
Code:
umount -l /dev/block/vold/179:2
to free the partition access ( the -l means "lazy" unmount)
then recreate the script.
 
just flashed the new 12072011 backside rom and the quicksilver ics remix theme and ive been getting random reboots?? and then adw launcher forces closed....

any reason for this??
 
What ROM did you come from? Are you overclocking? Did you follow every step in Jerry's original post? Did you flash the theme right after flashing the ROM, or did you run a couple of reboots first?
 
Wait a second,.....(House moment)...it's not the card. It's something locking access to the device, not a write failure. Try clearing up the 2nd partition, followed by wiping link2sd's cache. After that try recreating the mount scripts.

Format 2nd partition VIA computer?

in terminal or adb shell,
Code:
umount -l /dev/block/vold/179:2
to free the partition access ( the -l means "lazy" unmount)
then recreate the script.
Access denied. :/
 
Back
Top Bottom