[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
Related
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?
Sailfish OS for Nexus 4
The porting effort is now continued by community: http://forum.xda-developers.com/nexus-4/development/rom-sailfish-os-community-port-t2969823
{
"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"
}
This is Jolla's port of Sailfish OS for the Nexus 4 (check full address in post #3)
It features a gesture-based user interface with a unique design and ease-of-use in mind.
For more information about Sailfish OS please head over to sailfishos.org.
This is not an Android ROM, this is a different base of an operating system called Linux, running the GNU C library (glibc).
It only uses parts of Android for hardware enabling (drivers).
Special Thanks to the Nexus 4 porters, carepack who took over as community's release engineer, MultiROM author Tassadar, Jolla sailors especially MSameer for camera experiments, early porters Stskeeps, lbt, thp, alterego, faenil, LEDs spiiroin, sensors lpotter, USB phdeswer, the HADK team, the Mer Project, the Nemo Project and all the fine people over at #sailfishos-porters
Release Notes:
This release is based on Sailfish OS 1.0.8.19 (Tahkalampi).
The Nexus 4 port is considered to be of beta quality.
Though depending on your usage it might be stable enough for daily use.
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
MultiROM ≥v28 ability is in the image. See options of how to layout your MultiROM in #2 post below.
Alternatively, just have it as your primary ROM:
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/android/nexus/images#instructions
b. Download links can be found here: https://developers.google.com/android/nexus/images#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-ea/sailfishos-mako-release-1.0.8.19-EA4-demo-content.zip
* Install CyanogenMod 10.1.3 on your Nexus 4
a. Follow the instructions at: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* After flashing the "cm-10.1.3-mako.zip" file, flash the Sailfish OS .zip file in the same way ("on top of it")
* Reboot bootloader, Sailfish OS should boot and be visible
We recommend reading through http://jolla.com/guide/ -- some parts may not apply to Nexus 4
HW Support status:
(Look for Nexus 4 row): https://wiki.merproject.org/wiki/Adaptations/libhybris
Bug reports, if internet search refuses to help:
First search XDA for keywords. Things like libsailfishapp have already been worked out by this amazing community
Software-related bugs (Sailfish OS): first search http://together.jolla.com . Tag your questions with "community-build"
Hardware-related problems: at the Nemo Project Bugzilla under Hybris-ing component
Please do not contact Jolla Care or Jolla Developer Care, as this is not the Jolla phone
Known issues:
OTA Updates do not work
The camera does not fully work
Android app support is not available (unlike in Jolla phone): please ask about the status for open-source Dalvik runtime framework on #sailfishos-porters on irc.freenode.net and also check this XDA Thread
All remaining: In Bugzilla
Check changelog in #2 post.
Last Updated 2014-12-11
Changelog:
Read Sailfish OS release notes:
https://together.jolla.com/question...in-upgrade-to-software-version-11038-uitukka/
https://together.jolla.com/question/50175/release-notes-software-version-10819-tahkalampi/
Release notes/Known issues in EA4:
* EXPERIMENTAL: Jolla Camera
** Viewfinder stream freezes after ~20secs so be quick to take a photo
** Video recording is not available
* EXPERIMENTAL: orientation sensor works (no PS or ALS)
** was stable during tests, but we'd ask community to attempt making HADK hybris-11.0 port of mako instead, for hopes of better sensors integration
* LED notifications work
* Devicelock including Allow untrusted software
* MultiROM support (min. v28) New to MultiROM? Read here.
** you must have Android 4.2 and cm10.1 as your primary ROM
** Instructions: http://forum.xda-developers.com/nexus-4/orig-development/mod-multirom-v24-t2472295
** two alternatives for hackers:
*** 1. you can still have Android 4.4 -based secondary ROMs, provided you inject required firmwares (check MultiROM threads)
*** 2. you can have Android 4.4 as primary, flash (physically into phone's partition) modem image from 4.2 (0.84 tested OK), and still see things working in SF and CM (tested). It is not yet supported to inject radio.img for SailfishOS only (via MultiROM menu button)
* MultiROM's awesome side-effect fix - ability to power-off the device (thanks to isolated primary ROM)
* Once USB cable plugged, it gets assigned a DHCP address by an internal phone's DHCP server
* Available USB modes: Developer Mode, Charging; untested: Tethering, Mass Storage, PC Connection
Release notes/Known issues in EA3:
* EXPERIMENTAL: Jolla Store is now available, you'll need to register with your Jolla Account
** NOTE: Booting Nexus 4 with SIM first, and then removing SIM (or vice versa) may cause Jolla Store to see it as two different devices and cause potential breakage. Please stick to either SIM available or not when running Sailfish OS on Nexus 4.
** There may be a bug with oFono RIL support that makes it not report IMEI value causing this and will be sorted out in a later update.
** DISCLAIMER: Using Jolla Store with Jolla Account might break applications on your other devices, use it at your own risk!
** Android support is not available from the Store, even if you can see Android apps listed (those will be removed eventually from store view)
** This functionality means that image comes with only minimal set of pre-installed apps. Use Store to download the ones you need.
* The backlight is dark during first launch, but can be fix by switching the currently-not-working ambient light sensor off (uncheck Settings->System->Display->Adjust automatically)
* When display is blanked, power management sets WLAN to the lowest speed state
** Can be noticed in a SSH-over-WLAN session
** Chat notifications may arrive with a slight delay
Fixes after EA2:
* Watermark removed
* Phone-call audio volume can now be changed with the help of volume buttons
* Improved responsiveness when waking phone up with the power button
* Settings->System->Developer Mode or About Product do not freeze anymore
* Reverted to the original (non-Silica) Fingerterm
Fixes after EA1:
* Phone-calls with audio work
* Timers and alarms (with device powered on) work
* HTML5 video+audio works in Browser (tested splash on http://jolla.com )
* Update is based on Sailfish OS version 1.0.5.16
Release notes/Known issues in EA2:
* If not auto-detected from SIM, set-up mobile internet data settings via Settings->System->Mobile network->(long tap on the first toggle-item under "Mobile data" section)->(enter settings given by your operator)
Nexus4-specific known issues reported by the adopters:
* Chinese text input not working
* Localhost name is shown as Jolla
* Switching between the online and offline status in the status information setting takes very long and often doesn’t switch properly
* Google contacts which are put together with different information, are now split up into several contacts in Sailfish
* The battery display seems to be a bit buggy because it loses about 15% from one second to another
* The calendar overview when filled with events seems to be a bit laggy
* The email push is not working correctly, I do not receive any emails until I push the refresh button
* Splitting words in the German translation: e.g. in the open apps on the home screen it says: "Kurzzeitmesse" and in the next line the missing "r"
* NOTE: all other Sailfish OS issues have already been reported on TJC - http://together.jolla.com - and many of them were fixed in this 1.0.5.16 release
Release notes/Known Issues in EA1:
* There has been no throughout testing of telephony related functionality (roaming, airplane mode, etc) and any use of this functionality is at your own risk
* ALS and PS Sensors, Reset device, Bluetooth, USB MTP, Bluetooth, WLAN hotspot, Camera video recording, and video playback is not supported
* The image SW is not currently upgradeable, nor is any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, or word prediction for virtual keyboard preinstalled
* This image does not include any typically licensed multimedia codecs (MP3, etc), HERE maps, Android application compatibility layer, Microsoft Exchange support, or word prediction for virtual keyboard preinstalled
* It is not possible to double-tap to wake up the device
* FPS drop while scrolling in homescreen due to non-batching when rendering of application icon grid
* Icons/graphics appear unproportionally small in browser toolbar, time select widget, and Settings favourite icons
For even more curious ones: there has been a huge community porting effort to numerous devices, news and photos can be found here: http://forum.xda-developers.com/showpost.php?p=54302138&postcount=2
Jolla's relnotes:
Dear early adopter of Sailfish OS for Android devices. This is important - read this whole mail through and follow all steps exactly as written.
IMPORTANT: If you choose to publish this mail through blogs, news sites, forums, or others, quote it as-is and in complete form ONLY, or people's devices may be at risk.
We're happy to publish the fourth Early Adopter Release of Sailfish OS (1.0.8.19) for Nexus 4 (mako) to you.
We have also released the EA2 version of the Sailfish OS Hardware Adaptation Development Kit (HADK), as per earlier email.
This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see the release notes below. We are excited to get all of you properly included in the early stages of the project. Do note that this Sailfish OS image is strictly for personal and non-commercial usage only.
We've prepared a 'demo' version of the image which contains the kind of preinstalled 'marketing' content and the core apps used for demonstrations - this helps you quickly get a feel for all the interactions that are avalable on a device that has been used for a while but isn't really what you want for personal use. You can however cleanly remove the demo content.
We want to build a community around Sailfish OS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is work-in-progress and not a productised release. It is important for Jolla that correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product. If you do demo videos, take advantage of our new 'demo content' image (check availability for your device) that has pre-set contacts/imagery/messages/etc to show full functionality of Sailfish OS.
WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.
NOTE: You will lose your on-device data (including /sdcard), so make a proper backup and make sure to copy that backup to your PC.*
NOTE: Make sure to read all the release notes below. Please DO NOT contact Jolla Care nor Developer Care for any issues encountered with this Early Adopters build, instead use the following communication channels:
We will all meet in #sailfishos-porters (note, new location) on irc.freenode.net and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at http://github.com/mer-hybris .
You are also welcome to participate in threads at http://forum.xda-developers.com/nexus-4/general about Nexus 4 and Sailfish OS as well as for more general Sailfish OS topics at http://forum.xda-developers.com/jolla-sailfish/general
First
Is the SailfishOS 1.0.8.19 is the newest one?
thlinh130295 said:
First
Is the SailfishOS 1.0.8.19 is the newest one?
Click to expand...
Click to collapse
Yes it is, update9 is out in September
Im on the way to flash stock 4.2.2 and downloading cm + EA4, will report again
---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------
one more question, do it need to use MultiRom? i use TWRP/CWM instead, it's ok?
thlinh130295 said:
Im on the way to flash stock 4.2.2 and downloading cm + EA4, will report again
---------- Post added at 06:59 PM ---------- Previous post was at 06:56 PM ----------
one more question, do it need to use MultiRom? i use TWRP/CWM instead, it's ok?
Click to expand...
Click to collapse
multirom enables you to have multiple ROMs and select them at boot
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
x.0ni.x said:
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
Click to expand...
Click to collapse
what kernel you're using? You have to flash the modem of android 4.2.2 ak 0.84 or google factory 4.2.2 image.
flashable zip of modem:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
and a lttle help from first post:
Download & installation instructions:
* Install adb and fastboot
a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
b. Fedora: yum install android-tools
c. Mac OS X: Install Homebrew from http://brew.sh/, then: brew install android-platform-tools
d. Windows: See http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro for instructions
* Install Android 4.2.2 (JDQ39) to your Nexus 4
a. Instructions here: https://developers.google.com/androi...s#instructions
b. Download links can be found here: https://developers.google.com/androi...ges#occamjdq39
* Download CyanogenMod 10.1.3 for your Nexus 4
a. Perform Factory Reset and wipe contents of the /data/ partition in case of leftovers from previous ROMs
b. The file you want to download is cm-10.1.3-mako.zip
c. Download links can be found here: http://wiki.cyanogenmod.org/w/Install_CM_for_mako
* Download the Sailfish OS for Android image for "mako"
a. The file you want to download is http://releases.sailfishos.org/sfa-e...0.8.19-EA4.zip
b. Another flavour filled with demo content: http://releases.sailfishos.org/sfa-e...mo-content.zip
MultiROM ≥v28 ability is in the image. New to MultiROM? Read here. Check for more DIY alternatives how to layout your MultiROM in #2 post below.
Click to expand...
Click to collapse
x.0ni.x said:
So can I flash cm10.1.3 then the E4 thru multirom and make this as a secondary ROM and expect it to boot up? I tried with E3 and it stayed at the Google boot screen. Or do I have to flash 4.2.2 then cm10.1.3 then E4 to get it to boot? It's insanely confusing. Lil help would be nice.
And can I use this http://forum.xda-developers.com/nexus-4/development/Rome android as my 4.2.2 base before flashing cm10.1.3?
Nix all this. I flashed cm10.1.3 then the EA4. It loaded fine but the problem I'm having is no wifi...do I need to set get a 4.2.2 radio IMG to set for it to pic up wifi? I have a mobile connection. Jus no wifi.
Click to expand...
Click to collapse
Yes, 4.2.2 radio IMG needs flashing. But have no fear, we tested: primary CM11 still fully works with that, including 3G, so I don't even know what are the so-important radio.img differences there
carepack said:
what kernel you're using? You have to flash the modem of android 4.2.2 ak 0.84 or google factory 4.2.2 image.
flashable zip of modem:
http://forum.xda-developers.com/nexus-4/general/ref-mako-modem-collection-t2087227
google factory image:
https://dl.google.com/dl/android/aosp/occam-jdq39-factory-345dc199.tgz
and a lttle help from first post:
Click to expand...
Click to collapse
Awesome!! Thank you!! Found the radio in zip form. Fixing to flash in a few minutes!! I'll get bk to you shortly to let u know if this works! It's coming along tho. At least the camera is working and suck on this OS. Can't wait to see what the next update entails!!
x.0ni.x said:
Awesome!! Thank you!! Found the radio in zip form. Fixing to flash in a few minutes!! I'll get bk to you shortly to let u know if this works! It's coming along tho. At least the camera is working and suck on this OS. Can't wait to see what the next update entails!!
Click to expand...
Click to collapse
Read first post
sledges said:
Yes, 4.2.2 radio IMG needs flashing. But have no fear, we tested: primary CM11 still fully works with that, including 3G, so I don't even know what are the so-important radio.img differences there
Click to expand...
Click to collapse
Flashed radio image zip fill over sailfish os still no wifi connection grrrr so frustrating. I want this to work but lost now
---------- Post added at 11:36 PM ---------- Previous post was at 11:35 PM ----------
carepack said:
Read first post
Click to expand...
Click to collapse
Read it over and over tyvm
x.0ni.x said:
Flashed radio image zip fill over sailfish os still no wifi connection grrrr so frustrating. I want this to work but lost now
Click to expand...
Click to collapse
Which radio.img did you flash? Try another one, too. If you tried 0.84, then try 0.54 instead, or vice-versa. We did not test any others (and newer than 0.84 won't work)
sledges said:
Which radio.img did you flash? Try another one, too. If you tried 0.84, then try 0.54 instead, or vice-versa. We did not test any others (and newer than 0.84 won't work)
Click to expand...
Click to collapse
Tried .83. I'll download the other 2 now. Thanks again.
x.0ni.x said:
Tried .83. I'll download the other 2 now. Thanks again.
Click to expand...
Click to collapse
If you're still unlucky, could you give more info as to how exactly does the WLAN not work?
Do you enable it via Settings->WLAN (click on glowing bulb switch), then use pulley menu to "Connect to Internet" ?
sledges said:
If you're still unlucky, could you give more info as to how exactly does the WLAN not work?
Do you enable it via Settings->WLAN (click on glowing bulb switch), then use pulley menu to "Connect to Internet" ?
Click to expand...
Click to collapse
Flashed 0.54,0.83, & 0.84. Same thing for all 3. And yes that's how I'm TRYING to enable it. But it just says on that screen where u pull it down to "connect to the Internet" "unable to connect to internet. Please restart your phone". I even reflashed the ROM with all 3 radios and still nothing. I as well hit the lil "lightbulb"wifi switch in the row of like Bluetooth, mobile connection, etc. It comes on but I go to the WLAN connection to get wifi going nothing still. Same message.
I flashed 0.84 radio and Wi-Fi don't work too.
Kubino said:
I flashed 0.84 radio and Wi-Fi don't work too.
Click to expand...
Click to collapse
which kernel you're on?
try this one:
http://d-h.st/users/hellsgod/?fld_id=28949#files
If you have as first rom an cm rom then take the file with cm in the name
If you're on aosp android use the one without it. In my constellation it works quite right.
So the steps I've done:
1. I had an android AOSP rom as primary.
2. I've downloaded the kernel without cm in the name. Correct kernel is needed with kexec patch. Is included in the files
3. downloaded sfosEA4 and cm10.1 and radio 0.84
4. In android I've downloaded multirom manager from play store.
so this were my requirements. now the todo:
1. went into recovery and flash the kernel
2. went back into android / multirom manager and do the installation process
3. after some time you'll be back in android and installation is finished
4. reboot into recovery. flash modem 0.84
5. go back to android and look if everything is working
6. then back to recovery again Go -> Advanced -> add rom -> sailfish
7. then you can select 2 zips. first one is cm10.1 and second is sailfish
8. install
9. after that you'll be able to boot sailfish too. everything should be fine.
carepack said:
which kernel you're on?
try this one:
http://d-h.st/users/hellsgod/?fld_id=28949#files
If you have as first rom an cm rom then take the file with cm in the name
If you're on aosp android use the one without it. In my constellation it works quite right.
So the steps I've done:
1. I had an android AOSP rom as primary.
2. I've downloaded the kernel without cm in the name. Correct kernel is needed with kexec patch. Is included in the files
3. downloaded sfosEA4 and cm10.1 and radio 0.84
4. In android I've downloaded multirom manager from play store.
so this were my requirements. now the todo:
1. went into recovery and flash the kernel
2. went back into android / multirom manager and do the installation process
3. after some time you'll be back in android and installation is finished
4. reboot into recovery. flash modem 0.84
5. go back to android and look if everything is working
6. then back to recovery again Go -> Advanced -> add rom -> sailfish
7. then you can select 2 zips. first one is cm10.1 and second is sailfish
8. install
9. after that you'll be able to boot sailfish too. everything should be fine.
Click to expand...
Click to collapse
I have Paranoid Android 4.5 beta 2 as my primary ROM with the kernel you have as well. Also have Miui V5 installed with hellscore B47 as the kernel. I knew this in advanced as I figured Jolle was going to possibly release an update because multiROM had made it possible to finally flash it. Did all the steps provided above to my own knowledge. I think I'll delete the sailfish and start fresh. Hopefully that will work. If not may just be a bug that will be solved I'm sure. As these builds are only EXPERIMENTAL not even Alpha yet. Major bugs are to be expected. So no worries. I just really like the design of this OS outside of android.
EDIT. Are you saying to flash the radio over my primary ROM (PA 4.5 BETA 2 or the sailfish OS)? I flashed over the radio over the sailfish OS not primary. Just to be completely clear here.
Temasek's UNOFFICIAL CyanogenMod 13
{
"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"
}
This is a maintainer thread for the unofficial CM13 made by @temasek, build for the i9300.
Retirement of Temasek
Temasek Device Maintainers - V11 is ready. This is my FINAL build with a development device on hand. I will not guarantee further updates due to no more development device after 20 August 2016.
Click to expand...
Click to collapse
Big thanks to @trader418 for keeping the sources in sync
Important:
Please read carefully the first three posts. They contain important information and give answers to many questions you may have. It is really annoying for me to see questions in the thread which are covered in the initial posts!
There won't be any "magic" fixes: All problems you encounter on official CM13 for i9300 you will also have here!
Important: I am not a developer. I simply compile the builds for the i9300! The hard job is done by the people mentioned in the credits. If you enjoy this ROM show your appreciation to them.
The i9300 is no longer my main device. So don't be disappointed if one day I'll stop building for this device. But don't worry, at the moment there is no need to build for my main device and I need something to do
Quicklinks
FAQ
Features
Disclaimer:
Code:
******************************************************************************************
I take no responsibility for lost data, broken devices or anything else you encountered
during/after flashing this ROM.
You are responsible for what you are using on your devices!
Do some research before doing anything and always make sure to have a backup!
******************************************************************************************
Downloads
ROM:
Before downloading and espacially before flashing one of these files, make sure that you have carefully read the initial posts!
main: Android File Host
mirror (OTA, warning mixed devices in same folder): Basketbuild
Recommended Gapps: OpenGapps Direct: Pico, Nano
Recovery: TWRP official, TWRP unofficial
Installation:
Clean (e.g. when you come from another ROM):
Download all needed files from Download section
Reboot to recovery
Make a backup!!!
Wipe /system, /data, /cache and if possible internel /sdcard as well
Flash ROM
Flash Gapps
Reboot and have fun
If you want root, simply enable it in developer options.
Dirty:
Either download manually the update or use the built-in OTA app to do so. With the OTA app you can also check if the MD5 sum matches to avoid bad downloads and problems while flashing
Reboot to recovery
Make a backup!!!
Flash new ROM version
Optional: wipe /cache and dalvic-cache
Reboot and have fun
Changes:
Temasek's Twitter announcements: https://twitter.com/temasek71
Settings app changes: https://github.com/temasek/android_packages_apps_Settings/commits/cm-13.0
Full Changelog (all things stated as "hlte" can be ignored for i9300): https://github.com/temasek/Changelogs/blob/cm-13.0/cm_hlte-Changelog.txt
Sources:
ROM: https://github.com/temasek?tab=repositories
Device: https://github.com/DarkenedSky94/android_device_samsung_i9300, https://github.com/CyanogenMod/android_device_samsung_smdk4412-common/tree/cm-13.0
Kernel: https://github.com/DarkenedSky94/android_kernel_samsung_smdk4412
Proprietary files: https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-13.0/i9300
Toolchains: https://github.com/ArchiDroid/Toolchain
Credits and big thanks to:
Temasek for the ROM sources
Trader418 for keeping temasek's sources updated after his retirement
arter97 for his optimizations and his f2fs backport
JustArchi for his efforts during CM12.1 and his ArchiDroid optimizations
forkbomb444 for bringing up i9300 to CM13
CyanogenMod for the base
All people who help to keep the good old i9300 alive
MattBooth for OTA app
Lord Boeffla for Boeffla Sound Mod and Charge Levels
If I forgot someone please let me know. I am quite in a hurry at the moment. So my apologies to the affected people.
XDA:DevDB Information
Temasek's UNOFFICIAL CyanogenMod 13, ROM for the Samsung Galaxy S III I9300
Contributors
Darkened_Sky, Temasek, Trader418, Forkbomb444, CyanogenMod
Source Code: https://github.com/temasek?tab=repositories
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod, SlimROM, OmniRom, AICP
Version Information
Status: No Longer Updated
Current Stable Version: 12.3
Created 2016-01-13
Last Updated 2017-03-11
FAQ
Q: How do I get root?
A: Enable it in developer options.
Q: But can I use SuperSU instead of the built-in SU?
A: You can, but many suffer from bootloops when they try. Anyway some were succesful to use it, so search for it in the thread.. If you want to use it, make sure that the built-in SU is disabled in developer settings. Afterwards flash SuperSU. By default after a clean flash built-in SU is disabled, so you can also directly flash SuperSU after a clean flash. Note: bug reports seen after flashing SuperSU are not accepted. Built-in SU works as it should.
Q: Which gapps do I need?
A: This ROM is based on CM13/Android 6.0x/Marshmallow. Therefore choose your gapps accordingly. If you want to use the recommended opengapps, choose the ARM 6.0 version. I highly suggest to use either the pico or the nano package. All other gapps can later still be installed via playstore!
Q: Selinux switch in developer options is not working?
A: This option only works with SuperSU. But think about it, if you really want Selinux to be permissive.
Q: Help! I have a problem/issue/bootloop/....?
A: Please follow these steps:
Make sure that the problem is not already mentioned in either this thread or in the CM13 thread.
Make sure that you can reproduce the problem on your device with absolutely no additional modification and after a clean flash. This includes being on stock kernel and ext4 as all partitions' formats, no xposed, no SuperSU, no theme!
Try to replicate the problem on official CM13. If it appears there, please ask there.
If your problem couldn't be solved with above steps, post here, with an exact description of how to reproduce and if possible with logs.
Q: Is xposed working?
A: Yes but make sure to use the latest and the correct version for Marshmallow. Inform yourself in the xposed thread. Everything is clearly explained there which version you need. The version that works for you on official CM13 will also work here.
Q: Viper4Android is not working?
Normally Viper4Android needs Selinux to be permissive to work correctly. In the case of this ROM by using stock kernel this is not needed, and Selinux can stay in enforcing mode. If you want to use other kernels Selinux will probably have to be in permissive mode.
Q: Can I use custom kernels?
A: Yes. Users which use SuperSU sometimes report problems with bootloops after flashing a custom kernel. Therefore I'd suggest to use built-in SU.
Q: I have added files to my /system partition (not /data !!!), but after each ROM update they disappear?
A: Yes during a flash the /system partition is wiped (not /data !!!). In order to backup your files in /system and automatically restore them use addon.d scripts. Here is a thread by temasek which explains how to do it.
Features
Kernel features:
Boeffla sound don't use it. At the moment it mutes the headphone after reboot and I don't know why.
Charge levels
Compiled with Architoolchain GCC 5.2
Ofast optimizations
F2FS --> Note: The initial commits were made by arter97. CM simply merged them.
Warning this is only for advanced users:
For configuration you have to open the 94kernel script in /system/init.d/ and modify the script to your likings. Simply uncomment the lines by deleting the "'#" and insert your preferred values instead of the "xx" (or aa, bb, cc, yy etc.)
By default all options are disabled respectively are set to their default values. Therefore you can simply set again the "'#" before the code and reboot, and the option will be disabled. You can also delete or replace the file. In the case of boeffla sound, if you disable it, all other values won't have any effect (e.g. if you increased the headphone volume)
a simple example can be seen here:
For example if you want to increase the AC charge rate to e.g. 1100mA.
search the line
Code:
#echo xx > /sys/kernel/charge_levels/charge_level_ac
and change it to
Code:
echo 1100 > /sys/kernel/charge_levels/charge_level_ac
by deleting the "#" and replacing "xx" with 1100
The complete code can be seen here
This script will be executed after each reboot. So in order to see the effect you have to reboot or you can also directly execue the script by typing in terminal:
Code:
su
./system/etc/init.d/94kernel
In /system/addon.d a script is included (94-kernel.sh) which preserves your configuration after a dirty flash.
If something goes wrong simply delete the file (e.g. from twrp file manager) and reboot.
F2FS
Warning! For advanced users only! Don't try this if you are not 100% sure what you are doing!
Make a complete backup of your whole device including the internal sdcard and save it e.g. on an external sdcard. I highly suggest to combine these steps with a clean flash.
Download and flash a recovery which is able to format to F2FS. The one I used was the unofficial TWRP 2.8.7.3. (see download area)
Reboot to recovery
Go to "Wipe" then "Advanced Wipe" then select "/Cache" and click on "Repair or Change File System". Choose "Change File System and select "F2FS". Do the same again for /data. By doing this you will loose all your data and your files on the internal sdcard (which is placed in /data). Note you can do the same for /system but if you flash a ROM it will be formatted again to ext4. But /system is read-only anyway so it has not impact.
If you want to do a clean flash you can simply reflash the ROM and boot and restore your apps and the needed files on your internal sdcard.
You can also try to restore a nandroid backup, but I am unsure if it is from an ext4 backup that it could be formatted again to ext4.
Finally you can check your F2FS status by downloading a Terminal app and type in:
Code:
su
mount | grep f2fs
Now you are on F2FS. If you want to return to ext4 simply do the same process again but choose ext4 instead of f2fs
ROM Features:
ROM compiled with Sabermod GCC 4.9 toolchain
Archidroid Optimizations
All CM features (themes, adjust buttons, skip track with volume etc.)
OTA by MattBooth
Sound:
Boeffla Sound by Lord Boeffla does not work at the moment...
Viper4Android
adjustable volume steps (alarm, DTMF, music, notifications, ringer... helpful if you want e.g. many steps for music but less for ringer)
Enable/disable camera shutter
enable/disable screenshot sound
Statusbar:
Double-tap-to-sleep statusbar to turn display off
Clock: (alignment, color, date, font, size, seconds)
Battery symbols and battery bar
Temperature
Brightness control (slide over status bar to adjust)
Network traffic (incoming and/or outgoing)
Carrier label
Notification count
Disable Headset icon
Disable SuperUser icon
Configure all status bar icons which should be shown/hidden (Cast, Hotspot, Bluetooth, Do not Disturb, Alarm, Wifi etc...)
Notification drawer:
Task manager
Custom header image (see screenshots for example)
Quick and smart pulldown
Show/hide brightness slider and/or brightness icon
Force expanded notifications for apps which supports it
hide immersive mode messages
additional tiles
QS panel background transparency
Lockscreen:
Weather information
additional shortcuts
Change corner shortcuts
Double tap anywhere to put device to sleep
Different fonts for Lock Clock
Enable torch on power button longpress while having screen off
Blur lockscreen
Recents:
AOSP recents (with clear all, memory bar, search bar...)
Omniswitch aslo as main recents possible when home button long pressed
SlimRecents (Recents as sidebar, with many customization like only showing active apps etc....)
ParanoidAndroid PIE control
On-the-go mode: camera as semi transparant overlay over your display
Adjustable Power menu
App circle bar
Gestures anywhere
Configurable Toasts and other animations
Heads-Up White- and Blacklist
Enabled doze --> experimental: The S3 is lacking the needed sensor, but some users report that it works and has positive impact on battery life
Selinux switcher --> not working with builtin su. Only works with SuperSU
maybe another one.
Reserved 3
By the way v.2.3 online.
Have fun
Accepted @arter97 resignation.
You are now the official maintainer for I9300.
Congrats @Darkened_Sky, you are doing a great work for i9300. Bookmarked this page.
Heav you stream shot
Gesendet von meinem GT-I9300 mit Tapatalk
Great man!!!!! ??? tanks for your great job!!!!! What the from the new version???
Sent from my GT-I9300 using XDA Free mobile app
Romversion V2.3 works great, and it is my daily phone: Loving it!!
Amazing what you guys can do with a nearly 4 yearold phone! Thank you very much!!
Can I use the arter97 kernel with this ROM and dual boot anyone?
kush2.0 said:
Can I use the arter97 kernel with this ROM and dual boot anyone?
Click to expand...
Click to collapse
Probably No! As Arter's kernel do not work on MM builds.
---------- Post added at 09:03 PM ---------- Previous post was at 08:57 PM ----------
Okay! Some doubts!
1. Battery life?
2. Boeffla kernel works?
3. Any major bugs?
4. How good is Sound?
Thanks for the rom....
I have a problem with wifi, if i turn wifi on it disconnect after few second and then restart in a loop
sorry for my bad english i hope that you can help me
About time I would say lol
It's nice to see official tamasek here yet again
Congratulations @Darkened_Sky
Pardon me for asking.
What does this ROM provide which stock CM does not?
Sent from my GT-I9300 using Tapatalk
ansh1996 said:
Pardon me for asking.
What does this ROM provide which stock CM does not?
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
many useful additions
Congratulations! You also forgot all famous romb sign that makes this ROM so recognisable ??
Poslano sa mog GT-I9300 koristeći Tapatalk
Finally !!! This is happening.
Congratulation !!!! @Darkened_Sky for become a new official "temasek ROM" maintener for our good old s3 i9300.
i luv u.
Good day everyone! This is really a great rom indeed! But I have a few questions, Can I flash supersu 2.46, and latest boeffla for this kernel?
I tried flashing ROM>GAPPS>KERNEL>SUPERSU but I get a bootloop. Now I have flashed only ROM>GAPPS and it's working fine. But when I flash either BOEFFLA OR SUPERSU I get bootloop. Am I missing something here? Thanks!!
{
"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?
XOSXOS Chameleon ported from infinix Hot 4
{
"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"
}
Disclaimer:
Code:
I'm not responsible if your device gain the ability to fly or
became very cool & awesome after flashing this rom!
You're flashing this at your own risk.
After countless time spent on porting this rom, I present to you the beautiful XOS rom !
What is working?
- Display
- Sound
- WiFi
- Bluetooth
- GPS
- Camera (Primary & Secondary)
- Storage (SD card & internal storage)
- Ril
- FM radio
- Xtheme
- All x apps
- Root
- ... etc
- almost everything
What is not working?
- Flash light toggle in systemUI
Bugs:
- Notification LED is buggy Fixed
- No bugs in the rom.
Changelog:
Version 1:
Code:
- Based port on X557-H807A1-M-160815V57
- Added USB storage in build.prop
- Fixed screen lock password
- Removed apps inside system/vendor to reduce zip size
Version 2:
Code:
- Used better META-INF [SIZE="1"][COLOR="Gray"](Faster flashing process).[/COLOR][/SIZE]
- Used Android one 08082016 kernel.
- Changed mount point names in updater-script to Android one partition table [SIZE="1"][COLOR="gray"](Do not flash on infinix rom partition table).[/COLOR][/SIZE]
- Changed boot logo [SIZE="1"][COLOR="gray"](Used infinix Hot 4 logo)[/COLOR][/SIZE]
- Deleted some system apps to optimize rom for Android one system partition [SIZE="1"][COLOR="gray"](Deleted: Compass, Drive, Hangouts, fingerprint, Feedback, Google play music, User guide, XClub, and XShare)[/COLOR][/SIZE]
- Zipaligned apps to optimize ram.
- Replaced AOSP keyboard with Xperia keyboard by bejunk [SIZE="1"][COLOR="gray"](Keyboard has emotion prediction and skins)[/COLOR][/SIZE]
- Added apps to data/app [SIZE="1"][COLOR="gray"](Google Camera, Xposed installer, Xposed torch)[/COLOR][/SIZE]
- Added power saving tweak in build.prop
- Added low ram configuration tweak in build.prop
- Added Busybox zip.
- Fixed root and [B]added[/B] root package in rom zip [COLOR="gray"][SIZE="1"](No need to flash root after flashing the rom, it is already rooted!).[/SIZE][/COLOR]
- Fixed Notification LED and Charging LED.
- Fixed FM radio messed channels.
- Fixed Camera panorama FC when start recording.
- Fixed Gallery FC when editing a picture.
- Fixed lockscreen wallpaper doesn't change with theme.
- Fixed font not changing bug [SIZE="1"][COLOR="Gray"](report if it doesn't work for you, I'll look into it later) , (Fonts started to work for me when I done te following, [URL="http://forum.xda-developers.com/showpost.php?p=68753824&postcount=153"]check here[/URL]).[/COLOR][/SIZE]
Version 3:
Code:
- Rebased the port on firmware from Infinix Hot4 lite latest update.
- Used kernel from 20160914 Android one update.
- Used all audio libs from Hot 4 firmware instead of Hot 2 audio libs that were in pervious versions.
- Removed Hot 4 kernel logo as it shows glitches in offline charging. [SIZE="1"][COLOR="Gray"]( If you were on version 2, flash logo.bin from stock rom via sp flashtool )
[/COLOR][/SIZE]- Edited Updater-script to be flashable on both Infinix and Android one partition table. [COLOR="gray"][SIZE="1"]( To make flashing esaier for you ;) )[/SIZE][/COLOR]
- Added Google keyboard instead of AOSP keyboard [SIZE="1"][COLOR="Gray"]( For those having "keyboard not showing in setup wizard" issue )[/COLOR][/SIZE]
- Added support for missing Engineer mode *#*#3646633#*#*
- No Finger Print related settings/app on this rom.
- Status Bar is now tinted, no need for "Flat style bars" Xposed module.
- Removed build.prop tweaks.
- Fixed Google Camera, and related force closes in the app.
- Fixed GPS accurecy.
- Updated superSU and BusyBox.
Version 4:
Code:
- Rebased my port on the recent update from infinix (10-January-2017).
- Some other minor changes
- Infinix [URL="http://prtsc.ca/i/6rBcb"]changelog[/URL]
Version 5:
Code:
- Rebased on version 4
- Video bug fix by @memoo_mshm
Version 5.1:
Code:
- Rebased on version 4
- Updated vendor blobs
- Updated Boot.img zImage
- Fixed video bug
Screenshots
- Look in the screenshots tab.
Workaround for notification LED and flash light toggle: (fixed. this is not needed anymore)
- For LED you can try LED blinker notifications or Light flow with root to control LED and flash light, from playstore.
- You can also download any Torch app as an alternative for broken flash light toggle. (use xposed torch)
DownloadVersion 1:XOS Chameleon V.2.0.0Version 2:XOS Chameleon V.2.0.0 (2nd port)Version 3:XOS Chameleon V.2.0.0 (3rd port)Version 4:XOS Chameleon V.2.0.0 (4th port)Version 5 by memoo_mshm:XOS Chameleon V.2.0.0 (5th port)
UpdateVersion 5.1:XOS Chameleon V.2.0.0 (5th port - 5.1)
How to flash?
- Make sure you have Android one partition table (Flash Android one rom via SP flashtool).
- If you don't have a custom recovery, download from here (works well, recommended), or TWRP 3.0.2-1 for Hot 2 from Hovatek and flash it via SP flashtool.
- Reboot into recovery (Power off your phone, wait until it vibrates, hold power button + volume up button simultaneously)
- Wipe everything except SD card; wipe Cache, Dalvik /art Cache, Data, system. Internal memory is optional.
- Flash XOS rom, and Xposed framework then reboot. (Xposed framework is recommended for xposed torch to work with hardware buttons)
- Alternatively you can try dual boot patcher to flash rom. (SD card doesn't work when using the app with MM roms)
- If you are flashing a newer version of the rom no need to wipe anything. (wipe only in this case if you faced problems).
FAQ
Code:
[B]- Can't grant permission for an app?[/B]
Turn off all the draw over other app options.
[B]- Enable Magazine lock screen?[/B]
Go to Settings/Security choose Magazine lock screen.
[B]- Notifications not showing on lock screen?[/B]
Go to Settings/Sound & notification/Notifications choose "when device is locked" then "show all notifications content"
[B]- How to uninstall an app from launcher?[/B]
Xlauncher is a lil bit like EMUI launcher; apps present on home screen, what looks like an app drawer is just a small app to arrange apps from A-Z. So breifely uninstall app from home screen.
[B]- Status bar is not tinted on some apps? (Fixed on version 3).[/B]
This is not a port bug, XOS rom is just like that.. use flat colored bars xposed module to change it. (not needed now)
[B]- Can I use/enable USB OTG?[/B]
USB OTG is not supported by defualt in Hot 2 Android one kernel, we need kernel support for this feature to work.
[B]- How to remove fingerprint app from the app drawer? (removed on version 3)[/B]
You can't. It is inside settings.apk ; it needes to be deodexed and modified to remove it, so just ignore it.
[B]- Is flash light toggle/kernel gestures are going to be fixed?[/B]
No, it is impossible without kernel support.
[B]- I can't find a specific feature/this feature is missing?[/B]
Well, I only port the rom, I do not add features to it, if you can't find a specific feature you used to have on another rom, then simply it is not supported in XOS rom.
[B]- Night mode in camera force closes?[/B]
It is not supported, do not use it.
[B]- I found a bug, can you fix it?[/B]
Give me a logcat of the bug and for sure I'll try to fix it.. So logcat or it never happened.
[B]- When some bugs will be fixed?[/B]
Don't ask for ETA please, some bugs are hard to fix and other are unfixable.
~ Happy flashing ~
XDA:DevDB Information
XOS Chameleon, ROM for the Infinix HOT 2
Contributors
Mysteryagr, Nonta72
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: Android one partition table
Based On: Infinix UI
Version Information
Status: Stable
Current Stable Version: 5
Stable Release Date: 2017-3-22
Created 2016-09-06
Last Updated 2017-3-22
Reversed
Reversed
This is not needed anymore!
Flashing XOS rom on Android one
This is for people who do not want to flash infinix rom, or they don't know how to, or they found it a difficult task!
Some informations:
Android one has a small system partition approximately 1.80 GB, so when you try to flash some roms it will fail because of low space.
Usually the workaround for this is flashing infinix rom via SP flash tool (select format + download) it will change your phone partition table giving you a bigger system parition.
Even though this task is very easy, I get so many messages from people complaining about bootloops, or they couldn't flash infinix rom and they soft bricked their devices.. some other flashed infinix rom via custom recovery and they wonder why XOS bootloop for them * facepalm *
Workaround for you
1- Download XOS rom
2- Unzip it
3- Delete META-INF folder.
4- Download META-INF from attachments, unzip it to rom directory)
5- Go to system/app and delete some apps to free some space, for example you can delete (Chrome, Hangouts, Youtube, & userguide.. etc)
6- Make sure that system folder size is less than 1.80 GB (1.70 or 1.60 GB just in case)
7- zip the rom back
8- Flash it, it should boot.
Notice: current bugs in the rom cannot be fixed, I won't provide further updates.
(One more reserve).
Good job bro!
Gonna share it on my blog.
Nonta72 said:
(One more reserve).
Good job bro!
Gonna share it on my blog.
Click to expand...
Click to collapse
Thanks Bro
Go ahead, the rom won't be possible without your porting method
SD
Guys i have to Ask ..
First of all thanks for your great work ..
Second : i Tried to port it before but i got the SD Card is corrupted bug >> How Did you fix "SD card is Corrupted" bug ..
Please Reply to me .. :angel:
Thanks
Mazen Yasser said:
Guys i have to Ask ..
First of all thanks for your great work ..
Second : i Tried to port it before but i got the SD Card is corrupted bug >> How Did you fix "SD card is Corrupted" bug ..
Please Reply to me .. :angel:
Thanks
Click to expand...
Click to collapse
I didn't test SD Card actually, I flashed the rom via Dual boot patcher and it breaks SD card on MM roms.
Wait for someone to confirm that it is working, if it is.. all I've done is changed the mount point in the updater-script for flashing boot.img
Edit: SD card confirmed to be working.
Which recovery should we use?
emeey100 said:
Which recovery should we use?
Click to expand...
Click to collapse
TWRP 3.0.2 recommended.
LED is working but it is buggy, and charging LED doesn't work.
Frist of all
Good work bro And thanks for that amazing rom It's very smooth
But i found 2 bugs
1- usb connection didn't work with me even usb debugging
2- it same room unable to root
I've tried everything apps and su zips also
mody oka said:
Frist of all
Good work bro And thanks for that amazing rom It's very smooth
But i found 2 bugs
1- usb connection didn't work with me even usb debugging
2- it same room unable to root
I've tried everything apps and su zips also
Click to expand...
Click to collapse
1- USB on which mode? MTP or USB storage? what windows you have?
MTP mode doesn't work on windows 10, USB storage only.
2- it doesn't seem to work, didn't find a solution yet.
why just stuck in booting?:crying:
farrasto7 said:
why just stuck in booting?:crying:
Click to expand...
Click to collapse
Because you didn't follow the instructions, are you on Android one rom?
Android one rom has small system partition
Android one system partition = 1.82 GB
XOS rom size = 1.88 GB
It will fail if you try to install it on Android one rom.
You need to flash Infinix rom first via SP flash tool, it will modify partition table and you will have bigger system partition.
And do not flash root, it either bootloop or doesn't grant permissions.
farrasto7 said:
why just stuck in booting?:crying:
Click to expand...
Click to collapse
The ROM installation takes a lot of time(abt 20min). I almost aborted it. I tot it had freezed because it stood still at 'formating system' but later continued.
The bootloop occurred when I tried rooting the ROM so don't root it yet after installation.
-Please how do we fix the led notification bug?
Toluene15 said:
The ROM installation takes a lot of time(abt 20min). I almost aborted it. I tot it had freezed because it stood still at 'formating system' but later continued.
The bootloop occurred when I tried rooting the ROM so don't root it yet after installation.
-Please how do we fix the led notification bug?
Click to expand...
Click to collapse
I wrote clearly in the thread that flashing take time, I told you to be patient, but people do not read
No fix for notification LED bug at the moment, I'll try to fix it...
Finally, this is great guys.[emoji106] thanks @Nonta72 and all.
Sent from my D5110-X510 using Tapatalk
Smooth ROM
This ROM is by far one of the best for Hot 2, well done.
As with most of the ROM you ported, rooting is unavailable , so might be difficult to fix led bug on our own.
SD card works.
USB mode works...every other thing except LED.
Rocking this at the moment.
negga4al said:
This ROM is by far one of the best for Hot 2, well done.
As with most of the ROM you ported, rooting is unavailable , so might be difficult to fix led bug on our own.
SD card works.
USB mode works...every other thing except LED.
Rocking this at the moment.
Click to expand...
Click to collapse
Flash marshmallow compatible supersu in recovery!
Root is an easy job
Nonta72 said:
Flash marshmallow compatible supersu in recovery!
Root is an easy job
Click to expand...
Click to collapse
Unfortunately, people on facebook reported that it bootloops after flashing systemless root, and normal root is not working; it doesn't grant permissions
I'm looking into it, but not sure if there is something I can do.
The ROM is good with a but, could it be possible toake it easy for everyone to use cos most ROMs work well on android one so flashing is nothing.
But when one had to revert first to infinix ROM meh its not very encouraging knowing d data lose involved.
So if its possible to bring it down pls try.
Or make d infinix ROM flash able on android one...