Database Develop

[ROM][P75xx][JB][4.2.2] CyanogenMod 10.1 Nightly Discussions

At pershoots request, here is the official nightly discussion thread. I will be updating this with information that I find and users posts that are helpful. REMEMBER: THIS IS A WORK IN PROGRESS SO ALWAYS READ THE THREE POST FOR UPDATED INFORMATION
CyanogenMod 10.1 is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your tablet.
New CM Wiki page! http://wiki.cyanogenmod.org/index.php?title=Main_Page
New CM Documention! http://wiki.cyanogenmod.org/index.php?title=Documentation
{
"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"
}
Usual CM disclaimers:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Known Issues (copied from droidbasement):
-A random flicker (it’s faint and fast) can be observed occasionally/infrequently. If this becomes a nuisance to you, you can try to alleviate this by selecting ‘Disable HW overlays’ in Developer Settings. This does not survive a reboot (must be selected on every boot) and impacts swiping motion (it slows it down) in Trebuchet (the Launcher).
-P4*: A 720P recording, when played back, will have artifacts in the upper section of the image. Also when launching the recorded video for the first time, you will encounter a bit of a delay before it launches.
-P4*:If you use the standard GAPPS (from goo), the keyboard will close if typed on for 2 or 3 letters quickly in succession, if you use Google Search, Messaging and/or Gtalk (there could be more). This is a GAPPS library issue. Install a third party keyboard (Swiftkey 3 works ok) and switch to it. This does not affect Browser, System, etc (stock KB works fine there). The GAPPS from wingray don’t appear to exhibit this behavior from brief feedback (make sure your system is cleaned out using the latest recovery (format system), prior to installing the rom and gapps if you had the set from goo installed prior (it has also been reported that data needed to be wiped as well to rid of the residuals)): http://forum.xda-developers.com/showpost.php?p=35825009&postcount=3553
-Wallpaper will be down aligned on the lockscreen.
Things that need work from the community:
Samsung Keyboard Layout
Tell me more
CWM:
Make sure you have the latest (CWM 6.0.3.0)
Download from pershoot website, select your Tab version below:
P7510 (Wifi Only)
http://droidbasement.com/galaxy/roms/cm10.1/p4wifi/
P7500 (3G+Wifi)
http://droidbasement.com/galaxy/roms/cm10.1/p4/
SCH-I905 (Verizon)
http://droidbasement.com/galaxy/rom...//droidbasement.com/galaxy/roms/cm10.1/p4tmo/
Download recovery.tar.md5 and flash with ODIN or Mobile ODIN
Links for ODIN 1.85 : MediaFire
Links for Mobile ODIN by Chainfire Play Store and XDA
Bootloaders: Make sure you update your bootloaders to ICS. People who flashed an ICS custom ROM coming from HoneyComb (3.1) do not have the correct bootloaders.
Download Bootloaders from pershoot site: http://droidbasement.com/galaxy/roms/cm10.1/
Locate your variant and flash with ODIN. *NOTE: MOBILE ODIN DOES NOT FLASH BOOTLOADERS. ONLY ODIN WILL
Bootloader Flashing Instructions: (see image attached to post if unclear)
1) Open ODIN, all settings should be at default, if you change anything, hit reset or make it the same as image attached.
2) Select PDA slot and select the bootloader.tar file.
3) Flash
4) If unclear about the instructions, please ask!
Modems:
Download the recommended modem for your device at droidbasement:
http://droidbasement.com/galaxy/roms/cm10.1/
Install instructions are in post #3
P4 Variants Downloads: (Please see READ ME in post #2 to avoid and confusions or headaches)
P7510 (Wifi Only)
http://get.cm/?device=p4wifi&type=nightly
Changelog: http://mobile.10.1.cmxlog.com/?device=p4wifi
P7500 (3G+Wifi) (You must be on the ICS modem for best results.)
http://get.cm/?device=p4&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4
SCH-I905 (Verizon) (You must be on stock ICS (and it’s modem) before flashing to this build, for LTE functionality)
http://get.cm/?device=p4vzw&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4vzw
SGH-T859 (T-Mobile)
http://get.cm/?device=p4tmo&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4tmo
gapps: (update 01/29/2013)
P75xx gapps: gapps-jb-20130129-P75xx.zip http://www.mediafire.com/?44xhky6dyx4wlw2 Credit to dreamcwli from his thread on Xoom My Android ROM 4.2.1 for original package (Please thank him for the gapps)
Known Issues if using Goo Inside gapps or other gapp packages:
-Hot word detection for Google Now (caused the Google Now crash when starting)
-Gesture typing (causes random crashes when enabled)
-Photosphere (crashing when selecting camera or after aligning shot)
These features are removed in P75xx gapps.
Removed any Google Apps (e.g. Play Music, Sound Search, Calendar, Gmail) that can be downloaded in Play Store: https://play.google.com/store/search?q=Google+Inc.&c=apps
Credits:
pershoot for his hard work
Cyanogen for his amazing ROM
CyanogenMOD Team for their awesome work
Follow CyanogenMOD Team:
Google+
Twitter
PSA from CyanogenMOD about non-NEON future support: https://plus.google.com/u/0/117962666888533781522/posts/8wcuSVkr7zR

READ ME:
#If using 4.2.2 and want to roll back to 4.2.1 (last build is Feb 13th), you will need to do a full wipe to move backwards or you will bootloop. (update 02/19/13)
#PSA from CyanogenMod team: https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq (update 02/19/13)
ADB Whitelist
As of the Android 4.2.2 update, when you connect your phone to a computer, you are presented with your computer's RSA key fingerprint to open the adb connection. You also have the ability to permanently trust the computer, so you don't have to repeat this step upon every re-connect.
In order for this to work, you must be on the latest SDK which will grant you an updated 'adb' binary.
We will not be introducing any functionality to sidestep this default security, so if you don't update, you will lose the ability to access the device using adb.
# CM 10.1 is based on Android 4.2.1. Any and all proprietary applications that you have installed outside of CM should be updated to their 4.2.1 counterparts. Do not use the 4.1 versions of proprietary applications, else you will experience difficulties.
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# You do not need to wipe when updating to 10.1 if coming from an earlier CM version. However, as we mentioned in the weekend's PSA, users updating (instead of wiping) will experience a conflict in the application data for the Clock app. You are advised to clear this apps data on first boot of 10.1.
# Another item to note is that the support for the 10.0 feature that allowed for an expanded number of targets on the pattern lockscreen is not in 10.1. If you use this lockscreen, disable it before updating from 10.0.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0. Credit to post from CyanogenMOD team (G+ https://plus.google.com/+CyanogenMod/posts/9X561GFMxL5)
Coming from Samsung ICS ROM (custom or not) requires a FULL WIPE (Wipe Data, Cache, and Dalvik Cache) If you do not WIPE you will get a bootloop.
From droidbasement:
GT-P7500 (p4), GT-P7510 (p4wifi), SCH-I905 (p4vzw) and SGH-T859 (p4tmo)
-For P4VZW: You must be on stock ICS (and it’s modem) before flashing to this build, for LTE functionality
-For P4WIFI UK: You must be on the US ICS bootloader (odin .tar.md5 inside the .zip in the folder), otherwise you may incur a rolling screen
-For P4: You must be on the UK ICS bootloader (odin .tar.md5 from AUS inside the folder), otherwise you may incur a rolling screen.
-For P4*: You must be on the ICS modem for best results.
BEFORE REPORTING ANY BUGS, PLEASE DO A FULL WIPE AND FLASH AGAIN TO VERIFY THE BUG! ALSO, NOTHING WILL GET FIXED WITHOUT A LOGCAT (we cannot debug xda posts, need a logcat)
Getting a logcat:
1) Make sure ADB is installed (http://developer.android.com/sdk/index.html)
2) Open Command Prompt
3) adb logcat -d > logcat.txt
4) Locate the logcat and upload to xda

