{
"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?
Related
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.
As Cyanogen pulled the plug on CyanogenMod, this project will continue under Lineage OS
{
"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 ROM is Alpha and not ready for daily use at the moment
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
First I would like to thank the following developers :
@RaymanFX
@CTXz
I used @RaymanFX's T815 image to base my cm 13.0 build on, which in turn is the base of this cm-14.1.
Before you start
THIS ROM IS ONLY FOR THE SM-T810
Code:
*
* Your warranty will 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.
*
About the ROM
Current state of ROM : testing
Everything except what's reported below is working (or not yet reported as not working).
What is Fixed
In '20-09' build reboot to recovery triggers message 'Factory reset'. (wrong messagem not resetting)
Camera not working in selinux enforcing
Front facing camera unable to save image
Bluetooth not working
Hardware codecs not working (fallback to software for mp3/flac works)
Limited wifi 5GHz support (channels above 100 give issues)
Video recording not working? (not tested on T810, reported not working on T815)
What is not working
Important
Fingerprint scanner not working
Minor
Compass is 180 degrees mis-aligned
Mic not working (no input routing)
Instructions
How to install CM13.0
If you haven't run stock Android 6.x, flash that first with odin. (image won't boot without this step)
If you don't have TWRP yet, get it from here : TWRP by ashyx
Download the ROM and the Gapps that are located below to your device
Reboot into TWRP by holding VOL UP + POWER + HOME on boot
In case things go wrong make a backup
After the backup has completed return to home and select Wipe and then Advanced Wipe
Now ONLY tick Dalvik Cache, System, Data and Cache
After ticking those, Swipe below to wipe
Once the wipe has completed return to home and select the ROM
After you selected the ROM swipe below to install it
After the ROM has installed flash the Gapps
When all of this is done, reboot into system, wait, and enjoy CM12.1
How to ROOT
In CM 14.1 Enable the developer options
Select Root access
Select Apps Only
Done
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
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 Samsung 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:
**********
08-12-2016 - Compile with curren cm-14.1 source and [URL="https://review.cyanogenmod.org/#/c/173951"]this patch[/URL].
**********
25-11-2016 - Cm-14.0 is abandoned upstream, limiting uploads to cm-14.1.
- Recompile with camera fix merged in cm sources.
**********
21-11-2016 - Fixed camera (again).
**********
20-11-2016 - Broke camera in enforcing mode (unable to save picture).
**********
17-11-2016 - Recompile from clean tree, camera and youtube work now.
- Confirmed lock-screen-rotate fixed, but only after clean flash and [b]no restore of device ID[/b].
**********
14-11-2016 - First succesful cm-14.1 boot. (Switched project to cm-14.x)
**********
31-10-2016 - Selinux set to enforcing.
**********
12-10-2016 - Disabled telephony that got included regardless specifying I don't want it.
- Fixed several bluetooth issues
- Removed use of old api (v1) by camera
**********
03-10-2016 - First build with cm-14.0 release (previous were staging builds)
- Fixed bluetooth
**********
25-09-2016 - Fixed selinux contexts for camera so it works in enforcing mode
- Fixed front facing camera so it is able to save images.
**********
22-09-2016 - Reboot to recovery now triggers correct message
- 2nd build selinux permissive.
**********
20-09-2016 - 1st cm-14.0 build
**********
Downloads
Latest CM 14.1 build : https://www.androidfilehost.com/?fid=673368273298915423
All CM 14.1 releases can be found here : https://www.androidfilehost.com/?w=files&flid=128488
Recommended GAPPS by opengapps.org : http://opengapps.org/ (I use pico)
Source
Special Thanks to @RaymanFX for releasing his Exynos 5433 source, and already patching the common sources to cm-14.0, without him this ROM would most likely not be possible!
All my sources can be found here : https://github.com/CyanogenMod/android_device_samsung_gts210wifi
Screenshots
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
XDA:DevDB Information
CyanogenMod 14.1 for Tab S2 9.7 wifi, ROM for the Samsung Galaxy Tab S2
Contributors
T_I, Raymanfx, CTXz
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Android 6.x flashed at least once before install
Based On: Cyanogenmod
Version Information
Status: Alpha
Created 2016-09-22
Last Updated 2016-12-29
Nice! Thank your very much for this early build!
I will try it as soon as I am able.
Sent from my SM-T810 using XDA-Developers mobile app
GO hard brother, thanks for all your efforts!
I've been using cm-14 since the 20-9 build, it's running pretty stable, although it's even more stable with selinux in permissive. Looks like some contexts have changed a bit in cm-14. (or the camera and some other routines ignore them)
I found 1 game not playing nicely with Nougat, CSR Classics, but the racing set from CSR work nicely, so I think that's a CSR related bug.
Fixed camera so it'll work in selinux enforcing (not yet activated) and front facing camera is able to save images.
Updated OP.
Awesome thank you!
@T_I Thought you might like 2 comments re your really great adaptation of CM14. Have been using your CM13 nightly downloads for about the last 5 weeks on my T810 and was so pleased with the result that I was slightly hesitant about trying CM14, however this afternoon I took the plunge and installed it as per your instructions. First impression is that I can hardly believe how problem free the installation of the Rom and the Open Gapps 7.0 pico proved to be.
I don't have a huge number of apps installed, about 30, but with one exception they are all performing as scheduled and I couldn't be more pleased, the one app that doesn't work is "Set CPU", there is no "forced closure", no error message, it just doesn't work. There are no forced closures of any other app including the Google Play & Services.
One point which might interest you as you mentioned it in your "OP" notes. I play mp4 movies using the app "MX Player Pro" with the Arm 7 codec installed and they play using the HW+ codec perfectly,
Was initially disappointed that "Theme Chooser" was missing from "Settings" but I can live with that considering how well everything else performs.
Once more congratulations on a really superb "port".
EDIT on 09.27.... @T_I I know this point is insignificant and pure "eye candy" but I love the touch ..... I'm talking about when one connects a usb connection from PC to S2 then the "icon" displayed at top left is now "N" (for Nougat ?) instead of the normal CM icon.
planning to attempt with the t710 again?lol
NalNalas said:
I've had this flashed since last night, and the battery so far has been great. Thanks a ton for this.
Click to expand...
Click to collapse
How much better would you say the battery life has been?
Would also appreciate input from anyone else whos noticed a difference (good or bad) with the battery life.
This ROM is working great so far!!
samsung_xoom said:
planning to attempt with the t710 again?lol
Click to expand...
Click to collapse
I can run a cm-14 build for T710 to see if that one boots.
I can test it and let you know , in my limited time I have lol
This rom is very stable, fast and reliable. The battery life is excelent. I use it as my daily driver since sept. 22!!! (Now i have a sept. 27 update)
Thanks T_I for your hard work!!!
Uploaded new image. @RaymanFX got bluetooth working on his device and the fix works on T810 as well. Also CM switched cm-14.0 from staging to release. There is still work to be done, but build shows working bluetooth (at least I can connect a keyboard and that one works).
I noticed crashing phone app and saw one ExchangeServices crash. (don't use both) Updates OP.
Latest build works wonders after I deleted from /system/app and /system/priv-app all the apks related to telephony/SMS/MMS/etc. for my T810.
EDIT: After some time, it all came crashing down, Play Services didn't like the removal of the packages, and some apps auto-removed themselves. Better wait until dev ships out another build.
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Please don't forget T710....
lewmur said:
Just tried to install the Oct 3 version of this ROM and as soon as it boots a box appears saying "com.android.phone has stopped". No matter how many times I click OK, the message just reappears and I can't get past it. Even have to use the power-home-vol- button combination to power off. This is on a T810 after full wipe, install ROM and install 7pico gapps. Tried the install three times. Coming from cellular south 6 ROM.
Click to expand...
Click to collapse
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
T_I said:
I got the same message, but can mute. Don't know where it comes from. I was working on the staging version of cm-14 and switched to the release version. Looks like there are some bugs left. (it's now less stable then with the staging cm-14)
Click to expand...
Click to collapse
Just by clicking the OK button? Message just pop right back up when I do that.
lewmur said:
Just by clicking the OK button? Message just pop right back up when I do that.
Click to expand...
Click to collapse
I get the message with the 2 options 'stop application' and 'Mute until reboot'. The Mute option silences the warnings, but the app will still misbehave.
Exchange services I've been able to freeze, the phone app is also used for syncing contacts and I think calendar.
{
"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"
}
Android, Reimagined.
For the best experience, view the thread on a web browser like Chromium or Firefox.
Desktop: Brilliant. Mobile: Good. Tapatalk: OK. XDA-Labs: Horrible.
Code:
YOU are doing modifications to your device.
YOU are responsible for what you do.
We are not responsible for any damages, data loss or any type of unexpected,
bad or damaging results! If you have **SERIOUS** problems with this software,
please contact the developers or maintainers. We are not liable for anything
bad that happens to your device.
As long as you are responsible, some companies such as Xiaomi
WILL HONOR IT. Some people occasionally describe them as heroes.
Don't be stupid and bet on that though, please be responsible for what you do.
We prohibit you from overclocking to 1337 GHz thinking, that an OEM would
replace your glorious space heater etc.
We recommend you to take the advice above regardless.
halogenOS Checklist
Although no data should be lost or damaged by the flashing process,
we advise you to follow the following steps if you are coming from another rom:
Please take a full nandroid backup!
Please copy your back up to an external device.
Backing up your Internal Storage is also recommended.
When completed, please clean flash the build!
Although you usually can dirty flash halogenOS over other ROMs, considering the other
ROM has the same Android version, it is not guaranteed. In case of serious
crashes please do a clean flash.
You can dirty flash halogenOS 7 (Nougat) over halogenOS 6 (Marshmallow)
without any problems. Although we can't promise that it will work for you,
we can tell you that this has been tested. In fact, @xdvs23 did a dirty flash of
XOS 7 over XOS 6 and has no problems.
If you get app crashes after dirty flashing over XOS 6 or another ROM, please just
clear the app data of those apps, and it should work fine then.
XOS is a new generation Android-based cutting-edge OS based on the Android Open Source Project and Code Aurora Forum releases.
What is XOS?
halogenOS, also known as XOS is a new Android ROM which ships with the global aim to
become a modular ROM which keeps as high as potentially possible operating
performance on your mobile device while still maintaining a sufficient feature
base of nice, small and minimal features that would not be available via any
external feature base, extension, mod or plugin.
We hope you have a truly halogenified experience!
Internals of XOS
At core, the ROM is composed mainly of components from the Android Open Source Project (AOSP)
and CodeAuroraForums (CAF),
featuring only extremely minor set of components from LineageOS (LaOS or LN) which
have been added to source in order to allow for better cross-device compatibility.
Our LOVE to others
A huge thanks goes to those behind the AOSP and CAF, the LineageOS Project and all of its
contributors for the sources used in the development of the base ROM which we
started with inclusive of all the work and dedication their team puts in order to
keep us updated on the awesome contributions that they make.
We will be keen on ensuring that we be up to date with the code from our base sources,
with regular ROM updates hopefully coming from time to time.
Please do not ask for ETA's (else you shall be spooked by Mr Skeltal). Almost all of us are
students, and with the current lifestyles and routines we have, it is not that easy to acquire
time to develop the ROM, though we'll be sure to keep you updated and release OTAs as
soon as they are available and ready for publication. If you want to be really updated quick,
then join us on Telegram: http://telegram.me/halogenos
Visit our website for features such as: Downloads, Information etc.
http://halogenos.org
(constantly updated)
Common stuff
The ROM is super stable as of now and we'll maintain a clean and proper ROM.
Known issues are going to be fixed as soon as possible. We don't have infinite time.
Highlights (some are mido-only):
Reworked Lockscreen Visualizer
New implementation of button backlight
Modern Services -> Google Assistant etc.
Substratum
Full media support (FFMPEG, video codecs, ...)
Great Audio quality, no distortions, no crap
Optimized many portions of the system including surfaceflinger, inputflinger, System Server, and more
Super fast boot
Superuser-capable
Soundmod support (not all soundmods work on Nougat, it's not our fault)
addon.d support (backups your gapps etc. when flashing new build - don't wipe system before flashing!)
init.d support
BusyBox
Disabled Access Time for all partitions (We don't need access time. When access time is enabled, it will store the exact date of the access when a file is accessed, what just wastes write cycles (in theory) and has impact in I/O performance.)
Super smooth
Signature Spoofing toggle (Support for MicroG)
Support for trusted third-party WebViews like Chrome
Long press on home for assist toggle
Security Patches in kernel
Kernel optimizations
Kernel - Upstreamed Linux base to 3.18.55 and CAF Base to LA.UM.5.6.r1-04700-89xx.0
OpenGapps (Mini/Micro/Nano recommended) and Banks GApps support
DoubleTapToWake and DoubleTapToSleep
Alert Slider
Full KeyHandler & KeyDisabler support
Dexpreopt for faster (first) boot time and less space consumption on data partition
Upgrade & Boot the ROM in just 5 minutes - no more endless waiting for flashing a new build
Very high compatibility with other ROMs
VERY IMPORTANT: If you want to use root via SuperSU, make sure to use SuperSU 2.78 SR5 (or newer). Otherwise you won't be able to use sensors. You can also use Magisk and Phh's superuser if you desire to.
How to update the ROM:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Do not wipe anything
Flash the ROM
Flash SuperSU 2.78 SR5+ or Magisk)
Reboot
You don't need to wipe Cache/Dalvik.
You don't need to flash gapps again. There is some magic going on which keeps your GApps. Just make sure that you don't wipe system before flashing.
You don't need more than 5 minutes.
How to install the ROM for the first time:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Wipe system, data and cache (If you want to try a dirty flash, dont wipe anything)
Flash the ROM
Flash gapps if you want
Flash Magisk 11.5 (or newer) or SuperSU
Reboot
Screenshots
Currently right now, halogenOS will only include the stock Android theme.
We are going to use a custom theme as soon as that theme is working perfectly fine.
@regalstreak
@xdvs23 (actually xdevs23, but that was already taken on XDA)
@sewer56lol
@jbw716
@marpe
@dango99
@hunter_bruhh
@MSF-Jarvis
@keessonnema
ROM Download Links
Download halogenOS now
Join our
Telegram group
Telegram News Channel
Telegram Off-Topic Group
Telegram Testers Group
Credits
CodeAurora
CyanogenMod
And everyone else who contributed and helps us!
In case you feel left out here, please contact us!
reserved
Here we go......!!!! Downloading......
Nice!
Is it based on Aosp or Los?
Valeriuz said:
Nice!
Is it based on Aosp or Los?
Click to expand...
Click to collapse
i have a same question
fereidooni said:
i have a same question
Click to expand...
Click to collapse
Valeriuz said:
Nice!
Is it based on Aosp or Los?
Click to expand...
Click to collapse
Aosp
i just install this rom
no bug so far
sound quality better than any rom and kernel
camera is good
fingerprint sensor work good
buttom backlight not working
battrey not the best but good
reboot really so fast
you say somthing about modern service and google assistant and i see nothing ?
we get update for this rom or not
and thanks for your work :good::good::good:
Anyone has tried it on f2fs filesystem? this rom seems promising.
mszain said:
Anyone has tried it on f2fs filesystem? this rom seems promising.
Click to expand...
Click to collapse
Yes and it works very well
Is there a way to fix the backlight of menu keys in build.prop?
fereidooni said:
i just install this rom
no bug so far
sound quality better than any rom and kernel
camera is good
fingerprint sensor work good
buttom backlight not working
battrey not the best but good
reboot really so fast
you say somthing about modern service and google assistant and i see nothing ?
we get update for this rom or not
and thanks for your work :good::good::good:
Click to expand...
Click to collapse
Good, only button backlight not working is annoying any way to fix it?
I was pleasantly surprised by how fast the phone booted for the first time with this ROM, and the few apps that were installed gave it a very Slim-like experience. While I only used it for half an hour, I was quite happy with it, though my only suggestion for now is to add options to swap the order of the hardware buttons. Camera quality didn't seem particularly excellent either, though that could just be my personal opinion.
NightRaven49 said:
I was pleasantly surprised by how fast the phone booted for the first time with this ROM, and the few apps that were installed gave it a very Slim-like experience. While I only used it for half an hour, I was quite happy with it, though my only suggestion for now is to add options to swap the order of the hardware buttons. Camera quality didn't seem particularly excellent either, though that could just be my personal opinion.
Click to expand...
Click to collapse
for swap buttons
open root browser
go to system/usr/keylayout
open synaptics_dsx.kl file with text editor
you can find this text at the end of the page :
key 139 APP_SWITCH VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 143 WAKEUP
change BACK with APP_SWITCH don't touch VIRTUAL just BACK and APP_SWITCH
you have to use capital letters
Tell me, please, how disable Blinking diode on charge??????
Can't wait to install this on my soon the be shipped Mi5S... I gotta ask, what is the reason why (according to some users) MIUI sound quality is extremely bad? I hear that LOS/AOSP ROMs have much better audio, especially this ROM.
Very nice rom except that no option to swap navigation bar buttons..
warface9991 said:
Very nice rom except that no option to swap navigation bar buttons..
Click to expand...
Click to collapse
for swap buttons
open root browser
go to system/usr/keylayout
open synaptics_dsx.kl file with text editor
you can find this text at the end of the page :
key 139 APP_SWITCH VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 143 WAKEUP
change BACK with APP_SWITCH don't touch VIRTUAL just BACK and APP_SWITCH
you have to use capital letters
fereidooni said:
for swap buttons
open root browser
go to system/usr/keylayout
open synaptics_dsx.kl file with text editor
you can find this text at the end of the page :
key 139 APP_SWITCH VIRTUAL
key 102 HOME VIRTUAL
key 158 BACK VIRTUAL
key 143 WAKEUP
change BACK with APP_SWITCH don't touch VIRTUAL just BACK and APP_SWITCH
you have to use capital letters
Click to expand...
Click to collapse
key 139 BACK VIRTUAL
key 102 HOME VIRTUAL
key 158 APP_SWITCH VIRTUAL
key 143 WAKEUP
I did like that?
yes just like that
and restart your phone
this rom is the best rom for mi 5s without doubt
make this official devs
thanks a lot
{
"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"
}
LineageOS 14.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:
* 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
* 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.
NOTES
1) If you've found a bug, please report it along with a logcat.
2) If you experience a random reboot, please share /sys/fs/pstore/console-ramoops.
3) It should work on all models, just like LOS 13.
4) Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
5) I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
RIL (Calls, SMS, Data)
Audio ( Recording and Playback )
Sensors
Fingerprint
Notification LED
FM Radio
GPS
NFC
Hotspot
What's not working / bugs:
Camera is / looks zoomed when recording a video (it seems to be same on stock)
HDR?
IMS/Volte
Requirements
Huawei Nova CAN-L11 (should work on the other models too)
Unlocked bootloader ( here's a guide about how to unlock it)
TWRP. The TWRP made by @Grarak is also working fine. You can find it here.
Click to expand...
Click to collapse
Installation
Starting with January 2018 builds you need Nougat /product partition otherwise you'll get bootloop. To get Nougat product partition, you must install / flash EMUI 5 or restore this TWRP backup of Nougat /product partition (more details here). You don't know how to restore that backup? Check the steps from this post.
Make sure you meet the requirements listed above.
Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 7.1 and pico).
Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
Wipe system, data, cache and dalvik-cache.
Flash the ROM from the directory where you've placed it.
Flash GAPPS (OPTIONALLY).
Reboot.
Click to expand...
Click to collapse
Download
ANDROIDFILEHOST | MEDIAFIRE
Sources
LineageOS: https://github.com/LineageOS
Device: https://github.com/skinzor/android_device_huawei_hwcan
Vendor: https://github.com/skinzor/proprietary_vendor_huawei
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1
Click to expand...
Click to collapse
Donations
You don't have to, but if you like my work and you wish to support the development:
Donate via PayPal:
https://www.paypal.me/Henkate
https://forum.xda-developers.com/donatetome.php?u=4471434
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Credits
@Grarak
@gt_o
@abhishek987
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak, gt_o
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2017-11-13
Last Updated 2018-05-25
Changelog
25 May 2018
* security patch level 5 May 2018
The development has been resumed and is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
Click to expand...
Click to collapse
15 February 2018
Read this small, but important F.A.Q.
* synced Lineage sources
* security patch level 5 February 2018
* switched to enforcing selinux
Click to expand...
Click to collapse
25 January 2018
ROM
* synced Lineage sources
* security patch level 05.01.2018
* fixed in-call volume slider, mic/sound recorder (it's louder now) thanks to @gt_o. Read more here.
* updated audio configs to B382 and synced few audio props with stock ones
* show "HUAWEI NOVA" instead "Android" when phone is plugged to PC
* removed substratum support.
* added two blobs to fix two errors in logcat
* added the missing device_qcom_common (i don't know how i haven't noticed that till now lol). Now there are 5 profiles: powersave, efficiency, balanced (default), quick and performance. This can be configured at battery settings. As an idea, the powersave profile seems to turn off 3 cores (the cores doesn't seems to turn on when there is a high load though), while the performace one sets all cores to 2ghz. The power hal being used is the one of msm8937, which is also an octa core CPU. This is defined in the power hal's makefile on Lineage's repo (if the processor is msm8953, use the power hal of msm8937). I recommend it to keep the balanced profile (which is enabled by default), but it's up to you.
Kernel
* merged stock kernel source into the CAF one (tag LA.UM.5.6.r1-01300-89xx.0 as this one semeed to be the closest to stock, but also based on the Adreno log)
* got rid of many drivers from Huawei. You can see the commits here. Thanks to @gt_o, huawei's bootfail monitor (HWBFM) has also been removed. Although HWBFM was disabled till now, it was better to get rid of it, to get a cleaner kernel, but also being easier to merge the stock source into CAF.
* cpuset updates (also in ramdisk)
* added WireGuard support, thanks to @zx2c4. WEBSITE | XDA
* removed fsync/crc toggles as it's better to not mess with them
Click to expand...
Click to collapse
9 December 2017
ROM
* synced Lineage sources
* added Substratum support
* fixed blinking mode of notification light
* allow minimum brightness 1 (it was 4 before)
* possibly fixed the power usage reported by bluetooth ( i can't test right now as phone is charging and can;t reset the battery stats)
* Reverted this commit (more details there)
Kernel
* fixed hotspot
* cleaned ramdisk
Click to expand...
Click to collapse
25 November 2017
ROM
* security patch 6 November 2017
* fixed signal icon on 3G (it isnt empty / gray anymore)
* fixed flac audio playback
* updated media configs to N B382
* hide sRGB toggle in developer options
* increased the number of voice call steps from 5 to 8, and media volume steps
from 15 to 20
* increased the handset volume from the default (84) to 88 to improve UX with voice calls
* added ext4 support for /data
* added f2fs support for /cache
* added glove mode (Settings > Display > High touch sensitivity)
* from now on, Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
Kernel
* fixed logd/klogd issue (the high cpu usage)
* disabled HUAWEI_DEBUG_MODE config
* added DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
* added USB HID gadget support
* CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
* FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
Click to expand...
Click to collapse
13 November 2017
* initial release
Click to expand...
Click to collapse
Reserved
Dowloanding ^^
As soon as I can, I'll report back =)
Thank You #Henkate for keeping Nova alive!
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Works fine here, thanks a lot for the hard work !!!
Will give it a shot this weekend. I am a teacher and students are doing mid term exams this week, so I kind of need my phone.
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
GertFromTheWell said:
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Click to expand...
Click to collapse
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
Vinnom said:
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
Click to expand...
Click to collapse
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
#Henkate said:
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
Click to expand...
Click to collapse
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Vinnom said:
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
I see.
I have the second error too, after flashing the ROM. I haven't checked why, but it doesn't seems to affect anything.
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
#Henkate said:
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
Click to expand...
Click to collapse
@Vinnom
Here you go. Install it from recovery.
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
sk8buoy said:
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
Click to expand...
Click to collapse
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
icutzo said:
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
Click to expand...
Click to collapse
Nope, this bug is gone now. When I'm on LTE the icon don't show LTE (it show only the signal strength) but data works fine.
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Vinnom said:
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Click to expand...
Click to collapse
The recovery logs looks fine. I see that you have also installed Magisk and a Titanium Backup zip. Just to be clear, you have tried to install it without anything else too?
1) Did you wait about 5 mins ( although i dont think that much time is required)?
2) Can you take a kernel log too?
Run the following command, while booting (let it run few seconds after you think that you have got bootloop):
Code:
adb shell "cat /dev/kmsg"
I cant find anything wrong in logcat neither. I think the stock kernel may not be compatible with your model, so i will need to use the kernel source for your model or compare the two sources and import changes from CAZ-TL10 source into the one im using now.
The stock kernel source which is being used right now is CAZ_NG_EMUI5.0_opensource. According to Huawei`s website, it is meant for:
HUAWEI Nova,HUAWEI Nova Plus, CAN-L10, L11, MLA-L01,L11,L12,L13, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
When i search for "CAZ" on their website, i find nothing. But there seems to be:
Cannes-AL10_TL10 HUAWEI nova, Cannes-AL10, TL10, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
Perhaps thats the right one for CAZ-TL10 too?
imkoma said:
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Click to expand...
Click to collapse
Thank you too for your words!
By the way, its Henkate. You can also call me Robert .
1) When exactly camera is stopping and how? I didnt encounter this on my CAN-L11
2) What kind of issues does have front camera? My Nova`s front camera got damaged / broken when my Nova has been damaged, therefore i cant use it nor test it.
3) Regarding the cores, ive wrote at "notes" in first post:
The first thing you want to do after first reboot is to install a file manager and rename /system/bin/logd to "logd.bak" and reboot. You have to do this in order to get rid of the high CPU load. Consider this a workaround until the issue gets solved. Note that this breaks logcat, so you'll have to rename it back to "logd" and reboot to be able to take a logcat.
Click to expand...
Click to collapse
Would be nice if you could share a logcat regarding 1) and 2).
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Downloads Links
AOSP 9 Pie (Unlocked Bootloader) :
Xperia SP (Huashan) - 9 : https://mega.nz/#F!6hsHyKKT!ERgr5s0BMMtO2Cb9j8wLnA
Google Applications (optional) :
MindTheGapps : https://androidfilehost.com/?w=files&flid=170282 (Use packages for ARM, Android 9.0)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Recommended Recovery (optional) :
TWRP 3.x : http://forum.xda-developers.com/xperia-sp/orig-development/-t3309938
Configure the default Low-RAM features (optional) :
Low-RAM Property Patcher : http://forum.xda-developers.com/-/-t3737373
Informations and references :
Kernel CVEs : Security patches status https://cve.lineageos.org/android_kernel_sony_msm8960t
About AOSP : Repositories available on https://android.googlesource.com/
Flashing and updating
AOSP clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Install TWRP Recovery to the FOTA partition (Read the TWRP thread)
- (Optional) Wipe the data & cache (Backup to make sure not to lose data)
- Flash the AOSP ROM zip from recovery
- (Optional) Flash a GApps package to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
AOSP update / upgrade :
- (Information) Do not wipe anything unless you want to
- Flash the latest AOSP ROM zip from recovery
- (Optional) Flash a GApps package if you want to, otherwise preserved.
- (Optional) Every additional zip you want to flash
- Reboot
About the builds
Development project : https://github.com/AdrianDC/aosp_development_sony8960_p
Device tree : https://github.com/AdrianDC/android_device_sony_huashan
Kernel sources : https://github.com/AdrianDC/android_kernel_sony_msm8960t
Vendor blobs : https://github.com/TheMuppets/proprietary_vendor_sony
Issues and reports
- Report issues only if you use the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
Q&A - FAQ
Q : Is root access included into AOSP ?
A : No but you can now root with my Boot Bridge and a superuser tool.
Q : Is the ROM suited for daily usage ?
A : Yes. Check the list below to decide for yourself.
Q : Where can I change the Quick Tiles and Status Bar ?
A : Long press the Settings icon in the notifications drawer.
> You will have access to the SystemUI Tuner from Marshmallow.
Q : When USB is connected to a computer, I can't access the storage ?
A : The phone is in charge-only mode by default (since Android Nougat),
> due to a stronger security logic regarding unauthorised data access.
> Swipe down the notifications and change the USB mode.
AOSP available for Xperia Huashan also thanks to :
- Google AOSP
- The LineageOS Team
- CodeAurora Forums
- The CyanogenMod Team
XDA:DevDB Information
AOSP Oreo 9, ROM for the Sony Xperia SP
Contributors
AdrianDC
Source Code: https://android.googlesource.com/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Snapshot
Created 2019-08-17
Last Updated 2020-08-15
Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- Touchscreen : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- DRM : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Not tested yet
- SEPolicies : Permissive, enforcing is a work in progress
ALSO WORKING ON SONY HUASHAN
Music Lights Effects implementation fully working
Presentation of the features : https://forum.xda-developers.com/showpost.php?p=73049970&postcount=399
YouTube Presentation : https://www.youtube.com/watch?v=GHk__DhyL60
IMPORTANT FEATURES TO KNOW
Boot sequence : Once the LEDs light up :
- Press Volume - to open AOSP Recovery,
- Press Volume + to open the FOTA recovery (TWRP usually) if available
Powered-off alarm : When you have set an alarm
- If you power down the device, it will wake automatically 5 minutes before
- If you let the device charge offline, it will automatically reboot 5 minutes before
Gestures : Events like hand-wave and pocket removal can be enabled in the Settings
Force reboot : You can reset the device by holding Power and Volume+ 5 seconds
Reserved
Changes log
17/08 : Initial public release on Android 9.0.0_r46 August
2018: Initial AOSP 9 ports, internal bringup
>>> Kept private for development purposes
Recent branches commits
Devices + common projects: https://github.com/AdrianDC/aosp_development_sony8960_p/branches/all
Original AOSP 9 sources with following relevant additions
Huashan device tree, kernel and vendor
Bionic: Support for SHIMs (Camera)
Build: Backup tool full support (GApps)
NFC: Proper support & removed log spam
Toybox: Support for init_sony boot selection
AV: Camera support for Pie
AV: Initial camcorder partial support
Camera2: Fixes for wrongly rotated photos and improvements
UI: Various efficiency improvements and fixes
Telephony: Support for older RIL layers
Audio: 8960 adapted HAL and FM support
FM: Fully implemented with AOSP FM Radio
Music: Minor fix to permissions
Settings: Minor visual rendering improvements
Healthd: Support for Huashan offline charger
Core: Disabled flash_recovery service from AOSP
Sepolicies: Minimal changes and fully enforced ROM
Current local manifest
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- [url]https://android.googlesource.com/platform/manifest[/url] -->
<manifest>
<!-- See [url]https://github.com/AdrianDC/aosp_development_sony8960_p[/url] -->
</manifest>
I woke up in the morning and decided for a short walk around the internet - and to my surprise I found new builds of both AOSP and Lineage suitable for my favourite backup phone Thank you so much @AdrianDC - I know it is harder to withstand people than hardware
Thank you for LTS for our Xperia SP. :good:
Is it possible for miracast to work in LOS 16 as it does in LOS 15.1?
ze7zez said:
Thank you for LTS for our Xperia SP. :good:
Is it possible for miracast to work in LOS 16 as it does in LOS 15.1?
Click to expand...
Click to collapse
Sadly Google has removed support for Miracast in AOSP P.
An attempt to revive the abandoned code for LineageOS 16.0 is ongoing and on review.
Experience, first stable build
Hello, i want to share my critic experience with you and this rom.
(C5303, Clean flash, Data and cache FS changed to F2FS, without gapps, magisk)
1. Music - i had good experience, led controls work good, but after day of using phone and some restarts, it shows only 2 from my 600 songs.
So i installed Sony music app, no difference. Cleared data, cache for both apps, but still no difference.
2. AOSP Browser - After some succesful launches, FC every launch time, other browsers OK
3. After day usage, system started drain battery as fck...
4. At same time as battery and music, system going slowly
5. And biggest issue - phone cannot turn off - it restarts. So i have 2 go 2 recovery and turn off here.
I have been without gapps, because i wanted pure system, so i installed yalp store (some 404 client errors, but logged succesfully) and with magisk 19.3 bootbridge (Modules: V4A 2.7.1.0, Audio compatibility and modification patches, Pixelarity, SF-Font, Busybox, all modules works flawlessly)
I must give big + and thanks for developers, because 6 y.o. phone still breaths for today with the new system, but stable work must have itself finality. Check this things on your phones and please fix it for stable, pure AOSP experience.
And add please full dark mode.
Edit:
I have tried new Lineage 16 and same issues with different music players, browser and newly - gallery doesnt show anything and camera not working.
jurko217 said:
(---cut---)
And add please full dark mode, it changes battery life for some hours (---cut---
Click to expand...
Click to collapse
For amoled display only. Huashan doesn't have it.
sorry, another thread
Hi,
First of all, I want to thank again AdrianDC for bringing Android Pie on our lovely SP (that I'm keeping as a backup phone and can't let it go), man, you just rock
But I'm really surprised not to read anything here about the setup problems I've encountered, because for me, it was Hell on Earth !!!
It has NOTHING to do with the ROM or the work of AdrianDC, but it seems to be purely Google's fault
So, I thought I will share how I got through it, perhaps helping some of you not getting nearly insane, like me yesterday...
First one was "Stuck on "Checking for updates..", so I found first here : https://www.reddit.com/r/GalaxyS9/comments/aqa384/t_mobile_s9_stuck_on_checking_for_updates_after/ this reply : "I had to completely disconnect from wifi, took the sim out so it would skip that process. Its finally working fine now." method confirmed in this XDA thread here : https://forum.xda-developers.com/nokia-7/help/stuck-screen-checking-updates-hard-reset-t3767866/page2 in the post #15 : "Try without SIM card inserted. It should work."
Alternatively, in this thread : https://forum.xda-developers.com/2015-moto-g/help/reset-stuck-checking-updates-t3571496 the method explained in post #4 worked well also :
"On the TWRP Terminal:
echo "ro.setupwizard.mode=DISABLED" >> /system/build.prop
this will skip the first setup!
edit: may need to mount /system"
And then came the second bug : "Phone stuck on Preparing for Setup after factory reset of Android Pie"
I read a lot of threads about it :
https://forum.xda-developers.com/mi-a2/help/phone-stuck-preparing-setup-t3870469
https://forums.oneplus.com/threads/android-preparing-for-setup-prompt-always-appearing.1083942/
https://forums.oneplus.com/threads/stuck-with-android-setup-issue-on-oneplus-6t.953686/
https://forums.lenovo.com/t5/motorola-one-motorola-one-power/Preparing-for-Setup-you-can-finish-your-motorola-one-power-soon/m-p/4391471#M4710
https://www.reddit.com/r/tmobile/comments/9uj9vw/cannot_get_android_setup_app_updates_are_ready/e94uow3
https://uk.community.huawei.com/mate-20-series-20/app-updates-is-not-moving-preparing-for-setup-2591
https://uk.community.huawei.com/mate-20-series-20/android-setup-keeps-telling-me-that-app-updates-are-ready-and-that-i-should-connect-to-wifi-5687
And so on, but nothing in all this posts helped so I ended disabling the notification AND the Android Setup app !!!
Some of those reports are more than a year old and I've rooted and flashed custom ROMs on 5 differents devices / brands over the years, but I never encountered such a mess !
Google, what's wrong with you ?!?
So I hope this will help a bit, I wish you all a nice Sunday...
For completion's sake, I forgot to add that I've made a clean install and did follow exactly these steps to do it :
- having made the TA backup years ago and finding LineageOS Oreo a bit too lagy to my taste, I took the occasion to try (for the first time) to restore the TA partition (with success), this locking back again the bootloader and then, restored with Flashtool the original ROM that was shipped with the SP;
- so I find myself back with the original DRM keys and the original Jelly Bean :crying:, played a little bit with it (a real trip down Memory Lane) and confirmed forever to myself that I really don't miss anything of Sony's crap (Bravia Engine, Track-ID, whatever...), but to each his own;
- I used fastboot and Sony's code to unlock the bootloader again, then boot twrp.img, flashed the FOTA.zip and erase EVERYTHING, but the SD card !
- I just flashed the 20190817 build and the OpenGapps Micro, one after the other from the SD Card and let the BootBridge.zip with Magisk inside for a later time...
- I rebooted and then, all Hell broke loose
- Hours (and a lot of swearing) later, I flashed BootBridge.zip with Magisk and could finaly enjoy how mean and lean is Android 9 on this 2013 device again, bravo !!!
So, I honestly don't think that any of those steps described above could have been the cause of the 2 bugs (and the numerous threads I've read seem to confirm it), but I would be glady corrected if I'm wrong...
Really, nobody here had to go through this whole hassle, seriously ? You've all got a smooth ride with a clean install ?
I would really like to know if it's me or if, in this case, Google is having two left hands, and just with thumbs :silly:
fsw_informatrix said:
For completion's sake, I forgot to add that I've made a clean install and did follow exactly these steps to do it :
- having made the TA backup years ago and finding LineageOS Oreo a bit too lagy to my taste, I took the occasion to try (for the first time) to restore the TA partition (with success), this locking back again the bootloader and then, restored with Flashtool the original ROM that was shipped with the SP;
- so I find myself back with the original DRM keys and the original Jelly Bean :crying:, played a little bit with it (a real trip down Memory Lane) and confirmed forever to myself that I really don't miss anything of Sony's crap (Bravia Engine, Track-ID, whatever...), but to each his own;
- I used fastboot and Sony's code to unlock the bootloader again, then boot twrp.img, flashed the FOTA.zip and erase EVERYTHING, but the SD card !
- I just flashed the 20190817 build and the OpenGapps Micro, one after the other from the SD Card and let the BootBridge.zip with Magisk inside for a later time...
- I rebooted and then, all Hell broke loose
- Hours (and a lot of swearing) later, I flashed BootBridge.zip with Magisk and could finaly enjoy how mean and lean is Android 9 on this 2013 device again, bravo !!!
So, I honestly don't think that any of those steps described above could have been the cause of the 2 bugs (and the numerous threads I've read seem to confirm it), but I would be glady corrected if I'm wrong...
Really, nobody here had to go through this whole hassle, seriously ? You've all got a smooth ride with a clean install ?
I would really like to know if it's me or if, in this case, Google is having to left hands, and just with thumbs :silly:
Click to expand...
Click to collapse
Sometimes opengapps can cause errors given how itself is like a rolling Nightly packages generated on demand when you hit download. I recommend trying MindTheGapps as it went smoothly for me using that one.
Not a setup issue, but an issue nonetheless: During my attempt to flash this ROM, I had free space errors with Opengapps. Even on pico package!
Ninja Edit: I found out on the LOS pie thread that Pico is the only one that fits. I still however stand by the authenticity of my story
TechnoSparks said:
Sometimes opengapps can cause errors given how itself is like a rolling Nightly packages generated on demand when you hit download. I recommend trying MindTheGapps as it went smoothly for me using that one.
Not a setup issue, but an issue nonetheless: During my attempt to flash this ROM, I had free space errors with Opengapps. Even on pico package!
Ninja Edit: I found out on the LOS pie thread that Pico is the only one that fits. I still however stand by the authenticity of my story
Click to expand...
Click to collapse
Thank you again didn't thought about that one, I will give MindTheGapps a try, next time...
OMG, my second try was so quick & easy with MindThe Gapps, thanks again @TechnoSparks
I did a Nandroid backup and couldn't resist to give it another try, so from TWRP in the FOTA :
1) I manually erased all partitions, but recovery, SD Card and USB-OTG, just to be sure.
2) I queued and installed from the first post (and in this order) aosp-9-20190817-huashan-adriandc.zip, android_lowram_enabler.zip and MindTheGapps-9.0.0-arm-20190615_031401.zip, without any errors.
That was the right call to flash the android_lowram_enabler.zip in between, because I've noticed a message from the MindTheGapps installer :
"Low ressource device detected, removing large extras", which is lovely and exactly what I needed, no Google bloatware...
3) I rebooted and didn't met any of the bugs I had with OpenGapps, not even an initial setup :laugh: just had to pick manually language and Wi-Fi (location and date/hour too, as there is no SIM inside).
4) I got back to TWRP and flashed BootBridge-SonyELF.zip with Magisk19.3 inside, rebooted and updated Magisk Manager (Note: strangely, I had to reflash BootBridge-SonyELF.zip a second time, after the Magisk Manager update, to get it working back).
Now, it's all set up and I can finally test it further
Hope this helps somebody and keep up the good work, M. AdrianDC...
fsw_informatrix said:
That was the right call to flash the android_lowram_enabler.zip in between, because I've noticed a message from the MindTheGapps installer
Click to expand...
Click to collapse
Thank you for your report.
For information, I'll remind something for everyone : My Sony Huashan & Blue releases are all using the Go low RAM configs.
Flashing android_lowram_enabler is not required, it's a no-op, however android_lowram_disabler will bring back disabled features per user choice.
The android_lowram_enabler tool serves a purpose only to come back from a disabler and for any other devices not using Go low RAM configs.
AdrianDC said:
My Sony Huashan & Blue releases are all using the Go low RAM configs.
Flashing android_lowram_enabler is not required, it's a no-op, however android_lowram_disabler will bring back disabled features per user choice.
Click to expand...
Click to collapse
I see and I could report this is the case in the system...
But I swear I don't understand why the status bar still is transparent on the homescreen and in various programs.
Btw did you investigate using the ro.config.small_battery flag? I'm not sure if huashan would fit the bill (even though, assuming you still have the original battery it may as well do) but perhaps tsubasa could qualify.
sir can i do dirty flash if i want to downgrade to aosp oreo or nougat? i got a bit unresponsive on pie
i want to keep my app data if it possible
Not really expecting an answer at this point but here goes...
I am using a really early build of this rom (4/2019), but it works really well.
I've also installed the latest version of Magisk using Bootbridge. My problem is that I can't seem to make it pass the safetynet check, says false on both CTS Profile and Basic Integrity.
I've tried a lot of things, but nothing seems to work. Is it just because of the build, and something that has been repaired in later builds?
LaRazón said:
Not really expecting an answer at this point but here goes...
I am using a really early build of this rom (4/2019), but it works really well.
I've also installed the latest version of Magisk using Bootbridge. My problem is that I can't seem to make it pass the safetynet check, says false on both CTS Profile and Basic Integrity.
I've tried a lot of things, but nothing seems to work. Is it just because of the build, and something that has been repaired in later builds?
Click to expand...
Click to collapse
No version of this room pases CTS profile without a magisk module helping it to fool Safetynet. Basic Integrity failing is a weird error that does happen from time to time. Usually just reflashing everything fixes it. Keep in mind, that there have been some changes in safetynet that could be breaking it for you.
HI AdrianDC, thank you for all you work, i think its amazing, i Tryed this rom from yesterday, and everything is going perfect, navigation on this emviroment is smooth, i instaled the lastest GAPPS, no issue found, even i installed FB , Instagram and another social apps, works fine to me.
But i may find some kind of bug or something, some apps that i use has a media pleyer inside to play micro- video tutorial, but i cant see them, looks like buffering only, even videos played from chrome , like news videos i cant see them, only seems buffering, maybe its only me, or i did something wrong, can you or anyone help me?, please
regards!