[ROM][MTC20F][GalaxyTab7.7|Plus][13Aug2016 OmniROM-6]Android Marshmallow ROMs

Status
Not open for further replies.
Search This thread

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,344
Hong Kong
Realme X2


Here comes the Marshmallow!
I don't want to waste too much time to maintain a few threads. From now on, I'll put all Marshmallow developments in this thread.
Since Tab Plus is almost identical, it'll also be included here. All builds are unofficials. Please click the ROM images for details and read post#2 for extra infos.

Release Note: :)
2016/8/13
This is the Android-6.0.1_r62 version of OmniROM-6. This might probably be the last Omni-6. ;)

2016/8/4
This is the Android-6.0.1_r62 version of DU-10.4. :D

2016/7/29
This is the Android-6.0.1_r52 version of CM-13.0. As N is coming, it might probably be the last CM-13.0.
There were few reports on Gapps issues but again with no detail. I already mentioned many times that I can't access Google services locally. I tried once more on this new build via VPN and again I have no problem with that.
1. I flashed the latest CM (20160729) + opengapps pico 20160722 + SuperSU 2.52 with the latest TWRP 3.0.2-0.
2. After a factory reset and reboot, I completed the setup.
3. I connected to a VPN and add a Google account.
Everything went smooth as expected.
The following are the screenshots:
Screenshot_20160730-132605.png Screenshot_20160730-133601.png Screenshot_20160730-133233.png
I had also done a battery life test:
1. no sim card
2. WiFi off after sleep
3. Added a Google account.
My 3 years old battery can standby over 2 weeks. Everytime I turn on the screen, WiFi connected normally.
Here is the screenshot
Screenshot_20160609-021420.png
*** These are the minimal essential info. required for a report, nothing less.
*** If you don't want to provide those, just don't post. You'll be ignored...
;)

2016/7/7
DU-10.3 (Android 6.0.1_r46) is out. Cheers! ;)

2016/6/21
This is the Android-6.0.1_r46 version of OmniROM 6. Cheers! ;)

2016/6/9
This is the Android-6.0.1_r46 version of CM-13.0. Cheers! ;)

2016/5/25
DU-10.2 (Android 6.0.1_r43) is out. Cheers! ;)

2016/5/11
Omni merged Android 6.0.1_r43. This is mainly an version update. Cheers! ;)

2016/5/3
This is the Android-6.0.1_r30 version of CM-13.0. The adaptive brightness and live display are fixed. The Bluetooh app is also patched to work with Bluez now. Cheers! :D

2016/5/1
Android-6.0.1_r30 required a patch to work with Bluez. You may find the patch here. ;)
This patch would work for the latest Omni (20160414) and DU (20160425).
HISTORY:

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! :D

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! :D

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... :D

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... :eek:
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 :confused: 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


Screenshots: :laugh:
Screenshot_20151216-171540.png  Screenshot_20151216-171609.jpg  View attachment 3531073

Change log: :victory:
Code:
[COLOR="Blue"]2016/8/13[/COLOR]
  - Latest 6.0.1_r62 (MTC20F) source from Omni
  - Add PowerHAL for exynos4
  - Add MM native support for double tap wake in Display settings
  - Bluez 5.41 update
[COLOR="Blue"]2016/6/21[/COLOR]
  - Latest 6.0.1_r46 (MOB30M) source from Omni
  - Bluez update
[COLOR="Blue"]2016/5/11[/COLOR]
  - Latest 6.0.1_r43 (MOB30J) source from Omni
  - Bluez 5.39 from bluez.org
[COLOR="Blue"]2016/4/14[/COLOR]
  - Latest 6.0.1_r30 (MOB30D) source from Omni
  - Default RW permission for exteranl sdcard
  - Testing Mira cast with new Wifi library
  - Bluez 5.38 from bluez.org
[COLOR="Blue"]2016/3/23[/COLOR]
  - Latest 6.0.1_r22 (MHC19J) source from Omni
  - kernel: update modem driver for i815
  - Settings: fix a bug which cause Advanced page crash at the first launch
  - SystemUI: fix a bug in status bar
[COLOR="Blue"]2016/2/22[/COLOR]
  - Latest 6.0.1_r13 (MMB29U) source from Omni
  - kernel: fix a bug in DT2W
  - kernel: fix the occasional background process crash at cpu idle
  - PerformanceControl: fix the initial settings for CPUsettings
  - SystemUI: Fix the crash when 3minit battery apks not installed
  - Latest update from Bluez
[COLOR="Blue"]2016/2/4[/COLOR]
  Source revisions: 
  - Latest 6.0.1_r13 (MMB29U) source from Omni
  - kernel: Double tap to wake (DT2W), initial commit
  - kernel: DT2W, fine tune settings
  - Settings: add DT2W settings in Advanced page of Performance Settings
  - Settings: add bound region and time between taps controls
  - Settings: Add DT2W translations for zh-rCN, zh-rHK and zh-rTW
  - Bug fix in video playback
  - Bluez: fix file send via bluetooth. (receive still fail)
[COLOR="Blue"]2016/1/15[/COLOR]
  Source revisions: [ATTACH]3611268._xfImport[/ATTACH]
  - Latest 6.0.1_r10 (MMB29T) source from Omni
  - kernel: F2FS support
  - kernel: Fix a bug in F2FS
  - Rewrite samsung color format support
  - Fix rotation freeze after deep sleep.
  - To keep the data persist at reboot, PerformanceControl requries ROOT now
  - Add Power (screen off) Tile to QS. Short press:screen off, Long press:power menu
  - Include 3minit battery mod in SystemUI. (work with app from 3minit)
  - Bluez 5.37 update from bluez.org
  - DRM: low the security to Level 3
[COLOR="Blue"]2015/12/29[/COLOR]
  Source revisions: [ATTACH]3592090[/ATTACH]
  - Fix the RIL libraries for i815, 
  - GPS fix with Dmitry's patch as in cm-13.0
  - Latest Nexus5 DRM blobs
  - Introduce the new OmniJaws
  - New boot animation and wall paper (seems not working for us)
  - Delay the init.d script to 99ApkPermissions 
  - Increase the time out of AOT compiler
  - New set of camera preview data for Tab-Plus
  - gcc 4.9 is used for kernel and platform
[COLOR="Blue"]2015/12/16[/COLOR]
  Source revisions: [ATTACH]3578277[/ATTACH]
  - Latest 6.0.1_r3 (MMB29M) source.
  - Add 80ApkPermissions script to init.d
  - Add captive portal check switch in build property
  - Fixes in telephony to support 6.0.1
  - Add a few debug lines in camera HAL (for Tab-plus testing)
  - Fix a few minor bug in kernel
  - BlueZ update from bluez.org
  - Start Handsfree protocol without WB
[COLOR="Blue"]2015/12/5[/COLOR]
  Source revisions: [ATTACH]3565823[/ATTACH]
  - Fix video recording in Camera
  - Fix video playback (a bug in colorformat)
  - Fix rotation stop after awake
  - Suport SAMSUNG LPM in libhealth. (Fix reboot at power off when charge/usb cable is plugged)
  - Merge Mali API 29 code to kernel driver.
  - Update to Mali API 29 blobs
  - A few patches in the kernel
  - First port of BlueZ 5.36 to M
  - Reinstate the BlueZ support in kernel and platform
[COLOR="Blue"]2015/11/24[/COLOR]
  - Latest 6.0.0_r26 (MDB08M) source.
  - Triple check the RIL libraries for p6200 and t869
  - Patch in Camera HAL which fixed the torch in QS
  - Merge the Linux kernel source 3.0.y (3.0.101).
  - Disabled the Bluetooth backport for the time being. (Conflict with net)
  - Support for Samung LPM which avoid rebooting at power off (when charger or USB cable connected)
  - Include the GPS patch for the last build
  - Fix the Power management HAL.
  - Fix a few Omni features
  - Fix the glitches at rotation
[COLOR="Blue"]2015/11/14[/COLOR]
  - New blob for RIL (binary hack from newer Samsung device)
  - RILClass: update the responses and include new requests
  - optimize build script to shorten the time of flash
  - Rewrite the Camera HAL
  - Fix some Omni features
  - Add GPU support to PerformanceControl
  - Samsung Color Format support for codec
  - Replace some text relocation blobs
[COLOR="Blue"]2015/11/4[/COLOR]
  - Fix the external storage support
  - Support for  mode
  - Support for OTG sdcard
  - Fix the Camera
  - Add screenshot tile in QS
  - consolidate the boot menu
  - included the libemoji for Emoji factory
[COLOR="Blue"]2015/10/27[/COLOR]
  - Omni source 6.0.0_r1 (MRA58K), alpha release
  - Fix build for Frameworks, Settings, PerformanceControl, Hardwares, etc.
  - Fix release tool to pass build
  - Fix boot loop in boot.img
  - Fix orientation and colorspace
  - Fix light sensor
  - Fix GPS
  - Add kernel uid_cputime support
  - Add boot menu

