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.
Related
I would have posted this in the developments forums, but since im a new member, it wouldnt allow me. Heres the issue:
Running FRX04 android on my Sprint TP CDMA works great, except at random times the screen will become off center and shift to the left. At one point it became so garbled with lines it was unreadable, but came back to normal as I kept tapping the screen. Its almost as if the refresh rate is incorrect. Anyone ever had this issue?
Also, screens touch calibration seems to be off, any way to re-calibrate like in WM?
Thanks in advance!
Have you updated any of the files like the rootfs or the kernel package? Also, you will need to read the first post in THIS thread and replace the file either in the root of your microSD or if you are using the andboot option, in that folder.
R^7Z said:
Have you updated any of the files like the rootfs or the kernel package? Also, you will need to read the first post in THIS thread and replace the file either in the root of your microSD or if you are using the andboot option, in that folder.
Click to expand...
Click to collapse
Fixed the problem a while back, was related to the kernel, had to switch to a different one. Now everything works great, almost.
Although it is very usable, my problem has been that when when the phone goes to sleep, it will keep the backlight on for a period of time with the screen black. Then at some point the backlight will turn off, i assume a deep sleep. When this happens the phone is completely unresponsive, however the leds around the center button fades as if its charging. Only a soft reset will work.
Thanks again.
I usually don't enable auto back light because that is still being worked on if I'm not mistaken. Instead, I turn off the screen manually. Usually helps to enable pattern lock, for me anyway. Make sure you are updating as there has been some recent updates as of late: FRX05.
n-Joie (Enjoy)
ill give that a shot
I disabled all backlight features in WinMo and Android and everything works perfect. Thanks. However my GPS has never worked, just says aquiring until it times out saying that it couldn't find any satellites.
I believe GPS is disabled by default. This may or may not be listed as such but I think I recall reading this somewhere (maybe IRC logs?). Unfortunately, this is something the devs are still working on and hoping someone "fixes" it eventually...
Im not worried about gps at all, if i need it I can use WinMo. Been using android exclusively on my TP for 2 days now and it works great. Battery life is great too.
Have you tried out the camera yet? I tried it out the first time yesterday and I was stunned! Don't think I ever saw the camera work in Android before so to say the least I smiled when I tapped the camera icon and saw what the camera was pointing at... Even though it seemed like it hung after it took the picture, I may have been a tad impatient with it at the time as I was slightly excited!
Very nice!
I have not tried the camera yet unfortunately. I will right now and post back. Ive had pretty low expectations so im not like others and complaining by any means.
Additionally, it helps to have that sort of mentality. Not required but by all means it does help to be helpful!
R^7Z said:
Additionally, it helps to have that sort of mentality. Not required but by all means it does help to be helpful!
Click to expand...
Click to collapse
You cant expect too much when your running a non-native os on an unsupported device. I used to be a big member of the xbox dev forums back in the day. So i can understand the users that complain when things are in alpha stage. I guess I can start posting in the development forums now that im over 10 posts.
My camera didnt work when I tried it by the way. black screen area then showed a crash message. Like I said no big deal, usability I would say is still excellent. If i need to use gps or camera ill just use winmo till then, no biggie!
jasew503 said:
Fixed the problem a while back, was related to the kernel, had to switch to a different one. Now everything works great, almost.
Although it is very usable, my problem has been that when when the phone goes to sleep, it will keep the backlight on for a period of time with the screen black. Then at some point the backlight will turn off, i assume a deep sleep. When this happens the phone is completely unresponsive, however the leds around the center button fades as if its charging. Only a soft reset will work.
Thanks again.
Click to expand...
Click to collapse
Could you explain how you fixed your screen issue going off center and shifting to the left...I am having same problem
I downgraded my kernel. Can't remember which one I used in frx04 as I lost my SD card with 04 on it and have since been using FRX05 which worked as downloaded with no changes to the kernel needed. If you look at the FRX04 thread in the beginning, there is a reference to Touch Pro users having to use a different kernel (1225 I think), and I just down,loaded it and extracted it overwriting the kernel that came with FRX04. I haven't tried FRX06, but tried the GBXOA gingerbread bundle today on another SD card and it seemed too buggy for my liking, crashed in the XDA Dev app while trying to reply to your post. Sure loos and flows nie tho. Try using FRX05 or 06, rather than 04..
Sent from my MSM using XDA App
The kernel I replaced it with was 1242 btw
Sent from my MSM using XDA App
For about 4 days now my screen has been acting up and giving me quite the annoyance. It initially started while i was on Deck's "gbsense-e3d-deck [1.0]" ROM. I wiped cache and dalvik then re flashed the ROM twice but the screen kept malfunctioning. I was forced to perform a factory reset and re flash a new downloaded file of the same ROM which fixed nothing. I wanted to see if it was a ROM specific issue so i flashed CyanogenMod 7 VALPHA3 and the issue was still present but to a much less annoying degree. Now it seems as if my device doesnt register touch around the midsection. That makes me unable to select anything that may be in that area. I have tried multiple multitouch apps and testers to "diagnose" what is going on with my touch screen, but all i can gather is that my screen might be ****ed. The phone works flawlessly excluding the touch screen's unresponsive zone, so i don't know whether it's a hardware or software issue. Any insight concerning this matter is welcomed, Thanks.
I have attached a video demonstrating my screen while using the app "multitouch paint"
Anybody? 140 views 0 Responses
Could it be a ground issue? Try holding the phone in your hand and see if it still does it. I remember my OG Evo having a similar problem when I laid it on something non conductive.
husker91 said:
Could it be a ground issue? Try holding the phone in your hand and see if it still does it. I remember my OG Evo having a similar problem when I laid it on something non conductive.
Click to expand...
Click to collapse
It occurs both while in hand or on a surface. An example is if i pull down the notification bar, depending what hits the affected zone, i'm unable to select it. I used SBM quite often and now when drawing for example a straight line up it would look like this _____________ __________ (vertically of course) the gap being my speculated affected area but much wider.
MindSplit said:
It occurs both while in hand or on a surface. An example is if i pull down the notification bar, depending what hits the affected zone, i'm unable to select it. I used SBM quite often and now when drawing for example a straight line up it would look like this _____________ __________ (vertically of course) the gap being my speculated affected area but much wider.
Click to expand...
Click to collapse
Is it possible that both of the roms you tested are using the same kernel? I would swap out the kernel with the stock one just in case. At least it'll rule it out lol.
husker91 said:
Is it possible that both of the roms you tested are using the same kernel? I would swap out the kernel with the stock one just in case. At least it'll rule it out lol.
Click to expand...
Click to collapse
I'd take it one step further and return completely to stock, if it STILL does it, then I would guess it's a problem with the digitizer and you would either have to buy a replacement one, or take it to Sprint. If you don't have TEP then HTC's warranty should suffice.
Possibly related?
http://forum.xda-developers.com/showthread.php?t=1267124
It looks similar to this issue, but you are getting it with a single touch instead of with a multitouch. I get EXACTLY the same thing if I use a second tap while drawing a line. Try "multitouch visualizer 2" from the market and see if it registers one tap that is on all the time or if you can actually get the full 4 touches at once. I doubt it will be insighful, but it can't hurt--and if you have an "always on" (perhaps in the button area below the screen) then you know the digitizer is bad.
If it is the same issue, try restarting and give it time. Mine has gone from happening often to happening about 1% of the time. It is software and can be "corrected" by either time or a restart. It is WORST on the first boot after flashing something (even JUST a stock kernel). I have absolutely no idea why.
Good luck. I hate this junk. My Evo 4G never had this sort of glitchy garbage, but, whatever it is, it is likely due to HTC's glitchy kernel!
MindSplit said:
For about 4 days now my screen has been acting up and giving me quite the annoyance. It initially started while i was on Deck's "gbsense-e3d-deck [1.0]" ROM. I wiped cache and dalvik then re flashed the ROM twice but the screen kept malfunctioning. I was forced to perform a factory reset and re flash a new downloaded file of the same ROM which fixed nothing. I wanted to see if it was a ROM specific issue so i flashed CyanogenMod 7 VALPHA3 and the issue was still present but to a much less annoying degree. Now it seems as if my device doesnt register touch around the midsection. That makes me unable to select anything that may be in that area. I have tried multiple multitouch apps and testers to "diagnose" what is going on with my touch screen, but all i can gather is that my screen might be ****ed. The phone works flawlessly excluding the touch screen's unresponsive zone, so i don't know whether it's a hardware or software issue. Any insight concerning this matter is welcomed, Thanks.
I have attached a video demonstrating my screen while using the app "multitouch paint"
Click to expand...
Click to collapse
My friend us having the exact same issue. If you figure anything out, please let us/me know.
Sent by my Supercharged dual core from the 3rd Dimension
I would also like to know whats going on.. I have two evo's 3d and my friend was telling me that he is having issue with the touchscreen he is still on stock... and my was rooted the same day I got it and has no issues.. He mentioned that the same area mentioned in this thread is the are affected in his phone... could this be cause by the screen digitizer??
Ignore this... Thought I found what my issue was... But wasn't the case
I had the same problem but it only seemed to be in one horizontal strip of my screen. Im not sure what caused it maybe its from me dropping it or what. I also did try to flash other roms and kernals but still no fix so i said to myself im going to put it back to stock and take it to sprint. There they looked it for about 2 minutes and deemed it was a hardware issue. The guy asked if i had a warranty. Two days later i received a refurbished phone.
So in all revert it back to stock... search on htcevohacks . com
Take it back to sprint and show them your problem. They should also deem it as a hardware issue and send you a replacement
MindSplit said:
For about 4 days now my screen has been acting up and giving me quite the annoyance. It initially started while i was on Deck's "gbsense-e3d-deck [1.0]" ROM. I wiped cache and dalvik then re flashed the ROM twice but the screen kept malfunctioning. I was forced to perform a factory reset and re flash a new downloaded file of the same ROM which fixed nothing. I wanted to see if it was a ROM specific issue so i flashed CyanogenMod 7 VALPHA3 and the issue was still present but to a much less annoying degree. Now it seems as if my device doesnt register touch around the midsection. That makes me unable to select anything that may be in that area. I have tried multiple multitouch apps and testers to "diagnose" what is going on with my touch screen, but all i can gather is that my screen might be ****ed. The phone works flawlessly excluding the touch screen's unresponsive zone, so i don't know whether it's a hardware or software issue. Any insight concerning this matter is welcomed, Thanks.
I have attached a video demonstrating my screen while using the app "multitouch paint"
Click to expand...
Click to collapse
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
So I recently got my old bricked evolte replaced by Sprint. The one I was given worked fine the entire time the device was powered on. However, once turned off and back on, its screen would not work. It stayed like this for hours, until I finally started playing with it and realized it would come back on after playing with it for a little bit. I also found out that with this error the home screen pops up for a second when powering on your device, and that's exactly what I had. I read up on the error and found out it was a software error, and to reset to factory settings. So, this fixed it, I thought.
So now, after it is apparently fixed, it still does this to some extent. It will do this if the phone has been powered on for a while, and the screen won't stay off for more than like 2 or 3 minutes. Also the home screen doesn't pop up any more like it used to with the other error.
So what should I do? I was thinking of going to Sprint, but my problem is hardly reproducible. It only happens when it's been powered on for a long time, and won't do it twice in a quick succession. I feel that even if I could show them the problem, they might think they've fixed it when they haven't because it won't do it twice. I would like to root my device, but I'm afraid they're going to say that I'm the cause of the problem if I do that. If it's just a software problem though, maybe flashing a custom rom would fix the problem.
What do you guys think? What do you think is the best course of action? Any advice would be greatly appreciated. Thank you.
Never mind, I didn't know Sprint would order you a new phone if it was a minor problem like that. I thought they would only repair yours. So feel free to close this thread.
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