As the title suggests, I have a Nexus S i9023 (no root, perfectly clean) and the major problem is that i've upgrade the phone to ICS manually and now there are some things that don't work (recovery, light sensor, etc.). I know that there are a lot of threads like this, i know that the problem of the recovery is a problem of brightness, but i wanna know which ROM i've to flash. I'm using the build IML74K.
Another problem is that sometimes the keyboard freezes. Is it caused by the wrong build?
Which rom did you flash?
Try lastest version of ics
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
alfax21 said:
I'm using ICS 4.0.3, build IML74K, flashed manually.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am using the same on my i9023 with no issues, only difference is I am rooted and have clockwork recovery. I suggest a re flash.
I'll try to re-flash the same ROM. If it won't work i'll root the phone and i'll flash CM9.
Anyway, how can i solve the problem of the keyboard? I don't think it's a problem of the build.
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
alfax21 said:
I've flashed the ROM for Nexus S i9023 two times but the problems still remain. Any suggestion?
Click to expand...
Click to collapse
Only thing I can suggest is installing clockwork recovery, rooting etc and flashing another rom to see if the problem persists, if so then it probably a hardware issue.
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Ok maybe there's no solution (i'm new in this forum so i can't post link as the one below):
code.google.com/p/android/issues/detail?id=23065&can=1&q=ics%20nexus%20s%20i9023%20recovery&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars
So I think it will be fixed in the next release. I ask confirmation if someone knows something.
CONTACTMC said:
Also where did you get the rom your flashing? There is a thread in the general section with the full rom package I used. Its on the first page at the mo.
Click to expand...
Click to collapse
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
alfax21 said:
Yeah, i've seen it. This one, right?
forum.xda-developers.com/showthread.php?t=1445635
Click to expand...
Click to collapse
Yeah that's the one, flash the full rom package. You may just have a corrupt .zip.
Alredy done two times, but the problem remains. Mmmh i don't think it's a corruption problem, i mean, i've tried to put the update in the phone from two PC.
Sent from my Nexus S using XDA App
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Harbb said:
Unsure about your keyboard problem though, but it does like to stay open for longer than i'd like after going back to the home screen.
Click to expand...
Click to collapse
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
alfax21 said:
Yeah, it remains open also after going back to the home screen, and it doesn't work. The only way is to crash it by going to the setting of the keyboard in the notifications.
Click to expand...
Click to collapse
Mine doesn't remain open though,. It just stays for say half a second, then animates away. Would be much more perfected if it went away while animating the previous window away, not a second later. I've not experienced the keyboard causing those kind of problems.
Might be wise to try SwiftKey or some other kind of keyboard alternative? That is easily enough to sway me away from stock.
Harbb said:
That is easily enough to sway me away from stock.
Click to expand...
Click to collapse
I agree. I'll wait for an Experimental Mod of CM9, then i'll root the phone.
Ok i'll make the thread as solved. I want to thanks Harbb for his help, i quote his post for those who will read this thread.
Harbb said:
Recovery: Known problem. Backlight stays off. Nothing you can do without unlocking your bootloader or rooting. Angle + lamp will show you what is on the screen.
Light Sensor: It's still buggy. With the phone locked, cover your hand over the light sensor (left of the ear piece while facing the phone). Hand still covering, unlock the phone. After a few seconds, remove your hand and face it under a light source. What i've noticed is it'll get brighter initially but refuse to darken again. Of course, you need to have Automatic brightness adjustment (just in case it isn't set to auto).
Click to expand...
Click to collapse
If you have problems (like the recovery one and the light sensor) with ICS 4.0.3, build IML74K, on your Nexus S i9023 there's nothing you can do, probably Google will fix it on his next update 4.0.5.
I'll just add that many custom ROMs allow light sensor manipulation. I hear there are great, working settings, its just the stock calibration that sucks. I've not tried this myself, but should be available in cm9, cna, etc.
..
Election Day said:
This is how I have my i9023 set up. These settings work very well, so feel free to use them.
Click to expand...
Click to collapse
Are these settings of the stock ROM?
..
Related
Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,
restart phone and go from there
Sent from my ADR6400L using XDA App
vinnyjr said:
Have the Thunderbolt set up for making sound when touching screen. The screen will work as it should and then without reason it will get very soft and sometimes completely stop making any sound. Checked all my settings and they are as they should be. I also have the Sensation and the screen is set up the same way and it works properly. Is there something I'm overlooking or is this another bug?? Any help would be welcomed. Running stock Thunderbolt.
Thanks,
Click to expand...
Click to collapse
It's a bug of some kind. I've had it since the day I bought my TBolt(Launch Day). I think the reason its not heard about much is because most users don't use the screen sound option and also because a lot of users here and at AC root and flash custom roms.
I'm still running launch day software because it just works for me for the way i use my device.... this being the only bug that affects me. I rooted and flashed this rom:
http://forum.xda-developers.com/showthread.php?t=1013577
and the issue went away so if it really bothers you I would go that direction. I assume other custom roms fix it as well but I cannot comment as the above is the only rom I flashed before going back stock and un-rooting.
Thanks for your input, checked other sites and found other people with same issue. Going to root this thing anyways and I'm sure the new Rom will fix the issue. Might check out the one you downloaded, looks pretty fast.
Thanks again.
Hey guys, is there a way to calibrate the nexus s touchscreen? Sometimes it is unresponsive...
Anybody?
unresponsive? Maybe you just need to make a good wipe and fresh instal of your rom/kernel..
no?
I don't think so because it happened since gingerbread 2.3.6, and now i have brainmaster's stock 4.0.3 with eugene's kernel and still happens sometimes... and i did a full wipe before flashing ICS.
i used the nook screen calibrator from the market...it worked fine for me
sent from Ice Cream Infused NS4g
I'll give it a shot and let you know, thanks. BTW, on the market i've found Nook Screen Recalibrate, it is the same as you used, right?
Edit: I've tried the app and it managed to improve the touchscreen response, but didn't solve my problem at all (phantom touches). But they're almost gone. Is there any other app like that?
jedijos said:
I'll give it a shot and let you know, thanks. BTW, on the market i've found Nook Screen Recalibrate, it is the same as you used, right?
Edit: I've tried the app and it managed to improve the touchscreen response, but didn't solve my problem at all (phantom touches). But they're almost gone. Is there any other app like that?
Click to expand...
Click to collapse
Found anything else mate? I ran NSR, still have phantom touches
JohnSteveDoe said:
Found anything else mate? I ran NSR, still have phantom touches
Click to expand...
Click to collapse
Same thing with mine. The phantom touches are only vertical but the device has become unusable.
I'm installing Cyanogenmod 10 now. Let's see if that helps.
gcaliari said:
Same thing with mine. The phantom touches are only vertical but the device has become unusable.
I'm installing Cyanogenmod 10 now. Let's see if that helps.
Click to expand...
Click to collapse
It didn't help. touch seems to work but if I hold the touch the touch sensor goes crazy and starts touching several random points in the screen, all in the same vertical as the place I touch.
Does anyone have any suggestions?
gcaliari said:
It didn't help. touch seems to work but if I hold the touch the touch sensor goes crazy and starts touching several random points in the screen, all in the same vertical as the place I touch.
Does anyone have any suggestions?
Click to expand...
Click to collapse
Replace the screen, sounds like a physical issue to me.
polobunny said:
Replace the screen, sounds like a physical issue to me.
Click to expand...
Click to collapse
Could be but since the problem started after I ran the Nook Screen Recalibrate my first suspicion was the program.
I'm trying several different solutions from other threads and none seems to work:
- TouchRecalibrate.apk
- calibration.ini
- ts_calib-signed.zip
gcaliari said:
Could be but since the problem started after I ran the Nook Screen Recalibrate my first suspicion was the program.
I'm trying several different solutions from other threads and none seems to work:
- TouchRecalibrate.apk
- calibration.ini
- ts_calib-signed.zip
Click to expand...
Click to collapse
If you wipe everything and flash a rom, there's no way it's a software issue.
polobunny said:
If you wipe everything and flash a rom, there's no way it's a software issue.
Click to expand...
Click to collapse
Well, it's working now. I don't know exactly what soved the problem but in my despair I re-executed all procedures and something must have gone right. Wish I could tell what fixed it for others but I really don't know.
Thanks for the help polobunny
Same problem
Hey,
I got the same problem,
so I did some research, I found out that there lots of people got the same problem.
A wipe, or install an other kernel or rom will work, but it will for some reason return.
For some models it's enough to install a kernel with some other touchscreen preference. One problem, it will only work on android 2.3 there are not jet other newer kernels published
But 99% its not a screen problem, so u can buy a new screen and replace it with no success. But most of the people say it's a hardware problem. So modify the touchscreen driver.
sorry, bad english​
Hi!
For past two-three days I am experiencing this problem. Touch sensor just randomly stops working. Top side of the screen is very very difficult to control, sometimes even impossible. Sometimes it feels like sensor recognizes multiple touches at the same time which results random pages or menus opening and closing.
After short usage with screen up or after long downtime (like when I go to sleep) I'm not able to use sensor at all. I cannot shut down the alarm clock, I cannot answer the calls. I still can use the power button tho.
Now what is the most retarded is that nearly all that vanishes after phone reboot. The only thing that remains is that top side of the screen is still quite difficult to control. For example I cannot open that top slide-bar comfortably. I have to slowly move my finger over the screen in order to do so.
Phone specifications:
Custom ROM: Cyanogen 11-20140702-nightly
sdcard partition type: FAT32
bootloader version: 2.14
Security-OFF
CID: 11111
Custom recovery: TWRP 2.7.0.8
P.S.: tried to re-insall ROM did not help. Phone havent been damaged by any means recently.
Did u over or under clock..flash a mod to control kernel? That's what it sounds like
I'm assuming you're using the stock kernel? What you're describing is an ongoing issue with the CM kernel, flash a custom kernel (Torched or Bubba) and your problem should cease.
Sent from my Evita
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Look under Tims sig
marknoll said:
Wow. I never knew there was an issue with stock kernel...what's causing that anyways?
Click to expand...
Click to collapse
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
SoulSurvivors said:
Damn it..
I'm a newbie with all that kernel flashes. Any How-To for noobs? Guide or something? I have found Tourched Kernel for KK thread (I suppose it stands for Kit-Kat?), but it's quite puzzling for me with all that voltages.
P.S.: What caused such random issue all of the sudden? Have been using CM for quite a bit of time already. Got that issue just 2-3 days ago
Click to expand...
Click to collapse
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
timmaaa said:
I have no idea what's causing it, I do know that using a custom kernel always fixes it for me though.
Flashing a kernel is similar to flashing a ROM, if you want instructions just check the How-To Guide For Beginners thread in my signature.
Sent from my Evita
Click to expand...
Click to collapse
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
You can try flashing a different ROM, or rolling back to the last build of CM that you remember being ok.
Sent from my Evita
SoulSurvivors said:
Meh, I have updated kernel to 3.4.86-Torched-KK.B4.3+
Problem is still here.
Still cant open top slide menu properly. It is just weird, it really seems like some sort of damage to very top side of the screen. But i didnt hit it or anything like that. Screen itself without any visible damage or even scratches, cuz im using screen protector. Gonna see if I can at least answer the calls properly without sensor goin full nuts.
update:
That's definitely a software issue. If i turn the phone around so screen would get rotated that "damaged" area works just fine. What the **** is going on? It started so randomly
Click to expand...
Click to collapse
Maybe reflashing the ROM and the kernel would be a good idea. I've had to do that too. Its annoying,but sometimes I had to do that. Good luck.
Nop..
I've done the factory reset. Installer fresh ROM, Gapps and kernel.
Same ****. I Guess That is indeed hardware damage to sensor.
/sadpanda
There's a way to diagnose it. Download an app called sensor on play store
About a week and a half ago I got water into my GS3 and it ruined the OLED panel. It was a relatively slow process, and I was able to use it up until most of the screen turned black (touch still functioning properly). I ordered a new Screen Assembly which included the frame, OLED panel, digitizer, and glass as ONE unit, pre-assembled.
Upon taking the broken phone apart and re-assembling it into the new frame/screen, the phone hangs for a long time on the "Samsung Galaxy SIII" with Cyanogenmod Cid character, but finally boots, however the touch screen is unresponsive.
All hardware buttons work, and the capacitive buttons work as well (back and menu), it is only the touchscreen that doesn't function, but it looks beautiful!
is this a digitizer issue (faulty hardware sent to me)? It seems as if the phone is trying to communicate with the digitizer or some other hardware, gets stuck in that loop because it can't detect it, times out, and then finishes booting.
I tried re-flashing CM to see if it was a kernel error or something of the likes, but the issue persists.
Any Ideas? Thank you so much in advance.
XdrummerXboy said:
About a week and a half ago I got water into my GS3 and it ruined the OLED panel. It was a relatively slow process, and I was able to use it up until most of the screen turned black (touch still functioning properly). I ordered a new Screen Assembly which included the frame, OLED panel, digitizer, and glass as ONE unit, pre-assembled.
Upon taking the broken phone apart and re-assembling it into the new frame/screen, the phone hangs for a long time on the "Samsung Galaxy SIII" with Cyanogenmod Cid character, but finally boots, however the touch screen is unresponsive.
All hardware buttons work, and the capacitive buttons work as well (back and menu), it is only the touchscreen that doesn't function, but it looks beautiful!
is this a digitizer issue (faulty hardware sent to me)? It seems as if the phone is trying to communicate with the digitizer or some other hardware, gets stuck in that loop because it can't detect it, times out, and then finishes booting.
I tried re-flashing CM to see if it was a kernel error or something of the likes, but the issue persists.
Any Ideas? Thank you so much in advance.
Click to expand...
Click to collapse
Only way to tell if it's a hardware issue is to go completely to stock. If you can't get it to work at that point then something is wrong. Could be a broken digitizer, or could be a problem with the connection to the board.
I would try to make sure your connection is solid and you didn't miss anything. But I'd say going back to stock is a necessity. Just make sure you Odin a 4.1.2 image, and if your screen still doesn't work then pull the battery so it can't update, then decide where to go from there.
BadUsername said:
Only way to tell if it's a hardware issue is to go completely to stock. If you can't get it to work at that point then something is wrong. Could be a broken digitizer, or could be a problem with the connection to the board.
I would try to make sure your connection is solid and you didn't miss anything. But I'd say going back to stock is a necessity. Just make sure you Odin a 4.1.2 image, and if your screen still doesn't work then pull the battery so it can't update, then decide where to go from there.
Click to expand...
Click to collapse
Thanks for the input, I appreciate it!
I have double- and triple-checked the connections. So what exactly would Odin-ing back to stock get me? The software/firmware worked flawlessly beforehand, so wouldn't that eliminate the possibility of software/firmware issues on my device?
XdrummerXboy said:
Thanks for the input, I appreciate it!
I have double- and triple-checked the connections. So what exactly would Odin-ing back to stock get me? The software/firmware worked flawlessly beforehand, so wouldn't that eliminate the possibility of software/firmware issues on my device?
Click to expand...
Click to collapse
Theoretically yes, but if you go back to stock you'll know for sure. If the digitizer isn't working anyway you have nothing to lose. If everything is completely stock then you know for sure it isn't software related and it has to be the digitizer.
Okay thank you, I appreciate your help!
Sent from my ASUS Transformer Pad TF700T using XDA Free mobile app
BadUsername said:
Theoretically yes, but if you go back to stock you'll know for sure. If the digitizer isn't working anyway you have nothing to lose. If everything is completely stock then you know for sure it isn't software related and it has to be the digitizer.
Click to expand...
Click to collapse
Sorry for reviving my dead thread and noob questions, but I'm still having issues.
My phone is perfect except for the screen doesn't recognize touches, although all buttons and capacitive buttons work well.
I am currently running CM11 using clockworkmod recovery, and I want to return to rooted stock, as you mentioned.
I am wondering if the firmware for the display is not present, since it is a new display (entire assembly, including frame).
How would I go about returning to stock rooted, and flashing as much stock firmware as possible to hopefully ensure that the display firmware is flashed?
As a side question, does the MF1 firmware AiO include things like display firmware? I flashed that with no result, so is flashing back to stock pointless?
I would like a 4.1 Stock ROM or whatever DOES NOT have Knox, so that I at least have the option to go back to CM if I wish if I sort out the issues.
Thank you all so much
XdrummerXboy said:
Sorry for reviving my dead thread and noob questions, but I'm still having issues.
My phone is perfect except for the screen doesn't recognize touches, although all buttons and capacitive buttons work well.
I am currently running CM11 using clockworkmod recovery, and I want to return to rooted stock, as you mentioned.
I am wondering if the firmware for the display is not present, since it is a new display (entire assembly, including frame).
How would I go about returning to stock rooted, and flashing as much stock firmware as possible to hopefully ensure that the display firmware is flashed?
As a side question, does the MF1 firmware AiO include things like display firmware? I flashed that with no result, so is flashing back to stock pointless?
I would like a 4.1 Stock ROM or whatever DOES NOT have Knox, so that I at least have the option to go back to CM if I wish if I sort out the issues.
Thank you all so much
Click to expand...
Click to collapse
I'm almost sure Knox wasn't added until 4.3 ML1
From my Wicked S3 on SOKP
ShapesBlue said:
I'm almost sure Knox wasn't added until 4.3 ML1
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
Yeah, I think you're right
So anything Stock that will allow me to still have an unlocked bootloader when I'm done with it would be great!
4.0 - 4.2
XdrummerXboy said:
Yeah, I think you're right
So anything Stock that will allow me to still have an unlocked bootloader when I'm done with it would be great!
4.0 - 4.2
Click to expand...
Click to collapse
Correct. Custom roms will work just stay away from anything in the development forums that says BL LOCKED or any variation of that
From my Wicked S3 on SOKP
ShapesBlue said:
Correct. Custom roms will work just stay away from anything in the development forums that says BL LOCKED or any variation of that
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
But to solve my issue I need the stock firmware, which means stock (and rooted) ROM. Is there a forum for that in the development section or where could I get my hands on it?
Thanks!
XdrummerXboy said:
But to solve my issue I need the stock firmware, which means stock (and rooted) ROM. Is there a forum for that in the development section or where could I get my hands on it?
Thanks!
Click to expand...
Click to collapse
I'm assuming you mean 4.1.2?
Edit: I found it, I don't know if the links work though. http://forum.xda-developers.com/showthread.php?t=2178482
From my Wicked S3 on SOKP
ShapesBlue said:
I'm assuming you mean 4.1.2?
Edit: I found it, I don't know if the links work though. http://forum.xda-developers.com/showthread.php?t=2178482
From my Wicked S3 on SOKP
Click to expand...
Click to collapse
That was the right thread, the links were dead but took me to the right website, where I found this under archived devices:
http://www.scottsroms.com/downloads.php?do=file&id=511
Stock rooted 4.3 WITHOUT Knox, meant for people who haven't locked their device.
EDIT:
Just flashed, and WAHOOO Touch screen works well!
Thank you all so very much!
Just got the phone ,stock att, I already did factory reset it doesn't show 2nd screen when main off but the shortcuts still work(flashlight camera etc..). Could it be that it is super dim, anyway to change that ? It works normal with main screen on. I am on latest att update. I looked everywhere and didn't see anyone with similar issue that didn't get fixed by factory reset. Phone is unlocked also. Any ideas ?
Could you give a little more information about your problem?
The phone has a sensor that detects when you have a flip cover on and shuts off the second screen until you open it, so it could be there's something in front of it.
Another thing you can try is disabling Quick Cover in the settings if you don't have the official LG cover.
Sent from my LG-H900 using Tapatalk
Inquisitor956 said:
Could you give a little more information about your problem?
The phone has a sensor that detects when you have a flip cover on and shuts off the second screen until you open it, so it could be there's something in front of it.
Another thing you can try is disabling Quick Cover in the settings if you don't have the official LG cover.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
I tested that sensor with aida64 it seems to be working fine when I put my hand in front of it, also it doesn't show anything in front of it otherwise. I disabled the quick cover option and enabled it doesn't work either way. One thing I noticed that if I use quick cover case and open and close really fast I can see the 2nd screen being on for split second and then it goes black even though the shortcuts are still there.
aim1999x said:
I tested that sensor with aida64 it seems to be working fine when I put my hand in front of it, also it doesn't show anything in front of it otherwise. I disabled the quick cover option and enabled it doesn't work either way. One thing I noticed that if I use quick cover case and open and close really fast I can see the 2nd screen being on for split second and then it goes black even though the shortcuts are still there.
Click to expand...
Click to collapse
Ok. One last thing you should try is to go into settings, Second Screen, and toggle the two options in there. One should be for when the main screen is on, another for when it is off. Switch both of them off, then on, and restart the phone. If that doesn't work, perhaps there's something wrong with the screen.
Sent from my LG-H900 using Tapatalk
Inquisitor956 said:
Ok. One last thing you should try is to go into settings, Second Screen, and toggle the two options in there. One should be for when the main screen is on, another for when it is off. Switch both of them off, then on, and restart the phone. If that doesn't work, perhaps there's something wrong with the screen.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
Yeah did that, no difference.
aim1999x said:
Yeah did that, no difference.
Click to expand...
Click to collapse
Could you post an example of what exactly is happening? The second screen does have some issues, mainly light bleed, but that's something that is inevitable due to the manufacturing process. It could be a problem with the backlight, because as far as I know, the screens are independent and don't utilize the same backlight.
Sent from my LG-H900 using Tapatalk
Inquisitor956 said:
Could you post an example of what exactly is happening? The second screen does have some issues, mainly light bleed, but that's something that is inevitable due to the manufacturing process. It could be a problem with the backlight, because as far as I know, the screens are independent and don't utilize the same backlight.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
https://youtu.be/7XpASoy91dE
See the video.
aim1999x said:
https://youtu.be/7XpASoy91dE
See the video.
Click to expand...
Click to collapse
I see now. Does the signature show up or do neither of the options work?
I am not sure, but you could also try manually setting your clock and weather settings as well. It is definitely something software side.
Sent from my LG-H900 using Tapatalk
Inquisitor956 said:
I see now. Does the signature show up or do neither of the options work?
I am not sure, but you could also try manually setting your clock and weather settings as well. It is definitely something software side.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
Neither option work. Though like I said even though screen is dark if I swipe it to the left with main screen off the shortcuts do work. I want to think this is software issue, but then factory reset should have fixed it. With smart cover it will stay on for half a second and then go dark.
aim1999x said:
Neither option work. Though like I said even though screen is dark if I swipe it to the left with main screen off the shortcuts do work. I want to think this is software issue, but then factory reset should have fixed it. With smart cover it will stay on for half a second and then go dark.
Click to expand...
Click to collapse
Believe me, factory resetting a phone can fix many issues, but if 8ts a bug in the ROM itself, it won't fix that. It is a very strange issue, I admit. I don't know if the phone has a separate backlight for ambient display, but if the screen works when the device is unlocked, it should work when it is off.
My best recommendation for you is to exchange the phone if still under warranty. If you cannot do that, then perhaps try flashing another stock AT&T Rom. If you are unable to do that, then your best bet is to keep fiddling with settings to see if it gets fixed or not.
Sent from my LG-H900 using Tapatalk
Inquisitor956 said:
Believe me, factory resetting a phone can fix many issues, but if 8ts a bug in the ROM itself, it won't fix that. It is a very strange issue, I admit. I don't know if the phone has a separate backlight for ambient display, but if the screen works when the device is unlocked, it should work when it is off.
My best recommendation for you is to exchange the phone if still under warranty. If you cannot do that, then perhaps try flashing another stock AT&T Rom. If you are unable to do that, then your best bet is to keep fiddling with settings to see if it gets fixed or not.
Sent from my LG-H900 using Tapatalk
Click to expand...
Click to collapse
I did buy it on swappa. I do have the receipt from the person that bought it at att store (it was bought in december last year) however I am on cricket. I doubt att will help me. I may need to send it to LG as last resort. I was just hoping there is something else I can do. Could you point to a good guide regarding flashing a stock rom ? I haven't flashed anything in a while
aim1999x said:
I did buy it on swappa. I do have the receipt from the person that bought it at att store (it was bought in december last year) however I am on cricket. I doubt att will help me. I may need to send it to LG as last resort. I was just hoping there is something else I can do. Could you point to a good guide regarding flashing a stock rom ? I haven't flashed anything in a while
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-v10/general/guide-lg-v10-stock-firmware-to-stock-t3224170
I used this guide a quite some time ago when I was removing a rooted FW. I hope this can help.
I sent the phone to LG and they "repaired" it. They friggin replaced the lcd and obviously didn't test for the issue. It is still there. Question is should I return it again or should I try flashing it myself ?
aim1999x said:
I sent the phone to LG and they "repaired" it. They friggin replaced the lcd and obviously didn't test for the issue. It is still there. Question is should I return it again or should I try flashing it myself ?
Click to expand...
Click to collapse
Well, I flashed latest stock firmware using LGUP refurbish option and it didn't fix it. Does anyone have any other ideas ?
Well, I can tell you from experience that whomever received your device for repair probably didn't get all the information. He or she was probably told that there were issues with the screen and to just replace it, without anything else. This is what happens when you have a third party that doesn't understand much about the technology or the devices themselves transferring information between two points.
I can honestly tell you that if swapping out the display didn't fix your issue, there's not much to do about it. It's a shame though, because this is a great phone, and besides battery life, LG nailed pretty much every aspect of what a great phone is. I think your best best is to contact the original owner and notify them of the issue and work something out. Other than that, you can either keep using the device like it or switch to another phone.
Sent from my LG-H900 using Tapatalk