2016/4/25
DU has released the v10.1 which is Android 6.0.1_r30. A few bug fixes are included.
2016/4/14
Omni merged Android 6.0.1_r30. This is mainly an version update. Cheers!
2016/4/5
In this CM build, the flickering fix is included. CM also use the opensource UMB library now. Minus one in the blobs count and better chance for newer versions of Android. Cheers!
2016/4/3
DU use the AOSP linker. When updated to 6.0.1_r22, the PIE support is gone. I have rebuilt the linker. Flash this
View attachment du-gps-patch.zip will get the gps back. For i815, GPS is ok but the RIL library requires the same PIE support. You need to flash it too.
2016/3/31
The current Gapps have permission issues again. Flash this
View attachment gapps-perm-patch.zip after the ROM and Gapps would fix the permissions of Gapps at reboot.
Theory: I didn't want to change the original security of AOSP so I put an init.d script to fix the permission at start. It would be the same as the assignment of permission in App settings. The default security and permissions hierarchy is preserved. I think this is the better way.
However, the current growth of ROM and Gapps delay the Package Manager service (which is for permission granting). A wait loop is now added to the script. It would wait for the Package Manage service now. I think it would work for the future Gapps too.
2016/3/29
As I suspected, there are a few coincidences cause the flickering. DU and CM are quite different and yet both have the flickering issue... :cyclops: After I fixed the calculation of ambient and debouncing, the other cause embossed. I was aiming at the openGL, gui, ui, sensor, brightness and algorithm for weeks. Seems all dead ends after the fix. I decided to put it aside and started testing the Carbon-M. Carbon-M is quite "primitive" and close to AOSP. There is no flickering as expected.
When you have eliminated the impossible, whatever remains, however improbable must be the truth... I then start again with the whole frameworks. I compared the four sources and eliminate the libraries one by one. Finally, I think I found a solution! Only time can tell if it is the ultimate cure. :fingers-crossed:
Hoping this DU is more or less the complete released. Cheers!
2016/3/23
Omni also merged the 6.0.1_r22 source and It's been over a month since the last update. There are a few bug fixes in PerformanceControl. I also updated the modem driver for i815 in the kernel. Hoping the mobile data would work now. :fingers-crossed:
2016/3/15
CM has merged the latest 6.0.1_r22. It's time to have an update. The same fixes applied and the flickering is almost gone now. At this moment, it is more or less fully functioning now. Cheers!
2016/3/7
DU had updated the included SuperSU zip to 2.65 which is not working for our kernel. You would see an error message at the end of flashing.
For the time being, you can manually flash the Beta-SuperSU-2.52 after the rom to get root. I already updated the build script. Subsequent builds will replace the included SuperSU.
2016/3/5
The Display settings crashed in the last DU 20160303. This
View attachment du-patch-20160305.zip would fix that.
2016/3/3
Finally, I narrow down to a few services that cause the flickering of screen. I believe there are a few overlapping incidences causing it. The random combinations of ambient and debouncing calculation are almost impossible to trace. I can't say the flickering is completely gone now but it is limited to only a few at start. Similar fixes will be apply to CM later. I seldom quit the thing I started and the update of DU is always on my mind. This is the second and hoping the fully working DU. Cheers! :victory:
2016/2/22
Although r16 is out, it was for Pixel-C and based on r5. May be that's why CM and Omni didn't merge it.
I was thinking to release a new DU but I still have no idea about the flickering yet. I'm also busy on my Nexus7 developments. Omni has included some consolidations and I have fixed a few things. I think it's about time to have an Omni update. I didn't test it in deep. Hoping everything is still in the right place...
2016/2/10
I spent most of the time studying why there is flickering in CM-13.0 and others but not Omni6. It was really random to track a path. I haven't find anything concrete yet. I have put a few stability measures though. Anyway, it's a new version release. Some part of the performance control apk were rewritten.
2016/2/4
Turn out there are limits for a single post. So grouping all ROMs to one thread was another wrong move... Have to make adaptions later.
After a few long day and night of boring and sweaty works, I can finally sit down in front of my Ubuntu PC to enjoy a coffee. It is harder and harder to earn a few more bucks now...
Omni and CM just merged to the latest Android 6.0.1_r13 now so It's time for a new Omni. I had included the "Double tap to wake" feature in the kernel last week. I have tried on my Nexus 7 and p6800 for sometimes. After a few adjustments, I think it's time to release it for everyone to test. A new settings is added to the Advanced page of Performance Settings. Check post#2 for details. Tab Plus use a different touch screen. I just did what I thought appropriate, please report.
I hope there is nothing missing in this build but who can tell? :cyclops:
2016/2/2
There was a report that 20160122 cm-13.0 for Tab-plus not boot. I used a build script to build all the models. I think the ccache in my new system might catch some objects from 7.7. The graphic objects have different screen size which stop tab plus' graphic driver with a black screen. I have rebuilt the CM kernels for Tab plus. They will be available in the host and mirror shortly.
2016/2/1
Apn-config.xml is missing in the last DU-10.0. Apn set up would crash. I packed a patch which is in post
#239.
2016/1/27
Since there are not much progress in CM and Omni, I tried another ROM the
Dirty Unicrons. DU is also an old player for years. I use DU in my Nexus 4 for sometimes. It is stable and amazing. DU is even closer to AOSP than Omni. Even if it included SuperSU, it has smaller foot print. The Dirty Tweaks apk offers a lot of customizations. Before my hard drive failure, I can't fix a bug so I delayed it. Fresh start sometimes would give us surprises. I finally fixed the bug in DU. Sadly, it also got the occasional flickering. Really don't know why
Seems only Omni is immune from it. I used the same HAL libraries from Omni and most of the Graphic codes are the same! That must be something buried really deep... Any idea is welcome.
Anyway, DU has its good character which is worth trying. Enjoy!
2016/1/22
In this build, the barcode and Google translate format is fixed. Those apps won't crash now. I added extra settings to L2CAP in Bluez. Files can be sent via Bluetooth now but still can't received files. The occasional flickering appear in other Samsung devices too. I patched a few things for that. Seems it's gone now but only time can tell.
3minit battery mod is included as Omni. (See Q&A in post#2).
This is the first CM after my hard drive failure. Hoping everything is in the right place now... :fingers-crossed:
2016/1/18
2016/1/17
2016/1/16
2016/1/15
2016/1/7
2016/1/6
2015/12/30
2015/12/29
2015/12/22
2015/12/16
2015/12/14
2015/12/10
2015/12/8
2015/12/6
Flash this
View attachment 3567048 if you have SIM detection problem.
2015/12/5
2015/11/28
2015/11/26
2015/11/24
2015/11/16
2015/11/14
2015/11/4
2015/10/27
