Related
https://github.com/StarKissed/starkissed-kernel-ekgc100
This repository will include the kernel source from the "Update 1" version of the kernel.
The compile instructions included with the source do not cover making any modifications to the kernel and the previous thread seems to mirror those instructions, so this one will be dedicated to creating custom kernels.
The buildKernel.sh script is fairly straight forward to demonstrate the process, but the config files have a few eccentricities when building the wifi. When loading the config during the build, there are prompts for the bcmdhd parameters that are not referenced anywhere, as the system image does not include any bcmdhd firmware files.
The repository includes a generic ramdisk, as none is provided. Odin flashes the boot.img as a compiled file, so the ramdisk cannot be merged during install like most phones do to maintain the current version. A key note to this is that modules are built into the boot.img ramdisk, which is confusing not coming from any device that does not require Odin.
Edit: The last comment on ramdisk flashing during the install may soon be resolved. There are compatible tools to pack a ramdisk made for the recovery platforms, allowing those items to be included in a zip with the kernel. All that is needed is a custom recovery and that is in the works.
#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 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
Make sure you have a second partition on your SD card formatted to ext4 before flashing!!!! This can be created with either CWM recovery or with TWRP. gparted on Linux should also work. If you "SD card not supported" try repartitionning. If you get "Encryption unsuccesful" then you need to format the second partition as ext4 (or f2fs, your choice).
If on a BML rom (stock-based GB)...
1. Reboot to recovery
2. Make sure your version of CWM is at least 5.x
3. Install zip. 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 SuperSU whenever
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
4. If you want root or Gapps, install them now.
The first boot can take several minutes. Be patient. If it takes 10+ 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.
Bluetooth only enables from the notification pulldown, not when you go directly to settings. It does work just fine afterwards though
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 omni source code. This means that the recovery is TWRP and there aren't any added "features"
In order to get it rooted, you need to install SuperSu.
Gapps eat up about an extra 30MB of RAM so they slow down the device - tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Video Recording
Automatic Brightness
Encryption
Compass
GPS
Headset Buttons
Semi-Working
Powered-off charging animation - works at first, but then stops working. Seems to be an Omni problem, but it still charges...
What doesn't
SElinux is currently in permissive mode. Will not be going to enforcing, this would require a data wipe as well
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
Unofficial Omnirom 6.0 for Galaxy S 4G, ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99
Source Code: https://github.com/omnirom
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: OmniRom
Version Information
Status: Beta
Created 2016-01-11
Last Updated 2016-05-12
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 the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-6.0 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree (create the local_manifests folder if necessary).
After syncing the source, open a terminal and in the directory where you downloaded the source code type "./device/samsung/aries-common/patches/apply_patches.sh" to apply the patches necessary to have a working build. Then run "source ./build/envsetup.sh" and then "brunch galaxys4gmtd". For future builds, only the envsetup and the brunch parts are necessary. Please note that you will have to re-run the apply_patches.sh script after each time that you run repo sync. (Note: the patch script no longer runs automatically)
You should be able to use my trees for other first-gen galaxy S devices. You will need to apply a patch similar to https://github.com/xc-racer99/andro...mmit/fe6bc6b82881a12fc4a5647812f3cf0f52f79c6a to your device tree (if coming from Omni 5.1). I haven't done anything to P1 trees and may have broken the kernel for it...
Changelog
2015-12-20
Initial pre-release - many bugs
2015-12-26
Second pre-release - fewer bugs, but still plenty
2016-01-07
Initial actual release. Quite stable with minimal bugs
2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
Added T959P build
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
Added download mirror thanks to @FBis251
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Changelog for 2016-02-29
Updated Omni source - plenty of new features
Low-resource spinner from LegacyXperia (means that the loading spinner isn't the only thing using the CPU)
Miscellaneous performance tweaks (see github if interested)
md5sum for T959V: a7aa8cca3259208eafba7c2cccecdbfd
md5sum for T959P: 879256c93a0e58de0fb9c9e1be91e0e9
Changelog for 2016-04-02
Security fixes in the kernel
Freed roughly ~4MB of RAM in kernel
Updated android drivers resulting in better multitasking
OpenDelta updating system removed as we weren't using it (it used ~3MB of RAM)
Recents menu now has less lag when opened
Selinux contexts have changed. It could likely be put to enforcing now but this would require a complete data wipe so its still permissive
Live Wallpapers removed - we're low-ram
Bootanimation now fits the screen better
PowerHAL removed - it was broken and has been for a while...
Misc other changes - if you didn't notice problems, you won't notice the solutions
Known bug - Camera on T959V is broken...
md5sum for T959V: 247a721f4c27c5191a2a460e4c72ba3b
md5sum for T959P: d15339d8aa10f765155bdd8d1bb0c5f5
Changelog for 2016-04-08
Fixed camera on T959V
Security patch level of April 2, 2016 (latest to date)
Headset buttons fixed
T959V md5sum: 2b1560b99402c73275d1f69b3ceb9a22
T959P md5sum: e102cce0d624383fb85a32321c98c645
Changelog for 2016-05-09
Uses CMA kernel by default
Performance Control can now modify voltages
Systemless SuperSU is now supported
WebM playback is now working
EFS backup in TWRP now works
Data on boot should now work - no need to toggle airplane mode anymore
md5sum for T959P - 118789dd68760d9fd18cc961398bf346
md5sum for T959V - f9375a8d9792c3a0d222c113213c014d
Changelog for 2016-06-07
Security patch level of June 1, 2016
Microphone mute now works when in call
Battery now charges to 100% and should read properly after a system crash
Standby times should be improved
Slightly less RAM - but should result in better graphics performance
CMA crashes fixed (at least, I haven't crashed once since I started testing the patch a week or so ago)
PowerHAL is back - CPU is boosted when turning screen on to avoid delay
md5sum for the T959P: eeed77fb84189e84f2264e32d18ce454
md5sum for the T959V: b6457319d248029429183c342514b072
Changelog for 2016-08-02
First unified build (ie it works on both the T959P and T959V)
Screen recording now works in portrait mode
MMS should be able to be sent when data is disabled (will still use data though)
Default Camera app portrait photos are no longer square
SuperSU systemless updated to 2.76
Slightly less audio latency with UI sounds (and some sounds have changed)
Data should also be working on boot
Slight changes to battery and graphics config
Security patch level of August 5, 2016 (I'm a time traveller...)
md5sum: df587e0bd69552e0ece4b4ba3e214f45
Source, Downloads, Misc Notes
Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_telusgalaxys4gmtd for the device tree (see android-6.0-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-6.0 branch). The patches folder holds all the necessary patches along with a script to apply the patches.
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-6.0 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-6.0 branch)
Downloads!
All builds are found at https://drive.google.com/folderview?id=0B7vXjzo0Hj-iOGJ4dmdCd09OZmM&usp=sharing. As well, recent builds are mirrored on https://files.fernandob.com/#xc-racer99/Omni6.0
Gapps
Gapps cause the first boot to be very, very laggy. Things do improve after that. The best way to get through the Setup Wizard (IMO) is to skip everything possible (ie connecting to Wifi, settings up a Google Account, etc) and then reboot. You can manually add a Google Account later in Settings. While any (small) Marshmallow gapps should work, I have had success with OpenGapps pico package from www.opengapps.org (untested on recent builds).
SuperSu
SuperSu can be found at http://forum.xda-developers.com/apps/supersu. If on May 2016+ builds, systemless 2.71 works (other systemless versions may work, untested). If you're on an older build, you need to either force system mode (create a file in /system or /data called .supersu with the contents "SYSTEMLESS=false") or use an older version (ie version 2.52 or earlier). August 2016 build updates the systemless to 2.76.
Woooow thanks
As you suggested, Gapps caused lots of problems...made the ROM very slow and laggy, lots of FC's, lots of random reboots, etc. I re-flashed without Gapps. Was able to restore apps with TB and root with SuperSu. The basics...calling, browsing, messaging, camera...are working fine. Haven't taken it for a ride yet, but GPS test picked up 5 satellites and I haven't even taken it outside yet. If I desperately need another app, I guess I can find the .apk somewhere. Since I did a TWRP backup, maybe next week I'll try the pico gapps again and see what happens. At any rate, wonderful work.
Update: Took it out for a spin this afternoon....GPS works fine.
Been running the 1/7 for a few days. loving it so far
New Build Uploaded!
Alright, I've uploaded a new build
Changelog for 2016-01-23
Updated Omni Source code
Fixed Google Play (and other apps) download error (I think...)
New bootanimation - Its the new Omni one - it doesn't fit on our screen the best but it doesn't have one section lit up all the time so the screen doesn't burn in like the old one
Freed a bit more RAM
Improved zRAM performance by using LZ4 instead of LZO
I've also uploaded a T959P build as I had a request for one. Let me know if you guys find any more bugs.
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
DickyG said:
New build flashed fine although I had to re-flash the SuperSU zip...no problem since I already had it on my SD card. I'll let it rest up for a day or two and then I'll try to flash the pico-gapps and see if it
will run smoothly....good job.
Click to expand...
Click to collapse
Sounds good. Do note that when/if you flash gapps, you will need to do a complete data wipe first, otherwise you will get force-closes like crazy.
I've always just reflashed SuperSU manually and never relied on the script to restore it so I can't help you there.
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
SuccubusInc said:
Tried to install over MTD SlimSaber with TWRP 2.7.0.0, kept getting Status: 7 error with updater.sh script.
Any way to fix this?
Thanks in advance.
Click to expand...
Click to collapse
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
xc-racer99 said:
Hmm, going back to to stock with a OneClick/Heimdall/Odin will work for sure.
Alternatively, check if there is an omni.cfg file on your SD card. If there is, delete it and try again. Also, if you can get me the exact wording of the error output that would be great, along with the omni_mtd.log file from the SDcard.
Click to expand...
Click to collapse
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Installing '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
assert failed: run_program("/tmp/updater.sh") = = 0
E:Error executing updater binary in zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Error flashing zip '/sdcard/omni-6.0.1-20160123_galaxys4gmtd-HOMEMADE.zip'
Updating partition details...
Click to expand...
Click to collapse
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
SuccubusInc said:
I will Heimdall One-Click back to KJ6 and reflash the ROM after checking for the omni.cfg, and will quote the output and the log if I get another error.
I'll be back by 5:00pm PST. I have school to take care of.
UPDATE:
Tried again after a full wipe [not a restore to stock] and got this:
Is there any kernel/recovery you recommend for flashing after restoring to stock?
I've tried before on AntonX Voodoo Lagfix recovery and got a similar error.
Click to expand...
Click to collapse
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
I'll try out Blastoff if I can find it. But it probably failed because I did not partition my sdcard. I'll see if that helps later.
Thanks a lot.
xc-racer99 said:
I typically used the Blastoff kernel, but I have my own one-click as I have a Canadian variant.
Also, the omni_mtd.log will tell which part of the updater.sh failed. Another thing to check is if you have a second partition on your SD card. This ROM requires one as /data is put there.
Click to expand...
Click to collapse
Hey, xc-racer99, after about four assorted blind attempts at installing your work, I flashed back to stock/AntonX kernel with Heimdall and full wiped, then used CWM to create a 4GB partition on my sdcard. The ROM installed through CWM, then TWRP without an error and booted up after fifteen minutes or so of OMNI animation, and is running on my SGS4G without any issues. The only noticeable lag was for the first five minutes after the initial boot. Now my device is gliding smoothly after a few tweaks in the performance settings and turning off background processes. Thank you so very much.
Next time, I'll read the entire post before blundering through the install process with the assumption that I know what I'm doing [as usual].
Sorry for the trouble, if indeed I was any.
xc-racer99 said:
Alright, I've uploaded a new build
Changelog for 2016-01-23
...
Fixed Google Play (and other apps) download error (I think...)
...
Click to expand...
Click to collapse
I tried Pico gapps and the store works perfectly for me now. Thanks!
New Build Uploaded!
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Wooow...thanks
xc-racer99 said:
Changelog for 2016-02-04
Updated Omni source code - includes Feb security patches thanks to the Omni Team
Brought kernel defconfigs inline with upstream kernel/common (well, as close as possible without breaking things
More work on selinux - but its still in permissive mode
md5sum for the T959V - 975730824b335d9521d1201d4dac82b7
md5sum for the T959P - b209b78d3bc5dd4c5f5a7224a9d780c4
Still the same bugs present - headset buttons broken (have been on all 3.0 kernel-based ROMs for the Galaxy S 4G), laggy 720p recording, broken webM playback, microphone mute in calls, and bluetooth tethering.
Download link is the same as it always is. Also, thanks to @FBis251, we now have a mirror. It is located at https://files.fernandob.com/#xc-racer99//Omni6.0
Click to expand...
Click to collapse
Finally got pico gapps to run...the initial setup took quite a while but now that it's settled in, no problems. It's also interesting to note that Link2SD is running fine while it seems to be a major problem for other Lollipop & Marshmallow ROM's on other devices.
Hello,
Recently I downloaded the LineageOS 14.1 source code. I made some changes using IntelliJ but I find it a little cumbersome to test the source I wrote due to the following reasons:
1. I must always build the rom (building time around 20-25 minutes).
2. I have to reboot into recovery to flash the new rom
Is there any easier way to partially build the modified source and flash the changes to the device without rebooting?