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

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

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:
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!
The performance of adopted mode depends on the performance of the ext. SD. At least a class 10 is recommended.
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.
** 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:
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.
A factory reset won't erase the Gapps but only their settings and data.
Since it is pull from other devices. Resolution can be an issue causing crashes in some old devices.
Gapps usually rely on Google services. Upgrading google services might affects some of the Gapps.
Gapps and some system apps can be disabled/enabled in Apps settings now.
** 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:
Devices would easier to connect when it is ON before the tab.
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.
When audio is connected, press the button will end calls as usual.
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:
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.
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:
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.
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.
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.
Click to expand...
Click to collapse
Q & A:
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  
Click to expand...
Click to collapse

Thanks for your ROMS

Testing now
Not sure if placebo but its quite fast ,gonna try out doze

philipnzw said:
Testing now
Not sure if placebo but its quite fast ,gonna try out doze
Click to expand...
Click to collapse
Opening apps definitely felt quicker than 5.1.1

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

Thanks for the continued support

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.

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

Hi Daniel
I've installed your new rom to my P6200.
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.
So I did a search within the whole device
and the TI-backup folder was found at mysterious place
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
When I attach USB memory it apears like this:
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.
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:

Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound

vinnity said:
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
Click to expand...
Click to collapse
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.

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

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!

Battery live is very poor. Even in fight mode cellular network is active. No deep-sleep

Hope to have new build soon to experience

vinnity said:
Hi Daniel
I've problem with video playback
When I play video on youtube and other app it show only black screen with sound
Click to expand...
Click to collapse
uli-hh said:
Have the same problem, except with MX-Player + Codec ARMv7.
Click to expand...
Click to collapse
Harrison Le said:
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.
Click to expand...
Click to collapse
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.
philipnzw said:
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
Click to expand...
Click to collapse
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.
yurius said:
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!
Click to expand...
Click to collapse
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.
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.
uli-hh said:
Battery live is very poor. Even in fight mode cellular network is active. No deep-sleep
View attachment 3535470
Click to expand...
Click to collapse
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.
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.

@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

p3dboard said:
@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
Click to expand...
Click to collapse
Yeah! I don't why it's gone :cyclops:
I have uploaded the attachment again. Thanks!

Related

[ROM/DEV][CONTINUE] Unofficial CyanogenMod 7.2.0 "GalaxyMini" [11.11.2012]

