Hi all, thanks in advance for any assistance you can provide me. I have looked for similar posts but could not find any (maybe I just don't know what my issue is called). I bought an HTC EVO 4g LTE from a friend that had put meanbean on it (I assume it was the latest). I went through all sorts of steps loading twrp and getting s-off and whatever else I needed to do to load cyanogenmod 10.2. I was able to do this fine but the gapps I loaded would not show. I tried it together and separately and nothing would work. So I loaded (I believe) 3.16.651.3_stock_rooted_odex_CPTB.zip so that I could use my phone again with the gapps while I was waiting for some assistance on the cyanogenmod forums, which never came unfortunately. Everything was fine for about the past 10 days.
Today I used my phone all day and had no problems (extra info: I installed one app to access my bank info which went fine), but hours later and all of a sudden my screen basically got stuck. It looks like millions of randomly chosen colors for each pixel. The screen will turn on and off if I hit the top button (or let the display "timeout"), and I can hear the tones when I press the up and down volume buttons. This is telling me it's not bricked, but it is completely useless to me as is. When I reboot the phone, I don't see anything on the screen until the colors come up (which is after the vibration during the bootup sprint screen as far as I know). I was able to get fastboot to see it once but haven't been able to get back into the bootloader (there's nothing on the screen so I don't know what I'm doing).
Basically, nothing on my screen while it is booting up until it gets to the point where my laptop detects the USB connection, and the crazy colors comes on. BTW, as random as it seems, it's the same colors in the same exact position each time and it never changes. I haven't tried flashing any roms with fastboot because it seems my issues is bigger than a rom... I can't even see anything when I had it in the bootloader... This is my only phone and I use it every day. I'm really quite desperate and could use any and all help you're willing to provide. I've attached a zip with a picture of my screen so you all can see what I'm talking about. Thanks in advance...
just an update, got my laptop to see my device with fastboot so I'm gonna leave it hooked up. Could really use some advice on how to proceed because I'm at a loss. Thanks...
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
So can you say with any certainty that my issue is not due to the programming on the phone?
Magnum_Enforcer said:
From what I've seen in the past, it looks like the digitizer in the phone is bad. If you're good with your hands you can replace it yourself.
Sent from my HTC M8
Click to expand...
Click to collapse
I just thought I would see a similar screen in the bootloader if it were a physical hardware issue.
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Magnum_Enforcer said:
I'm basing my information off of previous posts with the same type of picture, and the replies that followed. All of those posts suggested that the digitizer was bad and that the issue was not software-related.
Click to expand...
Click to collapse
Okay great thanks for the reply... the touchscreen portion of the phone still works (I was able to answer a phone call today even though I couldn't see where I was touching). I saw some videos online so I'll watch carefully and order a new screen/digitizer or whatever. Thanks again
Related
Hey guys,
I ve recently started having trouble with the Touchscreen on my Evo 3D. The phone is fully rooted and S-Off, currenlty has Leedroid ROM 3.0.
Ive noticed that sometimes it will just stop responding. I press the power button to turn the screen off and back on again, then it works fine.
Other times it will be as if the screen has already been touched in 1 place (even though i havent touched the screen). If i touch the screen it detects a second finger and tries to pinch zoom.
Recently its gotten worse and now certain parts of the screen wont work at all, but other parts work perfect. For example, i can pull the notification bar down or even use the capacitive buttons at the bottom (Home, Menu, Back & Search).
The phone has never been dropped, I have removed screen protector and case, removed apps, defaulted phone, tested different ROMs, and removed the battery for a while. Nothing has helped and im only surviving right now by using Softkeys.
Has anyone seen this, or know what it could be?
Haven't had this problem myself but something to try would be to calibrate thr screen threw the phone options snd see if that helps at all.
Locked & Loaded
""shooter on Deck""
Long time lurker, first time poster, so pardon the n00b.
I am having the same issue. I was using Revolution HD (which is a phenomenal ROM if I say so myself), and a week or two ago my phone started having that issue. I thought possibly a ROM issue, but things had been running smooth for awhile, so it seems odd that it would just start happening out of the blue.
I uninstalled apps, and wiped my phone and reinstalled the ROM, and nothing seemed to fix the issue. I finally re-locked my phone yesterday, put stock ROM back on and still had the issues. I took it in to Sprint today and they said it was because the phone had outdated software and they updated it. The only thing I saw updated was the PRL, so I'm thinking they are full of it. I should have checked for updates before bringing it in, because then they wouldn't have been able to bring that up as an issue.
They also tried to blame some apps as potentially the issue, but I'm basically at stock with minimal added apps. The apps I'm using are ones that I've used since I first had the phone. Perhaps an update of one of those apps is causing the issue.
I'm gonna run it on stock for a day or two and see if the issue is resolved by whatever update they did. I will then put HD Revolution back on and see what happens.
If you figure something out, please post again. My issues sounds exactly like yours. Doesn't sound like a ROM issue, since you and I are using different ROMs. Maybe a manufacturer defect, but I wonder if we have a common app causing the issue.
Update: Have tried the HTC Touchscreen Calibrator here:
http://forum.xda-developers.com/showthread.php?t=1378142
No change at first. Then i re-calibrated the screen but this time touched below the designated targets (purposely putting the alignment slightly out). Now im able to pull the notification bar down! Meaning it thinks im touching part of the screen where the notification bar is when in fact im touching just below it. "Touch Test" from the Market is a great app for testing this.
Could this be a fault with certain parts of the digitizer?
I know digitizers can be found easily enough and theres videos on youtube, but has anyone actually replaced one or think it will help???
@gonzodog: How is yours looking? Do you think you can give this a try aswell?
I downloaded the calibration tool and will test over the next few hours. My screen issue doesn't seem quite as bad as yours. Turning on and off the screen usually resolves the issue ans it doesn't happen all the time.
I went back to Sprint to show the update he ran didn't work. He 'thinks' it is an HTC issue. I am am looking for a good AOSP Rom to try to see if it is a sense issue. The Sprint rep said he has the same issues on his phone.
I am new to Android (coming from webOS) so I am not used to having so many options for an OS, so I don't know which ROM I'm going to flash.
I saw another post in this forum by someone with similar sounding issues, starting to think it really may be a software issue and not a defect in the phone.
I'll let you know how it goes after the calibration.
I have this issue lately no matter what rom I run.. been running custom rom's now for Month's and this just started..can't seem to figure it out..it just gets stuck and the notification window will not pull down or it will think I want to copy and paste during a text, do goofy things while dialing etc....then I have to hit the power button to simply turn screen off and on..then all is good again...seems to be getting worse and I have used every wipe, rom etc..not sure what to do.
Someone else suggested it was a multi touch issue. Could an app cause that?
I have very few apps on my phone, since I reset to stock. Maybe I will remove the the ones I have downloaded and see what happens. I want to think the issue is caused by an app, maybe one that was recently updated.
My non stock apps are: tapatalk, barcode scanner, google authenticator, tasker, words free, godville, ringcentral, yahoo fantasy football, SwiftKey x, and Google+. Do you all use any common apps?
Sent from my PG86100 using Tapatalk
I'm having this issue as well. I'm loving the change in sprint policy making me go to a repair center just to get the run around. It's a bit silly that they can't hand me a new one. I'm well within my year manufacturer warranty and have insurance. I'm hoping that this issue can be tracked down. From my perspective as a former cell phone repair tech, I'm banking on defective digitizers that are wearing out or wearing in a strange manner to produce this effect. I've tried multiple roms, sense and aosp and still have the problem.
I have an unlocked evo (no carrier) full stock and it happens to me too.. Specially the "o" and "i" letters on keyboard.. It doesn't always happens but when it does is just a matter of seconds till it's ok again..
Sent from my HTC EVO 3D X515m using XDA App
@gonzodog: I dont actually use any of the apps. Even when i flashed a stock ROM, the fault occurred.
This seems more and more likely that its parts of the digitizer at fault....
This was the reason I went back to stock s on was having loads of problems
Sent from my HTC EVO 3D X515m using XDA Premium App
@ronin201085 If it is the digitizer, then the question is how to get Sprint to replace it. I may try a different Sprint store today and suggest a digitizer issue. I have insurance, so my preference would be fore Sprint to repair it. I did see that replacement digitizers are available via ebay for about $20, but I'd rather not pay to fix something when I have insurance.
honestly if you are covered under insurance then have they repair it for you... its too risky to replace the digitizer yourself, especially seeing as there are no good tear down videos available that show us how to separate the touchscreen and digitizer from the main body... suffering from the same problem
I have the same problem man.. sprints customers service blows, I have taken it down there twice and they still wont do anything because I can't "duplicate" the issue. And also, for me turning the screen off and on fixes the issue.
Sent from my PG86100 using XDA App
Same problem here. Took it to my local sprint store and they replaced the screen no questions asked, although I did have to unroot it before they would touch it. The way I showed them that the defective digitizer was the culprit was downloading the app touch test from the market. That got their attention. A whole section of my screen wasn't registering input.
@3vo kid: I really don't care to replace myself, but I have taken it to Sprint twice, and both times they said it was a software issue. I was able to replicate the issue in the store, still didn't help. I am going to try a different Sprint store, and if still a problem, maybe a call to customer service.
Sent from my PG86100 using Tapatalk
I work for an indirect dealer fixing Sprint phones and I can guarantee you that it is the digitizer. HTC really did disappoint with these crappy digitizers. Whats more sad is that sprint does not rule this as a common problem when it truely is.
Ok for starters im in Australia and this phone was an import, so sending it back under warranty is a loooooong process, so im open to ideas.
I know digitizers are easy to get, especially on ebay, there must be people that have already replaced them. Im engineer by trade so my technical skills arent bad. Im seriously considering just trying to replace it myself.
ronin201085 said:
Ok for starters im in Australia and this phone was an import, so sending it back under warranty is a loooooong process, so im open to ideas.
I know digitizers are easy to get, especially on ebay, there must be people that have already replaced them. Im engineer by trade so my technical skills arent bad. Im seriously considering just trying to replace it myself.
Click to expand...
Click to collapse
there are deff ppl that have replaced them... but no one has posted sufficient information, pics, or videos when replacing the screen. to my understanding the digitizers are attached to the lcds with an adhesive and there are ribbon wires that get in the way of removing them. in all seriousness it might be easier to order a replacement digitizer with an lcd already attached
Ur digitizers are dirty ... put you phones in boiling water .. should fix it
Sent from my PG86300 using XDA App
Hello,
I'm looking to figure out if anybody has found a software fix for the issue of screen backlight flickering on our phones. I've hunted down some threads through Google, but found nothing except 'go replace your phone and hope for the best.'
As a reminder, when grays are displayed onscreen (as in Play store loading screen), it seems as though the screen refresh rate can't 'keep up' with those colors. To me, the problem is even more noticeable when viewing pictures in the Gallery - seriously, I feel like I'm watching one of those 3D movies, and my eyes and head start to hurt! It's just enough that it drives me crazy, but other people do also seem to notice it, so I'm not just ACTUALLY going nuts. This problem showed up on stock before I rooted and went MeanROM, so I know it's not my fault. The problem is worse at higher brightness levels, and persists even with manual brightness settings on.
So yeah, anyone else have this problem? Any stories of successfully resolving it? I'm still within my Sprint 30-day replacement period, but already got 3rd-party insurance on my phone, so it'll be interesting to try to get a replacement phone insured under the same policy...
Yep have had this problem for a while now and actually got tired of it this morning and will take my phone back for a replacement whenever I have time! Gets so annoying especially noticing it in the littlest of places.
Sent from my EVO using xda premium
Hmm.. I never really noticed it until you pointed it out..
Sent from my EVO using xda app-developers app
drmclove69 said:
Yep have had this problem for a while now and actually got tired of it this morning and will take my phone back for a replacement whenever I have time! Gets so annoying especially noticing it in the littlest of places.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Whoa, please let me know if your replacement is any better after a day or two of playing with it. I will probably do the same if there's an improvement.
Was on meanROM 4.2 until today, when I relocked and unrooted in preparation for getting a replacement at Sprint (I'm still within my 30 days). I was going to replace the phone because of this exact problem - a weird, barely-perceptible strobe effect when viewing grays and looking at certain photos in the gallery. And now - after all the hard work of finding an RUU for 2.13, figuring out the android SDK, learning how to use ADB (not to mention the whole initial unlock/twrp bootloader shebang) - I find that the screen flicker has dropped off. OK, sometimes there's an extremely brief (~150ms) hint of it all on a gray screen, but absolutely nothing compared to the headache that it was before. I'd recommend completely unrooting/relocking your phone and pushing the correct RUU. QBking77's the best for it - look up his youtube vids on android sdk intstallation/usage, then relocking your bootloader, then unrooting/installing an RUU. Remember to clear your Google Wallet first, and set your fastboot to off (under power settings). After relocking your bootloader, you might notice that you cannot boot past it. That's fine; just push your RUU with fastboot USB. You'll know what I mean after watching the vids.
After all that, if your results were like mine, you'll know it actually had something to do with your custom ROM. I have no idea how that is possible, as I seem to recall a flickering in my stock ROM, too, but I guess I was wrong. Perhaps it has something to do with my charge status, and I'll see the issue come back... who knows?
For relocking/unrooting
Step 1: Android SDK setup
Step 2: Relock the bootloader
Step 3: Unroot/Push RUU (for some reason, I had to go straight to pushing RUU from step 2 without booting into any ROM).
From all my scouring online, though, I've noticed that the people most consistently hammered with this problem (especially on screens other than photos in the Gallery or gray colors in the battery histogram of power settings) have build issues with their screens. These include light leak seeming to emanate in bands fanning up out of the home 'button' or graphical issues. These people usually report a fix to the problem once they receive a replacement; the ones with my problems typically complained of having received up to 3 (!) phones in a row with the maddening flicker, suggesting a software issue. It seems that the HTC One X itself was plagued with these problems, with graphical glitches also entering the mix, but an OTA fix a month ago or so minimized issues.
Lemme know how things go... I still have 4 days or so to return my phone if the flicker comes back, haha.
I had to get my phone replaced. sadly for me it was a hardware failture. check google maps and see if it the graphics flicker there, of if the background on minecraft main screne flickers in and out
Spyderekz said:
I had to get my phone replaced. sadly for me it was a hardware failture. check google maps and see if it the graphics flicker there, of if the background on minecraft main screne flickers in and out
Click to expand...
Click to collapse
Yeah, woke up this morning and problem was back in full force. I think it might be charge-dependent or temperature dependent (which makes sense if its an analog hardware component like a voltage regulator that's being futzy). I ended up replacing it, too, but Sprint charged me a bull**** $35 because I bought the phone at third-party reseller instead of a corporate store (god... damn... it). Anyway, my new (and refurb, btw) unit has absolutely no problems. Zero. Rooting and reinstalling meanROM now, haha. At least the store people acknowledged that they could also see the problem. Software scans turned up absolutely nothing, although Sprint says HTC does not allow them to open things up because it's a unibody phone, so it's still possible that my regulator was faulty.
Anyway, seems to me that it's a hardware problem having to do with a particular batch of phones. Strange, since my new phone is a 0003 hardware revision, just like my last...
Went today for my 3rd time trying to get a replacement because of this issue and not to mention I got denied a replacement when I was in my 14 grace day period I went in 2 times after that today being the 2nd and I asked for a replacement, I then have to wait for the "tech" to look at it...waited 1 hour to get told it phone has no problems we ran all the tests and passed, me really confused asked her do you even know what the problem is? She replies no....I then am like WTF. I tell her about my issue and try shwowing her and somehow doesn't notice it. Then asks 5 other people and they notice it and then they replace my screen? After I wait another hour (caused me to be late to work) then once done it actually fixed the problem completely, go home to find out she broke my speaker and my sd card won't mount! Drop it off and picked it up and all is fixed. I know want to terminate my contract cuz sprint has been giving me Shi**y customer service since day one! Someone who works at sprint plz help me!
Sent from my EVO using xda premium
Alright, guys; I need some help. I previously had the classic all to well known problem with my digitizer, where I was missing about a half inch of touch input on my screen. I had gotten used to just rotating it to type, cause I was out of warranty, and I'm upgrading soon.However, more recently, I have developed a much bigger problem. My touch screen no longer works, AT ALL.
The issue first started when I attempted to install "Someone's ROM" with "That libs". I got screen fade-out that some other users reported, so I pulled the battery and flashed back to my EPinter's CM10 backup. After it had booted, I went to unlock the screen, and NOTHIN'. Not registering any presses or swipes what so ever. I then went into recovery and cleared everything, still nothing. Hooked it up to my PC, ran a FULL wipe (OS included), and flashed a fuitcake. After booting; still no touch screen. A helpful member of this forum suggested I try the PDS fix, so I did. Still left with the same result.
So, my question is... Is there any way that someone MUCH smarter than I can look at some type of statistic I can pull from my phone to see if there's a software problem causing this issue? And if so, is there any way I can retrieve said info with out being able to use the phone it's self? I really don't want to go the next 2 weeks with a flip phone. heh.
EDIT: If anyone can figure this out and get it fixed, I would be more than happy to donate.
Mast likely your digitizer is just broken!
Happens quite a lot on that phone.
They are not that expensive! (see for example http://www.amazon.com/Motorola-Screen-Digitizer-Replace-broken/dp/B004Z0UO8O)
If you can't change it yourself see if you find someone to do it.
Yup. Sounds more like a hardware issue since you already did all recommended procedures.
Sent from that Atrix.
Yeah, I figured as much. Just hard to accept that it's finally completely gone out on me. Especially since it happened at the exact second I tried flashing experimental, untested firmware. I am aware of how simple a digitizer replacement would be, but I don't want to spend $40 on a new one, when I'm about to dump another $300 into a new phone in two weeks, ya know?
Hi everyone. Thank you for reading.
I am posting for help with a friend's phone. I, personally, have an S3 on Sprint and haven't had much experience with T-Mobile phones. He has rooted his S5 (T-Mobile, obviously) using galaxys5root.com (I'm now not fond of that site due to his bad experiences that consistently happen) and has not put a new ROM on yet. It has been successfully rooted for several weeks, but today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on. He's getting a replacement anyway, but we want to unroot it before sending in the defective device. I'm wondering (and to my knowledge it seems like) if it's a boot loop. Nothing shows up on the screen at all, not even the back light is coming on. I have yet to connect it to Odin to see if anything comes up. I'm just seeing if this has happened to anyone else and if they have figured out a way to resolve it. My suspicion is that there's a problem with either the boot sector or the recovery sector, as it does not go into recovery.
Any insight would be much appreciated. Thanks again!
caderyn19 said:
today he went to text someone a response and the screen went black, and the blue notification light breathes. It also does a light vibrate, like when you are turning it on.
Click to expand...
Click to collapse
It sounds like the LCD display has gone bad if the vibration and blue light function normally but you cannot see anything ever.
When they get the new device you might want to suggest that they follow the rooting instruction in this forum on XDA instead of going to a website to do it. Just my opinion.
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
caderyn19 said:
We are thinking the LCD is bad as well, it just feels like a boot loop because the light vibration keeps happening (I forgot to mention that). Sometimes the blue light will go out and the phone will vibrate lightly and then the blue other starts breathing. It's just repeating that non-stop. I had to pull the battery.
As for him rooting through here, I told him to with his S4 and S5 but he didn't listen. The S4 took a crap, and now the S5 took a crap. I told him I think it's that site. The method is correct but who knows where those flash files come from... I've never had any issues rooting through here, just an occasional reset here and there, nothing as major as this.
Click to expand...
Click to collapse
Normally, even in a boot loop you see the initial Galaxy splash screen when it first starts booting. Then you see it over and over again. If you see nothing, it normally means the LCD is bad and unfortunately it's the most expensive part of the phone.
Good Luck with it.
If I've been helpful, please hit the thanks button.
That's what I figured... Thanks for your help! (I hit the button )
caderyn19 said:
That's what I figured... Thanks for your help! (I hit the button )
Click to expand...
Click to collapse
Wouldn't surprise me if the device is rebooting itself trying to fix a hardware fault. Might be detecting the LCD has stopped forcing itself to reboot.
But yeah, stick to XDA from now on We are good people here Welcome to the family!
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
caderyn19 said:
Lol I've been part of the family for years now... I've always come here first for any android help, and have always found just what I'm looking for!
Click to expand...
Click to collapse
Well get your friend over here too!
Sent from my SM-G900T using Tapatalk
Hello! I just got a new unlocked HAM2 from B&H yesterday. It works really well, but one thing that is kind of weird about it is that when you boot it there is a very, very quick flash of snow (like when an older television has no signal or the HBO logo snow) right before the Huawei logo bootscreen. Otherwise, the device seems to be working normally. It has the latest stock firmware installed from box and I have done no modifications to the phone. I was just curious if anyone has this strange, seemingly harmless glitch on their phone on boot or reboot. Also, is it something to exchange it over? I guess I was just worried it was a hardware problem or something that might get worse in the future. I know I have had Linux machines that do strange things in the past when initializing video on boot, so maybe it's just a software issue with the stock ROM. Thanks so much.
Weird. I've never heard of this before.
If you just got it, maybe you could try doing a reset? Resets have fixed some bugs for me and possibly a few others.
ScoobSTi said:
Weird. I've never heard of this before.
If you just got it, maybe you could try doing a reset? Resets have fixed some bugs for me and possibly a few others.
Click to expand...
Click to collapse
Thanks so much for your response. I just tried a reset but no luck. I used the VOL UP plus POWER method on boot to do it. I just posted a few screenshots of a video I took to give you an idea of what it looks like. On the off state, two during the snow state, and one after the snow state (seemingly normal). Imagine it as a very, very fast flash. If you blink you miss it. Probably happens over the course of just half a second. Maybe it's something to do with the LCD panel initializing or something.
EDIT1: I also wanted to note that the screen does not do this when it goes to sleep or is woken from sleep. Only during the initial powering on of the device.
EDIT2: One more note, the device came with build MT2-L03V100R001C00B148 installed from factory.
deploypenguins said:
Thanks so much for your response. I just tried a reset but no luck. I used the VOL UP plus POWER method on boot to do it. I just posted a few screenshots of a video I took to give you an idea of what it looks like. On the off state, two during the snow state, and one after the snow state (seemingly normal). Imagine it as a very, very fast flash. If you blink you miss it. Probably happens over the course of just half a second. Maybe it's something to do with the LCD panel initializing or something.
EDIT1: I also wanted to note that the screen does not do this when it goes to sleep or is woken from sleep. Only during the initial powering on of the device.
EDIT2: One more note, the device came with build MT2-L03V100R001C00B148 installed from factory.
Click to expand...
Click to collapse
By "snow", do you mean static or noise? The screen looks a bit staticy or noisy in those pictures. The only thing I can think of is maybe some of the animation images are somehow corrupted. The boot animation is just a bunch of .PNG images shown in succession pretty quickly. This might explain why you see that stuff in a split second every time you boot.
Same here, as of today. I've owned mine for about 3 months, and it just did the static-y flash thing you explained. I remembered this thread, actually, so when it happened I decided to come track this thread down.
Mine is rooted and tweaked, however. Stock ROM, unlocked bootloader. Everything has been mostly fine (except my phone learned a new trick it likes: "Flip the video orientation randomly when someone's watching youtube! Yay, upside-down!"
Other than the occasional tempermental quirks, it's been running smooth. So I'm not sure of what could be causing this. But if more people state theyre having this issue, maybe it'll be further looked into!
zombunny said:
Same here, as of today. I've owned mine for about 3 months, and it just did the static-y flash thing you explained. I remembered this thread, actually, so when it happened I decided to come track this thread down.
Mine is rooted and tweaked, however. Stock ROM, unlocked bootloader. Everything has been mostly fine (except my phone learned a new trick it likes: "Flip the video orientation randomly when someone's watching youtube! Yay, upside-down!"
Other than the occasional tempermental quirks, it's been running smooth. So I'm not sure of what could be causing this. But if more people state theyre having this issue, maybe it'll be further looked into!
Click to expand...
Click to collapse
Sounds quite odd, never read about this until this thread.
As for the upside-down video, check your root tweaks or display settings.
ScoobSTi said:
Sounds quite odd, never read about this until this thread.
As for the upside-down video, check your root tweaks or display settings.
Click to expand...
Click to collapse
It is odd, hopefully it's nothing serious to worry about. It'd be a shame if it were to become a problem, as I've really been enjoying this device.
And I've been checking about the video orientation bug, but I can't think of anything I may have changed that would alter it. It's very random, and seems to only occur within MX Player. May be limited to that app only. A reinstallation might fix that, but configuring the orientation to "force auto-rotation" within the App Settings module has ceased the issue.