Hope I’m posting this in the right place. Ok here we go:
Bought a Nexus S (i9020T) a couple of weeks ago. It was shipped with 2.3.2. I got the 2.3.4 upgrade OTA and installed it. After the installation the screen has a red tint. And I’m not talking about the color variations between different Android versions, this is really bad! I can’t look at pictures and some text is unreadable. The screen is not broken since the bootloader looks normal, so my guess is that it is software related.
I have downgraded the phone back to 2.3.2 and everything is normal. I have tried to reinstall 2.3.4 as well as going from 2.3.2 to 2.3.3 and then 2.3.4, both by downloading the files from Google and manually install and by doing it OTA. I have unlocked the bootloader and tried to load a whole bunch of different ROMs and Kernels. Nothing works. The Voodoo Color Control is not even close to fixing it. The only version that works is stock 2.3.2. I have googled it and it doesn’t seem to be a common problem.
So I’m reaching out to you guys to see if anyone has heard about this behavior and know what to do?? I can live with 2.3.2 but the reason I bought the phone was to get instant updates. I’ll attach a picture of the home screen which should be black. I don’t have international warranty so turning it in to Samsung is not an option.
Any ideas??
wow. that mr is a defective unit imho. i think that you should try to get a replacement. i do not think that you need international warranty or something. just a receipt might do it. (it worked with htc for many nexus one's purchased on ebay for ex) . just give it a try.
sorry for the news. i hope u get it solved or i hope i am wrong.
keep us updated.
Hmm, yeah I was afraid of that.
Just thinking though, what could be defective? It works just fine on 2.3.2. If i run 2.3.4 (or 2.3.3) and start the phone, the Google-logo shows up in white for about 5 seconds, then it turns red and everything is red after that.
Eldrin said:
Hmm, yeah I was afraid of that.
Just thinking though, what could be defective? It works just fine on 2.3.2. If i run 2.3.4 (or 2.3.3) and start the phone, the Google-logo shows up in white for about 5 seconds, then it turns red and everything is red after that.
Click to expand...
Click to collapse
That's really strange. It seems that the update only is screwing things for you. Try sending supercurio a PM. He knows these stuff. He is the dev of the voodoo tweaks and application. He'll surely be able to answer you and give you an advise.
Sent from my Nexus S using Tapatalk
Eldrin, Have you finally found a way to fix it ?
Or are you stick in 2.3.2 ?
Red complexion on ICS
Did you find a solution to this problem?
When I turned on my Nexus S i9020 this morning all greyish colors where red. Directly after turning it on, the lock and the google writing where white as usual, but after about 2 second it got a red complexion. I tried to make a screenshot of my homescreen, but in the jpg the red complexion has vanished and it looks as usual.
I'm running ICS 4.0.3 stock and did the update back in december. Removing the battery for a minute didn't help.
Has anyone an idea?
EDIT: After about 5 restarts it was back to normal! Anyhow, I made a short clip of the startup sequence before www . youtube . com/watch?v=vy5NkFrQDuA
Related
Hello,
As soon as I tap the wi-fi icon, it turns to an "error" state.
I ve seen some threads here, but could not be sure about the resolution. To give idea let me sum it up. My device has been brought from US and I am in europe. İt is alreasy ship s-off.
android version : 2.3.4
software number : android revolution HD 3.6.0. by mike1986
kernel version : 2.6.35.14-Sensation-faux123-v0.1.8+
baseband version : 10.42.9007.00p .....
build number : 1.73.401.2 CL161971
and this topic
http://forum.xda-developers.com/showthread.php?t=1193063&page=2
basilcallly tells to apply a signed ROM . But can you please advise which ROM would solve my wi-fi issue. and how to apply that?
Thanks in advance
I also had similar issue when I flashed the original recovery to remove the rooting and clock work mod...
Now if u have the original recovery installed...flash the OTA updates through it and if you don't have the OTA you need to flash the original ROM
After the flashing ur wifi will work normal
hello,
actually I am so new to the stuf. I havent applied any updates to the device, but I guesss it has been s-off ed and applied a different ROM before it has been sold to my friend in USA. Now, which exact ROM would you suggest me to flash and actually where I can find it and read the how to ?.
Thanks
after stock and root i was on Revolution 3.6.1 and now i am using S3N5EaY v 1.4.0 -> agree .. its very smooth - fast and looks great. but still the most important thing is : battery life.. so before i had to charge 2 times a day on hard-use.
theres no need anymore at the moment ;-)
try out by yaself..
hasan.acar said:
Hello,
As soon as I tap the wi-fi icon, it turns to an "error" state.
I ve seen some threads here, but could not be sure about the resolution. To give idea let me sum it up. My device has been brought from US and I am in europe. İt is alreasy ship s-off.
android version : 2.3.4
software number : android revolution HD 3.6.0. by mike1986
kernel version : 2.6.35.14-Sensation-faux123-v0.1.8+
baseband version : 10.42.9007.00p .....
build number : 1.73.401.2 CL161971
and this topic
http://forum.xda-developers.com/showthread.php?t=1193063&page=2
basilcallly tells to apply a signed ROM . But can you please advise which ROM would solve my wi-fi issue. and how to apply that?
Thanks in advance
Click to expand...
Click to collapse
Ello m8,
It appears your in the same boat as me, i have the wifi error too, it doesn't even turn on to be able to see networks, let alone connect to them so it's quite horrible.
What i've done:
Flashed pretty much every rom i possibly could. (old ones, new ones, no effect)
Changed the recovery to 4ext (which works great but didn't help)
Changed kernels (a lot)
Changed Radios and RIL files (a lot)
Flashed an official RUU (no effect at all)
Went back to S-ON as described in the tutorial on the main xda sensation guide, then S-OFF'd again.
I'm now back on P3D v 8 and it's running lovely but alas, still no wifi.
I've changed the back cover (the yellow connectors at the top have something to do with the wifi) Don't mess around with these as you may break something, changing the case had no effect, apparently the wifi still connects without the back cover on the phone.
I am literally at my wits end with this and i got my phone for free from my work and i was only supposed to have had it for a while (4 months) so if i say it's broke, they may take it back and i've lost the phone completely, if that wasn't the case then i would have sent it back after i'd tried everything software wise i could think of.
I'm not saying that you are in the same situation exactly but if you are then it looks bleak and i would say anything next to removing the wifi chip and replacing it would mean the wifi will never work, plus tutorials for replacing the wifi on a sensation are scarce to say the least (torque screwdrivers at the ready)
If i get it working i'll let you know how, please do the same if you get any joy.
Oh i almost forgot, another thread on another site they mention using an app called wefi, i didn't have any luck but you might.
Good luck matey Hope you have more than i did.
Hi,
I am having the same issue.
Have been running android revolution HD 3.6.5. by mike1986 and previous versions of it (2, 3) and no issues with the WiFi, as one day it just started (yesterday to be precise). I did not install anything or played with settings that could mess with the wi-fi. One day ago was working ok and the next not.
Tried the Wefi app but it did not help either.
feeling hopeless...
bk_25 said:
Hi,
I am having the same issue.
Have been running android revolution HD 3.6.5. by mike1986 and previous versions of it (2, 3) and no issues with the WiFi, as one day it just started (yesterday to be precise). I did not install anything or played with settings that could mess with the wi-fi. One day ago was working ok and the next not.
Tried the Wefi app but it did not help either.
feeling hopeless...
Click to expand...
Click to collapse
Looks like this error is more common than it would first have appeared, read my post a few up for what i've tried, i even feel like dropping it if it's something inside so as to knock it back into place, but i haven't yet Lol that's desperation.
I've got an appointment with HTC soon and i'm getting it changed, if anyone gets this sorted then let me know as i'd rather keep my phone.
dladz said:
Looks like this error is more common than it would first have appeared, read my post a few up for what i've tried, i even feel like dropping it if it's something inside so as to knock it back into place, but i haven't yet Lol that's desperation.
I've got an appointment with HTC soon and i'm getting it changed, if anyone gets this sorted then let me know as i'd rather keep my phone.
Click to expand...
Click to collapse
Hi,
I also tried all you tried and no results.
Changed the case with a friends phone but did not help either.
After a lot of reading through the forums did a logcat to see what the hack the phone is saying about this error and it seems it cannot load the driver.
If it helps smb to go deeper can post it.
Gave a thought or two about knocking it against the wall or throw it from the window but after-all, i think i can live for some time without wifi, my GPRS speed is not bad and maybe soon will be having 3G and during work time can use internet pass-through.
Worst case scenario, will sell it and get EDGE the new quad-core monster HTC will be releasing next year Q1 or early Q2.
dladz said:
Ello m8,
It appears your in the same boat as me, i have the wifi error too, it doesn't even turn on to be able to see networks, let alone connect to them so it's quite horrible.
What i've done:
Flashed pretty much every rom i possibly could. (old ones, new ones, no effect)
Changed the recovery to 4ext (which works great but didn't help)
Changed kernels (a lot)
Changed Radios and RIL files (a lot)
Flashed an official RUU (no effect at all)
Went back to S-ON as described in the tutorial on the main xda sensation guide, then S-OFF'd again.
I'm now back on P3D v 8 and it's running lovely but alas, still no wifi.
I've changed the back cover (the yellow connectors at the top have something to do with the wifi) Don't mess around with these as you may break something, changing the case had no effect, apparently the wifi still connects without the back cover on the phone.
I am literally at my wits end with this and i got my phone for free from my work and i was only supposed to have had it for a while (4 months) so if i say it's broke, they may take it back and i've lost the phone completely, if that wasn't the case then i would have sent it back after i'd tried everything software wise i could think of.
I'm not saying that you are in the same situation exactly but if you are then it looks bleak and i would say anything next to removing the wifi chip and replacing it would mean the wifi will never work, plus tutorials for replacing the wifi on a sensation are scarce to say the least (torque screwdrivers at the ready)
If i get it working i'll let you know how, please do the same if you get any joy.
Oh i almost forgot, another thread on another site they mention using an app called wefi, i didn't have any luck but you might.
Good luck matey Hope you have more than i did.
Click to expand...
Click to collapse
Dude I got the same problem and I did the same procedure so far but same results as well.
I am just wondering if you got any better results for this issue.
Thanks
Same problem, bad results...
I had the same problem. Both my Bluetooth and WiFi would get stuck on "turning on" but never did, I flashed so many ROMs and Kernels, Tried RUU's from Europe,Asia, and USA and nothing worked. SO I CALLED HTC...thankfully I was still under warranty (It's a 12 month warranty) and shipped my phone away after flashing the latest official T-Mobile RUU, Un-Rooting, and going back to S-ON. It's been a week...I called and they said THE MOTHERBOARD needed to be replaced, which I think is the "default fix" if they can't solve the issue. So hopefully in a week I'll have my phone back...Best of Luck...don't mean to be a Debby Downer but I tried EVERYTHING. Give em a call, it won't hurt to try.
http://www.xda-developers.com/android/galaxy-nexus-gets-ics-4-0-4-update/
We'll most likely get it once the sources are updated to 4.0.4. It looks like a lot of things have changed in this build too. Maybe performance will increase on our phones?
Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4
dw9906 said:
Source has been pushed.
Sent from my Amazon Kindle Fire using Tapatalk 2 Beta-4
Click to expand...
Click to collapse
ok guys its here Whitehawkx AOKP 29 is android 4.0.4 maybe its just me but it seems a lot smoother
I just like the fact that multitouch was updated in it for the keyboard issues I was having... Typing drunk on CM9 was messing with everything I needed lol.
Anyone know when the OTA will be out
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock
notinstock said:
Been trying different ROMs but then my phone started random rebooting even when I put it back to completely stock and re-locked it. So, I sent it in for replacement. Now my replacement phone at the top of the screen used to say "T-mobile" but now just reads "LG" on the glass. I guess the later phones were no longer branded T-mobile.
One thing I noticed though is when I put in a ROM that worked flawlessly on my old phone it would cause the replacement to have random reboots, force close, and just plain lock up where I would be required to remove/replace the battery to get it to work again. Any ideas or suggestions??? I have only been able to run the stock GB rom successfully.
Any ideas on what the phones issue may be?? Or maybe when the OTA for a stock ICS will be available?
Thanks,
NotinStock
Click to expand...
Click to collapse
1. why are you posting in this thread?
2. some roms/kernels are undervolted, if your phone cant handle it youll get random reboots.
3. nobody knows when ICS will get here, NOBODY. if anyone says they know when it will get here, they are lying. there are no exceptions, EVER!
Loving all the improvements that come with this update. I just installed AOKP build 31 and have had zero issues thus far. Just one thing missing...can't hangout in G+ and we know whose fault that is. Nvidia
Recently, my phone's display would turn green (nothing else, and not a solid green) after unlocking. This would go away for a moment if I left the display on for a while. However, this afternoon, It did the same but it has not gone away.
I own a Nexus S I9023 (I might be wrong since I haven't seen my phone's information since I rooted it back around in November) If it helps, It's from Wind Canada
Here's a picture showing my predicament
blod_trog said:
Recently, my phone's display would turn green (nothing else, and not a solid green) after unlocking. This would go away for a moment if I left the display on for a while. However, this afternoon, It did the same but it has not gone away.
I own a Nexus S I9023 (I might be wrong since I haven't seen my phone's information since I rooted it back around in November) If it helps, It's from Wind Canada
Here's a picture showing my predicament
Click to expand...
Click to collapse
Sent from my Nexus S
have you tried rebooting? what have you installed or flashed recently?
Sent from my Nexus S using xda premium
I tried rebooting it. It worked before but now it is permanently displaying that.
I haven't flashed or installed anything (just some apps from the market) and it's currently stock ICS 4.0.4
to start I have a crespo4g
not sure what happened.
installed latest euroskank nightly this morning. everything was running perfect.
my battery life got down to about 25% and a white line down the middle of the screen appeared
its only there when theres color other then black it seems? like the app drawer when its open, no white line, but if i go into recovery, anything highlighted in blue, (NOT BLUE TEXT) but the actually highlighted tab has the line
it almost looks like a screen crack but im not sure how that could be possible. my phones been on my desk all day. ive been watching season 4 of breaking bad lol
anyone?
Hurry up, they just started season 5! ahem. Anyway, have you checked the thread for the rom yet to see if its not an isolated issue? To me, at least, that would be the best place to start. Or roll back to a previous version and see if the problem persists, but since you said you can see it in recovery, sounds like it could possibly be hardware related
Sent by pocket technology.
chronophase1 said:
Hurry up, they just started season 5! ahem. Anyway, have you checked the thread for the rom yet to see if its not an isolated issue? To me, at least, that would be the best place to start. Or roll back to a previous version and see if the problem persists, but since you said you can see it in recovery, sounds like it could possibly be hardware related
Sent by pocket technology.
Click to expand...
Click to collapse
lol i know! im excited
im thinking the same thing tho now... im just not sure what would have caused it.
gonna try a flash back to stock after work and see if that changes anything
gonna be real pissed if i need a new phone :crying:
i just tried to screenshot it... it doesnt show up..
its like an overlay??
if i scroll thru my gallery the line appears but everything moves behind it so to speak
wtf mannnnnnnnnnn
Looks like its time to replace your screen.
Sent from my Nexus S using xda premium
kalico17 said:
Click to expand...
Click to collapse
this had happened on my Epic 4G a long time ago it passed over i thought it was probably the kernel/rom
i hope mine does the same.... it happened randomly today.... i just got this thing back new abt a month ago lol. went from AOKP to Skankwich and abt an hour or so later the line appeared smh
This was one of the similar threads found, but it didn't give me a solution. I messed around with the different CPU governor's but none of them solve my problem. When I unlock the phone, it doesn't respond well to my touch for a few seconds. I'm using CM10 and I've never had this problem before. It only came up recently when I replaced my lcd and digitizer because I was having touchscreen problems. Now the problems are mostly gone except at the lock screen. I've tried 3 different roms (one was a Sense 3.6 rom) and they all had this problem. Outside of the lock screen, it mostly worked well except inside the "phone app" in the sense rom. I called someone and they didn't hear it ringing, so it went to voicemail. I didn't want to record a message so I pressed end call like 30 times but it didn't work until i took out the battery. It happens in CM10 too, but its not as bad, usually ends the call after the 3rd or 4th time.
To troubleshoot the problem, I turned on "Show touches-show visual feedback for touches" under Developer options. I also made this video so you guys can see what it looks like.
Ir0nMa1deN said:
This was one of the similar threads found, but it didn't give me a solution. I messed around with the different CPU governor's but none of them solve my problem. When I unlock the phone, it doesn't respond well to my touch for a few seconds. I'm using CM10 and I've never had this problem before. It only came up recently when I replaced my lcd and digitizer because I was having touchscreen problems. Now the problems are mostly gone except at the lock screen. I've tried 3 different roms (one was a Sense 3.6 rom) and they all had this problem. Outside of the lock screen, it mostly worked well except inside the "phone app" in the sense rom. I called someone and they didn't hear it ringing, so it went to voicemail. I didn't want to record a message so I pressed end call like 30 times but it didn't work until i took out the battery. It happens in CM10 too, but its not as bad, usually ends the call after the 3rd or 4th time.
To troubleshoot the problem, I turned on "Show touches-show visual feedback for touches" under Developer options. I also made this video so you guys can see what it looks like.
Click to expand...
Click to collapse
Take a look at this thread, maybe it helps. I would say update your firmware to 3.33, and try cleaning and pulling out the gray pin on the back of the phone. Hope it helps
Did you replace the digitizer yourself? If yes, I'd go back and make sure nothing is wrong. Make sure everything is properly put back together. Hope this helps. best wishes.
Sent from my HTC Sensation using xda premium
realsis said:
Did you replace the digitizer yourself? If yes, I'd go back and make sure nothing is wrong. Make sure everything is properly put back together. Hope this helps. best wishes.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I did replace it myself and I think that's probably the problem but my dad is refusing to help me take it apart again. We're going to go to a cell phone repair store to see if they can give us some advice, then he'll probably agree to open it up again and see what's going on.
Ir0nMa1deN said:
I did replace it myself and I think that's probably the problem but my dad is refusing to help me take it apart again. We're going to go to a cell phone repair store to see if they can give us some advice, then he'll probably agree to open it up again and see what's going on.
Click to expand...
Click to collapse
It looks like you've opened 2 treads for the same problem, so here's what I answered you earlier - http://forum.xda-developers.com/showpost.php?p=34955821&postcount=3
Ah yes, I made some new discoveries since then and I forgot to check on that thread so I ended up making a new one. The digitizer/lcd I bought is supposedly new, and it's the one that says HTC in the middle (no T-Mobile logo on the side) I'm updating Cyanogen Mod to the newest version and flashing new firmware, so if that doesn't fix it then that'll rule out software issues. After that, I'll re-install the lcd/digitizer and see if I can get it to work.
Also, you said "when you change displays it's never the same as the original" I've been looking through hundreds of forums and many people have successfully replaced their screen only for the problem to come back again a few weeks later. I'm thinking it has something to do with static buildup caused by third-party batteries or chargers, as seen in this thread that i forgot to mention. I've changed my charger so all that remains is taking apart the screen again.
Thanks to dennis8, my screen is now fixed. He linked me to this thread and it worked right away after that. Finally my freaking phone works :laugh::laugh::laugh::laugh::laugh::laugh::laugh:
Ir0nMa1deN said:
Thanks to dennis8, my screen is now fixed. He linked me to this thread and it worked right away after that. Finally my freaking phone works :laugh::laugh::laugh::laugh::laugh::laugh::laugh:
Click to expand...
Click to collapse
glad for you man:good: