Maybe it's just bad luck, but I have had issues no matter with ROM I use. The last two times after crashing, my GN could not even restart in Bootloader so I was forced to get a replacement phone. Only got a few months of use on the first one before this problem happened again. I'm always finding some kind of annoying bug and I am getting tired of trying to determine why this keeps happening, so I thought I'd post and share just to see if anyone had advice. I love all the features in AOKP, but the crashes have hurt me the most. I have tried many others but think I'll stick with stock for now. I love the GN because of the beautiful and large screen. Unfortunately, Verizon will not give me another phone of equal or lesser value and I cannot upgrade until 10/13. I'm starting to think the GN is just not very ROOT friendly.
Does this happen to anyone else? I'm not nearly as techie as I'd like to be, but I've learned so much from this forum and loved all the ROMS I used- when they worked that is.
Hobbes650
Hobbes650 said:
I'm starting to think the GN is just not very ROOT friendly.
Does this happen to anyone else? I'm not nearly as techie as I'd like to be, but I've learned so much from this forum and loved all the ROMS I used- when they worked that is.
Hobbes650
Click to expand...
Click to collapse
what? this phone is the easiest phone to root/unlock the bootloader. you cant get more friendly than that.
when you say crash... what do you mean? ive had 0 problems out of aokp.
Hobbes650 said:
I'm starting to think the GN is just not very ROOT friendly.
Click to expand...
Click to collapse
What!?!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
import-ex
Here is what has happened the last two times. I turned the phone on and Ill I got was the "goolgle" screen. Nothing else, kept flashing on and off. Tried to restart directly into bootloader but no success. This has happened multiple times now. Rooting is not difficult for me, until this issue came along. Until I can figure out why that happened I don't want to try again. Haven't heard of this problem yet so please understand my frustration and lack of words to describe what is happening.
Thanks,
Hobbes
Hobbes650 said:
Here is what has happened the last two times. I turned the phone on and Ill I got was the "goolgle" screen. Nothing else, kept flashing on and off. Tried to restart directly into bootloader but no success. This has happened multiple times now. Rooting is not difficult for me, until this issue came along. Until I can figure out why that happened I don't want to try again. Haven't heard of this problem yet so please understand my frustration and lack of words to describe what is happening.
Thanks,
Hobbew
Click to expand...
Click to collapse
Rooting couldn't possibly cause that.
Bad hardware, memory corruption, bad flash of a kernel or rom maybe, but not root.
sounds like a bad kernel flash or rom flash
just adding root, does not do what you just described.
I agree with the rest. Rooting just gives you access to options and settings that you normally can't access. So you either got bum phones or you did something or had bad flash
Sent from rooted Jitterbug running ICS
Hobbes650 said:
Here is what has happened the last two times. I turned the phone on and Ill I got was the "goolgle" screen. Nothing else, kept flashing on and off. Tried to restart directly into bootloader but no success. This has happened multiple times now. Rooting is not difficult for me, until this issue came along. Until I can figure out why that happened I don't want to try again. Haven't heard of this problem yet so please understand my frustration and lack of words to describe what is happening.
Thanks,
Hobbes
Click to expand...
Click to collapse
sound like you were running a kernel with default fsync off and risky mount options. when it crashed, it lost everything.
Appreciate the help, and glad to hear. I did change kernels and that sounds like where the problem lies. I'm not too sure I really care much about kernels, so I will try again and keep whatever kernel the ROM comes with.
Thanks,
Hobbes
Hobbes650 said:
Appreciate the help, and glad to hear. I did change kernels and that sounds like where the problem lies. I'm not too sure I really care much about kernels, so I will try again and keep whatever kernel the ROM comes with.
Thanks,
Hobbes
Click to expand...
Click to collapse
really, i would find one you like and just use that one.
Hobbes650 said:
Maybe it's just bad luck, but I have had issues no matter with ROM I use. The last two times after crashing, my GN could not even restart in Bootloader so I was forced to get a replacement phone. Only got a few months of use on the first one before this problem happened again. I'm always finding some kind of annoying bug and I am getting tired of trying to determine why this keeps happening, so I thought I'd post and share just to see if anyone had advice. I love all the features in AOKP, but the crashes have hurt me the most. I have tried many others but think I'll stick with stock for now. I love the GN because of the beautiful and large screen. Unfortunately, Verizon will not give me another phone of equal or lesser value and I cannot upgrade until 10/13. I'm starting to think the GN is just not very ROOT friendly.
Does this happen to anyone else? I'm not nearly as techie as I'd like to be, but I've learned so much from this forum and loved all the ROMS I used- when they worked that is.
Hobbes650
Click to expand...
Click to collapse
Well, before mucking around, search some of the forums, because this problem is not caused by the ROM, or the phone. OSs only crash, wehn you're asking to much of them, eg.: Windows, open too many processes, it shuts itself down, so it doesn't burn out the RAM, it's just protecting itself.
Imagine you would have to work in an office, type three essays and phone with a multi-millionar client, all at the same time, then you know how an OS feels, when you ask too much of it. Just do one thing at a time, let it finish one job, before starting another, and don't overclock the CPU too much, 1.4 GHz, on both cores is enough to run Windows Vista, 7 and 8 64x, let alone the Android OS, which managed to run fine an a hTC nexus one...
If you really want some advice, from someone who has gone through 20 computer OSs and 6 smartphones in one year, then read on;
Take your phone and root it, to get the most out of it. Enjoy the phone whilst you have it and NEVER, EVER say an Android is not "root-friendly". Follow that piece of advice, with the tips I mentioned above, and you'll NEVER have a crash again (BTW, here's a quick one: take stock AOSP, flash the imgs and then put one feature on the, at a time... )
Related
Hello,
The purpose of this thread is to seek assistance with what has become a major issue.I have a rooted EVO 4g device(for several months) and I am not sure as to how it exactly happened but my phone now complete commands by itself.For example when in typing screen,it automatically starts writing letters,when I try to erase them they repeatedly come back.It will not let me complete many commands before taking over and clicking random selections.
**Things I have tried to remedy the problem include clear cache,data several times,install other roms(same problems with Cynagogen 7, syngergy and MIUI).
Powering off and powering back on.
Nothing seems to work and I would greatly appreciate it, as i am extremely close to unrooting and going back to the old fashion way.
What should I do?
Please help
Albert
Are you using the stock keyboard? or is this on a 3rd party keyboard?
Sounds like the touch screen is going bad to me. Does it also randomly open aps? Or is it just when you are typing?
wow! Incredible response time. I have tried several keyboards as well, stock, swift keyboard and the one that comes preloaded with cynagogen 7.
Are you having issues with response times any other times you touch the screen? Could be your digitizer going bad?
soloque1999 said:
wow! Incredible response time. I have tried several keyboards as well, stock, swift keyboard and the one that comes preloaded with cynagogen 7.
Click to expand...
Click to collapse
It's been a slow day at work.
Sounds like you've covered your bases pretty well. I'm still thinking it's a HW problem. There are intructions out there on how to replace the screens. You can buy replacements on eBay.
bizdady said:
Are you having issues with response times any other times you touch the screen? Could be your digitizer going bad?
Click to expand...
Click to collapse
issues with response time, such as not responding, clicking above and below the area I touch and not responding to the area I touched.
majorkillin said:
It's been a slow day at work.
Sounds like you've covered your bases pretty well. I'm still thinking it's a HW problem. There are intructions out there on how to replace the screens. You can buy replacements on eBay.
Click to expand...
Click to collapse
Curious, do you know how much a screen cost? Nothing else that can be done prior to this? excuse my ignorance.
I've seen anywhere between $11 and $28.
Call a priest, rabbi monk or other clergyman because your phone is possessed by a demon!
Actually, it sounds like a hardware problem. My wife's touchscreen android phone had a similar problem..it was hardware related
soloque1999 said:
Curious, do you know how much a screen cost? Nothing else that can be done prior to this? excuse my ignorance.
Click to expand...
Click to collapse
Its a a touch screen lcd Digitizer, pretty much the cover. Some ppl have replaced em when their screen cracks or scratches. You might want to unroot and take into store and see if they will replace.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Theyre about 20 bucks on ebay.
SantinoInc said:
Call a priest, rabbi monk or other clergyman because your phone is possessed by a demon!
Actually, it sounds like a hardware problem. My wife's touchscreen android phone had a similar problem..it was hardware related
Click to expand...
Click to collapse
quite commical, thanks for the humor during such turbulant times. How did you resolve the issue with your wife device?
bizdady said:
Its a a touch screen lcd Digitizer, pretty much the cover. Some ppl have replaced em when their screen cracks or scratches. You might want to unroot and take into store and see if they will replace.
Theyre about 20 bucks on ebay.
Click to expand...
Click to collapse
Thanks, a milliion times for your feedback. I actually looked it up after asking impulsively. I was thinking about taking it to sprint, but because I had such a difficult time getting my evo rooted in the first place. wanted to rule out all other options before going that route.
Does anyone have an updated version of the unroot process?
Sent from my PC36100 using XDA App
soloque1999 said:
Does anyone have an updated version of the unroot process?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Go to unrevoked's site and download the s-on tool, then flash that in recovery. Then download the newest RUU available. You can download it in .exe form to run from your computer or as a zip to flash through the bootloader. If you decide to go the zip route, rename it to PC36IMG.zip (don't add a zip, it's already there) and put it on the root of your SD card. Boot into the bootloader (vol down + power) and when it asks you to update select yes with the volume up button.
I wouldn't flash the s-on tool though, and would just run an RUU. If you used unrevoked or unrevoked forever during your root process then you'll keep s-off. They should still fix it as long as you're back to stock otherwise. That way if the tech gets the crazy idea to update your phone you can still get root back. If they replace it then maybe someone will get your s-off device
I had this issue, gave the bare screen a nice cleaning with an glass cleaning wipe and changed screen protectors and the issue never came back.
If you have a screen protector on, check this route first. If not, then digitizer it is.
I wouldn't unroot, just flash a stock, rooted ROM. I doubt they're going to look at your Hboot or anything. This way, if they get jumpy and update for you, you'll still be S-Off.
For some reason, no matter what I do, after I flash miui 1.9.9 on my EVO 4g, it gets stuck on the HTC EVO 4G screen, how do I get this to work?
What recovery are you using? Are you wiping completely? Cache, dalvik, data, system, boot, sd-ext, .android_secure?
Have you tried redownloading the rom or checking that the md5 matches?
If you answered yes to everything, you can always try a different version, like 1.9.2. If you are coming from 1.9.2 and don't normally wipe between builds of MIUI (assuming you only run MIUI like I do), it may be time to do a full wipe. I try to do one at least every 3-4 flashes. By that point I have so many apps I don't use that it does a lot of good to start fresh so I can weed out the useless apps. Plus MIUI can be picky. I've never personally had issues with it, but others have.
Sent from my PC36100 using Tapatalk
plainjane said:
What recovery are you using? Are you wiping completely? Cache, dalvik, data, system, boot, sd-ext, .android_secure?
Have you tried redownloading the rom or checking that the md5 matches?
If you answered yes to everything, you can always try a different version, like 1.9.2. If you are coming from 1.9.2 and don't normally wipe between builds of MIUI (assuming you only run MIUI like I do), it may be time to do a full wipe. I try to do one at least every 3-4 flashes. By that point I have so many apps I don't use that it does a lot of good to start fresh so I can weed out the useless apps. Plus MIUI can be picky. I've never personally had issues with it, but others have.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
I'm coming from End of Days rom, but I flashed 1.9.2 they took 1.9.9 off the site I guess a bunch of people are having problems with it. But thank you
I have the same issue. I am using CWM 5.0.2.2 (I think) and I do a fresh wipe of everything before hand. Should I try Amon RA?
If it's with MIUI 1.9.9, then OP just said that they took it off of the site. Try a different version, like 1.9.2.
Sent from my PC36100 using Tapatalk
prezmater said:
I have the same issue. I am using CWM 5.0.2.2 (I think) and I do a fresh wipe of everything before hand. Should I try Amon RA?
Click to expand...
Click to collapse
Yeah, actually bro, they took 1.9.9 off the site last night, and I flashed MIUI 1.9.2 and it works great, so I would try that if I were you.
I was having the same problem and what I did was just download 1.9.9 from the site, place it on SD, then just flash manually through recovery. Works now. Seems a little laggy though.
THe original release of 9.9 wouldn't flash on anyone's phone. It pretty much took up a few pages at the end of the thread, so good job not reading.
Anyhow, there's a new version on the miui.us site that's been fixed
I literally just made my account on this site yesterday, and it was just to message MagnusRagnarok about Destroyer v2.
That being said, I have never before run MIUI, and when I finally did decide to try MIUI out, it had nothing to do with a thread on this website, so I have no idea what thread you're talking about. So you can take your attitude somewhere else, and we can all be mature and helpful on my thread. Thanks.
Well, it would be thew tread about MIUI, which is a good place to start when you're gonna flash the MIUI ROM you never used before.
Of course, the 3 pages about that problem on MIUI.us site would have been another good place to look. You know, the one titled Hanging On Booth Thread? Or the Impressions thread.
Don't give me attitude because you were too lazy to actually do a little (needed) research before you blindly (and stupidly) flashed a new ROM.
Look, I'm sorry if I'm short with you, but look to the left and you can see I've been here awhile, I'm very active in these forums and I try to help out as much as I can, but I've seen far too many uneducated questions that could have been avoided by doing a little research before doing something like a completely new ROM that you have never tried before, and I don't feel the need to pull any punched with people like that.
HipKat said:
Well, it would be thew tread about MIUI, which is a good place to start when you're gonna flash the MIUI ROM you never used before.
Of course, the 3 pages about that problem on MIUI.us site would have been another good place to look. You know, the one titled Hanging On Booth Thread? Or the Impressions thread.
Don't give me attitude because you were too lazy to actually do a little (needed) research before you blindly (and stupidly) flashed a new ROM.
Click to expand...
Click to collapse
You're hilariously ignorant if you think I "Blindly (stupidly)" flashed a rom without knowing anything about it. Just because I read a site that has NOTHING TO DO with the rom, but rather a community of developers, that really just PORTED the rom some other people made, sooo.. Just because I researched it on the official MIUI site, instead of this one, you're going to falsley accuse me of some crazy ****. You think you're smart because you've been on the site for longer than me, but really you seem to have an inability to read my ****ing thread. I bid you good day sir.
Typical troll, get's called out for doing something wrong and lashes back instead of accepts the fact that he screwed up...
I'm afraid you are ignorant to what a troll is. You see, I was looking on a help forum, for help. If anyone here could be classified as a troll it would be you.
Sent from my PC36100 using XDA App
You are so right, with your 10 whole posts....
Yeah, so I'm new to a phone forum. The 15 years I've been browsing the rest of the internet and making 90$ an hour programming doesn't show anything. You know, you would do well to watch how you treat others because you know nothing about them. Just because you may know more about a specific problem than me doesn't make me any less of something than you, it just makes me less qualified to answer that specific question. If you asked me for help.regarding something you couldn't do... I would help you without question, especially considering I had the problem solved before you even posted on the thread.
Sent from my PC36100 using XDA App
Posting how much you make is pretty troll-like, for one. I'd think someone that has been on the net almost as long as I have would have a clue as to internet decorum.
Keeping this going, also very troll-like.
Welcome to teh internets
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You realize the thread was done before you hopped on it right? "Keeping this going is very troll-like" hahahaha yeah ok nice try. It wouldn't have even started if it wasn't for you.
Sent from my PC36100 using XDA App
Might want to check those dates, sonny.
My last post was Sept 7th, you came back Oct 27th and started it up again....
I saw earlier that people were saying that rooting the epic touch 4g may NOT be the cause of LoS. But I'm here to tell you that I only got the LoS after I rooted. All I did was root and install honeycomb battery + crt animation. The LoS was getting ridiculous, so I went back to the stock kernel and I'm LoS free. Just letting you guys know, this IS a root issue and it should be stated clearly for those who are considering rooting. I think it will just cuase a lot of grief for users if they are not properly warned, so please do so guys.
its not confirmed unless you have thousands of independent tests
Just a warning, you're about to get flamed for posting this in the development section. With that said, I too never received an LoS until the day after rooting the phone (had it for two weeks with no issues). Installing the LoS kernel has helped a ton, though.
i can also confirm that rooting caused my phone to experience an endless onslaught of LoS occurances. I had the phone for a month without any LoS issues, only ****ty battery life (losing 6-8%/hr idling over night). The day I rooted the phone, i experienced LoS three times. Installing the lostkernel helped and I only got one in three days, but I ended up switching to the EVO 3D since I coudl not stand the battery life.
I have never once had LoS, on either stock put root. I am one of the lucky ones. However in have read there are people out there that have LoS without routing, so I am not sure your confirmation is 100%.
Sent from the EPIC Touch
y0sup said:
I saw earlier that people were saying that rooting the epic touch 4g may NOT be the cause of LoS. But I'm here to tell you that I only got the LoS after I rooted. All I did was root and install honeycomb battery + crt animation. The LoS was getting ridiculous, so I went back to the stock kernel and I'm LoS free. Just letting you guys know, this IS a root issue and it should be stated clearly for those who are considering rooting. I think it will just cuase a lot of grief for users if they are not properly warned, so please do so guys.
Click to expand...
Click to collapse
Unless you can explain why my COMPLETELY STOCK phone got struck with the LOS bug, then no, rooting is not the cause. It may TRIGGER the LOS bug, but it is NOT THE CAUSE.
Please try to do a data profile clear/update, that's what fixed my phone.
sorry before hand but whats los? loss of service??????
I experienced LoS before and after root. Now I know what it means when I read "your milage may vary ".
Now to another issue, just because your phone is showing reception or 1 bar doesn't mean you haven't LoS... lol, only way to find out is by placing a call...
Samsung is very good with destroying its reputation... Before it was their lazy late updates, now defective devices... I was 100% set to get Galaxy Nexus, then I heard Samsung... Hmmm makes me think three times and looking to alternatives, definitely will wait atleast few weeks before getting Nexus.
I would compare samsung to a sexy sl*t lol
Wrong section
wrong info
Horrible logic
Just total overall fail
One case does not mean confirmation, plenty of people on stock are getting this problem.
Sent from my Galaxy S2
[CONFIRMED] You're an Idiot....
Root and go back to stock kernel... or use the repack, bet yu have the same rate of LoS...its not rooting, kernels built from source have been shown to increase it. Even unrooted kernels... please do som research and get the facts straight before posting incorrect info.. especially in the wrong section...
Sent from my SPH-D700 using XDA App
stangdriverdoug said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Galaxy S II
Click to expand...
Click to collapse
lol. Now comon our little section of the forum needs entertainment time to time.
In case everyone was with dwring if y0sup is a one-off offender, you need not search anymore http://forum.xda-developers.com/showpost.php?p=6532397&postcount=32
My phone musta been dipped in unicorn piss! I've never had LOS stock or rooted. Running LoStkernel exp.
Sent from my SPH-D710 using xda premium
y0sup, please post your full analysis, your abstract seems to be based on simple test/retest validity of one instance. I would like to see your lit review, research design, sample size, data analysis, findings, and any appendices you may have to support your hypothesis.
in my experience.. after I rooted.. I got one LoS and my Battery drained faster..
{CONFIRMED} Beans give me gas.
I know some folks out there eat beans and don't get gas, but let me tell you, beans cause gas. I never got gas until eating beans. Boy that was some nasty stuff. Because of this I'm returning the beans and demanding my money back.
majorkillin said:
I know some folks out there eat beans and don't get gas, but let me tell you, beans cause gas. I never got gas until eating beans. Boy that was some nasty stuff. Because of this I'm returning the beans and demanding my money back.
Click to expand...
Click to collapse
Lol
Sent from my mothapluckin' phone!
Wives phone+no root=los
My phone+ lostkernel= no los
I think from my findings that stock causes los
Sent from my SPH-D710 using XDA App
Also confirmed. Galaxy s 3 will by delivered be Santa claus.
Sent from my SPH-D710 using XDA App
Oh my goodness - closing this thread - it's already out of hand.
OP - follow the rules. Post in the right spot.
Hello
I have tested different roms with Sense 4. One V porting Rom.
Since I have flashed the first one my screen miss 1 mm border right and left.
I am not alone, and if you have falshed Sense 4, can you confirm it!?
Here are pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Original Size - Click here
Original Size - Click here
Original Size - Click here
Original Size - Click here
The size screen stay the same when I flash back a Sense 3 Rom as Revo HD & others.
Have you any idea?
Thanks
Flow & Co
Edit:
Something strange, when I take a screenshot the size is 480*800... :/
That's perfectly normal it's supposed to look like that.
Are you sure!?
I haven't already noticed that during 15-16 months :/
Hey,
i have the same issue since i flashed LeeDroid v5.1 and 5.1.1 (i still have the Rom and the issue). I remember that some time ago Lee had some wrong drivers for the touchscreen in his rom that had the same effect. It was in his v.3.. i think. But after an update it dissapeared. I never read of others users mentioned this for LeeDroid v.5.
As Lee's Rom is not an ICS Version, i think that it doesn't have something to do with ICS. I hope somebody knows how to help us
EDIT: While thinking about Lee's Touchscreen drivers i am not sure if it the problem was that 1mm of the screen was missing at the edge or that the screen didn't react on touchinputs at the edge of the screen. But its a fact that my screen looks like yours! And it didn't look like that all the time and with all the other roms i had.
Flow-Wolf said:
Are you sure!?
I haven't already noticed that during 15-16 months :/
Click to expand...
Click to collapse
it's obviously a driver issue in terms of resolution, I'll check it cause I solved this problem in my full sense4
Same problem.
memnoc said:
it's obviously a driver issue in terms of resolution, I'll check it cause I solved this problem in my full sense4
Click to expand...
Click to collapse
I have the same problem. Hopefully you will find a solution.
Here you go i'm using miui v4 btw but i just checked and it was the same on gingerbread. The reason they did this was because of when you tilt the device slightly you still see the full screen as the screen is slightly below the glass your pressing on.
PS: not the best picture quality but wth (^_^)
Sent from my Desire HD using XDA
Driver issue
xinos said:
Here you go i'm using miui v4 btw but i just checked and it was the same on gingerbread. The reason they did this was because of when you tilt the device slightly you still see the full screen as the screen is slightly below the glass your pressing on.
PS: not the best picture quality but wth (^_^)
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
The 1mm gap is 100% not normal. After flashing a sense4 rom i could see how it hapens. After the reboot the screen just got small. There is now a 1mm free black space at the right side off the desvice and an 0.3mm space on the top of the device. The "black spaces" are touch responsive. Thats a driver issue.
http://forum.xda-developers.com/showthread.php?t=1263594
Here you go.
PS: I dislike you XD, na just joking tho i didn't notice before and now i do......
It's not a resolution issue but aspect ratio issue...i don't think it's that big of a deal but do you get same results with GB roms?
Turn DHD over
Heya, just noticed that on the back of the phone says HTC.
J/K
1mm
So there is an fix for that? Because i think thats not an hardware issue. It happened when flashing primoS v3.3 Sense rom.
@Xinos, thanks I have't seen this thread yet
@shad0wboss, Yes I have same issue with GB. But I don't think I had it with official or before use Sense 4! here is the point
Flow-Wolf said:
@Xinos, thanks I have't seen this thread yet
@shad0wboss, Yes I have same issue with GB. But I don't think I had it with official or before use Sense 4! here is the point
Click to expand...
Click to collapse
Don't take this the wrong way but it's all in your head you noticed this when you flashed sense 4 and you were expecting bugs. So you notice smaller things including screen miss-alignment.
Trust me if everyone had this problem you would see alot more questions in this subject. Be my guest tho and do a factory reset, but i'm pretty sure it's a hardware fault that has always been there you just never noticed before like i did damn you (T_T) .
xinos said:
Don't take this the wrong way but it's all in your head you noticed this when you flashed sense 4 and you were expecting bugs. So you notice smaller things including screen miss-alignment.
Trust me if everyone had this problem you would see alot more questions in this subject. Be my guest tho and do a factory reset, but i'm pretty sure it's a hardware fault that has always been there you just never noticed before like i did damn you (T_T) .
Click to expand...
Click to collapse
No i have the same problem since flashing and it wasnt ther at 100% i played temple run before and there were no edges.
rafassoft said:
No i have the same problem since flashing and it wasnt ther at 100% i played temple run before and there were no edges.
Click to expand...
Click to collapse
Then what's stopping you from fully resetting your device that should fix it shouldn't it?
I really don't care what you do i'm just giving my piece of advice, one thing you could try is going into boot loader mode (power down device and then press on button+volume down) if it still has it that means youre device has a miss-aligned screen.
^^
Stay calm men
I have to try to flash a Ruu on my device and see if the "problem" change. Maybe this is not a problem
We have to see. But if we found a man which hasn't it can we call that a problem?
rafassoft said:
So there is an fix for that? Because i think thats not an hardware issue. It happened when flashing primoS v3.3 Sense rom.
Click to expand...
Click to collapse
It's not only the primos rom. I've realized this since this thread is started and I'm on IceColdSandwich.
How ever, you have to send it to HTC cause of the issue and use your warranty. There is nothing you can do with flashing a new ruu oder rom.
Regards.
Curiouse
DonPanda said:
It's not only the primos rom. I've realized this since this thread is started and I'm on IceColdSandwich.
How ever, you have to send it to HTC cause of the issue and use your warranty. There is nothing you can do with flashing a new ruu oder rom.
Regards.
Click to expand...
Click to collapse
But how this can be? Some magic troll got under the screencover and made the screen smaller? Because the screen is not moved in the device or anything. I know that there is an hardware issue on some phones that the screen is wrong aligned but thats not our case, because the screen got 1mm smaller on each side of the phone. its most likley an software issue.
Has any of you tried boot loader mode? If the issue still persist over there it's a hardware fault as you can't change the boot loader.
So tomorrow I have a HTC One X being delivered
Super-excited, but I have one question - should I update it when I get it or leave 'as is'. Reason being as I don't want to prevent any possibility of being able to put CFW on the device. Give or take a few weeks I'll probably jump off Sense and go for Cyanogen or something.
I know this a very noob question - it's just I'm not familiar with this particular device - rather the Xperia Play and Wildfire
Also, any things I should know?
Thanks!
droident said:
So tomorrow I have a HTC One X being delivered
Super-excited, but I have one question - should I update it when I get it or leave 'as is'. Reason being as I don't want to prevent any possibility of being able to put CFW on the device. Give or take a few weeks I'll probably jump off Sense and go for Cyanogen or something.
I know this a very noob question - it's just I'm not familiar with this particular device - rather the Xperia Play and Wildfire
Also, any things I should know?
Thanks!
Click to expand...
Click to collapse
You can update it, it should'nt do any difference. But remember you can be charged for repairs from htc if you do. I did, they changed the motherboard but I still got it for free.
You could wait for s-off. _If_ they manage to crack the damn thing, you won't loose the warrany because the bootloader is still locked.
Must still must say that sense is really good, and the 2.05 coming soon is superb, and so far I havent rooted again yet.
Hope it helps you decide.
Don’t unlock it right away, because like Sckank said you’ll loose warranty. There are some common hardware issues with the phone (i.e WiFi antenna problems), look in the general section to find out more, so wait a while and test everything out before you attempt it, or better yet wait for S-OFF (which is what I’m doing).
Sckank said:
You can update it, it should'nt do any difference. But remember you can be charged for repairs from htc if you do. I did, they changed the motherboard but I still got it for free.
You could wait for s-off. _If_ they manage to crack the damn thing, you won't loose the warrany because the bootloader is still locked.
Must still must say that sense is really good, and the 2.05 coming soon is superb, and so far I havent rooted again yet.
Hope it helps you decide.
Click to expand...
Click to collapse
hi,
became confused... :S
if was possible to make s-off you don't lose the warranty?
i know that you can reverted to s-on again ...but they will notice or not?
the bootloader can be relocked or isn't the same thing?
Nope if they can s-off then s-on is no problem and you're completely back to stock. And you don't have to agree to that you loose your warrany. And they can't see that.
Nope not the same thing, they will see that. It will say "relocked", not locked.
when you unlock without s-off, you need to pass through htc-dev, which will make it record your unlock status. and also, when you relock your bootloader, it will display "Re-Locked Bootloader" instead of :Locked Bootloader". With s-off, none of them will change.
EDIT : beaten. haha.
Still, a more complete answer about htc dev
thanks to both
Thanks guys!
I'll go ahead and update for now then.
I got my new phone this morning, unfortunately it has some nasty 'backlight leak' along the bottom of the screen so O2 are getting a replacement out to me tomorrow. It's a gorgeous phone, just hoping the replacement doesn't suffer the same problem...
It's pretty minor and I'm perhaps a little OCD but I showed someone else and they were like "it's all wavy "
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
droident said:
Thanks guys!
I'll go ahead and update for now then.
I got my new phone this morning, unfortunately it has some nasty 'backlight leak' along the bottom of the screen so O2 are getting a replacement out to me tomorrow. It's a gorgeous phone, just hoping the replacement doesn't suffer the same problem...
It's pretty minor and I'm perhaps a little OCD but I showed someone else and they were like "it's all wavy "
Click to expand...
Click to collapse
that's normal isn't it? ive had 6 and its been on every one of them, don't keep your hopes up for getting one that doesn't have it.
edit: saying that, im looking now and i can't see it.. weird.
lawrence750 said:
that's normal isn't it? ive had 6 and its been on every one of them, don't keep your hopes up for getting one that doesn't have it.
edit: saying that, im looking now and i can't see it.. weird.
Click to expand...
Click to collapse
I think it generally affects white and brighter backgrounds. I thought it might be 'normal' when I found various threads about 'stagelight' backlight leak, though this was after I'd given O2 a quick ring. Can't cancel the replacement now, just hope it's not a refurb replacement.
Not *too* bothered about it... it seems to have lessened since I first booted it up oddly.
All being said, I would consider this to be a defect really - the only time I've seen 'stagelight' bleed like this was after I had a smartphone go through the wash. HTC need to improve the manufacturing process considering the cost of these handsets near half a grand.