Install Instructions: IMPORTANT TO SEE READ ME IN POST #2 It will save you a lot of headaches when upgrading or updating your Tablet.
1) Install the latest CWM (see 1st post for more info)
2) Install ICS bootloaders (1st post) *People who flashed an ICS custom ROM coming from HoneyComb (3.1) do not have the correct bootloaders.
3) Boot into CWM and flash CM10.1 (Please see READ ME in post #2 for more information)
4) Flash gapps-jb-20130120-P75xx.zip (see 1st post for download)
5) Reboot
pershoot has stated before: "best to wipe as some experience lag with multi user." and "if you get any latency/ bizarro behavior, wipe"
F.A.Q
Want Adobe Flash on your Jellybean Tab? (update 05/21/13) New version is (11.1.115.58)
Check out the latest download here: http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html Scroll to Flash Player for Android 4.0 archives and download most current (11.1.115.58). *Note: Flash is not supported in Jelly Bean, no support given in this thread as well.
Need Developer options and Performance tabs?
Go to settings>About tablet and start tapping Build number until it says your a Dev.
I am getting sudden reboots or freezes?
Not all tablets are created equal, if you are experiencing sudden reboots after Overclocking, reset your options back to default.
I am still rebooting or freezing?
Do a full wipe and DO NOT install anything. If the tablet is not rebooting or freezing, install your apps one at a time to isolate the cause. If you are using Titanium Backup, DO NOT RESTORE DATA FOR SYSTEM APPS.
I get Force Closes (FC) when I launch ____ app?
Try clearing data for the application by going Settings>Apps and locate the app and select Clear Data.
How can I increase Launcher performance?
Enable wallpaper hack (Settings> Launcher>Homescreen) and select Wallpaper quick render to boost home UI response (when using a static wallpaper).
Once I am on CM10.1, do I need to continue getting my updates at get.cm?
No, you can update future nightly builds by going to Settings>About tablet>CyanogenMod updates. Once there, change Update types to "New Versions (incl. Nightlies)" *NOTE: Pay attention to the file name, you might occasionally see CM 9 or 10 in the list, DO NOT FLASH!
Can I enable Voice Calling on my tablet?
At this time, the framework has the hook enabled to allow for users to work on the feature. IT IS 100% UNSUPPORTED at this time because it requires you to flash modems which is a deviation from the recommended setup.
I flashed ___ from another___ thread, now ___ this stopped working?
Wipe data and flash CM 10.1 from get.cm, does this issue still happen? If so, post logcat... if not, seek support from the thread you flashed the file from.
I HATE the new layout with the navigation keys in the middle, can I move it?
At this time, the nav keys in the middle is the design. Who knows, CM Team might change this in future builds.
OH NO! Where did my previous CWM backup go?
4.2. changed the file structure on how internal storage is viewed. Data on the internal/fake sdcard will go to 0/ (i.e. /sdcard/0/; /data/media/0/) (both are the same thing).
Since the internal storage is emulated, it is setup now (using file explorer like ES) /mnt/shell/emulated then you will see /0/; /legacy/; /obb/; and /clockworkmod/. Copy clockwordmod folder to your PC and if you need to, flash back to old ROM with old CWM and then move the backup back to /sdcard and then restore.
Using the latest recovery, to find /sdcard while in recovery, you will need to adb to /data/media/. *Note: Make sure to have a copy on your PC, I ran out of space before restoring since it is all in the /data.
Hey! Did you see the easter eggs!!
So not only is there an easter egg when you press the Android version and long press on the jellybean, but if you hit CyanogenMod version, CM planted one too. But did you know that by doing the easter egg and long pressing on the jellybean, you unlock another one! Go to Daydreams under Display in settings and you will see BeanFlinger!
My sound is really low or really high when I am using headphones!
If you are having really low or high volumes while listening with headphones, I recommend Voodoo Sound from Supercurio in the Play Store (Link). This allows you to take control of your volume and change it to your preferences.
I see cm-10.1-xxxxxxxxx-UNOFFICIAL-p4xxxx.zip on Droidbasement, what's the difference between droidbasement builds and nightlies?
The UNOFFICIAL builds on droidbasement are experimental builds compiled by pershoot for testing. It is recommended to flash the nightly builds unless specifically asked to test an unofficial build.

Awesome man and thanks...
Sent from my GT-P7500 using Tapatalk 2

Crazy question, where is dev options located? can't seem to find it anywhere.

Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi

kiladubz said:
Crazy question, where is dev options located? can't seem to find it anywhere.
Click to expand...
Click to collapse
Go to About in settings and hit the Build Number until it says your a Dev now

eddai said:
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
I am going to need more information about Voice calling since I have the Wifi only model. If someone else can chime in about multi user would be great, I haven't tested multi user yet.

nakedninja42 said:
Go to About in settings and hit the Build Number until it says your a Dev now
Click to expand...
Click to collapse
oh, rock on dude, thanks!

eddai said:
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Not sure about voice calling... but as far as user account limits, I don't believe there are any beyond the physical limitations of the internal storage.
Sent from my Nexus 10 using Tapatalk HD

kbluhm said:
as far as user account limits,
Click to expand...
Click to collapse
i've capped it at +3.
https://github.com/CyanogenMod/andr...mmit/b6458e0209ecee044dfb338f9dae98c29efdfcc6

How can I check which bootloader I am currently on?

Dreameagl said:
How can I check which bootloader I am currently on?
Click to expand...
Click to collapse
You can't if you are not sure, then you should flash the one on droidbasement (see OP).

