Right, I have a problem with phone since I got it back from T-Mobile, the screen often goes very dark and I have to "bend" the phone to make it visible. After some searching I found that this is likely a backlight problem, unfortunately the method I used to mark it work previously has become less effective.
Does anyone have a diagram of the aces internals and where the backlight is, I don't want to mess with the wrong thing.
I don't think I can take it to the T-Mobile store again, as it doesn't run the stock tmobile firmware anymore. I have a cam backup of it in com
Uter but it's rooted and stuff.
Related
Hey
I am currently running 2.1 on my Samsung Galaxy S the only thing ive done to it is root it, so its running the normal firmware and I'm waiting till the end of september ti get the official 2.2 before I look at flashing something custom onto it, anyway...
I have an odd problem with the phone where the touchscreen part of the phone will become unresponsive for no real reason, sometimes playing a game, sometimes just sending a text or browsing the market. My actuall hard buttons like the homescreen or volume control still work during this and the only way to make my phone un-freeze is to press my power button once to turn the screen blank, then press it again and slide to unlock the phone, then it works fine.
No clue how to fix this... anyone got any ideas?
Thanks in advance..
Sounds like hardware issue. Get it fixed
Thanks for the response (know it was a while ago)
I've had the phone 2 months now in a contract with T-Mobile UK through Carphone Warehouse... Does anyone know what my return rights are? Talking to them later just want to know where I stand when asking for a replacement.
Thanks
Sent from my GT-I9000 using XDA App
hello, i have same issue. Did you fix this problem?
Thanks
This comes really long after. But did anyone find out the reason for this?
I've got an Galaxy S that works fine most of the time. But from time to time the screen will become unresponsive. If I press power button to lock the screen and unlock it again, it goes away. So it seems that it is a software problem.
Another peculiarity is that the keys on the Samsung keyboard are very inaccurate to respond to touch from time to time. Sometimes it is just impossible to hit a letter in the mid row and pressing "s" can put "wz" on the screen.
I was thinking to just put CM on it anyway. But it will void the guarantee in case it is a hardware problem. So I want to make sure that it is software related.
Did anyone manage to fix this either by returning the phone or removing TouchWiz. I am not living in the same country as I bought the phone. So returning it for a checkup will take some effort.
For what ever it is worth
I took the phone to an unofficial service center that flashed the phone with a brand new Android 2.3.3 (the phone came with 2.3.5). A downgrade, which normally isn't a very good deal. But the dead areas on the screen are gone. The phone is much more responsive and the keyboard is not acting funny anymore.
So... if you are experiencing the same. Try getting rid of the TouchWiz before you start taking the phone apart.
Good luck!
I get it occasionally but I've grown to live with it, mine tends to be the kernel recently flashed devils for 4.0.3 but after fiddling with volts mine stops.
Sent from my GT-I9000 using xda premium
Hey guys, i updated my CM7 from RC2 to final some days ago and i started to notice some strange behaivour.
I started getting the black screen during calls problem so i went back to RC2 but still happening.
So i installed Sensor Test from market and i can see that the light and proximity sensors are not working for some reason. The rest of the sensors have numbers changing but not the light or proximity.
This is not my first time flashing a rom and i did all the proper steps and wipes, now no matter to which rom i go cant see the sensors working.
Any idea??
I'm having the exact same issue. I flashed CM7 Final nearly the same time I replaced my digitizer so I thought it I messed up my install somehow but maybe it's actually software related.
my workaround for the moment so i dont get the black screen of death is hexedit /system/lib/hw/sensors.mahimahi.so and change /dev/cm3602 to something else.
That way the sensor is disabled and i can talk normally and then return to homescreen without having to remove the battery.
i found quite a few ppl with this problem, there isnt any official statement about this issue from cyanogen right?
i have the same problem
What can i do?
I'm with nightly 51
I have done the hex edit hack on /system/lib/hw/sensors.mahimahi.so, and that did turn off the proximity sensor. However changing the line /dev/cm3602 to /eev/cm3602 to turn off the proximity sensor, but this also turns off the accelerometer. No landscape view switch on 90 degree turns. (I'm guessing losing this functionality would also affect Navigation if i tried it).
I also went back to stock 2.2, and did the OTA to 2.3.4 from an old nandroid backup. The problem of the screen going off during a call (as others have described above), still occurs. Starting to think its a hardware problem.
I have tried the following apps to turn the proximity sensor off, or, lock the screen on in phone calls - to no avail:
- Screen Suite
- Todds Droid Tools
- Screebl
- Flip it!
I made 2 folders on my SD Card for sensors.mahimahi.so.
/Sensors switch/sensors.mahimahi.so (contains the hex edited on that turns off Prox)
/Sensors original/sensors.mahimahi.so
My thinking was I could copy/paste the files into system/lib/hw depending on the day and my needs. Eg.: If I need to do a lot of phone calls that day requiring dialpad on, or even check my voicemail. However reverting back to the original file still keeps the phone's proximity sensor and accelerometer off'd, even after rebooting. A Nandroid backup is all that will restore this functionality. Hence that approach will not work.
NEways, at this point I'm thinking of doing an HTC repair. I want to know if they will still be able to provide me an N1 (credit card hold on charge...how much?...do they even have N1s?), while sending this one in for repair.
Incidentally, I don't think I will qualify for warranty as this phone has previous water damage. I replaced the screen because of it with an ebay one, but the prox sensor worked for a long time after that.
In general, I'm not sure if a $$ repair is worth it, but on the other hand I just bought a $500 phone in the N1 less than 6 months ago.
What to do...
bump.
What would you guys do? in this situation?
its too good a phone to just sell, even if it just does web/tethering/low profile/android apps awesome.
(i can always switch /sensors.mahimahi.so filez on the fly, worst case scenario. with nandroid restores in between(saving refurb monies)).
nm,
ghetto Romguest 2005 fix:
(hope this helps someone googling same said problem. which i've heard appears on faulty proximity sensors on Droid_1s, and Nexus'ses)
2 Nandroid backups:
1. With the original sensor file of system/lib/hw (in an SD card folder)
2. with the hex edited sensor lib/hw (in an SD card folder number 2)
Copy both respectively into your current rom, and nandroid both respectively into two nandroid versions.
On the days you need touchpad/dialpad, restore 2.
On the days you need landscape/gps/accelerometer, restore 1.
Problem solved, if no hardware warranty options available like me.
$190 saved.
Priceless..
PROGRESS ON THIS THING! )
Ok, so the last time I left this thread i was at the point of sending the phone in for an RMA. The reason I'm writing on this thread is in case someone on an android phone comes up with the Proximity sensor issue ( and it seems a lot of droid devices have this bug, whether its a hw failure like mine on the sensor, or not) ... then at least this thread will be here for the body of knowledge.
So just to summarize:
- hacking the sensor file mentioned above will disable the proximity sensor from working.
- having two nandroids of the proximity file (hacked and normal), will allow you to switch between normal phone (where the screen blanks), and proximity hacked phone (where the screen stays on in call, but never landscapes).
Is there an APK app to manually switch from Landscape to Portrait? Nope... there is code for it that devs can use to force their programs to run in a certain way, but not an on the fly solution.
'Screen Lock' , a program that comes closest simply locks the phone into Portrait.
What if you want to view a web page sideways then? Do you have to nandroid restore the original OS before the hack?
I just found out you don't. I ran Asphalt to see if it would run in portrait or landscape, and it ran in landscape surprisingly. So the portrait locked fone can be tricked in to landscape. woot
On exiting Asphalt, it keeps the phone in landscape
Goto web browser...browse all u want.
Want it back to portrait?
Go to Phone dialer, and it forces portrait. On exit, of fone, your home screen goes back to portrait.
Does proximity sensor off affect the GPS positioning? I'm not sure, it might - have to test.
Does the proximity sensor disabled, mean the accelerometer still works? No, the accelerometer doesnt work in this mode. ;P cant play Asphalt.
Why don't i just warranty my phone? ...I might. Its just that HTC doesnt send out replacement N1s anymore for the warranty period (with a Credit card debit), AND, my ASDF provider, doesn't give out loaners.
Hope this helps out anyone in the meantime!
Hope my GPS still works
UPDATE: Moving to a new phone.....
UPDATE:
So I decided to fold on my software fixes, and went for the Warranty route. Unfortunately HTC couldnt do the warranty themselves, and forwarded me to my Carriers reseller (not the private store I bought the phone from, but the Corporation who bought N1s in bulk from HTC, and sold them to my Carrier), which turned to be a one room office with a personal voicemail machine....
So I went to my Carriers corporate store, as they said they'd do the warranty. The CSR said that he's had people waiting >1 month for Nexus One replacements, with no idea what they'd replace it with. I would have to buy a phone too to use in the interim because they had not loaners.
His guess was that if the warranty might be accepted (mine may have not been a warranty cover because I changed the LCD once and stuff), I might get a Nexus S, or the next HTC phone they offered. All guesses, and all with a month long wait time with no smartphone, and $100 out for a secondary phone...in the interim.
So last night I tried a fix that worked for some Droid owners failed proximity sensor. It involves a rubber grommet set in place between the screen and the sensor, to let it "see" properly again.
No go. As well, my Camera and LED no longer work. (from before the fix attempt btw). Go figure.
So I folded, and bought the next best option for my Carrier, and AWS HTC Mytouch 4g. I decided to forgo Ebay, and buy off newegg, b/c there is some ambiguity into the quality of SLCD and Eeprom (?) chip you may get, so at least Newegg has great service.
I tossed around the idea of selling my N1 last night, but I won't. First too much hassle explaining to a buyer all these issues, and getting a worthy price. They could just Paypal revoke their payment when they get as pissed off with my particular fones lack of function as well.
I'm really going to miss the form factor of the N1 the most, and already am. I think I may wifi tether it to the Mytouch, and use it with Google voice or something.
Anyways, that is the end of my story. Wished I could keep the N1. Even tossed up buying a used N1 off ebay, for the form factor and hacking alone.
I have a very weird issue with my phone. I flashed quite a few different roms and at one point I started to notice this flickering screen. It flickered no matter what screen I was on. The problem would come and go and just sort itself out somehow. Then I noticed a more serious problem. The screen would go super washed out. No display settings would fix it. This happened while using various roms. In the past it fixed itself and again, I don't know why. Today it happened again. I'm currently running an ICS rom, the Midnote 2.0 which is I think the very best ICS rom and it was running wonderfully. I was very happy with it. Suddenly the screen went crazy bright, washed out with extreme banding. It basically looked like a low resolution jpeg. Everywhere. I tried a lot of things to sort it out. I was at the point of calling tech support and I realized, there is no tech support!!! The guy from support for the US version of the Note told me that my phone was made in Japan (which sounds like nonsense) and that it would have to go back to Japan for repair. He gave me a phone number.
Eventually, after hours, I flash my Note back to it's original factory rom. The problem persisted. Then, having nothing to lose, I rooted it again and flash DarkyNote rom which also is a nice rom. After a few minutes, the screen flickered and went back to normal.
I have no idea if it will stay that way though. My fear is that this is going to happen again and who knows if it will stay that way next time. And I had no idea that there was essentially, NO SUPPORT!
I had wonderful tech support for my international HD2. I called them up with an 800 number and told them that I bricked it up by flashing roms and they replied, it's under warranty so the repair costed me like 16 dollars. LOL No problem. Samsung seems like a different ballgame. This has been an eye opener for me. This might be my last international phone.
Crap, during the space of this post, the screen has gone back to super bright.
Sounds like a hardware issue to me.
USB?
kuttyjoe said:
I have a very weird issue with my phone. I flashed quite a few different roms and at one point I started to notice this flickering screen. It flickered no matter what screen I was on. The problem would come and go and just sort itself out somehow. Then I noticed a more serious problem. The screen would go super washed out. No display settings would fix it. This happened while using various roms. In the past it fixed itself and again, I don't know why. Today it happened again. I'm currently running an ICS rom, the Midnote 2.0 which is I think the very best ICS rom and it was running wonderfully. I was very happy with it. Suddenly the screen went crazy bright, washed out with extreme banding. It basically looked like a low resolution jpeg. Everywhere. I tried a lot of things to sort it out. I was at the point of calling tech support and I realized, there is no tech support!!! The guy from support for the US version of the Note told me that my phone was made in Japan (which sounds like nonsense) and that it would have to go back to Japan for repair. He gave me a phone number.
Eventually, after hours, I flash my Note back to it's original factory rom. The problem persisted. Then, having nothing to lose, I rooted it again and flash DarkyNote rom which also is a nice rom. After a few minutes, the screen flickered and went back to normal.
I have no idea if it will stay that way though. My fear is that this is going to happen again and who knows if it will stay that way next time. And I had no idea that there was essentially, NO SUPPORT!
I had wonderful tech support for my international HD2. I called them up with an 800 number and told them that I bricked it up by flashing roms and they replied, it's under warranty so the repair costed me like 16 dollars. LOL No problem. Samsung seems like a different ballgame. This has been an eye opener for me. This might be my last international phone.
Crap, during the space of this post, the screen has gone back to super bright.
Click to expand...
Click to collapse
Sorry to hear about your trials! I read on another thread somewhere about similar issues (can't remember where sorry!) The offender seemed to be the USB charging port was a bit damp and caused charging issues and weird things happening. Pushing the USB cable into the charging port and pushing it at the right angle seemed to fix it. Someone else had to use a flat blade screwdriver to get the internal USB port at the right angle.
May be totally barking up the wrong tree, but who knows - it may help? Otherwise push your local support. I'm in Australia and the Note has still not been released here officially so hope I never have to get support as there is no-one locally!
Good luck and let me know how you go!
Hello there!
As some of you already know, but some probable don't, the B is a variation of the Galaxy S made for the regional area of Brazil, and it has some differences from the usual i9000, but hopefully not so many that someone well versed in this hardware won't be able to help me out.
A couple weeks ago, i installed a custom ROM, based on JB 4.1.1 with Devil Kernel, and it worked perfect for about two weeks, but after that the screen would go out sometimes and i would need to get the battery out and do a hard reset. I thought it was something wrong with the ROM and that the phone wasn't exactly in good terms with it. But alas, it got worse. And up to a point in which the i9000B would just power up, you would be able to hear the initial sounds of Samsung intro, and after it had completely booted up, you could feel the haptic vibrational responde from the touch of the screen, everything worked perfect, but the screen was off, the buttons light up, but the screen doesn't. Hold that thought.
With such, i tried many 'resurection' ROMs, to mixed results, but in the end the only real success i had was kind of sheer luck, for the screen would go out again after a certain amount of time, not to get back again. I really thought that somehow there had been some kind of unprovoked physical damage to the phone itself, and that was the reason for the black screen.
But these past days i sort of made a breakthrough, so much for serendipity: i found out that applying pressure (not too much, not too little) in the area immediatly above the middle of the screen, it would stay lit normally. The exact place would be the center following a line that crosses the screen beginning at the bottom of the Vol Down button.
Whole story explained, i just would like for someone more technically versed than yours truly to explain me what the hell is going on with this device, what could be causing it to act that way, and most importantly, how can i fix this, and if i fix this that nothing is going to happen again in case i install, say, CM10. Some help please? I really want to fix this phone, it is already past being a mere challenge at this point.
Regards,
....
the best thing to do in this case is flash stock rom with odin ...
and claim ur warranty and let samsung pay for their defective piece,,,
I have looked up all the threads relating to an issue with some galaxy notes going pink all of a sudden. The thing is I can't find a viable fix for the problem.
I had never disassembled my phone and the screen slowly turned purple and started blackening out. It was fully functional. This I knew because I connected it to my Windows 7 computer and used Android Commander. I ordered a new screen complete with bezel etc. I have two batteries, the first didn't even charge after I put it in the phone (it had drained totally during the wait for the new screen and went dead), the second was partially charged and allowed the screen to boot. It is however behaving like the first screen did before it went black, that is purple. I am sure I have not done anything wrong with the connections when I dismantled it. Could it be the batteries? or the adapter flex? I just hope it is not the mainboard. It is not on warranty and we don't have that many honest phone specialists around where I live. I am almost sure others have experienced the same problem and someone on xda knows what the problem is. If you do I would be indebted.
Whites show up ok on startup but turn immediately pink. Blues are a big problem. I think that it must be software because from bright white it turns pink, and at the moment it screen brightness is at full intensity it is ok for a time. However don't want to leave it at full intensity. I have tried changing screen intensity and unchecking screen power usage in Settings/display.
I was on Ultimate JB rom, but have just gone to stock JB Rom (Germany LT4) same problem.
Please help.
Thanks
Instead of wasting money and time, go to a Samsung Service Center and get it fixed. Someone in this forum (i guess he was from Brazil or Portugal) has the same problem when he updated to ICS or Jelly Bean but worked fine with gingerbread. Flash a GB rom from Dr.ketan post and look if it works. If still has the same problem, go to a Samsung Official Service. Good luck and sorry my bad english
Thanks for the advice
I'll try it out.