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

Root GingerShedBread/GSB

The Hulu Plus announcement (not Hulu, by the way, but the subscription Hulu Plus app and service) was announced for "select phones" running 2.2, with that list of phones coming later this year, sooner to the time that the app is released. I sincerely doubt that it will run on the Eris.

That said, it may not require Flash, since there is an iOS Hulu Plus app as well, and the iOS app supposedly works in iOS 3.2 and the original iPod Touch, which has similar specs to the Eris. Though, that may be comparing apples to oranges, as iOS may have some richer APIs to program to.

So, you never know... I guess we'll just have to see.
 
I've experienced some lag myself and I'm just wondering, since I saw a few people saying they were experiencing lag after some time and 1 response to that was to periodically reboot, if using the TB option to clean up the Dalvik cache would have an effect preventing lag. With A2SD and C2C enabled I'm not sure why my gingeris would bog down at all; it has more memory available to it than it ever did before on 2.1 ROM's but a reboot did bring it back to crisp running. So, I guess there's something to it.
Also, is there a feature I'm overlooking or an app that will batch delete all the app caches from memory instead of hunting and pecking through the Settings> Applications> Manage applications route?
 
our google, who art in mountain view, open source be thy name, your custom rom come, your flash be done, on phandroid as it is in xda. Give us this day our daily gingerbread, and forgive us our rooting, as we have forgiven our boot loaders. And lead us not into ios, but deliver us from itunes.

lol! :d
 
paleodust,that is awsome! it just became my facebook status :D


I've experienced some lag myself and I'm just wondering, since I saw a few people saying they were experiencing lag after some time and 1 response to that was to periodically reboot, if using the TB option to clean up the Dalvik cache would have an effect preventing lag. With A2SD and C2C enabled I'm not sure why my gingeris would bog down at all; it has more memory available to it than it ever did before on 2.1 ROM's but a reboot did bring it back to crisp running. So, I guess there's something to it.
Also, is there a feature I'm overlooking or an app that will batch delete all the app caches from memory instead of hunting and pecking through the Settings> Applications> Manage applications route?

i dont really think its a memory issue,per say,but cleaning the caches out definately seems to help. i use cache cleaner ng,from the market. you can set it on schedules,or periodically do it manually
 
Caches should tend to make the phone faster, not slower. It's ok to clear them if they start to take up too much space, and definitely if they app starts working improperly - it could be a corrupted cache - but if you are using cache2cache I can't believe that you are running out of space. I'd say that if you are over 30 MB free in data then there is absolutely no reason to clear cache. Try leaving caches alone for a while and see if things seem better.

Clearing caches are a way to save storage space, not to speed up the phone.

Running from SD may slow things down. Not by much, but it doesn't seem the most efficient way to store apps.

Turning on JIT wil help, unless you have some old app that cannot run under JIT. Turning on compcache may help as well, though it may actually make things slower - I tend to doubt that you'd notice much of a difference, but it's worth trying out.

I've had one occasional where one of my apps was lagging pretty badly, but a reboot solved that, and it has not recurred. I've been running my phone now for three days, all is completely normal.
 
So far, this ROM has been running more smoothly and more stable than any other. I've only had to reboot when a new setting requires it or something like that.
 
Hi, Another new kid on the block. Actually a pretty old kid, but it's nice that I can still be a newbie somewhere. I've been reading several of the threads and finally worked up the courage to root my old Eris and try a couple of the roms. I think I have the root down, but I haven't had much luck with the roms. I tried Cyanogen's GSB, but the phone started looping at the "touch android to start" screen. Then I tried xtrSense and that loaded, but google apps failed. Any thoughts on where this new kid went wrong?
 
Hi, Another new kid on the block. Actually a pretty old kid, but it's nice that I can still be a newbie somewhere. I've been reading several of the threads and finally worked up the courage to root my old Eris and try a couple of the roms. I think I have the root down, but I haven't had much luck with the roms. I tried Cyanogen's GSB, but the phone started looping at the "touch android to start" screen. Then I tried xtrSense and that loaded, but google apps failed. Any thoughts on where this new kid went wrong?

