These commits:
7541c803fdb9f49f84bbc19217dce7cdc5c1748d
086b30d3c51f2cb9599fcb923918c58dfd099e19
929ee91e83a3ef380b9c0ab573185d28923c846d
in the CodeAurora kernel/msm.git tree (sorry, can't post the direct link because the forum won't let me) aosp/android-msm-2.6.32 head appears to add RGB666 support for the OLED display, which would help the banding problem many people observe in smooth, un-dithered gradients.
https :// www codeaurora org / gitweb / quic / la / ?p=kernel/msm.git
(remove the spaces)
It mentions that it is for the newer CDMA hardware revisions, so it may be that the shipping GSM hardware doesn't have the necessary wiring in place for the extra two bits. Has anyone tried building a kernel with this patch and tried if it works on GSM Nexii?
(Interestingly, this also confirms that the display is currently used only in RGB565 mode, thus everyone shouting "it's just a software problem in Gallery and Browser" is most likely wrong.)
Please tell me it's not a hardware limitation!
I can't test this as I'm currently at work, have you built a kernel with the patch?
Those who shouted software did so becuase the banding only occured in those 2 parts of the n1. 3rd party browser/gallery didnt not show the problem.
Heres that link so nobody else has to fix it themselves..
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git
Yeah the banding was not due to hardware because it didn't show up in some third party apps.
Well, having dug further into the kernel source (specifically, drivers/video/msm/mdp_lcdc.c and arch/arm/mach-msm/board-mahimahi-panel.c) I can confirm that on the UTMS/GSM revisions, the hardware interface to the OLED panel is definitely RGB565 (and on the upcoming CDMA/Verizon version it appears to be RGB666). What isn't clear to me is if and how dithering works in the qsd8k lcdc. Dithering in principle should work really well with OLED panels due to the fast update rate (assuming the lcdc->panel bandwidth is high enough). Edit: dithering (both temporal (i.e. driver level) and spatial (i.e. software level)) probably are why different application software shows different apparent color depth/banding.
Summary: current Nexii are definitely running in RGB565 (16-bit) color mode.
I haven't yet rooted my phone so I can't try a patched kernel, but given the run-time checks for the hardware revision before activating 18-bit (RGB666) mode in the new code, I would guess that current hardware doesn't physically wire those extra two lines (i.e. the sixth bit for red and blue). Still, it'd be cool if someone could try?
does it really bother you that much?..
Where have you all noticed banding or poor colors? Everything looks gorgeous at all times...
hugonz said:
Well, having dug further into the kernel source (specifically, drivers/video/msm/mdp_lcdc.c and arch/arm/mach-msm/board-mahimahi-panel.c) I can confirm that on the UTMS/GSM revisions, the hardware interface to the OLED panel is definitely RGB565 (and on the upcoming CDMA/Verizon version it appears to be RGB666). What isn't clear to me is if and how dithering works in the qsd8k lcdc. Dithering in principle should work really well with OLED panels due to the fast update rate (assuming the lcdc->panel bandwidth is high enough). Edit: dithering (both temporal (i.e. driver level) and spatial (i.e. software level)) probably are why different application software shows different apparent color depth/banding.
Summary: current Nexii are definitely running in RGB565 (16-bit) color mode.
I haven't yet rooted my phone so I can't try a patched kernel, but given the run-time checks for the hardware revision before activating 18-bit (RGB666) mode in the new code, I would guess that current hardware doesn't physically wire those extra two lines (i.e. the sixth bit for red and blue). Still, it'd be cool if someone could try?
Click to expand...
Click to collapse
You build the kernal and I'll try to flash it.
Deathwish238 said:
Where have you all noticed banding or poor colors? Everything looks gorgeous at all times...
Click to expand...
Click to collapse
Whenever I make a wallpaper with gradiant I see very bad banding. Drives me nuts when I look at it.
Says "post-EVT1 CDMA revs" will have RGB666 support. EVT1 is a board rev, probably similar to PVT, DVT.
Also, system rev value has to be greater than 0xC0 to support RGB666. My new ATT N1 seems to be 0x81 (via dmesg).
See http://arstechnica.com/gadgets/news/2010/03/secrets-of-the-nexus-ones-screen-science-color-and-hacks.ars for more info on this.
Anybody want to hardcode the rgb666 support into a kernel to see if it works on the older N1s? I'd be willing to test a boot image... worst case it just doesn't show anything and you can reboot it right?
satadru said:
Anybody want to hardcode the rgb666 support into a kernel to see if it works on the older N1s? I'd be willing to test a boot image... worst case it just doesn't show anything and you can reboot it right?
Click to expand...
Click to collapse
Worstcase your N1 is frazzled and burns your house down
Flashing a boot image with RGB666 support will do nothing to the N1 lol it will not boot so you re flash the one from the .zip (CM or whatever) and it will be back to normal :-D
Ill test if anyone wants, just build me the kernel :-D
Yeah you can always just use fastboot to boot a new kernel to test without actually writing the kernel to the flash on the device.
I haven't seen any of this banding you guys speak of but the one thing I did truly notice when comparing my nexus to my friend's droid side by side is WHITE. White has a blueish tint to it... Blacks obviously look awesome but there is something whacked with the white.... you can really see it reading a webpage with black txt and white background thats what we were comparing....
I really doubt this is a hardware failure on the screen part... color dept and tuning is usually a driver thing... I'm sure someone will figure out how to tweak the color stuff eventually.
Zenoran said:
I haven't seen any of this banding you guys speak of but the one thing I did truly notice when comparing my nexus to my friend's droid side by side is WHITE. White has a blueish tint to it... Blacks obviously look awesome but there is something whacked with the white.... you can really see it reading a webpage with black txt and white background thats what we were comparing....
I really doubt this is a hardware failure on the screen part... color dept and tuning is usually a driver thing... I'm sure someone will figure out how to tweak the color stuff eventually.
Click to expand...
Click to collapse
See the banding pics here:
http://arstechnica.com/gadgets/news/2010/03/secrets-of-the-nexus-ones-screen-science-color-and-hacks.ars
I just built a kernel that forces RGB666 to run on older hardware revisions. I'm flashing it but I don't expect it to boot, or if it does, work.
edit: well, it booted, but I don't see a difference at first. Any test patterns?
coolbho3000 said:
I just built a kernel that forces RGB666 to run on older hardware revisions. I'm flashing it but I don't expect it to boot, or if it does, work.
edit: well, it booted, but I don't see a difference at first. Any test patterns?
Click to expand...
Click to collapse
Huh... well you could try the pictures from the arstechnica link above. Only trouble is they don't show banding in the actual browser, only in the gallery. So you'll have to save them. This is likely going to be a very difficult thing to test since the banding issues are so sporatic(likely because different apps do things differently throughout the phone)
coolbho3000 said:
I just built a kernel that forces RGB666 to run on older hardware revisions. I'm flashing it but I don't expect it to boot, or if it does, work.
edit: well, it booted, but I don't see a difference at first. Any test patterns?
Click to expand...
Click to collapse
There are a bunch here.
http://www.metalev.org/2010/03/generating-false-color-images-on-nexus.html
TheDudeOfLife said:
There are a bunch here.
http://www.metalev.org/2010/03/generating-false-color-images-on-nexus.html
Click to expand...
Click to collapse
I think that problem is entirely different from the color depth issue. That more has to do with the subpixel layout of the screen. I need patterns to actually test the color depth of the screen.
In any case, they did not look any different between the stock cm-kernel and my build.
edit: I think it's safe to say that there is absolutely no difference on this hardware. For those wondering, it's a really simple tweak. Just get rid of the restraint that checks for system rev (if (system_rev > 0xC0)) in board-mahimahi-panel.c.
Related
I believe I am unable to use this kernel because the frame rate is uncapped. This causes my display to go fuzzy as the GPU doesn't like something about the difference. I have noticed this on every kernel that has been uncapped has this issue on my device. Is there a way to turn this off (by app or otherwise) or perhaps there's a version of overstock kernel that that is still "capped"?
The only BLN kernel I have used with any success is the Categorically Worthless one. However, I think that kernel has a bug that mutes the mic in my bluetooth headset during a call. Very annoying. This kernel is no longer being maintained so I don't expect there to be any resolution if it is the kernel. So, I thought I might replace it with overstock aside from the fuzzy display. The stock (voodoo) KA6 / KA7 kernels don't manifest either of these issues. I would prefer not to have to give up BLN.
I am unaware of any other kernel that includes BLN but does not uncap the FPS. So if anyone knows of another without either of the above issues that also has BLN support, please post it here. I'm still using the CW kernel for BLN support but would prefer to move to something else. Any assistance would be much appreciated.
No one? Really?
Have you sent a PM to the developer of the kernel?
s15274n said:
Have you sent a PM to the developer of the kernel?
Click to expand...
Click to collapse
Thanks. Yes, I have sent a PM to both devs (at different times). I don't expect a reply from either dev as their time might be too valuable. I understand and have no problem with this should it be the case. While I wait for a reply from either I was hopeful that some one would have a discovered a workaround or kernel.
Fuzzy display? You could try changing your LCD density to something smaller than 240 (I use 210) because it makes everything look sharper for a temporary fix?
It's like changing the resolution on your computer from 640x480 to 800x600 .
buru898 said:
Fuzzy display? You could try changing your LCD density to something smaller than 240 (I use 210) because it makes everything look sharper for a temporary fix?
It's like changing the resolution on your computer from 640x480 to 800x600 .
Click to expand...
Click to collapse
This is all new to me, where do you adjust this? Settings > Display (not in front of my phone).
Same issue here
Sent from my GT-I9000 using XDA Premium App
buru898 said:
Fuzzy display?
Click to expand...
Click to collapse
Yes. It's hard to explain. It's like the refresh rate (Hertz) is off or something. The screen occasionally jitters or shakes like it's having a seizure.
buru898 said:
You could try changing your LCD density to something smaller than 240.
Click to expand...
Click to collapse
I've changed this before to see how it looked but have been running the stock density since. I don't want to change that. The stock kernels and CW kernel don't have this issue at any pixel density. Thanks for the potential workaround / input.
s15274n said:
This is all new to me, where do you adjust this? Settings > Display (not in front of my phone).
Click to expand...
Click to collapse
You won't find it there. You'll likely want to download an app (easiest way) from the market to do or edit your "build.prop" file. You can edit on the device with Root Explorer. Otherwise you can pull it onto the computer then push it back after changing it.
Well, I updated my CW kernel. An unexpected update, I'm going to take it for a spin.
Same thing happens to me, it makes my entire screen slightly jitter/appear to shake. Thankfully for me, once I power the screen off and back on, the jittering goes away completely until the next time I reboot the phone. It comes back after every reboot, but being able to clear it as easily as I have been is a small price to pay for an awesome kernel.
For those unaware or those who have come to this thread for answer to the questions I originally had, you might benefit from the (uncapped) kernel here...
http://forum.xda-developers.com/showthread.php?t=994694
The vsync hack boosting in some case the screen refresh to 65Hz is flawed, it does that and I don't recommend it.
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
seansk said:
is there a way to mod the camera flash so it lets me use it even if the battery is really really low...I want to set the threshhold at 0 percent...sometimes...I just need to take a pic...and 20 percent is more than enough for one quick flash for a pic.
Click to expand...
Click to collapse
anyone? please???
seansk said:
anyone? please???
Click to expand...
Click to collapse
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
frodoboy said:
When does it prevent you from using the flash? I've used mine at less than 20% but have had wifi, gps and data connection turned off. I wonder if unchecking the power saver and efficiency boxes would help?
EDIT: Okay, I see what you mean. I finally got it to say the flash couldn't be used because the battery level is too low. I turned off power saving and it still didn't work. I tried ProCapture which I like a lot because it doesn't compress the images thus better quality. It has a "torch" option on its flash menu so I tried that. The flash stays on continuously in that mode, even with a low battery. I took a shot in total darkness and it didn't seem to work. the flash was on but no picture? Maybe with some light it would work? ProCapture is free to try so you might want to try it to see if that would work under normal night conditions. I guess it won't work in total darkness like the auto flash will.
Another edit: I noticed that the flash was disabled right at 15% so I did some searching and found this: With root explorer (or any rooted file explorer), go to sys/camera_led_status/low_cap_limit. There you will find the number 15 for 15%. I tried to change this to 5 but the file is locked and I don't know enough to unlock it, rename it and then change it through adb. I think I read that you can't do this through root explorer. Maybe someone with knowledge of how to do this will know how to do it. I'm sure it is relatively simple and a zip file could even be written to change it. At least we now know where the setting is!
Click to expand...
Click to collapse
Yes thats exactly what I did in root explorer in sys/camera_led_status/low_cap_limit, I set it to 5, 1, 0, did not make any difference. Also Its retarded that you cannot use flash while you're in a call....if you talking to someone and trying to take a picture it says you cannot use flash since you're in a call....wtf does that have to do with the flash!!! There should be a file somewhere in the sense UI system to change these settings, If anyone has found anything please share...or if you can think of something please share as well...
I actually like the dialer and contact aspect of sense UI and how it integerates and automatically finds linked friends, how it updates friends status in facebook and twitter, (although they still need to integrate google plus)...all the other stuff of sense I do not like...I've changed to ADW ex...and widget locker...
I doubt there's a way to get that stuff with a senseless rom since its so integerated into the system...If there is I would flash another rom in a sec and just install that aspect of sense....
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Binary100100 said:
I got a better one for you.
Turn on the wireless access point feature, activate the camera and try to use the flash.
Click to expand...
Click to collapse
you gotta be kidding me!!!!
question 1. Are the other roms the same?? I"m unlocked and rooted but on stock rom. do senceless, beastmod or revolution have the same problem...I'm guessing they would since they use the same camera apk...or maybe not, If not i'm flashing to something else RIGHT NOW.
questions 2. are we ever going to see CM9 on the amaze....screw sense I want ICS AOSP asap...
seansk said:
so apparently I can't use flash under 20% battery...under a certain temperature and when I'm in a call...So basically don't use flash....lol....I messed around with files under sys/camera_led_status which I believe controls temperature and battery limitations and also /sys/android_camera_awb_cal which I believe limits flash while you're in a call...I backed up deleted the directories and rebooted but they came right back...is this part of the kernel...I believe this requires S-off because I am unable to change this part of the system...or perhaps someone can do a quick kernel mod and take off all those limitations...
Click to expand...
Click to collapse
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
frodoboy said:
As I understand it, you tried to change the value to 0, 1, 5 and it still didn't work. If you looked at the file, it was still set to 15 right? I think you have to unmount the system, then pull it from your phone to your computer, alter the file and then push it back to the phone and remount the system. I have no idea how to do that. Binary is pretty good at writing little zips to do that sort of thing. I don't know if permanently changing that value will do anything though. I do know that root explorer says it changes the file but it doesn't.
Click to expand...
Click to collapse
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
seansk said:
crap I wish I was a developer!!! instead I had to go and fix teeth and become a dentist!!! but I'm very much into electronics. Is there a book I can read to start developing?
btw where do I post the request? in development or general?
Click to expand...
Click to collapse
I would suggest in the forum that consists of the kernel that you are using.
Example:
If you have QuikSense then post the request in the QuikSense forum or PM the developer (in this case xboarder56) directly.
If you use Faux's kernel then post it in that thread.
No need to start a new thread for a request. However if you feel that it is absolutely necessary do it in General because the Development section is not really a section mod requests.
Binary100100 said:
I tried changing this by root explorer as well. The directory already says that it's R/W so I tried changing these values. As a result I was unable to force the changes either. I'm curious if something else changes the values back. Perhaps the camera app itself? I have no idea why the directory is set to r/w. However if you check any custom rom you will not see a /sys directory in there which makes me believe that it is in fact kernel related. That being said you would have to decompile the kernel itself, edit those values and reflash the kernel again. I might be able to do this for you however since everyone seems to have a different kernel and suffer from ORD (obsessive rom flashing disorder) I would find the work as pointless. My suggestion is to request it from your favorite developer for future kernels.
Click to expand...
Click to collapse
Thanks Binary. You are sooooo smart!!
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
faux123 said:
Flash limitation is controlled by kernel... Not sure why HTC decided to do that, but I can easily change this value in my next release from 20% to 10% or 5%.....
Of course if you decide to use the stock kernel, there's nothing much you can do about it... It is hardcoded in the kernel code.
Happy New Year!
Click to expand...
Click to collapse
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
seansk said:
Thanks
I think 5 percent is reasonable...also can you change the limitations for temperatureand also take off limitations when making a call and using wifi hotspot...the phone does not allow to take flash while its in low temp, when making a call or when using wifi tethering/hotspot.....thanks faux
Click to expand...
Click to collapse
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Binary100100 said:
Yeah that's HTC for you. Always thinking ahead. You never know when your phone might be damaged by taking a picture with the flash activated while using it as a hotspot. In regards to the cold... I live in Detroit, work at night and I've used it a couple of times without issue. How cold does it have to be? I kinda wanna see this! LOL! It's gotten down to about 19F here... can't remember if I had used the camera though.
But I can understand why you wouldn't want to use the flash in cold weather. Might cause an avalanche or wake a bear or something. Yikes! Smart thinking HTC!
Click to expand...
Click to collapse
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
seansk said:
lmao....it bothers me that I'm talking to my gf and she wants a picture of something i have to hang up take the picture send then call back wtf!!!!! and don't even get me started on wifi hotspot...how does this make sense????????????????? sense ui should be called retarded ui cause it does not make "sense" no pun intended.
Click to expand...
Click to collapse
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Binary100100 said:
To HTC or to whomever it may concern,
I intend to propose a class action lawsuit pending on verification of an intentional design flaw that prevents the consumer to use the flash on the device while talking on the phone while also using the device as a wifi hotspot in subzero degree weather. I discovered this flaw while taking pictures of Bigfoot eating Santa's raindeer at the North pole just after Christmas. Unfortunately I was unable to take proof of evidence of the situation because of the mentioned designed flaw. While I was on the phone with animal control they demanded photographic evidence of the situation. Because I was not able to comply due to this design flaw the raindeer could not be saved thus there will be no more Christmas. Evidence of the intention for the mentioned limitations is the simple fact that the appropriate error messages are programed into the kernel source. However because you fail to include the wireless drivers, the kernel source cannot be utilized to compile a patch for this flaw.
Shame on you HTC.
I should be a prosecutor.
Click to expand...
Click to collapse
omg rotflmao........so basically we really can't fix the hotspot issue or the call issue!!....I'm beginning to not like HTC...and I definitely don't like sgs2...I better start designing my own phone....the N1 never had this kind of BS problems....I used it as hotspot...called...took pictures alll the way down to 0 battery and it was made by HTC...what changed??? I still like my N1 better lol...hopefully next year we'll get
new years resolution dream phone:
720p super amoled PLUS "not pentile" screen
8 or more Mega pixel back side illuminated sensor with a f/2.2 or less and a wide lense camera lense with good optics and good audio quality while recording video.
able to use flash without limitations!!!!!!!!!!!!!!!!!!!!!!!!!
no flash bleed into camera sensor that requires 3 rounds of electrical tape
No screen bleed from the soft buttons
10 hour talk talk battery preferably over 2200 mAMp battery
STOCK ICS with custom amazing camera software like that amaze has now.
NO CARRIER BRANDING NO BLOATWARE. is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them...ok maybe this last one is asking too much.
is this so much to ask???
seansk said:
...is this so much to ask
a phone that can drill and fill my patients teeth, do root canals and make crowns for them... is this so much to ask???
Click to expand...
Click to collapse
Ummm... yes. I believe the best you can do is create a phone with a jackhammer for a vibration mode, shove it in the patients mount and keep calling it. But of course some other people would use it for... inappropriate purposes.
Example from one of SassyBoB's reviews: https://market.android.com/details?...t=W251bGwsMSwyLDEsImNlbml4LmFuZHJvaWQudmJyIl0.
So today, I put my friend's SII right next to mine and pulled up images on both to compare. She got hers in December and is running the older build, and I got mine a month ago and am running the latest update from Samsung/at&t.
I noticed that aside from the worse battery life, mine also has a skewed screen saturation. It's way more unnatural and quite dark (the blacks and their contrast make it almost impossible to see) and the whites are more dull. On hers (not updated), the screen color was excellent, just like how I saw on the Skyrocket and the Infuse, with more brighter colors and whiter whites. Both were set to auto brightness and then on every other brightness level to rule that out as being the cause. Even on auto brightness (and really, on every brightness level), hers was always a little bit more "brighter".
So, did anyone else notice the different color change when they updated to the newest build? I would like to know, in case it is my actual phone hardware that is being the issue.
Samoled screens vary so inconsistencies are there, other than that try setting your "screen mode" to dynamic in display settings. Might have been different compared to your friends the whole time. The last thing you could do is wait for Supercurio as he is working on a screen tuning app. http://forum.xda-developers.com/showthread.php?t=1241590
silver91342 said:
Samoled screens vary so inconsistencies are there, other than that try setting your "screen mode" to dynamic in display settings. Might have been different compared to your friends the whole time. The last thing you could do is wait for Supercurio as he is working on a screen tuning app. http://forum.xda-developers.com/showthread.php?t=1241590
Click to expand...
Click to collapse
Oh wow, I didn't know SAMOLED screens could vary by that much, thanks for the heads up. I tried looking for the screen mode option, but it seems like it's only on the international version (or perhaps also on the older official Samsung/at&t ROM, mine doesn't have that option).
I'll first try waiting to see if anything gets changed for the upcoming ICS update. If not, I may just have to go back to the good old days when I was flashing like a mad(wo)man when I was on the Infuse 4G.
Very common thing apparently. I have three co-workers who also have a GS2 and two of them look more "blueish" than the other two. We compared them on the simple google.com page with brightness all the way up on each phone, with stock ROM's.
It's the same thing with any phone. Put two iphones next to each other and the screens will look different.
harlenm said:
It's the same thing with any phone. Put two iphones next to each other and the screens will look different.
Click to expand...
Click to collapse
True, but two iPhone's together still aren't even as good as one Android IMHO.
yohannie said:
Oh wow, I didn't know SAMOLED screens could vary by that much, thanks for the heads up. I tried looking for the screen mode option, but it seems like it's only on the international version (or perhaps also on the older official Samsung/at&t ROM, mine doesn't have that option).
I'll first try waiting to see if anything gets changed for the upcoming ICS update. If not, I may just have to go back to the good old days when I was flashing like a mad(wo)man when I was on the Infuse 4G.
Click to expand...
Click to collapse
It's available on customized AT&T firmwares and ported international firmwares.
One of MANY features AT&T intentionally removed and why I basically no longer ever touch AT&T-mangled crap.
No third party app I've found is able to change the camera exposure -- whether on the stock rom or the others I've tried, it just stays the same, no matter what you set it to. Looking through these forums, it seems this is a pretty well-known problem, but I couldn't find a solution.
Is there still no known way to fix this? Do any alternate roms or kernels help?
freakified said:
No third party app I've found is able to change the camera exposure -- whether on the stock rom or the others I've tried, it just stays the same, no matter what you set it to. Looking through these forums, it seems this is a pretty well-known problem, but I couldn't find a solution.
Is there still no known way to fix this? Do any alternate roms or kernels help?
Click to expand...
Click to collapse
i don't think our phones have the hardware capable for this . there may be away to simulate it but true exposure timing adjustment is mechanical
shadowgrower420 said:
i don't think our phones have the hardware capable for this . there may be away to simulate it but true exposure timing adjustment is mechanical
Click to expand...
Click to collapse
True, but it is definitely capable of adjusting the exposure when it detects brighter or darker light. It's unfortunate that unlike my horrible old HTC phone (Wildfire S), the functionality doesn't seem to be exposed in software...
i believe the iso is adjusted not the exsposure, to assist with light .
Hey guys.
So I love my pocophone and the latest beta update (i'm actually using Xiaomi.eu Rom) does seem to improve a lot with the phones touch lag issue; however, I still kept getting some stutters during scrolling and in particular vertical scrolling. I believe this might be due to screen response times mismatching with screen refresh rates. I believe so because if I dragged my finger at relatively slow speeds (approx 7.5 s to go the entire vertical length of the screen) across even a relatively small page (my app drawer for example), the page would jump as if it didn't track my finger for a split second.
So things I did without much success:
1. used other kernels: franco and extreme (extreme kernel with 65 Hz screen refresh rate was a bit better though)
2. changed animation speeds. (also turned off animations)
3. turned off mi optimizations etc.
Today I found this old forum post on xda (https://forum.xda-developers.com/android/software-hacking/mod-increase-frames-5-14-15-t3108786). The author changes the egl swap interval to allow better screen refresh and fluidity. I am not an actual developer so from what I read, it seemed like it might be a decent thing to try. I didn't flash anything however I used the terminal command "setprop debug.egl.swapinterval -60" as suggested by author. This won't stick past a reboot but I think it did help with scrolling smoothness and fluidity.
I was hoping you guys could try it and let me know if there are any differences for you guys.
PS: Again, I'm just tinkering and trying to see what happens. Hoping to get some input from others just in case what I see is placebo. Didn't have any negative effects and I hope you don't either.
I really want to buy this phone but if the "stable" update does not correct all the touch issues (which i strongly believe it is a software issue), i won't buy it.
Of course you have that right. But a few things. Firstly, the phone is great, please use it for a bit to experience this. Secondly, I am being knitpicky and actually most people are reporting no issues whatsoever. In fact, this post is about the fact that I am not currently seeing the stutters. I am wondering if it's because of the changes outlined above and was hoping we could figure out together. Might even be that something else I changed corrected the issue. I just didn't realize it then. Lastly, if you're looking for the perfect phone without any issues, you might have to look away from "flagship killer" type phones. These phones typically give performance that comes at the cost of tiny issues. So are you a fan of the best bang for your buck, the highest highs of performance at the cost of minor tradeoffs that you can work with an active community to fix. Or do you want a perfectly smooth experience. At this price point, you don't really get both.
If the command has helped you you can set the command to run on startup. And try to use a stable build.
The Restless Soul said:
I really want to buy this phone but if the "stable" update does not correct all the touch issues (which i strongly believe it is a software issue), i won't buy it.
Click to expand...
Click to collapse
The touch issue is not software issue. It has been partially corrected through software, but it will never be fixed. If you want to buy a poco, be sure to search one from December batch because it has the Focaltech panel which is ok, and not the Novatek panel which is the ****ty one.
neinfricatu said:
The touch issue is not software issue. It has been partially corrected through software, but it will never be fixed. If you want to buy a poco, be sure to search one from December batch because it has the Focaltech panel which is ok, and not the Novatek panel which is the ****ty one.
Click to expand...
Click to collapse
And how can i make sure the phone is from December batch?
The Restless Soul said:
And how can i make sure the phone is from December batch?
Click to expand...
Click to collapse
It is written on the box. 12.2018
neinfricatu said:
It is written on the box. 12.2018
Click to expand...
Click to collapse
I highly doubt i can return my phone because it doesn't have the non-touch issue panel.
Any other way to check the batch without checking the box?
The Restless Soul said:
I highly doubt i can return my phone because it doesn't have the non-touch issue panel.
Any other way to check the batch without checking the box?
Click to expand...
Click to collapse
Ask the seller in advance..
neinfricatu said:
Ask the seller in advance..
Click to expand...
Click to collapse
I'm buying the phone from an local online store, that's the issue
I haven't noticed any kind of screen lag. Date on box: 09.2018, don't know what panel that would be.
10.2.2.0 stable, faultless performance.
SimboXXX said:
I haven't noticed any kind of screen lag. Date on box: 09.2018, don't know what panel that would be.
10.2.2.0 stable, faultless performance.
Click to expand...
Click to collapse
Not even touch delays/ghosting?
The Restless Soul said:
Not even touch delays/ghosting?
Click to expand...
Click to collapse
No, no problems at all.
There is a new update that is told to fix the screen issues. Has anybody tested it?