Related
Can you change the trackball colors on the nexus one?
Mod Edit:
Per lilHermit:
OK I've moved the initial su request to before the main screen is drawn to see if that helps.
lilHermit
Click to expand...
Click to collapse
Apk:
TrackballColoursConcept.zip
Yup, this, too, was one of the big surprises for me today when I got mine. I use and love several apps that flash the notification LED different/custom colours, but on the Nex1, the only colour I get is white.
I'm really, really, hoping that OS2.1 just changed the API and that updated apps will be able to do colours. I'm really, really scared that they cheaped out and put a white LED behind the trackball. >.<
][
People are saying that when Bluetooth is paired is flashes blue.
I heard when you have voicemail it flashes red. I haven't tried any of them yet though so I wouldn't know.
its a tri color led so it CAN do any color its just a matter of the third party apps adapting to be able to control it, cant wait
White, red, blue....
Anyone else wish they had green?
Though it was very patriotic of HTC.
AndroTMO said:
Anyone else wish they had green?
Click to expand...
Click to collapse
all colors can be reproduced... just depends on the software that lights up the ball.
indeed it can be changed
unfortunately it stops working after a notification is fired...
Install NotifyLight from XDA:
http://forum.xda-developers.com/showthread.php?t=575024
then set up the pulselight on and change the values in:
/sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/jogball-backlight/color
ie:
Code:
adb shell echo "255 0 0" > /sys/devices/platform/i2c-adapter/i2c-0/0-0066/leds/jogball-backlight/color
this will give you a nice red jogball.
"255 0 0" is in RGB format.
And off course you need root for this to work...
AndroTMO said:
White, red, blue....
Click to expand...
Click to collapse
When white, it is actually the red, green, and blue all on at the same time.
Would love to see an app to configure all sorts of different notification colors for missed calls, texts, emails, etc, and the blink frequency.
Btw.. MissedCall works, but it can't change the colors.
Once the SDK drops for 2.1 and Nexus One codes and such are released, we should have notifications fixed and custom notifications.
http://twitter.com/missed_Call
I have to say that Google disabled multicolor LED notifications on the Nexus One! (the hardware can do them) #missedCall #NexusOne #fail
xManMythLegend said:
http://twitter.com/missed_Call
I have to say that Google disabled multicolor LED notifications on the Nexus One! (the hardware can do them) #missedCall #NexusOne #fail
Click to expand...
Click to collapse
I can't even to express how disappointed I am at this news. Multicolored notifications was one of the most useful features for me...
cliffy15 said:
I can't even to express how disappointed I am at this news. Multicolored notifications was one of the most useful features for me...
Click to expand...
Click to collapse
As are others. Seriously pissed.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=0493493845dff4e4&hl=en
From all this drama going on, I'm gonna assume this guy has noooo idea what he is talking about:
Or what o_0
... and seriously over reacting.
Eclair~ said:
From all this drama going on, I'm gonna assume this guy has no idea what he is talking about:
Or what o_0
Click to expand...
Click to collapse
Well, it's unlikely that there are 3 led's in there, just one tri-colour.
I've just installed the NotifyLight application and echo'd values to is and it works fine.
People are seriously over reacting, suggesting that this is a deliberate move by google - get a grip, it's probably an oversight. I agree that it's very useful to have but I'm not throwing my toys out of my pram over it.
SC
ScaredyCat said:
Well, it's unlikely that there are 3 led's in there, just one tri-colour.
I've just installed the NotifyLight application and echo'd values to is and it works fine.
People are seriously over reacting, suggesting that this is a deliberate move by google - get a grip, it's probably an oversight. I agree that it's very useful to have but I'm not throwing my toys out of my pram over it.
SC
Click to expand...
Click to collapse
Every sign including feedback from one of the most popular notification apps Devs points to it not working.
If all of a sudden custom ringtones and contact pictures were removed you'd see the same reaction.
Google already closes off the ability to add codecs or EQ bands.
Considering how many apps took advantage of this I dont see why peoples reactions arent justified. You dont pay 500+ for something to lose functionality.
xManMythLegend said:
Every sign including feedback from one of the most popular notification apps Devs points to it not working.
If all of a sudden custom ringtones and contact pictures were removed you'd see the same reaction.
Google already closes off the ability to add codecs or EQ bands.
Considering how many apps took advantage of this I dont see why peoples reactions arent justified. You dont pay 500+ for something to lose functionality.
Click to expand...
Click to collapse
I'm not saying it's not, not working (without rooting). I'm suggesting that the mechanism (API and underlying implementation) has simply changed and it's an oversight. Looking at the link you provided earlier there was mention that the notification API hasn't changed in a long time.
"The SDK hasn't change in terms of Notifications since SDK version 1."
Perhaps that's the reason it's not working, perhaps the API needs an update rather that being deliberately disabled as that poster went on to say.
"Google just disabled that feature in Android 2.1."
That's simply an unsubstantiated claim by someone on the internet.
People are suggesting that this was a deliberate move by google to close off Android bit by bit. Perhaps waiting until we get some sort of response rather than flying off at the deep end is the best course of action.
2.1 is a new release and the Nexus One is a new device. That's what you paid for. You're an early adopter and really should understand that things might not be perfect in the first instance.
Since you're a senior member of the forum and by implication have been in here for a while and have obviously had more than one android phone, I'm a little surprised and your outrage.
SC
ScaredyCat said:
I'm not saying it's not, not working (without rooting). I'm suggesting that the mechanism (API and underlying implementation) has simply changed and it's an oversight. Looking at the link you provided earlier there was mention that the notification API hasn't changed in a long time.
"The SDK hasn't change in terms of Notifications since SDK version 1."
Perhaps that's the reason it's not working, perhaps the API needs an update rather that being deliberately disabled as that poster went on to say.
"Google just disabled that feature in Android 2.1."
That's simply an unsubstantiated claim by someone on the internet.
People are suggesting that this was a deliberate move by google to close off Android bit by bit. Perhaps waiting until we get some sort of response rather than flying off at the deep end is the best course of action.
2.1 is a new release and the Nexus One is a new device. That's what you paid for. You're an early adopter and really should understand that things might not be perfect in the first instance.
Since you're a senior member of the forum and by implication have been in here for a while and have obviously had more than one android phone, I'm a little surprised and your outrage.
SC
Click to expand...
Click to collapse
In and of itself youre 100% right.
But in context with every thing that has been coming out in the last week there could be much more to it.
For all I know there could be something N1 isnt capable of long term that these types of notifications may exploit.
Via Twitter and another via Email Ive seen 2 devs of notification apps confirm that the LED lights and patterns cant be manipulated.
Sure it can be an oversight or just some hitch. Perhaps Im giving these devs too much credit.But its the sqeauky hinge that gets the oil. While it may annoy other posters theres simply no better means than to continually raise a ruckus. Im not up in arms saying screw google F the nexus. Just being adamant about displeasure.
The only way any of us can expect a response is by having these conversations.
The 3g/edge issue doesnt seem to effect me but if its there a stink should be raised.
Frankly if a fix came out tomorrow for the rooted community and never by google Id be just as annoyed. I want the OS to move forward not backwards.
One gripe I have with my Nexus One is the inaccuracy of the colors on its screen. They appear oversaturated esp. with the reds.
Is there a fix for this or will it be possible that a firmware update may fix this in the future?
My understanding is it could be trivially fixed with a firmware update. I think the reason none of the modded/third-party kernels have done is is because it would require special colour measurement equipment, and (given that the technical docs for the AMOLED are not publically available) quite a bit of patience.
See http://android.git.kernel.org/?p=ke...74950cb35551;hb=refs/heads/android-msm-2.6.32
-- you can see the RGB gamma tables. Tweaking these should be able to change the saturation, colour balance, colour temperature, and theoretically (mostly due to changing the color temperature) improve brightness and display life.
One disadvantage of AMOLEDs at this point in time [since they are relatively new] is the software isn't exactly up-to-date with the hardware... and like @hugonz, we need to have info abt the hardware to tweak the software...
craigacgomez said:
... and like @hugonz, we need to have info abt the hardware to tweak the software...
Click to expand...
Click to collapse
That's not exactly what I said; it would be easier with hardware documentation, but the table looks pretty self-explanatory to me (for each brightness level there is a 7-point gamma curve for each of the R, G, and B components). I haven't yet rooted my phone but it's something I'll definitely look at doing once I start working on kernels (assuming no-one else does it first). Maybe I should try plotting the curves to see if that would inspire any kernel devs to try hacking on this issue now.
@hugonz, I understood ur point... but for us it's more a trial and error effort... and different AMOLEDs probably have different tweak values...
Well I hope it gets started as soon as possible.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I have installed Paranoid Android on my Note and noticed that there is severe clipping in the CM9 UI elements. Even the default ICS wallpaper , the one with the"rainbow" coloing stripes show severe clipping on the lockscreen. It looks just plain ugly. And since most of the CM9 UI backgrounds are a shade of grey, there is severe clipping of these grey elements to a purplish pixellation and to black. You can notice this if you take the settings page in Paranoid android or any other CM9 based ROM (assuming most CM9 based ROMS have the same default theme) Look under the status bar where the grey background fades to black and you may notice severe pixellation like issues at that area. Now, go to advanced, screen settings and MDNIE mode, you will notice that the clipping keeps changing when changing modes but its still there in every screen mode.
How many of you are experiencing this? Assuming a majority of the people who run Custom ROMS run a CM9 based ROM, why isnt this issue reported anywhere? I'm asking because, the issue is plainly visible in these grey areas and UI elements making the visual experience really bad. And why is Gamma Control disabled in these CM9 kernels? I believe lowering the gamma would solve the problem.
I've noticed that CM9 kernels have the worst clipping whereas in other stock based kernels, the clipping is comparitively lower, closer to the stock kernels.
So once again users of CM9, please do report if you face this issue.
CM9 users please report back because I havent seen anybody talking about this issue in any of the CM9 related ROMS thread. People seem to ignore an issue which stares back right at the face even in ambient lighting. Why havent this been reported?
I dont have much idea about who develops CM9 kernels for the note. How can we contact the CM9 developers and let them know of this issue and request to enable Gamma Control within the kernel?
Somebody please help me out here. Because its been a month after I bought my note and I've been struggling and doing my best to find a solution to this horrible clipping. I had got in touch with GSMArena and got this issue published, yet Samsung never responded, I tried kernel after kernel and realised that the intensity of the issue varies from kernel to kernel. I've seen that whomever I ask about the clipping in this forum says they have it but then everyone seems to be happy running different ROMS and in these CM9 based ROMs which look as close to stock Google ICS UI have severe clipping all over the UI and yet people dont seem to bother.
So what can I conclude from this? Is this an isolated issue or are all of you Note users who have this issue just keeping silent and living with it?
I do not mean to spoil anybody's peace or anything. I clearly dont know how to get in touch with the CM9 devs for the Note, somebody help me if possible. And if you feel that this is an isolated issue, do let me know otherwise. Because, when the basic UI shows severe clipping, the whole user experience is spoiled and nobody wants to live in fear with bright UI elements and bright wallpapers dreading the clipping if anything at all has to be dark. We paid a premium for this device and even Samsung seems to ignore. I have the SGS3 and there is no clipping on it but just that everything seems darker on the GS3 when compared to the Note. This alone shows that Gamma is a culprit here and I could just sell away my Note and just live with the GS3. But that doesn't help anybody who is facing this issue and wants to see a solution. Even I personally like the note more than the GS3 and I want to keep it but for this issue. Not everybody has the money to jump to the next flagship every now and then and for the people who spent their money on the Note doesn't have to "live with it" just because they decided to buy it without knowing such an issue existed. Not every store lets you try and trial their devices before buying them.
Samsung has even seemed to ignore the EMMC issue even after claiming they are "working on it" I dont see anything productive from Samsung's side as even a device which was previously unaffected had the affected kernels pushed to it via an update. So basically if it was not for people like Entropy who works day and night for that issue, Samsung could keep replacing motherboards for every random wipe a user does. They basically want to sell the note until the Note 2 and then this wouldn't be their problem anymore. Problems like the emmc bug is a MISTAKE from Samsung's part and they should be ready to repair devices even beyond warranty as the user may have only done the most harmless thing, i.e to reset the device to factory settings.
So, coming back to topic, how do we get in touch with the CM9 devs and enable gamma control on these ROMs? Most ROMS have gamma control under MDNIE settings which is greyed out, most probably because the kernel doesnt support it. This is the best I can do for the people who are affected by the clipping issue as I'm not a developer. This issue isnt an isolated case in my opinion and affects every Note I've got a chance to see.
It might help if you actually posted requests in the cm9 discussion thread? #commonsense
Seriously after reading TS long posts still*cannot figure out his problem
please post shots to show your issues
I have been using CM9 roms since build 2 and do not seem to notice such issues or maybe i am blind ?
mobile88 said:
Seriously after reading TS long posts still*cannot figure out his problem
please post shots to show your issues
I have been using CM9 roms since build 2 and do not seem to notice such issues or maybe i am blind ?
Click to expand...
Click to collapse
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Entropy512 said:
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Click to expand...
Click to collapse
Oops..I'm sorry for the long post. Its basically about the severe "black clipping" which has been affecting the Note since release. This issue is best seen when displaying dark shadows in images and videos. There were many threads discussing this issue. And GSMArena had published this issue in their news after I mailed them about the same.
What I wanted to tell was, I feel this is caused by the Note's screen having the gamma cranked up quite high and I believe lowering the gamma would resolve this issue.
The default CM9 theme shows severe clipping in backgrounds and UI elements. All the grey backgrounds, (the default theme) clip to black just below the status bar.
Even all the videos which have dark shadows are totally blocky due to this and the clipping makes them literally unwatchable.
I had reported this issue to GSMArena
http://www.gsmarena.com/samsung_galaxy_note_plagued_by_display_issues-news-4513.php
I wanted the Gamma Control feature which is presently disabled to be enabled in the CM9 kernels so that we can tune down the Gamma to eliminate this clipping
The same issues existed on the GNexus and was fixed with the Lean Kernel which had Gamma Tuning.
So once again, in short, I'm talking about the "Black clipping\crush" on the Note when displaying darker shades of colours.
All the notes have this problem, and we need to access to gamma control but as supercurio said it won't solve all the problems of the black clipping and banding issues
Sent from my GT-N7000 using xda premium
Satishp, i know what are you talking about. Just take a picture of your note and post it here. Of course, you won't use a screenshot feature but a camera.
I sold my note bc of the black clipping issue, but now I cannot buy an s3 or HoX cause their screens are just to small, that is, narrow. Gonna buy Note again and hope some solution will come out. It is too bad to buy a phone for its screen and get a crappy quality. Issue on s3 is solved with lowered gamma. Comparing with the Note, s3 has much darker screen. Sometimes too much.
Entropy512 said:
Yeah. OP is TL;DR complaining about some "severe" issue I've never seen and no one else has.
As to gamma control being disabled - I should remove that from the settings app, as that's something supported by the I9100/I777 display driver but not ours.
Click to expand...
Click to collapse
It's a very real issue affecting EVERY Note, derp
NotablyNice said:
It's a very real issue affecting EVERY Note, derp
Click to expand...
Click to collapse
http://www.gsmarena.com/samsung_galaxy_note_plagued_by_display_issues-news-4513.php
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Same. I don't often stare at my phone from a distance of 3cm to see any imperfections.
Sent from my GT-N7000 using xda premium
All of the speculation and misinformation of this issue is really starting to get frustrating. First, the issue IS with the hardware. It may be possible to reduce it's impact using software but the fact remains this is a hardware issue. How do I know? I have replaced my Note's screen and the newer screen I have isn't as good as the old one.
The new one isn't awful, it simply isn't as good as the other.
2nd point - everyone will have this issue. It is simply an inherent problem with the screen hardware and it is completely implausible that there are 1 or 2 'perfect' screens out there. There will simply be variations. Some people WILL have better screens than others. For some people the issue may be completely unnoticeable and for others it will be glaringly obvious. Don't judge or hate on people because their screen is worse than yours and vice versa.
3rd the issue is MORE noticeable at lower brightness values than high brightness values. If you have your note on higher brightness values then you're unlikely to notice it. In my case, I can not see any clipping if I am in a lit room. The only time I can see it is when I'm sat in the dark with very low brightness. As I said above this will vary from person to person.
I have attached 2 photos below. One is a normal exposure where you can see the clipping is hard to see. Another is a long exposure which amplifies the issue more and makes it more noticeable (I used a longer exposure on my camera to show this). Fortunately it isn't so bad for me, but for some people my long exposure image is the reality unfortunately.
Standard: http://i48.tinypic.com/4uxnia.jpg
Long Exposure: http://i48.tinypic.com/5akew3.jpg
Why have we got a clipping problem and can software solve it? I believe it is highly unlikely that this issue can be solvable. I also think the issue stems from one simple shortcoming to the screen; the minimum brightness achievable per pixel. The problem is the jump from this minimum brightness to the 'off' (perfectly black) pixel is too great. There is no transition. Can gamma control solve this? I'm not convinced. I think the issue is more to do with what the lowest pixel brightness the screen is capable of. For the poorer people this minimum brightness will be quite bright. For others the minimum brightness will be lower.
If any devs know of a way of controlling pixel brightness on a level where it can be noticeably changed and if it is possible to reduce this minimum brightness then sure, it would certainly be a possibility. But I don't think this is possible.
Part of this might be a limitation of the HD Pentile AMOLED technology. But if you notice, both the Galaxy Nexus and the Galaxy S3 share the same technology. For people who argue that the S3 uses a different manufacturing procedure, Samsung has no where mentioned this and its just an assumption.
The GNexus had the same issue but was solved with the LEAN kernel which implemented a gamma control within the kernel. If you've seen the S3's screen ( I own an S3 too, So I've spent a good time comparing), you will notice that the S3's screen is visibly darker than the Note's screen. Images tend to look darker and this shows that the S3's screen has its gamma set to a lower value which eliminates the clipping.
More proof for you, lets take the gammatest image and view it on our PC. Most PCs use an LCD display and still you can see the greys gradually fading to black.
Now increase the gamma of your display from your display adapter's color settings and view the same image again. You will see that you can see all the way upto 1 and then black just like how the image is displayed by the note.
http://forum.xda-developers.com/showthread.php?t=1800117
Now view a 720p or 1080p clip on your PC with the gamma values still high, you will see the clipping in every dark scene. Try it yourself.
This shows that gamma calibration can correct the issue to atleast some extent.
Hmm. There appears to be truth in what you say. Unfortunately the Note is lacking somewhat in the developer department. And the few devs there are have other pressing issues to deal with so the question becomes who can implement gamma control on the Note?
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Yup. Despite being pentile, compared to my I9100/I777 the screen is even more gorgeous.
I'm on minimum brightness nearly all the time. No clipping issues whatsoever.
MrDSL said:
Huh?
Everytime I turn my screen on I smile at how awesome it is..Hell it seems even better now that I have been using cm10 but i think thats just because its brightness seems to be overall set higher.
Click to expand...
Click to collapse
Yup, and it's even better when you switch the screen mode to "Dynamic" (Advanced Settings).
Sent from my GT-N7000 using xda premium
I have the clipping regardless of which mode I put it in, apart from the clipping the screen is mint, which makes me even more pissed off when I watch a movie and a dark scene comes on, then the shade between black and grey turns into a lego block mess. I really cant beleive so many people are happy with it, half of u guys must be blind, I exchanged my Note twice, tested my cousins and my bosses Notes, all have the exact same problem. I even bluetoothed the gamma test image to a few in carphone warehouse , same with them, even the samsung rep I spoke to over the phone said the one they have in the office also has the issue. Total crap imo, Samsung total FAIL.
Entropy512 said:
Yup. Despite being pentile, compared to my I9100/I777 the screen is even more gorgeous.
I'm on minimum brightness nearly all the time. No clipping issues whatsoever.
Click to expand...
Click to collapse
Actually use your Note and go watch a dark movie... It's there
NotablyNice said:
Actually use your Note and go watch a dark movie... It's there
Click to expand...
Click to collapse
I've watched plenty of dark movies... As good as if not better than my I9100/I777.
Entropy512 said:
I've watched plenty of dark movies... As good as if not better than my I9100/I777.
Click to expand...
Click to collapse
Please take a picture if your note displaying the gamma test image (blocks numbered 1 to 20) with stock gallery app in a dark room, screen mode dynamic, max brightnes with auto adjust switched off, I bet number 4 is light grey, then number 3 is black, if so your device has black clipping. There should be no abrupt drop from grey to black, it should be a gentle fade.
Thanks.
So I saw this in the build prop
"qualcomm sensors enable
#
# LGE CHANGE_S, 2013-10-29, [email protected]
# below sensor is default true by HAL source.
#ro.qualcomm.sensors.qmd=true
#ro.qc.sdk.sensors.gestures=true
#ro.qualcomm.sensors.pedometer=true
#ro.qc.sensors.step_detector=true
#ro.qc.sensors.step_counter=true
#ro.qualcomm.sensors.pam=true
#ro.qualcomm.sensors.scrn_ortn=true
#ro.qualcomm.sensors.smd=true
#ro.qualcomm.sensors.game_rv=true
#ro.qualcomm.sensors.georv=true
# LGE CHANGE_E, 2013-10-29, [email protected]"
Not sure if anything there can help, but I know that the sharpening is applied when there's something light on a dark background or vice versa and also if you have any type of floating menu it'll sharpen everything in the background.
Samsung does this as well but as far as I know only in multi window mode.
Its not a screen issue as its not always apparent. And as far as I know the oppo find 7 has the same panel and doesn't exhibit these effects.
So anyone have any ideas?
Kernel related ?
Display drivers?
Maybe we should all email lg and ask them for an option to remove it.
Just fyi oppo use japan display inc panel while lg use their own panel
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
daleski75 said:
I think the only way to defeat the sharpening is with a custom kernel and possibly an app to tweak the display unless LG of course turn this 'feature' off in the future themselves via an OTA update.
Click to expand...
Click to collapse
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Lostatsea23 said:
Hope they do. Its pointless.
So anyways I came across another thing.
If you tune the display with a kernel app as in colors. If you tune all the colors down and make the colors darker and such, everything will have the sharpening applied. So it seems like the software sees that and applies it to everything.
Hoping it's just kernel
Click to expand...
Click to collapse
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
daleski75 said:
I am just guessing as I am not a developer by any shape of the imagination but this sounds like it's built into the OS so possibly a tweak to prevent this behaviour from getting triggered which will turn off the sharpening effect.
Click to expand...
Click to collapse
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Lostatsea23 said:
Yes I think so. If someone can baksmali the ROM maybe they can find something. Id get in touch with a Dev but as this time it seems like no one owns the device.
Click to expand...
Click to collapse
When it finally rolls out to the USA then I think it will get better dev support.
I'll have the device soon, but I'm not sure we're able to turn it off since it may be the part of the driver. Haven't done it yet, but if we can debug the running code and binary patch the trigger effect into not signaling, we may fix it. If it IS a trigger at all; e.g. we should find when it does signal the driver/gpu to apply sharpening and just switch code from JE to JNE or similar to kill the trigger and never apply it.
Theoretically.
Hopefully LG can turn it off and not a hardware combo issue with the 801 and this particular display tech.
It can be turned off. They purposely added it
Lostatsea23 said:
It can be turned off. They purposely added it
Click to expand...
Click to collapse
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Lostatsea23 said:
The purpose is either, they want to emphasize the need for it so they make things extra sharp over 1080p not realizing it actually looks worse when its sharpened. Or its because the contrast ratio is low so to do that they sharpened it in areas where it would be more noticeable to make it more legible. Again, doesn't really help.
On the galaxy phones it would produce this on multi window mode as stated and when putting a cm ROM on it you wouldn't get any of that since there's no window mode. But... If you go into screen settings and change the screen aliasing type or whatever, if you change from standard to reading mode it would make the display sharp exactly like we see on this one. So once we get kernel support for screen modes (cm adds modes such as movie mode and sharpness ect) then we should be fine.
Click to expand...
Click to collapse
Well, I don't believe a whole bunch of smart engineers, designers and such in dev and QA would not notice it sucks...
And for screen modes, after so much hassle, I hope and expect LG is preparing us a "turn bloody thing off" setting...
Well once it comes out in the states I will be contacting some devs about it. We need a boot loader unlock as well though
toncij said:
I wonder if anyone knows the purpose. Because any sane person would turn it off after seeing it in action.
Click to expand...
Click to collapse
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
flaring afro said:
Without seeing it in person, it probably was added to make their simple UI have more of a pop to it. They were probably trying to make it stand out more in stores, like how tvs usually have horrible settings when on display at a store.
Click to expand...
Click to collapse
They're dumb because it makes it look worse. In almost positive a fix will be found. If anything maybe the carrier releases will have this fixed already.
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
haris182 said:
Guess what...
I installed bravia engine v3 from Android Tweaker 2 and...
I think my display is more clear and the sharpening is slightly gone!
You guys better try it and tell your impression
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Nope. Exactly the same. Placebo
Sugar pills taste so good
rushless said:
Sugar pills taste so good
Click to expand...
Click to collapse
Lol. If an update to remove this isn't out in the next couple weeks. Bye bye G3
Hello fellow Pixel users!
Just wanted to take a minute and start a small discussion with you about stuff that only works with root. Maybe you feel the same.
As an Android user from day 1, I always enjoyed the general "openness" of Android compared to other mobile OSs and used to frequently try out new custom ROMs, play with all the system UI tuner options and obviously got used to having a decent adblocker.
But ever since I got a Pixel XL, I was honestly surprised by the relatively small amount of ROMs and general lack of development on XDA regarding the Pixel phones. At least compared to previous phones I owned, with the exception of the Blackberry Classic maybe...
(Obviously I don't want to discredit the folks that ARE working on these devices. You're awesome and your work is very appreciated!)
Right now, I only use root for AdAway, Nova Launcher (for turning off the screen and locking it with a double tap) and Ex Kernel Manager (even though I never used it or changed any of the settings).
So what I really want to talk about is, what do you use root for? Or why did you unlock your bootloader? Is there something I'm missing?
TL,DR: Did you root your phone or unlock the bootloader? Why?
Yes and yes.
I will always run an unlocked bootloader. It's a security safety net. If my phone bricks, I have the option to flash factory images. I can always return to stock if something goes wrong.
Root, yes, of course. Because Android.
Pain-N-Panic said:
If my phone bricks, I have the option to flash factory images. I can always return to stock if something goes wrong.
Click to expand...
Click to collapse
Those are great points! You're absolutely right!
But what about apps or system tweaks? You said "Because Android" but how is your experience different from someone who didn't root?
paco8 said:
Those are great points! You're absolutely right!
But what about apps or system tweaks? You said "Because Android" but how is your experience different from someone who didn't root?
Click to expand...
Click to collapse
Root privileged apps- adaway, titanium backup, modded YouTube, modded Spotify, SD Maid, Substratum and a few others.
Also, custom kernel with customized color profile for a more vibrant display.
I also enjoy themeing my own device so having root is necessary for me.
I also need to root, well, BECAUSE ANDROID
Pain-N-Panic said:
Root privileged apps- adaway, titanium backup, modded YouTube, modded Spotify, SD Maid, Substratum and a few others.
Also, custom kernel with customized color profile for a more vibrant display.
I also enjoy themeing my own device so having root is necessary for me.
I also need to root, well, BECAUSE ANDROID
Click to expand...
Click to collapse
U don't need root for substratum on my 8.1 and use Andromeda add on for rootless substratum
I feel like going back to nougat and root for Xposed though...
Thanks for the suggestions!
If you ask me:
Not a fan of TB (restoring often causes problems)
or SD Maid (some cache is important and shouldn't be deleted - except for uninstalled apps),
Substratum is way too buggy for me (at least I can't seem to find a theme without bugs)
and I probably shouldn't ask about those modded apps on here, even though they sound interesting. I guess I'll have to Google that. :laugh:
After looking through Ex Kernel Manager, I can't seem to find anything that I'd want to use or fiddle with. The phone is fast enough, so no overclock. The colors are fine, so no tuning needed. And all the other stuff looks dangerous...
Where are all the awesome system UI options though? I'd love to have my clock in the center of the status bar and display battery percentage INSTEAD of the icon. I know that those are usually coded into custom ROMs but there are no 8.1 ROMs...
Oh, how I'd love to see an 8.1 DU ROM working flawlessly...
Edit: Why go back to Nougat and why use Xposed? I don't get what the big deal is about Xposed nowadays. I used it a few years ago but only because of one or two add-ons, if I recall that correctly.
I have center clock on 8.1 using a Substratum theme.
Also, you can choose to select battery percentage next to the battery icon in 8.1 battery settings.
Once source code gets released for 8.1, the SystemUI can be deodexed which will allow for 3minit battery mod to work. I believe 3minit requires root.
Reasons are getting thin aren't they. AdAway, TB, and Tasker (HBM and single tap sleep(without device admin permission thus required pin)). TB makes life easier but not a necessity. Different device wouldn't need HBM most likely. So basically it comes down to AdAway which I'm pretty sure I'd go nuts without.
TB, Tasker, lucky patcher, greenify, acr (automatic call recorder), ad away. And generally being able to mess with things.
ThePublisher said:
TB, Tasker, lucky patcher, greenify, acr (automatic call recorder), ad away. And generally being able to mess with things.
Click to expand...
Click to collapse
"Generally being able to mess with things" is the most accurate response this question for those who love Android at its core.
Pain-N-Panic said:
"Generally being able to mess with things" is the most accurate response this question for those who love Android at its core.
Click to expand...
Click to collapse
That's the technical term for it at least.
I'm down to one reason and I found out about it a few months back actually. Without it I probably wouldn't bother.
Assertive display - visibility outdoors in the freaking sun with sunglasses on? Heck yeah! The most annoying part is that it just takes two lines added to the build.prop file. If I could do this without root I sure as hell would.
Adaway
Thanks for all your answers!
This basically proves my point though in my opinion. Having a rooted Android device used to be such an open playground for fun stuff and now it's mostly just about adblockers and minor tweaks apart from a few apps that still take advantage of it like Tasker and TB.
At least the phones nowadays are fast as hell and have insane cameras. I just wish it would be more sci-fi-y if you know what I mean. Phones aren't just gadgets anymore, they're expensive pieces of hardware that seem to improve upon basic things that we could do for years.
Android updates used to have lots of cool new features with every new version number that was released and now they just seem to improve upon what they can already do and sometimes take features away or even lock them to specific phones (looking at the guy who thought it was a great idea to make stuff like "motion pictures" a feature only on Pixel 2 devices even though our device had the feature available for a day).
Guess I'll take this opportunity to spend less time messing around with tons of options and just be thankful for what they can do now. Like playing stupid gambling-like games with ps1-graphics on a device with a quad-core and 4GB of RAM. :laugh:
Am I the only one who gets turned off by games that have reviewers saying "addictive" and "great time-killer"? This thing could play GTA 4 and tons of people rather spend a hundred bucks on candy crush...
Whatever, it's all good. I guess I just have different expectations.
paco8 said:
Thanks for all your answers!
This basically proves my point though in my opinion. Having a rooted Android device used to be such an open playground for fun stuff and now it's mostly just about adblockers and minor tweaks apart from a few apps that still take advantage of it like Tasker and TB.
At least the phones nowadays are fast as hell and have insane cameras. I just wish it would be more sci-fi-y if you know what I mean. Phones aren't just gadgets anymore, they're expensive pieces of hardware that seem to improve upon basic things that we could do for years.
Android updates used to have lots of cool new features with every new version number that was released and now they just seem to improve upon what they can already do and sometimes take features away or even lock them to specific phones (looking at the guy who thought it was a great idea to make stuff like "motion pictures" a feature only on Pixel 2 devices even though our device had the feature available for a day).
Guess I'll take this opportunity to spend less time messing around with tons of options and just be thankful for what they can do now. Like playing stupid gambling-like games with ps1-graphics on a device with a quad-core and 4GB of RAM. :laugh:
Am I the only one who gets turned off by games that have reviewers saying "addictive" and "great time-killer"? This thing could play GTA 4 and tons of people rather spend a hundred bucks on candy crush...
Whatever, it's all good. I guess I just have different expectations.
Click to expand...
Click to collapse
You are right! I was also using root just for the 3 reasons you specified! Adaway is the biggest reason. There are other solutions, but nothing that reliable. And next biggest is Ex Kernel Manager to set up double tap to wake without lockscreen.
As for the motion photos, you still can get it. You need to download that version of Google Camera APK and disable updates. I am using it and it looks good. But it works only in Google Photos App. So not that useful as well!
DaSmith87 said:
I'm down to one reason and I found out about it a few months back actually. Without it I probably wouldn't bother.
Assertive display - visibility outdoors in the freaking sun with sunglasses on? Heck yeah! The most annoying part is that it just takes two lines added to the build.prop file. If I could do this without root I sure as hell would.
Click to expand...
Click to collapse
My quick reasons for bootloader unlocking and rooting mirror many of the others here:
1) Ability to flash factory images in a recovery situation.
2) Titanium Backup - although I haven't had to actually use this to recover anything other than a specific app or 2 in the past few years.
3) Adaway
4) Ability to modify build.prop to leverage native hotspot/tethering (Verizon GUDP)
I am interested in learning more about Assertive Display and the differences between it and Adaptive Brightness. My understanding is that Assertive Display works separately from Adaptive Brightness and actually adjusts the tone/color/contrast of individual display pixels to optimize viewing in bright sunlight. Theoretically, this allows you to turn down screen brightness to achieve better viewing/contrast in bright conditions. Can you provide the link to directions you used to enable Assertive Display? Also - does it play well with Adaptive Brightness - or do you need to manually tweak screen brightness to account for Assertive Display?
Thanks!
sb1893 said:
My quick reasons for bootloader unlocking and rooting mirror many of the others here:
1) Ability to flash factory images in a recovery situation.
2) Titanium Backup - although I haven't had to actually use this to recover anything other than a specific app or 2 in the past few years.
3) Adaway
4) Ability to modify build.prop to leverage native hotspot/tethering (Verizon GUDP)
I am interested in learning more about Assertive Display and the differences between it and Adaptive Brightness. My understanding is that Assertive Display works separately from Adaptive Brightness and actually adjusts the tone/color/contrast of individual display pixels to optimize viewing in bright sunlight. Theoretically, this allows you to turn down screen brightness to achieve better viewing/contrast in bright conditions. Can you provide the link to directions you used to enable Assertive Display? Also - does it play well with Adaptive Brightness - or do you need to manually tweak screen brightness to account for Assertive Display?
Thanks!
Click to expand...
Click to collapse
When I first enabled this I left my brightness at the same 50% level with the auto brightness left on. It works really well in conjunction with the normal brightness level settings. Maybe turning the brightness down could yeild better battery results but I was never one to complain by the Pixel XL's battery life.
This video from Android Authority here explains it well. I actually randomly got to the video at around midnight on YouTube a few months back. Phone wasn't rooted so I did root it in the middle of the night and followed this topic from the XDA forums to change the build.prop file. Applied the changes, rebooted phone and... Realized I have no real way to test it. Went to my kitchen's aspirator and switched the lights on, brought the phone under there super close at a very steep angle and I could still see it perfectly fine.
TL;DR - this is a great addition to the already standard brightness levels, works like magic, and hey, you can always revert if you end up not liking it.
DaSmith87 said:
When I first enabled this I left my brightness at the same 50% level with the auto brightness left on. It works really well in conjunction with the normal brightness level settings. Maybe turning the brightness down could yeild better battery results but I was never one to complain by the Pixel XL's battery life.
This video from Android Authority here explains it well. I actually randomly got to the video at around midnight on YouTube a few months back. Phone wasn't rooted so I did root it in the middle of the night and followed this topic from the XDA forums to change the build.prop file. Applied the changes, rebooted phone and... Realized I have no real way to test it. Went to my kitchen's aspirator and switched the lights on, brought the phone under there super close at a very steep angle and I could still see it perfectly fine.
TL;DR - this is a great addition to the already standard brightness levels, works like magic, and hey, you can always revert if you end up not liking it.
Click to expand...
Click to collapse
Thanks so much for the detail. I'm going to give it a whirl right now!
sb1893 said:
Thanks so much for the detail. I'm going to give it a whirl right now!
Click to expand...
Click to collapse
You're welcome! One thing I forgot to mention - don't bother with the flashable ZIP. It's more work than editing the build.prop file and it actually doesn't work on 8 and up. 7.1.2 was OK with it but I noticed it wasn't quite right on 8 when I tried to flash it even though it said it flashed with no errors.
sacthegreat said:
You are right! I was also using root just for the 3 reasons you specified! Adaway is the biggest reason. There are other solutions, but nothing that reliable. And next biggest is Ex Kernel Manager to set up double tap to wake without lockscreen.
As for the motion photos, you still can get it. You need to download that version of Google Camera APK and disable updates. I am using it and it looks good. But it works only in Google Photos App. So not that useful as well!
Click to expand...
Click to collapse
Thanks! I actually did disable auto update once I had it and still have the APK. Don't know if it works after a fresh install of 8.1 though. I guess I'll try later. Google's Motion Stills as an alternative just feels weird to me.
I think it's a neat feature though. Sometimes it really helps bring a moment back to life, more than a still picture would. Especially when it's snowing or raining.
That new AR stickers thing is also funny but it needs better content IMO. Two of the packs are basically ads for the StarWars movies and Stranger Things.