I am wondering if anybody else notices this, but it appears there are different screen dithering algorithms between the .901 and .902 versions. I just got my bionic, it came with .893. I didnt pay much attention to the screen at the time, and updated with the full "VRZ_XT875_5.9.902.XT875.Verizon.en.US_CFC_01.xml" package with RSD. After using the bionic a bit, I noticed that the screen had certain patterns that would cover certain colors, and they would move, sort of a buzzing fashion. Like a bunch of diagonal lines, especially when grey colors are displayed. I thought maybe it was a hardware thing and was stuck with it. Then later, I wanted to test the speed and how well .901 performed, so I reflashed to .893 with the full "VRZ_XT875_5.5.893.XT875.Verizon.en.US_CFC_01.xml" package in RSD, and then the .901 patch/update. The screen is now looking so much better, like there is less "noise" to it. I wanted to bring this up cause it may be helpful to others who are disappointed with the screen quality and are on the stock .902 rom.
Is anyone else able to verify this?
I believe there is still dithering on the .901 stock, but it's seems different. It doesn't buzz or move so much, it's more tolerable IMO.
Related
Hi I am new to android and am considering switching from my iphone 3gs to a nexus one (or possible samsung captivate) It would be great if yall could answer these questions and any other helpful information you have on the phone!
1. How are the touch sensitive buttons on the bottom of the phone? Do yall ever have any trouble activating them or anything?
2. How is the battery life on this phone? I use my phone for texting ALOT, probably 5000 messages a month. Will i still be able to get a good days use out of the phone? That's all i really need because i charge it at night anyway. Also does rooting the phone and installing different ROMs or kernels improve battery life, or any other improvements over stock android? If so, which ones would you recommend for this.
3. I've read about screen burn in and some touch screen issues, have yall experienced any of these first hand?
I would be very appreciative if you could answer these questions for me
1. How are the touch sensitive buttons on the bottom of the phone? Do yall ever have any trouble activating them or anything?
I don't but my wife does. However, she tends to mash the screen with the side of her thumb because she is a blackberry user and has long nails. As an iphone user I'd think you'd be fine. You'll LOVE Swype.
2. How is the battery life on this phone? I use my phone for texting ALOT, probably 5000 messages a month. Will i still be able to get a good days use out of the phone? That's all i really need because i charge it at night anyway. Also does rooting the phone and installing different ROMs or kernels improve battery life, or any other improvements over stock android? If so, which ones would you recommend for this.
My N1 lasts all day easily, unless I'm doing something crazy like wireless tethering without a charger. That said I have a 2nd battery on a home charger because I hate (or badly forget about) leaving my phone plugged in EVER. Mostly I swap the battery in the morning on my way out. Froyo boots up fast!
3. I've read about screen burn in and some touch screen issues, have yall experienced any of these first hand?
I would be very appreciative if you could answer these questions for me.
Have not noticed any burn in issues yet. The contrast on the N1 AMOLED is a gorgeous thing to behold. It has a nicer image than my LED backlit Samsung TV, which is no chump.
However, the phone's screen struggles terribly in direct sunlight.
1. Touch buttons have been improved and are more responsive after the Froyo update.
2. Can be be good, can be bad. Should last you the day, but with heavy texting i wouldn't know. If you unlock and root it you can experiment with different roms and kernels to improve it. When i got my phone with stock 2.1 -update1 the battery was average. But then i unlocked it and flashe Cyanogen ROM and the battery got way better. So it is up to you. Unlocking and rooting voids warranty, but HTC have been kind to fix/replace phone as long as you re-flash stock to it.
3. Has happened to some. Mostly i think is due to the white status-bar that with long use on highest brightness. It can happen because it is fixed on one place allowing the white and bright burn gradually into the screen. Like the old Tv's (pre-plasma) you know. Leave it on overnight with a still image actually burns the image on the screen when turning it off. Old news really . Again, rooting it will allow you to install a black status bar thus eliminate the threat of a screen burn.
Most phones like these struggles in sunlight. But when beefing brightness to MAX it actually is "OK" to use it in the sun.
i have the slight burn in. its very faint and you would not even notice it AT ALL its that minor. but the problem is google made the status bar all white, and it never moves from that position of the screen no matter what you are doing with the phone. so because its amoled screen, those pixels wore out slightly quicker.
there is an easy way to avoid this problem, change to an all black color status bar. problem solved however you need to root in order to do this. good news is that now you can root without unlocking the bootloader, so HTC can never tell the phone was rooted, in case you were worried about voiding the warranty.
How can you root without unlocking the bootloader? And how do you change the color of the notification bar? Is there a simple themeing application like there is on jailbroken iphones?
Look in Developers section for the non-unlocking rooting thread.
(personally - I don't live in US so warranty means nothing to me, my phone was rooted after ~2 hours I took to check intact parts functionality).
Look up "Metamorph" in Apps section.
Another question, my girlfriend recently got the mytouch 3g. It works pretty decent and everything, but it is quite noticeably choppy. I would assume the nexus one is very smooth due to the 1ghz processor?
legion21 said:
How can you root without unlocking the bootloader?
Click to expand...
Click to collapse
Pretty easily: http://forum.xda-developers.com/showthread.php?t=710842
Does upgrading the HBOOT help with the wonky touchscreen heat-related miscalibration issues that every Nexus owner knows about?
I raised this question on a different thread:
http://forum.xda-developers.com/showthread.php?t=903975&page=9
but wanted to throw this question out to a larger audience.
This week I finally got tired of having intermittent but definitive touchscreen miscalibrations, usually associated with charging and/or heavy usage. HTC shipped a swap for me to use.
The new one works pretty well, except the camera takes pinkish tinged images, so it unfortunately will be going back. However, I noticed that the HBOOT is the newer 0.35.0017 (though the date displayed by the bootloader screen is Jun 14, 2010).
So I upgraded the HBOOT on my original N1, and have been trying hard to reproduce the touchscreen craziness. So far I've been unable to do it.
It's difficult for me to make it happen on demand. I "stress tested" it essentially by doing the things that normally bring it on, GPS with charger, and graphics intensive games. But I'm getting really tired of beating angry birds again and again =P
So, if you're still experiencing touchscreen wonkiness that is fixed by turning on and off the screen, which HBOOT do you have?
There are of course many other potential mitigating factors I've thought about. Custom ROMS. Kernels. Touchscreen protector. Radio version.
Just for completeness, there are different part numbers on the two:
Original N1 part # 99hke002-00 F
Replacement N1 part # 99hke002-01
Who knows what the significance of that is.
No it doesn't.
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
You know, as strange as it sounds, since I upgraded to the 0.35 HBOOT about a month ago, I have had zero issue with the digitizer. Call it coincidence, but that is what's happening so far.
We will call it coincidence for now =)
A happy coincidence.
waylo said:
Well shucks, I'm finding it harder and harder to get my touchscreen to screw up. I guess I should be glad!
How often does yours go off?
Click to expand...
Click to collapse
Not very often, in fact think it hadn't done it over the past week. I've been using the crap out of it customizing CM7 over this weekend and no hiccups.
our touch screen is always a hardware problem..
That's not the question. The question is if you're still having a lot of problems with your touch screen, which hboot do you have?
I was actually kinda wondering the same thing. I finally got around to putting on CM7 (build 39) on Friday (coming from CM 6.1). I right away had the impression that the screen was more responsive (the notification drop-down bar tipped me off) and I have not had a single episode of wonkiness with the screen since. CM 6.1 was a little weird for me and I had screen issues (especially the drop-down).
Oh well, even if it isn't the HBOOT, something has changed for the better for now
Another thing I learned recently is that on the native google navigation app, there seems to be a touchscreen dead zone directly vertical in the center of the screen (in landscape mode at least). It basically corresponds to the current street you're on if your navigation is active and your path is straight ahead.
So if you touch there and try to shift the screen around, you might mistakenly think the whole screen is awry. I think this is by design.
I'm not sure why it's there but it reliably is unresponsive to drags. So I'm not using that center area to gauge if my screens gone wonky.
Now if you hit the menu button, the buttons centrally do respond to taps.
Just had my first case of misregistering digitizer in a while. But instead of the whole bottom 1/3 of the screen going stupid it was just the bottom right corner, around the enter button/backspace if you have a portrait keyboard.
Oh well, it still works better than stock eclair!
So just as an update, the HBOOT definitely does not rid the digitizer issues plaguing everyone. It seems actually that my kernel had more of say in when/how often the issue surfaces.
I found that on Enom's Froyo ROM, problems arose more often with stock Enom than Pershoot or Wildmonks. However, each kernel has its own benefits.
Hey!
I bought my galaxy 6 months ago. Not long after I noticed a minor issue with my AMOLED display. I could see blue "artefacts" in some bright areas of the screen from time to time. Nothing serious, just blue dots and stripes, subpixels. I even posted a picture of it on reddit (second attachment) more out of curiosity than anything but was later convinced it was probably a software issue. I did have some suspicions something might be wrong with my phone but it actually happened so rarely and the issue was so minor that I just got used to it because it didn't bother me that much.
I recently flashed dark core 2.2 along with rc6 and it got *significantly* worse. I could see blue subpixels all over the screen wherever there's bright white, generally on the lowest brightness setting. Now, I believed that the hardware got worse and it's time to ask for a replacement. So before doing so I obviously had to flash stock firmware and guess what - it all disappeared. So I flashed just the dark core again to go back to rc6 - and it was back again.
The thing is, I really love this ROM and I love the voodoo improvements that come with it. I don't think I can live without them any more. On the other hand, it might be difficult to convince people from samsung that there's actually something wrong with my phone - since it happens so rarely on stock ROM. And I think that this display defect is intensified by the screen improvements from voodoo/dark core.
My only idea is to somehow make it show up on stock ROM and send it to them just then. But is this even possible without rooting my phone? Does anyone has an idea why would these blue subpixels show up in white areas? Is it something they check with specialized equipment or do they boot the phone first to see what's wrong?
Anyway, guys if you could point me in the right direction or had any better ideas... Seriously, It would be helpful even if you said that I should just return my phone and hope for the best. I'm a student and I can't really afford to be charged for returning - what they think is - an operational phone
I attached two pictures
1. a picture of how my screen behaves after flashing the latest dark kernel
2. a picture of how my screen sometimes behave on stock kernels
I'd appreciate any help or advice
I am not entirely sure, but it seems to me that I have lost some precision with the S-Pen after I updated to ICS. When I am writing I have a feeling that the drawn line is slightly off the "pencil point" then before, maybe only for a fraction of a millimeter which is affecting the text, it seems much worse now.
When I am writing something it seems a bit more "unnatural" then before.
The only calibration I have found so far is the left-right handed set-up and it is set-up correctly for me.
Anyone else notice this?
I too have noticed this, Although I cant compare it to GB because i flashed ICS within minutes of getting the Note.
I have googled for the calibration methods but none of them work, They all relate to turning on / off the auto rotation and tapping the pen in 4 corners.
Could really do with a proper screen calibration tool
My drawing is pretty pathetic at the best of times, but with this inaccuracy im getting bullied on Draw Something
There is app on Google Play Store with which you can off set Spen position on the screen. It's called Touchscreen tune. It's not free to make changes permanent but you can try it to see if it works for you.
So nothing for unrooted devices?
Has the JB update fixed this issue for those who have updated their firmware?
No, it hasn't fixed the issue however there is a program in google play that fixes it (albeit you have to pay for the full version). It is called touchscreentune (galaxy note) - you can change the offset of the tip and also change things like the sensitivity if the screen. I can confirm that it works on most XXLSZ ROMS with Philz (haven't checked it on pure samsung JB).
Hello people,
the last OnePlus OS update disaster was the cherry on the s***cake I call OxygenOS. After years of microphone, display and sensor issues I want to go back to the only brand where I had almost 0 issues: Pixel.
Since I am still very wary I have a few questions for people who had the possibility to use the phone for a while.
1. Are there working TWRP and root methods out there? How about the backup and restore of nandroid in TWRP? Does it work flawlessly?
2. How fast ist the camera? I remember on my Pixel 2 that you could take the phone out, take a shot and put it away. The image will be sharp and clear in 95% of the cases. In other phones I had to stay still for about 1-2 seconds out of fear the image will be blurry or smeared.
3. Does Google still provide OTA .zips and tools to flash, unlock and recover custom roms and images?
4. Is the adaptive brightness on point? OP7 always needs an ever so slightly readjustmet which makes it kind of pointless.
5. Does the microphone in whatsapp voice messages work flawless?
6. Would it be possible to migrate my data partition from OP7P to Pixel 5 without issues? I have 2 authenticator apps that I have a backup for but can't restore on my OP7P without bootloop... (see intro text).
Thank you!
1. I think TWRP was just released but I don't think it's very functional. you can go to that thread to get more information since I don't use it myself.
2. This could be just me but the camera viewfinder will definitely freeze for a few seconds before I can start taking a picture. And because of the mid-range processor, it does take a few seconds for the image to process. However I think this is done after the picture is taken so you should be okay taking a picture and then turning the screen off - since it seems to process the image in the background afterwards.
3. If you do a Google search for Google factory images you'll see there are zips you can download, both full fastboot zips and OTA zips. I normally Flash the OTA zip through stock recovery via adb sideload.
4. The adaptive brightness definitely does favour going dim more than it needs to. I'm guessing this could be fixed in a potential future software update though.
5. I don't use WhatsApp so not too sure about this one
6. Not too sure what you mean exactly by migrating but I personally use the app called Swift Backup to backup and restore my apps. And then I just manually drag and drop my internal storage to my computer as a backup.
anphex said:
Hello people,
the last OnePlus OS update disaster was the cherry on the s***cake I call OxygenOS. After years of microphone, display and sensor issues I want to go back to the only brand where I had almost 0 issues: Pixel.
Since I am still very wary I have a few questions for people who had the possibility to use the phone for a while.
1. Are there working TWRP and root methods out there? How about the backup and restore of nandroid in TWRP? Does it work flawlessly?
2. How fast ist the camera? I remember on my Pixel 2 that you could take the phone out, take a shot and put it away. The image will be sharp and clear in 95% of the cases. In other phones I had to stay still for about 1-2 seconds out of fear the image will be blurry or smeared.
3. Does Google still provide OTA .zips and tools to flash, unlock and recover custom roms and images?
4. Is the adaptive brightness on point? OP7 always needs an ever so slightly readjustmet which makes it kind of pointless.
5. Does the microphone in whatsapp voice messages work flawless?
6. Would it be possible to migrate my data partition from OP7P to Pixel 5 without issues? I have 2 authenticator apps that I have a backup for but can't restore on my OP7P without bootloop... (see intro text).
Thank you!
Click to expand...
Click to collapse
Currently root works fine. There is no function TWRP yet, at least last I looked, but things are fine without it. But more volatile but once things are set up right you're golden. I moved from a OP7P to a P5, as well, so I'll give you the run down.
Biggest, biggest gripe: vibration motor. It's pretty ****ty. Not like, oh god, get this out of my hand ****ty, but the OP7P's vibrator was much, much better. Phone speaker quality is much worse, as well, but for how small the p5 is, and the fact that it has no earpiece speaker, it makes quite a decent effort. Snappines; the op7p was so fast that double pressing the power button from screen off to pull up the camera will actually unlock and relock your screen before it even registers you double clicked the power button, and apps would launch instantly. The P5 isn't quite *that* fast, but it IS nimble. Lower your expectations for snappines, though I do feel that, with the proper modifications to animations, to the kernel, to the os, it could be comparable. That's definitely something OP mastered, that snappines and responsiveness. I think what would really make a big difference in that snappines is just animation tuning. For example, I wish screen on and screen off animations just didn't exist, and instead it was instant. As it is now, currently, it's a quick fade. Small gripes though. Gravity box can solve a lot of complaints, too lol
But, the question remains, what do you gain?
You gain updates. You're now at the forefront of features. You don't know what you're missing until you have a Pixel. Battery Life? It's.. well, let's just say that the op7p sucks compared to the p5. I can easily get 9+ hours screen on time even with heavy, heavy usage, bluetooth on, location, nfc, tons of apps in the background. This phone WILL get you through the day, 100% guaranteed. You get wireless charging, too, which is awesome. Charging is nimble but not dash-charge fast. You get a phone that you can use in one hand.
Overall, will it be for everyone? No. But, I can say with confidence, I'm not looking back. I have my complaints, one of the biggest being that Google Assistant just isn't reliable for me on my p5 compared to how it was on my oneplus, and also that the ding it makes when I use the hotword is just kinda gone for some reason and I have no idea how to fix it.
But yeah, ramble over, there ya go.
Thank you for sharing your point of view!
The thing is, I got the OP7P as a gift when it released and I never got warm with its huge size. I never wanted a huge phone like this but coped with it because it was/is top of the line. But over the time those already stated minor issues started to arise and accumulate.
So basically I don't want to gain anything, I want to get rid of the surplus.
As long as doesn't have issues that bothes me every day or at least less than the OP7P, everything is fine.
anphex said:
Thank you for sharing your point of view!
The thing is, I got the OP7P as a gift when it released and I never got warm with its huge size. I never wanted a huge phone like this but coped with it because it was/is top of the line. But over the time those already stated minor issues started to arise and accumulate.
So basically I don't want to gain anything, I want to get rid of the surplus.
As long as doesn't have issues that bothes me every day or at least less than the OP7P, everything is fine.
Click to expand...
Click to collapse
You'll find it doesn't feel as premium in the hand, as well. The majority of the body is plastic, though it's a very high quality, biodegradable plastic called bio resin. It also can heat up during normal usage, but not to an uncomfortable level. Outside of usual android gripes here and there, there's really not much to complain about. It gets the job done, as a phone, really well. Camera is fantastic, and I tried to see just how quickly you can take a pic from it earlier and you likely won't be disappointed. You can snap a picture before the viewfinder even loads, so it's unlikely you'll run into any issue. It automatically enables night mode depending on the light, but you can disable that auto night mode from a button near the view finder, so that pics are taken instantly. Everything about the phone is like that - very intentional and miticulous design, while still remaining stock android. Not quite custom rom levels of customization, though. No custom OS colors, things like that. OP wins in customization, for sure, but again, you probably won't be disappointed.