Related
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
Hey folks, I am Canadian that is looking to possibly import an MI5 but I figured I should find out a few things from you all that have been living with these phones for a while before buying.
Are there any hardware or software issues with the MI5 that I should be concerned about? I have a sony z3 compact right now and it's been infamous for vibration motors, headphone jacks, and screen failures. It also has no AOSP based daily drivers.
Development seems to be pretty active here, is that actually true? Are developers dropping off from this phone or is there still a steady amount of work being done?
From the lurking I've done it seems that unlocking, rooting and ROM installing is pretty easy. Are there any permanent dangers to doing these hacks (above and beyond the usual)?
I'm aware there is some camera quality issues on non-stock ROMs, is the camera still usable? How is the battery on custom ROMs?
Is there anything preventing this phone from being a daily driver when using a custom ROM like RR? Does the fingerprint sensor work on AOSP ROMs?
I am also aware of the radio bands the MI5 supports, I should be fine with that as my imported Z3 Compact has the same bands (as far as I can tell).
Edit: I was also wondering if the IR blaster works on custom ROMs!
Thanks for reading, answering and putting up with my ignorance. I'm just looking for some answers I couldn't find on this forum when I was searching yesterday.
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
xdadevet said:
Community is happy to help
1. Hardware wise you have to keep in mind the phone is fairly fragile. Low light performance of the camera is a bit poor. Audio out of the headphone jack isn't great on stock MIUI, but that can be fixed with Viper4Arise or any AOSP ROM. RAM management and general performance on MIUI is "ok" - but the phone is blazing fast on AOSP + CAF. There is no component that is prone to fail that I am aware of, but I have read of the occasional hard-brick triggered from nothing more than a reboot on custom ROMs - this can be solved by flashing stock ROM in EDL mode.
2. There seems to be a steady amount of development going on - we just got the drop on about 7 new ROMs in the last month. However, there are and have been developers leaving in favour of the One Plus 3, and development is only moderate compared to its forum.
3. It's fairly easy, but a bit frustrating getting the bootloader unlock from Xiaomi, as it usually takes about 5 days for the unlock to be approved and then 5 more days for it to actually work. There is also a possible driver issue on Windows which can prevent unlocking, so if you're stuck that's probably the case. Except for the above mentioned possible hard-brick there are no additional dangers, and dare I say less so than other phones I worked on.
4. The camera is usable on custom ROMs but considerably worse. Mainly there is a lot more noise in the photos, but detail remains high. Video recording seems to be broken on most AOSP ROMs, but alternative camera apps are apparently a work around. In my experience battery life is better on custom ROMs as they have functional Doze on Nougat, but not by much.
5. Fingerprint sensor works fine on custom ROMs, even better if you consider that you can wake + unlock your phone without pressing the button. There have been reports of some people experiencing slow fingerprint scanning on custom ROMs (3-4s). I use a custom ROM as my DD and I don't have any major issues except video recording that I haven't yet bothered to address.
I hope that this information finds you well. The Mi5 isn't perfect, but I'd be damned to say that a better phone exists for $200. The camera, battery life, performance, screen, audio, and design is good and there really isn't much to worry about.
Click to expand...
Click to collapse
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
TheHow7zer said:
Thank you so much for the detailed response! Greatly appreciated!
This all is reminding me of the fun I had with AOSP ROMs back on my Galaxy SIII, happy thoughts! (I've been stuck in Sony's software for too long!)
What is CAF?
Is the IR blaster working in AOSP-based ROMs?
Click to expand...
Click to collapse
It's a pleasure
Well then it's good to know they run brilliantly on the Mi5 (buttery smooth UI, and I get good numbers on benchmarks as testament, see attached pics).
CAF is short for Code Aurora Forums, a collection of companies that merge their updated driver code with the vanilla AOSP code from Google.
I don't know if the IR blaster works on AOSP as I currently don't have any devices on me to test it with. I could try this weekend when I get home.
Edit: I've since arrived home and can confirm the IR blaster works on AOSP. I used Anymote if you're interested.
What do you think? Will the indisplay Fingerprint Scanner Work with custom ROMS like Lineage etc. Also Will the pop up camera work?
Some custom ROMs for the OnePlus 6T has the in-display fingerprint working but there is no animation while using it.
You should be rather worried about the front camera motor.
Dear All,
I want to switch to AOSP from MIUI if possible. Are there any ROM's for Mi9 which doesn't have any bugs/functionality broken in AOSP. For me the camera, bluetooth, fingerprint, batterylife are very important.
AOSP based ROMs tend to be buggier than MIUI, you can either try yourself or browse each ROM's thread and see for yourself what issues people are reporting. Achieving 100% bug free is near impossible, today's OSes are too complex to be tested thoroughly with limitless configurations from one person to another. At least MIUI gives guarantee for conditions they test, most AOSP based ROMs only state "you tell me" in the bug section, showing that the ROM is lightly tested only.
Sadly there is no Bug free aosp rom and i think there will never be one. The Best you can do is using stock rom or xiaomi.eu rom and debloat it if you dont want/need miui stuff, there are two or three threads related to debloat.
I'm on extendedui everything looks functional so fare. Only have few problems with automatic brightness and stuttering Bluetooth streaming but didn't take time to try to fix this issue.
samsac said:
I'm on extendedui everything looks functional so fare. Only have few problems with automatic brightness and stuttering Bluetooth streaming but didn't take time to try to fix this issue.
Click to expand...
Click to collapse
what about FOD?
It's working fine.
Hello,
although the developers are very active and we are getting there, my question is whether there's a ROM that is "complete" at the moment.
With that, I mainly mean the 100% working fingerprint sensor. With that, I mean a ROM that doesn't 100% brightness while using fingerprint reader and that has a functional fingerprint reader when screen is turned off (ie. wakes the phone)?
I am excited about the recent developments, however, I am just looking for a smooth experience for the time being
Thanks again to all the hard working developers.
At the moment, I think the only one that does not light up the screen (not tested by me) is Statix, BUT, apparently the screen needs to be at at least 40% brightness for the fingerprint scanner to work.
You can try all of these and chose the best one for you
(Lineage(18.1/19), OmniRom, StatixOS, ArrowOS (no longer supported, the unit of the maintainer ramdump-ed.))
I haven't tried Statix yet. Good time to try.
At the moment, I think the only one that does not light up the screen (not tested by me) is Statix, BUT, apparently the screen needs to be at at least 40% brightness for the fingerprint scanner to work.
Click to expand...
Click to collapse
Does this mean that fingerprint doesn't wake the phone either?
I currently have Los19, wasn't able to get 18.1 working. Haven't tried OmniRom, but I've tried ArrowOS and it wasn't bad.
Thanks for the pointers! Does anyone know what's the reason everyone is having problems with the scanner?