Related
I've looked all over for anything on this topic, so please forgive me if it has been discussed before. My daughters kf shows everything on the screen in inverted colors, kinda like a photo negative. I.e. Black is white, white is black, etc. It did it on the stock kf rom, but went away for some reason. It started to do it again so I thought I'd take the plunge and loaded the Reloaded ICS rom. Followed the directions and everything works as it should. But the colors are still messed up. I've tried going back to twrp and I wiped cache, dalvik. Even factory reset after none of that worked. Anyone have any ideas on fixing this? I'm desperate. Thanks in advance.
Sent from my Xoom using XDA Premium HD app
Could just be a display defect, I would restore it to full off-the-self factory and talk to Amazon.
Sent from my Amazon Kindle Fire using XDA
For future reference, if your device (ANY device) is 100% stock and is showing a problem, even if it's not a hardware issue, the WORST thing you can do is make with the flashing. You should have skipped straight to talking to Amazon about repair or replacement.
It was stock, but rooted. It did it for about a day the first time then returned to normal. Probably a month later it started it again and hasn't gone away. Was just trying to fix it and avoid the hassle.
Sent from my Xoom using XDA Premium HD app
Flash the most recent update from Amazon, clear out your sdcard and send it back. The worst thing they could do is not fix it, but that's unlikely.
Mine is doing that looks like a negative what do I do to fix it
Fixed it
just corrected it. go to settings > accessibility > invert colors. Turn this OFF.
Had a similar problem, went to settings > display> blue shade , tapped it off , hope this helps
You shouldn't have to factory reset for a color issue. To fix... Go to settings. Click on accessibility and check it color inversion in on... turn it off and it will return to normal
I'm still relatively new to rooting, so please forgive my lack of knowledge of terminology and such. I decided to give MIUI a try and flashed it on my phone. It was buggy, but not anything too crazy. Two nights ago, I flashed the newest update for it and ever since, the vibration when I touched the soft keys and when I entered my unlock pattern has gotten significantly weak. I went into the settings and changed the vibration level to strong but it did nothing. It was really bothering me, so I did a data wipe and flashed the latest build of AOKP. The vibration is still weak when I touch the soft keys and unlock pattern. I also have the stock ICS lock screen set up too, but when I slide the ring to unlock the phone, the vibration is normal again. I went into the device settings and changed the vibrations settings, but that didn't do anything either. I did a data wipe, wiped the dalvik cache, formatted the system and reinstalled the ROM, yet it's still the same. Is there a way to fix this? Sorry for being so long winded, I hope it made sense lol Thank you for any help
Did you drop the phone or cause any other physical damage to the phone? Because any control over the vibration would be reset after installing a new rom/wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
AyyEmBee said:
I'm still relatively new to rooting, so please forgive my lack of knowledge of terminology and such. I decided to give MIUI a try and flashed it on my phone. It was buggy, but not anything too crazy. Two nights ago, I flashed the newest update for it and ever since, the vibration when I touched the soft keys and when I entered my unlock pattern has gotten significantly weak. I went into the settings and changed the vibration level to strong but it did nothing. It was really bothering me, so I did a data wipe and flashed the latest build of AOKP. The vibration is still weak when I touch the soft keys and unlock pattern. I also have the stock ICS lock screen set up too, but when I slide the ring to unlock the phone, the vibration is normal again. I went into the device settings and changed the vibrations settings, but that didn't do anything either. I did a data wipe, wiped the dalvik cache, formatted the system and reinstalled the ROM, yet it's still the same. Is there a way to fix this? Sorry for being so long winded, I hope it made sense lol Thank you for any help
Click to expand...
Click to collapse
Probably because of the kernel. That's my best guess. Flash trinity kernel and see how the vibration is for that one.
did you flash miui.us or miuiandroid? have you tried to flash any different roms since this issue started to see if its a rom issue or hardware issue?
theking_13 said:
Did you drop the phone or cause any other physical damage to the phone? Because any control over the vibration would be reset after installing a new rom/wiping data.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I didn't drop the phone. Held it in my hand the whole time I flashed MIUI
sd0070 said:
did you flash miui.us or miuiandroid? have you tried to flash any different roms since this issue started to see if its a rom issue or hardware issue?
Click to expand...
Click to collapse
I flashed miui.us, but I thought the faint vibration was a result of the miui update so I wiped and flashed AOKP 39. I still have the faint vibration when I touch the soft keys or enter my unlock pattern. However, for everything else it vibrates normal.
If you haven't dropped your phone, then probably it's the kernel. Haptic Feedback sometimes lessens on certain kernels. Try flashing another one.
I flashed Trinity kernel with 1536MHz CPU And 512MHz GPU clock. I wasn't sure which one to pick so I just chose the one at the top of the list. Anyway, since doing so I can't change any settings under the device options, except for 'color hack presets' Everything else is grayed out and I can't select them. Is there something I missed or should've done? I didn't wipe data or the dalvik cache, because I read that it wasn't necessary.
I think Trinity is not compatible with MIUI, which follows CM team very closely.
Sent from my i9250
bk201doesntexist said:
I think Trinity is not compatible with MIUI, which follows CM team very closely.
Sent from my i9250
Click to expand...
Click to collapse
I couldn't deal with MIUI anymore, so I flashed aokp b39.
I use paranoid android 2.99 and Trinity a4, sometime when i didn't use my phone and i lock the screen, and i wanna turn it on again, the phone won't response. The only way that i can turn it on is by pulling the battery out, i can't help but wonder Ida's it a hardware or software issue?
Sent from my Galaxy Nexus using xda app-developers app
Have you tinkered with kernel settings? Lowered voltages? Changed governors?
Have you tried a different kernel?
cupfulloflol said:
Have you tinkered with kernel settings? Lowered voltages? Changed governors?
Have you tried a different kernel?
Click to expand...
Click to collapse
nope, I'm too scared to do that, i just change the screen color, besides, i have already uninstalled it, it's too risky i don't wanna mess up with my gnex
Go back to stock. If it still does "whatever", then it's hardware, most likely. Common sense.
Sent from my i9250
maybe try default setting for the screen.
Trinity a4 has sod issues. I didnt have any but many did. Your phone is fine (most likely) just flash another rom or kernel.
Change kernel.
Sent from my Galaxy Nexus using xda premium
I have a similar problem with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems.
Sent from my Galaxy Nexus using Tapatalk 2
nomad4ever said:
I have a similar problem with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
i have exactly the same problem... now im on cm10 and it happen less than before, but the issue is still there..
when did your problem start?
i dont know if it is a hardware or software issue, because with some stock roms happen a lot more than with some custom roms.
is there any difference between flashing using toolkit or odin?? if i wanna go back to stock, but i mean totally stock, toolkit or odin are exactly the same??
btw, this freeze that for some people happen "only" when the phone is in lockscreen it's exactly the same issue of the blank screen, the only difference is that you haven't had the the crash in your face XD... but it is the same.
I had it since 4.2. Also the occasional reboot. Before my Nexus never rebooted or locked on its own since March this year.
Sent from my Galaxy Nexus using Tapatalk 2
I finally rooted it yesterday and it now is very unresponsive at times. It will get to the point where it's frozen for about 30 seconds before it does anything. I flushed the caches and did a reset, same thing. So I flashed Jedi ROM on it. It's a little better but still has moments where ti freezes for a time. Is there a fix for this?
Rooting does absolutely nothing to the performance of the device. Its comparable to giving yourself admin rights on a windows computer. No performance change just extra features. Might want to check any apps that you installed after rooting
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
marksm said:
I did not install anything after root.
It works smooth as silk with the stylus. Possible sensitivity adjustment?
Maybe the sdcard needs to be reformatted?
Click to expand...
Click to collapse
ROOT will not brake the phone or cause lag. it changes nothing internally except rights to your phone. no tweaks or files deleted. I can see it being something with the screen since you say the pen works great and using your finger I assume it micro stutters. but even the freezing for 30 sec does not sound screen related. I would wipe and format data, and then try another Rom. I used jedi from the first build all they up to 15 and it ran like a champ. its something you are doing, or have not undone yet.
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
rangercaptain said:
I would suggest clearing caches. Its got nothing to do with rooting, but neither does rooting have to do with lag.
It sounds like an app was restored with data.
Click to expand...
Click to collapse
Agreed....
Excellent point ranger.....TY.....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
no apps were restored either. When I flashed the new ROM I cleared every cache I could see listed and wiped it clean. All I can think of is the old stuff on the sdcard is causing issues so tomorrow I will reformat it and reset again.
Well then, the only thing I can think of is you flashed an incorrect kernel. What exactly did you flash?
Used the root tool from http://galaxynote2root.com. Odin and cwm6-root-note2.tar.
It still had the bad lag and freezing after I un-rooted it and restored the original ROM.
I have since flashed Jedi, didn't like it and now am on NOTEorious Prime.
What I have noticed is that the lag and freezing go away when I am connected to a wireless network. Maybe it screwed up my modem?
And have you verified the APN settings as being correct ?
Or they may simply be mixed up by default..
It may be set on ATT LTE.....instead of ATT PHONE for example...
Both will work...but one will drop the network speed by about 70%...
Just a thought....g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
Perhaps a factory reset from within recovery --- to make all settings default. By now there's a lot of stuff floating around in there.
Why would the original root change the APN settings.
I have factory reset several times. Even with the factory image applied fresh, it still freezes. The weird thing is, it responds just fine to the stylus.
I am at the point where I restore the stock ROM again and take it to ATT to see if they will swap it out.
Thanks for the help, keep the ideas coming..
Flashing a custom rom or recovery or kernel voids your warranty. Please don't tell us about plans to return the phone to at&t. The phone worked as expected before you began flashing.
It's not the radio or wireless either. It works perfect with the stylus but seems like it doesn't detect my finger to operate normally. Does Samsung have a tool to reset the display sensitivity?
There is a dial code for the touch screen. I don't know it, but I've found those codes by googling 'android secret note 2 dialer codes' or something like that.
Looks like I have it fixed.. It's working right since I followed the instructions here http://android.stackexchange.com/questions/39423/galaxy-note-10-1-does-not-recognize-finger-touch
I had installed swiftkey so I removed that and tried swype beta and it's all good now.
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
marksm said:
I restored everything back to stock and it is still having problems. The screen is unusable with my finger, I have to use the S Pen for everything.
Would reloading the stock ROM with kies be different than using Odin? Does Samsung put some key piece of code in the areas that get changed with rooting?
I am at a loss..
Click to expand...
Click to collapse
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Bajanman said:
Ok to test you touch screen etc. type this in code in your dialer *#0*#!!
And don't think Sammy would put something in there, to make there phones not work correctly!
Me 2¢®
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
Click to expand...
Click to collapse
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
marksm said:
On the test screen, I have to tap screen many times until it finally registers. Then I drag my finger around for about 30 seconds before it starts picking up and filling in the boxes. It will finally let me fill in all the boxes and say it passes but it takes a lot of effort.
Click to expand...
Click to collapse
Yeah it's not suppose to be that difficult honestly. Something is defiantly wrong!!
Me personally if you bought the phone from an AT&T store! I'd reborn it for a replacement! And if it's not used from someone off the street. Then I'll put it back to fully stock, reset flash counter. Then return and replace at one of there local service centers. Especially if it's giving that much problems as it sounds to be doing. Seems as if the screen has some hardware issues inside...
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4
I need some help guys. I received the OTA update from Sprint with my stock firmware and it totally made my phone unusable. It keeps freezing and then rebooting. I have tried everything i can think of but nothing helps.
I did i full factory reset about 3 times. 2x with the zerolemon battery i was using for the last 2 years. Then another factory reset using the stock battery that came with the phone, which didn't get used more than about 5 recharge cycles before I replaced it with the zerolemon one.
After that I thought i could undo the patch but as you guys know the QI5 firmware is not backward compatible so am i kind of screwed? I have tried rooting and loading a custom rom, the CMDMOTO is the only one I tried since it seemed to work for others using the Qi5, but i still have the same issue.
I am a bit new to the rooting world but i have been reading up to figure out my problem, any suggestions? I have TWRP, super user and titanium backup.
Thanks
Work around FOUND !
Installing the app 'Wake Lock' and using level 4 'PARTIAL_WAKE_LOCK' seems to have made everything better. I will keep this thread updated if something else happens. I guess for some reason the last patch changed something that made the cpu go inactive or sleep much more frequently or something like that.
If anyone knows how to correct this let me know. It seems that this was actually a very common problem with the other variants of the note 4 it just took a while to get to this version. I wonder if anyone else was having this issue with the N910P.
Cheers
Have you tried booting to recovery and wiping the cache partition? If it falls asleep and freezes that points to a kernel issue if I'm not mistaken. Wiping cache will NOT delete any of your data. Hold Volume Up, Home, and power til the phone turns on and you see some yellow/blue/red text in the upper left corner then release. Try wiping cache and see if it helps
lazy_dingo said:
Have you tried booting to recovery and wiping the cache partition? If it falls asleep and freezes that points to a kernel issue if I'm not mistaken. Wiping cache will NOT delete any of your data. Hold Volume Up, Home, and power til the phone turns on and you see some yellow/blue/red text in the upper left corner then release. Try wiping cache and see if it helps
Click to expand...
Click to collapse
When I did the factory wipe from the 3rd time onward I always wiped the cache and all other options that were available. As long as i keep the wakelock app active the phone does not freeze up and/or shut down but it is draining my battery pretty fast. I am thinking it has something to do with the phone going to deep sleep and unable to come out of it properly. I am playing around with 'Kernel Auditor ' to see if i can find a setting that will fix this issue. I am almost convinced it has something to do with the cpu clock states and Deep sleep not working correctly anymore.
I personally am a fan of 3c Toolbox for most of my diagnostic needs. Theres a free version available, check under the cpu manager tab for whatever info is relevant to you. Example..it will tell you live cpu frequencies/load, live power usage, wakelocks, all sorts of goodies
Have you tried to ODIN a factory .tar image?
sammobile dot com has the QI5 image. Just make sure tou grab the sprint one and not the unknown carrier version.
maluconfusion said:
Installing the app 'Wake Lock' and using level 4 'PARTIAL_WAKE_LOCK' seems to have made everything better. I will keep this thread updated if something else happens. I guess for some reason the last patch changed something that made the cpu go inactive or sleep much more frequently or something like that.
If anyone knows how to correct this let me know. It seems that this was actually a very common problem with the other variants of the note 4 it just took a while to get to this version. I wonder if anyone else was having this issue with the N910P.
Cheers
Click to expand...
Click to collapse
Thank you so much for posting this work around! My Wife's Note 4 has been working great for over a year, she bought it used. Then a few weeks ago a bunch of updates were pushed to it and it just started to act up.
I narrowed it down to always occurring after the phone was idle for more then an hour or so and started to look for a clue if this may be a known issue so your work around makes a lot of sense.
It does appear to be an issue with Googles 6.0.1 OS version since my BlackBerry Key 1 also received a bunch of updates but its fine.