Related
Hi all,
This is a thread in which will try to keep track of "unofficial" changelogs. From my point of view Huawei does a really poor job at doing changelogs and some features or changes don't end up in the official list.
Disclaimer:
- Device: EML-L29 C432
- Initial software 8.1.0.106
- Carrier: Orange Romania
- All updates will be received via official OTA or full package from HiCare and I'll try to make my best in finding new stuff.
Changelogs
Update 9.1.0.311 changes - 17th August 2019
QR Code scan now works while offline (from lockscreen, really helpful when you want to scan a wifi share QR so you won't need to input the password again)
Small updates to Camera UI
Phone Manager app renamed to Optimizer
EROFS, GPU Turbo and other Huawei stuff (I could not find updates in Settings UI though)
July Security patches
To be continued
Update 9.0.0.280 changes - 1st June 2019
-May security patches
- To be tested
Update 9.0.0.270 changes - 2nd May 2019
-April security patches
- Minor fixes in the task switcher views
- Auto-brightness seems to favour brighter settings now
- To be tested
Update 9.0.0.236 changes - 2nd April 2019
-March security patches
- Battery improvements
- To be tested
Update 9.0.0.203 changes - 4th March 2019
-February security patches
-
- To be tested
Update 9.0.0.197 changes - 1st February 2019
- Recent apps navigation when using off-screen nav is fixed (no more problems with opening the apps one the sides of the navigation vertical list)
-January security patches
-
- To be tested
Update 9.0.0.160 changes - 18th December 2018
- EMUI 9: first public build
Update 8.1.0.152 changes - 14th August 2018
- GPU Turbo
- To test more
Update 8.1.0.132 changes - 13th July 2018
- Super Slow motion is improved with movement detection.
- Camera version 8.1.0.300...Huawei programmers either don't know how to version releases or there's no new code
- AAC bluetooth codec fixed!
- To test more
Update 8.1.0.128 changes - 6th June 2018
- Camera version 8.1.0.300
- New settings for notch: auto/on/off for individual apps
- New on-screen navigation similar to Android P
- Some info about "Digital Headset" firmware version inside sound settings. Not sure if this was present before.
- Expanding notifications si NOT fixed unfortunately...
Update 8.1.120 changes:
- Touchscreen sensibility is improved
- we have a new functionality called HiTouch which integrates Amazon assistant both in camera and in general menu. You can find it under Smart Assistance menu
Update 8.1.0.110 changes
- Camera interface is improved, modes are now more easy to access. It also has a strange leather like texture.
- Expanding notifications on lockscreen have been broken
The new camera UI
LE: Checked Google maps and it seems improved, still not perfect but the search and drop pin functionalities are now usable ( still have some lag but at least they work... Before this the app just froze )
Same C432 here,. 106 and no update shown. Switzerland.
Did you get it OTA?
bolof2 said:
Same C432 here,. 106 and no update shown. Switzerland.
Did you get it OTA?
Click to expand...
Click to collapse
Yes, OTA this morning/noon. Will probably roll-out to all in the following weeks
Update 8.1.0.128 changes
- New settings for notch: auto/on/off for individual apps
- New on-screen navigation similar to Android P
- Some info about "Digital Headset" firmware version inside sound settings. Not sure if this was present before.
- Expanding notifications si NOT fixed unfortunately...
paul678 said:
Update 8.1.0.128 changes
- Some info about "Digital Headset" firmware version inside sound settings. Not sure if this was present before.
Click to expand...
Click to collapse
Looks the same in .120
New firmware 8.1.0.130.
Changelog in screenshot.
bioan said:
New firmware 8.1.0.130.
Changelog in screenshot.
Click to expand...
Click to collapse
which model?
EML-L29C33 - Huawei P20 dual SIM 128 gb.
bioan said:
New firmware 8.1.0.130.
Changelog in screenshot.
Click to expand...
Click to collapse
Seems to be same as .128 for c432 version. Still waiting for the next OTA, from what I've seen on p20 pro forums it will include camera improvements ( including slowmo and ui updates)
new firmware showed up on firmware finder for c432. but still not approved to install.
Does anybody on 8.1.0.120(c782) receive qby updates? I have security updates from 1 april.
drmxmyt said:
new firmware showed up on firmware finder for c432. but still not approved to install.
Click to expand...
Click to collapse
What do you mean by "not aprovved to install"?
I've got an EML-L09 and on the update menu it appears that the 8.1.0.130 version is ready for being downloaded and installed. I download it but it doesn't install.
By the way, my phone is rooted.
New update available via OTA in Romania yesterday
Update 8.1.0.132 changes
- Super Slow motion is improved with movement detection.
- Camera version 8.1.0.300...Huawei programmers either don't know how to version releseas or there's no new code
- Apperture mode defaults to 2x zoom (it was 1x in the past)
- To test more
I'm on vacation so don't have so much time to check things out
Some guys on google+ group received 132 update for their UK C782 phones but i haven't yet. Still waiting
In Poland we have too in ORANGE 8.1.0.132 (c432)
security from 1 june 2018
New update in my L09
I can confirm AAC Bluetooth codec is now working. For those of us with aac Bluetooth headphones this was really important as it fixes many quality and signal strength issues!
paul678 said:
I can confirm AAC Bluetooth codec is now working. For those of us with aac Bluetooth headphones this was really important as it fixes many quality and signal strength issues!
Click to expand...
Click to collapse
Thats gr8. My Bose qc35 propably will sound better.
Does the Google Pay skan Gift cards bar codes properly?
Im still waiting for update c782
g_oral said:
Thats gr8. My Bose qc35 propably will sound better.
Does the Google Pay skan Gift cards bar codes properly?
Im still waiting for update c782
Click to expand...
Click to collapse
Not sure how cand I test the gift card without a gift card hehe
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
-
Links
18. 20210419: april security patch: https://drive.google.com/file/d/1ngw-Ac6JN16L5ZF5NfiVOzgFhrSnO-GZ/view?usp=sharing
17. 20201220: december security patch: https://drive.google.com/file/d/1sSJTq3EmkrF4e-JFgCHNHrN2ArxZn7vO/view?usp=sharing
16. 20200815: august security patch: https://drive.google.com/file/d/1CLna2ZCjwn6excJ48zEORQRs6KEYfwPS/view?usp=sharing
15. 20200724: july security patch: https://drive.google.com/file/d/1nfyXJKb_X4bspfzCEP1PU8TDbvg8CDZf/view?usp=sharing
14. 20200614: june security patch: https://drive.google.com/file/d/1OytkLQnOP_KMzsD52STQWG5QAd-zz_Y4/view?usp=sharing
13. 20200523: may security patch: https://drive.google.com/file/d/1-fNVsac004wNSMspGgJlJaOwFj51MAnV/view?usp=sharing
12. 20200411: april security patch, kernel update: https://drive.google.com/file/d/1yjI9j4dZmOY34AwdGNKv24hcaBg6ObPN/view?usp=sharing
11. 20200212: latest sources, February security patch: https://drive.google.com/file/d/1g4jjvW6u1hiJy2m81QKmyZ-gc1rmeTgB/view?usp=sharing
10. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1oxURZhtzFKu7MlI7VD1QQKwjavVJtBUJ/view?usp=sharing
9. 20191224: https://drive.google.com/file/d/1W0mQdKscN4qiaa6q3uUliTry5n6anPgz/view?usp=sharing
8. 20191215: fix internal speaker, bt calls: https://drive.google.com/file/d/1fXg0qVz7oARO9EkNZ04x8ZIsFejWfcDc/view?usp=sharing
7. 20191210: mobile data: https://drive.google.com/file/d/1fHycuBYogxuQOJuHG_pXHZdh0DnloPPc/view?usp=sharing
6. 20191116: november security patch: https://drive.google.com/file/d/1eexCgGG-vj0c6mEOboP56b4YzeK9WxOl/view?usp=sharing
5. 20191114: https://drive.google.com/file/d/1OuyEPQRMyxikHGjwHSke34cLintfOPnH/view?usp=sharing
4. 20191027: latest code, small cleanup, disable Codec2.0 components (long delay on start youtube) (thanks @followmsi): https://drive.google.com/file/d/1QYe1yi-q_pioLKVaR7EzdS7cqYnPjbs7/view?usp=sharing
3. 20191013: https://drive.google.com/file/d/1Q7DTLmy1HR7H_HJvEvWXyntpGUXpJXOD/view?usp=sharing
2. 20191007: https://drive.google.com/file/d/18SICwdnJqDJpytbCw0z3DgqBPf9_kXCU/view?usp=sharing
1. 20191006: https://drive.google.com/file/d/1NulGtfJV8Zq5F0JUPYwKW8d-AhhhOrLn/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM
Android: 10.0
Root
Install latest magisk (20.1+) from canary channel: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/lineageos
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to LineageOS team
I'm glad to run a new version of android for note pro 12.2.
Of course we are still at the beginning, the system is at an early stage, there are not even official gapps.
But already a lot of stuff work.
It's great to see that it goes with Lineage 17 for the P905. Thanks a lot Valera1978
Valera1978 said:
I'm glad to run a new version of android for note pro 12.2.
Of course we are still at the beginning, the system is at an early stage, there are not even official gapps.
But already a lot of stuff work.
Click to expand...
Click to collapse
Thank you, Valera!
Really thank you Valera! I'm very happy to see this. I sue this tablet to take notes at university so I have to reporter that palm rejection doesn't work. I hope in the next builds. Keep up the good work and thank you again!
The issue mobil data means, it doesn't work at all?
Dirty install over LineageOS 16.0 did not work. Could boot, but no login possible.
Clean install did work. Got message "Your device has an internal fault. Please contact the manufacturer". But could acknowledge and login. Working using the GApps from the first link (BiTGApps).
Could not get Magisk (19.4) to work. Could flash but Magiskmanager shows not installed and no root.
mad0701 said:
The issue mobil data means, it doesn't work at all?
Click to expand...
Click to collapse
for now - no mobile data at all
pantau said:
Dirty install over LineageOS 16.0 did not work. Could boot, but no login possible.
Clean install did work. Got message "Your device has an internal fault. Please contact the manufacturer". But could acknowledge and login. Working using the GApps from the first link (BiTGApps).
Could not get Magisk (19.4) to work. Could flash but Magiskmanager shows not installed and no root.
Click to expand...
Click to collapse
Right now "Your device has an internal fault. Please contact the manufacturer" message present on all lineage 17 firmwaresю
Magisk workaround is ready, see first post.
Valera1978 said:
Right now "Your device has an internal fault. Please contact the manufacturer" message present on all lineage 17 firmwaresю
Magisk workaround is ready, see first post.
Click to expand...
Click to collapse
Magisk does work now. Thanks a lot!
Thanks so much Valera
Thanks so much Valera, you have been helping us keep our Note Pro alive.
The only point I see need for more attention would be with palm rejection, as this is essential for using s-pen.
Gratitude for your work Valera, God bless you.
Palm rejection fixed?
Does this version fix the palm rejection issue? The last version working I think was Lineage 14.0. I really would like to use the S-Pen again for note-taking.
mnemonic-de said:
Does this version fix the palm rejection issue? The last version working I think was Lineage 14.0. I really would like to use the S-Pen again for note-taking.
Click to expand...
Click to collapse
No one?
dannyt84 said:
No one?
Click to expand...
Click to collapse
You mean that you can lay your hand on the screen while writing with the pen ? I will try to test it once I get the rom working.
dannyt84 said:
No one?
Click to expand...
Click to collapse
No not working
Will this work for the P900 or is it only the P905? Since the only difference is a mobile radio (to my understanding) I don't see why I can't but I don't see it mentioned specifically so figured I'd ask.
Ist only for P905... Processor and other Hardware are different...
Did anyone get safetynet to pass with magisk 20 or canary channel ?
Although i can not enjoy the fruits of your labour cos i have the sm-p900 i was think maybe if its possible to change my motherboard from p900 to the p905 board. i found one on ebay. I have 4 of these tablets i have purchased over the years as i keep dropping them and crack the screen. If anyone knows more if swapping the boards will work please let us know as this could be another way of upgrading and using the big lovely screen with Android 10
Did anyone test if Edxposed is working? Which version? I tried with Beta YAHFA and Sandhook, but did not booting (automatically always Download Mode)...
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading posts 1, 2, and 3 before posting.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as 17.1 is a work in progress. It boots and seems to work fine on my SM-T560NU, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
I built a new image of SM-T560NU following the instructions at
https://wiki.lineageos.org/devices/gtelwifiue/build
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store (using gapps pico)
Known problems.
1. stock camera
Stock LineageOS camera app back camera does not display properly. It is split into 8 frames. Use opencamera apk from
https://f-droid.org/en/packages/net.sourceforge.opencamera/
I will not be spending anytime trying to fix the stock camera problem. I never use it and opencamera works.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. text on home screen looks funny. This only seems to affect the home screen and nowhere else. Problem is with stock trebuchet launcher and/or its fonts. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/
Dec 14, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,200 files had to be recompiled).
Sept 16, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,000 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 5000 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 6000 files had to be recompiled).
May 9, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
Release notes for Feb 11, 2021
1. Feb 5 security patches.
2. Whatever LineageOS changed since last Jan 2021 update.
3. fixed audio over bluetooth. Problem was one variable pointing to the wrong audio directory which was changed in 17.1.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Whatever LineageOS changed since last Dec 2020 update.
Release notes for Dec 14, 2020
1. Dec 5 security patches
2. Changed some error messages to verbose to stop spamming log files
3. Whatever LineageOS changed since last Nov update
Release notes for Nov 7, 2020
1. Nov 5 security patches
Release notes for Oct 8, 2020
1. Oct 5 security patches
Release notes for Sept 15, 2020
1. Sept 5 security patches
2. added on screen nav buttons (you can change via settings)
Release notes for Aug 26, 2020
1. add fix for missing some play store apps (I have removed the Aug 20 build)
2. changed build fingerprint to a stock fingerprint
Release notes for Aug 20, 2020
1. initial release
2. initial testing, have no idea about long term stability
3. bug with hal hwbinder vibrator that causes tablet to be stuck at boot logo animation (have removed hal vibrator for now)
4. msm8916 kernel overclocked CPU to 1.6Ghz in kernel with 17.1 by default
5. incoporates aug 5 security patches
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) What TWRP should I use?
A1) Use 3.2.3 found at
https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue
Or use 3.5.2_9 that I built.
retiredtab - Browse /SM-T560NU/TWRP at SourceForge.net
sourceforge.net
Q2) Does the build work on xyz?
A2) I have no idea. I only have the SM-T560NU. It will not work on the SM-T561 and SM-T560 as it uses a different SoC (CPU).
Q3) Application xyz doesnt' work. Can you fix it?
A3) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q4) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A4) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q5) Do you plan to update the rom?
A5) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q6) Can you build this for the SM-T560?
A6) No, I don't have the SM-T560.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
I have attached the repo diff and roomservice.xml file that I have used. The repo diff are all the changes I have made to the "stock" msm8916 code.
Q9) Where can I download this rom?
A9) The 2020 builds are at
https://www.androidfilehost.com/?w=files&flid=315153
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds at
retiredtab - Browse /SM-T560NU/17.1 at SourceForge.net
sourceforge.net
Thanks for building this, downloading it now. Do you use opengapps or mindthegapps?
sillycat98 said:
Do you use opengapps or mindthegapps?
Click to expand...
Click to collapse
I tested opengapps pico and micro-g on the 16.0 build, but not on the 171. build.
retiredtab said:
Q5)This build is slow and buggy. Can you fix it? A5) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Click to expand...
Click to collapse
Isn't everything on this tablet slow and buggy? Even the stock rom was horrible for me. Think I might try mindthegapps when I get home. Any problems I'll swap over to opengapps.
sillycat98 said:
Isn't everything on this tablet slow and buggy? Even the stock rom was horrible for me. Think I might try mindthegapps when I get home. Any problems I'll swap over to opengapps.
Click to expand...
Click to collapse
This tablet isn't my daily driver so I have no reference if it's slow. I just got it and it happens to share some of the same code base as the SM-T350.
If this tablet is slow, it could be due to google services (gapps). You can always try microg. It's a way of running some Google services, but with a lighter set of software and some privacy.
https://microg.org/
I ran microg on this tablet with 16.0 and it seemed to work fine.
Runs great, the only problem I'm having is with one magisk module to spoof the props. It bootloops if I use it to change the fingerprint and I can't figure out why. Any ideas?
sillycat98 said:
Runs great, the only problem I'm having is with one magisk module to spoof the props. It bootloops if I use it to change the fingerprint and I can't figure out why. Any ideas?
Click to expand...
Click to collapse
I have only seen the need to change fingerprint to pass google's CTS. Is this what you are trying to do?
Does it bootloop with 16.0?
For boot loops, undo your changes.
Then unlock developer options, enable adb debugging and adb root. Then reboot tablet, re-enable your changes, reboot again and get a logcat while it's booting. It should show error messages in the logcat.
That's how I was able to figure out the vibrator hal causing a bootloop on the 560NU.
retiredtab said:
I have only seen the need to change fingerprint to pass google's CTS. Is this what you are trying to do?
Does it bootloop with 16.0?
Click to expand...
Click to collapse
It is what I was trying and it didn't with 16 but I can live without it, I'll just have to download what I want to my phone and extract the apks then transfer when over.
retiredtab said:
For boot loops, undo your changes.
Then unlock developer options, enable adb debugging and adb root. Then reboot tablet, re-enable your changes, reboot again and get a logcat while it's booting. It should show error messages in the logcat.
That's how I was able to figure out the vibrator hal causing a bootloop on the 560NU.
Click to expand...
Click to collapse
I'll try to get a logcat later.
sillycat98 said:
It is what I was trying and it didn't with 16 .
Click to expand...
Click to collapse
For 17.1, it's possible that a lineageos change in the future will fix the boot loop since 17.1 is still a work in progress.
Or what we did for the sm-t350, is we used a stock fingerprint and over rode the fingerprint to pass CTS. If I can get a stock SM-T560NU fingerprint, I can look at putting it into the 17.1 code. It's a single line of code in one of the mk files. It looks like this for the 350.
BUILD_FINGERPRINT=samsung/gt58wifixx/gt58wifi:7.1.1/NMF26X/T350XXU1CQJ1:user/release-keys
That spoofs play store into thinking its "certified" Samsung device.
Source:
https://github.com/Evervolv/android...mmit/5ad790d570e1c18e0706a7b2ce121e5c58ba79ba
BTW, if it works on 16.0, I plan to do monthly security patch builds for 16.0 as well, so you can stay on 16.0 if that makes life easier for you.
I'm likely to run 17.1 just to keep testing and again because 17.1 is a work in progress by the Lineageos team.
As I mentioned, this is NOT my daily driver tablet and I just got it and I wanted to run only microg and not use any gapps. As such, I didn't test gapps. Now that I loaded gapps and google plays store, I do see a problem. I will try to fix it over the next few days. I will update post #1 to reflect potential problems with google play store.
Google play store works in my 16.0 build. So if you need Google play store, use 16.0 for now.
For future builds, I will test goolge play store before releasing another build.
Looks like this is a known issue with the msm8916 team as per github (June 25th, 2020).
https://github.com/Galaxy-MSM8916/android_device_samsung_msm8916-common/pull/43
"Google PlayStore not showing some apps fix #43" Thanks for continuing, there is a fix on the way.
The fix at
https://github.com/ArbabAliRajper/a...mmit/73e686a841cb282299b97c133f097dfa2256706b
# Google Play Store
PRODUCT_PROPERTY_OVERRIDES += \
ro.opengles.version=196608
works. I can see more apps at the play store. I'll build this fix into the next September build after all the security patches are incorporated.
I don't know when msm8916 team will incorporate it or do something different.
I uploaded an Aug 26 build with the play store fix as per above and changed the build fingerprint. If I just use Magisk and enable hide Magisk, it passes CTS and shows as a "device is certified" in play store.
You may have to delete the files and cache in google play services and google play store to get rescanned for CTS.
I removed the Aug 20 build.
retiredtab said:
I uploaded an Aug 26 build with the play store fix as per above and changed the build fingerprint. If I just use Magisk and enable hide Magisk, it passes CTS and shows as a "device is certified" in play store.
You may have to delete the files and cache in google play services and google play store to get rescanned for CTS.
I removed the Aug 20 build.
Click to expand...
Click to collapse
Sorry for the delay, been busy the last few days. I appreciate you looking at it, this is the best this tablet has worked since I bought the thing. The main reason I wanted to go to 17.1 is Android 10 supports Bluetooth dual shock for remote play and 16 didn't. So I really appreciate everything you are doing. I wish I could afford to give you a little something, you deserve it, but unfortunately I can't at the moment. Let me know if you need anything from me though.
Edit: I hate to keep bothering you but is there any way to turn on the on-screen nav bar? I hate those buttons at the bottom and disabled them but I'm having some difficulty with XDA's navigation gestures, I'm used to my Pixel and I can't quite get it setup correctly.
sillycat98 said:
but is there any way to turn on the on-screen nav bar?
Click to expand...
Click to collapse
I'll add
qemu.hw.mainkeys=0
to the September security patch build.
For now, if you have Magisk installed, the easiest way to get on screen nav bar is goto Magisk Manager, menu, downloads, search for props, dowload and install and reboot.
Once rebooted, go settings, about tablet, tap build number 7 times to enable developer settings. Then system, advanced, developer options, enable local terminal.
Then go home, choose terminal app and type "props".
Choose 5 (add custom props), n (new), qemu.hw.mainkeys, enter, 0, enter.
Screen should say this will set qemu.hw.mainkeys to: 0
Press y to accept and reboot.
Your screen nav bar should appear after reboot.
Then goto settings, system, advanced, gestures, system navigation.
navigation bar settings are at buttons menu to let you swap (invert) the back and recent menu buttons to match hardware buttons.
Yes, I tested the above and there are no boot loops while adding this prop or use the prop editor that is downloaded from Magisk.
retiredtab said:
I'll add
qemu.hw.mainkeys=0
to the September security patch build.
For now, if you have Magisk installed, the easiest way to get on screen nav bar is goto Magisk Manager, menu, downloads, search for props, dowload and install and reboot.
Once rebooted, go settings, about tablet, tap build number 7 times to enable developer settings. Then system, advanced, developer options, enable local terminal.
Then go home, choose terminal app and type "props".
Choose 5 (add custom props), n (new), qemu.hw.mainkeys, enter, 0, enter.
Screen should say this will set qemu.hw.mainkeys to: 0
Press y to accept and reboot.
Your screen nav bar should appear after reboot.
Then goto settings, system, advanced, gestures, system navigation.
navigation bar settings are at buttons menu to let you swap (invert) the back and recent menu buttons to match hardware buttons.
Yes, I tested the above and there are no boot loops which adding this prop or use the prop editor that is downloaded from Magisk.
Click to expand...
Click to collapse
Thanks again, this worked a treat. I had used props to change the fingerprint before but had never messed with the custom option. I finally have a reason to use this tablet again thanks to you.
You rock.
BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
BACKUP YOUR DATA AND OLD ROM BEFORE trying this rom.
What works
I only test what I use. There could be other things that work or don't work. Let me be clear since there are people who don't seem to understand this. I cannot test things that I don't have like paid streaming/gaming, NFC, miracast or apps that I don't use. They may work or they may not work.
If you want to know if something works that's not listed here, then you need to try it for yourself. If that's not an acceptable or reasonable answer, then stop reading and find another rom that meets your requirements. I built this rom for myself to use and thought that some in the community might benefit by sharing it. If this rom doesn't meet your requirements, then delete it and use whatever does.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
What doesn't work
1. screen recorder. The current sepolicy doesn't allow screen recorder to work. While adding code to allow sepolicy to work
Code:
#============= mediacodec ==============
allow mediacodec camera_device:chr_file { ioctl open read write };
The [email protected] crashes. A mp4 file is created, but it doesn't seem to be in the correct format? Possibly related to ??
https://review.lineageos.org/c/LineageOS/android_device_htc_flounder/+/210609
FAQ
Q1) Does the build work on Nexus 9 LTE?
A1) I have no idea. I only have the Nexus 9 wifi so I don't know if it will work on LTE. If you have the LTE, you can build your own LTE rom. If you try the wifi build on the LTE, you may end up with a bricked device. Questions regarding LTE will go unanswered.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 14.1 or going back to the last rom that worked for you. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q3) My tablet hangs or crashes with 15.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 15.1 is a work in progress and will have bugs and frequent changes. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or higher. Get it from
Download TWRP for flounder
Download TWRP Open Recovery for flounder
dl.twrp.me
Q6) What is the difference between this rom and variants?
A6) Use whatever fits your needs. This is a stock LineageOS build with no modifications. I only offer this as an option for those who want or need a new rom and can't build it themselves.
Q7) Will there be a 16.0, 17.1 or 18.1 build?
A7) I tried building 16.0, but the rom get's stuck at the very begining of the boot process and I haven't investigated too much. Do not ask if there is progress on this. I'm an unpaid volunteer building this on my own time. Any questions regarding ETAs will go unanswered.
I suspect that one or two LineageOS developers have a working 16.0 build, but they are not ready to share their code? The repos have been updated to 16.0 at
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
on Nov 4, 2020.
If you are a rom builder or developer and want to help get 16.0 going, please contact me.
Q8) Should I upgrade from stock or 14.1 to 15.1?
A8) It's entirely up to you. If you do upgrade, you will need to backup your data, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. You cannot dirty flash from stock or 14.1 to 15.1, it must be a completely clean fresh install.
Q9) Can I build this rom myself? Where can I find the source and/or kernel source code?
A9) This is one of the few roms where it required no edits or changes to make it work. Follow the instructions at
Flounder
Build for flounder | LineageOS Wiki
wiki.lineageos.org
Flounder_lte
Build for flounder_lte | LineageOS Wiki
wiki.lineageos.org
and you will get a working 15.1 image. You will need to apply (hw video patch)
https://review.lineageos.org/268654
The roomservice.xml only consists of 3 repos. The roomservice.xml points to all the source code including the kernel source code. That is,
GitHub - LineageOS/android_kernel_htc_flounder
Contribute to LineageOS/android_kernel_htc_flounder development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_htc_flounder
Contribute to LineageOS/android_device_htc_flounder development by creating an account on GitHub.
github.com
GitHub - TheMuppets/proprietary_vendor_htc
Contribute to TheMuppets/proprietary_vendor_htc development by creating an account on GitHub.
github.com
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_flounder" path="device/htc/flounder" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_kernel_htc_flounder" path="kernel/htc/flounder" remote="github" revision="lineage-15.1" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.1" />
</manifest>
I changed the fstab.flounder from forceencrypt to encryptable.
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
Normally, monthly builds go smoothly, but every once in a while, the monthly changes break something. This happened with the Nexus 9 for the May 5 security patches. While compiling, it was giving
"SSL error when connecting to the Jack server."
After some dead ends and research, I found
Rebuild android code with error “SSL error when connecting to the Jack server. Try 'jack-diagnose”
System: ubuntu 18.04 environment：VirtualBox The first time I compiled the AOSP source code on Ubuntu 18.04, it passed, and the second time I compiled it failed. Here is an error message. [ 10% 538/...
stackoverflow.com
To fix this, you need to "Remove TLSv1, TLSv1.1 from jdk.tls.disabledAlgorithms in /etc/java-8-openjdk/security/java.security" file.
Q10) Why is my question not answered?
A10) It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q11) How is this 15.1 build different from the ones already on XDA?
A11) The 15.1 roms built before Nov 4, 2020 didn't include this patch
flounder: Patch libraries that rely on arm libm intrinsics · LineageOS/[email protected]
* Force-pick https://review.lineageos.org/268655, build "libm" target, rename "libm.so" to "libw.so", and then: `sed -i 's/libm.so/libw.so/g' libw.so...
github.com
Also, some of the 15.1 roms may not have included the hw video patch. It's not part of the repository and requires the builder to pick and apply that patch manually.
For some, depending on how the device is used, having the hw video patch isn't necessary and will work fine without it.
Q12) Is the video hardware accelerated in 15.1?
A12) Yes. The March 9, 2021 and all future builds include this patch
https://review.lineageos.org/268654
for video hardware acceleration.
Q13) Is encryption enabled by default?
A13) Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior starting with the March 13, 2021 build so that encryption is disabled by default.
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
Q14) Can you build a variant like slimrom, crDroid, etc?
A14) No, but you can following the instructions and source code above that has been provided.
Q15) What gapps should I use?
A15) I personally am moving away from all google apps and technology. If you must use gapps, pick the smallest one which is pico ARM64.
Q16) Where can I download this rom?
A16) See
retiredtab - Browse /Nexus 9/15.1 at SourceForge.net
sourceforge.net
Feb 24, 2022 release notes
1. Incorporates UNOFFICIAL Feb 5 security patches as per https://review.lineageos.org/q/topic:O_asb_2022-02
2. Whatever LineageOS changed since Jan 5, 2022 (about 2,900 files had to be recompiled).
Jan 28, 2022 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:O_asb_2022-01
2. Whatever LineageOS changed since Dec 2021 (about 1,200 files had to be recompiled).
Dec 9, 2021 release notes
1. Incorporates Nov 5 and Dec 5 security patches as per https://review.lineageos.org/q/topic:P_asb_2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12. Specifically
Nov 5th
Code:
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318648
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318649
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318650
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318651
https://review.lineageos.org/c/LineageOS/android_packages_apps_Contacts/+/318654
https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/318655
https://review.lineageos.org/c/LineageOS/android_build/+/318658
Dec 5th
Code:
https://review.lineageos.org/c/LineageOS/android_external_tremolo/+/319986
https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/319987 --> slight problem merging due to 14.1 and 15.1 code differences
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/319988
https://review.lineageos.org/c/LineageOS/android_packages_apps_Contacts/+/319989
https://review.lineageos.org/c/LineageOS/android_packages_apps_KeyChain/+/319990
https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/319991
2. Whatever LineageOS changed since Oct 2021 (about 4,300 files had to be recompiled).
3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.
Oct 11, 2021 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317622
2. Whatever LineageOS changed since September 2021 (about 2,400 files had to be recompiled).
3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.
Sept 24, 2021 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316179
2. Whatever LineageOS changed since August 2021 (about 1,800 files had to be recompiled).
3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.
Aug 9, 2021 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314577
2. Whatever LineageOS changed since July 2021.
3. This is the second build using Andrea's repos.
July 18 release notes
1. First build to incorporate changes by Andrea.
2. Incorporates July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313627
3. Whatever LineageOS changed since June 2021.
June 13, 2021 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312243
2. Whatever LineageOS changed since May 2021.
May 11, 2021 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309566
2. Whatever LineageOS changed since April 2021.
April 15, 2021 release notes
1. Incorporates April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307722
2. Removed livedisplay option from menu as it doesn't work on Nexus 9 Tegra SoC according to those more knowledgeable and experienced than I.
3. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.
Release notes for March 13, 2021
1. Changed encryption to be disabled by default.
Release notes for March 9, 2021
1. Initial build for 15.1 Nexus 9 wifi only.
2. March 5, 2021 security patches
3. Built from LineageOS 15.1 repos with no changes or edits and includes the hw video patch.
4. Please be patient on first bootup.
For those that downloaded the March 8 build, please delete it. While it works, there was a problem with the build missing a hw video patch that I didn't notice at first. I will upload a March 9 build. Sorry for the trouble.
Reserved
For those that downloaded the March 8 build, please delete it. While it works, there was a problem with the build missing a hw video patch that I didn't notice at first. When I did a clean repo sync, I forgot to apply the hw video patch at
https://review.lineageos.org/268655
in the March 8 build. The March 8 build works as I tested it, but it wasn't until a few hours later that I realized I forgot to reapply the hw video patch.
The March 9 build includes the above hw patch. Sorry for the inconvenience.
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
AgentCain said:
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
Click to expand...
Click to collapse
Me too
I don't use or load gapps and I never use ok google. I'm degoogling everything in 2021.
New build lineage-15.1-20210313-UNOFFICIAL-flounder.zip has force encryption disabled by default.
Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior.
Since 15.1 will never be official, I changed the fstab.flounder from forceencrypt to encryptable.
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
If you want encryption disabled, backup all your data, goto TWRP, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. Then install the March 13 build and encryption will be disabled by default. You can also change the cache and data to f2fs if you want for potentially better performance.
Going forward, all monthly security builds will have encryption disabled unless you enable it.
PS. That's the only change from the March 9 build. The above has been added to the FAQ now.
bought a nexus9 yesterday, went the noob path (outdated toolkit to unlock bootloader/ root+twrp... updated twrp to 3.5.9.0) then flashed your current rom... (9march) feel smooth and nice!
thanks for continuing working on this device! its a real upgrade from my previous tab (8" tab 3).. we cant all spend money on fancy device, nexus9 is still relevant today with this nice custom rom!
edit2: stupid me of course... now build 2021.03.13 is working well without encryption problem! (was trying to remove encryption following your tutorial with the previous rom)
I think there is a problem with accout registration. Ok google not working but it's impossible to register some account. I try microsoft one for word. It say internet connection is not present. Maybe this can help to solve the problem
Wow! Thanks for this! Since the new XDA update, it has been so awful I stopped using it. I just popped back on after 2 months away from XDA and found this rom! Going to try it soon.
One problem I had was with stadia not working. I don't mean to ask if it does now, but it does seem that the chrome browser version works now (vatrom's version). Can you at least take an educated guess if the new hardware acceleration patch in the repo might help get stadia working properly? I suspected it was either an unsupported codec or an issue with hardware acceleration being the culprit. Thanks
gk1984 said:
One problem I had was with stadia not working.
Click to expand...
Click to collapse
Never heard of stadia and I don't use google chrome browser.
Google Stadia is Google's cloud gaming platform. And no, I didn't ask about Chrome. I simply was trying to ask some clarity about Lineage's hardware acceleration patch vs Barron's, but included context to my situation. I clear8 stated I wasn't exactly asking if Stadia was working, but if the new hardware acceleration patch could impact it and why.
It's pretty unprofessional to blanket statement "I don't use x" and ignore the question. It also hurts your credibility as a developer if you can't explain what's being parched into the code if you directly mention it in the OP. You could simply respond with "I'm not an experienced developer and can't articulate X or Y, I'm just capable of building from source and distributing." We don't know you, we don't know your skill level or knowledge. I'm used to ROM developers or at least those building them to know what they're working on. But your. Blanket statement suggests otherwise.
back again.. and it fixed now! of course, i've downloaded the 20210309 build and couldnt figure a proper way to remove encryption on data partition... I've managed to flash gapps (use an old 16go usb key with microusb connector)..and come back to read CORRECTLY your post and understood my mistake... it was an old build!
Did a clean flash and flashed 0313 build, no more encryped data now! (flashed some nano gapps + magisk) setting up the device, so far so good!
It's great to see some people still have this tablet! They are under $50 used now, but it's a shame about stock performance...
Just some personal screenshoot...
AgentCain said:
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
Click to expand...
Click to collapse
I found a solution. Install the Google app from ApkMirror.com and restart the tablet. Should work after that. Looks like it's a common problem with open gapps I. General.
Hey thanks for sharing your rom
Can I dirty flash this rom from the other lineage os 15.1 build?
I'm not the developer, but I wouldn't recommend it. That usually leads to Android being unable to boot. Best to factory reset.
gk1984 said:
I found a solution. Install the Google app from ApkMirror.com and restart the tablet. Should work after that. Looks like it's a common problem with open gapps I. General.
Click to expand...
Click to collapse
Thanks it work for me
BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
BACKUP YOUR DATA AND OLD ROM BEFORE trying this rom.
I'm simply offering this rom for those who cannot build it themselves.
What works.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
FAQ.
Q1. How did you build this? Where can I find the source code and kernel source code?
A1. This is a continuation of bryan2894's 14.1 code found on github. His last rom was built Nov 19, 2017. His github repo shows the last changes on Nov 24, 2017. So you will get the following changes as seen at
Commits · thewizrd/android_kernel_samsung_msm8660-common
Contribute to thewizrd/android_kernel_samsung_msm8660-common development by creating an account on GitHub.
github.com
You will also get whatever LineageOS 14.1 changed in the last 3.25 years including the latest March 2021 security patches.
Thanks to @bryan2894 for his repos so I can build this rom. I have added no value, changes or edits to this rom other than compiling it for 2021.
Q2. Can you fix this GSM/LTE/voice/call/text bug?
A2. No. I recently bought the SGH-I727 (code named skyrocket), but I have no SIM card and I do not plan to get one. So I cannot fix any GSM/LTE/voice/call/text bugs that exist in this rom. Any questions regarding lost, dropped, poor quality calls, low or high volume, poor sound quality, bad microphone, can't recognize sim, etc will go completely unanswered. Do not report these bugs as they will not be fixed by me. If you want to fix them, you can look at the code repositories in post #1.
In addition, there are proprietary voice/radio Samsung blobs where there is no source code so changes are virtually impossible to make.
Q3. What version of TWRP should I use?
A3. You must follow the instructions in post #2 as written by bryan2894 exactly. I followed them and was able to flash my build successfully. If you can't flash the rom, it's likely you are not following the instructions provided. Do not ask TWRP questions in this thread, they will go unanswered.
Q4. How long does the first boot take?
A4. Booting the initial LineageOS 14.1 takes about 7.5 to 8 minutes. Be patient. After it boots, let it sit untouched for 5 minutes and then reboot the phone again. After it boots, let it sit untouched for 5 minutes again before proceeding. This will let the phone do all its stuff and get itself ready.
Q5. Does it run gapps?
A5. This phone was released in Nov 2011 so it's almost 10 years old. It only has 1GB DRAM so I would suggest that you DO NOT install gapps for best performance. There are many alternatives to gapps including Aurora Store and/or installing apks directly onto the phone. Similarly, if you watch youtube videos, I suggest newpipe which is an open source viewer and can skip ads. I use the Brave browser because it has an adblocker and anti tracking features and it works well with this 10 year old phone.
Obviously, it's going to be slower than a new phone, but it's useable as a second phone or some young person's first phone.
I use all the software below.
Aurora Store | F-Droid - Free and Open Source Android App Repository
A Google Playstore Client
f-droid.org
Releases · TeamNewPipe/NewPipe
A libre lightweight streaming front-end for Android. - TeamNewPipe/NewPipe
github.com
Secure, Fast, & Private Web Browser with Adblocker | Brave Browser
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software.
brave.com
If you must install gapps, choose pico as it's the smallest one.
Q6. Will there be monthly security patches?
A6. Yes as long as I have high speed Internet, I will try to release the rom monthly to incorporate the security patches around mid month (10th to 20th). At some point, LineageOS will discontinue back porting security patches to the 14.1 code and that's when I will stop releasing roms. Google does not provide security patches for Android 7.1 anymore (aka LineageOS 14.1).
Q7. Will there be a 15.1, 16.0, 17.1 or 18.1 release?
A7. I compiled 15.1 and while it compiled without errors, it does not boot. I get no boot animation and there is no adb output which makes debugging very difficult. I suspect a kernel problem. If someone can assist, maybe a team of people can get 15.1 running?
Q8. Can you provide step by step instructions?
A8. You can do your own research on how to install a rom and you must read bryan2894's TWRP post #2. There's lots of written FAQ or videos that show you how. In addition, I don't run Windows so I cannot answer any questions regarding drivers, odin, etc. Questions regarding how to install roms, TWRP and Windows will go unanswered.
Q9. Why is my question not answered?
A9. It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q10. Can I build this rom myself?
A10. Yes, I have provided the roomservice.xml file that I used to build the rom. With it, you can follow any LineageOS build guide/template like
Build for chagallwifi | LineageOS Wiki
wiki.lineageos.org
That's how I built my first rom.
If you are running a newer version of Linux, you may need this additional command to compile the rom.
Code:
export LC_ALL=C
For the June 2021 security patch, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
Q11. Does this rom run on Hercules?
A11. I have no idea. I only have SGH-I727 and that's what I tested it on. Celox is supposed to be the unification of Hercules and skyrocket, but I can't verify if it runs on Hercules. Having said that, member squircular in post #4 says it works on his/her Hercules device. There's no guarantee that with each monthly security update/patch that this will be true going forward.
Q12. I don't like this rom, can you help me revert back to stock or my old rom?
A12. No. If you want to try this rom, you must backup your data and know how to revert back yourself. Questions of this nature will go unanswered.
Q13. I bricked my phone trying to install this rom. Can you help me?
A13. You assume all responsibilty for trying this rom including a possibly bricked device, lost data, security vulnerabilities, etc. If you are not comfortable flashing roms and don't know how to revert back to stock or older rom, do not install this rom.
Q14. Okay, I accept all the risks and know what I'm getting into, now where can I download this rom?
A14. You can get it at
retiredtab - Browse /SGH-I727/14.1 at SourceForge.net
sourceforge.net
NOTE OS will show June 5th, 2021 security patches due to hold up of
https://review.lineageos.org/c/LineageOS/android_build/+/313397
Release notes for July 9, 2022
1. UNOFFICIAL July 5th, 2022 security patches as per
https://review.lineageos.org/q/topic:n-asb-2022-07
2. Whatever LineageOS changed since June 5th security patches (about 2,100 files had to be recompiled).
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for June 10, 2022
1. UNOFFICIAL March, April, May and June 5th, 2022 security patches as per
https://review.lineageos.org/q/topic:n-asb-2022-03
https://review.lineageos.org/q/topic:n-asb-2022-04
https://review.lineageos.org/q/topic:n-asb-2022-05
https://review.lineageos.org/q/topic:n-asb-2022-06
2. Whatever LineageOS changed since Feb 5th security patches (about 2,000 files had to be recompiled).
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Feb 24, 2022
1. UNOFFICIAL Feb 5th security patches as per ttps://review.lineageos.org/q/topic:n-asb-2022-02
2. Whatever LineageOS changed since Jan 5th security patches.
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Jan 28, 2022
1. Jan 5th security patches as per https://review.lineageos.org/q/topic:n-asb-2022-01
2. Whatever LineageOS changed since Dec 5th security patches.
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Dec 8, 2021
1. Nov 5th and Dec 5th, 2021 security patches as per https://review.lineageos.org/q/topic:n-asb-2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12 (about 2,100 files had to be recompiled).
2. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Oct 11, 2021
1. July 5 + August + September + October, 2021 security patches as per
https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:eek:pen OR status:merged)
2. A reboot after flashing the October build will take about 6 minutes. Be patient.
Release notes for July 9, 2021
1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(statuspen OR status:merged)
2. A reboot after flashing the new build will take about 6 minutes. Be patient.
Release notes for June 9, 2021
1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(statuspen OR status:merged)
2. A reboot after flashing the June build will take about 6 minutes. Be patient.
3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
Release notes for April 15, 2021
1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
2. A reboot after flashing the April build will take about 6 minutes. Be patient.
Release notes for March 8, 2021
1. Initial build for Celox.
2. March 5, 2021 security patches
3. Built from bryan2894 repos with no changes or edits.
4. Please be patient on first bootup. It can take up to 8 minutes. If you installed gapps, then it will take even longer.
Reserved
I can verify that this ROM works on Hercules (SGH-T989D). Thanks very much for your effort.
squircular said:
I can verify that this ROM works on Hercules (SGH-T989D).
Click to expand...
Click to collapse
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?
retiredtab said:
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?
Click to expand...
Click to collapse
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start). Both of these measurements were taken inside near a window so it might be faster outside.
squircular said:
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start).
Click to expand...
Click to collapse
Thanks for the feedback. I appreciate it.
Since I bought my phone used, I'm not sure if my GPS is working 100% due to hardware. It shows the satellites, but never gets a fix. If it does work, it takes about 10 minutes to get a fix. It's completely useless for a car GPS.
There are some error messages in the adb logcat which might be related to why I can't get a fix, but I will have to investigate.
I'm going to give this a try - this will be my first modded phone and so I'm taking it very slow. I've got a Rogers Samsung Galaxy S II Skyrocket SGH-I727R which I'm ok with making a mistake on. I don't want Gapps. I've currently got TWRP 3.1.1 and I'm reading through everything multiple times.
My current task is to do my best to understand bryan2894's notes on repartitioning.
Hello retiredtab (or anyone else),
I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:
4. In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.
As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.
Is this correct?
Many thanks for anyone who can confirm this.
JMSchneider said:
Hello retiredtab (or anyone else),
I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:
4. In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.
As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.
Is this correct?
Many thanks for anyone who can confirm this.
Click to expand...
Click to collapse
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.
retiredtab said:
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.
Click to expand...
Click to collapse
Thank you for the reply retiredtab - your input is greatly appreciated!
I think I found an article on TWRP that explains the partition name change.
Because the 'Internal Storage' seems to have changed spots (as indicated in the last post), I came up with a workaround for a problem that I encountered.
Initially, I was using the twrp-3.0.0-0-skyrocket.tar.md5 and reasoned it would be the "latest OFFICIAL TWRP" file for the ROM Installation instructions but in step #9 I ran into a problem - a red-highlighted section of the log read "Updater process ended with ERROR: 7". I later discovered this has something to do with version compatibility mismatching. So I decided to regress to the older Official TWRP (v2.8.6-0) recovery and go at the whole process with the exact files in the links. Then, when I went to flash the ROM I had no problems.
bryan2894 and others did all the initial work on TWRP and building this rom. I'm only updating his work + others so I don't know why specific versions of TWRP are required. All I know is that I followed his instructions exactly so that I could build a 2021 rom. As I stated, I'm adding NO VALUE other than compiling a 2021 version.
Once the 14.1 April security patches get merged in LineageOS, I will compile a new version, test it and then share with others who are interested. It looks like there are 5 patches for April as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
A number of people says it compiles, builds and boots with no problems, but I prefer to wait until it's officially merged before I start the compile process.
New build called lineage-14.1-20210415-UNOFFICIAL-celox.zip (had to try 3 or 4 times before upload succeeded).
Release notes for April 15, 2021
1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
2. A reboot after flashing the April build will take about 6 minutes. Be patient.
The May security patches still aren't merged yet into LineageOS as per
https://review.lineageos.org/c/LineageOS/android_build/+/309293
It's waiting approval since May 6. There are 3 CVEs for May.
At this rate, I'll probably skip making the May security patches and wait for June 5th as it's May 26 as I write this.
The May 5th security patches finally got merged today, June 7, as per
https://review.lineageos.org/c/LineageOS/android_build/+/309293
However, seeing how the June 5th patches should be announced shortly on LineageOS, I will wait until those are announced and then make a June build. No sense making a May build, testing and uploading it if June patches will be out in a few days.
New build called lineage-14.1-20210609-UNOFFICIAL-celox.zip.
Release notes for June 9, 2021
1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(statuspen OR status:merged)
2. A reboot after flashing the June build will take about 6 minutes. Be patient.
3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
New build called lineage-14.1-20210709-UNOFFICIAL-celox.zip
Release notes for July 9, 2021
1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)
2. A reboot after flashing the July build will take about 6 minutes. Be patient.
New build called lineage-14.1-20211011-UNOFFICIAL-celox.zip
I have not forgotten about this device, but there's a holdup with the security monthly patches starting with the July 5 patch not being merged due to a problem as per https://review.lineageos.org/c/LineageOS/android_build/+/313397
However, the August patches are officially merged while the September and October ones are pending approval. Rather than wait any longer, I decided to merge September and October security patches into this build.
So while the OS may report that it's on the June 5th security patch, that not true in this case. It has all the October 5th 2021 patches included.
Release notes for Oct 11, 2021
1. July 5 + August + September + October, 2021 security patches as per
https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:open OR status:merged)
2. A reboot after flashing the October build will take about 6 minutes. Be patient.