Ambient display drivers for Zuk z1 - Zuk Z1 Android Development

Hi everyone.
Recently i`ve been searching on how to enable ambient display on our phones.
i`ve found a commit which might help us to achieve thishttps://github.com/CyanogenMod/android_kernel_oneplus_msm8974/commit/735f665d2f5dd350b92cffae26517ed494760b5f
 @acuicultor & @OrdenKrieger please take a look.
I`ve been trying to port this on my own but currently i`m hindered by lack of time due to exams.
Although i`ll definately look into it next month.
Kernel devs plz take a look.

By the way there is a crdroid rom in which ambient display is working fine but it stops device from sleep

wiikii said:
By the way there is a crdroid rom in which ambient display is working fine but it stops device from sleep
Click to expand...
Click to collapse
Yep that's true. I guess it was a build by @bigbing

Related

Cyanogen 5.1 ROM confirmed!

It is great to hear that CM is coming to OPPO R7 Plus!
Current state is:
- RIL (telephony, SMS, mobile data) is working
- BT, GPS is working - camera is working
- sensors are working
- Wifi is semi-working
- audio is broken (no speaker, no headphones)
Great - will test definitely once wifi n audio is fixed
Is it official CM? Or unofficial?
This is fantastic. I have the Oppo r7 plusm. Are there plans for all three variants? How soon would this be released?
I am willing to do test builds on my oppp r7 plusm. PM me if you need any beta testers.
News about it?
I too would be interested in this. Just looked on Cyanogenmod website and there is no official roms. Suppose they will come with time.
Jaimeoss said:
Is it official CM? Or unofficial?
Click to expand...
Click to collapse
Its Official.
http://www.cyanogenmod.org/blog/expanding-the-cm-device-family
Looking forward to this
As a quick update:
- Audio is working now, there's only minor crackling noise when playing notification sounds in deep sleep
- Wifi is working, it's a bit unstable though (sporadically loses connection)
- fingerprint sensor is working
Only blocker for official nightlies that I can see is that we need to fix the SELinux policies.
maniac103 said:
As a quick update:
- Audio is working now, there's only minor crackling noise when playing notification sounds in deep sleep
- Wifi is working, it's a bit unstable though (sporadically loses connection)
- fingerprint sensor is working
Only blocker for official nightlies that I can see is that we need to fix the SELinux policies.
Click to expand...
Click to collapse
That`s fantastic news, you are making nice progress there! And we all happily waiting for CM to be released! BIG thank you to you and to other people working on this!!! :good:
maniac103 said:
As a quick update:
- Audio is working now, there's only minor crackling noise when playing notification sounds in deep sleep
- Wifi is working, it's a bit unstable though (sporadically loses connection)
- fingerprint sensor is working
Only blocker for official nightlies that I can see is that we need to fix the SELinux policies.
Click to expand...
Click to collapse
AWESOME!
I cross my fingers to be able to test it this week!! Tired of Color OS, hurry up guys!! Yay!!
maniac103 said:
As a quick update:
- Audio is working now, there's only minor crackling noise when playing notification sounds in deep sleep
- Wifi is working, it's a bit unstable though (sporadically loses connection)
- fingerprint sensor is working
Only blocker for official nightlies that I can see is that we need to fix the SELinux policies.
Click to expand...
Click to collapse
Dear Maniac,
Thanks for this good news. I just wanted to ask you how to "Unlock Bootloader" to be able to install a custom ROM.
Thanks.
At least on my unit the bootloader came unlocked. If it doesn't, it should work like on a Nexus by running 'fastboot oem unlock'.
BTW, we fixed SELinux today; I expect nightlies to start in the next few days.
Gesendet von meinem R7plusf mit Tapatalk
@maniac103 Do you anything about cyanogenmod for oppo r7? Sorry if it is off topic.
Skickat från min R7f via Tapatalk
maniac103 said:
At least on my unit the bootloader came unlocked. If it doesn't, it should work like on a Nexus by running 'fastboot oem unlock'.
BTW, we fixed SELinux today; I expect nightlies to start in the next few days.
Gesendet von meinem R7plusf mit Tapatalk
Click to expand...
Click to collapse
AMAZING! Thanks for your work guys, awaiting!!!
Enviado desde mi R7plusf mediante Tapatalk
Seamless said:
Do you anything about cyanogenmod for oppo r7? Sorry if it is off topic.
Click to expand...
Click to collapse
We're waiting for its Lollipop update, as its current bootloader can't run 64 bit kernels. Otherwise it should be mostly ready though, as the two devices are very similar.
Gesendet von meinem R7plusf mit Tapatalk
maniac103 said:
We're waiting for its Lollipop update, as its current bootloader can't run 64 bit kernels. Otherwise it should be mostly ready though, as the two devices are very similar.
Gesendet von meinem R7plusf mit Tapatalk
Click to expand...
Click to collapse
Hi dev..
Nice to see such great progress here.
As I can see, you committed fully working fingerprint sensor HAL into cm.
I am not a dev, but just curios that how you managed this ?
AFAIK, fingerprint and Laser autofocus things are closed source by OEMs., thats why lots of devices lacking this in CM like OnePlus 2.
So, how ?
I surprised.
RohanAJoshi said:
As I can see, you committed fully working fingerprint sensor HAL into cm.
Click to expand...
Click to collapse
Correct.
I am not a dev, but just curios that how you managed this ?
AFAIK, fingerprint and Laser autofocus things are closed source by OEMs., thats why lots of devices lacking this in CM like OnePlus 2.
So, how ?
Click to expand...
Click to collapse
The fortunate thing is that the code actually talking to the fingerprint sensor runs in the trust zone, thus I 'only' needed to trace and analyze the communication between the stock ROM and the fingerprint trustzone app. This turned out to be manageable, and after understanding that protocol, implementing the HAL was pretty straightforward. Doing something similar should entirely be possible for most devices that do fingerprint management in the trustzone; unfortunately there are a number of devices with fingerprint sensor (especially the early ones) which don't do it in the trustzone, thus are mostly out of luck. I had an Oppo N3 before the R7 Plus and decided not even to start working on a fingerprint HAL for it due to the sheer complexity of the task.
Great that you guys managed to get the fingerprint sensor fully working. So as far as you guys have updated the status of this build, the only issues are unstable WiFi and cracking sound in notifications when in deep sleep? That's amazing for a very first release! Congrats!

