blueish shadow on buttons and greys

[Guest jurrasstoil]

Hey,

rooted and flashed my SF (swiss TFT) today.

I used universal androot, then installed kallt_kaffe's modded clockwork 2.5.1.3 via fastboot, made full backup, then flashed fillyjonk rls4 and made a full wipe.

Seems like all went well so far, no bootloop, no crash, no nothing.

There is only one thing i'm not sure about, i have slightly blueish shadows on buttons and everything thats lightgrey

example:

Left how it looks on the screenshot

Right how it looks on my display

Edited December 23, 2010 by jurrasstoil

[Guest aleckxander]

hi i have an even worse problem here you can read my experience.

I can see the blue tint issue even better with some widget, i.e. stock energy saver/control widget.

As you can read in my thread i temporary solved restoring from my original nandroid backup only the boot.img (advanced option into che CWM)

[Guest jurrasstoil]

hi i have an even worse problem here you can read my experience.

I can see the blue tint issue even better with some widget, i.e. stock energy saver/control widget.

Yeah I saw that thread, but thought that the blue tint problem would be a bit stronger (cyan android logo for example, mine is still green).

I can see it on my energy saver widget as well, like a little curve from top right to top left.

The weird thing is tho: if I grab the widget to move it around the instantly disappears and once I let go it's back again.

[Guest aleckxander]

yes, same here.. now solved..

still i can't find a way to make it disappear when flashing a 2.2 ROM since my workaround don't work with them

Edited December 23, 2010 by aleckxander

[Guest and84]

I had the same blue tint on buttons and widgets and it would come and go away with no apparent reason.

Then I followed aleckxander method of restoring the original boot.img and so far so good! :)

[Guest jurrasstoil]

What does the original boot.img change when I restore it?

I mean, what does it contain and what does it replace? Apart from the blueish shadows the rom runs flawless, so I don't really wanna mess around with its core too much.

[Guest and84]

What does the original boot.img change when I restore it?

I mean, what does it contain and what does it replace? Apart from the blueish shadows the rom runs flawless, so I don't really wanna mess around with its core too much.

According to this boot.img = boot header + Linux kernel + ramdisk/rootfs

I did a backup with the tint before using the original boot.img and so far everything flows as normal minus the blue tint. If anything goes wrong I can always revert back

[Guest jurrasstoil]

okay, restored my old boot.img

now i have a bootloop -.- back to the old new boot.img i guess

Did this happen because i use version 2.5.1.3 instead of the .0.9?

Edited December 23, 2010 by jurrasstoil

[Guest and84]

okay, restored my old boot.img

now i have a bootloop -.- back to the old new boot.img i guess

Did this happen because i use version 2.5.1.3 instead of the .0.9?

Don't know I used .09 and had the tint so it must be something else

[Guest jurrasstoil]

Don't know I used .09 and had the tint so it must be something else

i meant the bootloop :)

some roms don't work with the .1.3 version of CWM, so i figured that my original boot.img from the stock rom might be having trouble with the .1.3 version as well.

can i just downgrade to .0.9 w/o any problems?

[Guest jurrasstoil]

well, restoring my stock boot.img with .0.9 resulted in a bootloop as well, sigh :)

[Guest and84]

the blue tint returned :) guess stock boot.img doesn't solve it [completely]?

Edit: After a few reboots and restoring old and new boot.img it still comes and goes whichever the boot.img is, something else is trigging this. Hardware acceleration perhaps?

Edited December 23, 2010 by and84

[Guest aleckxander]

well my experience is still positive..

i installed stock rom, seb's deorangeated rom, and finnish (i use this one now).

with all these rom i had blue tint, and with all i restored the original boot.img (i've backupped it everywhere in the house and workplase, kinda scaried to lose it -.-)

till now i got blue tint no more.

CMW__1.3 as far as i read here around do not flash boot.img properly so i think it's normal having issue while playing with boot.ini with this version of CWM recovery.

I'd like to underline that all that i say comes from empirical experience, i'm no expert, actlually i'd honestly say that i'm truly ignorant about the matter.

What frustrates me a lot is:

Why if I flash with CWM a dumped recovery, with his own boot.img, it seems to flash it DIFFERENTLY from a RESTORE of a boot.img?

where's the difference?

sadly i have to leave for xmas so i do not have time to try the new seb's CWM recobery (1.8 i think.).

i hope someone more expert than me can join this party and help us ;)

good luck :)

EDIT: stock rom has no hardware acceleration, finnish has as far as i know.. so i don't think this is the point..

Edited December 23, 2010 by aleckxander

[Guest aleckxander]

posted someother tests here : http://android.modaco.com/content/zte-blad...e/#entry1530817

can you that are facing this problem tell me please what blade you own? i mean carrier and nation?

[Guest jurrasstoil]

I have a swiss orange branded san francisco with TFT display.

[Guest jurrasstoil]

I figured the best way to show this problem to people who don't know what we are talking about is a picture of a colorpicker.

Here we go:

you can clearly see this band of "wrong" colors starting at the top right, heading for the middle, taking a small corner and then heading for the bottom center. Same for the blueish stripes on the white-to-black bar on the left.

(Pictures taken with a camera, so they show the actual screen.)

PS: and of course you can see that i should clean my slr sometime soon :(

[Guest aleckxander]

funny i have a CH SF too..

listen.. can you tell me whch driver you intalled?

[Guest and84]

posted someother tests here : http://android.modaco.com/content/zte-blad...e/#entry1530817

can you that are facing this problem tell me please what blade you own? i mean carrier and nation?

Since I have the same issue still I "hijack" this thread again:

My blade has a TFT and it's from Optimus carrier, Portugal and I'm using stock rom with clockworkmod 2.5.0.9 r2 installed. I already tried flashing several boot.img but still the blue tint comes and goes :(

I'm hoping that with the new cwm and "official" froyo release coming up it will be sorted out