Hi!
Our hammerhead currently lacks full support for ambient display in Android L. One+1 has the kernel changes we need already merged(https://github.com/CyanogenMod/andr...mmit/735f665d2f5dd350b92cffae26517ed494760b5f). I checked this patch before - it's not a match to our source, it needs some more merges in video drivers. I was just wondering if anyone on XDA tried to get this working and wanted to share progress and experiences with doze mode on 3.4 msm kernel?
Mike
mikegapinski said:
Hi!
Our hammerhead currently lacks full support for ambient display in Android L. One+1 has the kernel changes we need already merged(https://github.com/CyanogenMod/andr...mmit/735f665d2f5dd350b92cffae26517ed494760b5f). I checked this patch before - it's not a match to our source, it needs some more merges in video drivers. I was just wondering if anyone on XDA tried to get this working and wanted to share progress and experiences with doze mode on 3.4 msm kernel?
Mike
Click to expand...
Click to collapse
but does our panel really supports that mode?, i remember people thinkering with the digitizer to get the double tap to wake like on the g2 (Without bat drain) and they got nowhere
The panel itself works fine, we are missing one feature only - enabling ambient display afer device is picked up, it needs to be ported to our kernel and sensors hal I guess.
We have a IPS LCD display, using Ambient display will suck a lot of battery juice :/
DJBhardwaj said:
We have a IPS LCD display, using Ambient display will suck a lot of battery juice :/
Click to expand...
Click to collapse
IPS doesn't mean its gonna suck battery. Nokia did it on IPS before.
http://allaboutwindowsphone.com/features/item/18191_Nokia_works_a_LCD_miracle-Glan.php
The topic to be discussed here anyway isn't the screen type or its flaws. It is to get sensors to be able to wake the device with ambient display enabled.
akash3656 said:
IPS doesn't mean its gonna suck battery. Nokia did it on IPS before.
http://allaboutwindowsphone.com/features/item/18191_Nokia_works_a_LCD_miracle-Glan.php
The topic to be discussed here anyway isn't the screen type or its flaws. It is to get sensors to be able to wake the device with ambient display enabled.
Click to expand...
Click to collapse
Everyone's got their choice. I had my opinion laid.
how about applying the patch to cm kernel instead of stock, since it uses updated video drivers and such? is a no-go still?
opssemnik said:
how about applying the patch to cm kernel instead of stock, since it uses updated video drivers and such? is a no-go still?
Click to expand...
Click to collapse
It's included in CM12-CAF build, however we still don't have support for waking the screen after the device is picked up.
mikegapinski said:
It's included in CM12-CAF build, however we still don't have support for waking the screen after the device is picked up.
Click to expand...
Click to collapse
If I recall we had the option on some custom roms (4.4.4) to wake the screen when the device was picked up. I think it used the proximity sensor to detect when the device was picked up.
edit- I apologize, I just realized that this was for developers only.
@mikegapinski Any progress on this or is it abandoned? I'm really looking forward to using full ambient display on hammerhead if it's even possible.
Thanks!
You'd need over 750 patches in the graphics subsystem of the kernel before you can start applying relevant doze patches. Plus updated gpu kernel drivers etc etc
We'll have this on an additional nightly CM12 build eventually and it works pretty good. The only drawbacks at the moment are the situation where sometimes the pick-up sensor is triggered and enables the short wake-up effect; this is because we use a sensor blob from bacon. Then, in order to have a reliable pick-up, that always works, I abused the tilt sensor with some fixed parameters, which is wakeup capable. This however leads to a tad too long timespan from actual pick-up to showing the message on the display.
Whatever, take it or leave it.
myfluxi said:
You'd need over 750 patches in the graphics subsystem of the kernel before you can start applying relevant doze patches. Plus updated gpu kernel drivers etc etc
We'll have this on an additional nightly CM12 build eventually and it works pretty good. The only drawbacks at the moment are the situation where sometimes the pick-up sensor is triggered and enables the short wake-up effect; this is because we use a sensor blob from bacon. Then, in order to have a reliable pick-up, that always works, I abused the tilt sensor with some fixed parameters, which is wakeup capable. This however leads to a tad too long timespan from actual pick-up to showing the message on the display.
Whatever, take it or leave it.
Click to expand...
Click to collapse
Is this available fully implemented in any build?
Sent from my Nexus 5 using Tapatalk
akash3656 said:
IPS doesn't mean its gonna suck battery. Nokia did it on IPS before.
http://allaboutwindowsphone.com/features/item/18191_Nokia_works_a_LCD_miracle-Glan.php
The topic to be discussed here anyway isn't the screen type or its flaws. It is to get sensors to be able to wake the device with ambient display enabled.
Click to expand...
Click to collapse
Sorry for reviving this thread, but it IS about the display type. Not the AMOLED vs. LCD part, but if the display module actually incorporates Display Memory - which is a key in low-power Ambient Display options.
What Nokia/MS did is basically using DM with a simple script that moves the content around. It is low power, and as the phone does not need to be awake, power drainage is lowered even further.
Updates are ran by a background service that collects relevant notifications (the 6 lock screen notifications, the big lock screen info + current date/time), and on the exact minute, updates the DM. It results in a less than 1000ms wakelock, and does not keep the device awake.
I highly doubt that many Android phones would come with Display Memory enabled displays - it is simply not worth it financially, and would be mainly useless. So we cannot really reach the whole Nokia-level low power usage, though we can try.
MemoryController said:
Is this available fully implemented in any build?
Click to expand...
Click to collapse
CM 12.x hammerheadcaf
Related
Hey guys. I have looked around and can find no info on some of the tabs sensors. From what i understand the chipset is straight out of the galaxy s phones, which is the reason i see the existence of a proximity sensor but dont see any data from it.
Anyone have a clue whether it actually exists?
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
triplex76 said:
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
Click to expand...
Click to collapse
Doesn't need and doesn't have are different things. Point is, if it was stated that the tab has a proximity sensor, where is it?
I'm pretty sure it has one, in the unofficial CM build Technomancer says he fakes i at 10CM
There is no proximity sensor in Galaxy Tab.
My CM7 sensors driver pretends there is one and reports 10CM distance so the Phone app behaves better.
Thanks mate, that's what you said in the last thread back in October, but why do all the sensor pingers see it? Are they checking code rather than hardware?
Also, is there a working, sensitive light meter anywhere for the tabs ambient light sensor? The couple I've tried refuse to work...
There is working light sensor in the Tab. Both my CM7 and Samsung ROMs support it just fine. It has range from 0 to 6000 Lux snapped to one of several levels in the kernel driver. You can actually read it from sys interface.
The proximity sensor in my CM7 sensors driver is just software reporting constant 10cm to the system. The sensors test apps in my CM7 (I uses Sensor Test and Plot http://www.appbrain.com/app/sensor-test-and-plot/com.golborne.android.SensorTest) just reports 10cm from my fake sensor.
I think there is some leftover code in Samsungs sensors driver that may report presence of proximity sensor.
Yep, i use it as well, but my issue is with the three avaliable states the driver seems to report.
I get 5, 22 and 75. Are there only three levels then? And no way to modify them outside the kernel?
I can get up to 6000lux using strong LED flashlight directly on the sensor.
There is another sys device that can read unprocessed data that has values not snapped to 5,22,75 etc... but Samsung's driver uses the snapped device (and so is mine).
This is very annoying... im trying to make an app that needs a proximity sensor to work as intended so the light sensor as well as the sleep mode implementation are really no substitute.
In any case, im sure it will be quite usefull for all tablet owners running 2.2 and up and using a case. I will have a closed beta for xda members by the end of the day, so people can test it over the weekend.
Would you like a shot, mancer?
I don't know what would you do but if I understand why not to use the g-sensor ... just like in samsung omnia...put backwards enable silent courtesy mode.
the proximity sensor will be useful if you use the leather case to close the screen when touches the screen , like ipad 2 and galaxy tab 10.1 V they have proximity sensors , but i noticed that the sensor exists using sensor applications they see it exists but not giving readings
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
ftgg99 said:
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
Click to expand...
Click to collapse
Thanks I already bought it from market and it's great
Sent from my GT-P1000 using XDA App
Great! Im working on an update that will help improve the accuracy of the light sensor functions... been getting some flack for not updating it
Watch this space!
Will the nexus 6 have wave-to-wake feature like the Moto X 2014?
If not by default then is it possible that it can have this feature in future by any means??
No, it does not have it by default.
There are apps that can use the proximity sensor with older phones to wake it up, so I imagine that at some point, yes, it will be possible to replicate the Moto X wave-to-wake feature via app.
jt3 said:
No, it does not have it by default.
There are apps that can use the proximity sensor with older phones to wake it up, so I imagine that at some point, yes, it will be possible to replicate the Moto X wave-to-wake feature via app.
Click to expand...
Click to collapse
Ok.. I hope it does happen...
I use this this feature frequently on my Moto X 2014. I will definitely miss it if I get a N6.
Here's the app I use on my Nexus 5. Assuming there aren't any issues running it under Lollipop, it has a setting that wake the phone with a wave. However, I'm not sure whether it will FULLY wake the phone, or let you just activate Ambient Screen. Maybe contacting the dev, and requesting an Ambient Screen setting would help.
Gravity Screen - On/Off
It wont by default - it is a moto specific software feature.
Begging or hoping it is added will do nothing, as the nexus is from google OS wise, and moto hasn't added that specific software (or hardware, see below) to it like the moto X.
Your best hope is 3rd party app that can give that capability, however that said, the phone would have to have the IR sensors like the X in order to detect the handwaving, which AFAIK it doesn't have.
Is this the same feature found in the note 2?
RW-1 said:
...the phone would have to have the IR sensors like the X in order to detect the handwaving, which AFAIK it doesn't have.
Click to expand...
Click to collapse
All modern smart phones have proximity sensors though, and third-party developers have tapped into those. The trick isn't the detection, it's the activation of Ambient Screen without fully waking the phone.
For instance, the Gravity Screen app I posted earlier will wake my N5 with a wave over the screen just perfectly, but it FULLY wakes the device. If they can alter that to give the option of waking the device, or only activating Ambient Screen, then it would almost perfectly emulate the Moto function.
And yes I did make the title CAPS, because I am a bit cross they thought this would be a good idea.
Personally I don't think our screens need this feature....
It seems the nexus 6 has this 'automatic contrast brightness' feature built in.
Really, i cant think why.
I am really enjoying the phone, but for me the brightness just is not up to scratch (unfortunately) but hey hoo.
Anyway, i noticed this happening to mine. Start chrome for example, for a split second the screen is bright then it dims down.
I would say this is software setting, but it seems there is no access to it, can it be fixed by kernel setting or some other rom mod?
Cheers
MJ-12
Do you have Adaptive brightness turned on in the Display settings?
are you noticing this at full brightness?
stevemw said:
Do you have Adaptive brightness turned on in the Display settings?
Click to expand...
Click to collapse
Hi, yes it is off as is ambient display...
As stated in the OP, this is built in on the Nexus 6 as it is with the LG2 also i think.
It would be great if we where able to disable it, but from what I have read about Content-based Dynamic Contrast it might be kernel related or something within the rom...
Does anyone have any info on this CDC feature?
Cheers
MJ-12
There is no such thing. Do you have any reliable reference that it's a feature of the N6? I can only find one article from "PC Pro UK" whatever that website is.
What does happen like it happens with most if not all OLED (and Plasma btw) is that the screen has a max overall brightness it can achieve. If you have a small white square it will be able to get brighter than if you had the whole screen white.
In practice I don't notice it though, with the phone turned to max brightness and then opening a mostly white empty Chrome page.
Are you running stock? I don't have this type of issue unless I have adaptive brightness on.
When I first customized my OP5 settings under OOS 4.5.0 (before the last two OTAs) there was a "Proximity Wake" toggle under "Settings->Display-Ambient display". The feature allowed you to wave your hand near the OP5 and the display lit up briefly so you could see the lock screen. See "How to Enable Proximity Wake" and the accompanying YouTube demo.
Since the first and second OTA that option has been replaced with an "Lift up display" toggle. I'd much rather the proximity Wake feature or better yet, both.
Does anyone know why that feature was replaced? Did it not work reliably?
It's possible it was using too much battery power.
In an effort to save battery the setting was lost on the wayside...
ultramag69 said:
It's possible it was using too much battery power.
Click to expand...
Click to collapse
+1
ultramag69 said:
It's possible it was using too much battery power.
In an effort to save battery the setting was lost on the wayside...
Click to expand...
Click to collapse
A reasonable assertion but maybe they should've let the functionality be limited to "while on charger" like other battery sucking features. Thanks for your input.
All the Moto phones have this including the the Moto Z play and it has the longest battery life of just about any phone. This a a great feature and one of the reasons I bought a OP5 . Can't believe they just got rid of it.
Maybe if enough people complain it will be put back in by another Ota. One plus do seem to at least listen to the Dev community. ..
3DSammy said:
A reasonable assertion but maybe they should've let the functionality be limited to "while on charger" like other battery sucking features. Thanks for your input.
Click to expand...
Click to collapse
Yeah this was a great feature I had on my Nokia 1020, if it was causing battery drain on the OP5 then put an alert when you toggle it that it will have a direct impact on the battery life. Crisis averted then.
Ambient display in general is sort of weird on this phone. It doesn't exactly do what I thought it would. Maybe the removal of this feature is one of the reasons. But with the notification light so dim (maybe this can be altered with a mod or future ROM, I hope), the live display aspect is sort of needed. Is there a post on the OP forums on this yet? Someone should make one.
This is something I really miss from my old Moto
If you are rooted, there is a workaround to have proximity wake enabled. Instructions are provided in this thread: https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-enable-ambient-display-t3690488/page4
AOD is a useless battery drain in comparison to ambient display
I wish they would switch to ambient..
Is there a way to get ambient on stock rom without root?
Doubt it.. maybe you can mimickor do it using tasker?
Have a look here...
AOD is not inherently bad for battery life, not if it is done properly and is on AMOLED.
Any black you see is not causing power to drain and if you haven't done anything silly with AOD wallpapers or anything like that then the battery life that the clock, date and notifications takes up is minimal anyway - an ambient display could actually end up being a bigger drain (again depending on how it is actually set up) as it requires the phone to process something every so often as well as lighting up some of the screen.
I think it would be nice to have both options to choose from, ambient or AOD
Lennyuk said:
AOD is not inherently bad for battery life, not if it is done properly and is on AMOLED.
Any black you see is not causing power to drain and if you haven't done anything silly with AOD wallpapers or anything like that then the battery life that the clock, date and notifications takes up is minimal anyway - an ambient display could actually end up being a bigger drain (again depending on how it is actually set up) as it requires the phone to process something every so often as well as lighting up some of the screen.
Click to expand...
Click to collapse
I second this as correct and will add that it also has been proven that the displayed images shift pixels as not to cause screen burn
winol said:
I think it would be nice to have both options to choose from, ambient or AOD
Click to expand...
Click to collapse
more options are always better but i had a OP5T for a few days and they only thing i truly miss on note 8 is that ambient display and fast and well placed fingerprint scanner on OP5T
ho and its face unlock is also blazingly fast
bloodomen2 said:
more options are always better but i had a OP5T for a few days and they only thing i truly miss on note 8 is that ambient display and fast and well placed fingerprint scanner on OP5T
ho and its face unlock is also blazingly fast
Click to expand...
Click to collapse
Totally agree and also the software significantly faster and less laggy on the 5T...
mikey_sk said:
Totally agree and also the software significantly faster and less laggy on the 5T...
Click to expand...
Click to collapse
i stayed with note8 only cus i love the camera and all its features more but OP5T was insanely fast and smooth also battery life were better
i hope Oreo update for note 8 speed things up and improve the battery
i didnt stay with modified clean android because its a bit boring and you need many apps to make up for all the missing samsung quirks and features
but main reason i didnt stay with the OP5T was that it didn't work as well as my note 8 when using the gear s3 and a helmet bt headset together
on note i have them both connected as phone and can switch the audio easily when calling
OP5T got the audio switching option in oreo update but he cant take 2 devices as phone and switch between them when calling