Related
So I just put Clockwork Recovery on an new SLCD Droid Incredible. I was about to flash the IncDoes new Sense Rom which I'm also running on an Amoled Incredible (and enjoying on that device) and decided to pause for a second before doing it wondering if anyone had done it already. Are the roms compatible between the SLCD and Amoled Incredibles? Any one know? Or am I treading in uncharted waters?
codyt01 said:
So I just put Clockwork Recovery on an new SLCD Droid Incredible. I was about to flash the IncDoes new Sense Rom which I'm also running on an Amoled Incredible (and enjoying on that device) and decided to pause for a second before doing it wondering if anyone had done it already. Are the roms compatible between the SLCD and Amoled Incredibles? Any one know? Or am I treading in uncharted waters?
Click to expand...
Click to collapse
I have a SLCD Incredible and all roms run just fine. I don't notice anything different beside missing my vibrant AMOLED colors
You want to sell me your AMOLED Droid Incredible? I'm desperately looking for another INC to dev on...
ID
Well my company owns both of these, so I can't sell the other one.
So my SLCD DINC will not show Clockworks screens. I just get a black screen with two white lines down either side. phone boots fine and i can get to the bootloader screen but when i try to go into clockwork I only get the black screen with the white outside lines.
Are you using Clockwork? Did you use UnRevolked to load it or Fastboot?
How are you using fastboot, I take it you flashed the mfg hboot?
codyt01 said:
Well my company owns both of these, so I can't sell the other one.
So my SLCD DINC will not show Clockworks screens. I just get a black screen with two white lines down either side. phone boots fine and i can get to the bootloader screen but when i try to go into clockwork I only get the black screen with the white outside lines.
Are you using Clockwork? Did you use UnRevolked to load it or Fastboot?
Click to expand...
Click to collapse
Actually I'm not, I used Unrevolked3 to install Clockworkrecovery and supposedly root. But when I run ADB with the SDK it finds the device but it doesn't seem that I really have root.
I had remembered Fastboot-Windows from my previous work with the Nexus and original Droid. I cheated with Unrevolked3 this time, and it worked flawlessly on the Amoled Dinc, but not this SLCD Dinc
the real issue is that I can't see Clockwork's screens at all. Just a black screen with white lines down the side. I can clearly get to the phone through ADB cause it's listed and I can run commands like SU, although it tells me permission denied when I run SU. So it sounds like something didn't quite go right?
I'm not a developer, I'm just a guy that plays with ROMs on a lot of different phones.
Yeah I ran unrevoked on mine as well (just got an SLCD version today). I can backup ROMs and everything with full root access, but when booting into clockwork all it shows is black screen with white on the sides, so I can't actually tell what it's doing until it reboots.
bloodiedwraith said:
Yeah I ran unrevoked on mine as well (just got an SLCD version today). I can backup ROMs and everything with full root access, but when booting into clockwork all it shows is black screen with white on the sides, so I can't actually tell what it's doing until it reboots.
Click to expand...
Click to collapse
how can you tell you can back up roms with it? Do you know that the controls work? + - for up and down and the power for select? and are you just memorizing the locations?
I just opened up Rom Manager on my phone and when I choose make backup it goes to that black screen and when it finishes it reboots. When I go into ROM Manager it shows that there was a backup made.
I would definitely like a version that could be useable when going through manually into recovery though.
bloodiedwraith said:
I just opened up Rom Manager on my phone and when I choose make backup it goes to that black screen and when it finishes it reboots. When I go into ROM Manager it shows that there was a backup made.
I would definitely like a version that could be useable when going through manually into recovery though.
Click to expand...
Click to collapse
Wow, I've gotta get with the program. I haven't browsed this forum enough. I had no idea a tool like ROM manager was out there. found it downloaded it loading .7 now on the SLCD Dinc. Black screen with white now as it's loading the rom, no messages on whether it's working or not. Kind of scary, but I'll let it run.
Looks like a very cool tool.
side question, but any one know how much better the slcd version does with battery? and if they fixed the charging issue (bump charge)?
gummehbear said:
side question, but any one know how much better the slcd version does with battery? and if they fixed the charging issue (bump charge)?
Click to expand...
Click to collapse
i would also like to know this well atleast the bump charge part
the battery is Dependant literally on what colors u have displaying the most
for a
AMOLED screens if you display dark/black more you waste less battery
SLCD screens if you display white/bright colors more you waste less battery
great thing i have a amoled and i love dark colored themes
superchilpil said:
i would also like to know this well atleast the bump charge part
the battery is Dependant literally on what colors u have displaying the most
for a
AMOLED screens if you display dark/black more you waste less battery
SLCD screens if you display white/bright colors more you waste less battery
great thing i have a amoled and i love dark colored themes
Click to expand...
Click to collapse
interesting. how can one tell which screen their Dinc has?
mcgoo99 said:
interesting. how can one tell which screen their Dinc has?
Click to expand...
Click to collapse
Up to recently, they've had AMOLED. They are being made with SLCD now though.
Sent from my Droid Incredible
Div033 said:
Up to recently, they've had AMOLED. They are being made with SLCD now though.
Sent from my Droid Incredible
Click to expand...
Click to collapse
i know; i got my Dinc roughly two months ago, but don't know if it was before or after the switchover
mcgoo99 said:
interesting. how can one tell which screen their Dinc
has?
Click to expand...
Click to collapse
I found the answer here yesterday:
http://forum.xda-developers.com/showthread.php?t=799499
look on your box at the model number or on your phone
if it ends with w2 then it's amoled
if it ends with w3 is slcd
I checked my box last night but I sent the UPC back for a rebate so ???
julesism said:
I checked my box last night but I sent the UPC back for a rebate so ???
Click to expand...
Click to collapse
The rebate form stated to make and save a copy of everything If you have a receipt with the UPC google it. You could try calling big red, that might work
ToyTank said:
The rebate form stated to make and save a copy of everything If you have a receipt with the UPC google it. You could try calling big red, that might work
Click to expand...
Click to collapse
I have receipt copies somewhere. Hopefully the model number is on it. I do not have a copy of the box.
I had this same issue a few nights ago... you have to upgrade your bootloader to. 92
Sent from my Incredible using XDA App
Jaxon2319 said:
I had this same issue a few nights ago... you have to upgrade your bootloader to. 92
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
They should already have the .92 bootloader if brand new and stock 2.2.
codyt01 said:
Well my company owns both of these, so I can't sell the other one.
So my SLCD DINC will not show Clockworks screens. I just get a black screen with two white lines down either side. phone boots fine and i can get to the bootloader screen but when i try to go into clockwork I only get the black screen with the white outside lines.
Click to expand...
Click to collapse
Hopefully this helps you...
I do believe that IncredibleDoes uses Amon_Ra recovery, so if he is using a slcd like he says with no problem, then I would try that instead of clockworkmod.
Sent from my ADR6300 using XDA App
Have a major problem with my screen when turning phone on or rebooting the screen looks fine. But when I get to the actual home screen it's looks crazy with vertical lines on it like a white noise effect but when I shut the screen off and then turn it back on it's gone. It's freaking me the hell out what could be causing it? Is there something wrong with my phone? Is there a setting somewhere that's out of whack? Any advice would be greatly appreciated.
TheUnquietMind said:
Have a major problem with my screen when turning phone on or rebooting the screen looks fine. But when I get to the actual home screen it's looks crazy with vertical lines on it like a white noise effect but when I shut the screen off and then turn it back on it's gone. It's freaking me the hell out what could be causing it? Is there something wrong with my phone? Is there a setting somewhere that's out of whack? Any advice would be greatly appreciated.
Click to expand...
Click to collapse
sounds like a hardware issue, which ROM are you using?
Try reflashing.
Sent from my cm6evo using XDA App
I had this problem right after I flashed a kernel. Try wiping your dalvik and cache and rebooting, thats what fixxed it for me.
I have this same problem, and it only happens with certain kernels. I think it's an Epson thing. My last phone was a Novatech and had no issues and my current one is an Epson. Sometimes it's that crazy vertical line garbage, others times it's horrible tearing. It only happens after a reboot and ALWAYS goes away after turning the screen off and on. I stopped caring about it a while ago because it always goes away.
Thanks guys I rest easy now I was worried I was going to have to deal with sprint.
_MetalHead_ You the man.
TheUnquietMind said:
Thanks guys I rest easy now I was worried I was going to have to deal with sprint.
_MetalHead_ You the man.
Click to expand...
Click to collapse
No prob man. With my last phone I was very limited with which ROMs and kernels I could run. It wouldnt run any AOSP ROM and most if not all HAVS kernels were a no-go. My current one will run anything I want it to run, and runs MUCH smoother and snappier than my last phone. So, I deal with the weird screen thing and I get a phone that blows the socks off my last one. It's a fair trade off IMHO.
Ya I got worried as I'm still at noob status with this whole rooting thing and thought I fried my phone. I tried searching the forums but couldn't find the issue anywhere I had talked to sprint and they told me that it was a hardware issue. Glad that its nothing to worry about. I'm loving the boosted speed that I get from my phone.
Sent from my PC36100 using Tapatalk
Are you running a custom ROM/kernel or are you still stock?
Running cm6.1
Sent from my PC36100 using Tapatalk
Yeah, definitely don't worry about it then. If that's the only issue you're having then let it go, it's not a big issue at all
Have you tried MIUI yet?
No not yet.
Sent from my PC36100 using Tapatalk
Well if you are a fan of AOSP then I recommend at least trying it. I thought I was going to hate it but tried it on a whim and have never looked back.
This is a fairly common issue with cm6.1 rc1.
There's a thread in the cm forums where multiple people are getting the same thing. I would post the link, but apparently I'm too new here.
A friend has recently updated her Galaxy Nexus phone to 4.1.2 According to her, the screen is now much smaller with big thick black lines at the top and bottom of the home screen. Ideas on what the problem is, how to fix it?
Karzdan said:
A friend has recently updated her Galaxy Nexus phone to 4.1.2 According to her, the screen is now much smaller with big thick black lines at the top and bottom of the home screen. Ideas on what the problem is, how to fix it?
Click to expand...
Click to collapse
Hmm thats strange. Is it a ROM? If it is, wipe completely and choose a different one. If its OTA, then I have no idea. That's very strange.
Sent from my Galaxy Nexus using xda premium
Like what happens when iPhone app isn't optimized for 4 inch screen? That's weird. Never heard anything like that. I personally don't have it, but my friend has 4'1'2 and no problems there
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
that's not right at all... is it stock and updated to 4.1.2 via an OTA? Never heard of that problem.
Problem is taken care of. Until I was able to look at the phone for myself I wasn't able to 'verify' the problem. From what she was saying and what I saw, was two different things. In essence, it looks like the dock bar get's a little larger in 4.1.2 (Yes this is stock, unrooted. Mine is anything but, so I can't compare with hers.) and the shifting of the other icons threw her for a loop. So I installed Nova Launcher and now it looks more like it used to. Plus she loves the idea of having those extra grids and more.
Thanks for everyone's help, but it seems as if it was a false alarm. Gotta love non tech friendly friends.
So heading says it all, did you have the issue before you installed it and did the ROM fix the issue? I've done the low ISO, I missed around with the settings and it does not fix or make it at all better. I will not settle for a replacement device that is not brand new so I am looking for a software fix. I figure a ROM made from a developer phone would fix it since their software is not affected by this issue. So let me know if you have an answer for this. The key has to be that you had the issue before you installed the ROM. Don't trash the tread with junk or speculations of what might fix it I am only interested in facts at this point I've done all the Google might fix and none did....reply away!
Sent from my HTC6500LVW using xda app-developers app
So I read an article on engadget that said the 4.3 update made improvements to the camera in low light settings. I was previously avoiding 4.3/5.5 ROMs because you can't change the lock screen image independently of the home screen. Anyhow, I flashed it last night and have been snapping away with the camera. The pictures seem better.
It's a shame, other than the camera this phone is nearly perfect.
Sent from my HTC6500LVW using Tapatalk
The gsm ones that got the 4.3 update already owners has said it did not fix the low light issue. I doubt HTC has redid the update for tbd Verizon version
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
The gsm ones that got the 4.3 update already owners has said it did not fix the low light issue. I doubt HTC has redid the update for tbd Verizon version
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I don't know, it seems better but I don't have an objective way to measure it. I know that previously my newborn son's face always looked purple in low light pictures and now his skin looks more true to his natural color.
Also, over exposure doesn't seem as bad.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I don't know, it seems better but I don't have an objective way to measure it. I know that previously my newborn son's face always looked purple in low light pictures and now his skin looks more true to his natural color.
Also, over exposure doesn't seem as bad.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Place your hand over your lens and see if the purple comes back
Sent from my HTC6500LVW using Tapatalk
Dark Jedi said:
Place your hand over your lens and see if the purple comes back
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Sounds about exactly right for what can be done. The low-light picture taking is really a hard thing to accomplish, me thinks. I have a Canon DSLR, and fast lenses are expensive (apart from prime lenses), so I'm not surprised that this overprmised technology is not meeting expectation. That said, do people really use their camera phones that heavily? I don't. And it certainly wasn't a feature I considered when buying this phone. Not to knock any enthusiasts, but this defect has made me realize how many folks are satisfied with phone camera fidelity.
For any of you interested in photography. $50 spent on a 50mm prime will blow your brains out, expectation-wise.
Zynesterysdan said:
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Click to expand...
Click to collapse
Zynesterysdan said:
So when you use a 4.3 sense rom found in the forums, like the one I'm running which is the NuSense 4.3 RC5, it seems like its "fixed" but what actually happens when you put your hand over the lens is that the blue hue or red will show up, but as soon as the phone detects the hue it goes away. It seems to keep doing it in a repetitive pattern.Hue shows up, then goes away, then shows up again, then away, unlike before on 4.2 where if it shows up, it'll stay there.
My guess is that on 4.2.2 like others have said, when the ISO is raised too far, the hue showed up. So really, it seems like HTC just gave the a camera a limit to not raise the ISO too far.
It's "sorta" (not really) fixed. It's a hardware issue that's been somewhat softened by software implementations.
Click to expand...
Click to collapse
I use my camera as a camera not as some sort of blue noise detection meter. If the hue is gone from my pics and the ISO isn't so high that there is a bunch of color noise then I'm happy and for all practical uses I'd say it's pretty well fixed.
I tried putting my hand over the lens, after about 90s it started turning kinda blue around the edges then would fade to black. Better than before.
Sent from my HTC6500LVW using Tapatalk
mlin said:
I use my camera as a camera not as some sort of blue noise detection meter. If the hue is gone from my pics and the ISO isn't so high that there is a bunch of color noise then I'm happy and for all practical uses I'd say it's pretty well fixed.
I tried putting my hand over the lens, after about 90s it started turning kinda blue around the edges then would fade to black. Better than before.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
The problem with it still is that because it fades in and out, if you take the picture at the wrong time, the hue will be in the picture. That means you have to time when to take the picture, which I'm sure to many is absolutely not fixed. It's still got much room to improve.
Sent from my HTC6500LVW using Tapatalk
Over in the regular HTC one forum someone posted a video of a HTC one running kit Kat and the person had the phone laying down on a table. When he got to the camera the screen stayed black and their was no purple haze going in and out. So I hope it does fix it and look forward to a kit Kat Rom for our phones.
Sent from my HTC6500LVW using Tapatalk
Zynesterysdan said:
The problem with it still is that because it fades in and out, if you take the picture at the wrong time, the hue will be in the picture. That means you have to time when to take the picture, which I'm sure to many is absolutely not fixed. It's still got much room to improve.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Good point. I've been playing with it more today. I have been able to capture most pictures without the hue, but like you said, it kind of fades in and out.
Sent from my HTC6500LVW using Tapatalk
I can tell you this with certainty.. if you tell HTC you need a repair to take care of a camera issue, they will accept it as a legit reason for service. I told them my camera was showing the red/blue and having trouble changing a focal point once it caught one. They tried talking me into waiting for 4.3. I refused. They opened a service order, I sent it out, about a week later I had my same phone back with none of the original problems. I don't know if they swapped out the hardware or what the deal is but when I cover the lens it stays pitch black.
Yes, it hurts being without a phone for a week but it's better than living with a phone that disappoints you for some reason. And especially when that reason can be remedied.
one4thewings said:
I can tell you this with certainty.. if you tell HTC you need a repair to take care of a camera issue, they will accept it as a legit reason for service. I told them my camera was showing the red/blue and having trouble changing a focal point once it caught one. They tried talking me into waiting for 4.3. I refused. They opened a service order, I sent it out, about a week later I had my same phone back with none of the original problems. I don't know if they swapped out the hardware or what the deal is but when I cover the lens it stays pitch black.
Yes, it hurts being without a phone for a week but it's better than living with a phone that disappoints you for some reason. And especially when that reason can be remedied.
Click to expand...
Click to collapse
Did you return it to stock before sending it? I could stand being without it for a week to have it fixed
jessbowring said:
Did you return it to stock before sending it? I could stand being without it for a week to have it fixed
Click to expand...
Click to collapse
Yes, I did return it to stock before sending it in. I don't know that I needed to, but I wasn't going to take a chance on them refusing to do the work because they didn't like my icons or zooper widgets. =)
I used this thread here: http://forum.xda-developers.com/showthread.php?t=2475216
Just to update this thread I did end up sending my phone to HTC to get repaired it was a one week turn around and came back same phone and fixed. Getting my phone repaired was a big deal since I don't want a CLN or Refrib device. So phone is fixed!
Sent from my HTC6500LVW using xda app-developers app
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
I'm a crack flasher so I flash just about every ROM released just to give it a go and I have to have a ROM (4.2.2, 4.3 or 4.4) that has remedied the issue. HTC swears up and down that there is a camera update coming with 4.3 but seeing as how AT&T and Sprint folks said it helped nothing at all in their forums I'm leaning towards a hardware issue. Sucks but we might be stuck with it.
Zynesterysdan said:
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Not stuck with it mine was fixed under warranty repair didn't cost me anything and it's totally gone. 1 week turn around.
Sent from my HTC6500LVW using xda app-developers app
Before and after. No modifications just point and click didn't change anything on camera since I got it back.
Sent from my HTC6500LVW using xda app-developers app
Grnlantern79 said:
Not stuck with it mine was fixed under warranty repair didn't cost me anything and it's totally gone. 1 week turn around.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Well unfortunately I can't be without my phone for more than a couple of days. I use it for work and personal. Too bad HTC doesn't have designated repair centers we can take our phones to for repairs of manufacturer defects. HTC should have acknowledged the issue and authorized cell provider stores where the device was purchased to do exchanges after the traditional 30 day exchange was up. I tried to exchange mine at the Verizon store I bought mine at and they wouldn't do it. Said I still had to go through warranty repair. It's understandable on VZW's end bc it isn't their fault HTC shipped jank phones but on the customer service side it makes both companies look bad. Glad yours got fixed though.
---------- Post added at 12:17 PM ---------- Previous post was at 12:16 PM ----------
Zynesterysdan said:
Just to give an update, the new stock 4.4 gpe rom does a better job of preventing the blue/red noise from appearing. When I cover my hand it appears for half a second then is completely black for the rest of the time
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
It must be subjective bc my hue is still bad but my girlfriend's is semi-okay.
Has anyone noticed that, for all its pixel density, there is some really poor-looking emphasis on edges? Lots of places throughout the stock UI, fonts, icons, etc, will have their edges brighter than the rest of the object. What's more is this is not uniformly applied, so you wind up with some words or icons having this edge detection going on, and in other places, things look properly "flat".
Frankly it makes this "beautiful" screen look really ugly, since the UI it displays looks really ugly.
You may be talking about the over sharpening issue that's been discussed to death on these forums. Hopefully LG fixes it with an OTA update, or we get it fixed with ROMS.
Slash8915 said:
You may be talking about the over sharpening issue that's been discussed to death on these forums. Hopefully LG fixes it with an OTA update, or we get it fixed with ROMS.
Click to expand...
Click to collapse
Hoping for an OTA fix is a pipe dream. LG will not fix this since they will consider that they put a lot of hard work in to over sharpen their UI. Not your UI, their UI, for their phone. Not your phone. So that will never get fixed.
That, combined with the hilarious decision to put the buttons on the back, which no software can address, just kind of leaves some glaring issues. Issues? No, too soft a word. Let's just call them what they are. Errors. Errors in judgment, errors in design, whatever. They got it wrong.
courtlandj said:
Hoping for an OTA fix is a pipe dream. LG will not fix this since they will consider that they put a lot of hard work in to over sharpen their UI. Not your UI, their UI, for their phone. Not your phone. So that will never get fixed.
That, combined with the hilarious decision to put the buttons on the back, which no software can address, just kind of leaves some glaring issues. Issues? No, too soft a word. Let's just call them what they are. Errors. Errors in judgment, errors in design, whatever. They got it wrong.
Click to expand...
Click to collapse
Glad you like it.
americasteam said:
Glad you like it.
Click to expand...
Click to collapse
courtlandj said:
Hoping for an OTA fix is a pipe dream. LG will not fix this since they will consider that they put a lot of hard work in to over sharpen their UI. Not your UI, their UI, for their phone. Not your phone. So that will never get fixed.
That, combined with the hilarious decision to put the buttons on the back, which no software can address, just kind of leaves some glaring issues. Issues? No, too soft a word. Let's just call them what they are. Errors. Errors in judgment, errors in design, whatever. They got it wrong.
Click to expand...
Click to collapse
You knew the buttons were on the back before you bought it so the error is yours if you find there placement an issue.
I think the screen is fantastic and don't have the problem you speak of.
Sent from my LG-D855 using Tapatalk
Lol, buying a device with buttons on the back...just to come on xda and complain about buttons on the back? Okie
As far as the screen sharpness, they do need to address it somehow because black text are indeed awful (not to the point i will complain about them awful though)
Should have done your homework before buying a device that OBVIOUSLY came with buttons on the back though...considering it was flashed all over the internet so you cannot say "oh i bought it and realized buttons were on the back" lol
MaximoMark said:
You knew the buttons were on the back before you bought it so the error is yours if you find there placement an issue.
I think the screen is fantastic and don't have the problem you speak of.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
You have it, it just doesn't bother you. Good for you, my eyes are pretty sharp though and don't need LG's help in that regard. Button placement? Sure. Sure I knew that beforehand. That does not mean it's my error. It's still LG's error. See, I can't really use this thing before I purchase it. They have display models in stores, but the backs (and often the sides) are covered in whatever anti-theft anchoring the store uses. It's not until I get the device home, have it in my pocket, that these usability errors can really make themselves felt. It didn't bother me while the device was in my hand, I thought, well, maybe I will just learn, in time, where my fingers should go. Fine.
But then, and imagine this scenario as being one I cannot replicate in a store with a demo model, the phone was laying face side up on my desk, and I wanted to turn the volume down. Or I wanted to turn the screen off. I can do that without picking the phone up with just about all other phones in the world. Inconvenient. This is a small issue! This is not a big deal. But. But I paid $600 for this, I am not supposed to have to put up with some minor inconvenience, is how I see it. For their flagship phone, the top of LG's current heap, they shouldn't have got any "small issues" wrong. But they did. They got this wrong. And while people replying to this thread seem to want to forgive LG, and that is your prerogative, I refuse to do so.
Doesn't your phone have knock code to switch the screen off? Or have volume controls in the notification area?
Sent from my LG-D855 using Tapatalk
Anyway, the screen looks terrible and the big beautiful screen is the biggest selling point (or am I wrong on this? some argue camera...).
I wouldn't return the phone because the buttons were on the back and yes, "lol", I knew they were there before, during, and after purchasing it.
The big beautiful screen turning out to be not very beautiful, now that, that I could return a phone over. There's not even an option to disable the over-sharpening. Tell me that is not a design failure.
Why is this thread even in existence? This topic been covered elsewhere and not to mention the rest of the post are off topic.
Sent from my LG-D851 using Tapatalk
shook187 said:
Why is this thread even in existence? This topic been covered elsewhere and not to mention the rest of the post are off topic.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Not in terms of the screen looking not very great.
courtlandj said:
Not in terms of the screen looking not very great.
Click to expand...
Click to collapse
You mean the sharpening?
Sent from my LG-D851 using Tapatalk
shook187 said:
You mean the sharpening?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
I have found that the stock theme/wallpapers/icons etc don't do the device any favors. Tweaking these things made the phone much more tolerable for me.
shook187 said:
You mean the sharpening?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Including but not limited to. Sharpening is an issue, but since you cannot disable it, and since it is not by default enabled across all text rendering, not in all apps, etc, it's not uniform. The UI winds up non uniform. The entire graphical feel of it seems mixed and weird. So it made me feel like the display itself was not that great. I actually wondered if there was something physically wrong with my screen. Or, since it was not a uniform problem, was it only one part of the screen that was perhaps damaged or something.
courtlandj said:
You have it, it just doesn't bother you. Good for you, my eyes are pretty sharp though and don't need LG's help in that regard. Button placement? Sure. Sure I knew that beforehand. That does not mean it's my error. It's still LG's error. See, I can't really use this thing before I purchase it. They have display models in stores, but the backs (and often the sides) are covered in whatever anti-theft anchoring the store uses. It's not until I get the device home, have it in my pocket, that these usability errors can really make themselves felt. It didn't bother me while the device was in my hand, I thought, well, maybe I will just learn, in time, where my fingers should go. Fine.
But then, and imagine this scenario as being one I cannot replicate in a store with a demo model, the phone was laying face side up on my desk, and I wanted to turn the volume down. Or I wanted to turn the screen off. I can do that without picking the phone up with just about all other phones in the world. Inconvenient. This is a small issue! This is not a big deal. But. But I paid $600 for this, I am not supposed to have to put up with some minor inconvenience, is how I see it. For their flagship phone, the top of LG's current heap, they shouldn't have got any "small issues" wrong. But they did. They got this wrong. And while people replying to this thread seem to want to forgive LG, and that is your prerogative, I refuse to do so.
Click to expand...
Click to collapse
First, to your last post, the hardware buttons no software can address?
Tweaksbox can, they are hardware buttons like all others, it doesn't matter where they are on the device.
Turning the device off while flat on the table? Double tab the statusbar (yes, works with every launcher and in any app).
Sound: volume slider within notifications?!
If it's that much of an issue for you, swap it, simple as that, i do like having the buttons on the back, why? I can't press them by accident while gaming and i love the feel of having just the edges while in hand.
Last but not least, the oversharpening is your point, i don't really notice it and really like the screen, but that doesn't matter, that's just me, but anyways I'm pretty sure there will come an update for it, if not, that's xda, the bootloader unlock is almost released, there will be a fix for that, because, you know what, it's our device and we can mod the hell out of it if we like to. Every flagship has it's flaws, there isn't any perfect device on the market, if those of this device bug you too much, swap it for another, maybe those flaws you can stand.
Gesendet von meinem LG-D855
Buttons on the back is not an ERROR its lg DESIGN go to the lg 2 you will see, it wasn't thought over night...do not place your dislike on lg "error"
over sharpness been talked to death as it is. I never understand why people complain, don't like something return it. Its that much of an issue? return it. since I have gotten the phone I have only touched the volume keys for one, and only one thing....to take screen shot. Knock on puts the phone on for me, a simple double tap. If I want to be fancy, I can use the knock code or w.e the hell they call it. I only need my volume on two things, silent, vibration and sound...if its too loud notification is there to reduce it or voila...the buttons on the back a simple press will fix it.I do not need to move my hand in any weird kind of a way to do anything, I do not accidently have to press on the volume keys like i have done so many times.
The screen is beautiful without auto brightness. The oversharpness is batter of taste...you will either like it or you will hate it. You obviously hate it so very simple, return the phone instead of beating on the same dead horse. The screen is awful? we knoooooooooooooooooow from xda and all over the net and all over google + and every social media....the text are sharp? we knoooooooooooooooooooow...go return the phone.
mgbotoe said:
Buttons on the back is not an ERROR its lg DESIGN go to the lg 2 you will see, it wasn't thought over night...do not place your dislike on lg "error"
Click to expand...
Click to collapse
I feel that it is an error.
mgbotoe said:
over sharpness been talked to death as it is. I never understand why people complain, don't like something return it. Its that much of an issue? return it.
Click to expand...
Click to collapse
You are complaining about my complaints. I never understand why people complain about other people complaining. Don't like my complaint, ignore it. It's that much of an issue? Close your browser. :silly:
And with that, reported. We don't need another repetitive, argumentative thread that goes nowhere.
Than get rid of the error and return the phone like you said, no custom rom will fix that itch for you. Stop being a statistic of the list of people beating on the same dead horse.
Good luck on your future ventures I HOPE you do far more research on your next phone hunt huh? You rarely post in this forum as it is according to your junior status, member of 2011. Let hope the next post you choose to do about that phone wont result in something like this
Tootles
---------- Post added at 10:50 AM ---------- Previous post was at 10:48 AM ----------
meatlocker said:
And with that, reported. We don't need another repetitive, argumentative post that goes nowhere.
Click to expand...
Click to collapse
Thanks, i got lost in this lil banter. Lol see ya