Sorry to hear that. If I were in that boat, I would probably reformat my SD card and start over from scratch. You might want a second opinion on that, though.

In any case, welcome to the forum!
 
Hi, Another new kid on the block. Actually a pretty old kid, but it's nice that I can still be a newbie somewhere. I've been reading several of the threads and finally worked up the courage to root my old Eris and try a couple of the roms. I think I have the root down, but I haven't had much luck with the roms. I tried Cyanogen's GSB, but the phone started looping at the "touch android to start" screen. Then I tried xtrSense and that loaded, but google apps failed. Any thoughts on where this new kid went wrong?

What exactly did GSB do at the touch the Android screen?

When you tried to flash the gapps, did you do it right after you flashed xtrsense, meaning before you powered the phone off or rebooted?
 
Hi, Another new kid on the block. Actually a pretty old kid, but it's nice that I can still be a newbie somewhere. I've been reading several of the threads and finally worked up the courage to root my old Eris and try a couple of the roms. I think I have the root down, but I haven't had much luck with the roms. I tried Cyanogen's GSB, but the phone started looping at the "touch android to start" screen. Then I tried xtrSense and that loaded, but google apps failed. Any thoughts on where this new kid went wrong?

Did you wipe data/factory reset before you flashed the new ROMs?
 
Caches should tend to make the phone faster, not slower. It's ok to clear them if they start to take up too much space, and definitely if they app starts working improperly - it could be a corrupted cache - but if you are using cache2cache I can't believe that you are running out of space. I'd say that if you are over 30 MB free in data then there is absolutely no reason to clear cache. Try leaving caches alone for a while and see if things seem better.

Clearing caches are a way to save storage space, not to speed up the phone.

Running from SD may slow things down. Not by much, but it doesn't seem the most efficient way to store apps.

Turning on JIT wil help, unless you have some old app that cannot run under JIT. Turning on compcache may help as well, though it may actually make things slower - I tend to doubt that you'd notice much of a difference, but it's worth trying out.

I've had one occasional where one of my apps was lagging pretty badly, but a reboot solved that, and it has not recurred. I've been running my phone now for three days, all is completely normal.

clearing the caches seem to make my phone a lil less laggy. while it may slow it down a lil bit as things will have to reload,clearing the cache periodically seems to help my phone run smoother. maybe its psychological? :p i dunno. but for me it seems to help

on jit,i have run it on and off,and cant personally tell a difference in speed or smoothness either way. i tend to leave it on,since i understand 2.2(and thus 2.3) is based on its concept.

i have compache enabled and set at the max,and the vm heap size set at the max as well,and surface dithering off. tho i wont pretend i understand what any of those things mean :eek: ;)
 
Hi, Another new kid on the block. Actually a pretty old kid, but it's nice that I can still be a newbie somewhere. I've been reading several of the threads and finally worked up the courage to root my old Eris and try a couple of the roms. I think I have the root down, but I haven't had much luck with the roms. I tried Cyanogen's GSB, but the phone started looping at the "touch android to start" screen. Then I tried xtrSense and that loaded, but google apps failed. Any thoughts on where this new kid went wrong?

did you flash the gapps listed in the GSB thread immediately after flashing the rom? i experience bootloops with tazz gingerbread,but not with shedbread.
 
With A2SD and C2C enabled I'm not sure why my gingeris would bog down at all; it has more memory available to it than it ever did before on 2.1 ROM's...

Just saw this again and thought I should clear this up. There is a difference between memory and storage space. What apps2sd and cache2cache give you is more storage space - think hard disk space on a "real" computer - in one particular area of your phone - where your user apps and their data are stored. When you run an Eris, you will always have the same amount of memory, or RAM - 288 MB. I suppose that it's true that GB is a bit more RAM-efficient than Eclair, I can't believe that it is terribly dramatic.

