Related
Hello little birdies.
I am having an issue with my auto-brightness and I would like to know if anyone else has experienced this.
Whenever my auto-brightness shines through the power of the sun (goes to 100%) it seems to get stuck at full brightness and my already not so good screen-on time takes a dip and I always notice this too late . I use the quick settings widget which is preinstalled and the A for auto-brightness is set but when I click it the screen immediately lowers the brightness, while the A for auto-brightness remains, and a vain in my forehead pops.
Furthermore after checking badass battery monitor it shows that my screen is often at 100% sun shadowing brightness. Today it was at full mutated power the whole time. Anyone got an idea as to what could cause this? Anyone?
PS. You might have noticed in the text above that I think the screen is really bright when at full power and that I can see the screen perfectly during a warm ball-soothing sunny day.
Yes, I have a bug with auto brightness too. It seems to deactivate itself. I have activated it a couple of times and everytime it deactivate itself at 100 % after some use.
I have an international HTC One X with the latest 1.29.401.11 update.
Glad to know I'm not the only one. I will soon factory reset my phone to check if it magically gets better.
I noticed this last night. My phone was blindingly bright and I didn't understand why it was set to 100%. I set it back to Auto and so far its still on Auto. i will have to keep an eye on this.
HTC really need to fire the monkeys they have working as coders. I guess if their software is not fixed up in next couple of weeks there might be a whole lot of people, me included, who will migrate to the SIII (given of course that it doesn't have a gazillion bugs as well).
I've been trying all day to recreate the problem but ist not doing it. I put my phone in the sun, I tried using the camera app, I used the video app with its 100% brightness setting, but the phone is still showing Auto brightness.
Any ideas on what triggers 100% brightness?
I have the same problem with mine. It's just randomly turns off auto brightness
Sent from my HTC One X using xda premium
I don't know either what triggers it. It seems to deactivate at either 0 % or 100 %.
I don't have many apps installed, if I just do some web surfing and put it to sleep, when I wake it up the auto brightness is deactivated, in maybe 1 of 4 times. Irritating.
For whatever reason i haven't been getting the auto brightness bug for the past three days. Not sure how it resolved itself since I didn't get any software updates.
If you watch a video you can change the brightness and will stick and not go back to your original settings.
Sent from my HTC One X using xda premium
treebill said:
If you watch a video you can change the brightness and will stick and not go back to your original settings.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No, that's not the trigger. I investigated that on my phone and found no link.
I take that back. You are right! It seems the brightness setting in the movie play is the culprit. Although it doesn't always do it. One more thing for the chimps at HTC to fix.
Sent from my HTC One X using XDA
Yesterday the auto brightness bug kicked in right before my eyes. I was browsing the web in total darkness in bed, when suddenly I was blinded by 100% brightness. So it's not just the movie player brightness that causes this issue.
Sent from my HTC One X using XDA
Just got the autbrightness bug with the camera app. Everything seems to ****ing set it off now.. :banghead:
Sent from my HTC One X using XDA
Yeah. That's because the camera jacks up brightness for outdoor visibility. They need to have an option to disable that.
Sent From Mars
Hotzigetty said:
Yeah. That's because the camera jacks up brightness for outdoor visibility. They need to have an option to disable that.
Sent From Mars
Click to expand...
Click to collapse
I realize that, however it doesn't always do it. Also sometimes it will kick into 100% brightness without using the camera or movie player. It seems completely random to me.
mine is stuck at zero. started this morning and I did record a video actually.
auto just takes it.to zero.
but also, if i change it directly from the srttings menu, its not.effecting at all, just staying at the same previous custom level.
whrn using widget, just turns it to zero.
opened the video player, changed brightness level and its normal now. it was in the middle, the video brightness level
ok just edited this post and its malfunctioning again.. arrrgh!
Try an application that controls autobrightness, it should fix the problem. I would recommend Lux Dash.
So it is the widget, powertoggle.
Once I fix the issue by changing video brightness, it works fone, till I toggle the widget to use auto-brightness.
Several comments on PlayStore also confirms this with several phones.
Just don't use auto brightness from powertoggle. It is actually doffetent.from what OP describes, but.people may come up to this thread while searching, so I think it willbe useful to post here.
hxhx
i meet this problem
Auto brightness issue
I too had the same issue, i tried to resolve the problem with htc but unfortunately they said that it is a software but and we need to wait for an update....
ynischa said:
Hello little birdies.
I am having an issue with my auto-brightness and I would like to know if anyone else has experienced this.
Whenever my auto-brightness shines through the power of the sun (goes to 100%) it seems to get stuck at full brightness and my already not so good screen-on time takes a dip and I always notice this too late . I use the quick settings widget which is preinstalled and the A for auto-brightness is set but when I click it the screen immediately lowers the brightness, while the A for auto-brightness remains, and a vain in my forehead pops.
Furthermore after checking badass battery monitor it shows that my screen is often at 100% sun shadowing brightness. Today it was at full mutated power the whole time. Anyone got an idea as to what could cause this? Anyone?
PS. You might have noticed in the text above that I think the screen is really bright when at full power and that I can see the screen perfectly during a warm ball-soothing sunny day.
Click to expand...
Click to collapse
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
yap, I have two gnexs both have had this problem.
I can get a screenshot with vol-down + power
but the screen is totally black.
Yeah I've had this screen of death issue too. I've been trying forever to diagnose what is causing the problem. It happens on any kernel including stock. I factory reset, flashed stock images, everything.
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
i not have restaert using apk franco updater and set :good:
The sudden battery drop is normal when you pull out the battery. Basically, the phone loses it's calibration on the battery capacity. And that " auto charge" is your phone slowly trying to get a better estimate of your phone battery capacity.
Sent from my Galaxy Nexus using Tapatalk 2
I believe that SODs are a common problem faced by many on 4.2 i personally havn't faced it yet =] running arhd with ak kernel
I was able to reproduce this using Velis Auto Brightness https://play.google.com/store/apps/...SwxLDEsImNvbS52ZWxpcy5hdXRvLmJyaWdodG5lc3MiXQ
After messing with the brightness it wents black screen.
I'm sure this has to do with the autobrigtness!
Best regards
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
klobkelosh said:
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
Click to expand...
Click to collapse
I think you just helped me pin it on animation off. I have had the black screen happen to me 3 times in the 3 days that I disabled animations (stock rooted ROM, developer options). I kept trying to find an app that caused it but the animation off matches the start of my problem.
EDIT: Well, animation off isn't the cause since I just had another black screen.
simms22 said:
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
Click to expand...
Click to collapse
Totally agree with you!happened to me many times too,especially when crashing after tweaking\benchmarking.
I'm generally loving 4.2.2, but there's one issue I've noticed since updating. When I close my smart cover, the screen will usually turn off like it's supposed to do. But every once in a while, it will immediately turn back on at maximum brightness, then turn off properly after a few seconds.
My first thought was it was an app trying to update. But the fact it jumps to maximum brightness makes me think it might be system related. Anyone else having this problem and/or have a solution? Could some variation of this issue be contributing to the power drain some are seeing?
In the interest of making things easy for those who are holding off on the KitKat OTA, I thought it might be a good idea to consolidate all of our experiences into one thread. This is intended to cover mainly the changes specific to this OTA over Razr M-flavored Jellybean.
I'll start with my experience/thoughts and edit in additional findings. (Note: I'm bootloader locked, and now unrooted.)
The Good
The UI is definitely smoother. It doesn't jitter or stall under heavy usage anywhere near as much as it did in Jellybean.
Battery life when the phone is asleep seems to have been improved a little.
USB audio out is now supported.
The occasional "screen jitter" that plagued the Jellybean build is gone.
KitKat's Quick Settings panel is quite handy.
The native lock screen now supports adding, removing, and rearranging widgets.
Although it can't be installed from the Play Store, the Google Experience Launcher can be sideloaded and works just fine.
The Neutral / Very Subjective
The AOSP keyboard has changed; the keys are smaller and, in landscape, very squashed. You may need to adjust to it (I'm trying, but it's a struggle) or find a replacement.
Battery life when the phone is actively in use has not been noticeably improved in my experience; but it hasn't been noticeably worsened, either.
There's now a shortcut to the camera from the lock screen, which can be used even if the phone is locked by a pattern/PIN/etc. (Great if you're a shutterbug; not so great if someone else decides to troll your Dropbox/Drive account.)
The Google Camera app works - but Photosphere can't be used, as the Razr M doesn't have a gyroscope.
The Bad
No more root, for those with locked BLs (me). (Saferoot fails, and many users are reporting losing root even when they try survival methods.)
Wi-Fi tethering via most apps (e.g., FoxFi) has been blocked, so now you must pay your carrier for the feature unless a new workaround is discovered.
All notifications I've seen so far now flash the notification light white, instead of unique colors. This may be frustrating for some who used the colors to decide whether to check the phone immediately or later. (Luckily, there are ways to address this.)
The Blur launcher is same 'ol, same 'ol. It uses a solid black background for the soft keys and notifications bar (rather than taking advantage of KitKat's transparency support), and it still has that Quick Settings menu on the left (which is redundant now). In addition, Holo Launcher (which I was using) doesn't account for the space used by the softkeys at all, making it difficult to use. (I've switched to Nova Launcher, which is working fine.)
I've experienced some weirdness with the application switcher. Sometimes it drops me to the launcher right after displaying the list, and sometimes apps will overwrite another's position on the list, or be dropped from the list entirely without reason (this is always temporary, however - just bring up the switcher again).
Some apps can no longer write to the SD card - or at least not wherever they please. We still have the Files browser, mercifully (but I favor Total Commander anyway, which seems to work perfectly).
The audio quick switch on the lock screen has been removed. Also, the buttons for entering a PIN are smaller.
(Leraeniesh) Under heavy usage, the Razr M may get hotter under KitKat than it did under Jellybean, and may drain the battery more.
(GPIX) Some users have noticed decreased network performance in some apps, such as Chrome or YouTube, while on Wi-Fi and with Wi-Fi power-saving enabled.
(GPIX) Several users have reported popping noises - when a sound begins to play, or in the middle of playback. (I haven't experienced it, however.)
Swype is no longer included. If you used it in Jellybean, you will need to purchase it on the Play Store after taking the OTA.
(ls3c6) Some have encountered problems with sharing the address book to paired devices over Bluetooth.
My opinion, overall:
It's a nice upgrade, but all of little problems I've encountered (bugs, Verizon blockades, the works) make this feel like a bit of a letdown after the 6-month wait. In the end, after just three days, I find myself wishing I could take the phone back to Jellybean.
Here's hoping for either some exploitable holes or maintenance updates.
My opinion
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
Worth noting that I am using an unlocked bootloader, with CWM and SuperSU (only really did this to remove VZW bloat and install Xposed)
Leraeniesh said:
So I popped my sim back into the XT907 for the weekend, and heres what I've noticed (when compared to 4.1.2).
Higher temps - previously, my XT907 hovered around 85F-100F, but with 4.4.2, I've noticed it drift toward 110F with 5+ minutes of active use.
Worse battery life - On 4.1.2 I averaged around 20% after 16 hours moderate use. With 4.4.2, I'm averaging around 5% in the same span.
Lesser LTE coverage - This may be something with my area, but I can usually get 2-3 bars of LTE in the Livingston County area on 4.1.2 (I've noticed the XT907 accel in this category). While on 4.4.2, I could not get any LTE coverage in the same area, and could only find it within more populated areas.
Slower performance - I'll always be amazed by how quick the XT907 was on 4.1.2, beating out devices with similar specs in the same price category. With 4.4.2, I've noticed frame drops, stutters, and random reboots be a common occurrence over the last few days of usage.
Overall, I'm satisfied with 4.4.2, but I still prefer the overall usability with 4.1.2.
Click to expand...
Click to collapse
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to show more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
ATTACK said:
On 4.1.2 the "signal bars" were calculated by a xml in, I believe, SystemUI.apk. You could simply adjust the figures to show more or less bars, which Moto adjusted to so more. But having no LTE maybe a bad radio or a problem stemming from a bad flash. My Razr M doesn't get hot, no random reboots, and battery life seems to be the same. I haven't had any problems on KitKat.
Click to expand...
Click to collapse
Gonna be doing some more testing in that regard. Even my M7 with its garbage radios gets LTE just about everywhere in the Metro Detroit area.
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
I have had the KitKat OTA now for 2 days and haven't found anything major wrong. The changes to the keyboard bugged me but I use swiftkey so that was moot. I also have an issue I haven't seen listed yet. The new sound for screen taps....it seems to give that "popping" feedback (that ive seen listed as an issue on driver start-up) ALL the time. I maybe get 1 clear sound out of every 5-6 screen taps. That is the only real "problem" I can find as of this point though. Does anyone have any insight on that?
Also activated Dev Mode and changed to ART runtime. Might be placebo but app response seems to be noticeably better! Not groundbreaking by any means but better than 4.1.2 for sure. Overall I am happy with the upgrade. Rather, will be happy once a root exploit comes up (I miss my debloating! On that note though, disabling apps never seemed to work right with 4.1.2....after hitting disable the app would show back up in active processes after a short time. Now I've gone 24 hours and 3 phone reboots and that damn NFL app is STILL disabled and NOT running as a background process. Might just have been an issue with my phone in particular before, but its fixed now!)
I am generally happy.
It fixed all the issues I had with Dhackers KitKat.
and feels about the same once you have rid of all the Bloat.
I like and I am happy that we still surprisingly got the update unlike the Galaxy S3
Happy =)
Just wanted to comment on the heat issue mentioned above:
I have only had KitKat for 2 days but I have definitely noticed a difference in heat after extended use compared to JB. One of the things I really liked about my Razr M was lack of heat so hopefully this is a fluke and I wont notice it too much in the future.
---
With that said, no big issues.
I don't like the keyboard -seems smaller, or something, The heptic feedback seems to be different too (for the worse IMO).
The lockscreen number pad seems smaller - definitely liked the number pad from JB.
I had to change the messaging app (hated the all white/lack of contrast). Using "8sms" if anyone is curious.
I also changed launchers to use the google-now launcher so the "okay google" thing would work on the homescreen and also get the transparency notification bar. But, in doing that I did lose the circle widgets which I liked. Can't win for losing sometimes...
---
On a positive note, Chrome/google searches seem to be much faster. The UI seems about the same (no complaints with JB).
If battery life can increase then I'll be satisfied with update (so far, no difference).
My experience has been very positive. My phone was bootloader locked and not rooted before (and, of course, after) the OTA. I cleared the cache partition from the recovery menu post-install but have not done a FDR. General impressions:
-- UI is overall much snappier/quicker. Extremely noticeable.
-- Love the new quick settings panel that you can get to after pulling down the notifications shade.
-- KK's changes to how the SDcard works have not been a big deal at all for me. The native "Files" app seems to have complete read/write access, as does ES File Explorer.
-- Like the new clock feature to automatically add a "home" display when traveling outside a pre-defined timezone.
-- Hate the new way you set the alarm on the clock. (Really, whoever came up with that input method should be transferred to a department where s/he can never affect design decisions again.)
-- I miss the audio silencer/mute on the lockscreen.
-- Battery life has been interesting. When I first installed the update (morning of 05/15), battery life was definitely worse, probably by about 50%. It has gradually been getting better, however, and now is probably only about 20%-25% worse than JB. Why it would change I have no idea, but it definitely is (I've been keeping notes, and am sure it is actually happening). I have noticed, using the Battery History details screen, that there are a LOT less wakelocks in KK than JB. In JB, I used to see tons of "Awake" indicators on that screen that did not pair with "Screen On" indicators. In KK, there are very few incidences of "Awake" that are not paired with "Screen On." Someone smarter than me will have to explain how that translates into worse battery life.
-- It may be my imagination, but it seems like the battery charges faster w/ KK. If it's not my imagination, I wonder if that means that the apparent decrease in battery life is really an issue of improper calibration/accuracy.
I have not experienced some of the things others have reported:
-- No random reboots.
-- No changes to WiFi or 4G signals. I don't use Bluetooth so can't comment on that.
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
4039995825
GPlX said:
So far my experience with 4.4.2 has been positive. I agree with OP's list and would like to add these under the issue category.
ISSUE:
Decreased WiFi effectiveness/throughput - There is a noticeable decrease in performance on apps like Youtube and Chrome web browser.
Audio Popping noises - Some experience a popping noise when the sound driver starts up while others experience it during playback.
Click to expand...
Click to collapse
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Nidstang said:
-- No popping noise when using audio. (Note: I have seen some reports in other forums that a FDR fixes this issue for those who have it.)
Click to expand...
Click to collapse
Attempted a FDR on my phone, unfortunately it did not work for me. I will attempt to clear the cache partition to see if that may help the issue if
possible. So far i can only get the boot menu for a couple seconds and im lucky to get a selection in time.
EDIT: I cleared the cache partition, no effect. (NOTE: it seems to get into the recovery menu after selecting it at boot menu, you have to hold power & vol UP for a couple seconds)
crazy4android said:
go into wifi settings...in the setting "uncheck" the box "wi-fi optimization" it made my WiFi significantly better..
Click to expand...
Click to collapse
That is an excellent point. I'll shut off the optimization and will edit my results in after tinkering with it for a while.
EDIT2: Without doing speedtests etc. It is very noticable that the wifi has improved. Youtube & other apps load as fast as they did on 4.1.2
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
kashif87 said:
I'm on locked BL, definitly non root, and I happen to installed MotoCam from a store n IT DID INSTALLED. .
Opens up, takes pictures beautifully. .
Only problems are the slide in menu is glitchy AND after taking HDR pic, cam UI is not there. Only live cam feed.
Other than these issues, it's playing nicely ESPECIALLY auto HDR does work, surprisingly!
How can I make those problems go away??
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
maybe you can uninstall updates to the cam in apps
bwer1233 said:
Haven't looked into it so this MIGHT be a feature of the Google Now Launcher I installed, but I JUST noticed if you swipe down from the clock area of the new lock screen, you can add widgets! Am I crazy or is this a new feature on our phones? If so, LOVE it! Helps mitigate the loss of the quicklinks from our old 4.1.2 lock screen.
Click to expand...
Click to collapse
Lockscreen widgets were introduced in Android 4.2.2.
Just want to let people know that the Google Now Launcher is working great on 4.4.2 including the "ok Google" functionality.
You can't download it from the play store. I just grabbed the apk from this thread.
http://www.xda-developers.com/andro...-and-gpe-devices-apk-mirrored-for-all-others/
Sent from my XT907 using Tapatalk
rooted + cwm
can't use "memory" feature under settings, while calculating settings app would crash
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
tieuvienson2005 said:
how can I go to hiddent menu? *#*#4636#*#* is failed until my M get kk updrade...
Click to expand...
Click to collapse
There are many "phone info" apps in the Market. Or create the short cut with Activity Launcher.
Also the Cam sucks on my Wife's m so get the Lenovo from my Moto x signature link.
Hell0
Getting vertical lines on smt700 non rooted after over the air update (U.S)
After update I did a factory reset installed apps One by one and I started to notice a flicker of VERTICAL lines appearing at start of boot and also when batter is low it will freez slightly and do the vertical line thing before freezing a little then shutting off..
this only also with games...
Thanks a lot..
-AHMED-
My sister noticed an occasional black screen flash after updating her Tab S 10.5 to Lollipop. I have the same model upgraded to Lollipop and have never experienced this issue but twice, once on KitKat and once with Lollipop I saw part of the screen look scrambled (like an old set tuned to a channel that WA not in range), for a second after hitting the home key.
Sent from my SM-T800 using XDA Premium HD app
Green flicker
Smt700 wifi screen flashes green and gets vertical lines....
Sometimes when the screen does this flickering it restarts...
-Ahmed-
My 10.5" T800 has been on for over 200 days and has never been turned off or rebooted since i got it, no problems at all with flickering, but the older you get the less sensitive you get, I am not a gamer so my tablet is not stressed.
If you are having problems get your tablet repaired or replaced.
John.
I ve the same issue after upgrading to lollipop, I cant find the solution
Still flickering
try everything to solve this flickering with vertical line issue.
Nothing worked..
Factory reset, disable hardware overlays and limit performance ultimately won't fix this issue...
I have the same issue.
Downgrading does not solve the problem
I have seen that it happens when battery is lower than 50%.
To mitigate the problem I have set seen brightness to 30% fixed and also losing mobile segnala makes the screen flicker or the tablet to reboot
When you rotate the tablet do the vertical lines rotate as well.
John.
All problems started only after lollipop update.well most of us are getting them,,random reboots,green flickering lines,grey bars etc,,
But the only available solution for flickering Is turning the power saving mode on which is what I have done
iam facing this issue with my t705
its not the lollipop fault
its an hardware problem, the battery connector socket
This happened to me before and after the lollipop update. Someone suggested to use power saving mode to restrict CPU usage. It seems as if the tablet goes crazy whenever theres a high cpu load involved.
I have the same problem after update to lolipop. Most often occurs when there is a lot of notifications and low battery.
In my opinion is a software problem, what do you think ?
edit:
8% battery, lot of vertical lines during using notifications center, tablet reboots - this never happened before (on 4.4).
[SOLVED]
Fixed screen flickering issue !!
did this by governing the frequency to not pass more than 1.6 ghz...
Rooting then installing overclock widget and setting frequency to not pass 1.6ghz. Max..
From what I know about chips ''they are not all baked alike'' the same chip could come out with lower stable frequencies ..
I hope this helps someone for it has 100% solved the screen flickering problem for my smt700...
Thanks...
-Ahmed-
I found this, might be worth a try.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
Tinderbox (UK) said:
I found this, might be worth a try.
http://www.problogbooster.com/2014/06/on-screen-display-flickering-error-android-xda.html
John.
Click to expand...
Click to collapse
My relative has complained of an odd flicker (screen goes briefly black) after updating to Lollipop. Usually happens while moving from an app to the home screen. I sent them instructions based on that article so they can test if it fixes their issue. I'll post the results but likely after a few days to make sure it actually works. Oddly enough I have an identical model SM-T800 on Lollipop and do not have the issue that they find so annoying.
Thanks for posting the article.
Sent from my SM-T800 using XDA Premium HD app
I've seen it on mine since Lollipop came along. In my case I get the screen with snow - like a TV tuned to a channel with no signal - . It's happened when the screen was timed out and then awakened. I've not been bothered by it more than about 5 or 6 times so I've just not bothered with doing anything about it.
Sefto said:
I have the same problem after update to lolipop. Most often occurs when there is a lot of notifications and low battery.
In my opinion is a software problem, what do you think ?
edit:
8% battery, lot of vertical lines during using notifications center, tablet reboots - this never happened before (on 4.4).
Click to expand...
Click to collapse
Video:
https://www.youtube.com/watch?v=4iBDVirN_XM
Service center in Poland (CCS) replaced screen and repaired motherboard. It seems to be fixed.
I thought it was a lollipop issue, but having followed the advice to force GPU screen rendering through developer options, I found the problem did not go away. Thus, it must be a hardware issue.
corvus.corax said:
I thought it was a lollipop issue, but having followed the advice to force GPU screen rendering through developer options, I found the problem did not go away. Thus, it must be a hardware issue.
Click to expand...
Click to collapse
Hello,
Did you try to set the default CPU frequency to 1.6 ghz... maybe even try to govern it down to 1.4ghz.
For my WiFi smt700 simply underclocking the cpu completely fixed the issue...
The issue is due to either your tab cpu wasn't from a set baked that could handle Higher work loads or quick raises in frequency like from sleep or switching between apps.. forcing GPU rendering take away resources from cpu and forces the GPU to do the work.. Hopefully an official kernel update could help with this in the future...
But for now under clocking the cpu or force GPU rendering or powersave mode all appear to help resolve the screen flickering issue and the only constant that I can determine is that these fixes all involve taking away workload from the cpu...
UNDER CLOCK FOR NOW !!
Thanks... (hope underclocking helps some members here)
-Ahmed-
Sent from my SM-T700 using XDA Free mobile app
That's interesting. Unfortunately, my device is not rooted yet and I don't plan to do that in the near future. So while I can use powersaving, I can't underclock. If there is a problem with the quality of the CPU, then IMO Samsung owes me a fully working device. I mean, they sold the device with the idea it was able to run at correct speeds.