pershoot said:
i've capped it at +3.
https://github.com/CyanogenMod/andr...mmit/b6458e0209ecee044dfb338f9dae98c29efdfcc6
Click to expand...
Click to collapse
Any Solution for creating more? ı need more than 5+. Dont ask why
ı am running unofficial Build of Cm 10.1 (D2dyno's build) and, outgoing voice calls working perfectly, but no incoming calls tablet doesnt rings.
Any idea for your work?
Thanks for Reply.
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi

eddai said:
Any Solution for creating more? ı need more than 5+. Dont ask why
ı am running unofficial Build of Cm 10.1 (D2dyno's build) and, outgoing voice calls working perfectly, but no incoming calls tablet doesnt rings.
Any idea for your work?
Click to expand...
Click to collapse
sorry, i'm not increasing it more at this current time.
that unofficial rom is my device/vendor/kernel specific work + all of the cyanogenmod team's framework/system/build/misc work (from quick scan of the op's thread).
voice calls you are on your own with (the hook is enabled in the framework overlay so people can do what they will with it). you need to flash a separate modem for it. there's a thread around here where discussions were being held for it and people were attempting to fix some stuff regarding it.

Great thread. BTW I don't have KW issue on wingray's gaaps.

me_guitarist said:
Great thread. BTW I don't have KW issue on wingray's gaaps.
Click to expand...
Click to collapse
+1; everything is working great on P4vzw. Thanks to the OP for putting this thread together and to Pershoot for keeping the 10.1 alive and well.

Thanks ninja for creating this thread. The other one has grown too big. Cheers!
Sent from my GT-P7510 using xda app-developers app

Nice work
Wow. Great job Pershoot and team!
Running absolutely wonderful on the Google I/O P7510.
Been following your builds on droidbasement for the last 6 months. Glad to see it in the nightlies now.
Thanks for keeping this device alive.

Why is Google now often not working
Running the nightly with wingray gapps. It runs pretty good .
There were crashing issues with Google Now a while ago as well for CM10. What I'd so special about that app that it crashes way more easily than other apps?

[DEV][ROM][4.4.2][CM11] KITKAT for LG-P500 [WIP][VER-12 OTA]

Updated ROM Version-12 is available now through OTA
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
This Support of the CyanogenMod is Unofficial and the sources are up at Androidarmv6
The fastest, smoothest and more stable Kitkat 4.4.2, Check out this video with installation procedure.
Installation
- First time flashing CM11 to your LG-P500 (or coming from another ROM)?
Root your device and install ClockworkMod Recovery 6.0.4.6 or above (Get it here)
Reboot into Recovery using 3-button-combo (Power+Vol dwn+home)
Do a Nandroid backup!
DON'T WIPE ANYTHING (data/factory reset + wipe cache partition+wipe dalvik+ format system)
Download and flash the ROM from internal sdcard using ClockworkMod Recovery 6.4.0.6
Simply flash in recovery through sdcard or adb sideload,
Follow the Aroma Menu. Finish
Reboot Device
- Upgrading from another CM10.2 or Older ROM
Reboot into Recovery using 3-button-combo (Power+Vol dwn+home)
Do a Nandroid backup!
DON'T WIPE ANYTHING (data/factory reset + wipe cache partition+wipe dalvik+ format system)
Download and flash the ROM from internal sdcard using ClockworkMod Recovery 6.4.0.6
Simply flash in recovery through sdcard or adb sideload,
Follow the Aroma Menu. Finish
Reboot Device
- Instruction for upgrade to new version from older version:
Upgrade version through OTA Updater
In Aroma Menu, Select Wipe Option 1 to upgrade the version.
Must select previous running SD-EXT script and Avoid those apps, which you have already installed in previous version.
Finish and Reboot device. Done!!!
- Increase Device Storage size for more apps (optional)
Install Link2SD app (Link Here)and create "SDEXT4" mount script (dont reboot here), change settings to autolink apps and then reboot device into Recovery (click to see how to create SDEXT4)
Successful boot, now install as many apps as you want
SEX Must read this:
Some people are really lazy to read and they ask the same question without reading this part. So just put something catchy to attract their attention here
1. DON'T SELECT WIPE CACHE AND DATA IN OTA after download of ROM or any updater patch.
1. You have to insert an active Sim into device or run into Airplane Mode otherwise the ROM will be laggy.
2. In Version 9, if you are choosing "AD2Sdx" Script then please have some patient on first boot as it will take 20-25 minutes. This script will flash the all apps in data storage first and then move to external storage (SDEXT) but after first boot everything will be normal. Also note this script mean for Class 10 sdcards. Although I have put some tweak to increase the reading speed of below class 10 sdcards but still writing speed will be slow. So those using 2gb or below class 10, will face a little slow this rom with Ad2sdx.
3. To use version 8, you must have to select one apps from "Music" and "Enhancement" section.
Working List
Quote:
Code:
#include <std_disclaimer.h>
/*
ALMOST EVERYTHING NOW :)
*/
Not Working List
Code:
#include <std_disclaimer.h>
/*
After Wifi hotspot tethering require reboot to use Wifi
Other, You have to find it ;)
*/
XDA: DevDB Information
Cyanogenmod 11 for Optimus One, a ROM for the LG-P500
CREDIT:
Google, CM Team, @hephappy aka AndroidMeda Jenkins; Link2SD (Bulent Akpinar); @amarullz, @M3nti0n, @dipesh1502 and all LG-P500 XDA community
ROM OS Version: KitKat 4.4.2
Based On: CyanogenMod
Kernel Source: https://github.com/androidarmv6/android_device_lge_p500
Thread created by @mukulsoni on 29-12-2013
__________________________________________________________________________
Please hit THANKS button, its motivate developer to work more enthusiastically

Download Links
ROM:
Version 12: http://forum.xda-developers.com/showpost.php?p=52827619&postcount=1540
Changelog:
* Now get more internal storage Dalvik2Cache script (Must select this in Aroma) Thanks @HardLight
* LG G2 interface
* Fixed Gallery error
* Fixed Google+ error (Don't Update with latest version)
* Updated Link2sd and Google Now (Cricket and other games scores)
* Now get more internal storage Dalvik2Cache script
* Option for Statusbar Clock as Power Button
* Added more tweaks to make rom faster
* Added more languages dictionary
* Speed Tweaker (Feel like GB speed)
* V6 super charger include (Makes ROM super faster)
* Many more...About phone
* Many more...
Click to expand...
Click to collapse
VERSION 11: http://forum.xda-developers.com/showpost.php?p=52261911&postcount=1466
Changelog:
* Now get more internal storage Dalvik2Cache script (Must select this in Aroma) Thanks @HardLight
* LG G2 interface
* Option for Statusbar Clock as Power Button
* Added latest Link2SD app
* Added super tweaks to make ROM more faster
* Improved Camera
* SD-EXT scripts added : Link2Sd and A2Sdx
* Speed Tweaker (Feel like stock rom speed)
* V6 super charger include (Makes ROM super faster)
* Updated Changelog in Settings>About phone
* Many more...
Click to expand...
Click to collapse
Version 10.3 Delta: http://forum.xda-developers.com/showpost.php?p=51797156&postcount=1346
Changelog:
Deleted Halo feature (gives many error in version 10.2)
Fixed "package Installer" error
Fixed Bluetooth and Wifi tethering error
Increase Battery backup
OnNandroid Backup (Now take device backup without rebooting in recovery. Settings>OnNanroid Backup
Slimmed ROM (Now get more system partition space)
Updated system tweaks
Click to expand...
Click to collapse
Version 10: http://forum.xda-developers.com/showpost.php?p=51341582&postcount=1154
Version 9: http://forum.xda-developers.com/showpost.php?p=50929052&postcount=1000
Version 8 : http://forum.xda-developers.com/showpost.php?p=50421197&postcount=772
Version 7: http://forum.xda-developers.com/showpost.php?p=50059740&postcount=597
Version 6: http://forum.xda-developers.com/showpost.php?p=49902334&postcount=517
Updater patch (Flash it over the below patch): http://forum.xda-developers.com/showpost.php?p=49692286&postcount=439
New update patch for Version 5 ROM: http://www.mediafire.com/download/uq2o9wgfl2jii7m/Update-Ver5.zip
Flash it over version 5 only. How to update: Simply flash in recovery, clean cache partition and reboot to system
Version 5: http://www.mediafire.com/download/4ps36exjf1yh9c1/cm-11-P500-Ver5.zip (Jan14 Build)
Patch for updated Camera and Statusbar: http://www.mediafire.com/download/eow6yvehw4r5pxo/Camera+GradientSB-update.zip (13-01-2014)
Updated Version-4:http://www.mediafire.com/download/obeb8zn3g5hpnn3/cm-11-p500-ver4updated.zip (without messaging app)
Version-4: http://www.mediafire.com/download/xa249cvcy8n0az9/cm-11-P500-Ver4.zip (January 7, 2014)
Version-3: http://www.mediafire.com/download/x3lh7uzscrvra8n/cm-11-P500-Ver3.zip
Version-2: http://www.mediafire.com/download/fjsev8ay9543oyn/cm-11-P500-31Dec.zip (Updated Dec31 ver)
Version-1: http://www.mediafire.com/download/a8gwsnd76exyxjq/cm-11-p500.zip (Updated Dec27 ver)
OTHERS
GAPPSLight: http://www.mediafire.com/download/2ppd2ndlcqr187f/GAPPSlight.zip
UserGAPPS: http://www.mediafire.com/download/wav3fq2pq4od5cm/User-GAPPS.zip
User-SystemApps: http://www.mediafire.com/download/kgefvbn2qm0bbeq/User-SystemApps.zip
Updated KitKat Camera App: http://www.mediafire.com/download/nbpbbnd7qr5dx66/Camera-Kitakt.apk (Updated on Dec 31, 2013)
Viber Patch: http://forum.xda-developers.com/showpost.php?p=49717639&postcount=453 Flash in recovery to use Viber without any error
Link2SD: https://play.google.com/store/apps/details?id=com.buak.Link2SD
Now taste the KitKat......yummy

Screen Shots

On the right track here! Breaking things up this way will save a load of headaches. Which cm-11 are you using?
I had not tried making dsp and whisper user apps. Dsp is small enough and I know nothing about using whisper service.
Another candidate would be the filemanager.
Calendar is on Play and should be installed from there. Hangouts2 should also come off Play.
The original sms app is on the ROM unless you removed it. Not everyone want to bother with Hangouts.
Upgrades to Google Search will need to be downloaded from Play and sideloaded because it is technically not compatible for our device.
I (at least used to) need a gmscore on system, even though it is upgraded by the prebuilt and onwards. Just like phonesky needs be on system while Play has given me new ones since then. Waste of space. I will try removing the prebuilt from system and see if it still works.
Main functionality bug is lack of lockscreen widgets option in Settings.apk. Ideas on this?

Dovidhalevi said:
On the right track here! Breaking things up this way will save a load of headaches. Which cm-11 are you using?
I had not tried making dsp and whisper user apps. Dsp is small enough and I know nothing about using whisper service.
Another candidate would be the filemanager.
Calendar is on Play and should be installed from there.
Upgrades to Google Search will need to be downloaded from Play and sideloaded because it is technically not compatible for our device.
Click to expand...
Click to collapse
it is CM-11 Dec 27 build... Have trimmed rom but not removed LatinIME, FM etc. About whisperpush read this http://www.cyanogenmod.org/blog/whisperpush-secure-messaging-integration, Google search and card working through this mode of installation. :highfive:
Working on lockscreen widget only camera is working here for now. GmsCore working here.

are basics such as phone , sms ,calender working fine with no bugs.is it stable when no wifi .3g ,camera are used ??

hariraj96 said:
are basics such as phone , sms ,calender working fine with no bugs.is it stable when no wifi .3g ,camera are used ??
Click to expand...
Click to collapse
Yes, it is working like charm. I using this since Dec 27 and have not face fc or lag, all 3g wifi camera, google play, google card working. Just follow the installation process. :good:

You sure about Wifi and Usb?
Last time I checked Hephappy version and it was not working.
and Will this Rom work without SDEXT4?

aspee said:
You sure about Wifi and Usb?
Last time I checked Hephappy version and it was not working.
and Will this Rom work without SDEXT4?
Click to expand...
Click to collapse
Yes, wifi and usb working, you can use it without SDEXT4 too but you might not be able to taste kitkat fully.

Wow! You're great, i'm going to try it after the New year, when i get to my desktop PC.
Do you think it'll work with mount2sd?
I'm not asking about INT2EXT4, because it wasn't working even with 4.2.x Android.
Keep up!:highfive:

Rom lags, can not use it. How did you use it, if everything starts with a long delay mukulsoni ?

Is link2SD mandatory, or we can use also other a2sd scripts?
I'm used to "inflate" int2extv2+ directly in the rom.

uf0999 said:
Is link2SD mandatory, or we can use also other a2sd scripts?
I'm used to "inflate" int2extv2+ directly in the rom.
Click to expand...
Click to collapse
Other scripts are not working ..so yes ..we should better use link2sd
Sent from my LG-P500 using Tapatalk 2

The AOSP keyboard is fc on me after first boot. How should I fix that?

The rom is good except for some bugs:
1- You should replace LatinIme with the one from jenkins build or ther will be no keyboard showing and no hardware keys except home
2- launcher says PLACEHOLDERTEXT : can't find google search..... and if I install an older launcher it will run but no cards

After initial reboot (all wipes + formats + successful installation of cm11) I noticed the "back" hardware key is not working.
It is capable of killing an app if I enable it in developer options, though, but as a regular in-app back function it doesn't seem to work. Any ideas how to make the back button wrok again?
Another thing, I just noticed that cmfilemanager is not capable of opening zip files and did not think about decompressing the archives (useer and system gapps) beforehand :silly:

xander21 said:
Rom lags, can not use it. How did you use it, if everything starts with a long delay mukulsoni ?
Click to expand...
Click to collapse
jaibar said:
After initial reboot (all wipes + formats + successful installation of cm11) I noticed the "back" hardware key is not working.
It is capable of killing an app if I enable it in developer options, though, but as a regular in-app back function it doesn't seem to work. Any ideas how to make the back button wrok again?
Another thing, I just noticed that cmfilemanager is not capable of opening zip files and did not think about decompressing the archives (useer and system gapps) beforehand :silly:
Click to expand...
Click to collapse
Sorry guys... uploaded wrong zip. Just updated with new one : http://www.mediafire.com/download/a8gwsnd76exyxjq/cm-11-p500.zip
Flash it, follow the process and enjoy.... you will not disappointed now :good::highfive:

mukulsoni said:
Sorry guys... uploaded wrong zip. Just updated with new one : http://www.mediafire.com/download/a8gwsnd76exyxjq/cm-11-p500.zip
Flash it, follow the process and enjoy.... you will not disappointed now :good::highfive:
Click to expand...
Click to collapse
No need to apologize- it is well understood that at this stage it is a privilege to be able to boot in KK to begin with, and as with any new Android version, the first/early adopters usually are prepared for not working stuff.
Probably in a couple of weeks many bugs are fixed and KK ROMs start mushrooming all over the place

borchaniz said:
The rom is good except for some bugs:
1- You should replace LatinIme with the one from jenkins build or ther will be no keyboard showing and no hardware keys except home
2- launcher says PLACEHOLDERTEXT : can't find google search..... and if I install an older launcher it will run but no cards
Click to expand...
Click to collapse
Updated ROM... follow the process, you will get everything..:highfive:

Just flashed. No error, no FC... great ROM! Thanks hephappy, tanks mukulsoni!
Now testing...

[ROM][UNOFFICIAL][6.0.1][E5823/E5803] CyanogenMod 13 for the Sony Xperia Z5C [BETA]

{
"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"
}
CyanogenMod 13 for the Sony Xperia Z5 Compact E5823 and E5803​
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E5823 and the E5803
Code:
*
* Your warranty may be voided !
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Special Thanks
The authors of my books
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for maintaining the Z5P and reminding me that smashing your device can provide a solution
@zacharias.maladroit for maintaining Z5 (sumire)
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
The Sonyxperiadev team for releasing their sources to the public
SonyCM team
And of course the entire CyanogenMod team!
Issues
Laggy back camera
Video Recording on stock camera app (Use alternative)
What has been Fixed
Stability issues
SELINUX
Lag after booting up device
Camera Colors
Bluetooth
Fingerprint sensor
Full brightness
Torch
Double Tap 2 Wake
External SD recognition
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Download the Z5C AndroPlusKernel v31 by @AndroPlus from his official website (Scroll down and select Z5 compact, then chose Z5C_AndroPlusKernel_v31.zip and download it)
Extract the Z5C_AndroPlusKernel_v31.zip
Download our TWRP 3.0.0.0 build for the Z5 Compact (Special thanks to @moonbutt74 for getting the configs right)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 Compact from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 Compact if you haven't downloaded them on your device
Power Off your Z5 Compact and wait about 10-15 seconds to make sure it's off
To enter fastboot hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification light has turned blue you have entered fastboot mode
On your PC flash the boot.img that has been extracted from the Z5C_AndroPlusKernel_v31.zip using fastboot
Now flash the twrp-3.0.0.0 image by using fastboot
Once both of those images have been flashed you can exit fastboot
After exiting fastboot wait for the notification light to turn cyan (it says cyan if you can't read it) at the Sony logo
Once it has turned cyan (it says yellow if you can't read it), you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above, reboot your device and try the step above again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP make a full backup in case you want to revert back to stock (Note: Backing up on external sd still doesn't work yet)
After the backup has completed, go back to the main menu and select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS (But not your photos, music or everything else located in internal storage)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take some time)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable and enter the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How return back to stock via TWRP backup
In CM13, enable and enter the developer options
Enable Advanced Reboot
Hold your power button for about 3 seconds
Select Reboot
Select Recovery and press ok, you will then enter TWRP
If TWRP will ask you to enable read and write, simply swipe to continue
In TWRP select restore and then select your backup, finally swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Lastest recommended CyanogenMod release for the Sony Xperia Z5 Compact E5823/E5803 : ROM | MD5
All my releases can be found here : Android File Host
Gapps (Select ARM64 > 6.0) : Open Gapps
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Changelog
Code:
2016/8/28 - Complete re-write from scratch
- Fixed Bluetooth
- Fixed Fingerprint sensors
- Fixed Camera colors
- Fixed Camera breaks
- Fixed Stability Issues
- Fixed laggy boot
- Fixed torch properly now
- Enabled SELINUX
- Merged with Sony upstream repos
- Synced to the latest CM sources
- Old repos are now deprecated and are planned to be removed in the nearby future
2016/04/17
- Fixed Brightness
- Fixed Torch
- Fixed Double Tap 2 Wake
- Added CPU core optimization
- Added USB gadget support
- Synced with the latest CM sources
-----------------------------------------------
* For devs
- Added Kitakami patcher to manifests
2016/04/12
- Fixed sdcard recognition
- Updated binaries to v4
- Released CM build guide
- Synced with newest sources
2016/04/05
- Fixed GApps
- Partially fixed Bluetooth
- Synced to latest CM sources
2016/03/27
- Fix thermal manager lag
- Fix NFC
- Updated kernel configs
- Added ffmpeg codecs support
- Synced with newest CM sources
-------------------------------------------
* For devs
- Cleaned up suzuran and satsuki tree
- > Moved common media configs to kitakami common tree
- > Moved acdb files to vendor tree
2016/03/24
- Fix In-call Mic
- Add support for the E5803
- Add option to boot into recovery (On purple LED at Sony logo press VOL UP or VOL DOWN to enter recovery)
- Update Thermal manager
- Merge latest AOSP kernel commits
- Sync to newest CM source
2016/03/22
- Fix microphone
- Add settings for camera button
- Add settings for volume rockers
- Fix sound on calls
2016/03/20 - RIP TonyStark, you were a great moderator and we'll all miss you.
- Added Thermal regulation to avoid overheating problems
- Fixed Red flashy frames
- Fixed RIL (SIM detection)
- Fixed Dex pre-optimization
- Fixed Camera
- Fixed Sensors
- Fixed Crash after locking device
2016/03/18 - CM 13 For the Z5 Compact E5823 Released
Source Code
All Source Code can be obtained from here : Sony Kitakami Developer Organization
We gladly accept any developers that are willing to contribute to this project! Please PM me if you are interested in joining this project!
Build from Source
How to build CyanogenMod 13 for the Sony Xperia Z5/Z5C/Z5P from source
Screen Shots
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 Compact E5823 and E5803, ROM for the Sony Xperia Z5 Compact
Contributors
CTXz, zacharias.maladroit, oshmoun
Source Code: https://github.com/Sony-Kitakami
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-03-19
Last Updated 2016-08-28

Q&A
Q&A
Q: Does this work on the Z5/Z5 Premium
A: No, this ROM is for the Z5 Compact only. Please visit the appropriate forum for your device as the appropriate CM version for your device is located there
Q: Does this work on E58XX
A: This ROM was build for the E5823 and E5803, flash it on a different Z5C model at your own risk! If it works, please report it to me so I can update the thread
Q: How long until <insert issue here> gets fixed
A: ETA's (Short for Estimated Time of Arrival) aren't tolerated well on XDA. Please remember that this is only a hobby
Q: CM becomes really laggy after a few minutes (Should not happen anymore, however if it does then follow the answer)
A: Please check the "How to disable the Thermal Manager" guide in the thread

Z5 Development thread

Really looking forward to using this, I just got the Z5 Compact back today after repair.
Thank you!

Very excited to see CM coming for the Z5C.

@CTXz i bought rust, what to do now? :c

H3XabyT3LV said:
@CTXz i bought rust, what to do now? :c
Click to expand...
Click to collapse
Please PM me rather than posting on my threads, this isn't really Z5C related, is it?

@CTXz Well done!
I have been following your CM for Z5 & Z5C work closely and I'm excited to see your progress! Glad to have you on the Z5C thread!

Joeisgood99 said:
@CTXz Well done!
I have been following your CM for Z5 & Z5C work closely and I'm excited to see your progress! Glad to have you on the Z5C thread!
Click to expand...
Click to collapse
Hey, glad to see you reply. I'd really like to say thanks for your recovery since it supports the fstab that I use.
Cheers!

Hell yeah! Finally development for z5c. Btw, doesn't e5803 and e5823 run same software?

my last phone was a oneplus one. I couldn't get used to its size so I switched to the z5c. I kinda started regretting my decision but this makes me really happy.

Not sure if you already know or not, but here's a list of stuff you could do to fix the various issues:
1. RIL: you need this repo
2. Sensors: you need https://gerrit.omnirom.org/#/c/16961/ and this
3. Camera: you need this repo
I assume those are the reasons for the issues you listed, since I stumbled upon them myself before
Oh and could you please tell me what you exactly mean when you list "Full brightness" and "Dex preoptimization" under non-functional?

oshmoun said:
Not sure if you already know or not, but here's a list of stuff you could do to fix the various issues:
1. RIL: you need this repo
2. Sensors: you need https://gerrit.omnirom.org/#/c/16961/ and this
3. Camera: you need this repo
I assume those are the reasons for the issues you listed, since I stumbled upon them myself before
Oh and could you please tell me what you exactly mean when you list "Full brightness" and "Dex preoptimization" under non-functional?
Click to expand...
Click to collapse
Hey, thanks allot for the links. This will definitely give you credit once i've tried them out. Any help in such kind is extremely apriciated as it makes development quicker!
Dex preoptinization is ensuring that the boot up takes less time and apps are optimized for the 64 bit architecture. I've had to remove it completely at first from my build environment after experiencing memory related crashes. However, now I changed the vm config to a working one, meaning that I will try to build with dex preopt enabled again.
Brightness isn't at it's max when turned up, I believe the kernel is the reason to this, however I am quite sure where and what to do to fix that.
Huge thanks from me, this could get us a stable ROM in a very short time sir!
Feel free to join our developer organization since you have some experience with AOSP builds for the device I guess

CTXz said:
Hey, thanks allot for the links. This will definitely give you credit once i've tried them out. Any help in such kind is extremely apriciated as it makes development quicker!
Dex preoptinization is ensuring that the boot up takes less time and apps are optimized for the 64 bit architecture. I've had to remove it completely at first from my build environment after experiencing memory related crashes. However, now I changed the vm config to a working one, meaning that I will try to build with dex preopt enabled again.
Brightness isn't at it's max when turned up, I believe the kernel is the reason to this, however I am quite sure where and what to do to fix that.
Huge thanks from me, this could get us a stable ROM in a very short time sir!
Feel free to join our developer organization since you have some experience with AOSP builds for the device I guess
Click to expand...
Click to collapse
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Just happened to find these fixes :silly:
My main interest is PAC-rom, and sadly I don't have enough space on my system to also accomodate CM and try it out
Although I guess there's not that much difference because device trees originate from the same place (aosp)

oshmoun said:
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Just happened to find these fixes :silly:
My main interest is PAC-rom, and sadly I don't have enough space on my system to also accomodate CM and try it out
Although I guess there's not that much difference because device trees originate from the same place (aosp)
Click to expand...
Click to collapse
Wups, out of thanks... Reached the limit
Anyways, like I said feel free to join our organization, you can work on PAC-ROM there if you want.
Cheers

oshmoun said:
thanks for the nice words :angel:, but I'm just a script kiddy (at least according to @someone755 ) when it comes to these stuff.
Click to expand...
Click to collapse
hey im just saying you're a bad script kiddie
not that that's the only thing you are. Especially not with the 600+ hrs on Payday 2
btw please promote me i need donations thx

someone755 said:
hey im just saying you're a bad script kiddie
not that that's the only thing you are. Especially not with the 600+ hrs on Payday 2
btw please promote me i need donations thx
Click to expand...
Click to collapse
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...

CTXz said:
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
Click to expand...
Click to collapse
he was just kidding. we both have a weird sense of humor :angel:
oh and to get back on topic, you might be interested in the following repos, as they contain the commits required to reboot to recovery, like on other xperia devices
https://github.com/SonyCM
it also might be worth it to rebase your work on top of them, as they're maintained by a CM member
I'll see if i can get the stuff i have on my personal github sorted in a good way so they can be easily merged into your repos

CTXz said:
Promote for? Asking for donations without a reason on XDA is quite sad to be honest...
Click to expand...
Click to collapse
Lol don't worry I'm just taking the piss since this part of the forums is unknown territory for me.
You didn't think oshmoun would tag a complete retard? (don't answer that lol)

Much appreciate for all your hard work for the development of z5 series?

[ROM][I9100G][CM13] CyanogenMod 13.0 [UNOFFICIAL][Android 6.0.1][20161120][cm-13.0]

[ROM][I9100G][6.0.1] Cyanogenmod 13.0 [UNOFFICIAL][CM13][Galaxy S2G][CM 13.0]
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device.
This is an UNOFFICIAL build of Cyanogenmod CM 13.0 for Samsung Galaxy S2 G (I9100G). It's build from sources on github.com/cyanogenmod & xdaamg. Standard functionalities are working, when you follow flash instructions. Android 6.0.1 is running smooth on this device. Please read 'problems and not working'-section before you flash cm13.
Disclaimer:
By flashing a custom rom, your warranty is void.
I am not responsible for bricked devices, dead SD cards and so on. You are choosing to make these modifications.
I will not give support for any modifications, frameworks and apps you install.
I will not give support, if you did not follow flash instructions 'word by word'.
Confirmations of working things are welcome. If you found a bug, provide a logcat and description of it.
Click to expand...
Click to collapse
First time installation instructions:
Backup your media files (photo, music, downloads) stored on internal storage
Download cm-13.0 i9100g ROM, OpenGApps (ARM, Android 6.0, Stock) and .gapps-config.zip (details see below) to your sdcard. Extract .gapps-config.zip to same place as your opengapps file on sdcard, usually root of sdcard.
Boot into Recovery. If you don't have TWRP 2.8.7.0, flash TWRP and reboot into twrp recovery. Then wipe system, data, internal, dalvik and cache.
Flash cm-13 rom and OpenGApps Stock with .gapps-config file. It will install opengapps nano and replace aosp keyboard with google keyboard. Reboot system and follow instructions in setup wizard. After finishing all, reboot again.
Set default phone app, before you make your first call. Go to "Settings/Apps/Advanced/Default Apps/Phone App" and set it to "Phone".
Updating CM13 ROM:
Download cm-13.0 i9100g ROM to your phone
Boot into recovery and install cm-13.0 i9100g ROM and reboot system
Download I9100G CM13.0 ROM UNOFFICIAL:
Download i9100g CM13.0 20161120
Support development of this rom:
If you find this rom useful, consider donating please. Your donation helps to keep this rom alive and is your chance to support development.
Download Google Apps:
Open GApps (recommended: ARM, 6.0, Stock (Download))
Download .gapps-config file:
Download .gapps-config
Status:
Android-Version: 6.0.1
CyanogenMod-Version: 13.0
Security patch level: 01.11.2016
Kernel-Version: 3.0.31
SELinux: permissive
Standard functionalities working:
Telefon, sms, wifi, data 2g/3g, grafics, sensors, compass, location, camera, flashlight, vpn, wifi hotspot, playstore.
Special features:
TWRP IsoRec: Booting TWRP from recovery partition
F2FS: Flash-friendly file system supported (data, cache, sdcard)
zram support: virtual swap compressed in RAM
Best standby times by supporting app standby (doze)
Higly responsive, smooth gui
First i9100g android 6.0 rom and only one which still gets updates
Changelog CyanogenMod & i9100g device tree:
CM13.0 changes
20160523: display autorotation fixed & audio low latency deactivated & app standby activated (energy saving)
20160528: internal camera fixed; Snap camera from cyanogenmod project activated
20160609: camera stability improvements, gps patch, bluetooth config, audio config
20160611: camera whatsapp fixed, isorec recovery boot support
20160616: removed 'extended font footprint' and disabled journaling on system to save some space, AudioPackage13 added, board hardware class from omap4-next added: display color calibration, h264 profile set
20160618: Sound config test (based on other omap4 devices) -> removed, still sound distortions
20160830: gps fixes
20160903: bluetooth connection stabilty -> see FAQ below and disable battery optimisation for your audio player to fix bt
20160916: added f2fs fstab entries to support flash friendly filesystem on more partitions
20161019: power profiles: support performance & energy safe profiles; security fixes: android patch level 01.10.2016; device tree sources cleaned up; add hardware samsung cmhw
20161120: security fixes (kernel & device tree), sound testing
Not supported:
Manual selection of network carrier is not supported -> use automatic network search
Snap camera supports picture and video recording. Panorama mode is not supported (but working with some other camera apps). Digital zoom is not supported.
Problems and/or not working:
Sound distortions with some codecs or sample rates. Tested amazon video, amazon music and google music successfully. Also some mp3 files. But in some situations or with some codecs, sound/ringtones etc. sounds like with some kind of electronical effect. -> try different equalizer settings or use cm12.1, if audio quality is not accectable for you
GPS does not find all satellites, you will maybe not get a location fix with gps (reported by users) -> use cm-12.1. This bug could be solved by replacing proprietary libstlport.so with opensource external libstlport.so, but this breaks simcard detection atm.
When you found a bug/error/problem, post a logcat with description. Postings without these informations are likely to be ignored.
FAQ/Solutions:
Root: To enable root, go to settings/about phone and touch build-number seven (7) times. This will activate developer settings. Then go to settings/developer settings/root access and set it to apps only or apps and adb.
Recovery: Cyanogenmod 13.0 comes with Cyanogen Recovery by default. But this rom supports booting IsoRec TWRP recovery, read second post for more information how to use it. If recovery is not working, enter 'download mode' and flash a new recovery via odin, for example TWRP 2.8.7.0.
Bluetooth connections to headsets, speakers -> When you have connection problems try to disable battery optimisations for your audio app: go to settings/battery, select menu on top right and choose 'optimisation', in dropdown menu choose 'all applications' and select your music player app (for example cyanogenmod eleven), select 'not to optizime'. Reboot after you set this option.
Android security patch level: Google releases monthly security updates. Security bulletin is split into different security patch levels. Relevant for i9100g cm12.1/cm13 is only first part of this bulletin, for example patch level 2016-09-01, with changes in aosp source code. These issues gets fixed with an updated cm12.1/cm13 rom. Other issues mentioned in drivers and kernel are device specific. We could be affected by this errors or similar bugs, but only manufactor of this hardware could update (driver) binaries (and they don't care about old devices). The same with kernel bugs, i9100g kernel could be affected by this errors too, but there are no active kernel developers for this device and so these problems will normally stay unfixed.
Galery app: If galery app does not display all your albums/pictures/video for example of your sdcard: Open file explorer and search for a file '.nomedia' on your sdcard root/picture/video folder. If it's there, delete it. It tells android not to index this folder. Then make a new folder on your sdcard, for example 'media'. Move your pictures/videos/music to your new media folder. Mediascanner will scan these files automatically now and they should be visible in galery app.
Optimisations:
Low app space: If you are low on app data storage, think about repartitioning your phone storage. 4 or 6 gb should be sufficient even for many apps. Follow instructions in this thread. Alternatively use Lanchon Repit Tool.
Battery: Display and data connections/syncing use most energy. I suggest to reduce display brightness to a minimum and switch off adaptive brightness. Also switch off background data connections/syncing for apps you don't use or which will be updated when you really use it.
After first flash give phone some extra time to complete all tasks, even when it's reacting already to your inputs, it's working hard. Wait some minutes. It's also a good idea to do another reboot after some time. This solved some problems in the past.
Force closes: If you are experiencing force closes try first to clean cache/dalvik cache in recovery. If it's still not working, go to settings/apps, find the offending app and clear data. Still no solution? Then do a clean flash with factory reset and re-install apps without importing backups.
TWRP Recovery only signed:
Download TWRP 2.8.7.0 Recovery only signed
Download TWRP 2.8.7.0 Recovery only signed TAR for Odin
CM13 ROM archive (outdated, you should only use it, if latest build is not working for you):
Download i9100g CM13.0 20161019
Download I9100G CM13.0 20160916
Download I9100G CM13.0 20160903
Download I9100G CM13.0 20160830
Download I9100G CM13.0 20160731
Download I9100G CM13.0 20160616
Download I9100G CM13.0 20160611
Download I9100G CM13.0 20160609
Download I9100G CM13.0 20160528
Download I9100G CM13.0 20160515
XDA:DevDB Information
I9100G CyanogenMod 13.0 Android 6.0.1 cm-13.0, ROM for the Samsung Galaxy S II
Contributors
adxamg
Source Code: http://github.com/xdaamg
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20161120
Beta Release Date: 2016-11-20
Created 2016-05-18
Last Updated 2016-12-10

FAQ
How to use TWRP recovery with i9100g cm12.1/cm13 roms:
This rom supports IsoRec TWRP recovery. It means, it can boot a recovery from another, usually unused partition on i9100g phones. Default recovery of cm13 is cyanogen recovery. When you flash isorec twrp recovery to recovery partition, rom will boot twrp recovery. Isorec recovery will stay there until you overwrite/delete your recovery partition. Updating rom will not touch isorec twrp recovery.
Installation instructions for i9100g isorec twrp recovery:
Download i9100g IsoRec TWRP 2.8.7.0 Recovery to your pc
Download & install Minimal ADB and Fastboot on your pc. Ask google to find it.
Copy twrp_isorec_i9100g_20160612.img to install dir of adb/fastboot.
When you connect phone to your pc it should be detected. If not, install samsung usb drivers. Then connect phone.
Activate USB debugging in developer options and confirm message on phone
Open a command prompt and change to install dir of adb/fastboot
to backup recovery image follow instructions in this thread under section 2: dumping rom partition (optional)
Copy & paste following commands, don't mistype, you can damage your phone with a wrong command here!
adb root
adb push twrp_isorec_i9100g_20160612.img /dev/block/mmcblk0p6
It should be flashed in some seconds. Wait until it's finished. When you restart to recovery now, you should see twrp, booting from recovery partition.
To remove isorec recovery, flash 'overwrite_isorec.img' with adb push command.
Some screenshots of i9100g cm13:
{
"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"
}

Beta ? Wait 4 review

Give us some screenshots <3

Very strange sound became . What is the distortion . Please fix it.

<3 adxamg (no homo^^) big thx for making yet another Android update possible for this old phone!
Aditya18 said:
Beta ? Wait 4 review
Click to expand...
Click to collapse
You find some Information about it in the Alpha thread. Else you are welcome to try it out yourself and give us some Feedback
ROODYK said:
Very strange sound became . What is the distortion . Please fix it.
Click to expand...
Click to collapse
Is that a bug Report? Because that's not how it's done. That's not how any of that is done! And what's with that tone?
If you're trying to Report a bug, maybe try to be specific? Where does it happen? Headphones? Speakers? Music? Ringtone? What exactly did you Flash? You are not helping at all and then you try to Boss the dev around? shame on you!

adxamg said:
[ROM][I9100G][6.0.1] Cyanogenmod 13.0 [UNOFFICIAL][CM13][Galaxy S2G][CM 13.0]
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.1 Marshmallow, which is designed to increase performance and reliability over stock Android for your device.
This is an UNOFFICIAL build of Cyanogenmod CM 13.0 for Samsung Galaxy S2 G (I9100G). It's build from sources on github.com/cyanogenmod & xdaamg. Standard functionality is working, when you follow flash instructions. Android 6.0.1 is running smooth on this device.
Disclaimer:
First time installation instructions:
Backup your media files (photo, music, downloads) stored on internal storage
Download cm-13.0 i9100g ROM, OpenGApps (ARM, Android 6.0, Stock) and .gapps-config.zip (details see below) to your sdcard. Extract .gapps-config.zip to same place as your opengapps file on sdcard, usually root of sdcard.
Boot into Recovery. If you don't have TWRP 2.8.7.0 first flash TWRP and reboot into recovery. Then wipe system, data, internal, dalvik and cache.
Flash cm-13 rom and OpenGApps Stock with .gapps-config file. It will install opengapps nano and replace aosp keyboard with google keyboard and remove stock camera. Reboot system and follow instructions in setup wizard. After finishing all reboot again.
Set default phone app, before you make your first call. Go to "Settings/Apps/Advanced/Default Apps/Phone App" and set it to "Phone".
Install 'Open Camera' from play store or download it from developer website. It's open source. It will replace stock camera.
Download I9100G CM13.0 ROM UNOFFICIAL:
Download I9100G CM13.0 20160515
Download Google Apps:
Open GApps (recommended: ARM, 6.0, Stock (Download))
Download .gapps-config file:
Download .gapps-config
Support:
If you find this rom useful and want to support me, consider donating me a beer or coffee.
Status:
Android-Version: 6.0.1
CyanogenMod-Version: 13.0
Security patch level: 01. May 2016
Kernel-Version: 3.0.31
SELinux: permissive
Standard functionalities should work:
Telefon, sms, wifi, data 2g/3g, grafics, sensors, gps, compass, vpn, wifi hotspot, torch, playstore. Camera, when you followed flash instructions and installed open camera.
Problems/not working:
Stock camera is not working and replaced with open camera by following flash instructions. Front- and backcamera is functional. Lockscreen icon supported. Messenger apps can use it by clicking 'media icon' (not camera icon next to text field!)
Manual selection of network carrier is not supported -> use automatic search
When you found a bug/error/problem, post a logcat with description.
Changelog CyanogenMod:
CM13.0 changes
Additional information/FAQ/solutions for common problems:
To enable root, go to settings/about phone and touch build-number severl (7) times. This will activate developer settings. Then go to settings/developer settings/root access and set it to apps only or apps and adb.
If galery app does not display all your albums/pictures/video for example of your sdcard: Open file explorer and search for a file '.nomedia' on your sdcard root/picture/video folder. If it's there, delete it. It tells android not to index this folder. Then make a new folder on your sdcard, for example 'media'. Move your pictures/videos/music to your new media folder. Mediascanner will scan these files automatically now and they should be visible in galery app.
Cyanogenmod 13.0 comes with Cyanogen Recovery by default. If your recovery is not working, enter 'download mode' and flash a new recovery via odin, for example (TWRP 2.8.7.0.
If you are low on app data storage, think about repartitioning your phone storage. 4 to 6 gb should be sufficient even for many apps. Follow instructions in this thread.
About battery: Display and data connections/syncing use most energy. I suggest to reduce display brightness to a minimum and switch off adaptive brightness. Also switch off background data connections/syncing for apps you don't use or which will be updated when you really use it.
After first flash give phone some extra time to complete all tasks, even when it's reacting already to your inputs, it's working hard. Wait some minutes. It's also a good idea to do another reboot after some time. This solved some problems in the past.
If you are experiencing force closes try first to clean cache/dalvik cache with recovery. If it's still not working, go to settings/apps, find the offending app and clear data. Still not the solution? Then do a clean flash with factory reset.
Updating ROM:
Currently no updates available
TWRP Recovery signed:
Download TWRP 2.8.7.0 Recovery only signed
Download TWRP 2.8.7.0 Recovery only signed TAR for Odin
Older builds (outdated, you should only use it, if latest build is not working):
-
XDA:DevDB Information
I9100G CyanogenMod 13.0 Android 6.0.1 cm-13.0, ROM for the Samsung Galaxy S II
Contributors
adxamg
Source Code: http://github.com/xdaamg
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 20160515
Beta Release Date: 2016-05-15
Created 2016-05-18
Last Updated 2016-05-20
Click to expand...
Click to collapse
First thank for your hard work to bring new android for our devices. I installed and have some bugs:
- Open camera can't save the pictures.
- sometime when i make a call, i can't hear anything voice. When restart phone, it's normal.
- I got bootloop when flash the TWRP 2.8.7.0
Hope you'll fix it on next release
Sorry for worse English ?
Sent from my GT-I9100G using XDA-Developers mobile app

Thx a lot for this great work. :good:
The Problems I have:
- Screen is not rotating. Only few times after
Reboot it works.
- Music over BT doesn't work sometimes.

Build cm13 20160523 is online.
- updated cm13 sources
- display autorotation fixed
- audio low latency test
- app standby/doze activated, testing battery life, first test seems to improve battery life when phone is dozing

does the camera works for video calling in skype??
---------- Post added at 12:34 PM ---------- Previous post was at 12:30 PM ----------
jimmylin86 said:
First thank for your hard work to bring new android for our devices. I installed and have some bugs:
- Open camera can't save the pictures.
- sometime when i make a call, i can't hear anything voice. When restart phone, it's normal.
- I got bootloop when flash the TWRP 2.8.7.0
Hope you'll fix it on next release
Sorry for worse English ?
Sent from my GT-I9100G using XDA-Developers mobile app
Click to expand...
Click to collapse
may be u didnt set permission for storage for the open camera app.just check it in settings

Skype voice calls are working. Receiving videos is working. Sending videos does not work at the moment. Sending videos should work now.

Really nice! are the issues with the camera related to you now using open camera hal instead of proprietary Samsung files in this rom? Seems to be the last big chunk on the way to a fully functional Android 6 room for our phone...
Do you think it will be possible to either include twrp in this rom or use a persistent recovery as with the i9100?
Thanks for your hard work on this phone... much appreciated!
Gesendet von meinem GT-I9100G mit Tapatalk

McConnor said:
Really nice! are the issues with the camera related to you now using open camera hal instead of proprietary Samsung files in this rom? Seems to be the last big chunk on the way to a fully functional Android 6 room for our phone...
Do you think it will be possible to either include twrp in this rom or use a persistent recovery as with the i9100?
Thanks for your hard work on this phone... much appreciated!
Gesendet von meinem GT-I9100G mit Tapatalk
Click to expand...
Click to collapse
I have no plans to include twrp in this rom. Updating rom with cyanogen recovery is working. I used omnirom sources for twrp in cm12.1. But omnirom seems to be half dead.
Open camera is just an app, replacing camera2/snap. Instead of camera2/snap, open camera is able to use i9100g camera. Below this i'm using ti_omap4 sources from cyanogenmod now, because old camerawrapper does not work in cm13 anymore. ti_omap4 source is used for galaxy tab devices for example. Unfortunately i did not find a way to get it working with i9100g. Any ideas whats wrong? I would be happy to integrate a patch that will make camera.omap4 working.
For me, phone is fully functional. If somebody don't think so, stay at cm12.1 or any other rom you like.

Hi @adxamg Nice work for CM 13.
I got problem with SDCard. SDCard got Coruppted if i insert in device, but i tried in my PC, its work perfectly.
Can you explain that ? thanks

the file .gapps-config.zip cannot be extracted, could you upload again?

donduckt said:
the file .gapps-config.zip cannot be extracted, could you upload again?
Click to expand...
Click to collapse
gapps-config.zip work perfectly. Try again

I replaced link to .gapps-config file in first post. Now it's linked to correct .gapps-config file which will remove stock camera as described.
Test build cm13 20160525 is online. I need feedback about camera. Use these two downloads to flash rom and open gapps stock:
Download cm13 20160525 camera test
Download .gapps-config file
Test: 1. Open Snap camera, try to take a photo; 2. Open Whatsapp, try to take a photo
Post a logcat of this test here.

Yeah! Still in Portugal so no testing for me at the moment but I am eagerly watching the thread [emoji3]
Maybe also @Jiangyi could help. He has fiddled around with camera on OmniROM quite a lot and probably has much insight in the underlying code. Unfortunately he seems not around at the moment. Perhaps he emerges again to our help...
Gesendet von meinem GT-I9100G mit Tapatalk

McConnor said:
Yeah! Still in Portugal so no testing for me at the moment but I am eagerly watching the thread [emoji3]
Maybe also @Jiangyi could help. He has fiddled around with camera on OmniROM quite a lot and probably has much insight in the underlying code. Unfortunately he seems not around at the moment. Perhaps he emerges again to our help...
Gesendet von meinem GT-I9100G mit Tapatalk
Click to expand...
Click to collapse
You're lucky!
I had not much contact with him since i build cm12.1. I would not expect this will change now.
So, any testers here? I need logcats from testbuild, posting above. In the meantime i will do some other camera-tests.

adxamg said:
You're lucky!
I had not much contact with him since i build cm12.1. I would not expect this will change now.
So, any testers here? I need logcats from testbuild, posting above. In the meantime i will do some other camera-tests.
Click to expand...
Click to collapse
I can probs only get you the results in a couple hours. It's 2am here
Sent from my OnePlus One using XDA Labs

[CLOSED] [ROM][CUSTOM][O][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte)

{
"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"
}
brought to you by the
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of our LOS 15.1 builds.
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/ or: why are the builds CUSTOM?
The /e/ app store has been removed completely (read FAQ #0 why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules defined by /e/.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is PIE (Android 9) RIL will not work in this ROM. I am trying to fix that currently but while it works when your STOCK firmware/bootloader stack is on Oreo or earlier it stops working when you ever upgraded to pie
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
Latest TWRP build based on Oreo sources (build by myself) can be found here: click
Do a full Nandroid backup before doing anything!
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/oreo/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
nailyk
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-oreo_custom, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: NOUGAT/OREO only - if you have stock PIE installed RIL won't work!
Based On: Lineage OS
Version Information
Status: Beta
Created 2020-08-05
Last Updated 2020-09-09

-
Frequently Asked Questions (FAQ)
Q #0: Why is the /e/ App store not included??? It is GREAT!
Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:
First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.
It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
/e/ makes that not a secret though as you can read here.
So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
.. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".
here some facts:
you cannot get the owner by a whois request
They have a info page here which just roughly describes where the apps are coming from and how
There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
No way for devs to get their apps removed or updated
The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
The full topic where even Gael is talking (not that friendly) is: here
TL;DR:
/e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
Click to expand...
Click to collapse
Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
A relation between is for sure nothing they want to have public as this would cause legal questions.
So the last question is:
Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
TL;DR answer is: who knows...
Background:
/e/ points to LineageOS requirements which need to be met first. LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
No I personally do not have any plans in going official atm. That might change though.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: Will this ROM support / pass SafetyNet?
When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.
Q #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
.-

Reserved

Encryption of storage works?

jw96 said:
Encryption of storage works?
Click to expand...
Click to collapse
Haven't tested yet
Sent from my OnePlus 7T Pro using XDA Labs

I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.

Morceaux said:
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Click to expand...
Click to collapse
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-

steadfasterX said:
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
Click to expand...
Click to collapse
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?

Morceaux said:
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Click to expand...
Click to collapse
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-

steadfasterX said:
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
Click to expand...
Click to collapse
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)

Morceaux said:
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Click to expand...
Click to collapse
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-

steadfasterX said:
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)

Morceaux said:
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Click to expand...
Click to collapse
https://sfirmware.com/samsung-sm-j530f/

goodjob

steadfasterX said:
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged

jaggedN said:
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
Click to expand...
Click to collapse
Oof .. Well i don't have much time atm but i need that phone as my navigation device for my motor bike. so i need to fix it
Sent from my OnePlus 7T Pro using XDA Labs

New eOS v1-oreo build *20200909* has finished!
Changes:
- kernel: commits
- Device tree: commits
- Common Device tree: commits
Download: see OP
Known issue with the OTA Update!
Unfortunately it will work with the next update first. There was a missing entry in the fstab causing the install to fail. You can still use the Updater to download the package though!
1. Open Settings —> System
2. Expand Advanced & select Updater
3. Refresh if not listed already
4. Download
5. Reboot to TWRP
6. browse to /data/lineageos_updates/ and select the zip from here
BREAKING NEWS
I've decided to create a Telegram group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
The second one will also show sha256sums of every build for those who need it.
.-

No more OREO builds!
The reason is that almost everyone has flashed stock PIE in the meanwhile and I switched to Android 10 already. A10 works great so far and so backporting whatever is needed is not worth it.
Check it out: j5y17lte - Android 10 / Q
Thread closed.
.-