[rom] aosp - caf 7.1.2 (24-10-2017)

As i promised I have been working into this build , finally got ti working properly and to be used as a daily driver. As for now I´m testing ( I don't have much time ) if you want to try it and give feedback I´ll try to repair all the bugs.I think everything is working at least for me ( 256gb/6gb ram ). I don't have much time to write a proper post so I will give you the mega link ( soon upload to androidfilehost ) . I promise to merge all the updates on the base code.
Download Link​https://mega.nz/#!dbozEBpb!kNG-ea8AYNovLEiAf-s_SDreC9xYAsHTpuIa2rxVIKM
Credits​
Big thanks to Marchetto ,BitO, CAF devs , Papps , all of you for downloading and testing and Me for spending 1 month with the rom hehe. Nothing more to say , just enjoy AOSP and pure Android. Best wishes and happy week.
Edit: NFC Not working ( Working on it , sorry : ( )
Nice..downloading and excited to try this out
rhong said:
Nice..downloading and excited to try this out
Click to expand...
Click to collapse
Enjoy !! And if you wish report bugs!!! Thanks for downloading ^-^
YazumiWuHung said:
Enjoy !! And if you wish report bugs!!! Thanks for downloading ^-^
Click to expand...
Click to collapse
Installed and running smoothly. The difference between PA by Bito and this is that this one is purely aosp .
Bugs encountered while replying is that chrome fc but when reopen it runs OK again. That's it for now.
Thanks dev!
Great!! Is proximity sensor working..? I have it pending in PA...
Can you share links to device tree sources, please?
Big thx for your work @YazumiWuHung !
I would love to have a ROM that properly nails the proximity sensor.
MrColdbird said:
I would love to have a ROM that properly nails the proximity sensor.
Click to expand...
Click to collapse
Even on stock ROMs there are the problems we have with our builds. And i'm fairly sure that several cases the users have are not making the situatrion better.
BitOBSessiOn said:
Great!! Is proximity sensor working..? I have it pending in PA...
Can you share links to device tree sources, please?
Big thx for your work @YazumiWuHung !
Click to expand...
Click to collapse
Yeah its working , at first it didn't but It does now. Brightness too ( Auto too ) , I have tried to make all work .
When I come back to Hong Kong ( tomorrow ) I´ll update the post with all the info and make it good looking .
Thanks i'll try tomorrow night
The problem isn't whether the sensor works or not, it's about whether it works reliably.
My proximity sensor sometimes does work, sometimes it doesn't, with the latter being the more common case, forcing me to manually turn the screen off during a call as to not hang up on the other side with my ear.
MrColdbird said:
The problem isn't whether the sensor works or not, it's about whether it works reliably.
My proximity sensor sometimes does work, sometimes it doesn't, with the latter being the more common case, forcing me to manually turn the screen off during a call as to not hang up on the other side with my ear.
Click to expand...
Click to collapse
Ah, really
The only time where the proximity was working reliably was with my first devicetree for the mix that was based on the marchmallow blobs. Since the switch to oss sound + nougat blobs it isn't working 100% for several users. As said, if you browse the China dev based ROM threads you could find several reports stating the same issues you describe. The logical conclussion is, the blobs Xiaomi provides are the problem, if you have problems like that with the stock based ROMs, too.
Anyway there are several cases on the market that make the proximity more unreliable too. I've tested and owned many cases and found two producing 100% the same issue and one killing the proximity 100%.
But you're right, the main issue is for sure the driver software.
Seems good, anyway to swap back and recent button
james1089 said:
Seems good, anyway to swap back and recent button
Click to expand...
Click to collapse
Probably need Xposed as this is pure aosp, no bells and whistles.
Sent from my MI MIX using XDA-Developers Legacy app
pappschlumpf said:
Ah, really
The only time where the proximity was working reliably was with my first devicetree for the mix that was based on the marchmallow blobs. Since the switch to oss sound + nougat blobs it isn't working 100% for several users. As said, if you browse the China dev based ROM threads you could find several reports stating the same issues you describe. The logical conclussion is, the blobs Xiaomi provides are the problem, if you have problems like that with the stock based ROMs, too.
Anyway there are several cases on the market that make the proximity more unreliable too. I've tested and owned many cases and found two producing 100% the same issue and one killing the proximity 100%.
But you're right, the main issue is for sure the driver software.
Click to expand...
Click to collapse
On ViperOs the proximity sensor has worked perfect and I have never had any issues with the sensor
Ultraman666 said:
On ViperOs the proximity sensor has worked perfect and I have never had any issues with the sensor
Click to expand...
Click to collapse
Yea viper and screwd, then other problems appeared down the line.
james1089 said:
Yea viper and screwd, then other problems appeared down the line.
Click to expand...
Click to collapse
I have no issues with anything on ViperOs...
I am going to download this and give it a try
Sent from my Viper MI MIX using Tapatalk
Ultraman666 said:
I have no issues with anything on ViperOs...
I am going to download this and give it a try
Click to expand...
Click to collapse
No Bluetooth streaming on screwd ROM.
Fine for Bluetooth calls though.
YazumiWuHung said:
Edit: NFC Not working ( Working on it , sorry : ( )
Click to expand...
Click to collapse
Any update on NFC fix?
Cheers
Enjoying the ROM
is there a reup link for this?

Developer Support

I like the phone and I want to upgrade from my 5T.
Since ROM and Kernel Development is very important for me I just wanted to ask if there are some developers who will get it and make a LOS and/or other Roms.
Tiz92 said:
I like the phone and I want to upgrade from my 5T.
Since ROM and Kernel Development is very important for me I just wanted to ask if there are some developers who will get it and make a LOS and/or other Roms.
Click to expand...
Click to collapse
Development will definitely be there.. but support for pop-up camera, 90hz display might take sometime
ram4ufriends said:
Development will definitely be there.. but support for pop-up camera, 90hz display might take sometime
Click to expand...
Click to collapse
What do you think about the fingerprint sensor? Took quit some to get it working on the 6t.
Tiz92 said:
What do you think about the fingerprint sensor? Took quit some to get it working on the 6t.
Click to expand...
Click to collapse
As it is already available for 6T.. I don't think it would take much time on 7 Pro

Fod and dttw

Is there any Android 12 rom that has the FOD and dttw working property with the always on display? Thank tou.
radaan said:
Is there any Android 12 rom that has the FOD and dttw working property with the always on display? Thank tou.
Click to expand...
Click to collapse
Hey there,
So far I tried derp, pixelex., Nameless and Cr droid without any luck.it seems that the aod is kind of broken on all of them, it works sometimes and sometimes not, I could not figure it out.
Also they are all bit stable enough for me, to much hickups, but that is just my opinion.
Greetings
TanakaX5 said:
Hey there,
So far I tried derp, pixelex., Nameless and Cr droid without any luck.it seems that the aod is kind of broken on all of them, it works sometimes and sometimes not, I could not figure it out.
Also they are all bit stable enough for me, to much hickups, but that is just my opinion.
Greetings
Click to expand...
Click to collapse
Thanks for the reply. Finally someone. I tested a few too and there is not one that has dt2w on the aod working. The rest works Just fine, at least considering my daily use.

Question Too saturated colors on custom

Hello !
I've already talked about this on the Project Elixir thread but I don't feel like there's really any progress on it.
I'm on Evolution X and once again, the colors are way too saturated, even in natural mode (which is the same setting as in adaptive)
I don't understand this problem which doesn't seem to bother people I have the impression...
Is this an AOSP issue? It's really annoying because otherwise the rom is really perfect, the author really did a great job for us but it's really difficult with a screen like that....
Thanks
Shuyin10 said:
Hello !
I've already talked about this on the Project Elixir thread but I don't feel like there's really any progress on it.
I'm on Evolution X and once again, the colors are way too saturated, even in natural mode (which is the same setting as in adaptive)
I don't understand this problem which doesn't seem to bother people I have the impression...
Is this an AOSP issue? It's really annoying because otherwise the rom is really perfect, the author really did a great job for us but it's really difficult with a screen like that....
Thanks
Click to expand...
Click to collapse
Yes Colors are indeed too sharp and saturated in Custom ROM's
It must be due to wrongly calibrated value of screen
Use terminal with root
service call SurfaceFlinger 1022 f 1
With value run from 0 - 2
You can set it like
service call SurfaceFlinger 1022 f 0.985
Really ?! Is it good ?!
Shuyin10 said:
Really ?! Is it good ?!
Click to expand...
Click to collapse
It's working on every phone I've ever test including realme
Is it better to Kcal saturation setting ? Unfortunately, that doesn't solve the problem. Unfortunately, that doesn't solve the problem.
Shuyin10 said:
Is it better to Kcal saturation setting ? Unfortunately, that doesn't solve the problem. Unfortunately, that doesn't solve the problem.
Click to expand...
Click to collapse
It has nothing to do with KCAL. Non KCAL kernel support it even Samsung's exynos
It's literally an open Android API
Vipxpert said:
It has nothing to do with KCAL. Non KCAL kernel support it even Samsung's exynos
It's literally an open Android API
Click to expand...
Click to collapse
Thanks, i'll try it soon !
Is it permanent or do you have to do it every time you reboot?
Shuyin10 said:
Thanks, i'll try it soon !
Is it permanent or do you have to do it every time you reboot?
Click to expand...
Click to collapse
Everytime you reboot actually. You can use termux widget for convenient
THANKS A LOT !
I used service call SurfaceFlinger 1022 f 0.92 and it's perfect for me !!

Categories

Resources