Welcome to KitKang ROM!
* Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* 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 us for
* messing up your device, we will laugh at you.
Click to expand...
Click to collapse
Description:
KitKang ROM is a ROM built from the CyanogenMod 11 source, with some cherrypicks added for features and functionality.
Bugs List:
Code:
-???
Current CherryPicks
Code:
#56346 LockScreen: allow long-press actions from hardware keys (1/2)
#56357 LockScreen: allow long-press actions from hardware keys (2/2)
#55209 Forward port Status Bar interface (1/2)
#55211 Forward port Status Bar settings (2/2)
How To Flash:Coming From a Different ROM?
1. Make sure you are unlocked and running the latest version of ClockworkMod Recovery (Either Touch or Non-Touch is fine). If you do not know how to unlock your bootloader or install recovery, follow these steps.
2. Make sure you are running the latest firmware version. If you do not know what firmware version you are running, you can check in Settings in the "About Phone" tab. Currently, the latest firmware is VRBMF1, and a recovery flashable of the firmware can be found here. To install, simply reboot to ClockworkMod and flash the zip file.
3. Backup everything you need. All of your files will be deleted! To backup your apps, I recommend using Helium. It is very easy and straightforward.
4. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
5. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
6. Wipe the data, system, cache, and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
7. Install the ROM and G-Apps files
8. Reboot and setup your phone!
Click to expand...
Click to collapse
Updating From A Previous KitKang Nightly?
1. Download the ROM and G-Apps from the links provided and copy them over to your phone via USB cable.
2. Reboot to recovery. To do so, either use the built in reboot option to recovery in ROMs such as CyanogenMod, or power down and hold Power + Home + Vol Up and you should be in recovery.
3. Wipe the cache and dalvik cache partitions in recovery. (Dalvik wipe is located in Advanced Settings)
4. Install the ROM and G-Apps files
5. Reboot!
Click to expand...
Click to collapse
Download Links
ROM DOWNLOAD
(Note: This is a folder, and has all of my builds. Download the one you want. If you don't know what to download, use the latest.
G-APPS DOWNLOAD
KANGED G-APPS DOWNLOAD
Not supported or recommended because of stability issues. However, this does include the new dialer with Google Search support. Use with caution. If you do not know which G-Appps package to use, use the first link.
Enjoy?
If you enjoy the ROM, please consider sending me a donation
XDA:DevDB Information
KitKang Rom CM11 Kangs, a ROM for the Verizon Samsung Galaxy S III
Contributors
dmeadows013, XRaptor29, cammykool, tvall
ROM Kernel: Linux 3.4.x
ROM Firmware Required: VRBMF1
Based On: CyanogenMod
Version Information
Status: Testing
Created 2013-11-14
Last Updated 2014-01-01
Guide to Building
Guide for Building KitKang on Mac OSX
This is a guide demonstrating how to build KitKang for yourself on Mac. I am not responsible for anything you do to your computer or your phone as a result of following this guide. Before building, I would recommend that you have at least a little knowledge of Terminal, and a powerful computer. AOSP takes up a lot of resources, and even my i7 Ivy Bridge build with 16GB RAM and an SSD takes almost an hour to build. The AOSP code takes up a lot of space, so I recommend AT LEAST 150GB free space, just to be safe. This guide involves installing specific packages to build AOSP. To install these packages, we will use Homebrew. You will also need XCode to build. If you do not have these installed, refer to the beginning of the guide. If you already have these installed for some reason, skip the first section for installing XCode and Homebrew.
Click to expand...
Click to collapse
Installing XCode/Homebrew
Download and install XCode from the Mac App Store. You will need an Apple account to do this.
After downloading and installing XCode, you will need the Command Line Tools. These can be installed by opening a Terminal window and entering:
Code:
xcode-select --install
After entering this, hit return and a box should pop up asking you if you want to install Command Line Tools. Click yes, and wait for it to install.
Now, make sure you have the latest Java Runtime. You do this in Terminal by entering a command and going through an installation process. Enter the command
Code:
java
With the Command Line Tools and Java installed, we can now install Homebrew. To do so, open Terminal again and enter the following:
Code:
ruby -e "$(curl -fsSL https://raw.github.com/mxcl/homebrew/go/install)"
Make sure Homebrew is installed and works correctly by running
Code:
brew doctor
If you got errors in the previous command, try googling to see if there is something else you need. If you can run the command without errors, you are good to go!
We must now move the SDK so the build recognizes what to use. To do this, run the following commands in Terminal
Code:
sudo mkdir /Developer
Code:
sudo mkdir /Developer/SDKs
Code:
sudo cp -r /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk /Developer/SDKs/MacOSX.sdk
NOTE: You need superuser permissions to run the previous 3 commands.
Now, in Terminal, type
Code:
nano ~/.bash_profile
If you get a no file found error, then run
Code:
nano -w ~/.bash_profile
You should get a screen with some text. Scroll to the bottom using the arrow keys until there's just blank spaces, and paste the following code
Code:
export BUILD_MAC_SDK_EXPERIMENTAL=1
Save the file using ctrl-x and clicking yes and enter
Restart Terminal to make the changes take effect
With Homebrew now installed, we can continue to downloading required build packages!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Installing Required Packages
Now we will install packages required to build the AOSP source. This can be done with the Terminal command
Code:
brew install git coreutils findutils gnu-sed gnupg pngcrush repo
With these packages installed, we need to make some symlinks so that OSX knows which files to use, and doesn't mess up the build. To do this, enter
Code:
ln -s /usr/local/bin/gfind /usr/local/bin/find && ln -s /usr/local/bin/gsed /usr/local/bin/sed
With these packages installed, we are now ready to create a build environment and download the AOSP source.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Preparing the Build Environment and Downloading the Source
First, we need to create a dedicated workspace for our AOSP code. This can be done in Terminal by entering
Code:
hdiutil create -type SPARSE -fs "Case-sensitive Journaled HFS+" -size 120g -volname "android" -attach ~/Desktop/Android
This will create the workspace image on our desktop. To move it, simply drag and drop in Finder to the location you want.
Now, locate the workspace in Finder and double click it to mount it
NOTE: If you moved your workspace to a different directory, you will have to use the path to that directory in the previous step.
Next, from within Terminal, locate the directory by typing
Code:
cd /Volumes/android
Now that we are in the working directory, it is time to download the Android Source. This is done by entering the following command
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0 && repo sync && say 'finished'
Wait for the download to finish. Depending on your connection, it can take a long time, so get comfortable.
When the download finishes and you can see all of the source folders in your directory, it is time to download the S3 specific files. To do this, we need to edit the roomservice.xml. However, this file is hidden. We can access it by entering the following in Terminal
Code:
open -a TextEdit .repo/local_manifests/roomservice.xml
You should get a blank file in TextEdit. Enter the following code as is here
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_d2vzw" path="device/samsung/d2vzw" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="CyanogenMod/android_device_samsung_msm8960-common" path="device/samsung/msm8960-common" revision="cm-10.2" />
<project name="CyanogenMod/android_device_samsung_d2-common" path="device/samsung/d2-common" remote="github" />
<project name="CyanogenMod/android_kernel_samsung_d2" path="kernel/samsung/d2" remote="github" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
</manifest>
Save and close the file, and again run
Code:
repo sync
With the S3 specific files downloaded, we need to download the CyanogenMod specific app files. This can be done by running
Code:
./vendor/cm/get-prebuilts
With this done, we need to download the cherrypicks specific to the S3. Eventually, these will not be needed, but as CyanogenMod 11 is still in beta, it is needed for now. Because the cherrypicks are often being merged, and new ones created, the kind folks at CyanogenMod have created a Google Document with a list of the latest commits. This is located here. NOTE: This document does not include any cherrypicks that I may include for features. By using these cherrypicks, you are installing everything needed to make the ROM as stable as possible. I may occasionally include other cherrypicks that I find enhance features. Inside the document, scroll down to the '# repopicks' section and continue scrolling past the commit messages. At the bottom, you will see a section titled 'Combined'. This will have a command such as
Code:
repopick -s s <List of commit hashes>
You could simply copy this command and paste it into a Terminal window, but that would put the cherrypicks on new branches of the source, which could cause problems with resyncing the source. I would recommend copying only the commit numbers.
In Terminal, run the command
Code:
. build/envsetup.sh
Run the repopick command, adding the commit numbers to the end. Here is an example
Code:
repopick 53075 53131 53302 53309 53356 53445 53528 53595 53603 53604 53637 53964 54197 54198 54219 53468 54251 54274 54277
If the commits do not all merge correctly, you will get what is called a merge conflict. This is because one or more of the commits does not play nice with the CyanogenMod code. Make sure you have the latest code by resyncing, and also make sure you have the latest cherrypicks. If the command still fails, wait a few hours because the document probably just hasn't been updated.
Once you get all of the commits merged correctly, it is time to build!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Building the Source
Before building, if you have extra space on your hard drive, you can optionally use CCache to speed up your build a bit. Enable this from inside the working directory by using
Code:
export USE_CCACHE=1 && prebuilt/darwin-x86/ccache/ccache -M 20G
You may also need to change the ulimit to support building. On OSX 10.9, I experienced errors stating that I had too many files open, and I had to change the ulimit amount. NOTE: If you have issues, you will need to do this every time you build! Change the ulimit amount by running
Code:
ulimit -Hn 8192
and
Code:
ulimit -Sn 8192
Make sure your working directory is clean by running
Code:
make clean
Next, initiate the build by running
Code:
brunch d2vzw
If all goes well you should have a flashable zip in the out/target/product/d2vzw/ folder. Enjoy!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Updating the Source
Later on, you may decide to build another file to see with new changes to the CyanogenMod code. Think of this as a ROM update. To do this, you will need to follow some steps. All of these steps have been completed already in this guide, so I will just be outlining them, and will not be listing everything. If you forget how to do something, consult the guide.
Repo sync
Apply cherrypicks
Enable CCache (Optional)
Set the ulimits
Clean your working directory using
Code:
make clean
Build the code using
Code:
brunch d2vzw
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Reserved
reserved
Recognized Developer - OP
OP hmmm OVER POWERED
Finally i can choose between sspencer10,tvall and cammykool and now you!
---------- Post added at 01:06 AM ---------- Previous post was at 12:41 AM ----------
Same Gapps? PA?
Is the 4.3 or the 4.4 camera included in this rom? If it is the 4.4 camera, is the quality of the photo better than the initial builds? Thank you.
-External SD Card May or May Not Work
It does work
markdapimp said:
-External SD Card May or May Not Work
It does work
Click to expand...
Click to collapse
The reason why he posted that is because one thing gets fixed another is broken. Every Device is different kinda thing.
XRaptor29 said:
The reason why he posted that is because one thing gets fixed another is broken. Every Device is different kinda thing.
Click to expand...
Click to collapse
I have 3 S3's my mom's dads and mines SD works perfectly on all 3
markdapimp said:
I have 3 S3's my mom's dads and mines SD works perfectly on all 3
Click to expand...
Click to collapse
Well thats a good thing lol :good:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
mds96 said:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
Click to expand...
Click to collapse
Do a clean wipe in CWM and flash the FULL PA Gapps
---------- Post added at 02:22 AM ---------- Previous post was at 02:12 AM ----------
Some screenshots for OP
mds96 said:
Anyone know of a fix to get the apps from the Play Store that say sd card storage is insufficient to install? Root Explorer did it to me, but that's all I know of so far. Not a big deal, can use other apps. Thanks for the builds!
Click to expand...
Click to collapse
seems to be a bug to only paid apps. free ones work for me. weird.
XRaptor29 said:
seems to be a bug to only paid apps. free ones work for me. weird.
Click to expand...
Click to collapse
I see what you mean
Thanks Markdapimp! I kinda figured a clean wipe would solve the problem, but guess I wanted to be lazy, lol
markdapimp said:
I see what you mean
Click to expand...
Click to collapse
Pretty sure this is because of the SD card problem. Hopefully there is a fix soon
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
WeThePeople13 said:
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would just do a clean flash just to be sure
WeThePeople13 said:
Downloading!! Quick question before I flash..... I am running tvalls build from a few days ago, can I dirty flash or no? Also I love your builds it reminds me of when CM9 was built for the ReZound!! Props bro!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Yes dirty flash should be fine, but idk for sure. I've got homework to do but when I get time I'll make a new build and upload/put more stuff in the OP. Maybe tonight but probably not.
Screenshots in screenshots tab thanks @markdapimp
Yea that is what i was thinking. I just am lazy lol and I really hate doing that whole process of getting art enabled.
Sent from my SCH-I535 using Tapatalk 2
Related
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by Open Desire Project and TeamCodefire. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
Mustaavalkosta
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON.
Reboot and enjoy.
Update instructions:
Download Nightlies
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: saga_cm11_defconfig
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I and Mustaavalkosta don't really need your money right now but if you insist on donating to us we suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
TWRP 2.8.0.0 SAGA or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_odp.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Open Desire Project, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2014-10-29
Last Updated 2017-01-04
Reserved
Bugs:
headset mic
S2w switch in device settings
kylon said:
nightly builds will start tomorrow!
thanks to Mustaavalkosta.
Bugs:
Wifi AP/hotspot/tethering
headset mic
Click to expand...
Click to collapse
Thank you all, GODS of ROMS!!!!!!!!
So i've been using your 20141024 release and i'm sticking with it. For next release, should i make it dirty or clean install?
Awesome work :highfive:
kylon said:
nightly builds will start tomorrow!
thanks to Mustaavalkosta.
Bugs:
Wifi AP/hotspot/tethering
headset mic
Click to expand...
Click to collapse
Thanks people!
One question...
There will be Stable versions in this thread? i mean over time of course.
kylon said:
nightly builds will start tomorrow!
thanks to Mustaavalkosta.
Bugs:
Wifi AP/hotspot/tethering
headset mic
Click to expand...
Click to collapse
Download files are just up.
kylon said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by Open Desire Project and TeamCodefire. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
Mustaavalkosta
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
[* This should be a temp step]Download this fix.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
[* This should be a temp step]Flash mic fix.
Remember to flash boot.img via fastboot if you have S-ON.
Reboot and enjoy.
Update instructions:
Download Nightlies / [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-saga.zip
[* This should be a temp step]Flash mic fix.
Remember to reflash boot.img via fastboot if you have S-ON.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: saga_cm11_defconfig
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I and Mustaavalkosta don't really need your money right now but if you insist on donating to us we suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
TWRP 2.8.0.0 SAGA or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_odp.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Open Desire Project, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2014-10-29
Last Updated 2014-10-29
Click to expand...
Click to collapse
<3 :3
No sound in incoming - people don't hear me.
_hugh said:
Thanks people!
One question...
There will be Stable versions in this thread? i mean over time of course.
Click to expand...
Click to collapse
probably not.
Lapyyyyyy said:
No sound in incoming - people don't hear me.
Click to expand...
Click to collapse
flash mic fix.
kylon said:
probably not.
flash mic fix.
Click to expand...
Click to collapse
Thank you Kylon.
Three questions please:
-do we need to make a clean installation starting from this new nightly build for the first time?
-can we just dirty install for next nightly after this first one?
-will the headset mic be fixed?
Thankssssssssss
Clean install the dirty.
No guarantee
Installed per instructions, played with it a bit then restarted and since then dead black... Never happened something like this before...
Sent from my Desire S using Tapatalk
Last kernel (from build 28.10.2014) don't work with another ROMs - bootloop/restarts... Last kernel for me is ok. I think had been something new, like problem with sim card, if u remember year ago).
Restart phone... All is ok - without any issues.
Men, thank for hard work and your time!
docertabum said:
Installed per instructions, played with it a bit then restarted and since then dead black... Never happened something like this before...
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
tomorrow i ll make a test kernel.
connect your phone via usb and use monitor (android sdk) to see the log. or you can use adb
Kylon, how different are these nightly from your last build on the other thread? I mean, do we need to update every day? So many changes every day?
Grazie
They are "clean", no test stuff.
No saga changes for now, only cm fixes/new features
kylon said:
They are "clean", no test stuff.
No saga changes for now, only cm fixes/new features
Click to expand...
Click to collapse
On the first page, intallation instructions there is:
"
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
[* This should be a temp step]Download this fix."
What fix are you referring to? I found just the mic fix flinny zip attached
grazie
---------- Post added at 11:26 PM ---------- Previous post was at 11:22 PM ----------
Lapyyyyyy said:
Last kernel (from build 28.10.2014) don't work with another ROMs - bootloop/restarts... Last kernel for me is ok. I think had been something new, like problem with sim card, if u remember year ago).
Restart phone... All is ok - without any issues.
Men, thank for hard work and your time!
Click to expand...
Click to collapse
Hi is this new rom so different from the previous one ? everything working fine so far?
thanks
kylon said:
They are "clean", no test stuff.
No saga changes for now, only cm fixes/new features
Click to expand...
Click to collapse
Thanks for your effort. Besides Wifi Ap and calling mic needs fix, other than that it is working fine. I do not have headset though. Very smooth, fast and stable so far. Again thank you very much for your effort.
Same problem
docertabum said:
Installed per instructions, played with it a bit then restarted and since then dead black... Never happened something like this before...
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
+1
dead screen after reboot
Ammiraglio said:
On the first page, intallation instructions there is:
is this new rom so different from the previous one ? everything working fine so far?
Click to expand...
Click to collapse
Hi! Everything works, with change file audio (fix is in this thread, at 1t post) works all good. Different - don't know
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM12.1 Lollipop Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM 11.0 and 12.0 builds. Builds are generated automatically on Mon/Wed/Fri/Sun. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
Mustaavalkosta
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-12.1-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-12.1-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
Kernel
Source: github
Compiler: stock AOSP gcc-4.8
Branch: cm-12.1
Kernel Version: 3.0.101
defconfig: saga_defconfig
Contact:
My Google+
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Download and install the latest recovery here.
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: Hey, my old phone is running the latest Android version, i want to thank someone!
A: Press thanks button here
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM12.1 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm12.1
cd cm12.1/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-12.1/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
Unofficial CyanogenMod 12.1 Nightlies, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl, Phantom Shadow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Twrp 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2015-04-02
Last Updated 2017-01-04
Bugs / Not working stuff
headset mic in call
kylon said:
ffc camera
headset mic in call
Click to expand...
Click to collapse
Thanks, Kylon, Mustaavalkosta, Paunb_nl, and Phantom Shadow, for being active in supporting DS's community with up to date development. I am very appreciated your kind contribution. Thank you very much.
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Lapyyyyyy said:
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Click to expand...
Click to collapse
Yeah, I fell asleep before the build finished and I had chance to say the same here that I already said on the ace thread:
First build is now on the mirrors. Expect everything to be broken, be thankful for anything that works. There's no schedule for these nightlies yet as I haven't really had time to think how I'll juggle 3 different versions so they don't start compiling at the same time. New builds will come whenever I feel like making one until things settle down a bit and build schedule is decided.
Lapyyyyyy said:
Writes
Not enough memory. Please delete minimum 250 mb...
I see in the settings is all right.
Phone has lags
Thank you so much!!!
EDIT: cyclic reboot
Click to expand...
Click to collapse
Thanks, I got the same thing as you mention plus android keyboard FC. However, it is the first built, just booted up is alright. The rest is leaving for Mustaavalkosta to take care of. If DHD is working, DS should be working as well. Thanks for Mustaavalkosta hard work.
Hi Mustaavalkosta, CM-12.1-20150403-UNOFFICIAL-saga.zip faced the same issues as previous built, Android keyboard FC, not enough space for the system. There should be somethings wrong because the internal storage still has 1.03 GB available as well as my SDCard still has 14 GB available space. However, front camera is working on this built. I am wondering if it is possible to copy files related to camera from this built to CM-12 and which files should it be replaced. I am trying to produce logcat without success. I am sorry about that. Thank you very much for your great effort.
Thanks, Mustaavalkosta, I got the answer by replacing Camera2.apk from this built to CM-12 by installing using root explorer and front camera is now working on my device, CM-12 Rom.
kylon said:
ffc camera
headset mic in call
Click to expand...
Click to collapse
No, it is not. Front camera is working fine on CM-12.1. Thanks.
Can I perform update from CM12 to 12.1?
@qd42: Shouldn't be a problem since it's a minor Android update. But since this is in alpha state I'd suggest you wipe.
Same for me: "not enough space", keyboard FC on first boot (works good now in German). Front-camera works flawlessly. I'll be testing more.
Well, I'm tried to make update from CM12 and I don't reccommend to do this to others because of various system errors after boot like "android.process.acore errors".
How can i install this rom ?
I am using TWRP 2.8.5.2 as Recovery
I have swiped evertyhing i could on the phone
When i choose to install this ROM i get the Message: script succeeded result was /system
After flash boot.img, the Cyanogenmod-Logo still dont disappear after 10 Minutes ... (while booting)
€dit: Forget it. After 15 mins the Logo disappeared and the system has booted. But my SIM was not detected ...
€dit: SIM was detected ... but the phone tells me, i have less than 250mb free space ... wth ? I thought after a full wipe it should be at least 300mb free space ...
LuckyLoop said:
€dit: SIM was detected ... but the phone tells me, i have less than 250mb free space ... wth ? I thought after a full wipe it should be at least 300mb free space ...
Click to expand...
Click to collapse
It's a bug. As a temporary workaround remove /system/media/bootanimation.zip and warning should go away.
Mustaavalkosta said:
It's a bug. As a temporary workaround remove /system/media/bootanimation.zip and warning should go away.
Click to expand...
Click to collapse
Thanks MUstaavalkosta. So far, It is working fine. Flashed superSU v.2.48 beta makes it better. Ringtone is good, front camera is good. Just keyboad and google service have stop sign showed up some time. In fact they are still working. Thanks for your kind contribution.
I can't install any apps from the store get an error ’'-504''
Remove Boot animation before flashing as Mustaavalkosta suggested.
Okay,now that ive taken a break from studying,i can post a bug report on this. Accorrding to what ive seen,other than the known,solved ones,there are no other bugs. Much faster than 5.0.1 thats for sure. This is my new daily driver.
Sent from my SM-G900T using XDA Free mobile app
Hey guys, last time I flashed this the opposite side was not able to hear me upon my first call and the call quality was terrible when I returned the call after.
Of course I was in an area with good signal coverage.
Was this solved lately by any chance?
The space (LOL) problem is still unsolved. I believe that
Code:
55d502e msm7x30: use halfres bootanimation
was supposed to fix it.
vojtah1 said:
The space (LOL) problem is still unsolved. I believe that
Code:
55d502e msm7x30: use halfres bootanimation
was supposed to fix it.
Click to expand...
Click to collapse
How about without gapps? Works fine here on ace after that commit.
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
General:
These are UNOFFICIAL CM13.0 Marshmellow Nightlies brought to you by Open Desire Project and TeamCodefire as a continuum to CM 11.0, CM 12.0 and CM 12.1 builds. Builds are generated automatically on Mon/Wed/Fri/Sun. Process starts around 00:30 PST/PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Last 7 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
Mustaavalkosta
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
Open Desire Project
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies
Download gapps from here
Put the files on SD card
Reboot to recovery
Do factory reset (ie. format /system, /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-saga.zip
Flash gapps zip
Remember to flash boot.img via fastboot if you have S-ON
Reboot and enjoy
Update instructions:
Download Nightlies
Put the file on SD card
Reboot to recovery
Flash cm-13.0-YYYYMMDD-UNOFFICIAL-saga.zip
Remember to reflash boot.img via fastboot if you have S-ON
No need to flash gapps as CM backuptool script should take care of them (results may vary depending on which gapps package you are using)
Reboot and enjoy
Kernel
Source: github
Compiler: stock AOSP gcc-4.8
Branch: cm-13.0
Kernel Version: 3.0.101
defconfig: saga_defconfig
Contact:
My Google+
#opendesireproject @ freenode
Donations:
For build server & hosting: codefi.re (use the donation button)
Do not donate to me, but if you insist on donating, I suggest you donate that money to Mustaavalkosta or EFF instead here: https://supporters.eff.org/donate
FAQ:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
Or I'm having other recovery issues.
A: Download and install the latest recovery here.
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: Hey, my old phone is running the latest Android version, i want to thank someone!
A: Press thanks button here
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM13.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm13.0
cd cm13.0/
repo init -u git://github.com/CyanogenMod/android.git -b cm-13.0
mkdir -p .repo/local_manifests
wget https://github.com/OpenDesireProject/android/raw/cm-13.0/local_manifest.xml -O .repo/local_manifests/local_manifest.xml
repo sync
. build/envsetup.sh
lunch cm_saga-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/saga/ directory.
Q: My problem is not listed here.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[ROM][UNOFFICIAL] CyanogenMod 13.0 Nightlies OpenDesireProject, ROM for the HTC Desire S
Contributors
kylon, Mustaavalkosta, paulb_nl, PhantomShadow
Source Code: https://github.com/OpenDesireProject
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Twrp 2.8.7.0
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-12-04
Last Updated 2017-01-04
Bugs (Device specific):
Glitches here and there
Headset Mic in call
SAGAOPT SETUP INSTRUCTIONS (see also Mustaavalkosta dhd post)
Disclaimer: You will lose everything on your sdcard if you follow these instructions so take appropriate steps to secure your data before continuing. Also this will be a "clean flash" from the start due to different partition layout.
Prerequisites:
TWRP for sagaopt by @jrior001
saga cm13 zip
Gapps and addons if you want them. IIRC, there was around 400-500MB space left on new /system partition after flashing base gapps package so there's a bit more room for addons.
If you have already partitioned your sdcard you may want to repartition it to have only single partition because you won't benefit from having separate sd-ext partition with this variant build. I won't write anything about this as I expect you can reverse what you have done yourself.
Installation instructions:
Flash TWRP in fastboot or your current TWRP (Install > Images > etc.)
Reboot to recovery even if you are already in TWRP. You need to reboot to be in newly flashed sagaopt TWRP.
Wipe cache and system under Advanced wipe.
Convert your sdcard to either EXT4 or F2FS under Advanced wipe by choosing data partition > Repair or Change File System > Change File System > EXT4 or F2FS.
(Optional) If you had your old /data partition formatted as F2FS you also need to convert it to EXT4 meaning converting system partition in the sagaopt recovery.
At this point your sdcard is completely empty so you will need to move the ROM zip and any additional zips into sdcard or use adb sideload.
Install cm-13-XXXXXXXX-UNOFFICIAL-sagaopt.zip and gapps.
Reboot
kylon said:
Bugs (Device specific):
Glitches here and there
Headset Mic in call
Click to expand...
Click to collapse
Thank you very much Kylon for putting up the thread for CM-13. I have already tried 20151203 and 20151204 nightlies with no CM Account and facing problem on flashing either Open GApps or Delta GApps for MM, it is showing Setting Wizard has stop mainly and some time Google play service has stop and System does not response all the time making setting up impossible. Anyway no problem on ROM flashing. Thanks.
It s a known problem on cm13.
You have to delete setup wizard
kylon said:
It s a known problem on cm13.
You have to delete setup wizard
Click to expand...
Click to collapse
Thanks for your prompt reply. I shall do that.
<Reserve>
aakashasaj said:
<Reserve>
Click to expand...
Click to collapse
Hi Kylon,
I am wondering if the keyboard and google play service stop could be solved on CM-13 sagaopt. Thank you very much.
yea, the official cm-13 is still in testing, every fc will be fixed when cm is more stable
f2fs test
kylon said:
yea, the official cm-13 is still in testing, every fc will be fixed when cm is more stable
f2fs test
Click to expand...
Click to collapse
Thanks. I will try the kernel.
kchaisu said:
Thanks. I will try the kernel.
Click to expand...
Click to collapse
It caused boot loop at the HTC logo. Thanks for your kind contribution. I have noticed that system partition is always formatted to ext4 no matter how you have changed to f2fs and finally it will be formatted back to ext4. Thanks.
Can you take a log?
kylon said:
Can you take a log?
Click to expand...
Click to collapse
I do not know how to take a log when it did not boot up. Please tell me. Thanks.
kylon said:
Can you take a log?
Click to expand...
Click to collapse
I flashed your kernel and everything is all right! Any bootloop I didn't get. Work well, don't see any difference.:highfive:
kchaisu said:
I do not know how to take a log when it did not boot up. Please tell me. Thanks.
Click to expand...
Click to collapse
Mmh, can you try with a clean install?
Maybe something went wrong on your phone.
Thats ok, this will not turn saga in a quad-core phone but it should be a better f2fs version, maybe faster and more stable
kylon said:
Mmh, can you try with a clean install?
Maybe something went wrong on your phone.
Thats ok, this will not turn saga in a quad-core phone but it should be a better f2fs version, maybe faster and more stable
Click to expand...
Click to collapse
I made a clean install, factory reset and all wiped except internal memory and SD-Ext and also change file system to f2fs. It did not boot up with black screen. So, if you and Lapyyy have no problem with the kernel, it should be my device problem or set up. However, I have tried with every nighlies and Open Gapps and Delta Gapps and have faced the same problems. Now I shall try with difference SDcard with different format. Thanks for your kind contribution.
I don t have a saga xD
Cannot test.
You should be able to take a log with android monitor and a boot.img with secure=0
kylon said:
I don t have a saga xD
Cannot test.
You should be able to take a log with android monitor and a boot.img with secure=0
Click to expand...
Click to collapse
Thanks for your prompt reply. We will see how the problem could be solved. Now I reformatted the Data partition to EXT4 and all the stuff was gone. I have to copy all necessary files to the SDcard again and will try your kernel. By the way replaceing AnySolfKeyboard by F-Droid eliminated FC on keyboard issue and making Google Account setup possible. Thanks.
Amazingly mature
I'm running 2015-12-06 since yesterday evening, and I'm amazed how mature it already is. It seems quick stable and "slick."
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
As hinted by @kchaisu (thanks!) I've installed an alternative keyboard app (Google's kbd), and now it's running really well.
The old Facebook problem (that often the device reboots when installing the app) can still be observed, but maybe it's just that our Saga has too little RAM.
Thanks, @kylon and @Mustaavalkosta, and all others who contribute to this, for breathing new life into our little Sagas...
ralfbergs said:
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
Click to expand...
Click to collapse
Well, nothing is removed per se but system hides the camera icon etc. if it can't find appropriate camera hardware which it currently can't find because camera libs won't load due to missing symbols.
ralfbergs said:
I'm running 2015-12-06 since yesterday evening, and I'm amazed how mature it already is. It seems quick stable and "slick."
One thing I've noticed is that the camera API doesn't seem to be implemented/functioning yet. This is probably the reason why no camera app is included, right?
As hinted by @kchaisu (thanks!) I've installed an alternative keyboard app (Google's kbd), and now it's running really well.
The old Facebook problem (that often the device reboots when installing the app) can still be observed, but maybe it's just that our Saga has too little RAM.
Thanks, @kylon and @Mustaavalkosta, and all others who contribute to this, for breathing new life into our little Sagas...
Click to expand...
Click to collapse
Actually, I got the idea from HD CM-13 forum which was post by @marek287. Thanks to him.
Thanks to Mustaavalkosta and Kylon for the CM-13-20151211-sagaopt nightly. This bulid is fast booting up for GApps. However, SetupWizard and AOSP Keyboard still remains FC. Thank you very much.
Code:
Code:
/*
* Your probably long expired 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
* and point my finger right back at you.
*/
Installation Instructions
It will wipe your entire SD card! In order to make things work better, I've set it up to use the entire SD card as /data as opposed to having two partitions. The advantage is that you don't have to pick a size of /data.
If on a BML rom (stock-based GB)...
Untested, but is setup to hopefully work. If it doesn't flash my 6.0 Omni first
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want gapps, reboot to recovery, wipe data+cache and install gapps.
5. If you want root, flash according to instructions in Post #3
If on an MTD rom (CM7 and all ICS+)
1. Reboot to recovery
2. Wipe data, dalvik/art cache, system, and cache partitions
3. Install zip. First time will fail and let you know its repartionning. Second time it will reboot a couple of times, don't be worried.
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 20+ minutes, pull the battery and reboot to recovery.
Things to Take Note Of
I actually have a T959P, not a T959V... It was released by Telus in Canada. It is a very similar device (I can run ROMs for the T959V with limited problems - ie sometimes I get wakelocks and the gps never works), it has a different GPS chipset and also uses different cell bands (but I can still use your guys modems but I lose access to the 850Mhz band). I have created a build specifically for the T959V as best as I can guess.
If you're coming from either the last Lollipop build or the initial pre-release Marshmallow build, there is a bug in TWRP that will prevent flashing anything but the ROM. To get around this, please flash the Marshmallow zip, then reboot to recovery, and then follow the typical instructions.
If you decide to install gapps at a later date (ie after you've installed the ROM), you must do a factory reset first - otherwise you will get force-closes upon bootup
If you come across a bug, feel free to let me know by posting in this thread. I will not be working non-stop on this project, but will try to fix bugs that affect me as this is still my main phone (out of choice, not necessity).
This build is very close to the official AOSP source code. Recovery is TWRP but otherwise there aren't any added "features"
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully. Opengapps pico works on the latest 7.0 build, untested on 7.1 but should work just fine
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Camera (built-in app needs workaround, see below)
RIL
SMS
Recovery
Bluetooth - first time it won't enable if enabling through settings, back out and then second time it will. Works just fine from status bar pulldown
Wifi
Vibration
Automatic Brightness
Compass
GPS on T959P, untested on T959V
Headset Buttons
SElinux in enforcing mode - this may have broken the T959V's gps...
Partially working
Camera and Browser apps need to have all their permissions manually enabled through settings for full functionality. This is because I've used the older Camera app (which hasn't been updated for dynamic permissions) and the older Browser app as the new one is simply a test shell with no features (thanks Google!)
What's been removed
TV-Out - It was removed upstream plus I think binary blobs would need a ton of shimming in Lollipop+
Everything else is not tested!!!
XDA:DevDB Information
AOSP 7.x for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/xc-racer99/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Created 2016-10-22
Last Updated 2016-10-21
Thanks Time!
Thanks Time!
This would not have been possible without the following people:
Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to FB and Dao for their work on the CM-11 device tree. I used several of their fixes.
Thanks to noiphonehere for his device trees and kernel, most of my work was based off of his.
Thanks to the OMAP4 AOSP team for their work on porting CMA to a 3.0 kernel.
Thanks to bhundven and the other members of teamacid for their work on the aries kernel.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P and without him I'd still be on stock...
Build your own!
Follow https://source.android.com/source/initializing.html. The branch you want when you run repo init is the latest tag from https://source.android.com/source/build-numbers.html#source-code-tags-and-builds for your desired android version (7.0 or 7.1). Before you run repo sync, from the WORKING_DIRECTORY/.repo folder, run "git clone https://github.com/xc-racer99/local_manifests -b BRANCH" where BRANCH is either aosp-7.0 or aosp-7.1. Continue on with the build guide, the device codename you want is "galaxys4gmtd".
If you want to build the kernel, follow the instructions in WORKING_DIRECTORY/kernel/samsung/aries/AOSP_README. Put the resulting arch/arm/boot/zImage in device/samsung/galaxys4gmtd-kernel
Other aries devices (captivate, i9000, i9000B, vibrant) should be fairly easy to do (ie the galaxysmtd on my github as well as the captivate trees work). The fascinate and p1 would need a fair bit of work.
Changelogs
Changelog for 2016-12-19
December security patches
goes back to the older graphics drivers so hardware recording works but has a kernel patch to prevent crashes
Tweaked the graphics drivers options so it seems a little bit faster
Tweaked the RIL a little bit for better stability
Other things I've forgotten about, see github for details
Changelog for 2016-12-19-V2
Kernel without slowdowns....
Changelog for 2017-1-19
selinux to enforcing - this may break the T959V's GPS - if it does, let me know and send me a dmesg and I'll fix it
Update to the interactive governor - should have less slowdowns if using the default governor
Slightly better RIL reliability (I think)
Better low memory killing - we now don't run out of memory as often
Hardware decoding re-enabled
Slightly less intensive background services
Based on 7.1.1_r13
Source Code, Downloads, Root Options
Main Source
https://android.googlesource.com/
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see aosp-7.x branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see aosp-7.x branch).
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see aosp-7.x branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see aosp-7.x branch)
http://github.com/xc-racer99/android_patches for all the patches necessary for the device to work properly (see aosp-7.x branch)
Downloads!
All builds can be downloaded from AndroidFileHost at https://www.androidfilehost.com/?w=files&flid=58191
Gapps
The smallest http://opengapps.org/ package for 7.0 is known to work, but any small 7.0 gapps package should work. However, they will cause the device to slowdown significantly as they use a fair bit of RAM. Gapps are untested on 7.1
This ROM is compatible with MicroG (https://microg.org/ and http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616) gapps. This is an open-source reimplementation of Google Play Services that doesn't track you and uses way less battery than the original.
Root
Root is achieved via Magisk or SuperSU.
MagiskDue to our odd partition layout, you need to use my custom Magisk install zip (source code here) attached to this post and not the official install or the Magisk Manager install. Then follow the instructions on how to root/install other modules from http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 Also, don't try to use the official Magisk uninstall tool as it won't work.
SuperSU
Please note: I've been told this doesn't work any more, YMMV
Again, we need a custom SuperSU install zip for it to work due to our partition scheme. It should be an all-in-one zip so it's simplier than Magisk (but not open source). This is based off of the latest (at time of writing) 2.79SR1 release, the diff is below
Code:
diff --git a/META-INF/com/google/android/update-binary b/META-INF/com/google/android/update-binary
index d437f6f..3a312bf 100644
--- a/META-INF/com/google/android/update-binary
+++ b/META-INF/com/google/android/update-binary
@@ -642,16 +642,23 @@ detect_systemless_required() {
find_boot_image
CONTINUE=true
+if false ; then
if [ -z "$BOOTIMAGE" ]; then
# no boot image partition detected, abort
return
fi
+fi
# extract ramdisk from boot image
rm -rf /sutmp
mkdir /sutmp
+if false ; then
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero "" "" "" "LD_LIBRARY_PATH=$RAMDISKLIB $BIN/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if (! $CONTINUE); then return; fi
@@ -1331,6 +1338,8 @@ else
ui_print_always "Boot image patcher"
ui_print "******************"
+if false ; then
+ # SGS Modification - we don't have a "real" boot image
ui_print "- Finding boot image"
find_boot_image
@@ -1357,6 +1366,10 @@ else
fi
check_zero_def "- Extracting ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --bootimg-extract-ramdisk $BOOTIMAGE /sutmp/ramdisk.packed"
+else
+ mount /ramdisk
+ cp /ramdisk/ramdisk.img /sutmp/ramdisk.packed
+fi
check_zero_def "- Decompressing ramdisk" "LD_LIBRARY_PATH=$SYSTEMLIB /su/bin/sukernel --ungzip /sutmp/ramdisk.packed /sutmp/ramdisk"
if ($CONTINUE); then
@@ -1545,6 +1558,7 @@ else
check_zero_def "- Calling user boot image patch script" "sh /data/custom_boot_image_patch.sh /sutmp/boot.img"
fi
+if false ; then
if ($CONTINUE); then
DEV=$(echo `resolve_link $BOOTIMAGE` | grep /dev/block/)
if [ $? -eq 0 ]; then
@@ -1564,6 +1578,10 @@ else
dd if=/sutmp/boot.img of=$BOOTIMAGE bs=4096
fi
+else
+ cp /sutmp/ramdisk.packed /ramdisk/ramdisk.img
+ umount /ramdisk
+fi
rm -rf /sutmp
fi
Link for the download ROM is not working... it is private... ?!?
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
pickandrew said:
Link for the download ROM is not working... it is private... ?!?
Click to expand...
Click to collapse
Shaggy_thecat said:
Here is the link to the rom that is not private https://www.androidfilehost.com/?w=files&flid=58191
Click to expand...
Click to collapse
Thanks, I used the link that I would use if I was already logged in, my bad. OP is now updated.
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
graycow9 said:
It's been a while, no home internet and very busy life lately but the time I did get The 7.0 zip to flash (0930) it was running very well, no random reboots and limited freezes (just 1 really)
BUT. I always reinstall a new ROM to get the process down and- I haven't been able to get it running again. Let alone with root which I haven't managed to do. When I install the ROM now it gives me a quick first boot however it says encryption unsuccessful and asks me to reset. Resetting and factory resetting as well as formatting won't help it.
Excellent work ^_^ you're becoming the new SGS4G guru around here
As for a new setting in the dev options, labeled Consistent Logging-- if I turn this on is it A: Safe in terms of information vulnerability and B: Will it fill up my SD card quickly with a mass amount of logging data?
Click to expand...
Click to collapse
Hmm, flash the ROM, go into recovery, change the filesystem of /data to ext4 or f2fs. The error sounds as if the sdcard is formatted as fat while it shouldn't be. If that doesn't work, please send me the contents of /sdcard/aries_mtd.log after you've installed it.
Hadn't noticed the new "persistent logging" section. I suspect that what it does it keep the logcat contents over a reboot. Since the logcat does have a max size, it is probably safe to enable it. I highly doubt it contains any more info than a regular logcat.
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Domunus said:
Thanks for keeping this device alive in this community! My kids wanted to use it for simple games so I dusted it off and came here to see if anything was still in development and sure enough there was!
I tested going from BML stock and it worked! I had to restart the install 5 times, but it ultimately took. The first two times installed TWRP, then it rebooted into TWRP. Then it took 3 additional times before it went through the whole install. It booted up fine, but I had messed up and forgot to do a full reset before install gapps. So it would boot the encryption screen telling me it was interrupted and I had to reset the phone. Unfortunately at that point no matter what I did it would always boot to that encryption error screen. So I wiped completed and started over but mistakenly flashed the 7.1 build. It went through but was stuck on a boot loop. So now i can't install 7.0 because it keeps telling me it can't install over newer builds. Is there anything I can do to fix this or do i have to start from stock all over again?
Edited* Update
I went ahead and started from scratch but still ran in to the same problem with the encryption. Didn't install gapps this time.
Click to expand...
Click to collapse
Ok, sounds like a messed up somewhere. I'll do some testing and try to release an updated build. Could you please post the output of /sdcard/aries_bml.log and /sdcard/aries_mtd.log? The "Encryption Unsuccessful" message sounds as if the SD wasn't properly formatted to ext4/f2fs.
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Domunus said:
Hi xc-racerr99, I found what the issue was. Apparently I had an extra partition on the sdcard. After removing it and running the install script again everything booted up and i'm now using the ROM! It's awesome I have Nougat on this old Galaxy S. Without Gapps it's been running really stable and very responsive..
However, at this point, I've tried opengapps pico and TKgapps pico and neither work. The script runs and says update completed, but it's too fast. When I boot to the ROM no gapps were installed. Is there another gapps you would recommend trying?
Click to expand...
Click to collapse
Odd, I thought my install script removed the extra partition.
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Doesn't work....
I'll try to do some more testing with gapps and from stock with 1 or 2 partitions when I get a chance.
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling. ?
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
graycow9 said:
I figured out a sure fire way to boot 7.0, I'm running it as I respond with XDA app right now. But to keep it short if possible, I just fix permissions then factory wipe before I run the zip- do this while on CWM right after you heimdall to BML.
So to recap:
1- Flash to stock via heimdall
2- Fix permissions + factory wipe
3- Flash 7.0 zip
4- TWRP should boot- so flash ROM once more - wipe caches
5- Reboot and chew some nougat
Will follow up with a log next time I try to get the 7.1 rolling.
Oh! And when I add my email (hotmail) I get a bad handshake everytime. Do I need gapps to sync my contacts?
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, I get a bad handshake as well. Only happens with hotmail/oulook accounts, my gmail and my other email work just fine.
I figured out what was causing the issues with install from BML - on TWRP boot, it wasn't setting up the sdcard properly. I've now fixed it so that it should work regardless (in the next build, obviously).
Anyways, it sounds as if there's some issue with recovery. You could try replacing the ramdisk-recovery.img in the ROM zip you downloaded with the one from https://www.androidfilehost.com/?fid=457095661767105384. Then reboot to recovery and flash your gapps package again.
Click to expand...
Click to collapse
Gave this a try and still no luck.
Update **
It actually killed the recovery. Recovery just keeps crashing and rebooting when trying to get in to it. Tried it from the a clean install and same results. Will wait for your next build. Thanks for putting time in to this!
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore ?? (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build ?
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
graycow9 said:
Odd, it lets me add my gmail but only syncs my emails- no option for contacts still. I ought to keep a vcf from my other device jic.
The performance is even better than M and it doesn't have the weird battery glitch anymore (I think the new partition layout helped a lot.)
Another thing I noticed, sometimes my SIM won't register or gives me a no signal indicator. I can't get root still either[emoji14]still poking around. Looking forward to the next build
Edit: Another bug I noticed is the inability to save files through the browser or Tumblr app for example.
(By the way, just wanted to add, I hope I'm still being more help than a nag or something. I aim to be helpful. So I look for things that seem astray. Heh)
Sent from my SGH-T959V using XDA-Developers mobile app
Click to expand...
Click to collapse
I've never used the contact sync.
With SIM not registering, it's because Google introduced a bug and the workaround the bug causes the SIM to occasionally not work. One of the problems with legacy devices I guess.
With the files not saving, manually grant the storage permission in Settings->Apps - it doesn't seem to automatically update for most apps.
With root, sounds like I should modify the SuperSU install zip as it's easier to use (but not open-source). For the PHH Superuser, you need
1) The Magisk-7-SGS.zip from my thread.
2) The phh-superuser-r259.zip from the Magisk root thread (link in OP)
3) The PHH Superuser app from the Play Store or FDroid
Even then, it only works for certain apps as it doesn't mount anything to /system/xbin/su which is what some apps look for
Edit: And I have no issues if you keep posting here with the problems you find, it's good to know.
bootloop
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
asmalldharma said:
just tried to flash this 7.1 rom from your omnirom 6.0. Seemed to flash ok as described. couldn't get pico opengapps to flash but ignored it. Now it's stuck in a bootloop and I can't get into recovery using hardware buttons. Any guidance as to how I should proceed? As a relative novice, can I push a new recovery through ADB and try again?
Click to expand...
Click to collapse
Well, it depends on where you are bootlooping. If you're stuck at either of the first two splash screens, then you're out of luck with ADB as it isn't available yet. If you're bootlooping but getting to the bootanimation, then you can. To do so, run
Code:
$ adb root
$ adb shell mkdir /data/ramdisk
$ adb shell mount /dev/block/mtdblock5 /data/ramdisk
$ adb push ramdisk-recovery.img /data/ramdisk
$ adb reboot recovery
where ramdisk-recovery.img is from the AOSP 7.0 zip.
If you're stuck at the first or second splash screens, then you need Odin or Heimdall. With heimdall, you can do
Code:
$ heimdall flash --KERNEL boot.img
where the boot.img is the one from Omni 6.0, the one from 7.x won't work on its own as the recovery is not stored in it. You can use Odin to go back to stock.
I haven't tried gapps so I guess I should sometime and see what the issue with them is.
Gets to the second splash screen. I'll give that a shot when i have some free time. I'm really looking forward to getting this working as I'm amused by the idea of my oldest android phone running the newest OS before my other two.
Update: couldn't get it to work with my cheap laptop. Kept throwing up the libusb 12 error. Then when i finally gave up and pulled the battery, I noticed it was starting to bulge a little. I think I'm out for a while. I'm hoping i can come back to this soon.
Sent from my A0001 using XDA-Developers mobile app
DESCRIPTION
Unofficial LineageOS ROMs for Mi-4c (libra) and Mi-4s (aqua), with base-layer enhancements and performance optimizations. Version 15.1/16.0/17.1/18.1 are available for download.
FEATURE
The following items may not be available for all versions, please use the latest build!
Click to expand...
Click to collapse
Build with user variant instead of userdebug (to reduce image size and improve performance).
CPU/GPU is overclocked with optimized voltage/bus-cci and 300 Hz/Jiffies kernel clock frequency. [16.0 +]
EAS (sched cpufreq governor from linux-3.18) CPU scheduler implemented. [16.0 +]
Full-weight NotoSansCJK fonts included (to display East Asian characters with more font weights).
High screen refresh-rate (75 Hz) support for Mi-4c with "Sharp-rsp61322 LCD" screen. [16.0 +]
Implement ZRAM with ZSTD crypto algorithm (KSM is used after 20210116) to improve I/O performance on devices with 2GB RAM. [16.0 +]
Linux kernel is built by clang-12 toolchains, with Polly + LTO + -Ofast optimization to get better performance. [17.1 +]
Pre-dex2oat with everything filter globally (sacrificing space and first-install time to improve efficiency).
Remove or disable unnecessary kernel configs and modules, also includes some other optimizations. [16.0 +]
Remove unnecessary apps/binaries/libraries/services from system. [16.0 +]
Signature spoofing support (ready for MicroG, including Chinese translations).
User-friendly controller for special features in Settings app (like CPU overclock, Edge gesture and Screen refresh rate). [17.1 +]
...
STATUS
Go to GitHub Issues for more details and give me feedback.
Click to expand...
Click to collapse
Working
Basic hardware
Baseband/SMS
Bluetooth
Camera/Flashlight
IR remote
Speaker/Microphone
Wi-Fi
Extras
Camera API2 (with patch) [17.1 +]
Edge gesture (in Settings > System > Buttons) [16.0 +]
Overclock control (in Settings > Battery > Battery saver and performance) [17.1 +]
Screen refresh rate (in Settings > Display) [17.1 +]
Not working
SELinux permissive [16.0 +]
VOLTE (won't fix because of no compatible IMS stacks) [16.0 +]
DOWNLOAD
GitHub Releases: https://github.com/BYZYB/android_device_xiaomi_libra/releases
Kernel/ROM: https://www.androidfilehost.com/?w=files&flid=287533
TWRP: https://www.androidfilehost.com/?fid=8889791610682882451
SOURCE
Device: BYZYB/android_device_xiaomi_libra
Forked from (16.0 +): android_device_xiaomi_libra + android_device_xiaomi_msm8994-common
Kernel: BYZYB/android_kernel_xiaomi_libra
Forked from: android_kernel_xiaomi_leo
Vendor: BYZYB/android_vendor_xiaomi_libra
Forked from (16.0 +): android_vendor_xiaomi_libra + android_vendor_xiaomi_msm8994-common
Custom changes: repo_17.diff + repo_18.diff
Thanks to all developers and users (Gah0 | Mortezadadgar | Xiaomi classic dev | ...) who contributed to Mi-4c/Mi-4s (including other devices shipped with MSM8992/8994 SOC) or gave me help!
Click to expand...
Click to collapse
TIPS
Here are some tips which may improve your experience or resolve some problems.
Basic quality assurance: I only have one smart phone (3+32GB Mi-4c ×1), so the ROMs here should at least satisfy my daily usage.
This project will be kept maintained even after I bought my new mobile phone (8+128GB Mi-Mix-2 ×1) in 2021. My Mi-4c is one of the most meaningful items of my own, it's not easy to leave it behind in the drawer and say goodbye. The new battery and rear cover (thanks to yipinghuang1991) will refresh this old device and make it usable again.
Even though the signal icon in status bar shows "No signal" at the first minute after boot, the device is still able to receive SMS and phone calls (so the device does have signal, but the system doesn't admit it at all).
If the free space in /system is not enough to install GAPPs, try to delete /system/fonts/NotoSansCJK.ttc to get about 100MB free space (If Chinese/Japanese/Korean is not your main language). Removing the prebuilt Webview packages (about 120MB) after installed another one is also a solution.
If you found random reboot on your device with overclock enabled (or just updated to lineage-17.1-20201216 and left overclock option unchanged), please disable this feature to see if this issue is resolved. Go to Settings > System > Battery > Battery saver and performance, enable then disable "High performance mode", and reboot your device. If you are using lineage-17.1-20210209 or newer, it's no need to do such steps after a clean install (as both persist.sys.cpu_overclock and persist.vendor.edge_touch_mode are default to false by default).
It's highly recommended to disable system logs to reduce resource consumption (for better performance and privacy), unless you're going to collect system logs. Go to Settings > System > Developer options, and set the value of "Logger buffer sizes" to off.
It's not recommended to use SELinux enforcing mode even if it's supported in some builds. Also, please consider the negative effect of I/O performance before enabling disk encryption, unless you really want to.
BUILD
As all source codes and custom changes in my LineageOS ROMs are open-source, you are permitted to build your own ROM or kernel (not only for LineageOS) with my sources for non-commercial purpose.
There are many documents about how to build custom Android ROMs in Linux/OSX, so I will not post these basic steps here to reduce redundancy. However, there are still some important things which may not be included in other documents. Here are some basic steps about what you should do (using lineage-18.1 as example), you can also take a reference to other tutorials.
Install necessary packages
There are a number of "necessary" packages listed in most tutorials, but not all of them are needed. Here are the packages you need to install manually on Ubuntu or Debian.
sudo apt install bc bison git gnupg make repo rsync unzip zip
Sync Android sources
You need to download and update your local repo with upstream sources regularly, in order to get new changes as soon as possible (just like other open-source projects).
Init repo to current directory: repo init -u https://github.com/LineageOS/android.git -b lineage-18.1 --depth=1
Sync all repos and prune unused branches: repo sync --prune
If nothing wrong happened, the LineageOS sources have been downloaded to your computer (about 100GB). Here are some commands which might be useful in the future.
Show all local changes of your repos: repo status or repo diff
Perform any operations to all repos: repo forall -c "xxx"
Setup local manifest
To sync your Android sources with upstream repos easily, it's recommended to create a local manifest in ./repo/local_manifests/. The local manifest should be a XML file like the following one, any filename is accepted (file: libra.xml).
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="BYZYB/android_device_xiaomi_libra" path="device/xiaomi/libra" remote="github" revision="lineage-18.1" />
<project name="BYZYB/android_kernel_xiaomi_libra" path="kernel/xiaomi/libra" remote="github" revision="master" />
<project name="BYZYB/android_vendor_xiaomi_libra" path="vendor/xiaomi/libra" remote="github" revision="lineage-16.0" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="lineage-18.1" />
<project name="LineageOS/android_hardware_xiaomi" path="hardware/xiaomi" remote="github" revision="lineage-18.1" />
</manifest>
Resolve build errors
Due to some hacks in my device configurations which are conflict with Android build rules, there might be some build errors if using all my repos directly. To resolve this issue, you need to modify project build/make/manually on your disk. After that, you should be able to prepare the necessary environment for Android build without errors.
Setup build namespace only: . build/envsetup.sh
Prepare build environment for Mi-4c with a specified build variant (xxx = eng/userdebug/user): . build/envsetup.sh && lunch lineage_libra-xxx
If you want to build the ROM in "user" build variant instead of the default "userdebug", more changes are needed to avoid build errors or potential bootloop. The following commands are some ways to build a full ROM.
Build full ROM in "user" variant: brunch lineage_libra-user
Build full ROM in "userdebug" variant: brunch lineage_libra-userdebug
Build full ROM with a specified number of threads (x ≤ physical CPU cores): lunch lineage_libra-xxx && make -jx
If you have lunch before, here is the simplest way: m
As git patch files are similar to git diff, you can always do these changes manually without using git am xxx.patch && git reset HEAD^ or other shell commands.
Kernel build toolchains
The kernel supports to be built with gcc-9+ or clang-10+. As Link-Time-Optimization (LTO) for Clang is enabled by default (config: CONFIG_LTO_CLANG), building the kernel with GCC directly will result in build errors. In conclusion, it's recommended to choose Clang as your toolchains for both faster build speed and better performance.
As VDSO compat is enabled (config: CONFIG_COMPAT_VDSO), both arm and arm64 toolchains are needed to build the kernel. Clang could handle different cross compile targets easily (thanks to LLVM), but GCC could not. Also, though the kernel sources are compiled by clang, they will be linked by LD (included in GCC toolchains -> Binutils) with LLVM plugins. In conclusion, if the ROM you are building provides legacy gcc-4.9 toolchains (like LineageOS based projects), it should be safe to go ahead without installing GCC toolchains or Binutils. Otherwise, you need to install both Binutils and Clang packages in your computer to avoid build problems.
If you are using Ubuntu or Debian on your computer, please install the following packages (choose one way).
Using prebuilt toolchains in Android repo (recommend): sudo apt install libc6-dev libgcc-12-dev
Using toolchaings in your distribution: sudo apt install clang llvm-dev
For ROMs without legacy gcc-4.9 toolchains: sudo apt install binutils-aarch64-linux-gnu binutils-arm-linux-gnueabihf
Then you should be able to build the kernel without modifying build configs.
Build kernel image only: make bootimage
Build recovery image only: make recoveryimage
Apply custom changes (optional)
This is great. Is signature spoofing enabled? If not, could it be? MicroG users would like it. Ty.
Edit: signature spoofing is enabled, but It seems LineageOS 17 locked my bootloader.
Edit2: LineageOS 17 do not support custom partition tables. After flashing, my 2.3gb "system" goes to 1.8gb and there's no space left for NanoDroid and other mods.
Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?
rostopira said:
Flashed ok, seems to be working just fine, but can't install gapps due to "insufficient space"
Any advice?
Click to expand...
Click to collapse
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.
WJXXBSH said:
Right, there is really no enough free space in "/system" to install GAPPs (even the "pico" version). If Chinese/Japanese/Korean is not your main language, try to delete "/system/fonts/NotoSansCJK.ttc" to save 117MB free space, which seems enough for the "nano" version.
Click to expand...
Click to collapse
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)
rostopira said:
Thanks for advice, I've removed it, but still not enough space even for pico package
Code:
/system/system # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 888.2M 176.0K 888.0M 0% /dev
tmpfs 888.2M 24.0K 888.1M 0% /tmp
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /data
/dev/block/mmcblk0p44
11.2G 2.9G 8.1G 26% /sdcard
/dev/block/mmcblk0p42
372.0M 440.0K 363.9M 0% /cache
/dev/block/mmcblk0p41
1.8G 1.7G 178.0M 90% /system
UPD: Removed some other noto fonts, symlinked to roboto, deleted ringtones. Got 202M free
I really hope, that won't result in a bootloop
UPD2: It booted, immediately restarted, and booted again successfully
Feels good)
Click to expand...
Click to collapse
It seems you're using lineage-17.0 roms, which needs more free space than 16.0 (eg. the APEX image).
Deleting the fonts that you never used is surely a way to get more space. If you have installed "Android System Webview" (com.google.android.webview) from play store or other origins, removing the prebuilt one from "/system/product/app/webview" should be another possible solution (get another 100MB). However, make sure to choose the new webview package in "Developer settings" and prevent factory reset unless flashing the rom again, or it might result in problems.
Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks
elna.nitz said:
Hello, everyone.
I use TWRP 3.1.1.0 and get error 7
When I try Flash latest official TWRP / or twrp 3.3.0 from here via fastboot I can't boot to recovery.
Which version of TWRP do I need to use to flash Lineageos 17?
Thanks
Click to expand...
Click to collapse
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.
WJXXBSH said:
Try this recovery: https://androidfilehost.com/?fid=1395089523397945946
It's just the one I used on my device.
Click to expand...
Click to collapse
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here (twrp from lollipop - nougat bootloader) I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.
elna.nitz said:
Yes, I already tried that after installing TWRP from your posted link I'm stuck on icon Xiaomi and the device doesn't get into recovery. It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data.
Only when I flash TWRP 3.1.1.0 from here I manage to get into the Recovery, the problem then I get eror 7 when I try to flash Lineageos 17.
It must be noted that before that I used Lineageos 13 and already did wipe system & Chache & Dalvic & Data. So now I am without an operating system, only recovery.
Click to expand...
Click to collapse
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!
WJXXBSH said:
It seems you are using the old bootloader of Android 5.x, but it doesn't support new ROMs after all. To upgrade to the new bootloader, you must have access to officially unlock your device, then flash the latest MIUI and boot one time (it will make sure you could unlock your bootloader).
Use the unlock tool here (official solution): https://www.miui.com/unlock/index.html
If you have other ways to unlock the new bootloader without the official method, it's also right. It may take you some time to get the official permission (from Xiaomi) to unlock the device, good luck!
Click to expand...
Click to collapse
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?
elna.nitz said:
Thanks a lot, how do I flash latest MIUI? From TWRP?
Where do I download the latest MIUI file?
Click to expand...
Click to collapse
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?
elna.nitz said:
I can get permission to open the device only after connecting to my MI account through the device when installed on it official miui.
Therefore I seem to have previously had flash latest MIUI then log in to MI account and submit a request to open bootloader. Am I right?
Click to expand...
Click to collapse
Yes, if you want to unlock your device. A Mi account is needed to do this, on the latest MIUI version (if stable version "10.1.1.0" doesn't work, the develop version of MIUI is needed).
WJXXBSH said:
To flash the latest MIUI, this official document may help you: https://www.miui.com/shuaji-393.html
If you don't want to flash MIUI, but have the permission to unlock your device (IMPORTANT!), just flash the latest firmware and the new TWRP, then reboot to fastboot and unlock your phone.
If anything went wrong during the second way, your phone will be not able to boot unless flashing MIUI. If you just failed to unlock your device, but flash the new firmware and TWRP successfully before reboot, you will still have chance to boot into the recovery and flash the new rom with "locked bootloader".
Click to expand...
Click to collapse
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?
elna.nitz said:
Ok
I flashed latest firmware and TWRP 3.3.0, then Unlock bootloader with Mi Unlock.
Then flashed Lineageos 17 successfully.
The problem is that when I try to flash Gapps pico I get eror 70...
I tried to search for the font folder in the system path in TWRP File explorer and I couldn't find it (System Folder is empty) .
I tried reboot to system anyway, and after a long boot with the logo of the Lineageos 17, device initializing itself back to Recovery.
What else can we do?
Click to expand...
Click to collapse
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).
WJXXBSH said:
The latest version of lineage-17.0 could boot properly (tested my self). However, you flash the GAPPs and got interrupted halfway, which may cause some strange issues.
To fix this, format "/system" and flash the rom again. After that, mount "/system" manully in TWRP, then you could modify "/system" with the TWRP file manager.
There is another way to solve the GAPPs problem: If you're using magisk, try some modules that could install GAPPs without modifying "/system" (eg. "Weeb GAPPs"). Android 10 takes more free space in "/system" than Android 9 at present, even if without the fonts, it still has possibility that makes the GAPPs installation failed (this way works in lineage-16.0, which has 2.5× free space than 17.0).
Click to expand...
Click to collapse
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?
elna.nitz said:
Ok, I deleted the Notosansjfk.ttc from fonts & android viwe system app, And now I am able to flash Gaaps pico and boot to system.
But when I run the system and try to get to the System User Interface Launcher course, you can't use your device. Probably happened because I deleted the font or the Android view system..
Any solutions?
Click to expand...
Click to collapse
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "◻".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download
WJXXBSH said:
You deleted the "Android System Webview" without installing a new one? That's not a good news after all, because every APP that contains webview will crash. The CJK font will not cause any serious problems, just make some words a "".
As a solution, if you could use Play Store, just install "Android System Webview" from there. Otherwise, you could still install one through ADB.
Download the webview app here (if Play Store not working): https://www.apkmirror.com/apk/googl...em-webview-78-0-3904-108-android-apk-download
Click to expand...
Click to collapse
Finally I installed Weeb Gapps magisk Moudle, and The majority are fine.
There are 2 problems:
1. The device feels very lag in the opening of the apps and in the transition between them.
2. After restart takes the device nearly 2 minutes to find a cellular network