This is going to be for discussion of various issues with using older sensor HAL blobs on 4.4, and how to properly implement backwards compatibility.
To participate in this thread, you MUST have the Sensor Kinetics and Z-DeviceTest apps installed.
https://play.google.com/store/apps/details?id=com.innoventions.sensorkinetics - Sensor Kinetics
https://play.google.com/store/apps/details?id=zausan.zdevicetest - Z-DeviceTest
Current status:
Oppo Find 5
In Sensor Kinetics, 3D and Scalar sensors work. Derived sensors such as "Rotation Vector" do not work.
This manifests itself with a number of user-facing issues:
1) No compass in Ingress
2) No level/compass function in GPS Status and Toolbox
Fixes tried:
So far - None
Samsung Galaxy S4 family
I do not own this device. This section is based on reports from jumoog and others.
Some sensors don't work. I have yet to have anyone tell me which ones work and which ones don't. I need this information (especially if the behavior matches what I described above for Find 5)
If a number of sensorservice patches from 4.4 are reverted, some or all sensors begin working:
https://github.com/TEAM-Gummy/andro...a80c19/core/java/android/hardware/Sensor.java
(need to find the rest, out of time)
It is unknown what happens if only some of the sensor patches are reverted. Some of them seem benign and unlikely to cause issues
Sensors that dont work on: jflte (Samsung Galaxy S4)
All Sensor's detected
But this Sensor's give no value back:
Hardware
Gyroscope
K330 Gyroscope Sensor
Magnetometer
YAS532 Magnetic Sensor
Proximity Sensor
MAX88920
Barometer Sensor
Bosch
Software
Gravatiy Sensor
Linear Acceleration
Rotation Sensor
OK, so it's worse than find5 (raw mag/prox/gyro/accel work on find5) - do ANY sensors work?
Entropy512 said:
OK, so it's worse than find5 (raw mag/prox/gyro/accel work on find5) - do ANY sensors work?
Click to expand...
Click to collapse
Working Sensors:
Accelerometer
Ambient Temperature
Light Sensor
Pressure Sensor
Relativ Humidity
With TEAM-Gummy patch: broken left (only software Sensors)
Gravatiy Sensor
Linear Acceleration
Rotation Sensor
Ok, so your hacks bring it, at best, to a state where it matches the find5
Entropy512 said:
Ok, so your hacks bring it, at best, to a state where it matches the find5
Click to expand...
Click to collapse
Maybe this works with find5 too
Just to make sure, you are aware that there's more to sensors than just frameworks/base, such as hardware/libhardware, right?
MWisBest said:
Just to make sure, you are aware that there's more to sensors than just frameworks/base, such as hardware/libhardware, right?
Click to expand...
Click to collapse
thats true but dont need a patch for me
i use this https://github.com/chenxiaolong/hudson/commit/fecb144b093262b74010d7cdbcc532d1339cf0d2
MWisBest said:
Just to make sure, you are aware that there's more to sensors than just frameworks/base, such as hardware/libhardware, right?
Click to expand...
Click to collapse
What do you think I meant by "need to find the rest, out of time"?
Entropy512 said:
What do you think I meant by "need to find the rest, out of time"?
Click to expand...
Click to collapse
Ah, my apologies, I missed that! If you need some help finding things I'd be more than willing to assist, I learned quite a bit about the sensors when I added an ambient temperature sensor to the Galaxy Nexus (albeit somewhat unuseful due to the heat pollution from the rest of the phone's components >.<).
MWisBest said:
Ah, my apologies, I missed that! If you need some help finding things I'd be more than willing to assist, I learned quite a bit about the sensors when I added an ambient temperature sensor to the Galaxy Nexus (albeit somewhat unuseful due to the heat pollution from the rest of the phone's components >.<).
Click to expand...
Click to collapse
Heh. It's been quite a while since I last touched sensors, back since the old days when I was fixing up the sensor HAL for Exynos 4210 devices and adding the pressure sensor for the N7000.
Blob compatibility is always a pain in the ass because sometimes you have no idea why it isn't working. It's strange because if you look at all of Google's commits, the new sensor stuff should retain backwards compatibility with old HAL APIs...
On n7100, following doesn't work -
Compass
Light sensor
Proximity sensor
Rest all works.
Sent from my GT-N7100 using Tapatalk
Interesting. It looks like Google did a branch merge - as a result, there are commits buried deeper in the history than you might expect.
https://github.com/omnirom/android_frameworks_native/commit/cdd7d8bc145bbbd21a1689ed87a381287aeec229
It looks like the branch started after the April 17 commit in sensorservice's history (which can be viewed at https://github.com/omnirom/android_frameworks_native/commits/android-4.4/services/sensorservice )
After calibrating proximity sensor, it works.
Sent from my GT-N7100 using Tapatalk
Could someone upload gummy patches to gerrit ?
UtkarshGupta said:
After calibrating proximity sensor, it works.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
calibrating? So N7100 is fully working?
UtkarshGupta said:
Could someone upload gummy patches to gerrit ?
Click to expand...
Click to collapse
Which ones?
At this point, issues with fused sensors are fixed - https://gerrit.omnirom.org/#/c/2757/ (needs device tree change to enable) - this is confirmed on find5 and n1, and will likely fix the issues with jflte that remained after doing their sensorservice reverts. Obviously jflte needs something "extra" the question is - what?
Entropy512 said:
calibrating? So N7100 is fully working?
Which ones?
At this point, issues with fused sensors are fixed - https://gerrit.omnirom.org/#/c/2757/ (needs device tree change to enable) - this is confirmed on find5 and n1, and will likely fix the issues with jflte that remained after doing their sensorservice reverts. Obviously jflte needs something "extra" the question is - what?
Click to expand...
Click to collapse
There was a apparent fix for n7100 by calibrating. I did it and some how proximity sensor worked for 1-2 hours and then it was dead again. N1 and find5 are different from exynos so I think the fix for them would be different.
I'll try device tree part and see.
Also http://review.cyanogenmod.org/#/c/54482/ , seems hopeful. Since they are open source now, issues can be ironed out. But it would need a lot of work before its done.
Sent from my GT-N7100 using Tapatalk
Can you give some details as to this "calibration" process? I have noticed on find5 that no data is reported until after the sensor triggers once.
As to the setrate-on-enable - While I can confirm it affects qcoms, the reasons qcom put it in there indicate that other vendors are highly likely to have similar workarounds for pre-kitkat behavior. e.g. other sensor HALs may assume that they receive two setrate calls for each sensor and ignore the first one for "fused"/"derived" sensors like rotation vector and such.
The opensource sensors is another good approach, although after all I've learned, I'm wondering how much is given up with those sensors. I'm 90% certain the old galaxys2 family didn't have derived sensors implemented at the HAL level - but it sounds like N7100 does. In theory, motion fusion in the HAL is better tuned to the device than the generic one in the frameworks.
The process was for tw Roms only, which was reported later.
https://gerrit.omnirom.org/#/c/2389/ - this should fix software sensors I hope.
And yes setrate is for qcom devices. It can't effect exynos devices.
Sent from my GT-N7100 using Tapatalk
UtkarshGupta said:
The process was for tw Roms only, which was reported later.
https://gerrit.omnirom.org/#/c/2389/ - this should fix software sensors I hope.
And yes setrate is for qcom devices. It can't effect exynos devices.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Have you tried it? I would not be surprised at all if Samsung used the same hack in their Exynos sensor HALs that qcom did in theirs.
There is NOTHING qcom-specific about the change - the only "qcom" connection is that most devices with in-HAL sensor fusion are qcom-based. It really depends on what the HAL author did to handle multiple setrates on a fused/derived sensor - qcom ignored the first one, I wouldn't be surprised if Samsung used the same approach.
The setrate logic is one of the largest differences, from the perspective of a legacy sensor HAL, between 4.3 and 4.4 - Even if the workarounds for 4.3's double-setrate are different in other HALs, the fact that 4.3 and earlier did double setrates means that a lot of HALs are likely to assume that it happens and behave badly if only a single setrate is issued.
So for this "calibration" - you had to calibrate it in TW then flash over??? If that's the case, the calibration process may need to be reverse engineered and implemented in omni. (We did something similar for accel cal on the galaxys2 family ages ago...)
Related
From ICS to JB and still no camera recording fix at 720p. I thought i read somewhere in xda infuse that 720p recording was fixed, maybe i'm wrong.
cat2115 said:
From ICS to JB and still no camera recording fix at 720p. I thought i read somewhere in xda infuse that 720p recording was fixed, maybe i'm wrong.
Click to expand...
Click to collapse
It's a damn hard problem to fix. If you think about it it's a deep down driver level issue that requires a pretty broad skill base to diagnose and fix. Years of coding experience to understand yet alone begin to fix it... It doesn't help that this isn't supported by Samsung nor the camera developer.
So it's incredible that the damn thing even turns on. I'd say Entropy and jt are smart enough to fix it in time though
Sent from my SGH-I997 using xda premium
I miss 720, imo its the only thing holding me back from flashing any other ICS Roms. I wonder if the camera can be fixed with an aftermarket app, like how TORCH was fixed by using an app.
I guess this could help you https://www.box.com/s/e122d0f656ea949f58c2 It's from this forum http://www.htcmania.com/showthread.php?t=432576&highlight=Fix+grabacion+720p+JB
SMiGGs said:
I miss 720, imo its the only thing holding me back from flashing any other ICS Roms. I wonder if the camera can be fixed with an aftermarket app, like how TORCH was fixed by using an app.
Click to expand...
Click to collapse
in likely...I could be wrong but I believe the problem relays in the drivers/kernel
rodrigoalumno said:
I guess this could help you https://www.box.com/s/e122d0f656ea949f58c2 It's from this forum http://www.htcmania.com/showthread.php?t=432576&highlight=Fix+grabacion+720p+JB
Click to expand...
Click to collapse
NOOOOOOOOO DON'T USE THAT YOU WILL LIKELY BRICK OR BREAK THINGS!!!
That was taking from an HTC website...we have Samsung...two COMPLETLY different company's with COMPLETLY different hardware....
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
NOOOOOOOOO DON'T USE THAT YOU WILL LIKELY BRICK OR BREAK THINGS!!!
That was taking from an HTC website...we have Samsung...two COMPLETLY different company's with COMPLETLY different hardware....
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Sorry, but this forum is not only to HTC devices. If you take a moment, you see that it's like this web. The only mistake I maked is that this patch is for the Samsung Galaxy S i9000GT, but I post it just to help you. Maybe this patch could give you some idea to make one by yourself.
rodrigoalumno said:
Sorry, but this forum is not only to HTC devices. If you take a moment, you see that it's like this web. The only mistake I maked is that this patch is for the Samsung Galaxy S i9000GT, but I post it just to help you. Maybe this patch could give you some idea to make one by yourself.
Click to expand...
Click to collapse
I wasn't mad at you or anything...I knew you were trying to help, I mainly made such a big deal to ward off newbs...they may flash it. May break something then they freak out...wanted to save them.the trouble
Anyways...some of our best devs have been trying to fix it for quite a few months (entropy, jt1134...).theyve tried to use/adjust the I9000 camera patches...but still nothing :/
I just saw HTC in the address and assumed it was an HTC patch
Sent from my HTC PH39100 using Tapatalk 2
---------- Post added at 07:48 PM ---------- Previous post was at 07:32 PM ----------
Actually...720p is A LOT smoother then it used to be (haven't used it in months ) and just for the heck if it I flashed your linked I9000 zip...well after the flash it was back to how bad I had remembered (neither were good)
Sent from my HTC PH39100 using Tapatalk 2
Goodbye sweet 720p
SMiGGs said:
Goodbye sweet 720p
Click to expand...
Click to collapse
Here's the fix for 720p recording.
I am also torn over the missing 720p recording, but I am still incredibly happy with JB! The only other major issue is the banding I get in photos, although someone had mentioned that possibly JB changed the shutter/refresh speed in the camera which produces the banding under fluorescent lighting conditions. Unfortunately I saw nowhere to manually adjust this.
The other major issue was the darn thing disconnecting from Bluetooth in my Toyota Entune system, but supposedly version 2.12 and the OC V2 Kernel fix the issue. Will be testing it out today.
I get the same lighting effect on my pics as well. Paranoid Android, is working flawlessly. Besides 720 and other issues, its a great rom, and good on battery life.
Everything is almost fixed, so we might get lucky w/ 720
SMiGGs said:
I get the same lighting effect on my pics as well. Paranoid Android, is working flawlessly. Besides 720 and other issues, its a great rom, and good on battery life.
Everything is almost fixed, so we might get lucky w/ 720
Click to expand...
Click to collapse
I just wanted to update and say that the banding lines I was receiving seem to be isolated to a specific building at my university. I am guessing the JB Rom somehow changed the shutter rate setting and in doing so it introduced a "flicker" banding line effect due to the fluorescent lighting in the building. If I go outside, or to other buildings with fluorescent lighting it does not do this, so the bulbs in the original building must be perfectly attuned to a rate that interferes with the imaging sensor.
I haven't found a way to tweak or fix this issue, but as long as photos in most other lighting and outside are fine I am alright with it.
Please try this out and let me know if this is also your issue.
SirAndroid said:
I just wanted to update and say that the banding lines I was receiving seem to be isolated to a specific building at my university. I am guessing the JB Rom somehow changed the shutter rate setting and in doing so it introduced a "flicker" banding line effect due to the fluorescent lighting in the building. If I go outside, or to other buildings with fluorescent lighting it does not do this, so the bulbs in the original building must be perfectly attuned to a rate that interferes with the imaging sensor.
I haven't found a way to tweak or fix this issue, but as long as photos in most other lighting and outside are fine I am alright with it.
Please try this out and let me know if this is also your issue.
Click to expand...
Click to collapse
That's cool! I wish I could find a way to reproduce that!
Just released Vecorder, a new free android app for estimating the height of objects! Move along the object and let the app derive the height difference through the acceleration sensors of your device! Would love to here some feedback about this app, especially the success/failure rates of your height scans.
Try it out through Google Play: https://play.google.com/store/apps/details?id=de.mathfactory.vecorderfree
Mathfactorysoftware said:
Just released Vecorder, a new free android app for estimating the height of objects! Move along the object and let the app derive the height difference through the acceleration sensors of your device! Would love to here some feedback about this app, especially the success/failure rates of your height scans.
Try it out through Google Play: https://play.google.com/store/apps/details?id=de.mathfactory.vecorderfree
Click to expand...
Click to collapse
Nice idea!
Unfortunately it doesn't work on my Desire. but I guess that's because the device is quite old - once I lift the phone it just keeps on counting and counting.
not bad,it worx perfectly and the height is right i have test many times.hve rated 5stars in store.:good:
Thanks for your feedback and the rating!
charliebigpot said:
Nice idea!
Unfortunately it doesn't work on my Desire. but I guess that's because the device is quite old - once I lift the phone it just keeps on counting and counting.
Click to expand...
Click to collapse
Well, the method *should* work also with older phones (if the acceleration sensors are not extraordinarily crappy or damaged). After some researching it turns out there could be another interesting explanation for those "runaway"-countings: The sound speakers sometimes seem to irritate the acceleration sensors when playing sounds too loud (through sound vibrations). The start signal played by the app could then be interpreted as a movement by the sensors. So, you could try to mute the sound before making a scan. And leave a message if that was the reason.
I will address this issue in an app update the next days by reducing/removing the sounds while sensors are active.
Stay tuned.
Released Vecorder v1.1
Released v1.1 of Vecorder on Google Play. Changelog for this version:
- Shortened start signal to prevent acoustic interference on acceleration sensors
- Slightly improved standstill detection
Keep vecording!
charliebigpot said:
Nice idea!
Unfortunately it doesn't work on my Desire. but I guess that's because the device is quite old - once I lift the phone it just keeps on counting and counting.
Click to expand...
Click to collapse
Same problem on my galaxy s3 mini gt-I8190
Sent from my GT-I8190 using xda app-developers app
Nice idea. Worked perfectly on my HTC one . Pretty nice result for an estimate. Thanks for sharing the app
Edit: my suggestion would be to add option for metrics/us measurement. I personally use cm; but some people might like option for inch
Sent from my HTC One using xda app-developers app
shuvarts said:
Nice idea. Worked perfectly on my HTC one . Pretty nice result for an estimate. Thanks for sharing the app
Edit: my suggestion would be to add option for metrics/us measurement. I personally use cm; but some people might like option for inch
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for your suggestion! I have implemented your idea in Vecorder 1.2 available as of today with support for the metric and the imperial unit system.
Nice idea!
Unfortunately it doesn't work on my Desire. but I guess that's because the device is quite old - once I lift the phone it just keeps on counting and counting.
Click to expand...
Click to collapse
The new version of Vecorder has some adjustments to prevent such runaway readings. Also please try to follow the procedure description given in the app or the google play page. Runaway readings especially do occur if you don't move the device along the force of gravity. If you've done everything correct and it still doesn't work with the new version please report back!
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!
Any chance of having pure Android on S6?
On previous Android devices we always were having lots of problems on AOSP roms. Will it be like that on S6 too?
eruben said:
On previous Android devices we always were having lots of problems on AOSP roms. Will it be like that on S6 too?
Click to expand...
Click to collapse
How would we know that? There are not even early alpha stage CM Roms on the horizon for the S6...
Not unless Samsung provides proper documentation for the Exynos processor first.
Why would you want Cyanogenmod on the S6 when the stock is so fast & optimised for the S6. You'd also loose fingerprint scanner and camera quality would drop
Shipoftheline said:
Why would you want Cyanogenmod on the S6 when the stock is so fast & optimised for the S6. You'd also loose fingerprint scanner and camera quality would drop
Click to expand...
Click to collapse
finger print wont drop in cm13 it has built in support
bhavstech said:
finger print wont drop in cm13 it has built in support
Click to expand...
Click to collapse
It may have fingerprint support built in but you must get the drivers to work correctly or else it would never work. Don't assume it would work "just as it should" because it is supported natively.
popthosegaskets said:
It may have fingerprint support built in but you must get the drivers to work correctly or else it would never work. Don't assume it would work "just as it should" because it is supported natively.
Click to expand...
Click to collapse
one more bad news
CM on these pieces of sh*t is all bad news,
Sent a year in the future from my s6 edge+
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 Linkhttps://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?