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

Root GingerShedBread/GSB


v1.8.1 Fixes
Added notification profile support
camera: Add sliders for contrast/saturation/sharpness
camera: Raise YouTube duration to 15 minutes
Add BOARD prefix to AVOID_DRAW_TEXTURE_EXTENSION
Improve 2G/3G speed
ADDED 2D Gallery to build, 3D is still there
REMOVED Mau5 theme to make more space, search for "CM7 themes" in market to grab it
Cleaned up build.prop a bit

can someone explain what exactly does build.prop do?

I'm having a hard time going back and forth between xtr's clear lockscreen and the 2.3 lockscreen. I used to love it, but i absolute can't stand anything but clear now. for that matter, I wouldn't mind dispensing with xtr's 'slider' entirely and just using menu/trackball unlock.
 
I'm having a hard time going back and forth between xtr's clear lockscreen and the 2.3 lockscreen. I used to love it, but i absolute can't stand anything but clear now. for that matter, I wouldn't mind dispensing with xtr's 'slider' entirely and just using menu/trackball unlock.

That's funny. I think that showing things on a display that do nothing when you touch them (unless they are obviously grayed out) is terrible UI. The first thing that I do with xtrROM is add a background to the lock screen, just to hide what's behind it while the lock is visible. In fact, I really liked Tainted Tenzo when I tried it last month but could not use it because you had the transparent lockscreen with no way to change it (unless you use metamorph, which is too hacky for me.)
 
well its friday night so I decided to flash 1.81. and froze on the skaters for the first time I can remember. blegh.

edit: hell, this is annoying. third wipe and still nogo. I guess I have to nand back, redownload and hope for the best?

That's funny. I think that showing things on a display that do nothing when you touch them (unless they are obviously grayed out) is terrible UI. The first thing that I do with xtrROM is add a background to the lock screen, just to hide what's behind it while the lock is visible. In fact, I really liked Tainted Tenzo when I tried it last month but could not use it because you had the transparent lockscreen with no way to change it (unless you use metamorph, which is too hacky for me.)

on occasion I like to see whats behind it without unlocking the phone. the best example is beautiful widgets. Its really useful widget, so simply tapping the end key and seeing time, weather, and graphical battery is really important to me.

it absolutely confuses the hell out of most people "wheres the slider?!" but its just a personal preference thing.

widgetlocker would be a great workaround but its just too heavy on the resources for me.
 
can someone explain what exactly does build.prop do?

thrawn86,

I thought that this would be a really easy question to answer... I know what I think it contains and does, but I had a really hard time finding a resource that adequately or exactly explains what it is...

There's a ton of sites talking about all of the edits and changes you can make to the build.prop file, but its pretty hard to find one that actually defines it.

I would define it as a file that contains phone/device (and even ROM)-specific properties. These values are referenced and modified by the O/S to affect the phone's behavior.

These values can be retrieved and inspected via command-line utilites like the getprop command (for the ROMs that include/support it):

# getprop (will display all build.prop property values)
# getprop ro.serialno (display your phone' serial #)
# getprop ro.product.model (display your phone's model)

There's also a corresponding setprop command to change these values.

There are also system functions (APIs) for programmatically doing this.

The sites that I mentioned above typically have you pull the build.prop file from the phone and edit it externally and then (carefully) replace it after modification. You should use all due caution (read "take a Nandroid backup") when/if you ever decide to edit your build.prop file since you can really goober-up your system.

Cheers!

References: Configuring a New Product | Android Open Source
 
cool, thanks.

I guess I was interested why he would mentioned "cleaned up build.prop" when it doesn't seem like it would affect the phones performance.
 
cool, thanks.

I guess I was interested why he would mentioned "cleaned up build.prop" when it doesn't seem like it would affect the phones performance.

Yeah, he might have just gotten rid of property entries that weren't relevant or appropriate to his ROM... I'm sure that the ROM devs borrow/trade/share/re-use files like this when crafting their new works, so there's undoubtedly some entries that are not needed.

I still have a Nandroid backup of GSB 1.6 that I'm going to restore now that the March 2011 OTA has been captured (still no joy on my phone though :p), so I'll try to save-off the build.prop file before I upgrade to 1.7 or 1.8, compare them, and report back what he cleaned-up.
 
What does it include?

