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.
Related
No matter what I tried via kernel modules (mmcfix), I was not able to fix the issues with writing to certain sdcards under 2.6.29 kernel (of our 'vulnerable' recovery that we use to start OpenRecovery).
So I decided to give a try to 2ndboot from 2.6.29 to 2.6.32 kernel under recovery.
Here is a version of OpenRecovery 1.46 that runs under custom 2.6.32 kernel using 2ndboot:
Download: http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_2.zip
Fixes:
- all issues with writing to some sdcards under recovery ("DMA transaction error with device 61" in dmesg)
- missing huge_file feature of ext4 filesystem under recovery
New features:
- battery charging under recovery
Please let me know if you encounter any problems.
The start of OpenRecovery with 2ndboot takes a bit longer, so be patient.
You can see a phone reboot during the start of OR under certain conditions - it's intentional, just wait, the OR will start automatically afterwards.
Kernel source: https://github.com/nadlabak/kernel/tree/recovery
UPDATE 30.01.2013
- prevent watchdog reboot (by automatic reboot of recovery if it was not started via /cache/recovery/command)
- use 10% battd for better compatibility with 3rd party batteries
- modversion set to 2ndbootOR v1.2
UPDATE 03.11.2012
- kernel and 2ndboot files updated (2.6.32.60, L2 cache enabled etc.)
- patches by justcsdr from issue #773 included (power off, mass storage with complete access to all sdcard partitions etc.)
- modversion set to 2ndbootOR v1.1
UPDATE 26.09.2012 (2)
- fixed linker issues - IMPORTANT! please update from the previous version
- modversion set to 2ndbootOR v1.0
UPDATE 26.09.2012
- battery charging and status display added
UPDATE 23.09.2012
- workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
UPDATE 21.09.2012:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Seems to be working for me. No issues
Sorry for the dumb question, but what is the purpose of this OR?
Erovia said:
Sorry for the dumb question, but what is the purpose of this OR?
Click to expand...
Click to collapse
Read the first post...
LuigiC6 said:
Read the first post...
Click to expand...
Click to collapse
Oh god, i really should go to sleep..
By the way, i tried it, works fine, no issues so far. :good:
Works great, slowest but for me without issues
Now my nandroid backups are not hanging on system dump anymore. Great work man. Thanks a lot.
Update:
- fixed backup of logo, bpsw, lbl and devtree partitions
- added 2ndboot splash screen
Download: http://d-h.st/AeS
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Just a suggestion/question - can't you change version numbers so not to confuse new 1.46 with old 1.46?
DJPatriX said:
Kabaldan I have one question.
Is there possibility to run rom on this second kernel? Maybe this is the way to make kernel more complatible for rom
Click to expand...
Click to collapse
DJ,
As far as I understand, Rom already runs on this "second" kernel. This second kernel is the Motorola Froyo Kernel, recovery was using an older kernel to boot. Both are signed by motorola, so, it is not a custom kernel.
It actually is a custom kernel (2.6.32.59), not signed by Motorola (the last kernel released by Motorola for Milestone is 2.6.32.9 from early 2011).
Check 'cat /proc/version' and see when it was compiled .
You could even use swap with this kernel, if it would make sense under recovery .
But you're right that it's not the main point - this OR release is about recovery to be run under 2.6.32 kernel to achieve reliability in sdcard operations, which was not possible under 2.6.29 kernel of our old recovery.
The problem with 2ndboot (or kexec) method to run custom kernel is that there is no known way to get the Wrigley 3G BP working afterwards (BP = Baseband Processor - the gsm/umts phone features).
This is fine under recovery as the phone functionality is not needed there.
But there's no known way to run a custom kernel on Milestone (or any other Wrigley 3G BP phone such as Defy(+), Milestone 2 etc.) while the device would still be able to function as a phone.
Thanks for the update. Seems to be working fine. Console, nandroid backup/delete (haven't tried restoring yet), scripts...
Btw., indeed very nice 2nd boot splash image
Thank you
Thank you for this update, everything is working just fine!
the dl-link does not work for me. could you reupload it, please?
As dev-host seems to be off-line, I've uploaded new update to issue-tracker site
http://code.google.com/p/cyanogenmo...nRecovery_v1_46_SHOLS_2ndboot_2_6_32_kern.zip
UPDATE 23.09.2012
- added workaround for occasionally non-working adb
- clean kernel build (no change in functionality)
Thanks for the reply. I've seen some issues with radio an other roms who runs on "second kernel". Now everything is clear 4 me.
Cheers
battery charging under recovery added
Link
That is amazing... Thank you.
Btw., you might have forgotten a link http://code.google.com/p/cyanogenmo...1_46_SHOLS_2ndboot_2_6_32_Charge.zip&can=2&q=
New version uploaded:
http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=OpenRecovery_2ndbootOR_v1_0.zip
It contains important fix for a nasty bug introduced with the addition of battery charge support. Please update.
#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
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.3 or higher is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
Official: https://download.lineageos.org/oneplus3
Last unofficial: https://androidfilehost.com/?fid=1395089523397903569
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Beta
Created 2018-11-13
Last Updated 2019-08-12
Reserved
Changelog:
2018.11.13:
Initial release
2018.11.17:
Sync latest source
Fixed directly reboot to recovery when attempting to enter power on password when secure boot enabled
Downgraded kernel to LA.UM.7.5.r1-02500-8x96.0 due to CAF stability regression, but there's still a race condition which could cause random kernel panic, especially when attempting to wake up the device, I'm still debugging on this.
Improved GPS performance
Minor bug fixes
2018.11.29:
Sync latest source
Kernel baseline updated to LA.UM.7.6.r1-03600-89xx.0
Thanks to a clue provided by @markakash , the "random kernel panic on wake up" issue seems to be fixed now. The ROM is probably stable enough for daily use, so I call it "beta" instead of "alpha" now. Please report if you still have the issue.
Minor bug fixes
2018.12.02:
Sync latest source
IMS experiments, VoLTE is confirmed working, VoWiFi is untested
Battery life optimization
Fix fingerprint sensor not respond on first boot and after user switched
Minor bug fixes
2018.12.05:
Sync latest source
SELinux enforcing for now, let me know if there're any regressions
Minor bug fixes
2018.12.15:
Sync latest source
Fix some suspend issue
Kernel baseline updated to LA.UM.7.5.r1-03700-8x96.0
Minor bug fixes
2018.12.22:
Sync latest source
Slider key fix by @nvertigo67
App launch boost & touch boost, hope it helps reduce lagging
2018.12.30:
Sync latest source
Kernel baseline updated to LA.UM.7.5.r1-04000-8x96.0
WiFi display support
Bug fixes & improvements
2019.1.1:
Sync latest source
Various bugs in the last build have been addressed
Working unofficial SU addon: https://androidfilehost.com/?fid=11410963190603887268
Happy New Year & Enjoy!
2019.1.12:
Sync latest source
Add support for always-on-display
Minor bug fixes
2019.1.24:
Sync latest source
Fix touchscreen when gesture disabled
Fix whatsapp and CamScanner camera issue? Not sure, need feedback
Minor bug fixes
2019.2.10:
Sync latest source
Update kernel to LA.UM.7.5.r1-04100-8x96.0
Livedisplay & touchscreen gestures internal API migration
Allow disabling new USB gadgets when the device is locked
Minor bug fixes
2019.3.1:
Sync latest source
Fix weird color after boot? Need your confirmation
Performance optimizations
New offmode charging animation
Minor bug fixes
Note that some features/bugfixes will NOT be included in the upcoming official builds, be aware before switching from unofficial to official.
Future:
https://download.lineageos.org/oneplus3/changes/
Your opinion on migrating to official Pie firmware
dianlujitao said:
As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I didn't see my launcher desktop as usual, but an "Decryption unsuccessful" warning telling me that my data was corrupted. Undoubtedly, after rebooting to TWRP it failed to mount /data thus I lost everything on my internal storage.
After several experiments I finally figured out the cause:
If your data is encrypted and bootloader is unlocked, after upgrading to Pie modem firmware, there's 100% chance of your data to become corrupted, and probably no way to restore them. The cause is on firmware side, probably something wrong with key migration, so there's no way for 3rd party developers to fix it. Note that which ROM was in use pre-upgrade doesn't matter at all, i.e., if bootloader was unlocked and you were upgrading from OOS 5.0.8(enforce encryption by default) to OOS 9.0, you'll lose all personal data after reboot from recovery installation. Interestingly, everything works as expected if bootloader was locked.
I couldn't comprehend why do they apply diverse low-level strategies to locked and unlocked bootloader. Arguably this is a bug and should be fixed when they started rolling OTA updates to the public, but it's also possible that this is by design and aims to restrict "unsafe" operations. Regardless, always be careful and backup your data before upgrading firmware in the near future.
Click to expand...
Click to collapse
Unfortunately they still didn't fix the issue in the OxygenOS 9.0 Community Beta released hours ago, in contract their PR claimed "SW team is aware of this issue" during the early closed beta stage. Given the fact the issue persists in both public H2OS and OOS build, I highly doubt if they're actively working on fixing the issue or they'd even gaf. Ofc it's still possible but very unlikely for them to fix it in future builds.
Now I'd like to know your opinion on migrating to Pie firmware. Device owners with encrypted data and unlocked bootloader MUST either backup data or relock bootloader before installing new firmware, others are not affected. Please vote.
Nice
Is it possible to update with a wipe system only ?
good
whats the difference in this build and does this uses 4.4 kernel ?
Playa82 said:
Finally
Is it possible to update with a wipe system only ?
Click to expand...
Click to collapse
Why this question is asked each time ?
You have TWRP right ? So backup your current install, flash without wiping, if it goes wrong, you know you have to clean flash, simple.
Plus, from the O.P of this thread:
O.P said:
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Click to expand...
Click to collapse
lol, right when I clean flashed 15.1 and reinstalled everything from too many dirty flashes
karkiankit said:
does this uses 4.4 kernel ?
Click to expand...
Click to collapse
Why don't you check yourself? OP clearly states which kernel is in use:
https://github.com/dianlujitao/android_kernel_oneplus_msm8996/blob/lineage-16.0/Makefile#L1-L3
Nice!.. op3 community love u
Thank you
Weeew the legend is back. Awesome job
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
ele95 said:
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
Click to expand...
Click to collapse
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Screenshots pls... Anyone??
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
IIRC, we need OnePlus sources from Android Pie for encryption to work correctly.
pjgowtham said:
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Click to expand...
Click to collapse
dirty flash works and bootup fine for me but there is no sim signal so i revert to old one
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
The same happened to me also. I'm encrypted on f2fs coming from OOS with a clean install.
@dianlujitao could you please add in the OP that it needs to be installed on an unencrypted phone - assuming that the reboot to recovery is caused by booting on an encrypted device.
Sent from my OnePlus3T using XDA Labs
Sometimes when I try to unlock using the fingerprint reader the screen stays black, while the buttons light up. The phone freezes and I need to reboot it. Someone else experienced the same issue?
Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
you knew that going in this, so why write and be supprised?