Note: This port is 100% built from source, based on the work of subskype. All credits goes to him!
I try to maintain subskype's original project releasing a new version when will be sensible modifications into CM7.2 git tree
CyanogenMod 7.2.0 "GalaxyMini" Port
Latest release: mebitek [11 November 2012]
Latest Google Apps package: official: 20110828
Pre-requisites:
Your phone must have a Gingerbread bootloader installed (as it uses the 2.6.35 kernel & Gingerbread proprietary files).
Any version of ClockworkMod that supports EXT4 partitions. Unfortunately, the build supplied with ROM Manager doesn't seem to be compatible.
Recommended: ensure that you have a backup of your current ROM and user data.
Installation:
Reboot into ClockworkMod. You can do this via adb reboot recovery, or by choosing the Reboot -> Recovery menu if you are already using CyanogenMod.
If you are upgrading from a stock or custom ROM, you absolutely must perform a data wipe: Select wipe data/factory reset and confirm the operation. Note that you will lose all of your user data, so be sure that you have performed a backup. Otherwise, skip to the next step.
Choose the option install update from sdcard -> choose zip from sdcard. You will see the two (or three) .zip files in the list.
install:
The base package named update-cm-7.X-GalaxyMini-KANG-signed.zip
The Google Apps package, named gapps-gb-DATE-signed.zip
Once all packages are installed, you can now reboot
latest version
download version mebitek here
old versions
download version mebitek 01.10.2012 here
download version RC1 - v1.2 here
download version RC1 - v1.0 here
download version v0.7 here
dowload hotfix v0.6b: here
dowload release v0.6: here
dowload release v0.5d: here
dowload release v0.5c: here
hotfix for camera orientation: here (thx to squadzone)
dowload release v0.5: here
dowload keyboard size hotfix (it works with v0.3 and v.04): here
dowload release v0.4: here
dowload hotfix2 for v0.3b: here
download release v0.3b: here
download release v0.2: here
download release v0.1: here
download release v0: here
Latest Changelog:
Vmebitek - 11 Novemebr 2012
Totally recompiled froms scratch
Camera patch
fix some settings to impreve battery life.
mms - Port "Strip Unicode" feature from ICS branch into GB
cmparts - Apply selected render effect on boot.
Refresh whole screen after changing render effect.
Fix memory leaks due to long living references to InCallScreen activity
Allow SIP calls to be added as a contact from call log
Fix music resume after call.
Add simple caching to XML compilation
update transaltions
Vmebitek - 01 October 2012
Totally recompiled froms scratch
Camera patch
Contacts: o not allow intents to initiate special char sequence handling.
Contacts: Caller name is lost in caller log for SIP calls
Overhaul CMScreenshot.
DHCP renewal failing due to missing iprenew_tiwlan0 service
watchprops would go to 100% CPU after processing first change
Fix memory leaking in the VM
Fix file descriptor leak in read_num
free memory allocated by strdup
fix memory leaking
Fix typo in queue_property_triggers ident
Don't malloc between fork and exec
Fix invalid APN line for Bouyges Telecom.
Ignore 'Incoming call in background' option when the phone is docked
Include nickname and organization in T9 search.
Fix endless loop of mediascanner with some MPEG files.
Browser: Update search engines
Don't cache contact list and T9 characters longer than the dialer's lifetime.
When import vcards, make preferred numbers super-primary.
ActivityManagerService: stay away from zombie content providers
Added missing <include sys/resource.h> for gcc > 4.7.0
Calendar: Fixed alerts so that alerts for all-day events now fire relative to local time
UEventObserver runs its own thread, so make sure to trigger the volume change UI
Fixing gingerbread compiling and mms for non VM carriers
libaudio-msm7x30: TI FM Radio support
Increasing ringtone volume option
Settings: Use new Google apps
update File Manager 1.2 for Cyanogenmod 7.2
Make sure internal state is initialized when toggling network mode
Apply haptic feedback to all buttons, not just the sound button.
Fix occasional completely mute incoming call
Close notification view when swiping away the last notification.
update languages and translation
V1.2 - 01 May 2012
Totally recompiled froms scratch
Implementing Sunfire-related fixes
expand the build time GCC check to include 4.7.x
Kill off USB notification sound.
Make absolutely sure the keyboard is never shown over the dialer.
Bluetooth: Fixup problems with the SDP records
Fix call forwarding indication.
Don't cache toasts.
Fix for a Phone app crash related to multiradio operation.
gps: Set supl_host_set flag in loc_eng_set_server
GCC 4.7 now correctly implements the two-phase name lookup rules
Make PhoneToggler accept the same values as are configurable in the settings.
telephony: added support for samsungs realcall parameter needed for incall audio
audiosystem: support for samsungs isSeperatedStream()
dalvik: Obvious mix of = and ==
wireless: Never save ap_scan setting to config file.
Lockscreen : Update quick unlock summary
Quick unlock : Fix bug
Allow theming of framework UI elements.
policy: fix "Skip on security" functionality
Added T9 italian strings
Externalize symbol picker options to resources
PatternUnlockScreen: Battery status can be shown if desired.
Dialer: Fix initial state for t9 sort mode
ipsec-tools: racoon: introduce authentication method parameter
policy: implement Motoblur-like fingerprint tactile feedback
ADW: add sortable apps list for catalog setup.
Added a max SMS length option.
Add option to enable/disable the ICS rotation animation
update transaltions
V1.0 - 18 March 2012
Totally recompiled froms scratch
proprietary samsung firmware libs update to android 2.3.6 baseband S5570XWKTH/S5570XEOKT9/S5570XWKT4 (2012.02)
CM verrsion updated to RC1
Common: Updated translations
Common: T9 predictive Phone dialer
Common: Media player and recorder fixes for a number of corner cases
Common: Profile resets
Common: Assorted Wifi fixes
OMAP Common: Support for recent OMAP3/OMAP4 devices
Common: Control haptic in quiet hours
Common: Lockscreen updates and new styles
Common: Bluetooth MAP support
Common: ICS telephony fix backports
Common: Support for Bluetooth GPS dongles
Common: Better support for mouse and usb keyboards
Common: Fix timezone detection in Hawaii
Common: ICS Transition effects backport
Common: ICS Rotation effects backport
Common: Allow photo storage selection when possible
Common: Improved Calendar reminder options
Common: Fix color banding in Gallery while displaying 32bpp images
Common: ADB over network
Common: Improved AVRCP 1.3 compatibility
Common: Improved external keyboard and mouse behaviour on some corner cases
Common: Status bar battery icon configuration
Samsung Galaxy S GSM devices: Fix emergency dialing
Several devices: Fix device identification on Android Market
Backport "disappearing SD media" fixes from CM9.
Show PIN entry screen even if lockscreen is disabled.
Create Kineto-compatible AudioTrack::set and AudioRecord::set methods.
Cherry-pick WebKit r100677 to fix a rendering crash
Error handling in WebViewCore::contentDraw
Error handling for Network Plugin API getContext
v0.7 - 11 March 2012
Fix build date info against locales
policy: don't lock users out if they wipe their fingerprint database
add more CDMA SamsungRIL fixes.
Email: Enable user specified port for Exchange server.
CallFeatureSetting: only disable cellular specific options in airplane mode
improve transalations
CMParts: tr: Notification power widget mobiledata auto 2g/3g
wifi: move AP driver configuration in board flags
Use supplementary service notifications to display additional call info.
Gallery3D: always use orientation sensor for screen rotation
Fix battery charging detection in NotificationManagerService
change device specific icon (hdpi/mdpi), original one is 'blur'
Email: Fix STARTTLS handshake error in Email's SmtpSender class (GB)
Ensure that "*cover*" or "*front*" matched file has proper extension
Toolbox implementation of chown has a bad print
policy: do not count invalid fingerprint swipes as bad tries
Add build date to 'About phone'.
toolbox: prefer busybox dmesg
T9 Dialer: View contact on long press on T9 resuts
Add support for EXIF datetime on Qualcomm libcameras
ext4: Fix image generation when size is exact multiple of block size
Fix soft keyboard appearing on dialer under certain conditions.
Fixed Proprietary info feild skipping in Samuel Berube's voicemail notification
fix gps hook signali time (thx to h3llstorm)
v0.6 - 27 February 2012
framework totally compiled from scratch
fix music quality
LGEStarRIL: fix DST handling exception
landscape layouts for incall screen
modinfo: use ifdef block for android without-utsrel modules path
Fix screen hang after dismissing a landscape alarm.
Notification power widget mobiledata auto 2g/3g
Implement basic framework for fingerprint lockscreen
Settings for fingerprint
better RGB_565 support
v0.5d - 17 February 2012
camera orientation fix
fix battery drain (not really yet... battery life is improved in front of v0.5c)
framework updated
v0.5c - 15 February 2012
finally fixed camera orientation bug => not work will try to fix in next release
finally fixed camera sound shutter
Furtherly fix up notification swipe handling.
Fix entries of Digitel, Movistar, Movilnet (Venezuela)
Add notification type constants.
additional landscape layout for sim pin unlock
Fix display freeze happening when changing device orientation while screen is off
update transaltions
v0.5 - 13 February 2012
keyboard has default size
fix camera orientation (please provide feedbacks for that)
Support lapdock audio routing
Fix mDeskModeKeepsScreenOn logic
Add safety net for notification swipe handling.
Notification power widget mobiledata auto 2g/3g
Furtherly fix up notification swipe handling.
update transaltions
v0.4 - 09 February 2012
Unfreeze display even if screen is off
Gallery3D: Fix images being scaled incorrectly.
AbsListView: add option to disable scrolling cache
Improve scrolling cache (ported from ICS)
Music: Fix music widget transparency in landscape layout.
improve transaltions
v0.3b + hofix2 - 08 February 2012
finally fixed long press back button to kill foreground app. (thx to squadzone to point me)
more free ram (about 92mb)
video rec tweaks
3g data tweaks (improve download/upload speed)
Galledy3D: Fix images being scaled incorrectly.
Galledy3D: Fix banding for 32 bpp images
v0.3b - 06 February 2012
fix some build.prop (removed unused and fix syntax)
Make CyanBread the default theme
Don't animate rotations when screen is off
libgralloc and libcopybit updated
ICS transictions
Change proximity behaviour for devices w/ fixed keyboard
update busybox
Revert "Fix low battery warnings on lockscreen on some languages"
update translations
shutter sound fixed
v0.2 - 03 February 2012
sd card cache tweak (now 4096kb)
improve build.prop tweaks (thx to denzel09)
add FM radio app
framework update at 03/02/2012 (details)
FM: seek: respect upper and lower freq limits
impreoved translations
v0.1 - 02 February 2012
sd card cache tweak
low memory values tweak (v6 supercharge aligned)
build.prop tweaks
framework update at 02/02/2012
v0 - 01 February 2012 (subskype original settings)
fix typo in dutch translation
add blade lockscreen
add option to disable scroll cache
officialy merged fm bcm20xx chipset support
fix low battery warnings
gallery 3D banding for 32bpp fix
backport ICS transactions
lockscreen alignment
Source code :
here
Donations:
If you like my work, please feel free to click on donate button. It will be really appreciated! thanks
if you like my work please use thanks button and rate this thread
N.B. seems that antutu benchmark calculate wrong sd card speed. With SD tools I'm able to reach 11.5MB/s (writing) and 36.8MB/s(reading)
v0.6 + performance scrernshot (806Mhz, thx to galaxy mini)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
v0.4 + performance screenshot:
v0.3b + horfix2 permormance screenshot:
v0.2 performance screenshot:
v0.1 performance screenshot:
v0 performance screenshot:
Can i flash this rom without wiping data?
Cause i want to try it..grrr
Im using cm7.2 rc5.3 by squadzone
bluestricker_21 said:
Can i flash this rom without wiping data?
Cause i want to try it..grrr
Im using cm7.2 rc5.3 by squadzone
Click to expand...
Click to collapse
it is safe to wipe data.
You can backup your apps with Titanium Backup, sms with sms backup and export your contacts in the contacts menu.
I suggest to do a nandroid backup before wipe and flash the rom so you can easily restore all your device in just one click from recovery menu
Nice work
Just one thing, please upload to mediafire instead. Github is not an upload site. Its meant for source code only.
Thanks i will try it immidiately
nice
but NIGHLTY BUILDS will be releasing the pure and official CM7.2 for our mini
so i think that would be nicer
thanks for the effort here
the unit is 5570
not 5770
mediafire??
@mebitek
could you pls make a mediafire download link for this, i will give a try!!
solved its mediafire now ;-) got it in download
sevenfolds said:
nice
but NIGHLTY BUILDS will be releasing the pure and official CM7.2 for our mini
so i think that would be nicer
thanks for the effort here
the unit is 5570
not 5770
Click to expand...
Click to collapse
Great.. we will have an official cm7 soon..
Waiting for it but i will try this rom for a while
sevenfolds said:
nice
but NIGHLTY BUILDS will be releasing the pure and official CM7.2 for our mini
so i think that would be nicer
thanks for the effort here
the unit is 5570
not 5770
Click to expand...
Click to collapse
thank you for the errata corrige. I've change repository name.
Until CM7.2 will officially released I think that is a nice thing to mantain this kind of project, don't you think?
sevenfolds said:
nice
but NIGHLTY BUILDS will be releasing the pure and official CM7.2 for our mini
so i think that would be nicer
thanks for the effort here
the unit is 5570
not 5770
Click to expand...
Click to collapse
when and where i can find news?
mebitek said:
thank you for the errata corrige. I've change repository name.
Until CM7.2 will officially released I think that is a nice thing to mantain this kind of project, don't you think?
Click to expand...
Click to collapse
Yeah mantain this projekt
Sent from my GT-S5570 using xda premium
mebitek said:
thank you for the errata corrige. I've change repository name.
Until CM7.2 will officially released I think that is a nice thing to mantain this kind of project, don't you think?
Click to expand...
Click to collapse
sure man, no big problem
yes it's good to maintain this
it's good to have variations.
cm7.2 Nightly Build was released.
sevenfolds said:
sure man, no big problem
yes it's good to maintain this
it's good to have variations.
cm7.2 Nightly Build was released.
Click to expand...
Click to collapse
I cannot find it in http://download.cyanogenmod.com/
where is that night build in the official cyano site?
mebitek said:
I cannot find it in http://download.cyanogenmod.com/
where is that night build in the official cyano site?
Click to expand...
Click to collapse
not yet...he's referring to nightly builds by squad.
roofrider said:
not yet...he's referring to nightly builds by squad.
Click to expand...
Click to collapse
so it's squad mod one not pure cm7?
roofrider said:
not yet...he's referring to nightly builds by squad.
Click to expand...
Click to collapse
correct
mebitek said:
so it's squad mod one not pure cm7?
Click to expand...
Click to collapse
well saying squad mod is not exactly correct.
he's just using mods that have not yet been merged into the tree..most of it is still up for review. it'll will be part of vanilla cm7 once it's merged.
so this nighlty by squad is his usual rom with source update(nightly changelog) i believe(just like what u've done)..i have not tried it so i'm not very sure.
----edit----
sorry i cant really have a say on this as i have not tried the 'nightlies'.
ok wait....nightly builds by squad are pure but with using his device config.
and the experimental builds implement unmerged mods frm the cm gerrit.
roofrider said:
well saying squad mod is not exactly correct.
he's just using mods that have not yet been merged into the tree..most of it is still up for review. it'll will be part of vanilla cm7 once it's merged.
so this nighlty by squad is his usual rom with source update i believe(just like what u've done)..i have not tried it so i'm not very sure.
Click to expand...
Click to collapse
another correct
nice explanation dude!
wow very big thanks for you BROTHER !!! thanks for continue this cyano project from subpsyke,i like cyano from subpsyke,and i think i like you too keep up the good work !! please continue this project from subpsyke source

[ROM] TheROM - take it or leave it [stable: build 26 | exp: build 27]

TheROM - take it or leave it
Okay guys, as promised I am sharing the ROM I made for myself to suit my personal needs.
I prefer stability and smoothness over features - so it focuses on some core features I love but isn't overloaded with each and every possible option out there.
All features are carefully and cleanly picked into the ROM without the use of nasty hacks wherever possible.
Please read the FAQ at the end of the first post before using this ROM!​
​
If you appreciate my work on the LG Optimus 2x you can support me by donating!
I am doing this for free in my leisure time because I like working on Android stuff and helping others out.
You're not required to donate, but I highly appreciate a couple free beers or pizzas as a gratidue for my work.
To quote one of the most famous xda developers:
Chainfire said:
Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
Click to expand...
Click to collapse
I am nowhere near his usercount, but just imagine if every happy (and only those) user of one of my ROMs has donated 5€+.​
Important:
Let me explain the "take it or leave it" phrase from the title:
You got two options, either you like the ROM and use it as it is without any complaints, or you don't and use another one.
I made this ROM for myself and am sharing it to you as there's a broad interest.
But I am not interested at all in feature requests, ETA questions, silly bug reports(!), etc. etc.
If I derped something (e.g. a FC within the settings app) you can of course post about it.
But you have to a) do a full wipe and confirm the bug is still there, b) describe your bug in detail, c) post a logcat.
It is the ROM I personally use (or for the CM10.1 version: used), so you can talk about the ROM, but you don't get to ask about any changes.
If we're clear on the rules let's go to the fun part.
This thread is in the general section for a reason. As we're not going to discuss which features this ROM absolutely needs we got a whole thread to our liking.
Which means: It's meme time!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FAQ:
Read the FAQ carefully before asking any questions!
Okay, I know you said no feature requests, but I really need [feature xyz]!
Why should I try this ROM?
I want to try this ROM, can I just flash it and be good to go?
I have a question..
New: I have a question regarding bluetooth...
Listen, I'd like to know if you could ...
I will donate to you if you include my beloved feature:
This is a joke right?
Really, I just want to know when you're going to release the next update?
I don't like the way you're doing this thread!
TheROM
Okay, this ROM comes in two versions. CM10.1 and CM10.2 based.
The former is based on my work on CM10.1.
The latter is based on my work-in-progress CM10.2.
If you're new to the LG 2x then you should check both linked threads and read about the differences, bugs and features of these ROMs.
I just don't see a reason to have two threads for this ROM, thus I'm merging them together in here.
The CM10.1 ROM is deprecated, it's been the ROM I've been using until I made the switch to CM10.2.
I just share it here for those of you who might prefer it. So don't expect any further updates.
​
FEATURES / INFORMATION:
Only features I made or ported are listed here, nothing that's already in CM.
TheROM CM10.2:
Hybrid Engine (per app dpi / layout)
Halo 2.0
Additional hardwarebutton customizations
(like Screen off, open Torch, Power menu etc.)
Notification Brightness slider
Center Clock option
Text-only battery style
PreferenceDrawer in the Settings
Custom Carrier text
Advanced low battery options
My memory management option
Fixed performance menu for Tegra2
Option for all home screen widgets on the lockscren
notification drawer background & transparency
standard softkey vibration lowered
ships with the awesome kowalski kernel by pengus77
comes with my non-neon compatible mini gapps package
Option to use the external storage as default one
comes with bluedroid which means speedup bug and no BT phone calls possible
If I find some time I might try to include bluez, but right now I don't and bluedroid will stay in until further notice.
App Ops option in the settings (with PAs changes)
based on the newest CM10.2 sources
and loads of small stuff here and there I forgot to list
Differences in the depracted CM10.1-based version:
comes with an older Halo version (1.0)
ships a couple more hardwarebutton customizations (esp. custom app)
comes with bluez and is compiled with GCC 4.7 which means a) no speedup bug but therefore b) no BT phone calls
based on CM10.1.2 stable + custom picks of the nightlies
​
Download:
Get the ROMs here:
http://tonyp.basketbuild.com/index.php?dir=main/TheROM/
All ROMs are for the newbl - if you're using the oldbl use the converter (or wait for someone to upload the converted build).
Kowalski Kernel M1 rh and my non-neon compatible mini gapps are included.
Installation instructions:
CM10.2 (coming from another ROM than my CM10.2):
Do a full wipe. Do another reboot after the first boot. Don't *****.
CM10.1 (coming from another ROM than my CM10.1):
Do a full wipe!
Updating to a newer TheROM build:
Flash the ROM. Reboot. No wipes needed.
Do not update from any CM10.1 ROM to CM10.2 (full wipe it is!)
Known Bugs:
Do not ask about features on the known bugs list. They're known, there's no need for a reminder.
all CM bugs (no HDMI rotation etc.) are present - check the CM10.1 / CM10.2 threads for more details
This especially means that on CM10.2 bluetooth calls are not working!!
If this is a dealbreaker for you: move to a ICS / CM10 or my CM10.1 t-build ROM!
See this post for more details regarding the bluetooth situation.
Hybrid Engine: Sometimes changing the system dpi will produce a small layout error (an empty line below the statusbar).
Just do a reboot and it's gone
Credits:
TheROM contains features from the following ROMs.
I either ported them myself or rewrote them based on their inspiration:
CyanogenMod
[*]ParanoidAndroid
[*]Jellybeer
[*]SlimBean
[*]ChameleonOS
[*]PAC-man
A special thanks to these people:
pengus77 for his awesome kernel
arcee for his work on CM7 - CM10.1
spyrosk for the bootloader converter (and AIO toolkit)
all the guys helping out in the threads (which are too many to list)
Thanks for the people who provide me with buildbox access and free hosters:
xda
Korumera (xdafileserver.nl)
basketbuild
vadonka
goo.im
​
This Known Issues List
should prevent one-liner finding reports related to already known issues
should keep later disappointment from end-users of tonyp's theROM and clean CM 10.2
defines an everlasting unique identifier for each known issue. Use the identifier for simplified unambiguous communication. Please write e.g. "issue #2" if you want to refer to the silent blue-tooth call bug
should show possible workarounds, or, even better, should motivate discussions to fix the issue.
should neither let you imply that the issue will be fixed soon, nor that it is fixable at all! It is technically really hard to analyze, find and fix the root cause. Please never ask for an ETA! The community is aware of, and is of cause already unhappy (see e.g. this post) about these known issues.
will not cover issues that exist in only 1 or 2 intermediate builds of theROM and that are already fixed in the latest build. Please also consult change log by @[email protected]
Known Issues List as of 2013/12/28 (theROM build 22-26 resp. clean CM10.2 incl. 2013-12-13):
HDMI doesn't work
Workaround: use stock LG GB ROM (I don't know whether stock LG ICS works)
Calls from BT headset connect but are silent for caller and callee
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: not yet found; speculation: volume gain factor is set to 0 somewhere
Discussion: see e.g. post3, post2 , post1 issue b)
Mobile data counting doesn't work (blue arrows on mobile data indicator don't appear; e.g. Avast shows error message)
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: bug in Android 4.3 (inherited to CM10.2)!?
Discussion: see e.g. note 3 in post3, post2, post1, report to Google
Stock camera
takes heavily over-exposed pics with flash
Workaround: tap the screen first before you click the camera fire button; this will correct exposure parameters
crashes often, or produces crashes of Trebuchet and gallery
Workaround 1: use e.g. cam app ported for CM10.1 by feav; it provides also features like panorama pix missing in the stock cam
Workaround 2 (not fully proven): flash the gallery.apk from build 23; some say the stock cam works without crashes then
BT media playback speeds up after minutes to hours.
Fix: at least fixed in build 22 (I dont't remember the exact build)
Some apps (e.g. Candy Crush) crash with the KK in the RAM hack version
Workaround: flash the no RAM hack (norh) version of Kowalski kernel (KK) by Pengus77
Slow GPS fix. Cause: missing file \data\gps\lto.dat that is up to date too.
Fix: seems to be fixed in build 23; some issues with the fix have been reported; under investigation
Literature: xda forum thread2, [URL="http://forum.xda-developers.com/showthread.php?p=15271402#post15271402"]thread1[/URL]
Long lags after heavy filling and emptying the flash memory. Reboot does not help
Workaround: backup data partition, wipe it, and restore the backup
Root cause: kernel does not implement TRIM functionality that makes use of the SD/MMC ERASE (CMD38) command.
References: wikipedia TRIM, wikipedia TRIM#SD/MMC
Discussion: post4, post3, post2, post1
Mobile data mode keeps being disabled when switching airplane mode off
Workaround: either disable and re-enable data or toggle 2g/3g twice. In some rare cases these workarounds won't work and a reboot is needed
Root cause: yet unknown
Current time shown is that for GMT time zone instead of for your local timezone. Time shift is always in full hours.
Workaround 1: Reboot; normally this restores correct time display.
Workaround 2: Disable automatic time sync and install a time sync app
Workaround 3: If you'd like to keep using automatic time you should add "telephony.test.ignore.nitz=true" to your build.prop
Root cause: yet unknown
Discussion: post2, topic #3 in post1
Some apps always crash under theROM and they also don't work on stock ICS on P990. Some of such seem to be Viber, Instagram, etc.
Request: please report as soon as the app started working correction on a new theROM build.
Recommendation 1: Search in this thread if your app is known to be incompatible with theROM
Recommendation 2: Search the internet if your app is known to be incompatible with stock ICS on P990
Recommendation 3: Try your app on P990 under stock ICS
Rule: never post problems with your app in this thread if its incompatibility to theROM or ICS on P990 is already known!
Recommendation 4: Ask the author of your app for help
Workaround: Use your app on P990 under stock ICS, or on another phone. (sorry for bad news!)
Root cause: potentially missing NEON support by P990; many others possible
no FM radio
note: theROM builds from version 27 ship Kowalski Kernel 3.1 (instead of KK 2.6 M1). As this might solve old known issues and might bring new ones I decided to archive and hide the above list for builds up to version 26. The below list for build version from 27 starts as a 1:1 copy of the above. As I am not on build 27 yet, I am not able to bring in my own experience. Additionally I don't have the time to read and evaluate all posts regarding build 27+. Please notify me for necessary corrections and additions of the below list.
Known Issues List as of 2013/12/28 (theROM build from 27):
HDMI doesn't work
Workaround: use stock LG GB ROM (I don't know whether stock LG ICS works)
Calls from BT headset connect but are silent for caller and callee
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: not yet found; speculation: volume gain factor is set to 0 somewhere
Discussion: see e.g. post3, post2 , post1 issue b)
Mobile data counting doesn't work (blue arrows on mobile data indicator don't appear; e.g. Avast shows error message)
Workaround: use e.g. CM10.1 T-builds or ParanoidAndroid (PA) ROM
Root cause: bug in Android 4.3 (inherited to CM10.2)!?
Discussion: see e.g. note 3 in post3, post2, post1, report to Google
Stock camera
takes heavily over-exposed pics with flash
Workaround: tap the screen first before you click the camera fire button; this will correct exposure parameters
crashes often, or produces crashes of Trebuchet and gallery
Workaround 1: use e.g. cam app ported for CM10.1 by feav; it provides also features like panorama pix missing in the stock cam
Workaround 2 (not fully proven): flash the gallery.apk from build 23; some say the stock cam works without crashes then
BT media playback speeds up after minutes to hours.
Fix: at least fixed in build 22 (I dont't remember the exact build)
Some apps (e.g. Candy Crush) crash with the KK in the RAM hack version
Workaround: flash the no RAM hack (norh) version of Kowalski kernel (KK) by Pengus77
Slow GPS fix. Cause: missing file \data\gps\lto.dat that is up to date too.
Fix: seems to be fixed in build 23; some issues with the fix have been reported; under investigation
Literature: xda forum thread2, [URL="http://forum.xda-developers.com/showthread.php?p=15271402#post15271402"]thread1[/URL]
Long lags after heavy filling and emptying the flash memory. Reboot does not help
Workaround: backup data partition, wipe it, and restore the backup
Root cause: kernel does not implement TRIM functionality that makes use of the SD/MMC ERASE (CMD38) command.
References: wikipedia TRIM, wikipedia TRIM#SD/MMC
Discussion: post4, post3, post2, post1
Mobile data mode keeps being disabled when switching airplane mode off
Workaround: either disable and re-enable data or toggle 2g/3g twice. In some rare cases these workarounds won't work and a reboot is needed
Root cause: yet unknown
Current time shown is that for GMT time zone instead of for your local timezone. Time shift is always in full hours.
Workaround 1: Reboot; normally this restores correct time display.
Workaround 2: Disable automatic time sync and install a time sync app
Workaround 3: If you'd like to keep using automatic time you should add "telephony.test.ignore.nitz=true" to your build.prop
Root cause: yet unknown
Discussion: post2, topic #3 in post1
Some apps always crash under theROM and they also don't work on stock ICS on P990. Some of such seem to be Viber, Instagram, etc.
Request: please report as soon as the app started working correction on a new theROM build.
Recommendation 1: Search in this thread if your app is known to be incompatible with theROM
Recommendation 2: Search the internet if your app is known to be incompatible with stock ICS on P990
Recommendation 3: Try your app on P990 under stock ICS
Rule: never post problems with your app in this thread if its incompatibility to theROM or ICS on P990 is already known!
Recommendation 4: Ask the author of your app for help
Workaround: Use your app on P990 under stock ICS, or on another phone. (sorry for bad news!)
Root cause: potentially missing NEON support by P990; many others possible
no FM radio
Consider not flashing theROM in case you can't live with one or more of the listed open issues.
Please report any ideas, how to further analyze or fix the issue. Or please provide better workarounds.
The above list is to my best knowledge. I can neither guarantee it is correct nor it is complete. Please help to improve it.
Every bug is an issue. But there might be issues not caused by bugs (= errors in source code).
thanks to
@tonyp
@spyrosk
@pengus77
OLD BUILDS DOWN HERE :
"THEROM" OLD BOOTLOADER VERSION 26.2 CM 10.2
"THEROM" BUILD#3 OLD BOOTLOADER VERSION 26.2 CM 10.2
"THEROM "BUILD #4 OLD BOOTLOADER VERSION 29 AUG
"THEROM" BUILD #9 OLD BOOTLOADER VERSION
"THEROM BUILD10" OLD BOOTLOADER VERSION
"THEROM BUILD13" OLD BOOTLOADER VERSION
"THEROM BUILD15" OLD BOOTLOADER VERSION
"THEROM BUILD16" OLD BOOTLOADER VERSION
"THEROM BUILD17" OLD BOOTLOADER VERSION
"THEROM BUILD 18" OLD BOOTLOADER VERSION
"THEROM BUILD 20" OLD BOOTLOADER VERSION
"THEROM BUILD 21 OLD BOOTLOADER VERSION
"THEROM BUILD 25 OLD BOOTLOADER VERSION Thanks @dcr-NI (first conversion)
if someone is also interested in the experimental version, please check for the link below: These two builds are not exactly same, please see which suits you more and give feedback to @tonyp accordingly.
"THEROM CM10.2 - exp-opt OLD BOOTLOADER VERSION
Thanks and enjoy guys
Changelog TheROM - take it or leave it
Changelog build 27:
Ships with the awesome kk 3.1 bcmdhd alpha 15 by @pengus77.
Big thanks to @hjunii - without him this wouldn't be possible.
added option & quicksettings tile to enable/disable Halo
reverted my netd tethering hacks, they were bcm4329 specific.
I do not know if tethering works with bcmdhd, yet - feedback required
re-enabled wifi optimizations by default (they were incompatible with bcm4329, so i had disabled them)
in case you notice any problems (which you shouldn't) go to settings - wifi - advanced and untick it.
Changelog build 26:
merged CM10.2.0 stable codebase
merged all TheROM translations pull requests
Changelog build25:
fixed Stock Camera
cyanogen has merged in some Features which our camera blobs don't support anyways, so I've rolled them back
merged upstream
I believe this should fix the ThemeChooser some people posted here, at least I've seen a commit regarding that on Gerrit.
Please provide feedback.
Changelog build 24:
fixed the brightnessslider to only show when enabled
merged CM10.2 RC1
ships with a customized KowalskiManager by @wfd which automatically enabled auto hotplug as well
Changelog build 23:
added auto downloading the lto.dat file (for gps assistion data). Hopefully this brings up GPS back to the CM10.1 standards (at least after the first fix aka TTFF).
It's enabled by default, but will only update the file via WiFi by default (check the new option at Settings - Location access)
Properly enabled GPU accelleration.
I've found out that our device didn't fully utilize hardware accelleration. The reason is our low RAM - and enabling hwa takes about 8mb.
But with a GPU as powerful as ours I think those 8mb are well spent, we'll see how it turns out, make sure to post feedback.
In a first quick test the UI does seem more responsive.
Note that this is NOT equal to the "Force GPU rendering" option in the developer section! This one should stay off, as apps that for various reasons do not use GPU rendering shouldn't get forced into it.
enabled 2nd core auto hotplug by default. This will hopefully get rid of the plug-in BSODs of people not reading the threads (and thus not enabling the option at the KowalskiManager).
updated Torch overlay (this does hopefully fix the missing torch widgets some people had - please post feedback)
updated the OpenGL version. I have no idea how and if we'll notice that.
Thanks @DJNoXD for sending me a pull request.
removed the CMUpdater which slipped in under my nose.
I've slapped in a new more generic bootanimation, courtecy of +Dima Skvarskyi
Changelog build 22:
-Os buildflag optimizations
(smaller modules loaded into the RAM means more free RAM available to the phone)
synced to CM10.2-M1
Changelog build 21:
merged upstream
(3 weeks of CM10.2 patches and updates - didn't particularly check them, if you notice something new post it here)
included Google Maps (v7.3.0) by default
(as Google removed Tegra2 compatibilty for v7.0+)
reverted the Camera Wrapper for now, I am not convinced about it's usefulness and want to try it without for some time again.
Changelog build 20:
It's mostly identical to build 19, I just merged upstream and included the new translations (see below).
A couple days ago I read a tip somewhere to use -Os instead of -O2 when compiling arm modules.
So I just made another exp build to try this - you can find it labeled as "exp opt" (experimental optimization) in the download directory.
In theory the exp build should have a slightly worse performance (if noticable at all) but more free RAM which could help our low RAM phone (if noticeable at all).
Oh and I've included the translations I got sent (Spanish, French, Russian, Portuguese BR & PT):
https://github.com/tonyp/TheROM-translations/commits/master
Changelog build 19:
It's basically an upstream merge - but CM fixed the Camera image being "stuck" after taking a photo, which is the last bug that I wanted to see fixed before calling it the next stable.
Changelog build 18:
Quickmemo support
As @Firtecy already posted he fixed the Quickmemo apk to work with CM10.2.
Thus I re-added the Quickmemo support into the framework.
I've recoded it with a better, adaptive implementation. Now you'll only have the Quickmemo entry in the Buttons settings when Quickmemo is actually installed - if not it will be completely hidden.
Flashable zip download here: http://tonyp.basketbuild.com/index.php?dir=main/TheROM/addons/
To open it you got two options: press vol- and vol+ simultaneously or assign the button at Settings - Buttons.
added a new bootanimation.
Thanks to @vviper for creating it!
replaced statusbar icons with the one from PA (which are a little lighter)
removed the Statusbar Transparency "always" option
Settings - buttons FC fix + another minor memory leak fix + merged upstream
Changelog build 17:
Network Location Toggle
Custom System Animations
Fixed a bunch of FCs & brought back Storage Settings content
merged upstream (Camera Launcher QS Tile etc.)
Changelog build 16:
removed ActiveDisplay again
disabled listview animation by default
You can turn it on at Settings - TheROM. I think they're quite fun to play around with!
merged upstream fixes
Changelog build 15:
Statusbar Transparency
Active Display re-added (I've disabled the proximity sensor properly now - it only gets used in the pocket mode now)
Still this does drain some battery when you get lots of Notifications. I'll look into creating a widget to toggle it on and off.
ListView animations
To show off and for the lulz it's enabled by default - you can disable (or change) it at TheROM settings.
I've added a a quick option to the Notification Drawer style options to restart the SystemUI.
I've been annoyed by the fact that I either had to reboot or use an external app.
changed default dpi to 213
(you can change back to the stock 240 at TheROM settings - hybrid)
merged upstream
(but removed the CMAccount, me no likey)
Changelog build 14:
Implemented the RIL_UNSOL_LGE_RESTART_RILD response.
This has been reported as missing by @gios_ some time ago here.
I'm not sure if the implementation is correct, I've adaptoed it from the P880.
We'll have to test and see if it changes anything for those who still have data drops every now and then (for me they seem fixed since kk 126).
(Note: This isn't related to the no signal after airplane mode bug, which you usually can solve easily by double tapping data in the QuickSettings (= disable and enable it)).
Replaced PerformanceControl with the KernelControl app by @Beene.
If you encounter any bugs make sure to report them to him and post your feedback about the app in his thread.
Merged upstream.
One of the changes is the integration of CMs PrivacyGuard into App Ops - called Privacy Guard 2.0.
You'll find it at Settings - Security - Privacy Guard.
Unfortunately the longpress on an item (where you could fine tune your settings in theory) isn't working yet (FCs), will get fixed soon.
Update: here is an updated Settings.apk which will solve the FC for those who need access to App Ops.
Needs to be pushed to /system/app. Then longpress the app in the Privacy Guard options.
Changelog build 13:
removed Active Display for now
(fixes the battery drain)
Changelog build 12:
cleaned some commits, especially Active Display
It works as expected for me - hopefully now for everyone else as well.
Additionally it's a "make clean" build, I assume the android version update broke something here in the last one.
fixed some logspamming
I've discovered a minor bug in the Processor settings in the Performance menu.
Thus I disabled it - to compensate it I included an updated PerformanceControl app again, which gots some decent additions compared to the old version
I removed ViPER FX again as I discovered you can just get it from the PlayStore
Don't worry, it'll be in English once you install it
restructured the TheROM Settings. I've got a PM from someone who wanted to translate it to other languages, this makes it easier.
You can download the strings here
After translating the file move it into the correct subfolder for your language and post it here, then I'll include it.
Changelog build 11:
I got great news. I don't know if someone remembers, but ages ago in my PA ROM I had experimented with hacking the framework and changed some ADJ values to protect the launcher from redrawing.
One shouldn't just change the values (that's what the SuperCharger does), as that would break androids default memory management, thus I re-arrenged the code in the ActivityManagerService to reflect those changes back then.
I just had a look at my old code and figured out a way better and way cleaner method to hook into that.
I've just compiled my testbuild and it seems to work. It's not yet ready, just a test if my theoretical concept works.
I want to introduce an option for that, where you can control the intensity. By the end of next week I will have a bit more time, then I'll expose an option in the settings.
My current idea is to call it "Prevent launcher redraws" with the levels "disabled", "moderate", "needtothinkofsomething" and "extreme".
Currently extreme is hardcoded.
I've uploaded the build to my TheROM folder if anyone wants to try it out. Please give feedback if you notice an improvement.
With extreme it'll be quite hard to get it killed, as only perceptible apps (like playing music) will be more important.
I've switched around between Google+, Boat Browser and the Reader+ app and I didn't manage to kill the launcher
Edit: good, opening webpages with loads of images in the browser does kill the launcher. We don't want to have it unkillable (keep in memory), when the system needs the ram it should be possible to get it.
It's a lot cleaner than the hacky way the Supercharger does to accomplish the same goal.
The supercharger hacks into the framework and changes the ADJ values directly - unfortunately these are directly accessed in the ActivityManagerService.java which causes some unwanted sideeffects with the default android memory management.
I'm just modifing the ADJ value at runtime.
Additionally what I really don't like with the Supercharger: It's prioritizing the Launcher above perceptible and even visible apps.
Killing the music player while listening to music or killing visible elements instead of the launcher when the system needs memory? That's insane imo.
To prevent confusion: visible apps are not identical to the foreground app - but could be some elements visible behind an overlay. Would still look bad if those suddenly dissappear.
Edit: I've decided to just brand it as build 11.
Additional changelog: Android 4.3 JLS36G merged
Changelog build 10:
- added Active Display options from ChameleonOS
- added notification drawer background options and transparency (requires a reboot to apply)
- QuickSettings: option to open the apps in floating mode ("in Halo") on longpress
- RAM usage circle on recent apps
- cherrypicked some memory leak fixes from various sources
- fixed some FCs
- fixed (?) the Trebuchet FCs (at least I can activate the searchbar again)
- merged upstream
Changelog build 09:
Based on the idea of alok.tari clicking the clock in the statusbar dropdown will open Timely if it's installed.
(Longpressing it will always open the clock app you set as default).
Then I reverted the dalvik low memory initializing, I suspect that to be related to some of the slowdowns. The system will use ~6mb more RAM again, but it might be worth it, we'll see.
Additionally I merged upstream of course - I've seen some fixes for headset plug-in (which fixes a bug if you don't have a music player app installed) and Trebuchet, I guess these will fix the issues reported here.
I will say it again: CM10.2 is in nightly status - which means there will be bugs every now and then in the sources.
Let's hope CM will try to build stable releases soon again, as soon as those are out the amount of new bugs will decrease.
I won't have the time to look into individual issues up until the end of this month.
I just quickly made this build for myself (and am sharing it here with you).
Changelog build 08:
- new options for Halo (ninja mode, ping etc.)
- ViPER FX replaces DSPManager
- back to the ramhack kernel (M1) - I just missed the additional RAM it gives which results in more Launcher redraws etc.
- Cyanogenmod account (check CMs G+ page for details)
- Trebuchet: Support for custom icons per shortcut
- merged upstream
Changelog build 07:
- notification sound bug fix while playing media
- enabled backlight button brightness options at Settings -> Buttons
- reverted gps.tegra.so to the one official CM10 and CM10.1 use (this fixes all GPS problems for me)
- included Kowalski M1 norh kernel
- merged upstream (loads of bugfixes from CM)
Last but not least I tried something highly experimental - I decreased(!) the playback buffer as I want to know if this has an impact on A2DP playback.
Unfortunately I don't have my BT headset at hand, so you guys need to test it.
> Is BT audio (listening to mp3s) still working?
> Does the audio still speed-up?
Additionally I added some missing bluetooth configurations which might or might not increase it's stability.
Changelog build 06:
Gosh I just hate bugs, so I just had to push out a quick fixup build
I fixed the SystemUI FCs (this has been a bit nasty!), the Bluetooth share FC after booting and @Firtecy fixed his disappearing brightnessslider after rebooting.
(you can push the Bluetooth.apk to the clean CM10.2 ROM to fix the bluetooth share FC there as well).
Changelog build 05:
I've added the Notification BrightnessSlider, ported by @Firtecy (thx!).
Additionally some other small fixes I stumbled across + I removed the QuickMemo option again for now - it only works for CM10 and CM10.1 until someone ports it.
Changelog build 04:
I've added the following hardwarekeys button actions to the ROM:
- Screen off
- Open Power menu
- Toggle Last app
- Toggle Torch
- Take Screenshot
- Quickmemo (this is optional, you need to use my Quickmemo installer)
The CM10.1 ROM had some more options (like custom app, re-assign the back key), but that would have required more work and time than I can currently spend).
The important ones are in now (I consider Torch and Powermenu/Screen off extremely useful).
Oh and in CM10.2 you got the sweet "double tap home action".
Google keyboard updated to v1.1
Trebuchet loosing icons should be fixed
Changelog build 03:
Hybrid Engine \o/
Focal removed - it's buggy and takes 12mb of space
Extract it from my CM10.2 ROM if you need it
Donation menu moved to the buttom to get it out of the way
Some new stuff for Trebuchet , including the option to use icon packs
Oh and the apk now takes about 6 instead of the former 12mb
Some small fixes here and there
Changelog build 02:
I have pushed a small bugfixing update online: cm-10.2-TheROM-20130826.2-tonyp.zip
I just did some quick workarounds which certainly isn't perfect, but fixes the FCs for now:
1.) I removed the SetupWizard.apk. The PreferenceDrawer Settings app is causing problems with it. I will fix it properly when I find the time, but the Wizard isn't really needed anyways.
You will just have to manually go to Settings - Accounts and add your Google account now after a full wipe.
2.) I have removed the two SDCards from the storage menu (it now only contains the option to use the external SD as default one).
I tried some quick fixes but they didn't work and I really gtg, so this will do for now. Again I will properly fix it when I get more time.
If you absolutely need access to the menu for something (although I don't know what this could be) you should be able to use the Settings.apk from my CM10.2 build for that.
I've hidden old changelogs to shorten the post. You have link to every original post/changelog from tonyp...
angel_boulevard said:
every day you bring us to new exciting..many many thank to you @tonyp..your rom is priority for me
P/s:a question.do any plan gapps 4.3 which google now working ?
Click to expand...
Click to collapse
Google now works in every ROM he puts out, I found that when you restore your apps your have to let everything instal [including google play services], uninstall google now and reinstall and it should work.
harucrux said:
Google now works in every ROM he puts out, I found that when you restore your apps your have to let everything instal [including google play services], uninstall google now and reinstall and it should work.
Click to expand...
Click to collapse
read again this is cm10.2 which one with mini gapps not working google now
Its working for me with the steps in the post above.
---------- Post added at 05:21 AM ---------- Previous post was at 05:12 AM ----------
angel_boulevard said:
read again this is cm10.2 which one with mini gapps not working google now
Click to expand...
Click to collapse
Its working for me with the steps in the post above.
Just couldn't stop laughing reading the FAQ
An awesome Rom and an awesome thread.
Thanks a lot for your hard work, we really appreciate it:thumbup::beer:
Sent from my HTC One using xda app-developers app
Dig bick! xD
Enviado desde mi LG-P990 usando Tapatalk 2
[FONT="<font><font>Comic Sans MS</font></font>"]Thanks for the new ROM, (again XD).
Keep it up!!.
Enjoy your holiday.
Greetings.[/FONT]

			
				
Thx 4 all Tonyp ! Downloading now...
EDIT : is possible to update from CM 10.2 by Tonyp 20130824.1 ???
Great work Tonyp thank you for everything!!
Going to buy you a beer!!
Since this is your personal ROM could you give us the settings and values you use or recommend?
Sent from my LG-P990 using Tapatalk HD
Where will you post changelog from now on since there are like 5 topics? i see new build but cant find changelog?
thanks
PYCON said:
Thx 4 all Tonyp ! Downloading now...
EDIT : is possible to update from CM 10.2 by Tonyp 20130824.1 ???
Click to expand...
Click to collapse
ya..no problem
I converted CM10.1 version for oldbl, flashed it and it works perfect. I'm currently uploading it, it will take about half an hour, if anyone wants to download it. Many thanks tony, I will donate as soon as I get my paycheck.
edit: here is the link https://dl.dropboxusercontent.com/u/11122462/cm-10.1-TheROM-slap-20130730-tonyp-oldbl.zip
sad to be the onliest guy, which have settings error crash after install.
I can't expect any help from TonyP (I can understand), anyone can help of the other users?
I do full wipe, install cm10.2 version, boot, the first I do is a reboot, and after next boot I choosed the language eng (us) and ok. then I got everytime settings error. then crash to language chooser......
all good now!
packyman said:
sad to be the onliest guy, which have settings error crash after install.
I can't expect any help from TonyP (I can understand), anyone can help of the other users?
I do full wipe, install cm10.2 version, boot, the first I do is a reboot, and after next boot I choosed the language eng (us) and ok. then I got everytime settings error. then crash to language chooser......
Click to expand...
Click to collapse
Try 4 WIPES !
Wipe Cache + Wipe Davilk + Wipe Data ( Factory ) + Wipe System ( Rom ).
Flash THE ROM e retry...

[ROM][5.1.1_r34][p6800/p6810](6April2016-Build1.8)SlimLP 5.1.1-.beta.0.15-UNOFFICIAL

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SlimRom is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and Gerrit.
Code:
/* #include <std_disclaimer.h>
*
* Your tablet's warranty is now void.
* This is a custom ROM developed by p3dboard.
* You are flashing this on your Samsung Galaxy Tab 7.7 at your own peril.
* I am not responsible for hard bricks, damages to SD Cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* I would definitely help you out if you are stuck somewhere, provided that you give
* me clear details of the mishap.
* Don't ask for ETA's cause there is a thing called "LIFE" outside XDA.
*/
SlimLP is currently in beta stage, some settings are already in place, much is still missing and would come with time. Stay tuned!
I am also new to development, so not as experienced as Daniel, and I also don't have a lot of extra time, so I'll do what I can, and fix what I can as I learn over time. But I wanted to contribute something new, and from Daniels survey, Slim was the second most popular rom after Carbon.
WHAT'S INCLUDED: (This is just a standard blurb, some of these SLIM extra's are not in their Beta yet)
Android Lollipop
Slim Center
Slim Launcher
Slim File Manager
Slim Heads Up
The Real Dark Slim User Interface
SlimPIE (inspired by ParanoidAndroid's PIE with a light touch of Slim)
Smart Card Service
Adaptive Backlight
Adaptive Brightness
Smart Lock
Privacy Guard
Sounds Tweaks(Audio FX and Music FX)
Status Bar Tweaks
Battery Saver Mode
Removed Bloatwares
Notification Reminder/Snoozer
Drawer Shortcuts
Lockscreen Shortcuts
Custom Quick Settings Tiles
Improved Performance
Camera - True View
Camera - Smart Capture
and Much More!
WHAT'S WORKING:
Camera
Video Recording
Wi-Fi
Bluetooth
ADB
Proximity Sensor
External SD Card
Internal SD Card
Video Playback
Speaker
Airplane Mode
RIL(Mobile and Data Network)
Compass - Can require calibration before being reasonably accurate (moving tablet around in a figure 8 a few times) - Might be a way to recalibrate this?
Automatic Brightness Sensor
GPS
POSSIBLY WORKING - TESTING REQUIRED:
Mobile Hotspot (can someone with a p6800 tell me if it works for them?)
BUGS/NOT WORKING:
Wifi Driver Bug that can reboot (ES Explorer Direct Send between two devices)
QS Torch Tile (Quick Settings Torch)
Touch Keyboard at initial boot - you need to either not flash GAPPS immediately or cancel the Setup with GAPPS flashed, then go into SETTINGS -> LANGUAGE&INPUT -> Current Keyboard and then turn on Hardware Input - After that the AOSP keyboard works - need to figure out how to fix this.
HOW TO INSTALL:
1. Download the ROM and the GApps and place them on your SD Card/Internal Storage.
2. Reboot tablet into TWRP recovery.
3. Wipe data, cache(factory reset), dalvik/art cache and system.
4. Flash the ROM and the GApps.
5. Reboot System. (First boot takes 5-6 minutes. Be patient.)
UPGRADING: If you are upgrading from a previous SlimLP build (not Kit kat Slim rom's, as you will get some issues)
1. Download the ROM, place it on your SD Card/Internal Storage.
2. Reboot tablet into TWRP recovery.
3. Flash the ROM
4. Reboot System.
SOURCES:
Daniel_HK's GitHub
SlimRoms Website
Google+
My code change notes - Download "Slimlp Changes to compile.txt" - How to compile after you have read and understood Daniels Instructions on compiling Rom's - read - read - read - something I didn't and don't always seem to do
CREDITS:
SlimROMs Team
@daniel_hk
and others I may have forgotten.
DOWNLOADS AND CHANGELOG IN THE SECOND POST
XDA: DevDB Information
SlimLP 5.1.1 by SlimRoms, ROM for the Samsung Galaxy Tab 7.7
Contributors
@p3dboard
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Galaxy Tab 7.7 (p6800,p6810)
Based On: AOSP
Version Information
Status: Build #1.8
Latest Build Release Date: 2016-04-06
Created 2015-09-15
Last Updated 2015-10-28
Change Log and Downloads
Slim Gerrit - Slim Rom's change log
4 April 2016
SlimLP Beta 0.15 - Build #1.8 - Build Date 20160406 - Download ROM from this URL
- Updated Source Code to Beta 0.15 (Patch Level is up to February 2016 in Security - Possibly this is the last update Slim might make for Android 5.1.1, CM 12.1 sources have been updated to April 2014, but not Slim so far)
- P6800 & P6810 builds completed (just the NoZram version)
- Added Daniel's Performance Control app, but it errors out when going to the Battery tab, I'll leave it in their incase anyone wants to use the CPU / Governor controls - but if you want to tweak memory, use another app like Trickster Mod from the play store.
- Returned Davlik Memory settings back to stock in this build, as if you don't have too many apps installed that run background services, you can open apps that use larger Ram values.
I decided to recompile a newer build as I wanted a Rom with a more recent security patch level that also had Google Play Movies working, Android 6.0 currently has issues the the L3 DRM blobs. It's still got the same old issues as mentioned in the first post with workarounds as above - Touch keyboard, and the QS Flashlight not working, along with the reboot bug if you try to transfer data over Wifi using Es Explorer. But apart from that its pretty stable.
28 Oct 2015
SlimLP Beta 0.10 - Build #1.7 - Build Date 20151028 - Download ROM from this URL
- Updated Source Code to Beta 0.10
- Making two version of the build, one with zRam and one without - you can choose which one you feel performs better
- Updated RIL libraries for p6800 from Daniels latest CM 12.1 build (October 2015 build)
- p6800 rom's uploading now for Build 1.7, zRam and no-zRam version
- The no zRam version still supports zRam but its not turned on by default. If you have the app Trickster Mod from the playstore, (there's probably others) you can turn the zRam off any time you want to while running the rom. If you turn it off and then back on in Trickster Mod however, the new zRam partition is only 10% of the memory, which is smaller then the 256mb zRam I am turning on at boot.
- P6810 Zram build uploaded, uploading non-zram p6810 rom version now, compiling p6800 rom.
- P6810 beta 0.10 compile completed (no zRam version), uploading, compiling p6810 zram build. Once this finishes building, i'll start the p6800 build
- Synced SlimLP Beta 0.10 source code, starting compile of P6810 rom
- I'll make two builds of each for the next rom, one with Zram turned on and one without.
- I still haven't had time to look at the Keyboard issue or the QS torch icon, got to many things on at the moment - so just doing source code updates
14 Oct 2015
SlimLP Beta 0.9 - Build #1.6.2 - Build Date 20151014 - Download ROM from this URL
- Added missing blob libsec-ril.so file for p6800
- Added a 256mb zram swap partition (cm12.1 i9100 nightly just implemented this as they said it can help with low memory situations, so I've added it to see if it helps us at all - give me feedback, we can always turn it off).
@4:05pm - p6800 build is uploaded.
@3:35pm - p6800 build complete, checked that libsec-ril.so was in the /system/lib folder. Uploading now (about 30min it should be there)
@8:44am - build 1.6.2 for p6810 with 256mb zram uploading now. I am building the p6800 rom now.
@8:25am - I just discovered I missed adding /system/lib/libsec-ril.so to the p6800 build (builds 1.6 and 1.6.1) - so stick with 1.5.1 until I fix this on the p6800, so Mobile services won't be available. I'll recompile the rom for the p6800 today.
13 Oct 2015
SlimLP Beta 0.9 - Build #1.6.1 - Build Date 20151013 - Download ROM from this URL
- New Stagefright security patch and October 1st Android Security patches (see Slim Gerrit changes for today for the latest list of changes)
- Bug in this build: P6800 rom missing RIL blob - mobile / data won't work
@6:43pm - p6810 build completed, uploading now.
@4:55pm - p6800 build 1.6.1 compiled, uploading now. Compiling the p6810 build now.
@4:00pm - i just noticed that the slimlp source just received the new stagefright security fix, i've synced the new source code updates and am compiling build 1.6.1, it also has the other Google security updates for October. Building p6800 rom now.
SlimLP Beta 0.9 - Build #1.6 - Build Date 20151012/13 - Download ROM from this URL
- Sources updated to SlimLP Beta 0.9
- Bluetooth built using Daniels new Bluetooth packages that allow Bluedroid and Bluez to co-exist
- Daniels USB-OTG update (from his sources)
- Bug in this build: P6800 rom missing RIL blob - mobile / data won't work
@3:08pm - p6800 build is up.
@2:20pm - p6800 build 1.6 compile completed. Uploading now (should be about 30min)
@8:23am - p6810 build 1.6 is uploaded
@8:20am - I'm uploading the p6810 build at the moment, then I'll start compiling the p6800 build
12 Oct 2015
- I've just downloaded SlimLP Beta 0.9 source code and sync'd Daniels latest device tries, starting on compile for the p6810 (Android 5.1.1_r20)
- I'm also going to test adding persist.sys.debug.multi_window=true to /system/build.prop - which might only be a Marshmallow (Android 6.0) setting, but I'll see if it works in 5.1.1_r20 of SlimLP Beta 0.9 source code
- I'm also going to test building Daniel's updated Bluetooth Package from his Github that allows it to co-exist with Bluedroid Bluetooth, rather then removing it.
- I haven't had any time to look at the Torch QS tile or the keyboard fault in the last two weeks, eventually I'll get onto those.
1 Oct 2015
SlimLP Beta 0.8 - Build #1.5.1 - Build Date 20151001 - Download ROM from this URL
- Modified /system/build.prop Davlik values again based on some more testing. dalvik.vm.heapgrowthlimit=64m. Previous build 1.5 tends to be laggy when launching multiple apps. You can test Build 1.5 and 1.5.1 and decide which settings give better performance if you like. If you know how to modify build.prop with root access, you don't need to reflash the rom, just set the Build.prop values.
@11:00am - p6810 build also uploaded.
@10:20am - p6800 build uploaded. p6810 build uploading now.
@9:17am - p6800 build compiled. Uploading. Compiling p6810 build now.
@8:00am - I think the new Davlik values are a bit excessive. I think increasing to dalvik.vm.heapgrowthlimit=64m, instead of dalvik.vm.heapgrowthlimit=100m, provides better responsiveness, but still enough for background apps like facebook (which uses around 60m of ram). For example, with the 64m value, opening a hyperlink from Gmail in Chrome works nicely, but at 100m, it's very laggy. My previous builds had this value set at 48m.
I think these values are better - I'll put a build 1.5.1 up soon, for those who want to try the different values (or you can manually set it yourself in Build.prop if your comfortable).
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
30 Sept 2015
SlimLP Beta 0.8 - Build #1.5 - Build Date 20150930 - Download ROM from this URL
- Updated Device Tree's from Daniel, Mobile Hotspot should be fixed for p6800 users
- GPS fixed
- Modified /system/build.prop Davlik values based on Article about Ram and Davlik settings, seems to be giving better performance, Games like Asphalt 8 seem to be smoother, more Ram seems to be generally available.
@7:14pm - p6800 rom uploaded
@6:34pm - p6800 build completed, uploading now, should be there in 30min
@6:15pm - P6810 Build #1.5 is uploaded. P6800 build still compiling..
@6:10pm - playing with Facebook installed in the background, dalvik.vm.heapsize=256m is more friendly for Facebook (dalvik.vm.heapgrowthlimit=100m is what helps Facebook to run more smoothly as a background process) in that games like Asphalt 8 are still playable with the 256m value, rather than dalvik.vm.heapsize=320m. But dalvik.vm.heapsize=320m / 384m is better for Real Racing 3 on High detail level, medium and low detail are fine with 256m.
@5:30pm - finished p6810 compile, uploading p6810 rom. Compiling p6800 rom now.
@3:35pm - doing a recompile of the p6800/p6810 with the adjusted Davlik VM settings, after which I will upload the rom's
@3:30pm - I finished my Davlik memory testing, I'm going with these values for my Build 1.5, a bit larger for the dalvik.vm.heapsize, as games like Real Racing 3 benefit from the larger value, and probably the Chrome Web browser does as well. The article recommended dalvik.vm.heapsize=174m, which is probably better if you have lots of smaller apps, but I'll optimize for some bigger apps using dalvik.vm.heapsize=320m. The dalvik.vm.heapgrowthlimit=100m seems to have given back more base memory, I can get over 460m of free Ram at times now.
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=320m
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
@8:35am - Test Build 1.5 - GPS works - so Non-Pie blob support is working again! Just testing the new Davlik memory settings now.
@8:00am - p6810 build 1.5 test build completed, if it's working ok I'll upload it as Build 1.5, otherwise I'll have to investigate why the Non-Pie support is not working.
29 Sept 2015
- 7:50pm - Starting build 1.5 for p6810 - will test to make sure GPS is working before doing p6800 build.
-I've manually updated the Bionic libraries with the Non-Pie support, as the Bionic libraries in SlimLP Beta 0.8 had more changes to them then just the non-pie support additions from the previous library which Daniel had given me, which was basically the same Bionic Library as SlimLP Beta 0.7 with the Non-Pie additions.
- Found interesting article on Davlik Heap values and ART https://01.org/android-ia/user-guides/android-memory-tuning-android-5.0-and-5.1 - I am going to test build my next one with their recommended settings to see the difference in performance (they say this benefits facebook as well due to the way it uses memory).
28 Sept 2015
- Looks like Daniel pushed another change to danielhk/proprietary_vendor_samsung_smdk4210 for the Hotspot after I did the Build 1.4 yesterday - https://github.com/danielhk?tab=activity - so I think that when I compile Build 1.5, this will hopefully fix the hostpot as well. I
- Build's 1.3 and 1.4 have issues with GPS again. I will have to do a recompile, it seems like the non-pie support was not enabled for GPS in those builds. Builds 1.1 and 1.2 the GPS works fine.
27 Sept 2015
SlimLP Beta 0.8 - Build #1.4 - Build Date 20150927 - Download ROM from this URL
- Updated Device Tree's from Daniel, Ambient Sensor should be fixed
- Mobile Hotspot doesn't seem to be fixed
- GPS has broken (non-pie support) - It has on my p6810 - will have to do a recompile for Non-Pie support that got missed some how
@10:15pm - The compile with CONFIG_KEYBOARD_SEC_DOCK=m or CONFIG_KEYBOARD_SEC_DOCK=n failed due to the fact that this causes other issues with the Kernel code. The code would need some adjustments to make this work for us. Anyway, I'll keep on investigating trying to turn the initial value to on for the Hardware switch in the Language and Input settings error. I checked Daniels omnirom build, and he's not turning on the hardware switch, so he must be specifically enabling the Touch Keyboard in the code even if a hardware keyboard is listed as present (I have seen some old code examples of people doing this, but some of the variables are not present in the SlimLP code - so I can't just copy their examples without finding the rest of the additional code needed).
@10:00pm - I got a reply from a Galaxy Tab 2 developer, he told me how they overcame this same issue, they got the commit included into Cyanogenmod to make the Keyboard Dock driver a module, so for anyone who needs it, the module can be started as an init.d module. I am doing a compile now to see if this fixes the keyboard driver, if so I'll make it build # 1.5...
http://review.cyanogenmod.org/#/c/83499/
espresso10: build KEYBOARD_SEC_DOCK as module Our sec_keyboard driver does not properly unregister the input device when no dock is detected, which makes the system believe that a physical keyboard is present at all times, which prevents the software keyboard from being shown. Some user own a Keyboard-Dock and meight miss the ability to use the dock if it gets disabled completely. Building it as module gives the user the ability to add a simple init.d script to start the module at boot if they need it.
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p6800_defconfig
Code change CONFIG_KEYBOARD_SEC_DOCK=y -> CONFIG_KEYBOARD_SEC_DOCK=m
/kernel/samsung/smdk4210/arch/arm/configs/cyanogenmod_p6810_defconfig
Code change CONFIG_KEYBOARD_SEC_DOCK=y -> CONFIG_KEYBOARD_SEC_DOCK=m
@9:41pm - p6800 build compiled, uploading now.
@7:47pm - p6810 build compiled and uploading, building p6800
SlimLP Beta 0.8 - Build #1.3 - Build Date 20150926 - Download ROM from this URL
- SlimLP Source code updated to Beta 0.8
- GPS has broken (non-pie support) - It has on my p6810 - will have to do a recompile for Non-Pie support that got missed some how
@3:04pm - p6800 build 1.3 uploaded. P6810 build 1.4 commenced.
@2:35pm - resetting Code base and Resyncing Daniels Device Library changes for Build 1.4 (Hotspot fix and Ambient Display fix)
@2:30pm - P6800 SlimLP Beta 0.8 build finished, uploading now (build 1.3)
@ 8:00am - P6810 SlimLP Beta 0.8 build finished and uploaded. Building P6800 rom. (My Rom build # 1.3)
- I've just looked at Daniels new Omnirom Change Log for 20150926 build and his new sources (which came out just after I started this new build) fixes the Wifi Hotspot and the Ambient Display issues. Once the first build of Beta 0.8 is compiled, I'll resync my Sources to get his updates and then build 1.4, which will include these fixes.
26 Sept 2015
5:30pm - I've just updated my SlimLP code base to Beta 0.8, and am recompiling my p6810 build. I'll leave it compile tonight and compile a p6800 build after that.
Next week I'll keep on tracking down this Soft Keyboard bug, where it's not initially enabled (I'm only going to try set the initial Toggle value to on - not try and resolve the false positive on the driver believing that there's a keyboard docked).
5:00pm - My testing has confirmed that this code only removes the hardware option (set to false and the hardware option re-appears), it doesn't set the hardware toggle to on. But I might be able to use this bit of code to help me start to find the option. I just need to find where the Default Value of this toggle switch is set, and then adjust the default to be turned on, instead of off.
2:30pm - I just had a chance to test the build, the value of config_forceDisableHardwareKeyboard = true, completely hid the Hardware option from the Input and Settings area, preventing the value from being changed. I am just trying a test build with the value of False, but I don't think this is going to turn on the value.... I'll have to try see if I can find where the Hardware Setting is kept (probably in the same part of the code) and work on some sort of fix.
8:30am - I've made a p6810 test build to see if it fixes the keyboard. I'll test it later today as I have to go out now.
I've set the config_forceDisableHardwareKeyboard to true via an overlay file (which overrides the default value of false - which I believe turns off the fix and makes things behave as if the extra code was not included). From what I understand from my reading, the keyboard issue is present because the default driver is wrongly reporting that a Keyboard dock is present. Which if you plug in a keyboard via usb, you see that it behaves like one is, the softkeyboard just gives you word predictions on screen, but no keyboard. So I think that is right. Changing that Hardware option in input corrects this wrong assumption and then the soft keyboard appears.
25 Sept 2015
10:43pm @ I think i might have found some code to fix the soft keyboard not working at startup issue at https://gerrit.omnirom.org/#/c/903/2
Edit: Looking over Cyanogenmod code, they have already implemented this fix, but SlimLP hasn't added it to their code base, so I have added it to the source code and am doing a compile now. The only thing I think I need to work out is if I need a true / false value for the config_forceDisableHardwareKeyboard parameter, but once I have that worked out, hopefully this should fix it.
24 Sept 2015
SlimLP Beta 0.7 - Build #1.2 - Build Date 20150924 - Download ROM from this URL
- Media DRM fixed for Google Play Movies / Youtube DRM based content (libraries from p3100)
- increased dalvik.vm.heapsize=320m - Hopefully should provide a bit more memory for Facebook / Facebook Messenger
@9:30pm - p6800 build is uploaded
@8:43pm (10:43am GMT)- Compile finished for p6800, uploading now
@7:00pm - Build #1.2 - Compiled p6810 build and am uploading. Compiling p6800 build
@10am - I fixed the Play Movies streaming issue. Using libdrmdecrypt.so from p3100 (https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/p31xx/common/system/lib) - goes in the /system/lib, also the three libwv*.so files from (https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-12.1/p31xx/common/system/vendor/lib) in the /system/lib folder, the libdrmwv...so file from (https://github.com/TheMuppets/propr...ee/cm-12.1/p31xx/common/system/vendor/lib/drm) in the /system/lib/drm folder and finally, in /vendor/lib/mediadrm (the vendor folder should really be a link to /system/vendor, not a seperate folder as it currently is in our builds), the libwvdrmengine.so from (https://github.com/TheMuppets/propr...-12.1/p31xx/common/system/vendor/lib/mediadrm).
- Next build if I will try incorporate this fix
23 Sept 2015
- I was having a bit of a play last night with Google Play Movies, as to why it doesn't stream. It seems that Lollipop (as compared to kitkat) requires /vendor/lib/mediadrm/libwvdrmengine.so and possibly a few other components. I have gotten a copy of this file from the exynos 4412 smdk files, but there are a few more components missing (this might not even be compatible with our exynos 4210 but its worth a try). But with this file in place, it no longer gives the device is unsupported message, it tries to start streaming and errors out. I had a quick look in the log and I think it also wanted another crypto .so driver file, so I'll see if I can find that driver as well. There's a large collection of samsung blobs at https://github.com/TheMuppets/proprietary_vendor_samsung
20 Sept 2015
- 1:25pm - 3:25am GMT - I tested GPS on my P6810 (wifi model) and it now works!
- 7:51am - 9:51pm GMT - p6800 build is uploaded.
Daniel has given me some feedback on the i815 and some other things I was wondering about, so I'll go read over his instructions and my code some time next week and see if I can work this out. Once I have it compiling i'll make an update. Thanks @daniel_hk
- 7:24am - 9:24pm GMT - uploading p6800 build. It should be there in the next 20 minutes.
19 Sept 2015 - 11:18pm - I've uploaded the P6810 build of the rom, I'm waiting on the p6800 build to finish compiling - going to sleep now, so that will probably be in the morning. I've had a report from a tester that the Package Installer was crashing on the p6800 build when trying to manually install an APK package. I haven't had this happen on my P6810 build, so if someone can test the new build and let me know if this is an issue still that would be great.
SlimLP Beta 0.7 - Build #1.1 - Build Date 20150919 - Download ROM from this URL
- Rebuilt rom with Bionic Library supplied by Daniel that has Non-Pie Blob / Driver support
- GPS working
- Manually copied RIL Libraries into /system/lib folder from Daniels latest Omnirom Build - Hopefully for the p6800 this should enable RIL / Sim Card support - Files copied from Omnirom build are as follows:
/system/lib/libreference-ril.so
/system/lib/libril.so
/system/lib/librilutils.so
/system/lib/libsecril-client.so
/system/lib/libsecril-client-sap.so
/system/bin/rild
19 Sept 2015 @ 7:14am - Checked my PC this morning and it failed with the same compile error again for the i815. I'll have to keep on looking.
18 Sept 2015 @7:55pm - 9:55am GMT - Clearing out my build folders to try a fresh compile of the i815 code in case some of the p6800/p6810 build code is causing issues. I'll probably post an update tomorrow on how this went. Once I can compile the i815 code properly, I'll start looking at the other issues.
Update: 10:48pm - it may have gotten past the error below now, during the build I noticed the following in the output... still a number of hours to go before the i815 compile finishes.
Code:
build/core/Makefile:46: warning: overriding recipe for target '/home/peter/android/slimlp/out/target/product/i815/system/lib/hw/sensors.exynos4.so'
build/core/base_rules.mk:550: warning: ignoring old recipe for target '/home/peter/android/slimlp/out/target/product/i815/system/lib/hw/sensors.exynos4.so'
15 sept 2015 @10:42pm - 12:42am GMT - My compile of the i815 code hit an error, I'll have to track it down tomorrow if I get a chance
Code:
make: *** No rule to make target '/home/peter/android/slimlp/out/target/product/i815/obj/SHARED_LIBRARIES/libinvensense_hal_intermediates/export_includes', needed by '/home/peter/android/slimlp/out/target/product/i815/obj/SHARED_LIBRARIES/sensors.exynos4_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
15 sept 2015 @5:38pm - 7 :38am GMT - p6800 rom uploaded
Around 7hr 15 min for my old e5400 CPU to compile the 21gb of output per device specific folder to build the p6800 rom (there's a common output, and then device specific output). I'm just about to start the i815 build... just moving my cm12.1 code folder off the drive to an external disk so I have enough room to build the i815 rom.
15 Sept 2015 @ 10:52am - 12:52am GMT - I've uploaded the p6810 rom, I'm currently compiling the p6800 rom and when that's done I'll compile an i815 rom
SlimLP Beta 0.7 - Build #1.0 - Build Date 20150915 - Download ROM from this URL
- Built from SlimLP Beta 0.7 Sources
- Bluetooth Fixed
- OpenGL ES values set to 2.0 values in /system/etc/build.prop
- Davlik VM settings adjusted to possible better values
- Compiled from Daniel's Github sources - check the local_manifest.xml to see which sources where used
- GPS and ASOP keyboard bugs still present, QS tile for torch not working.
- Google Play Movies only work if you download locally first then play, not streamed - I have tested this on other Android 5.1.1 roms on my p6810 and it's the same on all of them at the moment.
- GPS.exynos4.so (GPS driver) from Galaxy S2 i9100 / CM 12.1 rom in this build (it may or may not work with our Exynos 4 processor, but it's a PIE build of the GPS blob for Exynos 4, which means that I didn't need to modify the BIONIC libraries for Non-Pie support). I've uploaded the GPS exynos 4 blob to my Androidhost.com folder for Slim as well - Next build I try for my p6810, I'll use Daniel's older GPS blob's and enable non-pie. However with this PIE based GPS blob, I don't get any GPS Client communication errors / socket not open errors. So I might simply need a different gps config file for this to work
GApps:
Official SlimRoms GApps
Questions and Answers
Testing- Just a note at the moment, I only have a p6810 (wifi only model) so my testing is limited to this. I am compiling p6800 and i815 rom's based on @daniel_hk's github source tree's, doing the modifications that I do for my p6810 to compile. So if you want to test and let me know about p6800 and i815 issues that would be great
i815 - Hopefully in a week or two I'll have time to make a build once I sort out a compile error. Daniel's given me some feedback, I just need to find some time to look over it.
QS Torch - I'll try work out the code for this QS torch tile setting soon
Memory Settings - Interesting article on Davlik Heap values and ART on android 5.0 and 5.1 https://01.org/android-ia/user-guide...id-5.0-and-5.1. Give me some feedback on performance as i still think we can tweak ram a bit more.
No time frames on anything, I'll just do what I can when I can.
Sim card not detected
I tried the new rom on p6800 with no sim card error.
Thanks for reporting back, at least I know that it boots on the p6800. Next build I do for the p6800/p6810 I'll be enabling the Non-PIE blob support which should help with some of the older driver libraries for things like GPS and possibly the RIL library which might fix this error for you as well.
hot spot not working on p6800
dear sir,
I just flash the new 1.1 rom on p6800. Every thing was fine except the hotspot.
My phone can detect the hot spot by p6800, but cannot get connected.
Thank you so much for such a great works.
Wait so is beta 0.7 the newest or alpha 1.1
On beta0.7 now and very smooth
philipnzw said:
Wait so is beta 0.7 the newest or alpha 1.1
On beta0.7 now and very smooth
Click to expand...
Click to collapse
Beta 0.7 is the slim ROM teams designation of their ROM build status. Alpha 1.1 is just my own designation to say it's my test builds, that being my second build, once I have the bugs sorted I will call it stable.
p3dboard said:
Beta 0.7 is the slim ROM teams designation of their ROM build status. Alpha 1.1 is just my own designation to say it's my test builds, that being my second build, once I have the bugs sorted I will call it stable.
Click to expand...
Click to collapse
Aha
It's quite stable already
philipnzw said:
Aha
It's quite stable already
Click to expand...
Click to collapse
I've changed my personal Labelling to Build #, instead of Alpha, that way its less confusing
p3dboard said:
Questions and Answers
QS Torch - I'll try work out the code for this QS torch tile setting soon
Click to expand...
Click to collapse
i think this could be an issue with slimroms in general.
it wasnt working on slimbean last time i tried it and its currently not working on slimkat either. (im on daniels slimkat)
p3dboard said:
Automatic Brightness Sensor - Have to do some more testing - Turning off Automatic Brightness, allows for a greater range of brightness
Click to expand...
Click to collapse
this issue is also present on daniels CarbonLP for me. either its related or somethings wrong with my p6800 thats duplicated on your p6810.
even tho its stable according to some, i think ill wait for a gps update before trying this out.
its times like these i wish we could have the dual/multi boot functionality.
way better and easier for the community to help test out the new/experimental builds.
especially for people like me whos using the p6xx as a daily driver.
good luck to you sir.
HM i will try it and lett you know how it go on my P6800,the lollipop 5.1.1 from daniel,i dont know what is wrong,when the wi-fi is turned on,i cann not tell you how much the difference in performance is,when i turn it on,it become laggy unbearably,so i will check with this................
Still holding up well after installing some xposed modules
Turning on awesome player seemed to help with YouTube crashing randomly
Also, uploading a picture with fb messenger app crashes everything (need to hold down power button)
Think Daniel's roms didn't have this issue.
I might need to increase the maximum memory amount for apps in the Build.prop,i set it to 256m, the default is 384m, but i dropped that lower as when some apps got to that size the rom's can become sluggish. I have had another app (real racing 3) lock up while trying to upload a game profile. I will play with the values some more. These are set in the build.prop file under /system/etc i have posted about them before in one of the other rom threads. If you are comfortable playing with the settings you could put them back to stock values and see if that fixes things for you and you can let me know. Thanks, Peter
Lag
p3dboard said:
I might need to increase the maximum memory amount for apps in the Build.prop,i set it to 256m, the default is 384m, but i dropped that lower as when some apps got to that size the rom's can become sluggish. I have had another app (real racing 3) lock up while trying to upload a game profile. I will play with the values some more. These are set in the build.prop file under /system/etc i have posted about them before in one of the other rom threads. If you are comfortable playing with the settings you could put them back to stock values and see if that fixes things for you and you can let me know. Thanks, Peter
Click to expand...
Click to collapse
Something to REPORT,i dont know it this just on my tab or not,but,it doesn't matter do i use CyanogenMod 12 or Carbon,or this SlimLP,yesterday wehn i instaled Carbon,after 30min when i installed all my apps,the last one that i installed was Facebook,and when i set it,then it become unbelievably Lagg,and i then installed SlimLP,and didnt installed other apps just Facebook,and this Lagged to,just now it just restarted alone.......................is this just because of FB or what is it,i just cann not take it any more,when i see it,the best android was 4.0.1
Definitely Lollipop rom's are more memory hungry than Kitkat Rom's. I am enquiring with one or two other rom maintainers who say they have implemented some optimizations for devices with 1 Gb Ram, to see what changes they are adding to improve performance. So far the best performing Rom i find is still Slimkat 8.2, Android 4.4.4, but it maybe possible to tweak lollipop for better performance. I have read on the Galaxy s2 forum that Facebook is an app with issues on the s2 CyanogenMod 12.1 rom as well. I will do a bit of testing and hopefully with some input from some others we might be able to fix this, we really need a lollipop rom with low memory overheads. Have you tried Facebook on Daniel's omnirom builds? They are the closest to stock Android, and may work better
Edit: i just installed Facebook on my s2 phone with CyanogenMod 12.1 (Android 5.1.1) and it seems to be ok, just wanted to test it on another 1gb ram device. The s2 has about 20mb more usable ram than our galaxy tab 7.7 due to lower screen resolution. Anyway, we will see what we can do to try improve things, a bit of trial and error,playing around
p3dboard said:
Definitely Lollipop rom's are more memory hungry than Kitkat Rom's. I am enquiring with one or two other rom maintainers who say they have implemented some optimizations for devices with 1 Gb Ram, to see what changes they are adding to improve performance. So far the best performing Rom i find is still Slimkat 8.2, Android 4.4.4, but it maybe possible to tweak lollipop for better performance. I have read on the Galaxy s2 forum that Facebook is an app with issues on the s2 CyanogenMod 12.1 rom as well. I will do a bit of testing and hopefully with some input from some others we might be able to fix this, we really need a lollipop rom with low memory overheads. Have you tried Facebook on Daniel's omnirom builds? They are the closest to stock Android, and may work better
Click to expand...
Click to collapse
no,i didnt try omnirom,i just used Daniel's Cyanogenom and Carbon,and this Slim,but when i charge my p6800 i will instal omni and try it.
LeonardoD93 said:
no,i didnt try omnirom,i just used Daniel's Cyanogenom and Carbon,and this Slim,but when i charge my p6800 i will instal omni and try it.
Click to expand...
Click to collapse
Might wanna try fb lite
Always avoided the main app on lollipop roms,after fb the whole system just lags like mad
Fb lite is like a smaller version of the main app,the user interface is absolutely horrible,but hey it works~
Just letting you all know that I have a fix for the Google Play movies not streaming DRM based content. I've posted about it in my Change Log.
philipnzw said:
Still holding up well after installing some xposed modules
Turning on awesome player seemed to help with YouTube crashing randomly
Also, uploading a picture with fb messenger app crashes everything (need to hold down power button)
Think Daniel's roms didn't have this issue.
Click to expand...
Click to collapse
I just tested Facebook Messenger with the davlik memory value set at 320m, and it uploaded a photo fine in my test, no crash. So it may be a memory limitation. SlimLP seems to be lighter on Ram, it may even be ok with 384m, but 320m seems to working ok for me. Next build, I'll increase the /system/build.prop Ram value to at least 320m, possibly 384m.

[ROM][N4][NMF26O] Fake nexus rom for Nexus 4. [Dec/06/2016]

[ROM][N4][NMF26O] Fake nexus rom for Nexus 4. [Dec/06/2016]
Introduction
This is an Android 7.1 custom rom for Nexus 4 that fully integrated Gapps. (Pixel Launcher, Google dialer, Contacts, Webview, backuptransport, etc.. )
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features
Almost same as Pure Nexus Stock image.
Enabled SEAndroid, No Rooting feature provides for security reason.
All build scripts are opened on github
3G data is disabled as default for user that has cheap data plan. But you can enable on data setting menu.
Stock rom users can use this rom without perform reset userdata partition. (In theoretically, it can be applied to other custom rom users, but not tested. )
Known Issues
Nougat version is still unstable. Please use at your own risk.
Some apps can be crashed (ex: firefox, games using unity, etc...)
Camera app shows invalid orientation on preview screen
[*] User switch feature is not working. It should be fix in next release.
Please see FAQ
Installation instructions
1. power down
2. press power and volume down button, and your nexus 4 will go fastboot mode
3. connect usb cable with your PC
4. run fastboot for flashing
If you are using stock factory image or already use this rom.
Code:
$ fastboot update occam-img-20160108.zip
Or if you are using other custom roms, you might perform clear userdata partition.
Code:
$ fastboot -w update occam-img-20160108.zip
After flashing, it needs several (about 5-10) minutes to complete booting.
Changelog
Dec/06/2016: 20161206 (testing)
Update to NMF26O(android-7.1.1_r4)
Nov/08/2016: 20161108 (deprecated)
Update to NDE63V(android-7.1.0_r6)
Rebuild stubs for destroy useless icons
Nov/03/2016: 20161103 (deprecated)
add GmsCoreSetup
add Google VR Service
add help uri on Settings
apply pixel color accents
Nov/01/2016: 20161101 (deprecated)
fix user switch feature
add ringtone migration
fix tethering feature
fix dirtycow exploit
Oct/25/2016: 20161025 (deprecated)
Integrate Wallpaper picker on Settings
Integrate Google Backup & Sync on Settings
Integrate Google Storage Manager
Add Gesture menu on Settings
Enable color temperature setting in developer options
Use Ustwo wallpaper as default
Add Google Wallpapers
Stub apks can show round icons
Oct/21/2016: 20161021 (deprecated)
Update to NDE63P(android-7.1.0_r4)
apply pixel bootanimation, sounds, white navbar
apply latest pixel launcher
apply rounded icons for launcher
Note: it is not capable to use google assistant.
Note2: apps are not odexed, so, boot speed can be slow.
Note3: default ringtone, alarm, and notification sound is changed.
If you cannot hear these sounds, please set manually.
Oct/05/2016: 20161005 (deprecated)
update to NBD90Z (android-7.0.0_r14)
Oct/04/2016: 20161004 (deprecated)
fix ptrace bug on linux 3.4, thanks @zaclimon
switch to non-debuggable build
Sep/30/2016: 20160930 (deprecated)
Remove useless binaries and save space for system partition
apply qualcomm specific build macros
tune codec configuration for legacy binaries
Sep/26/2016: 20160926 (deprecated)
switch to debuggable build.
No more several apps might be crashed . but lesser secure.
revert to 320dpi as default
Sep/23/2016: 20160923 (deprecated)
debuggerd can dump stack when app is crashed on native code
Use Pixel launcher as default home
set 352 dpi as default
sign with release key
Refactor scripts to build other device(Nexus 5)
Sep/07/2016: 20160907 (deprecated)
update to NRD90S (android-7.0.0_r4)
Turned on sdcardfs
Sep/05/2016: 20160905 (deprecated)
Rebase device tree from @zaclimon V4
Remove w/r permission from vidc encoder device to all
It seems while mediacodec server open vidc encoder, camera server cannot use hardware encoder, and cannot record video stream.
Fix facelock funtion
Update widevine drm binary blobs from bullhead.
It might prevent to crash mediadrm and media service. But I cannot be sure it can play drm contents.
Switch to user build.
Sep/03/2016: 20160903 (deprecated)
Enable cpuset
implement exclusive core feature with simple mpcpusetd. @xenyz hints to me how to implement. Thanks.
Tune cpu governor while booting
Aug/31/2016: 20160831 (deprecated)
Rebase device tree from @zaclimon V3
Aug/29/2016: 20160829 (deprecated)
Rebase device tree from @zaclimon V2
Aug/28/2016: 20160828 (deprecated)
update to NRD90M (android-7.0.0_r1)
Rebase kernel source tree from @zaclimon
Rebase device tree from @zaclimon
Update occam device tree (fix compilation, update resources, etc...)
Aug/02/2016: 20160802 (stable)
update to MOB30Y (android-6.0.1_r60)
update google apps
Jul/07/2016: 20160707 (deprecated)
update to MOB30P (android-6.0.1_r50)
replace google photo as stub for reduce rom size
update google apps
Jun/07/2016: 20160607 (deprecated)
update to MOB30M (android-6.0.1_r46)
apply kernel security patches
update latest gapps
remove korean ime
May/03/2016: 20160503 (deprecated)
update to MOB30H (android-6.0.1_r41)
update latest gapps
update google play stub apks' icons
Apr/12/2016: 20160412 (deprecated)
update to MOB30D (android-6.0.1_r30)
apply flo kernel patches
Apr/05/2016: 20160405 (deprecated)
update to MMB29X (android-6.0.1_r20)
update latest gapps
Mar/21/2016: 20160321 (deprecated)
apply flo kernel security update for mm_mr1
Mar/09/2016: 20160309 (deprecated)
sync sources properly and rebuild
Mar/08/2016: 20160308 (deprecated)
update to MMB29V (android-6.0.1_r17)
update latest gapps
Feb/02/2016: 20160202 (deprecated)
update to MMB29Q (android-6.0.1_r11)
update latest gapps
setupwizard property typo fix ( reported by @jolas )
add hdcp binary blobs ( reported by @xenyz )
update opengl binary blobs (Jan 2016 qcom update)
Jan/08/2016: 20160108 (deprecated)
update latest gapps
I hope it could resolve Input Method issue.
Jan/05/2016: 20160105 (deprecated)
update to MMB29O (android-6.0.1_r7)
apply latest callmealdy kernel
Remove SysV IPC from kernel
fix leak of kernel memory to userspace
update qcom opengl binaries
Dec/10/2015: 20151210 (deprecated)
fix Google LatinIME to enable swipe gesture.
In 20151209 version, this rom used latinime from n7 factory image, and it had some problems when try to input with swipe gesture.
So I replaced with latinime from n5 factory image.
It is binary change, so there is no git commit link.
Dec/09/2015: 20151209 (deprecated)
update latest gapps that includes latinime
remove duplicated sound resources
add Google Connection Service and Nfc Provision
Dec/08/2015: 20151208 (deprecated)
update to MMB29K
remove unnecessary patches
replace to stub package for DeviceAssist to save storage
MMB29K image is slightly bigger than olders.
add Stk package as requested from @MarvinOl .
but cannot tested, because my mobile operator is not supported.
update apn list
update latest gapps
Nov/21/2015: 20151121 (deprecated)
Update adreno drivers (Nov 2015)
Update media codec profiles from flo
Apply audio resources from Nexus 5X (same things, but it is smaller than aosp stuff)
Apply memchr optimize patch
Apply patch that make surface buffer allocation asynchronous
Apply workaround for GoogleCamera3 crash
Nov/11/2015: 20151111 (deprecated)
apply libcore patches for speed up finalize daemon and object reference from aosp master
apply skia patches for using NEON from codeaurora
Nov/08/2015: 20151108 (deprecated)
remove useless camera behavior patches
reapply flashlight bug patch
Nov/07/2015: 20151107 (deprecated)
Switch to MDB08M (tree for Nexus 5x/6p)
Update resources and properties for MDB08M
add Dialer workaround for MDB08M
fix Audio HAL for MDB08M
apply recent gapps
Nov/03/2015 : 20151103 (deprecated)
MRA58V(Nov 2015 security patch level) applied
update kernel configurations for android recommands
add init.occam.rc (but it is empty yet)
remove invalid EAP-SIM support
Oct/30/2015 : 20151030 (deprecated)
FaceLock added
set Google Messenger to Default SMS/MMS app
adjust Launcher layout slightly
Oct/29/2015 : 20151029-1 (deprecated)
fix issue that home button is not working when upgrade from Stock factory image
Oct/29/2015 : 20151029 (deprecated)
All locales are available!!!
Also All (Stub) Gapps are available, too
Enable full odex (except prebuilt gapps) to reduce first booting time
Oct/25/2015 : 20151025 (deprecated)
stock rom users can be transitable to this rom without perform clear userdata partition
enable minikin text layout engine
fix gps hal build
Oct/24/2015 : 20151024 (deprecated)
fix a2dp bluetooth profile.
fix calendar sync problem (If calendar app is crashed, Please perform Settings -> Apps -> Calendar -> Storage -> "CLEAR DATA")
add several locales (sk_SK ar_EG pt_BR)
add version codes in gapps build rules
Oct/21/2015 : 20151021 (deprecated)
update adreno gpu driver (Oct/2015)
apply @CallMeAldy mako kernel
apply memcpy, memmove patch from codeaurora
apply flashlight torch mode bugfix
add "Press power button twice for camera" menu in Accessibility Setting (it will be removed after MDB08I source code opened)
Oct/16/2015 : mra58k (deprecated)
initial release
Before you ask something about this rom
Please read this article at first..
If you cannot read English well, it's okay. There are many translations of this article.
This is a very famous article for beginners that want to solve their problems.
Please DO NOT ASK via Private Message or Mail as described as upper article.
I cannot reply all messages and I may not understand all your problems.
If you post your question in this thread, any others can tell about your problems.
If you want to report your issue with this rom specific, please share bugreport data.
You can gather bugreport data with following methods.
Turn on USB debug feature, connect with PC, and run this command
Code:
$ adb bugreport > bugreport.txt
OR
Go to Developer options, select Take bug report. After several minutes, notification will be shown to share data.
Downloads
Stable (Aug/02/2016): https://androidfilehost.com/?fid=24651430732235260
Testing (Dec/06/2016): https://www.androidfilehost.com/?fid=457095661767121028
XDA:DevDB Information
fake_nexus, ROM for the Google Nexus 4
Contributors
ganachoco
Source Code: https://github.com/ganadist/vendor_fake_nexus/tree/nougat-dev
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Current Stable Version: 20160802
Stable Release Date: 2016-08-02
Current Beta Version: 20161206
Beta Release Date: 2016-12-06
Created 2015-10-21
Last Updated 2016-12-06
Is there any way to apply torchlight fix to frank ROM as a flashable zip?
Sent from my Nexus 4 using XDA Forums
I flashed the testing version. It works like a charm!
So with this I can just login after start and use google restore and also my apps will be able to backup to drive when the developer implemented it? Or do I still need to set permissions for gapps?
//Edit: Cmon, I just flashed da **** Yeah works as stated above.
What's new in testing? And what does it mean no ROOTed. Aren't those custom kernels, rooted already? (noob question).
Many thanks.
finchi said:
What's new in testing?
Click to expand...
Click to collapse
Did you even take a look at the first post
Ah sorry. I mistook lines. I was reading it like Oct/21/2015 : 20151021 (testing) and nothing there. (feeling stupid)
Shouldn't a long press on the recent square switch to the previously used app? It does not work in this rom but did on franks. This was really cool.
Camera is launched on double tap on home circle oO nice
Great ROM, I hope it will stay pure as possible
LoadGamePL said:
Is there any way to apply torchlight fix to frank ROM as a flashable zip?
Sent from my Nexus 4 using XDA Forums
Click to expand...
Click to collapse
That is a source level patch.
Please ask that apply that patch to frank ROM maintainer.
bassbox said:
Shouldn't a long press on the recent square switch to the previously used app? It does not work in this rom but did on franks. This was really cool.
Click to expand...
Click to collapse
This rom provide only stock rom features.
I have no plan to add other features.
bassbox said:
Camera is launched on double tap on home circle oO nice
Click to expand...
Click to collapse
You find it!
That is hidden test feature that samsung phones have.
And I put for vefify https://android-review.googlesource.com/177020
finchi said:
What's new in testing?
Click to expand...
Click to collapse
Please see Changelog.
finchi said:
And what does it mean no ROOTed. Aren't those custom kernels, rooted already? (noob question).
Many thanks.
Click to expand...
Click to collapse
In testing release, this rom uses @CallMeAldy kernel.
And rooting feature that other roms have, is not provided as default for security reason.
ganachoco said:
This rom provide only stock rom features.
I have no plan to add other features.
Click to expand...
Click to collapse
Yeah I thought this is a New stock feature ^^
Can you integrate large version of Google Now Launcher (1.2.large) which originally comes with Nexus 5, 6...? Your rom contains 1.2.small version of Google Now Launcher.
Whenever I browse youtube, screen freezes and System UI FC's.
Rock-86 said:
Can you integrate large version of Google Now Launcher (1.2.large) which originally come with Nexus 5, 6...? Your rom contain 1.2.small version of Google Now Launcher.
Click to expand...
Click to collapse
Which are the changes between 1.2 large and 1.2 small?
Inviato dal mio Nexus 4 utilizzando Tapatalk
sidnoit22 said:
Whenever I browse youtube, screen freezes and System UI FC's.
Click to expand...
Click to collapse
Which version of the ROM are you using?
You should upload bug report data:
ganachoco said:
You can get bugreport data by
Turn on USB debug feature, connect with PC, and run this command
Code:
$ adb bugreport > bugreport.txt
OR
Go to Developer options, select Take bug report. After several minutes, notification will be shown to share data.
Click to expand...
Click to collapse
cianz94 said:
Which are the changes between 1.2 large and 1.2 small?
Inviato dal mio Nexus 4 utilizzando Tapatalk
Click to expand...
Click to collapse
Not sure, but Large is comming with Nexus 5, 6..
I found one note for Small version:
Notes / What's New
Uploader's notes: Google Now Launcher Version 1.2. small from Android One Device running Android Marshmallow 6.0
Click to expand...
Click to collapse
Rock-86 said:
Can you integrate large version of Google Now Launcher (1.2.large) which originally come with Nexus 5, 6...? Your rom contain 1.2.small version of Google Now Launcher.
Click to expand...
Click to collapse
According by this figure, N4 has large screen, and I'll put large version when next version release.
Thank you for notify!
Hmm seems interesting seeing that 3 days left on the battery page screenshot . I have not seen mine say more than a little over a day left since a LP ROM I had a very very long time ago where 3 days was almost actually what I got pretty darn close to a few times . Very cool
Update- just checked and at 91% left its says 14 hrs left lol. But I'm currently running a different Android 6.0 ROM but must say hands down this Marshmallow is the FASTEST/smoothest I've ever seen my N4 run. Hell was gunna get me a N6 or the newer N5 so I could use my google fi invite but Im very happy with my device speed that I'm not sure I want to atm now .

[DISCONTINUED][ROM][6.0.1r52]Resurrection Remix-MM 5.7.0 [T00F/J]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Features:-
Based On Latest Google Android 6.0.1 Release
Based On Cyanogenmod 13 Sources
RR Customizations:-
-Navigation Bar
-Enable/Disable Navbar
-Navbar Button Customization
-Navbar Slim Dim
-Animate Dim
-Dim Timeout Duration
-Dim Alpha
-Double Tap To sleep navbar
-Navigation Bar left/Right handed mode Switch for landscape
What NOT working:
GPS && FM
NOTE:
This rom marked as nightly but it does not mean that it is unstable and etc.
It mean that i add something every day. Nothing else.
How to flash it:
Step 1:
You should download files for flashing:
Latest Flashable nightly build:
OP: Link is removed
ADB v1.0.32: Google Drive
TWRP 3.0 MM by @X AnwarMov: AndroidFIleHost
Gapps: http://opengapps.org
Flashable boot with enabled selinux (optional; SIM is OK):
https://drive.google.com/open?id=0B-Fin8UxrD6PN2lZSTdUQ0NUUG8
Note: Choose x86 -> Android 6.0 -> pico
Flash it BEFORE first boot.
How to install ROM with gapps and without data/cache wipe:
Disable FC noifications in Settings
Flash this TWRP:
https://www.androidfilehost.com/?fid=24572369242686021
Flash gapps. DO NOT wipe data or cache
Reboot to system
Go to Settings -> Apps
Manually give all permissions to Google Play Services, Play Market and Google Keyboard.
After that open menu with system process.
Find Setup Wizard and give all permissions to him too.
Xposed for TWRP (optional): Google Drive
Step 2:
1) Unpack archive with ADB and put TWRP image there.
2) Copy file with rom to internal/external memory of your phone.
3) Then you should reboot your phone in the droidboot mode. (turn off you gadget then press Turn off button and volume + button)
Then go to the ADB folder and hold Shift + Right Mouse button and write this command:
Code:
fastboot flash recovery cm-13.0-20160408-UNOFFICIAL-T00F-recoverytwrp.img
Then you should reboot your phone in the recovery mode. (turn off you gadget then press Turn off button and volume - button)
Step 3:
Then you phone will reboot in the recovery. In the recovery you should install package with rom.
Step 4:
After flashing, you should format (not wipe) data and cache in the TWRP.
Then you should reboot to system.
How to root this rom:
Go to the develoepr settings and enable it there
Dirty flash:
If you want to make a dirty flash, you should flash rom without gapps and wipe cache.
But if you need gapps, you should wipe data too.
Credits:
Credits goes to:
@X AnwarMov (device tree + TWRP)
@dgadelha (hardware folder)
@quanganh2627 ( i used few stuff from his device tree)
@shobint7 (for new ROM logo)
@Sukarn (for his unofficial OTA app support)
USING MY ROM AS BASE FOR YOUR ROM IS DENIED
IF YOU IGNORE IT, I WILL ASK MODERATOR TO DELETE YOUR THREAD
XDA:DevDB Information
RR MM for Zenfone 5, ROM for the Asus Zenfone 5
Contributors
tank0412
Source Code: https://github.com/tank0412/RRmm_device_asus_ctp-common
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Any Lollipop or Marshmallow rom
Based On: CM,
Version Information
Status: Nightly
Created 2016-04-12
Last Updated 2016-07-10
Changelog (08072016):
Merge 6.0.1_r52 branch
July stagefright patch is there
Build is is MOB30R
Changelog (07072016):
Fix sensors
Sync RR sources
Changelog (06072016):
Use another ramdisk
Remove CMactions
Sync RR sources
Changelog (23062016):
boot: changes in zram and f2fs work
boot: update adbd and healthd binaries
Update RR Ota app to v69
Sync RR sources
Changelog (21062016):
Fix camera video recording
Fix Houdini
Fix A-GPS
Update ramdisk of boot
Build new bzimage
Sync RR sources
Revert a ton of changes
Changelog (17062016):
Use device tree, ramdisk and bzImage by X AnwarMov
It was very hard to make bring up because there are many missing stuff in his tree but i fixed it. xD
So if something does not work, report me.
Note: If somebody consider to do same, use this:
https://github.com/tank0412/android_device_asus_ctp-common
https://github.com/tank0412/proprietary_vendor_asus
http://review.cyanogenmod.org/#/c/142597/
Changelog (15062016):
Fixing APN issue
Revert "Test Houdini from Samsung Galaxy Tab 3 10.1" (it may fix freezes in games)
Sync RR sources
More old changelogs:
Changelog (14062016):
Partly fix APN issue
Use blobs from 3.24.40.87 firmware (experimental)
Sync RR sources
Changelog (13062016):
overlay: enable automatic brightness by default
Use stock apns.conf
ctp-common: add power_profile.xml from T00F
update from stock power profile
Add support power profile for a600cg
ctp-common: overlay: add conf fir mms, platform and upd tel conf
Fix SD write perm (!?)
ctp-common: overlay: fix building errors
Sync RR sources
Changelog (12062016):
(cherry-pick commits by quanganh2627)
Add new config_TerminalDetectWindowOrientation & config_nonPollingWindowOrientation
Some stuff for recording call session
Add intel permlic permissions
[Telephony] Allow users to switch prefer Network Mode (2G/3G/GSM...)
Let system handle the restoring of network selection
Sync RR sources
Changelog (11062016):
Add values for brightness from Kitkat
Sync RR sources
Changelog (08062016):
June stagefright patch is there
Merge 6.0.1_r43->6.0.1_r46 (build id is MOB30M)
Sync RR sources
Changelog (06062016):
More stuff for debugging and clean up in default.prop
Revert: boot: Use NOOP I/O Scheduler during boot
Revert: boot: enable LZ4 compression for zram
Use ramdisk from kernel with enabled selinux (selinux was disabled there)
Also apply previous changes to this ramdisk:
Use fstab.zram, init.modem.rc, init.wifi.rc, init.wifi.vendor.rc, init.wireless.rc, init.zram.rc and init.gps.rc from ramdisk for RR LP (Stable7.2) by quanganh2627
Rom: sync RR sources
Changelog (05062016):
Use fstab.zram, init.modem.rc, init.wifi.rc, init.wifi.vendor.rc, init.wireless.rc, init.zram.rc and init.gps.rc from ramdisk for RR LP (Stable7.2) by quanganh2627
Sync RR sources
Changelog (03062016-V2):
Fixing issue which increased a rom size
boot: increase zram-swap (i hope that it will help users with 1 GB RAM)
boot: fixing Bluetooth
Sync RR sources
Changelog (01062016):
Add kernel which based on ramdisk from Stable3.1. Lets see is it fix a battery drain.
Sync RR sources.
Update custom OTA app to v65
More old changelog:
Changelog (31052016):
boot: use GCC v4.9 for building
boot: go back to ramdisk of 27th May
Sync RR sources
Changelog (29052016):
Update ramdisk of boot, build a new boot.
Update OTA app
And sync RR sources
Changelog (28052016):
Update OTA app by Sukarn to v52
boot: test another init.modem.rc
Sync RR sources
Changelog (27052016):
boot: Use NOOP I/O Scheduler during boot
boot: enable LZ4 compression for zram
rom: sync RR sources
Changelog (25052016):
Sync RR sources
Add updated OTA app by Sukarn
Changelog (24052016):
boot: fixing USB debugging (borrow ramdisk by dgadelha)
add custom OTA app (It looks like it is working) Thx Sukarn
Sync RR sources
Changelog (22052016):
boot: define CONFIG_LOCALVERSION
boot: revert few changes in a ramdisk to fix fc of kernel auditor
Revert "ctp-common: change ro.telephony.ril.config"
Sync RR sources
NOTE: commit a16437db6cd687bcfc8d2ca210f70c9fff80b24d by CM Team (Add p2 option in OpenLogicalChannel) for frameworks/opt/telephony was reverted due to building errors.
Changelog (21052016):
Update RR sources to 5.6.9
Changelog which was provided by RR Team:
ResurrectionRemix - v5.6.9 - Android 6.0.1_r43 - 20160520
Android 6.0.1_r30-> r43
Introducing Resurrection Remix Rom stats
SysUI:Custom Recents Style -Taskviewheader colors
Carrier Label Fonts Style
Custom Headers : Add new material design colorful headers
SystemUI : Re-order left statusbar icon layouts and paddings
Option to Hide carrier label based on notitication icons
FWB: Carrier label font style
Battery bar enhancements
ActivityManager: fix perf boost NPE
Qs: Add Audio Fx Visualizer Tile
batteryservice: Add support for segmented power LEDs
QSPanel: Fix Reported SystemUI FC on Themes Tile
SystemUI: avoid lock screen shortcut picker crash
SysUI: Show keyguard when LLS dies and had focus
pms: Skip reinstall of prebundles correctly per user.
systemui: Fix the TrustDrawable animation state
SystemUI: bail out of recents-to-home animation when losing focus
Lockscreen : Bunch-o-fixes
Themes: Expose manifest styles for framework activities
Add new options for call waiting response in InCallUI
SysUI: Make sure LLS focus is false when unlocking
perf: Send the process name and pid for launch boosts
am: Remove extraneous boostage
batteryservice: Use Alpha channel for segmented LED power level
ThemeTile: tighten up how we execute a theme change
CmRes: Attach themed cmsdk resources to assets
SystemUI: attach a queue to media player notifications
SystemUI: fix play queue crash
am: Don't protect apps that atttempt to grant uri perms
SystemUI: fix potential NPE with Queue
only use proximity checks on wakeup keys
SysUI: Use VectorDrawable's for rendering battery
Fix SystemUI FC on Media Notification Queue
bootanimation: fix check for system bootanimation
MediaScanner: Add support for default ringtones per sim
Fix incorrect behavior for statusbar and quicksettings panel
ActivityManager: fix perf boost NPE
QS: fix performance profile tile observer
SystemUI : Fix multi-user for keyguard
SystemUI: Set circle battery path as untranslatable
Update volume slider only if ringer mode changed
SystemUITests: fix compile error
Lockscreen : Disable left edge after showing keyguard
Keyguard: Allow swiping up when trust managed
SpamFilter : Hide option if notification cannot be filtered
FWB: Move Pulse Configs to Secure
LS:Fix Weather Panel Not hiding With Max Notif
Acquire wakelock until dream service acknowledges dream state change
Lockscreen : Only animate targets if launched via swipe
Ensure camera is launched if doing screen off gesture
Keyguard : Ensure we expand onIconClicked
WindowManagerService : Ensure we update both size/position
Fix Battery Icon Tint on Keyguard
SysUI:Update a Custom Logo
SysUI:Update some quick tile icons
Qs: Add Audio Fx Visualizer Tile
Speed up notification panel pulldown animation when called externally
Lls: Use LlsController for checking LLS focus
LLS: Don't change bar state when changing LLS focus
LLS: Ensure LLS loses focus when showing bouncer
ShutdownThread: Decrypt before stopping storage manager
VisualizerTile: Use proper Techniques to unlink with Pulse
Release alarm wakelock for blocked uid.
SyncManager: Adjust sync remaining time calculation.
Themes: Fix theming of cmsdk assets
Fix isComponentProtected calls in package manager tests
MSIM: Fix to resolve SIM PIN unlock in APM.
SystemUI: Check current data subscription when updating signal cluster
SysUI: Adjust battery dimensions for better look
am: Handle unchecked activity starts for protected components.
SysUI: Check swiping progress before collapsing KBA
SystemUI : Fix left swipe when dismissing bouncer
usb: ensure accessory detached sent on re-attach
SysUI:Cleaup Observers and fix certain mem leaks
SystemUI: fix NFC tile sometimes hiding
SystemUI : Ensure bouncer is not shown for SHADE
Port "Settings: add a way to not localize zone selections" to cm-13
Telephony: fix crash if SubInfo isn't ready
Settings:Close "Protected apps" activity during power cycle
Settings: Move vibrator value restore to onActivityStop
Settings: Use correct icon for sim card
Settingsisable battery pulsing if segmented battery LED is enabled
Settings:Update MultiTasking Category Icon
Settingsrotected apps: fix rotation states
Settings:LockPatternView: persist state across rotates
Settings:LLS: Load title and summary from ext. package if avail.
Settings: Make sure to rebuild on app entries loaded.
Settings: fix backlight illumination wrong summary
Settings: More Dashboard Customizations
Fix Reboot on Call Waiting Scenario
Update Translations
All updates from CM
For more info Track Github Activities
Changelog (20052016):
ctp-common: add charger images to device tree
Boot: fixing headphones
Sync RR sources so mobile internet must be OK. Just check it.
Changelog (19052016):
(based on work by dgadelha and X AnwarMov )
ctp-common: change ro.telephony.ril.config
ctp-common: Disable fsck on power off
ctp-common : drop ituxd overlay
ctp-common: switch to latest ramdisk (it looks like battery drain is fixed)
ctp-common: add libinit
boot: Disable faulty smartassH3 governor
boot: switch back to GZIP compression
boot: Update healthd, charger, dnfix and remove pclinkd (blank battery icon during charging in offline mode is fixed)
Sync RR sources.
Changelog (17052016):
Use updated libmultidisplay sources (cherry-pick commit by dgadelha)
Add more stuff to TARGET_OTA_ASSERT_DEVICE
Use boot from Stable3.1
Sync RR sources
Changelog (15052016):
Use boot.img from S3.2
Many changes in BoardConfig.mk (based on work by X Anwar Mov)
Sync RR sources
Add missing thermal config to system/etc
Changelog (14052016):
Add ituxd and thermal config (desparate attempt to fix heating)
Add non-modificated boot.img by dgadelha (desparate attemt to fix battery drain)
Sync RR sources
Changelog (13052016):
ctp-common: remove unused thermal config (enabled ituxd cause lag for some users)
ctp-common: Wi-Fi: add cyanogenmod additions by @X AnwarMov (hope that it will solve a wi-fi problem for some users)
Totally remove CMactions
Sync RR sources
boot: update ramdisk to possible fix of battery drain for some users
Changelog (12052016):
power: fugu: fixing DT2W (it was time to code)
power: fugu: make more changes in code
Sync RR sources
ctp-common: Enable the onscreen "Dial" button in the emergency dialer (Thanks X AnwarMov)
Preparing to remove CMactions (gesture menu) from Settings because it is useless.
Changelog (11052016):
Revert "board: disable the usage of cursor layers"
common : cmhw : recorect lto src (thx X Anwar Mov)
Some translate changes in CmActions
Automatic translation import for CMactions
Use Hoduini from Samsung Galaxy Tab 3 10.1 (Line app is working, so i think that Houdini is OK)
Sync RR sources
Changelog (10052016):
Use power driver from fugu
Test building without BOARD_PROVIDES_RILD (RIL)
board: disable the usage of cursor layers
Enable cpusets
Sync RR sources
Changelog (09052016):
boot: build new kernel from source (headphones is OK)
boot: revert few changes in a ramdisk
Sync RR sources
Other changes is based on work of X AnwarMov :
overlay : update tether configuration , fix wifi hotspot
cmhw : add Long Term Orbits (LTO) support
overlay : rename wifi direct name
boot: Use init.modem.rc from cvtlp-common repo (i hope that it will improve work of RIL)
Changelog (08052016):
Add support of f2fs
Re-add call of hardware/broadcom/wlan/bcmdhd/firmware/bcm4339/device-bcm.mk
Cherry-pick few commits by X AnwarMov :
Changes in GPS configuration
Use sepolicy from his cvtlp-common
ituxd : add thermal management to overlay
Changelog (06052016):
Add config for Snap camera app so freezing after photo took was fixed! You do not need anymore to enable HDR mode to fix it.
Add ALAC (Apple Lossless Audio Codec)
Build some audio libs from src
Sync RR sources
Test block-based otapackage
Changelog (05052016):
Remove MmgrClient from device tree (it affect work of RIL so i hope that RIL will become more stable)
Sync RR sources
Use otapackage building (flashable zips) as was suggested by @X AnwarMov Unfortunatly, it still does not block based.
Changelog (04052016):
Merge 6.0.1_r43 branch
Apply all fixes for ROM by RR Team
Add May stagefright patch
Add KeyDisabler from mofd tree
Remove rild.te from sepolicy folder
Changelog (03052016):
Update to RR v5.6.8
Merge 6.0.1_r30 branch
Apply all fixed for ROM by RR Team
Know NEW isues:
Bootanimation is lag a lot. (It is a ROM sources fault)
Changelog (02052016):
ROM:
Add few variables for GPS to BoardConfigCommon.mk
OTA: update device maintainer list in Settings (it looks like OTA is still dead)
Boot:
(apply all changes by @dgadelha)
Update devicenamefix
Add screen lock fix by XDA member vigneshvikky, enabled by default. (REMOVED)
Click to expand...
Click to collapse
Changelog (29042016):
Rom: Add more stuff to overlay for SystemUI. mms, Dialer and Phone.
Boot: disable again Timed Modem Restart for ASUS Zenfone 5/6 RIL by dgadelha
Boot: Change charging animation (while phone is turn off)
Changelog (28042016):
Add more GPS config to overlay
Use latest ramdisk for boot.img from Bitbucket
Changelog (27042016):
Add GpsLocationProvider from stock
Changelog (25042016): (fixed)
A-GPS fixes:
add missing init.gps.rc in ramdisk of boot.img
add missing gps.conf, gpsconfig_HULA.xml and gpsconfig_NoHULA from etc folder.
Old changelogs:
Changelog (24042016):
Push fixes to boot.img to fix battery drain and netwrok lost issues
Use another RIL config in device tree
Delete nfc.te sepolicy (because our device does not have NFC)
SuperUser was fixed so you do not need anymore to flash SuperSU for root
Changelog (23042016):
Few changes in Wi-FI config (i hope that it will fix problem with WI-FI for some users; Please report me is it fixed)
Kernel: update ramdisk and fix charging in offline mode (healthd fix)
Changelog (22042016):
Testing Marshmallow CM13 sepolicy from Asus Zenfone 2
Use Snap app instead of Camera2 app
ota_conf was updated
Changelog (20042016):
Apply my autobrightness fix
Add CMactions
Remove ituxd
Sync CM13 device tree so
Changed Camera app
Fix some RIL behavior
Fix some green bars on video playback
Update CMHW classes
Fix Camera
Changelog (19042016):
Remove underclock (it is useless and making lag)
Problem with headphones on my kernel was fixed
Audio: use asound.conf and audio_policy.conf from stock Lollipop firmware instead of file from Zenfone 2 firmware
Media: use media_codecs.xml from stock Lollipop firmware instead of file from Zenfone 2 firmware
Changelog (18042016):
Enable ituxd for thermal stuff
Add thermal config
Changelog (17042016):
Add ota_conf (trying to enable OTA)
Use another RIL config (trying to fix "com.android.phone was stopped" issue)
Update ramdisk of boot.img
Enable DT2W in boot.img
Add ton governors and i/o stuff + underclock
Changelog (16042016):
Camera was fixed
Problem with SMS was fixed (use android_packages_apps_Messaging from CM13 repo; branch - stable-cm-13.0-ZNH2K)
Rom became stable for daily use. So release version of rom is changed to Stable.
Changelog (14042016):
Delete strings with LTE (Z5 does not support it) from overlay
Trying to use Camera Wrapper from Xiomi MI4 (cm13 branch) - no success
Add init.superuser.rc in kernel ramdisk
Add Asus Flashlight app. This way you can use Flashlight (flash) via this app
Changelog (12042016):
Apply patch for vibrator (pls tell me is it work)
Autobrightness and brightness were fixed.
Size of rom was reduced (this way you will be able to install more stuff with this rom)
Use LP config for camera (it stay dead)
Changelog (11042016):
Initial release
Reserved #2
Wahh luvin' it im waiting for camera fix. Will V4A works in this rom?
Yeah finally RR is back, good job
Uppppp. Thanks
sol212307 said:
Wahh luvin' it im waiting for camera fix. Will V4A works in this rom?
Click to expand...
Click to collapse
What means V4A?
tank0412 said:
What means V4A?
Click to expand...
Click to collapse
Viper4android...just curious cuz selinux is disabled o.o
Thanks. Please fix the camera. Can't wait more.
Sent from my ASUS_T00F using XDA-Developers mobile app
SMS work ? No error ?
Sent from my ASUS_T00F using XDA-Developers mobile app
Oops, i forget to add credits.
Credits goes to @dgadelha (device tree) and @X AnwarMov (TWRP)
adamilmanns said:
SMS work ? No error ?
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Dammed.
It looks like it does not work.
Nice work @tank0412. Keep up man!
tank0412 said:
Dammed.
It looks like it does not work.
Click to expand...
Click to collapse
Link for root dead? Can't find the link
sol212307 said:
Link for root dead? Can't find the link
Click to expand...
Click to collapse
You can get root via Developer Settings because it is a CM-based ROM. xD
I switched to RR due to this.
wow....
Sent from my ASUS_T00J using XDA Free mobile app
good job. Repels only camera and SMS , it is important for me.
Link root??
Phamtung30h said:
Link root??
Click to expand...
Click to collapse
Flash SuperSU via TWRP:
https://drive.google.com/file/d/0B-Fin8UxrD6Pdmkwbnk1aE1YOEk/view
awesome bro, thank you so mush for your hard work
ASUS_T00F cihazımdan Tapatalk kullanılarak gönderildi

Categories

Resources