The OTA or workshed's changes?

Heck, here's both:

First, the OTA info:

http://support.vzw.com/pdf/system_update/eris.pdf

+ Improved Bluetooth connection performance with Mercedes-Benz E350 automobiles.
+ New Twitter authentication allows users to login to their accounts with ease.
+ The Received Signal Strength Indicator (RSSI) display, showcasing the strength of the incoming signal on the device, has been visually improved.
+ Visual Voice Mail (v1.0.19) now comes preloaded.
+ Microsoft Exchange Server 2010 calendars can now be synced with the device.
+ Videos, pictures, and audio multimedia messages can be sent and received with or without text included.
+ Videos, pictures, and audio multimedia messages sent to devices on other wireless carrier networks will be received.

Workshed's 1.8.1 change log:

GSB v1.8.1 CM7.0.0 RC1 - GingerBread (GingerShedBread)

  • Android Gingerbread 2.3.3 using CyanogenMOD 7.0.0 RC1
  • Sync'd with CM7 source & compiled on 3-4-2011
  • Conap's Unreleased CFS Kernel clocked @ 604 *I've been playing with a balance of battery life/performance and this is proving to be a nice balance.
  • Undead Call Fix by bftb0
  • 2d & 3D Gallery
  • BobClockD3 widget (green)
  • LauncherPro-0.8.3
  • CCName App by Conap (Let's you replace 'Verizon - RULE the AIR!' with whatever you would like it to say. Thanks Conap!)
  • gTabsimiClock Widget
  • Circular Battery Indicator App
  • Wallpapers are in CyanogenMOD Wallpapers
 
Has the March 2011 OTA been captured in 1.8.1?

I can't believe that much could be. Stock uses the HTC Sense framework, and GSB is using straight CyanogenMod/Android Open Source. When they get time, I am sure that Zach.xtr and Tenzomonk will be incorporating the changes into their ROMs (assuming the builds work better than July 2010 OTA that is...)
 
One problem I'm having with this rom aside from the laggyness is when I download something or do app updates I get "download unsuccessful" and a window saying "insufficient storage availiable" which is not the case. It's really annoying having to redo things 2 or 3 times before being successful. I came back to 1.8 to update to 1.8.1 from TastyBreadBuild and remembered that problem. Also after flashing the update I got a google sign in error and had to sign back in and also I get a voicemail notificantion even tho I don't have any new one's. The notification is still there even after rebooting a couple of times.
 
+ Visual Voice Mail (v1.0.19) now comes preloaded.

I don't like that idea.

How quickly we forget. VVM was always pre-installed.


One problem I'm having with this rom aside from the laggyness is when I download something or do app updates I get "download unsuccessful" and a window saying "insufficient storage availiable" which is not the case. It's really annoying having to redo things 2 or 3 times before being successful. I came back to 1.8 to update to 1.8.1 from TastyBreadBuild and remembered that problem. Also after flashing the update I got a google sign in error and had to sign back in and also I get a voicemail notificantion even tho I don't have any new one's. The notification is still there even after rebooting a couple of times.

bobcat331, do you happen to be running with cache2cache? Ever since I fresh-installed 1.8 without cache2cache I have not had that problem.

One other thing: I understand that a data wipe/factory reset is recommended for 1.8.1, even if you are coming from GSB 1.8.
 
How quickly we forget. VVM was always pre-installed.




bobcat331, do you happen to be running with cache2cache? Ever since I fresh-installed 1.8 without cache2cache I have not had that problem.

One other thing: I understand that a data wipe/factory reset is recommended for 1.8.1, even if you are coming from GSB 1.8.

I am running cache2cache and I didn't do a data/factory just a dalvik.
 
It looks like people are having issues with 1.8.1. I recall that I had a 24 hour wait before installing a new update for a reason. I'm going to have to start following my own rule.
 
updater-script fixed

Is that the fix to the issue we've been having with market updates?

I think that the updater-script was improperly clearing out the existing /system files, so if you were coming to GSB from a 2.1 ROM there would be fragments of 2.1 code still in the phone.

Again, since I started running without cache2cache after a full data wipe when I installed 1.7 = no issue with the market at all.
 
Do you think it would all go away if we didn't use cache2cache?

Or should it work now that the updater-script is fixed?
 
Back
Top Bottom