Because the storage on an Eris is actually flash memory, you do not get the same sorts of data access slowdowns from disk fragmentation that you get on mechanical hard disk drives when disk drives have available space issues. Perhaps there is a little extra work done, but reading flash is so fast that you'd never notice a difference.

It's true that Android doesn't like being in a condition where storage starts to get too low, but if you have more than 20 to 30 MB free, as I mentioned in an earlier post, you shouldn't have any issues with lag from space issue.

Lag issues may be due to several issues. Remember that CyanogenMod 7 is fairly early beta, so there is probably still some optimization that can happen. And, as others above me have listed, in this particular build LP tends to be shut down while other apps run. If the "lag" people are noticing is only when you go home and you have to wait for LauncherPro to restart - it's pretty obvious when it happens - that's probably the issue. Ignore that stuff about adding particular text to system files unless nothing else works - CyanogenMod has a setting (in Performance) to lock the home screen in memory, and combined with the experimental LauncherPro setting that does the same, that seems to work for most people. Those settings in the LauncherPro forum might be useful in a non-CM ROM that doesn't have the lock home in memory setting.
 
did you flash the gapps listed in the GSB thread immediately after flashing the rom? i experience bootloops with tazz gingerbread,but not with shedbread.

He wasn't reporting a bootloop - it's happening after the OS has loaded. And because it's happening just after the "Touch Android to begin", that means that the setup app is running, and I believe that is part of Google apps.

Because it is also happening in xtrSENSE, it sounds more like a missed data wipe. It could also be that the phone is overclocked too high for the phone to handle, but GSB is clocked at 604.8, and while I've heard of phones that cannot handle 710, I'd be surprised if 604.8 was too fast for an Eris.
 
He wasn't reporting a bootloop - it's happening after the OS has loaded. And because it's happening just after the "Touch Android to begin", that means that the setup app is running, and I believe that is part of Google apps.

Because it is also happening in xtrSENSE, it sounds more like a missed data wipe. It could also be that the phone is overclocked too high for the phone to handle, but GSB is clocked at 604.8, and while I've heard of phones that cannot handle 710, I'd be surprised if 604.8 was too fast for an Eris.

i guess i was confused(for a change ;))... from this statement,i thot the "looping" he was refering to was a bootloop. what i percieved was happening was: touch the android,phone reboot,touch the android,phone reboot,etc. :eek:
I tried Cyanogen's GSB, but the phone started looping at the "touch android to start" screen. Then I tried xtrSense and that loaded, but google apps failed.
from the second part of this statement,i percieved it as a different prollem,with no looping.
 
clearing the caches seem to make my phone a lil less laggy. while it may slow it down a lil bit as things will have to reload,clearing the cache periodically seems to help my phone run smoother. maybe its psychological? :p i dunno. but for me it seems to help

on jit,i have run it on and off,and cant personally tell a difference in speed or smoothness either way. i tend to leave it on,since i understand 2.2(and thus 2.3) is based on its concept.

i have compache enabled and set at the max,and the vm heap size set at the max as well,and surface dithering off. tho i wont pretend i understand what any of those things mean :eek: ;)

Just wanted to caution you that running the max size heap is ok if you need it, but the downside of a large heap is that the VM will need to garbage collect more objects which can take longer. The end result is that you may see longer pauses during usage. I would try to run a smaller heap and see if you have any issues... Unless of course your phone is running good as is.

Being a java developer I have dealt with figuring out an optimal heap size for the application I develop for at work.
 
thanks for the tip. it does seem to be running fine,but i may try it smaller or disabled and see what happens :)
 
I've been running it with compcache disabled and VM heap size maximized, as that's the default in GSB. Do you recommend changing it to something else that might be more optimum?
 
I want flash cache2cache, however, I just already flashed 1.7 and gapps the other day. Would I have to reflash 1.7 and gapps again then cache2cache? Or would I just go in and flash cache2cache anyways (if so, should I wipe davlik on the SD Card)?
 
Back
Top Bottom