I've created this thread to discuss LOS19. Hopefully, one of the maintainers will create a proper thread.
Downloads
Official: https://download.lineageos.org/sunfish
Installation
https://wiki.lineageos.org/devices/sunfish/install
Upgrading from 18.1
https://wiki.lineageos.org/devices/sunfish/upgrade
Updating
https://wiki.lineageos.org/devices/sunfish/update
If you find their work useful, don't forget to support all their work.
https://paypal.me/LineageOS
https://patreon.com/LineageOS
Visual Voicemail Error
I'd like to thank @razorloves for working on a fix to the VVM problem. Razorloves has already provided the work to the Android project. Let's hope all goes well. The work is greatly appreciated.
Razorloves created a new "Dialer.apk" for LOS19. The LOS18 version is already being shared in that thread.
I've attached "Dialer-19.1.zip", which contains the file razorloves created with the fix. There's also a sourceforge download link. I don't know if that would be better.
To try this fix....
Enable USB debugging in your phone.
Enable ADB root in your phone.
Use these adb commands....
'adb root'
'adb remount'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is from 2008
'adb push Dialer.apk product/priv-app/Dialer/Dialer.apk'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is now from 2022
reboot your phone.
Hopefully, the fix will make it through AOSP & onto the official LOS19 ROM soon.
Got notice that the VVM issue has been closed. The Dialer app will be fixed in next build.
So, if you're on LOS19, you can just wait for the June 2 build.
Big thanks to @razorloves for the work that made it happen
EDIT: Sorry! Deleted this post because my lack of knowledge made it appear like I was insultingly impatient. Many thanks to all the people who make LOS available for us dunces.
Sincere apologies to anyone whom I might have offended.
Since I switched from LOS18 to LOS19, I'm having a couple of issues.
This is NOT a complaint. I'm simply sharing to see if others are also experiencing these.
I updated per the LOS webpage instructions (ie. not a clean install). Phone has no custom-kernel,
no GApps, and no Magisk. Build is June 9th (latest).
1) Calendar notifications.
I'm not getting calendar notifications. This was working fine in LOS18. I'd get a notification at the defined time before an event. Sometimes, while I'm working on the Calendar, I get old notifications (as in events from days ago). Today, while testing, I got a "Calendar keeps stopping" popup.
My calendar data is offline. I deleted my calendar and created a new one. Nothing changed.
2) Charging.
When I plug into my PC, I get the sound acknowledgment from my phone. The Battery screen tells
me "Charging". However, it is not charging.
EDIT: As always, I'm a day late and a dollar short.
This is a known LOS19 issue (with USB) that was being processed. They have a fix in place that we should see next build (June 16th). Thanks (again) to the LOS team for their time/effort!
Is anyone else having the Calendar issue? If you're not, did you update to LOS19? Or, did you perform a "first time" install (wipe data & such)?
Thanks for your time.
@mangokm40 How is the battery life on LOS 19?
AkumDX said:
@mangokm40 How is the battery life on LOS 19?
Click to expand...
Click to collapse
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
mangokm40 said:
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
Click to expand...
Click to collapse
Oh okay ... Haven't used LOS 18 for few months now... Currently on 13 beta, battery isn't that great so thought of switching
4a LineageOS 19.1 Update 2022-06-16 - Security Bump
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-09 + lineage-19.1-20220609-recovery-sunfish to build 2022-06-16. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 12 minutes.
There are a bunch of changes as you can see here:
I tested the USB fix. It's not working for me. Thanks to user razorloves. I toggled the "Always allow USB connections" setting in "Settings->Privacy->Trust". My phone is now charging, even when locked.
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "June 5, 2022".
The Vendor security patch level (just below) is also "June 5, 2022".
The Build number at the bottom is now "SQ3A.220605.009.A1".
The Baseband updated to "g7150-00090-220406-B-8411773".
See Android Security Bulletin - June 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220616" and active slot 'a'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
lefteyecat said:
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
Click to expand...
Click to collapse
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
mangokm40 said:
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
Click to expand...
Click to collapse
Thanks,looks like i have to hold out on 18 for as long as i can.
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
Nope.
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
i use swiftbackup and nova launcher, its not as good as twrp ( still need log in verifications) but does restore all apps and screen positions , best and easiest solution i have found so far. Root reguired.
Is anyone running the latest version of LOS19 (lineage-19.1-20220623-nightly-sunfish-signed.zip) ?
I'm asking because there's this VVM issue open for a OnePlus7, running LOS18.
VVM is working for my 0616 build of LOS19, and the issue mentions it broke when they installed their device's 0619 build. Thus, I looked at the list of changes for our device here.
There are 5 changes to "android_packages_apps_Contacts".
There are also many changes to "android_vendor_lineage" that mention APN changes for various carriers.
I'm wondering if anyone is running the 0623 build & has VVM working.
Thanks.
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
mangokm40 said:
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
Click to expand...
Click to collapse
Thank you mangokm40 for all the infos, tips, tricks and hints you post! Really appreciate it!
4a LineageOS 19.1 Update 2022-07-14 - Security Bump, Calendar Update, Hidden Apps
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-16 + lineage-19.1-20220616-recovery-sunfish to build 2022-07-14. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 11 minutes.
There are a bunch of changes as you can see here.
The ones that I noticed are:
1) Security Bump - see details below.
2) Calendar Update - the update to version 1.0.30 didn't clear the search crash problem. The battery use is now forced to "Unrestricted", to allow all notifications to appear on time.
3) Hidden & Protected Apps - It remembered all my hidden apps from LOS18 & they were hidden without needing any new input from me. WooHoo!
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "July 5, 2022".
The Vendor security patch level (just below) is also "July 5, 2022".
The Build number at the bottom is now "SQ3A.220705.003.A1".
The Baseband remains as "g7150-00090-220406-B-8411773".
See Android Security Bulletin - July 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220714" and active slot 'b'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Hello, can someone help me with the following question?
* Does Google Pay / banking apps work good with this rom? I suppose that magisk is needed along with some safetynet fix?
Thanks!
Related
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 before flashing!!!! This can be created with minitool partition wizard on Windows or gparted on Linux.
If on a BML rom (stock-based GB)...
0. Read "Things to take note of" below
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 root or Gapps, flash them now
If on an MTD rom (CM7 and all ICS+)(I tested CM9, CM10.1 and CM11)...
0. Read "Things to take note of" below
1. Reboot to recovery
2. Wipe data, and cache paritions (just in case). If updating to a newer build, you can probably skip this step
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
Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!
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 and also provide T959P builds.
The USB connection is MTP and not mass storage as Omni has removed mass storage. In recovery there is still an option to mount as mass storage device.
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 reportedly slow down the device significantly so tread carefully.
Backup Backup Backup! I'm not responsible for you losing any data.
Working
Taking pictures
RIL
SMS
Data
Recovery
Bluetooth
Wifi
Vibration
Powered-off charging animation
Flash from BML
Video Recording
Automatic Brightness
Moving Apps to the SD Card
GPS
Encryption
Compass
SElinux in enforcing mode
What probably doesn't
Microphone mute option doesn't work during calls
What doesn't
720p recording is very laggy
What's been removed
TV-Out - It was removed upstream plus I think binary blobs are broken in Lollipop...
Live wallpapers - this is a low-ram device
Everything else is not tested!!!
XDA:DevDB Information
Unofficial OmniRom 5.1 for the Galaxy S 4G (T959V) and Galaxy S Fascinate 4G (T959P), ROM for the Samsung Galaxy S 4G
Contributors
xc-racer99, humberos
Source Code: http://github.com/omnirom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: All
Based On: OmniRom
Version Information
Status: No Longer Updated
Created 2015-06-30
Last Updated 2016-05-12
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 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-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Download folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch galaxys4gmtd"
Changelog
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
Notifications are sometimes wonky. To fix, in Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.
Changelog for 2015/07/20 Build
The data partition is now the second partition of the SD Card as opposed to internal storage
Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.
HSPA vs UMTS settings in DeviceSettings has been fixed
High-End graphics are forced by default to fix notification issue
ART parameters have been tweaked
Miscellaneous other tweaks, see my Github for details
Changelog for 2015/07/24 Build
Stabilized bluetooth connection
Fixed typo in GPS initialization. Does it work?
Added ability to use f2fs file system on /data. Supposed to give better performance
Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...
Changelog for the 2015/07/29 Build
This is a maintenance build. Very little has changed
Some more RAM freed (disabled some debugging stuff, TV-Out driver, IR driver)
Sepolicy updated for fast charge and touch wake
GPS initialization tweaked - unsure if works. If it doesn't, a dmesg would be appreciated
Changelog for 2015/08/02 Build
SElinux changed to permissive - this build only
GPS sepolicy changed - unsure if all necessary things are implemented
Changelog for 2015/08/13 Build
Selinux back to enforcing. Thanks to @anoymonos for the dmesg and @DerPugNa for offering to send me one as well
Fixed encryption
Changelog for 2015/08/31 Build
Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)
Restoring /system in TWRP should now work
When installing from BML, a chance is given to install gapps and/or SuperSu before rebooting
zRam is now actually used...
Changelog for 15/10/2015 Build
Fixed typo in updater.sh (thanks @FBis251!)
Update Omni source code - plenty of little tweaks since last build
Source Code and Downloads
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-5.1-t959v branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)
Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing
Please let me know if the link doesn't work! There are also builds there for the T959P, in case there are any users of it left.
Gapps
Gapps do not work on builds prior to 2015/07/20. On more recent builds, they can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2
SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/
Thanks thanks ....
Awesome work @xc-racer99!
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
GFX.myst. said:
Wow, bringing this ole device back from a coma here. Nice to see someone else willing to work on lollipop for this oldie but goodie. Keep this device alive man.
Edit: If you are in need for some GFX for this thread, let me know and I'll see what I can brew up for you.
Click to expand...
Click to collapse
I hope I can keep this great little device going a little longer, however it will probably get tough. I did a repo sync earlier today and things are starting to break. The last few builds haven't even booted. With humberos no longer maintaining the i9000 and aries-common, I've had to fork the aries-common repository to try to keep going. The only upside of this is that I now have a little bit more freedom and can add things in if I want to.
Thanks for the offer of the graphics. If I can get a new build working, then I'll probably take you up on your offer. I think I've traced the problem but I'll have to wait and see...
For anyone that is trying/has tried this out, I'd be very curious on the status of the GPS on the T959V. I'm interested in creating the sepolicies for it so we can put selinux into enforcing mode but I don't want to go to the effort if it doesn't even work right now.
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
New Build Uploaded!
Download is still at the same link as before, just use the 2015-07-03 build
I managed to find out why my new builds hadn't been booting - it was because the syntax for using a custom kernel toolchain had changed.
Anyway...
Changelog for 07/03/2015 Build
Newer Omni source
Added volume controls and flight mode toggle to power button menu
Added Bigmem option. This increases available RAM by ~20mb but breaks 720p video recording. Humberos created the kernel setup and I integrated a toggle for it into Advanced device settings.
Selinux is now in enforcing mode. I had to modify the GPS startup to have any chance of getting here. Please let me know if it still works/doesn't work/never worked
On another note, I've had a look at re-implementing TV-Out support. It doesn't look promising as several of the functions in the android frameworks that it used have been tweaked.... Still working on it but don't hold your breath.
Also, if somebody could test dock audio that would be appreciated. I don't have any way of testing it. If it doesn't work, I do have an idea on how to fix it (for those interested, another almost-aries device, the Infuse 4G, had to modify things slightly to get it to work. I would try to emulate their solution).
Omg download nowwww....thanks my friend
Alright, I'm having some issues on the latest build with notifications and the lockscreen. I'm still working on tracing down the reason for the problem...
DickyG said:
I've downloaded the zip and one of the smaller Gapps packages...won't be able to flash until early next week...I'll be out of town...will post results later...thanks for keeping this phone current.
Click to expand...
Click to collapse
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
billowusu47 said:
Hello, im a user of a t959v. And I've been using this rom for three days. Everything is fine and very smooth on this rom except that, I can't install anything from the playstore. I always get (cannot install app due to an error 963). And Ive tried all the gapps, even the new link provided but still no luck.
Click to expand...
Click to collapse
Good to hear that that's its (mostly) been working for you. I was hoping that the gapps problem was just me
Out of curiosity, which of the alternate gapps did you try?
A brief google of the error brings up a couple of possibilities...
Try an older gapps version. The ones from devloz on the i9000 thread devloz and the oldest revision for 5.1.1 are probably your best bet. Please be aware that Google Play store will automatically update!!! In order to prevent this, you will need to create a folder called "com.android.vending-1.apk" in /data/app (use a root explorer such as ES File Explorer or adb if you know how). If a file with that name already exists, delete it first.
Another thing to try would be to unmount your sdcard first before trying to install an app. I know, its a terrible work-around but it should work. This is because the error is that Google Play is trying to save some data on your sdcard but then for some reason it fails (I'm not sure why).
I'll hopefully get around to seeing if its a permissions problem after I find out what's been causing the issue with the notifications on the latest build.
P.S. Does the GPS work?
Early update...
...ROM flashed fine...a little slow to boot...about 3 minutes...but it booted.
...Gapps flashed fine...used 20150513_5.1.x package
...Installed Super SU (although I don't think that's necessary) and TB.
...So far only gave a quick test to camera and web browser...no problems.
...Am now in the process of re-installing user apps and data from TB...this will take a while.
When I'm done with that, I use Link2SD to link most of my user files to the SD card. After that is all set up, I'll test stuff like GPS, root access, etc. I'll post back later...maybe tomorrow.
But so far so good.
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
DickyG said:
OK...I did some testing tonight and here's some results.
Working:
.it boots
.root
.browser
.playstore
.camera
.link2sd (about 180 mb free in internal)
.camera
.wifi
.email
Nor working:
.bluetooth
.google search/voice search
.just about all the rest of the Gapps
.tons of force closes including Maps so can't test GPS
Won't be able to do anymore testing until next week.
Click to expand...
Click to collapse
Alright, thanks very much for the update. I'll do some more testing here and see if I can solve anything. For me, bluetooth file transfers to the phone work but not from the phone.
I've been looking at the notification "error" where the lockscreen notifications do not appear correctly. It appears to have been introduced upstream with a merge. I'm having difficulty finding out exactly what changed and since no errors are being thrown in the logcat, it could be a while...
For testing the GPS, there's an app from the Play Store called GPS Test which does a nice job of showing satellites and whether or not you have a lock on them.
you're the man!
nice one! its nice that this device are still alive.! and now were on 5.1
DerPuGNa said:
nice one! its nice that this device are still alive.! and now were on 5.1
Click to expand...
Click to collapse
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.
For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work
Uh-oh, looks like I jumped the gun.... Having problems once again
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
AgainstTheFlow said:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
Click to expand...
Click to collapse
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!
I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.
I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...
All the problems with the notifications that I've found are:
Only one notification will show up at a time
Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)
Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss
The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock
SRGX2 for Life One X2 MiniThis Rom Is a Stripped down modified version of the Life One X2 Mini stock Rom.
NOTE: After installation give Launcer 3 notification permission and update Google Play Services (click on the notification).
(Please remember I do this in my free time and with my own money. If you like it please hit the thanks button)
Mods:
Malware removed
Build.prop Tweaks
Oreo Launcher
Camera app replaced by OpenCamera
File manager replaced by MiXplorer
To do list:
Build wifi drivers into the Kernel
Strip down rc scripts
What Works:
Boots
Calls
SMS
Data
GPS
Wifi
Bluetooth
Audio
Video Playback
Sensors
Led
Camera
Flash
Fingerprint
Not Working Yet:
(You tell me)
Downloads:
Current Build: https://www.androidfilehost.com/?fid=673956719939824825
Builds: https://www.androidfilehost.com/?w=files&flid=239712
Patches: https://www.androidfilehost.com/?w=files&flid=254440
TWRP: https://drive.google.com/file/d/0BzMHnGbQH3bhTERvcGxlSkZFa2M/view?usp=sharing
Kernel: https://github.com/vampirefo/android_kernel_blu_kernel_x2 (Special thanks to @vampirefo for the kernel source)
Screenshots: comming soon
Changelog
Version: Testing
Build: 01072018211020
Initial release
Version: rc1
Build: 01142018205847
switched to stock theme
Version: 1.1.0
Build: 02182018215948
rebuild off of the 01/04/2018 update
Version: 1.1.1
Build: 02242018165134
fixed mobile data bug
Version: 1.1.2
Build: 03032018224915
changed DPI to 441
added stock calendar app
added stock calculator app
add stock clock app
Troubleshooting
reserved
Does quick charge work?
Been running for a couple of days now without issue.
cyrusharding said:
Does quick charge work?
Click to expand...
Click to collapse
Yes it works, I've beeen using 2 QC3 chargers with no problems at all.
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
cyrusharding said:
try "dogfood spotify" i had same issue and got that to work on the lineageos 13 blox2mini ROM.
Click to expand...
Click to collapse
Interesting, didn't know that exists. I currently just download off of http://download.spotify.com/android/SpotifyAndroid.apk
enduo said:
Awesome, works great so far. Here are a few things I noticed :
1- Keyboard didn't show up easily during setup, but eventually it became smooth
2- Following apps did not install (Package Helper error) : Fitbit & Spotify. Spotify was a known issue in stock rom but Fitbit was working fine in stock.
3- Netflix is not available. Previously I had LineageOS 13 and I was able to install Netflix. I know they banned uncertified devices, but I was still able to get it with that rom.
4- Fingerprint is not working 100%. I am able to unlock the device with it but apps are not able to use it properly. For example try Starbucks or any banking app. They will ask if you want to use fingerprint, you say yes and you put your finger, some apps crash, others will say fingerprint recognized, but then they don't actually store/use that fingerprint? Something must have gone wrong... LineageOS 13 also had this issue, but stock rom did not.
I would like to know if it's possible to not have the customizations you did for colors. Blue (pun not intended) hurts my eyes and transparency doesn't look great with some apps open. Also, if you go to device encryption, because you changed colors, some foreground and background colors are now identical and I wasn't able to read the options... I think that screen was the one for if I wanted to ask for password when the device boots.
Also do you have a git for the source tree? I'm learning to build Android and am hoping to see how you are doing things?
Thanks again and keep it up!
Click to expand...
Click to collapse
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
srgrusso said:
I'm doing my mods on the precompiled factory rom. If you go to the Lineage OS thread, Vampirefo has a link to the device and vendor tree he created for his rom. I am considering having two versions of my rom for the Mini. A light theme (stock) and dark theme the one that is out now. Right now the rom is only in testing stage. I enjoy seeing your interest in learning how to do what I am doing, the more developers the better.
Thanks for you feedback, here are some helpful links. I am a Linux user and my links may be geared toward Linux, some things can be done in Windows, but some require Linux.
Lineage OS for the Mini: https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814 (has links to his device and vendor tree)
How to compile an Android kernel: https://forum.xda-developers.com/le-2/how-to/guide-compiling-64-bit-android-kernel-t3512749 (I'm still trying to locate the Mini kernel source)
Tool to unpack and repack a rom: https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
tool for unpacking apks: https://ibotpeaches.github.io/Apktool/
I hope these help you and enjoy
Click to expand...
Click to collapse
This is awesome thanks so much!! I use Windows on a daily basis but I do have a pretty good knowledge about Linux and have set up a build environment in for Android. These links should help me understand what I am missing. I am also happy to continue testing and give you feedback on this ROM as it is currently my daily driver.
New Rom out. It has the stock theme, other than that it is the same.. I haven't decided if I'm going to build two Roms or have the theme be a patch. Maintaining all the different variants of the Rom are getting to be very time and space consuming.
https://www.androidfilehost.com/?fid=889964283620778170
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Requia77 said:
Strange question, but on the original stock rom, I started having issues with the Package Access Helper not working, while installing updates for Paypal, and just straight up trying to install Spotify, even the APK. I did a full factory reset, still did not work. I also installed the custom rom over at BLOX2.com, and the Package Access Helper still would stop working, even after clearing data/cache. I'm just curious if you know if your rom will fix that issue?
Click to expand...
Click to collapse
Is this without root? I don't know if my rom will fix that, I never used the Paypal app. Your welcome to try and let me know. Also there is LineageOS 13 for the mini which has been built from source.
https://forum.xda-developers.com/android/development/lineageos-13-life-one-x2-mini-t3692814
New rom rebuilt from the 01/04/2018 update.
v 1.1.0
There is a problem with the latest version of SRGX2. Mobile data doesn't work. I work on it this weekend and keep everyone updated.
Here is the fixed rom.
https://www.androidfilehost.com/?fid=818070582850494825
Good news I was able to get Android File Host to make the Life One X2 an official device. I have made a request for the Mini too. For now all the files will be under the Life One X2 device.
Updated rom: https://www.androidfilehost.com/?fid=673956719939824825
It includes the stock Calendar, Clock and Calculator apps. I changed the DPI to 441. Let me know if anyone has any problems with the Playstore. I know that there has been some requests for the stock Camera and file Manager apps. It's hard to please everybody so I added a patch section which may please some.
Code:
I am not responsible for anything that happens as a result of you using the ROM. Sure, i'm willing to help with bugs, but if you get fired because the Alarm app crashed, gremlins crawl out of your arse, thermonuclear war starts, or if your progress in Clash of Clans gets reset, i'm not the one to blame.
Features
Code:
microG and F-Droid pre-installed
Anything else LineageOS can do
Is not certified cancer-free in California
Stuff you need to actually use this
- Unlocked Bootloader (duh). Seriously, I will ignore you if you mention that you tried to boot this with Safestrap.
- Update TWRP to Android-7.1 builds located here. Please make sure to use the recovery image which is appropriate for your device (Thor or Apollo)
How do I actually install this?
- Backup existing ROM if you want. Or don't. I don't really care, truth be told.
- Wipe /data partition. You can keep media storage if you want, but I prefer to format it to make it SQUEAKY CLEAN
- Flash the .zip
- Do not flash OpenGapps. Or any Gapps. That defeats the purpose of microG.
- Flash any other crap you want. This'll probably Magisk.
- Reboot.
Downloads
AndroidFileHost: Thor, Apollo
Extra junk you might want
Magisk
Yalp Store (play store wrapper)
Flashable Standalone Google Play Store
Sources
I didn't make any of this. I just compiled and signed it. People smarter than me, like hashcode and ggow did, made this work on the HDX. Lots of other people made LineageOS and microG. Thanks to you all.
Phoenix Kernel
HDX-Common device tree
Thor device tree
Apollo device tree
Docker instance that I use to build this
How do I tell the NSA didn't tamper with my download?!
Luckily, I signed the builds with my own key!
Code:
$ keytool -list -printcert -jarfile lineage-14.1-20180613-UNOFFICIAL-thor.zip
Signature:
Owner: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Issuer: [email protected], CN=steamport, OU=steamport, O=steamport, C=US
Serial number: b1b3cdcf593b5030
Valid from: Tue Jun 12 20:49:48 EDT 2018 until: Sat Oct 28 20:49:48 EDT 2045
Certificate fingerprints:
MD5: 13:E0:38:54:47:CC:FA:B8:24:50:16:6D:41:90:C7:4F
SHA1: 5F:AD:C9:4B:43:D3:1E:C3:6B:5F:86:DE:6A:F6:C7:F8:72:CB:B7:04
SHA256: BB:A1:BB:0F:7B:E1:62:2D:87:27:FE:EC:C5:CA:C6:B7:E3:EA:1A:CB:32:33:7E:F4:2C:D6:BC:BC:6E:46:27:CC
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
XDA:DevDB Information
LineageOS for microG, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
steamport
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader, TWRP
Based On: LineageOS
Version Information
Status: Testing
Created 2018-06-13
Last Updated 2018-06-22
so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.
locolyric said:
so confuse about microg. there are some games we must live with google play or the games can't run.
but micro g are great for user who not play games rely on google play.
Click to expand...
Click to collapse
What is there to be confused about? Yes, Google Play Games doesn't work with microG yet. Just don't play with games that mine your data. Problem solved. Or just try to lubricate it with cat piss. I don't care.
Stupid Question: does this support LTE?
CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.
CCF_100 said:
Stupid Question: does this support LTE?
Click to expand...
Click to collapse
steamport said:
I don't think any Nougat ROM for thor or apollo supports LTE. Sadly, no.
Click to expand...
Click to collapse
Correct - only KitKat based custom ROMs support LTE (data only). FireOS 4.5.x is the best choice for voice and mobile data support.
New zips are out. I just updated microG's GMSCore to one I built myself based on master and a fix PR. Also pulled from latest Lineage 14.1 sources.
Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..
NeverSmile said:
Bluetooth issue ? I still use kitkat because i can use bluetoooth. But so boring ..
Click to expand...
Click to collapse
Likely won't be any different with this ROM as core issue resides at the kernel level. Inconsistent connection behavior leads to erroneous claims based on individual experiences but really not ROM related other than the binary KitKat (Android 4.4.x) or above checkpoint.
Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.
kfhdxuser said:
Firstly this is an amazing ROM! Well done to you and the team! However, the recent Apollo release is broken. Not sure about the Thor version, i would check but the device I bricked because I was messing around... Anyway it boots successfully but the screen is blank and is still turned on, no boot animation other than the generic grey kindle fire. I can still tap the screen and hear android feedback noises after waiting awhile so it works! Just I cant see anything :laugh: The previous release worked fine, no problems! Maybe you could keep the recent previous releases available for download for backups in case? Thanks again
Edit: Obviously I have the bootloader unlocked etc. Using latest TWRP if that helps at all.
Click to expand...
Click to collapse
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link
Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.
kfhdxuser said:
Been trying for about an hour now all i'm getting is feedback noises, is the confirmation dialog being prevented due to the setup process if there is one? Cant seem to get out of it and ADB keeps saying the device is unauthorized. I'll keep trying on the OS and once i get anything i'll update you as soon as i can.
Click to expand...
Click to collapse
I've seen the dialog pop up as soon as it finishes booting
Done!
steamport said:
I've seen the dialog pop up as soon as it finishes booting
Click to expand...
Click to collapse
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur
kfhdxuser said:
Okay i've got a log file after a few unsuccessful attempts, i'm not sure why the code you gave me did not work but I tried myself using "adb shell adb logcat -d > Lineage14.1.txt" and that seemed to do the trick. (Hopefully this is what you were after).
I tried to upload this to pastebin but it refused so i've uploaded it to an alternative website here: https://paste.ee/p/kL4Ur
Click to expand...
Click to collapse
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?
steamport said:
Thanks.... this is a weird log. It mentions turning the screen on several times? Can you try fully wiping system and reinstalling?
Click to expand...
Click to collapse
Yep i'll do that, was it the method that I used to extract the log file that could be the culprit? I should probably mention that you can see the screen when it turns off and on its just a different shade of black indicating that the screen works but it just won't display anything if that makes sense. I'll do a complete wipe and start again to see if its any different this time around.
Edit: Here is the new log: https://paste.ee/p/VK4oS
^^^
I've noticed it is considerably smaller this time around so hopefully this a good sign haha.
It is weird how the previous release worked and this one doesn't, i'd assume it's an application interfering from the latest build but if it works on Thor then it mustn't be right? Maybe something was accidentally changed for the Apollo release somewhere. Sorry if my ramblings aren't useful
Thanks @steamport! What is the security patch level on this build?
NextDroid said:
Thanks @steamport! What is the security patch level on this build?
Click to expand...
Click to collapse
Whatever the latest for 14.1 was as of 6/7/18?
steamport said:
Whatever the latest for 14.1 was as of 6/7/18?
Click to expand...
Click to collapse
Well, that depends, as the last AEX build, for example, was still on May 5.
Tapatalk を使用して私の LG-RS988 から送信
steamport said:
I don't have an apollo, so can you do some debugging for me? ADB into it. It'll ask for authorization on the screen, just guess where the OK button is til it works. Anyways, when you do get adb auth, run this:
Code:
adb shell
logcat > log.txt
exit
adb pull log.txt
, then put the log.txt on pastebin and give me the link
Click to expand...
Click to collapse
I've got the same problem. Loads but no screen and unable to find the "ok" to authorize the device. There must be a better way.
I will revert back to previous version until this is fixed.
EDIT 2018-1-10
Changed ROM download link from single file to folder structure.
The folder will include new builds for OPPO R7f
Latest build currently 09-14
First off this wouldn't be possible without mikeNG, TheMuppets, LineageOS team
I'm just the cook
Devices supported: R7f, ONLY
Do not flash this rom on any other R7 variants. It will brick the device
Device specific changes/fixes compared to previous release:
BUILD: 07-15
* Tape 2 Wake should be completely functional now!
* Updated Oreo source (OPM2.171026.006.H1)
* Various minor kernel & device specific changes (Check Github)
BUILD: 09-14
* Android security patch level updated (September)
* Updated Oreo source (OPM6.171019.030.K1)
* Various minor device specific updates (check git)
* Various minor LineageOS updates (check git)
* Not verified, battery lifetime seems a bit longer
How to install and all that kind of jazz please refer to my previous 15.1 thread
Updating from previous 15.1 release. Regular wipe in recovery is enough also wipe Dalvik & Cache
Downloads :
[ROM] Unofficial R7f LineageOS 15.1
Archive must be unpacked! Contains flash-able zip & md5 checksum
[Gapps -> ARM -> 8.1]
*Don't select the Aroma variant. TWRP doesn't like it
[TWRP Recovery for R7f] (twrp-3.2.2-0)
thank you. I am downloading and want to try it now.
Thanks again. It looks like it's time for me to try it as well.
P.s. please don't create a new thread for each release
Forage81 said:
Thanks again. It looks like it's time for me to try it as well.
P.s. please don't create a new thread for each release
Click to expand...
Click to collapse
I'll keep this as a rolling thread
PS. I wasn't unable to successfully build with Ubuntu
ParrotOS worked much easier and seems more stable as build environment
Wow this is great! thanks!
oh and would u be updating the build with the new lineageos features like true dark mode etc.?
ph03nae said:
oh and would u be updating the build with the new lineageos features like true dark mode etc.?
Click to expand...
Click to collapse
With the next (major) device specific changes and/or android changes I'll make another build which will include the newer LineageOS features
Guess within the next 1 ~ 2 Months you could expect another build from me.
In the meantime I'm taking a crash course on Android kernel development.
Would be nice to squeeze some extra juice out of this device.
JJRT said:
With the next (major) device specific changes and/or android changes I'll make another build which will include the newer LineageOS features
Guess within the next 1 ~ 2 Months you could expect another build from me.
In the meantime I'm taking a crash course on Android kernel development.
Would be nice to squeeze some extra juice out of this device.
Click to expand...
Click to collapse
Alright! Will be looking forward to the next release! (oh and btw is it possible to shift the power menu from the right to the left since the power button is on the left?)
ph03nae said:
Alright! Will be looking forward to the next release! (oh and btw is it possible to shift the power menu from the right to the left since the power button is on the left?)
Click to expand...
Click to collapse
You'll have to do that yourself
I want to keep this ROM a pure LineageOS source no modified frameworks
Try Xposed with NeoPowerMenu module, think it's able to do the trick
@JJRT,
Thank you very much for 'cooking' this ROM! On vacation I discovered that GPS did not work on that old 7.1.2 version. Now again works perfectly fine with this ROM!
I have one small problem though. Android indicates that my SD card is corrupted and want to fix it by 'configuring' it.
1) Does anyone know if it is actually going to try to fix it or will it just reformat it?
Obviously I do not want the latter. I would rather remove it from the phone and repair it in my PC.
2) Can I 'hot swap' the SIM/SD tray or do I really need to turn off the phone? The latter will most likely cause the phone to go into boot loop.
Thanks in advance for any help or info.
eximiusnl said:
@JJRT,
Thank you very much for 'cooking' this ROM! On vacation I discovered that GPS did not work on that old 7.1.2 version. Now again works perfectly fine with this ROM!
I have one small problem though. Android indicates that my SD card is corrupted and want to fix it by 'configuring' it.
1) Does anyone know if it is actually going to try to fix it or will it just reformat it?
Obviously I do not want the latter. I would rather remove it from the phone and repair it in my PC.
2) Can I 'hot swap' the SIM/SD tray or do I really need to turn off the phone? The latter will most likely cause the phone to go into boot loop.
Thanks in advance for any help or info.
Click to expand...
Click to collapse
Likely partition filesystem issues/corruption.
Preferable to do this with a SDcard-reader
Under Linux I'd suggest using Gparted to check/change filesystem and/or format
Under Windows Paragon Partition Manager™ Would do the job splendidly. Even ext4 / exfat layouts
And yes you could hotswap with phone still on, but I wouldn't recommend doing so out of precaution
I notice the following issues with this ROM:
1) Battery life noticeably less than the 'old' 7.1.2 (of 23-8-17).
2) Notifications arrive 20 to 30 minutes late.
3) In the about it says "Playform: msm8916", which is a 4 core Snapdragon 410. However, the R7f contains MSM8939, which is an 8 core Snapdragon 615. Does this mean only 4 cores are used?
eximiusnl said:
I notice the following issues with this ROM:
1) Battery life noticeably less than the 'old' 7.1.2 (of 23-8-17).
2) Notifications arrive 20 to 30 minutes late.
3) In the about it says "Playform: msm8916", which is a 4 core Snapdragon 410. However, the R7f contains MSM8939, which is an 8 core Snapdragon 615. Does this mean only 4 cores are used?
Click to expand...
Click to collapse
1: I do notice a bit, not dramatically
Concerning battery , did you do a clean install? (format data / cache / system) coming from 14.1 it's advisable to do so
2: Not having those issues (WiFi and 3G) Whatsapp/gmail/youtube notifications are near instant. Have more info?
3: Yeah not sure what the deal is with that. While building the rom it does use the msm8939 sources from LineageOS/TheMuppets
But indeed the info screen of 'Model & Hardware' Does report msm8916. Shall look into that (Guess it's just a left over from a initial script source they've used)
Other diagnostic software does identify it correctly and the performance is on par with 8939
JJRT said:
1: Concerning battery , did you do a clean install?
Click to expand...
Click to collapse
Yes, I did a complete wipe.
JJRT said:
2: Not having those issues (WiFi and 3G) Whatsapp/gmail/youtube notifications are near instant. Have more info?
Click to expand...
Click to collapse
Notifications usually get in when I click the button on the left side to unlock the phone or after a certain time (20-30 minutes). So it seems it does not work instant when the phone is locked.
I also notice that I only get notifications from email, sms and whatsapp. I checked the settings and notifications are enabled for all apps, but I do not get any notifcations from any other apps.
eximiusnl said:
Yes, I did a complete wipe.
Click to expand...
Click to collapse
Try getting some stats about what is eating your battery in the battery usage section of the settings or an app like BetterBatteryStats.
With the 14.1 lineageOS release I sometimes have/had that sensor use went nuts for a long period of time, draining battery as a result.
eximiusnl said:
Notifications usually get in when I click the button on the left side to unlock the phone or after a certain time (20-30 minutes). So it seems it does not work instant when the phone is locked.
I also notice that I only get notifications from email, sms and whatsapp. I checked the settings and notifications are enabled for all apps, but I do not get any notifcations from any other apps.
Click to expand...
Click to collapse
Can it be that this only happens when you are connected to WiFi? If yes, verify the WiFi settings to make sure remains connected or if it's not doing something else undesirable.
is it possible to activate camera2api and install google camera? Los 15.1
Ravhinzy said:
is it possible to activate camera2api and install google camera? Los 15.1
Click to expand...
Click to collapse
Currently no, camera firmware restriction
Might become possible if someone manages to update the sources, but I wouldn't count on it
JJRT said:
Currently no, camera firmware restriction
Might become possible if someone manages to update the sources, but I wouldn't count on it
Click to expand...
Click to collapse
Just curious, who would be able to update the sources/what needs to done to update the sources?
I solved the problem with the notifications of Whatsapp. The trick is to disable battery optimization for Whatsapp. Of course this is even worse for the battery life. I find it interesting that Android 8 has measures to save battery, but ends up using much more battery than 7.1.2.
This does not help for the apps that do not give any notifications at all. Maybe there is something changed in the way Android 8 handles notifications? I did read some comments from one app maker that they had updated their app to make notifications work on Android 8.1.
ph03nae said:
Just curious, who would be able to update the sources/what needs to done to update the sources?
Click to expand...
Click to collapse
Someone with low-level hardware/firmware/kernel knowledge
What exactly needs to be changed in order to make it compliant, I don't have a clue. It's over my head
I'm not a fan of Android 12's Material You, i.e. dull color schemes, ginormous headers and copious amounts of whitespace. Screens got bigger over time, but information density is getting lower and lower. It's crazy. Anyway, I'll spare you the rant.
As the LineageOS project stopped publishing builds for LineageOS 18.1, but they continue to patch their 18.1-branch with Android's monthly security updates, I decided to start building it myself following the instructions here.
You can download the builds here:
LineageOS 18.1 for Pixel 4a (sunfish) - Browse Files at SourceForge.net
Unofficial builds for those who wish to stay on 18.1 a bit longer.
sourceforge.net
I usually publish an update every month.
Additional tweaks
Default maximum lockscreen password length of 64 characters (instead of 16) [more info]
FirmwareIt's probably best to run the latest Android 11 firmware, since this is Android 11. You can download the last official Android 11 factory image from Google and flash it from fastboot mode (your data will be erased).
Clean install
Download the latest lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img and lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip from aforementioned link
Boot to bootloader a.k.a. fastboot
Flash the boot image with this command (replace filename with actual filename):
fastboot flash boot lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish-boot.img
Boot to recovery
Factory reset > Format data/factory reset > confirm (your data will be erased)
Apply update > Apply from ADB
Sideload the ROM with this command (replace filename with actual filename):
adb sideload lineage-18.1-xxxxxxxx-UNOFFICIAL-sunfish.zip
(If it asks "Signature verification failed. Install anyway?" answer Yes)
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
Reboot system now
UpdatingUpdates are delivered through the built-in updater (Settings > System > Updater).
If you use Magisk, deny the Updater's request to reboot at the end of the update process, open Magisk, tap Install and then "Install to Inactive Slot (After OTA)". Tap reboot after the process completes.
Migrating from last official LineageOS 18.1 buildSo it turns out builds are signed with a secret cryptographic key and when you install an update it has to have the same cryptographic signature or bad things will happen. This means you can't directly update from the last official build (signed by the LineageOS team) to my build (signed by me).
The solution: build and install (as an update a.k.a. dirty flash) a so called "migration build", which "resets the keys on all packages at every boot." I guess after booting into this build once, you can just update to the regular build using the updater (the LineageOS wiki is very concise on this topic and doesn't explain much).
You can download the migration build and boot image from the aforementioned link, they are marked MIGRATION instead of UNOFFICIAL. Don't run this build any longer than necessary, it's a security risk by its very nature.
When I tried this migration, my system wouldn't boot (stuck on boot logo). ADB worked and I could see in dmesg or logcat that, among other errors, SystemUI failed to start. Was it because I didn't reflash Gapps? But I never reflashed Gapps when using LineageOS' builtin updater...
Later I did some testing. I did a clean install of the latest official build, then my migration build, then my normal build, all was fine. Then I did a clean install of the latest official build WITH Gapps, then flashed the migration build WITHOUT Gapps, and the system booted up just fine. Huh? Then I flashed my normal build DIRECTLY over the latest official build, without migration build in between, and all was STILL FINE! So uhm... what's happening, how does this signing work and when does it become a problem? I have no clue.
If you decide to try the migration route, make sure to backup any data you don't want to lose and let us know how it went!
AcknowledgementsThanks to the original maintainers PeterCxy, cdesai and mikeioannina for bringing LineageOS 18.1 to the Pixel 4a!
Source code
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
GcamYou can just install it from the Play Store. There are a few bugs:
In photo mode, slide up to record video doesn't work
Motion Photos doesn't work
It doesn't scan QR codes without Google Lens
App versions without Material YouIf, like me, you try to avoid Material You like the plague, here's a list of the last versions of Google apps that I use(d) that don't have Material You. Note that LineageOS includes its own versions of some of them and all of them are optional anyway. You can find them on e.g. APKMirror.
Calculator 7.8
Calendar 2021.35.3
Camera 8.2.400
Clock 6.4.1
Contacts 3.49.2
Gboard 10.8.05
Maps 10.80.1
Phone 68.0.3
Photos 5.58.0
Translate 6.24.0.02
Is it wise to run older software? You decide. In an ideal world security updates and bug fixes would be separate from UI and "we decided you don't need this functionality so we removed it" updates. I've long ago stopped regularly updating my apps (i.e. turned off automatic updates) because I like to be able to trust my device will look & work the same tomorrow as it did today.
P.S. After you've installed the regular 20220815 build, the updater will keep showing an August 16 update which is actually the build you're already running. This is because I had to move the timestamp one day forward in order to enable updating from the MIGRATION build, which was also build on 20220815 and wouldn't see the regular 20220815 build as an update otherwise. This will be remedied with the next update I publish.
The September update is now live.
Does banking app works?
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
icantlogin said:
My bank's app has always worked fine on LineageOS. Your bank's hasn't?
Click to expand...
Click to collapse
I had never tried this rom want to try if bank apps works out of box
icantlogin said:
The September update is now live.
Click to expand...
Click to collapse
Been using this for several days now without a hiccup , fast ,,smooth, and google proofed, Thanks!!
Thanks for keeping LOS 18.1 alive with these security updates. I recently upgraded to 19.1 to try it out for a few months but I just couldn't get used to or appreciate the new UI. With every app update they also make it more like A12 and it just wasn't working for me.
Just installed your September update and all is well so far.
The October update is live!
A little background: I'm building this ROM on a Google Cloud Compute Engine instance, which is a virtual computer (also called virtual machine or VM) running in a Google data center. To keep the VM around is very costly, as it uses 300 GB of SSD storage which doesn't come cheap. So I create a new VM every month and dismantle it afterwards. This means I have to set up the build environment from scratch every time, which consists of a lot of steps. So from the beginning, I've put most of those steps in a Bash shell script (the VM runs Ubuntu 20.04) to speed things up drastically.
Last week I added some code that generates the updater.json file (that's read by your phone when it checks for updates) which I had been creating by hand before. I also added code to automatically upload the build to SourceForge. So yesterday all I had to do was create the VM, upload the script and run it. Six hours later, your phone was able to download the update without any further intervention on my part.
What can I say, the geek in me is very happy
Hi, I thank you for your work. Would you know if I can install microg without magisk, maybe via nanodroid or similar while maintaining OTA updates?
I have no experience with that. I assume you would have to apply the signature spoofing patch and install microG before booting from the updated system partition. So after installing the OTA update boot into recovery and do this?
Hello ! How to you push the google apps on this one ?
I'd like to get a pico gapp installed to get some game running
It's in the instructions in the first post, after flashing the ROM:
Optionally flash Gapps or anything else:
Advanced > Reboot to recovery
Run adb sideload with your zip
I'm using NikGapps Core myself.
This only works if you do it before first boot by the way, as far as I know you can't put Gapps on an installation you're already using.
Hi! Do you know if this will retain microg if I dirty-flash it on top of a lineage.microg.org build (the last official release) using your MIGRATION build? If you're not sure I'll back up my stuff and give it a shot and report back Thanks a lot for your your work!
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
icantlogin said:
Well... I don't think that would work, since this ROM doesn't include microg and the needed signature spoofing, so my guess would be you'll just loose that—if the migration works at all. Let me know what your findings are though!
Click to expand...
Click to collapse
Here is what I found, in case it helps someone: flashing the migrate ROM and then the latest proper ROM works perfectly, however I did lose microg, system f-droid, etc, and anything which is in the lineage.microg.org build but not in this one.
Now since you are building monthly ROMs, would you consider applying the signature spoofing patch to your builds? This would make it easy for those who want to run microg instead of google play framework/gapps. As far as I understand it you just need to apply this patch with `cd android_frameworks_base; patch -p1 -i /path/to/android_frameworks_base-R.patch`. Thanks again for your efforts
I'm open to consider this, but as I somewhat but not fully grasp the security implications of enabling signature spoofing, and not everyone might want to have this enabled by default, it would have to be a toggle in Developer Options and disabled by default, or I would produce a separate build with the patch applied.
If you could find a patch for me that implements the toggle in Developer Options, that would be great. As I researched it a bit I read that some ROMs have this.
Interesting that the migration worked, by the way!
Some more thoughts on this: it seems with signature spoofing enabled on the ROM, an app still has to ask for the permission to spoof its signature, so for advanced users like us who know what we're doing, I guess that's good enough. I'll have to read up on this a bit more though. I know the LineageOS devs are against implementing it but most everyone else says it's actually not that big of a security risk.
I just reply to show you my gratitude for maintain LoS 18. I updated to 19 two weeks ago and I was literally suffering with the system theme. IDK what they were thinking but it was terrible. Also for me, on 4a, was having lag: An example is when I shuffle songs on Musicolet, they take a good while to update the information (song name, basically) while with 18 it updates as soon as I press next.
BTW, can you recommend me a good KERNEL? Thanks!