Know issues: :(
1. Transmit large file to server with ES file explorer would crash. For the time being, use other apk (eg. AndSMB, Astro, etc.).
  TO DO: Without the source of ES, nothing can be done.... *
2. Mobiledata for i815 probably working now.
  TO DO: A shim library and a few patches with the blob. Can read the Baseband now. Waiting for report form i815 owner
3. Fast forward in video playback not working properly.
4. Adopted mode for ext. sd might not work.
5. May be more. Please report.
*** Number of asterisks indicate the importance and priority. ***



Screenshots: :laugh:
View attachment 3569154  Screenshot_20151209-151140.png
Change log: :victory:
Code:
[COLOR="Blue"]2016/7/29[/COLOR]
  - Latest 6.0.1_r52 (MOB30R) source from CM
  - Add custom PowerHAL
  - Add native support for double tap wake in Display settings
  - BlueZ 5.41 update
[COLOR="Blue"]2016/6/9[/COLOR]
  - Latest 6.0.1_r46 (MOB30M) source from CM
[COLOR="Blue"]2016/5/3[/COLOR]
  - Latest 6.0.1_r30 (MOD30D) source from CM
  - Fix the adaptive brightness and live display
  - Bluetooth app: patch to work with Bluez
  - BlueZ 5.39 update
[COLOR="Blue"]2016/4/5[/COLOR]
  - Latest 6.0.1_r22 (MHC19J) source from CM
  - Fix the occasional flickering for screen
  - Testing Mira cast with new Wifi library
  - Open source UMB library
  - Enable write permission for external sdcard
  - kernel: update modem driver for i815
  - PerformanceControl: fix a bug which cause Advanced page crash at the first launch
  - BlueZ 5.38 update
[COLOR="Blue"]2016/3/15[/COLOR]
  Source revisions:
  - Latest 6.0.1_r22 (MHC19J) source.
  - All fixes in Omni6
  - Fix the Display service for Ambient and Decouncing calculation
  - kernel: A few minor fixes
  - PerformanceControl: Fix the crash of Highend Graphics in Advanced page
  - BlueZ update from bluez.org
[COLOR="Blue"]2016/2/10[/COLOR]
  Source revisions:
  - Latest 6.0.1_r13 (MMB29U) source.
  - kernel: Double tap to wake (DT2W), initial commit (see post#2 for detail)
  - kernel: DT2W, fine tune settings
  - PerformanceControl: add DT2W settings in Advanced page 
  - PerformanceControl: add bound region and time between taps controls
  - PerformanceControl: Add DT2W translations for zh-rCN, zh-rHK and zh-rTW
  - SystemUI: fix a bug in 3minit battery which cause battery icon not shown
  - Fix video playback.
[COLOR="Blue"]2016/1/22[/COLOR]
  Source revisions: [ATTACH]3618827._xfImport[/ATTACH]
  - kernel: fix a bug in F2FS
  - camera: fix the format for barcode and Google translate
  - Fix auto rotation. (Not working in the previous builds)
  - PerformanceControl: settings are persist after reboot now
  - DRM: low the security to Level 3
  - Include 3minit battery mod in SystemUI. (see post#2 for detail)
  - Bluetooth: Fix in l2cap settings. Files can be sent now but not received yet..
[COLOR="Blue"]2016/1/6[/COLOR]
  Source revisions: [ATTACH]3601912._xfImport[/ATTACH]
  - Latest 6.0.1_r10 (MMB29T) source.
  - Add F2FS support in kernel
  - Modify gpsd blob to load libdmitry
  - Fix in sensor listener. (for rotation fail after deep sleep)
  - gcc 4.9 is used for both kernel and platform
  - Fix the RIL libraries for i815, 
  - Latest Nexus5 DRM blobs
  - Increase the time out of AOT compiler
  - Seperate set of camera preview and thumbnail data for Tab-Plus
  - BlueZ 5.37 update from bluez.org
[COLOR="Blue"]2015/12/22[/COLOR]
  Source revisions: [ATTACH]3585427[/ATTACH]
  - Add libdmitry to fix Gps
  - Modify gpsd blob to load libdmitry
  - stlport build from source
  - New DRM blobs from other device
  - Add USES_LEGACY_ACQUIRE_WVM support to frameworks
  - Add old Parcel::writeBlob() definition to work with the old blobs
  - Add ApkPermissions script to init.d (to fix the permissions of Gapps)
  - Fix i815 data by shim library
  - exFat support for external sdcard (from CM)
  - BlueZ update from bluez.org
[COLOR="Blue"]2015/12/10[/COLOR]
  Source revisions: [ATTACH]3571293[/ATTACH]
  - Latest 6.0.1_r3 (MMB29M) source.
  - Enable hot swap to disable the "SIM card added" pop up
  - Add captive portal check switch in build property
  - Fixes in telephony to support 6.0.1
  - Use original AOSP keyboard (CM's port crash on new Google service)
  - BlueZ(5.36) support for M
  - Start Handsfree protocol without WB
[COLOR="Blue"]2015/11/28[/COLOR]
  Source revisions: [ATTACH]3563538[/ATTACH]
  - Latest 6.0.0_r26 ((MDB08M) source.
  - Patch in Camera HAL which fixed the torch in QS
  - All fixes in Omni6
  - Fix the Power management HAL.
  - Mali API 29 blob update 
  - Merger Mali API 29 source to kernel driver (r3p2-01rev4)

Know issues: :(
1. Transmit large file to server with ES file explorer would crash. For the time being, use other apk (eg. AndSMB, Astro, etc.).
  TO DO: Without the source of ES, nothing can be done.... *
2. Mobiledata for i815 probably working now.
3. Adopted mode for ext. sd might not work.
4. May be more. Please report.
*** Number of asterisks indicate the importance and priority. ***




Screenshots: :laugh:
Screenshot_20160128-232531.png Screenshot_20160128-232626.png Screenshot_20160128-232617.png
Change log: :victory:
Code:
[COLOR="Blue"]2016/8/4[/COLOR]
  - Latest 6.0.1_r62 (MTC20F)-DIRTY-DEEDS v-10.4
  - Add custom PowerHAL
  - Add native support for double tap wake in Display settings
  - BlueZ 5.41 update
[COLOR="Blue"]2016/7/6[/COLOR]
  - Latest 6.0.1_r46 (MOB30M)-DIRTY-DEEDS v-10.3
  - All Fixes from Omni are included
[COLOR="Blue"]2016/5/25[/COLOR]
  - Latest 6.0.1_r43 (MOB30J)-DIRTY-DEEDS v-10.2
  - All Fixes from Omni are included
[COLOR="Blue"]2016/4/25[/COLOR]
  - Latest 6.0.1_r30 (MOB30D)-DIRTY-DEEDS v-10.1
  - All Fixes from Omni are included
  - Testing Mira cast with new Wifi library
  - BlueZ(5.39) update from bluez.org
[COLOR="Blue"]2016/3/29[/COLOR]
  - Latest 6.0.1_r22 (MHC19J)-DIRTY-DEEDS v-10.0
  - All Fixes from Omni are included
  - Fix the occasional flickering
  - Fix the crash in Display settings
  - Assign the default write permission to external sdcard
  - Fix the hardware decoder for video playback
  - Reinstate the SuperSU-2.52 as built-in root
  - PerformanceControl: Fix a potential crash when stated at the first time
  - BlueZ(5.38) update from bluez.org
[COLOR="Blue"]2016/3/7[/COLOR]
  - Latest 6.0.1_r13 (MMB29U)-DIRTY-DEEDS v-10.0
  - All Fixes from Omni is included
  - kernel: Full F2FS support
  - kernel: Double tap to wake (DT2W), with fine tune settings
  - PerformanceControl: DT2W settings in Advanced page
  - PerformanceControl: zh-rCN, zh-rHK and zh-rTW translations
  - Fixes in Display service for Ambient and Decouncing calculation
  - Include the missing APN from last build
  - Bluetooth: Latest Bluez stack with MM patches.
[COLOR="Blue"]2016/1/28[/COLOR]
  - Android 6.0.1_r10 (MMB29T) -DIRTY-DEEDS v-10.0
  - All kernel features as CM and Omni. OC, F2FS, uid_cputime, etc.
  - All Fixes from Omni is included
  - Fixes in Dirty Tweaks
  - camera fix for barcode and Google translate included
  - Include 3minit battery mod in SystemUI. (see post#2 for detail)
  - Bluetooth: Latest Bluez stack with MM patches.

Know issues: :(
1. Fast forward in video playback not working properly.
2. Adopted mode for ext. sd might not work.
3. May be more. Please report...



Testing ...


Planning ...

Downloads: :highfive:
 OmniROM:
  AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
  Dev-Host: OmniROM6
  mirror: 百度网盘 ***Request from China.

 CyanogenMod
  AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
  Dev-Host: cm-13.0
  mirror: 百度网盘 ***Request from China.

 DirtyUnicorns:
  AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
  Dev-Host: DU-10.0
  mirror: 百度网盘 ***Request from China.

 Gapps:  OpenGapps  DeltaGapps
 ** some Gapps might cause random reset and misbehaviour **

 To ROOT: download the latest recovery flashable ZIP from chainfire.eu
   Tested SpuerSU versions: Omni:2.49, 2.52, 2.65, 2.66  CM:2.49, 252
   DU is already rooted.

Source: :cool:
 github: https://github.com/danielhk?tab=repositories

Credits: :good:
 ** The OmniROM team who have such a good idea and their hardworks
 ** The CyanogenMod team who keep many devices alive!
 ** The DirtyUnicorns team's selflessness and persistance.
 ** All those donate and/or support me. Giving me the resources and reasons to carry on!
 ** The Bluez team who makes bluetooth possible for old devices!
 ** @Chainfire for the great SuperSU

Donations: :angel:
 
 
 
show.htm

 

Attachments

  • omni6-video-patch-21060118.zip
    1.1 MB · Views: 5,054
Last edited:

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,344
Hong Kong
Realme X2
Extra Informations

Background Info. & Tips: ;)
  • New approach for ext. SD and OTG  
    M auto-detect the external storage and mount it accordingly. For ext. SD, you may choose either Portable or Adopted mode. An adopted SD would act like the internal SD. When a SD (or USB OTG with an SD) is inserted, a notification will handle it. You might need a simple convertion first. If the card is originally FAT, FAT32 or EXT4, the content is most likely preserved. For obsolete format like exFat, the content will be erased.
    *** In any case, backup the content first.
    TIPS:
    1. Remove Portable SD card before reboot or power ON. Google doesn't have device with ext. SD. Limited support.
      If an ext. SD is inserted before boot, it might take longer to boot and sometimes a crash. Fixed!
    2. The performance of adopted mode depends on the performance of the ext. SD. At least a class 10 is recommended.
    3. In Portable mode, the mount point is automatically generated. You may browse its content from notification or Settings. 
      Update your file explorer (eg. ES) to latest if available.
    4. ** Some report that openGapps cause Adopted mode not working, you may try BaNK's (in DU's site) or others **
  • Things about Gapps
    Everyone knows that Gapps are those proprietary apps from Google. For custom ROMs to have them. Contributors pull those apps and supporting libraries form an existing (usually the latest model with latest version available) stock AOSP ROM. Pack them into a recovery flashable zip. It is up to that contributor to decide which apps to included.
    The question is "Why Gapps are so unfriendly to M?"
    After some digging, I found a reason. The SensorManager has changed. Some essential functions that "Old" blobs (even from KK or some LP) required are undefined now. Thus some blobs would fail to load. The most obvious one is gpsd. Even if they were loaded, some function were failed. Play service can't get the LOCATION permissions because it "thinks" GPS is missing.
    TIPS:
    1. Those apps are usually located inside the /system partition. Flashing a ROM would format the /system partition and required flashing the Gapps again. Some Gapps are in /data and would survive. However, "thanks" to the eMMC brick bug, our devices won't actually format the /system partition. Hence Gapps would survive in our device.
    2. A factory reset won't erase the Gapps but only their settings and data.
    3. Since it is pull from other devices. Resolution can be an issue causing crashes in some old devices.
    4. Gapps usually rely on Google services. Upgrading google services might affects some of the Gapps.
    5. Gapps and some system apps can be disabled/enabled in Apps settings now.
    6. ** Some report that openGapps cause Adopted mode not working, you may try BaNK's (in DU's site) or others **
  • BlueZ support for Marshmallow
    If you read the View attachment README.txt of BlueZ for Android. It states that Kitkat is fully functioning but some features are not yet or partial implemented in Android 5.0. Definitely more for 6.0. Socket (L2CAP & RFCOMM) is one of the partially supported. That means file transfer in Lollipop is not fully working now. Some devices with Bluedroid also face similar situation. During the porting, I found that 6.0 has change quite a lot. Some struct and functions are redefined. Some requests would crash in the Old HAL (Bluedroid too). I fixed a few things (eg. Handsfree protocol). May be still a few glitches but its usable. Let's hope for the best.
    TIPS:
    1. Devices would easier to connect when it is ON before the tab.
    2. During calls, the Bluetooth icon would appear but with no audio.
      You might need to press the Bluetooth button once to connect the audio to the Bluetooth headset.
    3. When audio is connected, press the button will end calls as usual.
    4. When audio is connected, volume keys would sync with the system volume.
  • F2FS (Flash friendly file system)
    F2FS is a "new" thing. It is include in the Linux 3.8 kernel in late 2012. As the name imply, it is friendly to NAND storages. Since there is no cylinder, head and sectors, a different way to handle it seems sensible. The solid state flash storage is non volatile storage which requires a "higher" voltage to write (or flash). There is a life limit for such action (over 100K flashes for SLC). The MLC (and then TLC, QLC) technology make it easier to multiply the storage capacity but shorten the life of it at the same time. Most of the eMMC are MLC (1k ~ 5k flashes) now. How to make use of all the cells equally is definitely essential for the life of the flash storage. F2FS take it into account so it is "friendly" to Flash memories.
    TIPS:
    1. To test F2FS, just convert the /cache partition first. If the kernel doesn't support it, it would just fail to boot. It would done no harm to your valuable data.
    2. Read only partitions (eg. /system) has no or little difference. For compatibility, most of the custom ROMs won't support it. No need to try.
  • Double Tap to Wake (DT2W)
    This feature was implemented in a few China made phones for sometime. Recently, there is a leak of this disabled feature in the Nexus6 kerenl. There are a few ports in the Nexus' kernels. I studied them for a while and decided to make a move. ElementalX's kernel for flo helps a lot. I finally port it to my Nexus7 and our Tab. To increase the reliability and avoiding false activation, I added two interfaces for bound area and duration between taps. It depends on the resolution of the touch screen to decide the optimum values.
    TIPS:
    1. If you have dirty flash from earlier version or DU, you need to clear data of Settings. and reset. Otherwise the Advanced page in Performance Settings might crash.
    2. The default bound between the taps is 30 pixels which is around the size of our finger tip. To avoid false activation (say inside a bag, etc.), you may make it smaller but it would required more accurate taps to activate.
    3. Similarly, the shorter duration between the taps would lessen the chances of false activation but you need a quicker action to activate. The default duration is now set to 50ms. Taps over this period would be ignored.
Q & A: :confused:
  • Q: How to flash?
  • A: NOTE! This is for user with experience:
    1. Latest TWRP (2.8.6.x or above) is required.
    2. Download ROM (+Gapps (+SuperSU)) and copy to the Sdcard (external or internal.)
    3. Backup data to external sd and keep in a safe place
    4. Reboot to recovery (Press [PWR] + [Vol+], Release [PWR] when Samsung Logo appear)
    5. Factory reset / wipe data
    6. Flash ROM (+Gapps and SuperSU if you want to ROOT)
    7. Reboot and wait for at least 10min. (Block mode not working for all devices. It might take longer for post setup) 
    ** If you flash Gapps separately, it would cause "SetupWizard" to crash and other issue. **
    Flash everything again at the same time. OR, see the fix in another Q&A below
  • Q: How to enable "Developer options" in Settings?
  • A: Follow the steps:
    1. Settings > About Tablet
    2. Hit "Build number" 7 times
    To restore the default state (Developer options hiding):
    1. Settings > Apps
    2. Select the app "Settings"
    3. Hit "Storage"
    4. Hit "CLEAR DATA"
  • Q: Why my PC can't see the Tab when USB is connected? 
  • A: With the USB cable connected, check the following:
    1. Make sure USB debugging is ON. Settings > Developer options > USB debugging
    2. Pull down the QuickSettings
    3. Hit the "USB file transfer" Notification.
    4. If Charging only is selected. Hit "Transfer files (MTP)" or "Transfer photos (PTP)".
    Still not working!
    1. Make sure the USB cable is OK
    2. With the cable connected. Turn USB debugging OFF. Settings > Developer options > USB debugging
    3. Turn USB debugging ON again.
    4. A dialogue will popup on the Tab's screen. Enable the checker box (which is the PC connected)
  • Q: Why can't I download anything with Browsers? 
  • A: M has a new stricter and wider permission settings.
     For security reason, "Dangerous" permissions are disabled. 
     It is up to the user to decide and assign afterwards.

    Futher info. of System Permission can be found HERE.
    To check the permission for each app:
    HTML:
    Settings > Apps > [the app] > Permissions
  • Q: How to fix SetupWizard crash of Gapps? 
  • A: As the above, It is the security again.
     The permissions for SetupWizard are "Dangerous" and disabled.  

    Note: For CM with Gapps, there will be two SetupWizards. "com.cyanogenmode.setupwizard" and "com.google.android.setupwizard". The one with the blue CyanogenMod icon is from CM. It's the one comes with Gapps crashed.
    1. Just flash ROM (+ SuperSU) only and set up the system first.
    2. Then flash Gapps.
    If SetupWizard crash after reboot:
    Method 1:
    3. You can still enter Settings via QS. There will be a short time slot after you press OK in the warning dialogue. A bit tricky but doable.
    4. Select "Apps" and select "show system" in the advance menu. (top right)
    5. Locate can select SetupWizard.
    6. Select "Permissions"
    7. Enable "Phone" and "Contacts" will stop the crash.
    OR
    Method 2:
    Your device is rooted and you know how to use adb. Use the following commands:-
    Code:
    3. adb shell
    4. $ su
    5. # pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
    The crash will stop immediately.
  • Q: How to fix Google Play service crashes? 
  • A: Again It's the security. Google Play service requires the permissions 
     ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION.
     BUT there is nowhere to set it. 

    Only a rooted device with adb can fix it:
    Code:
    1. adb shell
    2. $ su
    3. # pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION 
    4. # pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
  • Q: How to enable 3minit battery mod?
  • A: Follow the steps:
    1. Download V3.1 apps MinitBatteryResources and 3MinitBatterySettings
    2. Install both apps
    3. Reboot
    4. Launch 3MinitBatterySettings to setup (take a while to start)
    Note: The default size -20 is a bit too small, -5 is good enough for me ;) 
    _20160116_164706.JPG
 
Last edited:

golfinggino

Senior Member
Nov 23, 2011
1,389
143
burlington, on
Nice to see android 6 on this dinosaur lol- just flashed and a lot of restarts and crashes hoping they will be fixed with updates thanks for another rom option

Sent from my Xperia Z Ultra using XDA Premium HD app
 

scoobydu

Senior Member
May 16, 2005
480
44
Seems very useable when gapps are not installed, but with them I cannot get past the setup wizard crashing.

Tried other gapps with the same result.

Anyone get past this already?

Edit: Seems installing everything and then factory resetting lets me get further.
 
Last edited:

Espen96

Member
May 5, 2013
46
34
26
Bergen
Wow, I can't believe this device is still kicking! Even though I don't have mine anymore, it was my first android device. May it prosper
 
  • Like
Reactions: daniel_hk

uli-hh

Senior Member
Hi Daniel
I've installed your new rom to my P6200.
Screenshot_20151105-180724.png
The install process was as easy as usual. Flashed rom, g-apps and superSu in one turn.
The first boot took really a very long time (>10 min. SD was inserted). I was a little afraid that I was stuck at the boot-logo but finally the setup wizard appears. :highfive:
Setup went through without any problem. (except the known "SIM issue")
When I was trying to restore my backup from ext. SD with Titanium Backup I could not select ext. SD as usual.
Screenshot_20151105-180414.png
So I did a search within the whole device
Screenshot_20151105-180428.png
and the TI-backup folder was found at mysterious place
Screenshot_20151105-180351.png
After the restore of my apps and data I started ES file explorer and found that the mysterious place is my ext. SD with a new name: 6E12-D522 :confused:
Screenshot_20151105-180638.png
When I attach USB memory it apears like this:
Screenshot_20151105-180951.png
all the content is in one folder, so you have to open up this folder to find you folders and files on the stick (minor issue)
I was not able to send the screenshots to my google-drive via wifi.:confused:
I've had two unexpected FC till now.
Some times when leaving setting the apex-launcher needs some seconds to reload the app-icons.
Overall performance and handling is really good.
For a first experimental-release this is a great shot!! Thank very much Daniel.
I'm sure you will make marshmallow usable for our "stone-age" devices :fingers-crossed:
 
Last edited:

vinnity

New member
Jul 3, 2007
2
0
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
 

Harrison Le

Senior Member
Oct 30, 2015
224
45
Install Youtube take long time, have to cancell and reinstall then it ok but during playing youtube just have sound with black screen also not get simcard.
 

philipnzw

Senior Member
Jul 5, 2012
167
49
Viper4android not working .-. Might be the selinux mode thingy ,haven't tried changing that yet
Can't get play store to install apps,just gives error message

Tablet crashed when changing sd card to adoption mode (panicked), 16gb card became 16mb ,reformating using slimkat helped fixed that
Overall it's very usable and smooth ,can't wait for next build
 

yurius

Member
Apr 3, 2007
29
3
daniel_hk, thnx for your work! As i can feel, M running much faster, tnan 5.x.x - and thats really great.

Some issiues that i found
- video only shows in s/w mode in MX Player (no awesome player in developer options?)
- stock browser crashes on download
- Android terminal emulator crashes on start (may be this is app issue)
- seems that wi fi not stable, when playing video from samba share approx. every 10 min playback in mx player stopped. Fixing it by sliding left for a few seconds back
and last, that comes from 5.x.x (as i remember) - very long charging time with genuine samsung cable/adapter (as i remeber SkyHigh Kernel is quite faster), if it is possible to increase charging speed, that will be great!
 
Last edited:
  • Like
Reactions: philipnzw

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,344
Hong Kong
Realme X2
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
Have the same problem, except with MX-Player + Codec ARMv7.
Install Youtube take long time, have to cancell and reinstall then it ok but during playing youtube just have sound with black screen also not get simcard.

In my region, I can only access Youtube and Google services via VPN. Someone had set up a server for me to download the source. It is quite slow but working. I don't think I have the luxury and time to browse those...
Anyway, media codec seems not working yet. I think Omni team is working on it, I just don't want to repeat. I will take a look when official (or any other unofficial) is out.

Viper4android not working .-. Might be the selinux mode thingy ,haven't tried changing that yet
Can't get play store to install apps,just gives error message

Tablet crashed when changing sd card to adoption mode (panicked), 16gb card became 16mb ,reformating using slimkat helped fixed that
Overall it's very usable and smooth ,can't wait for next build

1. I'm not a gamer nor an active Youtuber. Can't help much. Let the experts discuss and share.
2. I had tested adopted mode with no problem. Yes, it is a bit lagging and might took a retry in reformatting. After that, there will be two partitions, one small and the rest would be internal.
M use a new approach to handle Sdcards. Our good old way of file browsing (eg. with ES) need to evolve. There is a link in post#2 which is the "detail" provided by Google... It might take some time to digest.

daniel_hk, thnx for your work! As i can feel, M running much faster, tnan 5.x.x - and thats really great.

Some issiues that i found
- video only shows in s/w mode in MX Player (no awesome player in developer options?)
- stock browser crashes on download
- Android terminal emulator crashes on start (may be this is app issue)
- seems that wi fi not stable, when playing video from samba share approx. every 10 min playback in mx player stopped. Fixing it by sliding left for a few seconds back
and last, that comes from 5.x.x (as i remember) - very long charging time with genuine samsung cable/adapter (as i remeber SkyHigh Kernel is quite faster), if it is possible to increase charging speed, that will be great!

1. See the above for video playback
2. I don't have problem in downloading with the included browser. Details please, to int. sd or ext. sd? which link? etc. It might be site related.
3. As before, I don't think I'm in the position to test third party apks.
4. What you described seems that it go to sleep and wake lock issue. MX might need an update for M.
5. This is another common question I don't want to answer. I'm not comfortable to compare nor pointing out who's right or wrong. Not long ago, someone think I ignored the fixes in S2 and keep on pressing and posting. Our mind is a funny thing. No matter how many time and whatever I said. I just can't change what someone think. Only if people willing to open their eye to see the fact. One man's candy can be the other's poison.:D

Nowadays, everything is efficiency oriented. People tends to pick a few keywords and think they get it. Only few would really read. I don't know how many people would read this but it's my habit to explain as clear as possible. ;)
For charging, I think it apply to all devices...
There were a few things we believed working. I can tell you those few "tricks" are all included in the kernel either before or after for years. After studied the specifications (from chip manufacturer not Samsung) of the chips inside our tab carefully, I can tell you it is not what we thought.
a. The boot loader firmware has a set of value for the chip. Something like current limit.
b. No matter how high the current is applying, the main decision is inside the battery's circuitry. To avoid "explosion", it would allow only the right amount of current to charge the battery at a specific temperature.
If the device is ON, yes, the consumption of the OS would account for the time to fully charged. It depends on how many apks installed and running, environmental aspects like wifi signals, carrier signals, temperature, etc. It is just too argumentative to "feel".
If it is OFF, the difference should be neglected. The boot loader firmware has its own set of value. No matter what inside the tab's memory, even without a kernel or ROM, it can still charge the battery. The kernel binary (which I already mentioned has the same "tricks") is account for showing the charging images and sensing the buttons etc. Yes, there are differences on the only few services (adb, screens, etc.) but it is simply neglectable.
The main aspect would be the age of the battery which account for how long and how fast it is charging. Just do an experiment. Flash different ROMs and time the differences.

Battery live is very poor. Even in fight mode cellular network is active. No deep-sleep:(
View attachment 3535470
Yes, the radio daemon crash because the ril blob is tooooo old. It would retry indefinitely even if you are in flight mode. It would be definitely a drain. The good news is that I think I found a fix. I'm working on it now. It would be the ultimate solution which I believe we can survive a few more generations. :D

To all:
This is a completely new OS. Some apks are not working as expected. When the time come, apks might have updates. In this experimental build, some features are not working yet. This is not the daily driver if you are looking for.
Thanks for the support and enthusiasm but no matter how many wants and hopes are there. No matter how many people mentioned how times times, I simply don't have the resource and time to fulfil them all. I appreciate the detail reports on issues which I miss or overlook. I'm humble to those pointing me out. Although only few people would really read, I'm polishing the presentation of my posts. I "hope" people would know what I'm doing. :)
 
Last edited:

p3dboard

Senior Member
Oct 20, 2013
1,003
616
@daniel_hk - the source revision attachments in the omni change log says it's missing when i try to open it.

Thanks for your hard work. I started on a slim marshmallow build, but it was missing a number of code patches in their base code
 
Last edited:

daniel_hk

Inactive Recognized Contributor
Nov 12, 2012
1,634
5,344
Hong Kong
Realme X2
@daniel_hk - the source revision attachments in the omni change log says it's missing when i try to open it.

Thanks for your hard work. I started on a slim marshmallow build, but it was missing a number of code patches in their base code

Yeah! I don't why it's gone :cyclops:
I have uploaded the attachment again. Thanks!
 
  • Like
Reactions: Harrison Le
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 65


    Here comes the Marshmallow!
    I don't want to waste too much time to maintain a few threads. From now on, I'll put all Marshmallow developments in this thread.
    Since Tab Plus is almost identical, it'll also be included here. All builds are unofficials. Please click the ROM images for details and read post#2 for extra infos.

    Release Note: :)
    2016/8/13
    This is the Android-6.0.1_r62 version of OmniROM-6. This might probably be the last Omni-6. ;)

    2016/8/4
    This is the Android-6.0.1_r62 version of DU-10.4. :D

    2016/7/29
    This is the Android-6.0.1_r52 version of CM-13.0. As N is coming, it might probably be the last CM-13.0.
    There were few reports on Gapps issues but again with no detail. I already mentioned many times that I can't access Google services locally. I tried once more on this new build via VPN and again I have no problem with that.
    1. I flashed the latest CM (20160729) + opengapps pico 20160722 + SuperSU 2.52 with the latest TWRP 3.0.2-0.
    2. After a factory reset and reboot, I completed the setup.
    3. I connected to a VPN and add a Google account.
    Everything went smooth as expected.
    The following are the screenshots:
    Screenshot_20160730-132605.png Screenshot_20160730-133601.png Screenshot_20160730-133233.png
    I had also done a battery life test:
    1. no sim card
    2. WiFi off after sleep
    3. Added a Google account.
    My 3 years old battery can standby over 2 weeks. Everytime I turn on the screen, WiFi connected normally.
    Here is the screenshot
    Screenshot_20160609-021420.png
    *** These are the minimal essential info. required for a report, nothing less.
    *** If you don't want to provide those, just don't post. You'll be ignored...
    ;)

    2016/7/7
    DU-10.3 (Android 6.0.1_r46) is out. Cheers! ;)

    2016/6/21
    This is the Android-6.0.1_r46 version of OmniROM 6. Cheers! ;)

    2016/6/9
    This is the Android-6.0.1_r46 version of CM-13.0. Cheers! ;)

    2016/5/25
    DU-10.2 (Android 6.0.1_r43) is out. Cheers! ;)

    2016/5/11
    Omni merged Android 6.0.1_r43. This is mainly an version update. Cheers! ;)

    2016/5/3
    This is the Android-6.0.1_r30 version of CM-13.0. The adaptive brightness and live display are fixed. The Bluetooh app is also patched to work with Bluez now. Cheers! :D

    2016/5/1
    Android-6.0.1_r30 required a patch to work with Bluez. You may find the patch here. ;)
    This patch would work for the latest Omni (20160414) and DU (20160425).
    HISTORY:

    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! :D

    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! :D

    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... :D

    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... :eek:
    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 :confused: 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


    Screenshots: :laugh:
    Screenshot_20151216-171540.png  Screenshot_20151216-171609.jpg  View attachment 3531073

    Change log: :victory:
    Code:
    [COLOR="Blue"]2016/8/13[/COLOR]
      - Latest 6.0.1_r62 (MTC20F) source from Omni
      - Add PowerHAL for exynos4
      - Add MM native support for double tap wake in Display settings
      - Bluez 5.41 update
    [COLOR="Blue"]2016/6/21[/COLOR]
      - Latest 6.0.1_r46 (MOB30M) source from Omni
      - Bluez update
    [COLOR="Blue"]2016/5/11[/COLOR]
      - Latest 6.0.1_r43 (MOB30J) source from Omni
      - Bluez 5.39 from bluez.org
    [COLOR="Blue"]2016/4/14[/COLOR]
      - Latest 6.0.1_r30 (MOB30D) source from Omni
      - Default RW permission for exteranl sdcard
      - Testing Mira cast with new Wifi library
      - Bluez 5.38 from bluez.org
    [COLOR="Blue"]2016/3/23[/COLOR]
      - Latest 6.0.1_r22 (MHC19J) source from Omni
      - kernel: update modem driver for i815
      - Settings: fix a bug which cause Advanced page crash at the first launch
      - SystemUI: fix a bug in status bar
    [COLOR="Blue"]2016/2/22[/COLOR]
      - Latest 6.0.1_r13 (MMB29U) source from Omni
      - kernel: fix a bug in DT2W
      - kernel: fix the occasional background process crash at cpu idle
      - PerformanceControl: fix the initial settings for CPUsettings
      - SystemUI: Fix the crash when 3minit battery apks not installed
      - Latest update from Bluez
    [COLOR="Blue"]2016/2/4[/COLOR]
      Source revisions: 
      - Latest 6.0.1_r13 (MMB29U) source from Omni
      - kernel: Double tap to wake (DT2W), initial commit
      - kernel: DT2W, fine tune settings
      - Settings: add DT2W settings in Advanced page of Performance Settings
      - Settings: add bound region and time between taps controls
      - Settings: Add DT2W translations for zh-rCN, zh-rHK and zh-rTW
      - Bug fix in video playback
      - Bluez: fix file send via bluetooth. (receive still fail)
    [COLOR="Blue"]2016/1/15[/COLOR]
      Source revisions: [ATTACH]3611268._xfImport[/ATTACH]
      - Latest 6.0.1_r10 (MMB29T) source from Omni
      - kernel: F2FS support
      - kernel: Fix a bug in F2FS
      - Rewrite samsung color format support
      - Fix rotation freeze after deep sleep.
      - To keep the data persist at reboot, PerformanceControl requries ROOT now
      - Add Power (screen off) Tile to QS. Short press:screen off, Long press:power menu
      - Include 3minit battery mod in SystemUI. (work with app from 3minit)
      - Bluez 5.37 update from bluez.org
      - DRM: low the security to Level 3
    [COLOR="Blue"]2015/12/29[/COLOR]
      Source revisions: [ATTACH]3592090[/ATTACH]
      - Fix the RIL libraries for i815, 
      - GPS fix with Dmitry's patch as in cm-13.0
      - Latest Nexus5 DRM blobs
      - Introduce the new OmniJaws
      - New boot animation and wall paper (seems not working for us)
      - Delay the init.d script to 99ApkPermissions 
      - Increase the time out of AOT compiler
      - New set of camera preview data for Tab-Plus
      - gcc 4.9 is used for kernel and platform
    [COLOR="Blue"]2015/12/16[/COLOR]
      Source revisions: [ATTACH]3578277[/ATTACH]
      - Latest 6.0.1_r3 (MMB29M) source.
      - Add 80ApkPermissions script to init.d
      - Add captive portal check switch in build property
      - Fixes in telephony to support 6.0.1
      - Add a few debug lines in camera HAL (for Tab-plus testing)
      - Fix a few minor bug in kernel
      - BlueZ update from bluez.org
      - Start Handsfree protocol without WB
    [COLOR="Blue"]2015/12/5[/COLOR]
      Source revisions: [ATTACH]3565823[/ATTACH]
      - Fix video recording in Camera
      - Fix video playback (a bug in colorformat)
      - Fix rotation stop after awake
      - Suport SAMSUNG LPM in libhealth. (Fix reboot at power off when charge/usb cable is plugged)
      - Merge Mali API 29 code to kernel driver.
      - Update to Mali API 29 blobs
      - A few patches in the kernel
      - First port of BlueZ 5.36 to M
      - Reinstate the BlueZ support in kernel and platform
    [COLOR="Blue"]2015/11/24[/COLOR]
      - Latest 6.0.0_r26 (MDB08M) source.
      - Triple check the RIL libraries for p6200 and t869
      - Patch in Camera HAL which fixed the torch in QS
      - Merge the Linux kernel source 3.0.y (3.0.101).
      - Disabled the Bluetooth backport for the time being. (Conflict with net)
      - Support for Samung LPM which avoid rebooting at power off (when charger or USB cable connected)
      - Include the GPS patch for the last build
      - Fix the Power management HAL.
      - Fix a few Omni features
      - Fix the glitches at rotation
    [COLOR="Blue"]2015/11/14[/COLOR]
      - New blob for RIL (binary hack from newer Samsung device)
      - RILClass: update the responses and include new requests
      - optimize build script to shorten the time of flash
      - Rewrite the Camera HAL
      - Fix some Omni features
      - Add GPU support to PerformanceControl
      - Samsung Color Format support for codec
      - Replace some text relocation blobs
    [COLOR="Blue"]2015/11/4[/COLOR]
      - Fix the external storage support
      - Support for  mode
      - Support for OTG sdcard
      - Fix the Camera
      - Add screenshot tile in QS
      - consolidate the boot menu
      - included the libemoji for Emoji factory
    [COLOR="Blue"]2015/10/27[/COLOR]
      - Omni source 6.0.0_r1 (MRA58K), alpha release
      - Fix build for Frameworks, Settings, PerformanceControl, Hardwares, etc.
      - Fix release tool to pass build
      - Fix boot loop in boot.img
      - Fix orientation and colorspace
      - Fix light sensor
      - Fix GPS
      - Add kernel uid_cputime support
      - Add boot menu

    Know issues: :(
    1. Transmit large file to server with ES file explorer would crash. For the time being, use other apk (eg. AndSMB, Astro, etc.).
      TO DO: Without the source of ES, nothing can be done.... *
    2. Mobiledata for i815 probably working now.
      TO DO: A shim library and a few patches with the blob. Can read the Baseband now. Waiting for report form i815 owner
    3. Fast forward in video playback not working properly.
    4. Adopted mode for ext. sd might not work.
    5. May be more. Please report.
    *** Number of asterisks indicate the importance and priority. ***



    Screenshots: :laugh:
    View attachment 3569154  Screenshot_20151209-151140.png
    Change log: :victory:
    Code:
    [COLOR="Blue"]2016/7/29[/COLOR]
      - Latest 6.0.1_r52 (MOB30R) source from CM
      - Add custom PowerHAL
      - Add native support for double tap wake in Display settings
      - BlueZ 5.41 update
    [COLOR="Blue"]2016/6/9[/COLOR]
      - Latest 6.0.1_r46 (MOB30M) source from CM
    [COLOR="Blue"]2016/5/3[/COLOR]
      - Latest 6.0.1_r30 (MOD30D) source from CM
      - Fix the adaptive brightness and live display
      - Bluetooth app: patch to work with Bluez
      - BlueZ 5.39 update
    [COLOR="Blue"]2016/4/5[/COLOR]
      - Latest 6.0.1_r22 (MHC19J) source from CM
      - Fix the occasional flickering for screen
      - Testing Mira cast with new Wifi library
      - Open source UMB library
      - Enable write permission for external sdcard
      - kernel: update modem driver for i815
      - PerformanceControl: fix a bug which cause Advanced page crash at the first launch
      - BlueZ 5.38 update
    [COLOR="Blue"]2016/3/15[/COLOR]
      Source revisions:
      - Latest 6.0.1_r22 (MHC19J) source.
      - All fixes in Omni6
      - Fix the Display service for Ambient and Decouncing calculation
      - kernel: A few minor fixes
      - PerformanceControl: Fix the crash of Highend Graphics in Advanced page
      - BlueZ update from bluez.org
    [COLOR="Blue"]2016/2/10[/COLOR]
      Source revisions:
      - Latest 6.0.1_r13 (MMB29U) source.
      - kernel: Double tap to wake (DT2W), initial commit (see post#2 for detail)
      - kernel: DT2W, fine tune settings
      - PerformanceControl: add DT2W settings in Advanced page 
      - PerformanceControl: add bound region and time between taps controls
      - PerformanceControl: Add DT2W translations for zh-rCN, zh-rHK and zh-rTW
      - SystemUI: fix a bug in 3minit battery which cause battery icon not shown
      - Fix video playback.
    [COLOR="Blue"]2016/1/22[/COLOR]
      Source revisions: [ATTACH]3618827._xfImport[/ATTACH]
      - kernel: fix a bug in F2FS
      - camera: fix the format for barcode and Google translate
      - Fix auto rotation. (Not working in the previous builds)
      - PerformanceControl: settings are persist after reboot now
      - DRM: low the security to Level 3
      - Include 3minit battery mod in SystemUI. (see post#2 for detail)
      - Bluetooth: Fix in l2cap settings. Files can be sent now but not received yet..
    [COLOR="Blue"]2016/1/6[/COLOR]
      Source revisions: [ATTACH]3601912._xfImport[/ATTACH]
      - Latest 6.0.1_r10 (MMB29T) source.
      - Add F2FS support in kernel
      - Modify gpsd blob to load libdmitry
      - Fix in sensor listener. (for rotation fail after deep sleep)
      - gcc 4.9 is used for both kernel and platform
      - Fix the RIL libraries for i815, 
      - Latest Nexus5 DRM blobs
      - Increase the time out of AOT compiler
      - Seperate set of camera preview and thumbnail data for Tab-Plus
      - BlueZ 5.37 update from bluez.org
    [COLOR="Blue"]2015/12/22[/COLOR]
      Source revisions: [ATTACH]3585427[/ATTACH]
      - Add libdmitry to fix Gps
      - Modify gpsd blob to load libdmitry
      - stlport build from source
      - New DRM blobs from other device
      - Add USES_LEGACY_ACQUIRE_WVM support to frameworks
      - Add old Parcel::writeBlob() definition to work with the old blobs
      - Add ApkPermissions script to init.d (to fix the permissions of Gapps)
      - Fix i815 data by shim library
      - exFat support for external sdcard (from CM)
      - BlueZ update from bluez.org
    [COLOR="Blue"]2015/12/10[/COLOR]
      Source revisions: [ATTACH]3571293[/ATTACH]
      - Latest 6.0.1_r3 (MMB29M) source.
      - Enable hot swap to disable the "SIM card added" pop up
      - Add captive portal check switch in build property
      - Fixes in telephony to support 6.0.1
      - Use original AOSP keyboard (CM's port crash on new Google service)
      - BlueZ(5.36) support for M
      - Start Handsfree protocol without WB
    [COLOR="Blue"]2015/11/28[/COLOR]
      Source revisions: [ATTACH]3563538[/ATTACH]
      - Latest 6.0.0_r26 ((MDB08M) source.
      - Patch in Camera HAL which fixed the torch in QS
      - All fixes in Omni6
      - Fix the Power management HAL.
      - Mali API 29 blob update 
      - Merger Mali API 29 source to kernel driver (r3p2-01rev4)

    Know issues: :(
    1. Transmit large file to server with ES file explorer would crash. For the time being, use other apk (eg. AndSMB, Astro, etc.).
      TO DO: Without the source of ES, nothing can be done.... *
    2. Mobiledata for i815 probably working now.
    3. Adopted mode for ext. sd might not work.
    4. May be more. Please report.
    *** Number of asterisks indicate the importance and priority. ***




    Screenshots: :laugh:
    Screenshot_20160128-232531.png Screenshot_20160128-232626.png Screenshot_20160128-232617.png
    Change log: :victory:
    Code:
    [COLOR="Blue"]2016/8/4[/COLOR]
      - Latest 6.0.1_r62 (MTC20F)-DIRTY-DEEDS v-10.4
      - Add custom PowerHAL
      - Add native support for double tap wake in Display settings
      - BlueZ 5.41 update
    [COLOR="Blue"]2016/7/6[/COLOR]
      - Latest 6.0.1_r46 (MOB30M)-DIRTY-DEEDS v-10.3
      - All Fixes from Omni are included
    [COLOR="Blue"]2016/5/25[/COLOR]
      - Latest 6.0.1_r43 (MOB30J)-DIRTY-DEEDS v-10.2
      - All Fixes from Omni are included
    [COLOR="Blue"]2016/4/25[/COLOR]
      - Latest 6.0.1_r30 (MOB30D)-DIRTY-DEEDS v-10.1
      - All Fixes from Omni are included
      - Testing Mira cast with new Wifi library
      - BlueZ(5.39) update from bluez.org
    [COLOR="Blue"]2016/3/29[/COLOR]
      - Latest 6.0.1_r22 (MHC19J)-DIRTY-DEEDS v-10.0
      - All Fixes from Omni are included
      - Fix the occasional flickering
      - Fix the crash in Display settings
      - Assign the default write permission to external sdcard
      - Fix the hardware decoder for video playback
      - Reinstate the SuperSU-2.52 as built-in root
      - PerformanceControl: Fix a potential crash when stated at the first time
      - BlueZ(5.38) update from bluez.org
    [COLOR="Blue"]2016/3/7[/COLOR]
      - Latest 6.0.1_r13 (MMB29U)-DIRTY-DEEDS v-10.0
      - All Fixes from Omni is included
      - kernel: Full F2FS support
      - kernel: Double tap to wake (DT2W), with fine tune settings
      - PerformanceControl: DT2W settings in Advanced page
      - PerformanceControl: zh-rCN, zh-rHK and zh-rTW translations
      - Fixes in Display service for Ambient and Decouncing calculation
      - Include the missing APN from last build
      - Bluetooth: Latest Bluez stack with MM patches.
    [COLOR="Blue"]2016/1/28[/COLOR]
      - Android 6.0.1_r10 (MMB29T) -DIRTY-DEEDS v-10.0
      - All kernel features as CM and Omni. OC, F2FS, uid_cputime, etc.
      - All Fixes from Omni is included
      - Fixes in Dirty Tweaks
      - camera fix for barcode and Google translate included
      - Include 3minit battery mod in SystemUI. (see post#2 for detail)
      - Bluetooth: Latest Bluez stack with MM patches.

    Know issues: :(
    1. Fast forward in video playback not working properly.
    2. Adopted mode for ext. sd might not work.
    3. May be more. Please report...



    Testing ...


    Planning ...

    Downloads: :highfive:
     OmniROM:
      AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
      Dev-Host: OmniROM6
      mirror: 百度网盘 ***Request from China.

     CyanogenMod
      AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
      Dev-Host: cm-13.0
      mirror: 百度网盘 ***Request from China.

     DirtyUnicorns:
      AndroidFileHost: GalaxyTab 7.7, GalaxyTab Plus
      Dev-Host: DU-10.0
      mirror: 百度网盘 ***Request from China.

     Gapps:  OpenGapps  DeltaGapps
     ** some Gapps might cause random reset and misbehaviour **

     To ROOT: download the latest recovery flashable ZIP from chainfire.eu
       Tested SpuerSU versions: Omni:2.49, 2.52, 2.65, 2.66  CM:2.49, 252
       DU is already rooted.

    Source: :cool:
     github: https://github.com/danielhk?tab=repositories

    Credits: :good:
     ** The OmniROM team who have such a good idea and their hardworks
     ** The CyanogenMod team who keep many devices alive!
     ** The DirtyUnicorns team's selflessness and persistance.
     ** All those donate and/or support me. Giving me the resources and reasons to carry on!
     ** The Bluez team who makes bluetooth possible for old devices!
     ** @Chainfire for the great SuperSU

    Donations: :angel:
     
     
     
    show.htm

    23
    Extra Informations

    Background Info. & Tips: ;)
    • New approach for ext. SD and OTG  
      M auto-detect the external storage and mount it accordingly. For ext. SD, you may choose either Portable or Adopted mode. An adopted SD would act like the internal SD. When a SD (or USB OTG with an SD) is inserted, a notification will handle it. You might need a simple convertion first. If the card is originally FAT, FAT32 or EXT4, the content is most likely preserved. For obsolete format like exFat, the content will be erased.
      *** In any case, backup the content first.
      TIPS:
      1. Remove Portable SD card before reboot or power ON. Google doesn't have device with ext. SD. Limited support.
        If an ext. SD is inserted before boot, it might take longer to boot and sometimes a crash. Fixed!
      2. The performance of adopted mode depends on the performance of the ext. SD. At least a class 10 is recommended.
      3. In Portable mode, the mount point is automatically generated. You may browse its content from notification or Settings. 
        Update your file explorer (eg. ES) to latest if available.
      4. ** Some report that openGapps cause Adopted mode not working, you may try BaNK's (in DU's site) or others **
    • Things about Gapps
      Everyone knows that Gapps are those proprietary apps from Google. For custom ROMs to have them. Contributors pull those apps and supporting libraries form an existing (usually the latest model with latest version available) stock AOSP ROM. Pack them into a recovery flashable zip. It is up to that contributor to decide which apps to included.
      The question is "Why Gapps are so unfriendly to M?"
      After some digging, I found a reason. The SensorManager has changed. Some essential functions that "Old" blobs (even from KK or some LP) required are undefined now. Thus some blobs would fail to load. The most obvious one is gpsd. Even if they were loaded, some function were failed. Play service can't get the LOCATION permissions because it "thinks" GPS is missing.
      TIPS:
      1. Those apps are usually located inside the /system partition. Flashing a ROM would format the /system partition and required flashing the Gapps again. Some Gapps are in /data and would survive. However, "thanks" to the eMMC brick bug, our devices won't actually format the /system partition. Hence Gapps would survive in our device.
      2. A factory reset won't erase the Gapps but only their settings and data.
      3. Since it is pull from other devices. Resolution can be an issue causing crashes in some old devices.
      4. Gapps usually rely on Google services. Upgrading google services might affects some of the Gapps.
      5. Gapps and some system apps can be disabled/enabled in Apps settings now.
      6. ** Some report that openGapps cause Adopted mode not working, you may try BaNK's (in DU's site) or others **
    • BlueZ support for Marshmallow
      If you read the View attachment README.txt of BlueZ for Android. It states that Kitkat is fully functioning but some features are not yet or partial implemented in Android 5.0. Definitely more for 6.0. Socket (L2CAP & RFCOMM) is one of the partially supported. That means file transfer in Lollipop is not fully working now. Some devices with Bluedroid also face similar situation. During the porting, I found that 6.0 has change quite a lot. Some struct and functions are redefined. Some requests would crash in the Old HAL (Bluedroid too). I fixed a few things (eg. Handsfree protocol). May be still a few glitches but its usable. Let's hope for the best.
      TIPS:
      1. Devices would easier to connect when it is ON before the tab.
      2. During calls, the Bluetooth icon would appear but with no audio.
        You might need to press the Bluetooth button once to connect the audio to the Bluetooth headset.
      3. When audio is connected, press the button will end calls as usual.
      4. When audio is connected, volume keys would sync with the system volume.
    • F2FS (Flash friendly file system)
      F2FS is a "new" thing. It is include in the Linux 3.8 kernel in late 2012. As the name imply, it is friendly to NAND storages. Since there is no cylinder, head and sectors, a different way to handle it seems sensible. The solid state flash storage is non volatile storage which requires a "higher" voltage to write (or flash). There is a life limit for such action (over 100K flashes for SLC). The MLC (and then TLC, QLC) technology make it easier to multiply the storage capacity but shorten the life of it at the same time. Most of the eMMC are MLC (1k ~ 5k flashes) now. How to make use of all the cells equally is definitely essential for the life of the flash storage. F2FS take it into account so it is "friendly" to Flash memories.
      TIPS:
      1. To test F2FS, just convert the /cache partition first. If the kernel doesn't support it, it would just fail to boot. It would done no harm to your valuable data.
      2. Read only partitions (eg. /system) has no or little difference. For compatibility, most of the custom ROMs won't support it. No need to try.
    • Double Tap to Wake (DT2W)
      This feature was implemented in a few China made phones for sometime. Recently, there is a leak of this disabled feature in the Nexus6 kerenl. There are a few ports in the Nexus' kernels. I studied them for a while and decided to make a move. ElementalX's kernel for flo helps a lot. I finally port it to my Nexus7 and our Tab. To increase the reliability and avoiding false activation, I added two interfaces for bound area and duration between taps. It depends on the resolution of the touch screen to decide the optimum values.
      TIPS:
      1. If you have dirty flash from earlier version or DU, you need to clear data of Settings. and reset. Otherwise the Advanced page in Performance Settings might crash.
      2. The default bound between the taps is 30 pixels which is around the size of our finger tip. To avoid false activation (say inside a bag, etc.), you may make it smaller but it would required more accurate taps to activate.
      3. Similarly, the shorter duration between the taps would lessen the chances of false activation but you need a quicker action to activate. The default duration is now set to 50ms. Taps over this period would be ignored.
    Q & A: :confused:
    • Q: How to flash?
    • A: NOTE! This is for user with experience:
      1. Latest TWRP (2.8.6.x or above) is required.
      2. Download ROM (+Gapps (+SuperSU)) and copy to the Sdcard (external or internal.)
      3. Backup data to external sd and keep in a safe place
      4. Reboot to recovery (Press [PWR] + [Vol+], Release [PWR] when Samsung Logo appear)
      5. Factory reset / wipe data
      6. Flash ROM (+Gapps and SuperSU if you want to ROOT)
      7. Reboot and wait for at least 10min. (Block mode not working for all devices. It might take longer for post setup) 
      ** If you flash Gapps separately, it would cause "SetupWizard" to crash and other issue. **
      Flash everything again at the same time. OR, see the fix in another Q&A below
    • Q: How to enable "Developer options" in Settings?
    • A: Follow the steps:
      1. Settings > About Tablet
      2. Hit "Build number" 7 times
      To restore the default state (Developer options hiding):
      1. Settings > Apps
      2. Select the app "Settings"
      3. Hit "Storage"
      4. Hit "CLEAR DATA"
    • Q: Why my PC can't see the Tab when USB is connected? 
    • A: With the USB cable connected, check the following:
      1. Make sure USB debugging is ON. Settings > Developer options > USB debugging
      2. Pull down the QuickSettings
      3. Hit the "USB file transfer" Notification.
      4. If Charging only is selected. Hit "Transfer files (MTP)" or "Transfer photos (PTP)".
      Still not working!
      1. Make sure the USB cable is OK
      2. With the cable connected. Turn USB debugging OFF. Settings > Developer options > USB debugging
      3. Turn USB debugging ON again.
      4. A dialogue will popup on the Tab's screen. Enable the checker box (which is the PC connected)
    • Q: Why can't I download anything with Browsers? 
    • A: M has a new stricter and wider permission settings.
       For security reason, "Dangerous" permissions are disabled. 
       It is up to the user to decide and assign afterwards.

      Futher info. of System Permission can be found HERE.
      To check the permission for each app:
      HTML:
      Settings > Apps > [the app] > Permissions
    • Q: How to fix SetupWizard crash of Gapps? 
    • A: As the above, It is the security again.
       The permissions for SetupWizard are "Dangerous" and disabled.  

      Note: For CM with Gapps, there will be two SetupWizards. "com.cyanogenmode.setupwizard" and "com.google.android.setupwizard". The one with the blue CyanogenMod icon is from CM. It's the one comes with Gapps crashed.
      1. Just flash ROM (+ SuperSU) only and set up the system first.
      2. Then flash Gapps.
      If SetupWizard crash after reboot:
      Method 1:
      3. You can still enter Settings via QS. There will be a short time slot after you press OK in the warning dialogue. A bit tricky but doable.
      4. Select "Apps" and select "show system" in the advance menu. (top right)
      5. Locate can select SetupWizard.
      6. Select "Permissions"
      7. Enable "Phone" and "Contacts" will stop the crash.
      OR
      Method 2:
      Your device is rooted and you know how to use adb. Use the following commands:-
      Code:
      3. adb shell
      4. $ su
      5. # pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
      The crash will stop immediately.
    • Q: How to fix Google Play service crashes? 
    • A: Again It's the security. Google Play service requires the permissions 
       ACCESS_FINE_LOCATION & ACCESS_COARSE_LOCATION.
       BUT there is nowhere to set it. 

      Only a rooted device with adb can fix it:
      Code:
      1. adb shell
      2. $ su
      3. # pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION 
      4. # pm grant com.google.android.gms android.permission.ACCESS_COARSE_LOCATION
    • Q: How to enable 3minit battery mod?
    • A: Follow the steps:
      1. Download V3.1 apps MinitBatteryResources and 3MinitBatterySettings
      2. Install both apps
      3. Reboot
      4. Launch 3MinitBatterySettings to setup (take a while to start)
      Note: The default size -20 is a bit too small, -5 is good enough for me ;) 
      _20160116_164706.JPG
    11
    On the 29th Dec Omni, I realized that anything related to gapps may cause soft reboots. Tried to install GTalk/Hangouts from PlayStore, soft reboot. Tried to use outdated YouTube app, soft reboot.

    I am still having trouble with Wifi not automatically reconnecting after a drop though. On previous android versions, I never have to manually reconnect to my AP and the wifi connection never drops even when at 1 bar.
    However, my current wifi connection will periodically disconnect and will never reconnect even at 3 bars. Seems to disconnect when tab is locked/sleep for a period of time.

    Anyone having something similar? Wifi apps do not really help much unless I have been using the wrong ones >.>

    Am on a P6800 though am not sure if it means anything.

    Rotationfix is really working. Have not had any problems and am happily uninstalling rotation control. :D

    Have not updated Omni6 for the F2FS though.
    Seeing all the hype up above but is there really much of a difference? I understand how it could be optimized for memory/performance but is it really that simple for our tabs? Based on a simple Google search, it is giving me an analogy of some sort like a comparison between a class 10 sdcard and a class 8. Well, that is how I see it. I might be wrong.

    On our tabs, is it a plus for redundancy to use F2FS? Still reading through some posts to understand it and still trying to figure out if its worth it on the tab.

    If anyone has done any benchmark tests or can enlighten me on this, I would appreciate it. Was just curious about it since it seems that some were waiting for it.

    Did you use 5G wifi?

    This is the best way, doing homework before trying.
    F2FS is not just for performance. I'll add the F2FS info. to post#2 later.
    Take a look if you have time. ;)

    oh my god! from time to time I come back to old 7.7 tab thread and every time I'm surprised to see you @daniel_hk are keeping alive this wonderful device ... thanks!
    I have a question: I remember that with AOSP build there was a problem with HDMI output which was not working and probably can not be fixed ... is this still true or do you have found a solution? After trying a lot of your old build for kitkat and lollipop I went back to stock rooted rom since I'm often using the tablet as tv box ... anyway, I'll try marshmallow as soon as possible!

    I have the same problem on my p6810 with the latest cm13, screen flicker occurs, not constantly but every few minutes. I have decreased the animation speed to 0.5 and this seems to have improved things. It's almost like it's not always rendering according to vsync frames. I have formatted /cache and /data to the new file system and that's working well.
    I don't have motivation for the HDMI yet. I have gathered some info. these weeks. The blobs are really ancient. There are 6 or 7 of them might require binary hack. I believe it is not really difficult.

    Frankly, my main concern is being relied on others to test. There were a few occasions proved that it is not really reliable. Just like the recent camera for Tab plus. A few minutes work took days to have feedback and weeks to finish. It's been weeks now, still no feedback for the mobile data of i815. :(
    I just can't control the schedule. Hours or days of work might become weeks or months.
    I understand that everyone has his normal life. Sometimes people would made promises and lost their interests and enthusiasm afterward. Excuses are easy to find but not for me. I just don't want to leave another unfinished work. Yeah, most people won't give a **** but I'm old school. I would feel shame.

    "Promises like a baby, easy to make, hard to keep, painful to deliver"
    9
    Hi Daniel
    I've problem with video playback
    When I play video on youtube and other app it show only black screen with sound
    Have the same problem, except with MX-Player + Codec ARMv7.
    Install Youtube take long time, have to cancell and reinstall then it ok but during playing youtube just have sound with black screen also not get simcard.

    In my region, I can only access Youtube and Google services via VPN. Someone had set up a server for me to download the source. It is quite slow but working. I don't think I have the luxury and time to browse those...
    Anyway, media codec seems not working yet. I think Omni team is working on it, I just don't want to repeat. I will take a look when official (or any other unofficial) is out.

    Viper4android not working .-. Might be the selinux mode thingy ,haven't tried changing that yet
    Can't get play store to install apps,just gives error message

    Tablet crashed when changing sd card to adoption mode (panicked), 16gb card became 16mb ,reformating using slimkat helped fixed that
    Overall it's very usable and smooth ,can't wait for next build

    1. I'm not a gamer nor an active Youtuber. Can't help much. Let the experts discuss and share.
    2. I had tested adopted mode with no problem. Yes, it is a bit lagging and might took a retry in reformatting. After that, there will be two partitions, one small and the rest would be internal.
    M use a new approach to handle Sdcards. Our good old way of file browsing (eg. with ES) need to evolve. There is a link in post#2 which is the "detail" provided by Google... It might take some time to digest.

    daniel_hk, thnx for your work! As i can feel, M running much faster, tnan 5.x.x - and thats really great.

    Some issiues that i found
    - video only shows in s/w mode in MX Player (no awesome player in developer options?)
    - stock browser crashes on download
    - Android terminal emulator crashes on start (may be this is app issue)
    - seems that wi fi not stable, when playing video from samba share approx. every 10 min playback in mx player stopped. Fixing it by sliding left for a few seconds back
    and last, that comes from 5.x.x (as i remember) - very long charging time with genuine samsung cable/adapter (as i remeber SkyHigh Kernel is quite faster), if it is possible to increase charging speed, that will be great!

    1. See the above for video playback
    2. I don't have problem in downloading with the included browser. Details please, to int. sd or ext. sd? which link? etc. It might be site related.
    3. As before, I don't think I'm in the position to test third party apks.
    4. What you described seems that it go to sleep and wake lock issue. MX might need an update for M.
    5. This is another common question I don't want to answer. I'm not comfortable to compare nor pointing out who's right or wrong. Not long ago, someone think I ignored the fixes in S2 and keep on pressing and posting. Our mind is a funny thing. No matter how many time and whatever I said. I just can't change what someone think. Only if people willing to open their eye to see the fact. One man's candy can be the other's poison.:D

    Nowadays, everything is efficiency oriented. People tends to pick a few keywords and think they get it. Only few would really read. I don't know how many people would read this but it's my habit to explain as clear as possible. ;)
    For charging, I think it apply to all devices...
    There were a few things we believed working. I can tell you those few "tricks" are all included in the kernel either before or after for years. After studied the specifications (from chip manufacturer not Samsung) of the chips inside our tab carefully, I can tell you it is not what we thought.
    a. The boot loader firmware has a set of value for the chip. Something like current limit.
    b. No matter how high the current is applying, the main decision is inside the battery's circuitry. To avoid "explosion", it would allow only the right amount of current to charge the battery at a specific temperature.
    If the device is ON, yes, the consumption of the OS would account for the time to fully charged. It depends on how many apks installed and running, environmental aspects like wifi signals, carrier signals, temperature, etc. It is just too argumentative to "feel".
    If it is OFF, the difference should be neglected. The boot loader firmware has its own set of value. No matter what inside the tab's memory, even without a kernel or ROM, it can still charge the battery. The kernel binary (which I already mentioned has the same "tricks") is account for showing the charging images and sensing the buttons etc. Yes, there are differences on the only few services (adb, screens, etc.) but it is simply neglectable.
    The main aspect would be the age of the battery which account for how long and how fast it is charging. Just do an experiment. Flash different ROMs and time the differences.

    Battery live is very poor. Even in fight mode cellular network is active. No deep-sleep:(
    View attachment 3535470
    Yes, the radio daemon crash because the ril blob is tooooo old. It would retry indefinitely even if you are in flight mode. It would be definitely a drain. The good news is that I think I found a fix. I'm working on it now. It would be the ultimate solution which I believe we can survive a few more generations. :D

    To all:
    This is a completely new OS. Some apks are not working as expected. When the time come, apks might have updates. In this experimental build, some features are not working yet. This is not the daily driver if you are looking for.
    Thanks for the support and enthusiasm but no matter how many wants and hopes are there. No matter how many people mentioned how times times, I simply don't have the resource and time to fulfil them all. I appreciate the detail reports on issues which I miss or overlook. I'm humble to those pointing me out. Although only few people would really read, I'm polishing the presentation of my posts. I "hope" people would know what I'm doing. :)
    6
    Installed 20150115 version for p6800 with Delta base gapp.
    1. I have reformated the data and cache partition to F2FS using TWRP . upon boot up, it mention that there is an encryption error.
    2. After flash the modified boot.img, the encryption error message goes away.
    3. Wifi is not working on this build. After flashing the RIL patch 3, phone function is working.
    4. Video playback - blank screen with sound only.
    5. DSP Manager - received message "Unfortunately, DSP Manager has stopped".

    6. Went back to the previous build for the time being

    Thanks for your new 6.01 rom. it makes the Tab 7.7 very responsive like new.

    1. The kernels are the same. You may require a few reboot to get the sdcard ready. I'll test it myself later. Need to backup the sdcard first (almost full...)
    2,3. You don't need the flash the boot.img earlier. Flash that would kill the Wifi. (Different modules for that boot.img)
    4. I'm checking the codecs now. Just forgot what I have done then.... :eek:
    5. I haven't gotten DSP work on M yet...

    Edit: I confirm that F2FS format for /data is not working now. That means my system didn't resume to the former state yet... :(
    May be its time to "begin again"....
    F2FS fixed kernels are uploading to host and mirror now.