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

Root Which ROM type are you using?

Which type of ROM are you using?

  • Sense ROM

    Votes: 108 32.8%

  • ASOP ROM

    Votes: 129 39.2%

  • MIUI ROM

    Votes: 35 10.6%

  • My phone is not rooted

    Votes: 57 17.3%
  • Total voters
    329
You still see the Homescreen banding with a launcher. Where do you turn off overscroll in redux?
 
I'm probably being stupid here, but I can't see any banding anywhere.

Under Settings | Interface, the first option is a check box labelled "Overscroll glow". I have the latest r2 Test, so it may be new - I don't recall seeing it in 1.2, but I don't recall seeing the banding either (I used your excellent blue theme then though, which may have helped?).
 
adskankster said:
I'm probably being stupid here, but I can't see any banding anywhere.

Under Settings | Interface, the first option is a check box labelled "Overscroll glow". I have the latest r2 Test, so it may be new - I don't recall seeing it in 1.2, but I don't recall seeing the banding either (I used your excellent blue theme then though, which may have helped?).
Click to expand...

There's no overscroll checkbox on that menu on 1.2
 
Might be the case - but as I've never noticed it in either version, best to ask someone else or ihlades (I can't post in XDG dev yet).

Anyway, thanks for the explanation. :)
 
SUroot said:
I know its definitely in 1.2. Ihlades even told me which code did it in BoardConfig.mk
Click to expand...

Yeah sorry, I meant that as I never noticed it in 1.2, the fact that I don't notice it in 2 doesn't help us to know whether it's in 2. All I can say for definite is that you can turn overscroll off in 2 (which I have done - though it may have been off by default).
 
I've been running MIUI 1.8.19 for a while now. I really love it. It's not the fastest rom, or the best on battery. But neither are bad, and it's just so darn pretty, those things don't bother me. I am running Go Launcher over it though.
 
SUroot said:
No there Isnt. the banding is on 1.2. Maybe he has fully removed it in 2.0
Click to expand...
It was there in the second Redux2 test snapshot. That added an option to turn off the overscroll glow, which makes it less obvious, but it was also visible in some backgrounds.
 
Hadron said:
It was there in the second Redux2 test snapshot. That added an option to turn off the overscroll glow, which makes it less obvious, but it was also visible in some backgrounds.
Click to expand...

How do those bg's compare for you in dGB?
 
Homescreens seem fine, and I don't see noticable banding in the overscroll glow (which was always easily visible in Redux). I do have one app background that shows severe banding in both dGB and Redux (but not CM or Miui), but that apart I don't notice anything.

When I next try Redux I'll do a comparison with a few wallpapers which I'd expect to show it, but seem OK on dGB.
 
SUroot said:
Wasn't mine originally to be honest... :)
Click to expand...

Nor mine but I got there eventually. Got cyanogenmod yesterday but not sure what to make of it just yet, mainly because of the browser and the fact there's no numeric keypad for entering text.

At least not that I've found :confused:
 
ceider said:
Nor mine but I got there eventually. Got cyanogenmod yesterday but not sure what to make of it just yet, mainly because of the browser and the fact there's no numeric keypad for entering text.

At least not that I've found :confused:
Click to expand...


Oh, cyanogenmod appears to be even buggier than gingerbread now. I'm having no luck with this crap.
 
What CM version, and what bugs?

I was using CM7 until about a week ago - mainly running nightlies (which are in principle experimental builds, but are usually perfectly stable), but have also used stable and release candidate builds, and didn't meet a lot of bugs. But it may depend on your setup and what you are doing?
 
Hadron said:
What CM version, and what bugs?

I was using CM7 until about a week ago - mainly running nightlies (which are in principle experimental builds, but are usually perfectly stable), but have also used stable and release candidate builds, and didn't meet a lot of bugs. But it may depend on your setup and what you are doing?
Click to expand...
cm7 nightly and 701 is actually quite buggy and one of the reasons i moved to dgb

lots of wierd stuff like none persistent changes in apps like poweramp not saving the EQ enabled flag after restart or lock.

lock screen flick off when screen on animation is enabled

statusbar pull down issue where it refuses to retract all the way when flinged has plagues it for months but they dont seem to fix them.
there also seems to be a cpu cycle leak if keep on for a few days without rebooting.

i didnt have these issues with 7.0.3 and dont have these issue with dGB
 
It's funny how usage differs - as I don't use the equaliser, don't use screen on animation, and rarely managed a few days without reboot I missed most of those :)

Though the reason I don't use screen on animation is that it caused problems in the early GingerVillain releases (and I've just never tried it since), so if that's the same thing then that bug has been there a long time! (Though you do say it wasn't in 7.0.3, so maybe not)
 
I used cyanogenmod 7.03 for desire, a stable one apparently. Bugs, too many to list, from widget settings freezing, to not being able to set themes.... SwiftKey stopped working altogether.

I used s - off, clockworkmod, and the revolutionary method. Cyano was the first custom rom I used. Initially it seemed ok, but in the end I couldn't be bothered fighting to get it to work.

Worse still, i restored my system to the date before I gained root access. Well done Ceider, well done.
 
Hadron said:
It's funny how usage differs - as I don't use the equaliser, don't use screen on animation, and rarely managed a few days without reboot I missed most of those :)

Though the reason I don't use screen on animation is that it caused problems in the early GingerVillain releases (and I've just never tried it since), so if that's the same thing then that bug has been there a long time! (Though you do say it wasn't in 7.0.3, so maybe not)
Click to expand...

that bug came to gingervillain as he started using the nightly commits when it moved to 2.3.4 gb
7.0.3 was 2.3.3 and gv under 2.3.3 didnt have this issue either

i personally feel that cm has gone down hill
 
I like CM, i tried it when I was bored when dGB appeared to be at a standstil (well I compiled a custom version) but the size was just too unyielding, But also Battery life was a huge concern also. Didint stick long enough to find bugs
 
You must log in or register to reply here.
Back
Top Bottom