Related
Here are the most important changes between krt16o and krt16s:
Fix (e41ab11) of a critical bug related to encrypted disks. The passphrase entered by users after a prompt (4.4 uses a more secure encryption mechanism) was not verified if correct. Thus user data could become corrupted. This issue could only affect users upgrading from 4.3 and with encrypted disks.
The backup service now has registration occurring dynamically. (c46c4a6)
Fixed issues with 2012 GSM Nexus 7 radio.
The Nexus 4 received a new prebuilt kernel (6a0177d) with an updated WLAN driver and a few tweaks to the APNs for several carriers (753ddc7, 59e4a0c, 0af7ccb, 962c235).
Source http://www.androidpolice.com/2013/1...-bug-in-full-disk-encryption-explains-hotfix/
Sent from my Nexus 4 using Tapatalk
Double post...
I AM VERY SORRY, I THINK I AM IN THE WRONG FORUM!
Hi Guys, has anyone rooted the latest Asus Zenfone 4 Lollipop? The new OTA can be downloaded from here
http://www.asus.com/ph/supportonly/ASUS ZenFone 4/HelpDesk_Download/
Thanks in advance.
BTW. more details
Version WW_7.3.3 (Android L)
ASUS ZenFone4(T00I) software Image: V7.3.3 (Android L) for WW only*
Note1: Please make sure update software version V6.6.3 first before update to software version V7.3.3
Note2: Download the OTA file and put the file to the device root directory directly.
Please note! The listed apps below will be removed once the
Android 5.0 Lollipop upgrade is complete.
1. Battery Widget
2. Google Text-To-Speech
3. Movie Studio
Please notice that below new apps will be added in this system upgrade.
1. TripAdvisor
2. Gameloft
3. CleanMaster
4. Zinio
5. ASUS Auto-start Service Manager:
Prevent unwanted apps from automatically starting up and using RAM
Stop services immediately and prevent Android from restarting these apps again
6. ASUS Support
Add Assistance in ASUS Help
Support bug reporting mechanism?
Enable Push notification service
Add unread count badge
Add new item reminders for articles
Support Google Analytics mechanism
Please notice that some feature changes in this system upgrade.
1. Lockscreen: remove standalone wallpaper & weather info
2. Dialer/Contacts: reduce tab count from 5 to 3; remove group tab name/photo
3. InCall screen: remove inCall animation & cover
4. Quick settings/Recent app layout change
Steps of Update:
1.Check software version of your device**
2.Download device software and Update SOP (From “Manual” Item)
3.Only apply to same SKU update, Example: WW->WW, CN->CN, TW->TW.
4.Software update cannot transfer the software SKU and downgrade the software version.
5.Wrong SKU may cause update failure, please update the same SKU version only.
*How to know the device model?
Path: Settings->About-> Model number
Example: ASUS_T00I
**How to know the device software version?
Path: Settings->About-> software information->Build number
***System upgrade may cause part of data missing, please buckup your important data before system upgrading.
Root not working
Root not working, error during update install.
Subhajitdas298 said:
Root not working, error during update install.
Click to expand...
Click to collapse
Sorry dude... I do not have root myself just yet. Let's wait for other to share root..
Asus Zenfone 4 lollipop can be easily rooted using temporary cwm session for intel device method. T2 method works fine. I have tried this and it works fine.
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Hello,
are you able to understand if the filesystem is encrypted?
Best regards,
If FS is encrypted, you will have to provide a password in order to boot the phone. Without that password, phone cannot read the "disk".
Sent from my VTR-L09 using Tapatalk
I am afraid this does not need to be true anymore...:
Android 7 should come with File Based encryption in contrast to the android versions before...used exactly with the same reasoning (you cannot boot otherwise).
(https://source.android.com/security/encryption/file-based#enabling-file-based-encryption)
Does anybody know more?
Just bought this phone as I expected all Android 7 phones to be encrypted....would be curious to know!
To further add information/confusion here my today's tests:
- Moving the primary storage to SD card warns me that this (external) storage is not encrypted, while the internal storage is. Indicating the phone is encrypted.
- In AIDA64 you find the Device feature android.software.file_based_encryption. Indicating that the phone CAN do that, not sure if it DOES.
- Using the app Activity Launcher, you can start the (otherwise hidden) Encryption dialog. It attempts to reboot, but does nothing. Dialog shows it as un-encrypted though...
- In Settings you can search for options. If you search for " encr..." it will find the dialog "Convert to file encryption". However clicking on it does nothing.
- I could set up my companies exchange connection. This says it requires an encrypted 'application' storage. So some parts at least should be encrypted.
Oh, I am talking about the P10 lite. But I am sure, this also helps for the P10. If the lite has encryption, the P10 clearly should have.
This other thread seems to indicate that data is indeed encrypted on these phones.
https://forum.xda-developers.com/p10/help/twrp-strange-folder-names-crypted-t3615989
This because of force encryption in boot.img it can be disabled by flashing a zip which removes dm-varity and force encryption from boot.img
Hi,
this thread aims at keeping the LineageOS 13.0 version alive for the Moto G 2015 (osprey) device with current security patches from LineageOS (branch 'cm-13.0'). The build here has already a history in this thread on XDA - it may be worth to scroll through it to find additional information.
The build has got the following features:
LineageOS 13 with current security patches
Patched for microG (see https://microg.org, signature spoofing as switchable permission)
Squid kernel for the Osprey device (own fork)
LineageOS Jelly Browser
Current Android System Webview
CMUpdater is not part of this build
Renewed CA-certificates from AOSP master branch
VoLTE (may not work in all cases!)
Current build data
Download here
AOSP tag android-6.0.1_r81
Security string 2018-06-01
Android System Webview on M66 (stable, taken from LineageOS 14.1)
Contains the fix for the KRACK attack against WPA2
Root access included (can be switched on/off in developer settings)
Unofficial microG-build as 2nd build variant
Download here
Hardened build with pre-installed microG apps. For more information, see https://lineage.microg.org/
(This is an unofficial build for LineageOS 13 f. osprey based on the work described on the project page)
Different from the 1st build, the following features apply, everything else is the same:
No root available (can be flashed separately)
Pre-installed microG apps (see lineage.microg.org page)
SQLite 'secure delete' feature enabled
Access to /proc/net blocked for user apps
Enhanced Privacy Guard (1): Switches for motion sensors and other sensors available
Enhanced Privacy Guard (2): Switches for read phone state and storage (read/write) available
Oreo backport: SET_TIME_ZONE permission restricted to system apps
Oreo backport: Access to timers in /proc restricted
Cloudflare DNS (1.1.1.1) as default fallback
Privacy-preferring default settings
Source Code links
LineageOS: https://github.com/LineageOS
Kernel: https://github.com/MSe1969/android_kernel_motorola_msm8916/tree/mse_cm13
microG patch: https://github.com/microg/android_p...aster/patches/android_frameworks_base-M.patch
microG-Build: https://github.com/lineageos4microg
local manifest: https://github.com/cm13-microG/local_manifests
hardening features: see reserved post further below
Installation instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G 2015 (osprey) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume key to the reboot recovery option and select with power key)
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
Download the most current .ZIP file of this ROM and place it to your phone's internal memory or SD card
If you wish to install Google apps (GApps), please refer to the GApps section further below
An unlocked bootloader (read the warnings carefully and backup your data!
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it.
However - I recommend to use the TWRP recovery linked here. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (see above) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped.
Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
GApps
The following instructions only apply for the 1st variant, do not flash Gapps over the "microG build":
You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device.
Choose ARM as platform, Android 6.0 and the flavor of your choice. I recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for. The 'microG patch' in this ROM has no negative impact on installing Gapps.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd).
Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe.
If you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process.
(Note: If you wish to get rid of GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps. When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 13.0 - be patient, the first boot after flashing a new ROM takes quite long!
microG Installation
These instructions apply to the 1st 'default' variant, not the 'microG build' (which has already microG installed)
The ROM is patched for the use of microG, but it does not contain the microG system components.
The best way to obtain them is to include the microG repository into the F-Droid store as described on the microG Download page, where you will also find links for the direct download of the .apk files.
Please refer to the official installation instructions. However, there are three pieces of information, which are explained on the microG pages, but unfortunately not directly in the installation instructions, so I would like to point them out here:
Download the 'unstable' Gms Core version 0.2.4-105-... to avoid "outdated play services" warnings
The Location Provider functionality is included in Gms Core, but also available as separate application. I recommend Gms Core - however, the explanation is not included in Gms Core, but only here
To grant the signature spoofing permission, go to Settings - Apps - Advanced (the 'gear' icon) - App Permissions - Spoof package signature; it is not possible when you enter the individual app's permissions menu
Credits
Android Open Source project (AOSP)
LineageOS project
squid2 (Kernel)
microG project
XDA:DevDB Information
Osprey LineageOS 13 with microG patch, ROM for the Moto G 2015
Contributors
MSe1969
Source Code: https://github.com/cm13-microG/local_manifests
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Testing
Created 2017-10-23
Last Updated 2018-07-24
Change Log
June 20th, 2018
Announcement to discontinue the cm-13.0 builds - please visit my Lineage OS 14.1 microG thread, which continues with LineageOS 14.1
June 10th, 2018
Security string 2018-06-01
May 22nd, 2018
Security string 2018-05-01
Android System Webview M66
Cloudflare DNS as default (instead of Google)
Privacy-preferred default settings
Kernel fix for in-call sound issue
April 11th/12th, 2018
Security string 2018-04-01
Android System Webview M65
March 16th/17th, 2018
Security string 2018-03-01
Squid Kernel r22c (Oreo)
Renewed CA certificates from AOSP master branch
Bugfix of date/time reset on reboot, when no carrier sync
Bugfix in microG build: Always skip GMS page in SetupWizard
February 19th, 2018
Update after ASB merge in LineageOS 13.0
Webview now on stable M64
February 10th, 2018
Security string 2018-02-01
Squid Kernel r22c (Oreo)
Privacy Guard enhancements
Further security hardening in 2nd "microG build" variant
January 16th, 2018
Security string 2018-01-01
Squid Kernel r22 (Oreo)
System Webview switched back to M63-stable
2nd build variant "unofficial microG build"
December 21st, 2017
Security string 2017-12-01
Squid Kernel r21 (Oreo) forked
Recent Jelly build
Android System Webview 64.0.3282.30 (beta)
November 24th, 2017
Security string 2017-11-01
Squid Kernel (Nougat) forked and merged 3.10.108 updates from kernel.org
October 23rd, 2017
Fix of KRACK attacks
Security string 2017-10-01
AOSP tag 6.0.1_r81
Android System Webview updated to M64
Squid Kernel (Nougat)
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Historical entries from this thread:
September 21st, 2017
Security string 2017-09-01
AOSP tag 6.0.1_r80
Jelly updates
Fix of 'Blueborne' attack (part of Sept. security patches)
September 2nd, 2017
Security string 2017-08-01
Android System Webview updated to M60
July 14th, 2017
Security string 2017-07-01
June 14th, 2017
Security string 2017-06-01
Android System Webview updated to M59
May 28th, 2017
Replaced Gello with new LineageOS Jelly Browser
Android System Webview updated to M58
May 26th, 2017
Security string 2017-05-01
April 17th, 2017
Security string 2017-04-01
AOSP tag 6.0.1_r79
March 24th, 2017
Security string 2017-03-01
Included Kernel from cm-14.1 branch to regularly receive sec. patches
March 13th, 2017
Security string 2017-02-01
February 21st, 2017
Security string 2017-01-01
Rebranded LineageOS
Security Hardening (microG build)
Details about additional security hardening in the "microG build"
1. SQLite 'Secure Delete' feature
This sanitizes deleted data by overwriting it with zeroes, rather than having it persist within SQLite's free list.
Backport from Oreo, see https://android-review.googlesource.com/q/topic:"secure_delete"
2. Restrict SET_TIME_ZONE permission to system apps
Backport from Oreo, see here
3. Enhanced Privacy Guard (1) - Sensor permission switches
An own sensor template to control access to motion sensors (ask mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard. Commits: (1), (2), (3)
4. Enhanced Privacy Guard (2) - Switches for 'Read phone state' and 'Storage'
The existing AppOps to read the phone's IMEI and to control access to the SD card have been made accessible.
This is a cherry-pick of the proposed LineageOS change here
5. Restrict access to /proc/net for user apps
An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. This is the main commit. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitorhas been bundled
6. Access to timing information in /proc restricted
To prevent side-channel attacks as described here, the respective Oreo patch has been back-ported.
7. Cloudflare (instead of Google) default DNS
Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)
8. Privacy-preferred default settings
When newly installed, the below settings are defaulted, different from standard LineageOS 14.1 (all setting can be changed at any time later):
Privacy Guard is enabled on install (proposal during Setup)
Anonymous LineageOS statistics disabled (proposal during Setup)
The standard browsing app does not get the location runtime permission automatically assigned
Sweet..
Nice. Good to see this as separate post.
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
shadowbone said:
Every time the ambient display lights up the screen, it is in on a high brightness mode. And the moment I tap, it gets back to normal brightness. I know this could be a cm13 issue but, any way to resolve this ?
Click to expand...
Click to collapse
I haven't observed this behavior on my device, can you provide some more details?
MSe1969 said:
I haven't observed this behavior on my device, can you provide some more details?
Click to expand...
Click to collapse
It isn't that big a difference but perhaps I could provide you a log, if that could help.
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Thanks - will have a look later
MSe1969 said:
Thanks - will have a look later
Click to expand...
Click to collapse
Sure thing.
Also, is this volte supported or should I flash the volte patch ? Because I can't seem to get it work. I am on the latest build.
VoLTE
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
MSe1969 said:
As you can see in the old thread, there have been some discussions about VoLTE support (and also some attempts from my side to get it running).
Let me quickly summarize:
I have tried the VoLTE patch(es) from XDA - VoLTE menu was there but no VoLTE calls on my phone
I have tried to create a test build with the contents of those patches and also looked at what was done in cm-14.1 - same result: menu there, but no VoLTE calls (LTE symbol disappears when calling)
Got mixed feedbacks from people using the test build - works well for the ones and does not work or stops working after reboot for others . . .
LineageOS 14.1 is supposed to have VoLTE support f. osprey - same story, not on my phone (menu entry there, but *#*#4636#*#* menu and IMS status there tells VoLTE not available - tested with SIM cards from different carriers)
So I'm having trouble to get it working on my device (XT1541 16GB) at all. On my repo's at github, the msm8916 device and vendor tree have two volte branches for testing.
Any insight, advice and/or build suggestions welcome
Click to expand...
Click to collapse
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Erick_Summer said:
dear user, could you tell me what application I can get this file (
File Type: txt 2017-10-25-14-38-27.txt), since I have some errors in the rom, thanks.
Click to expand...
Click to collapse
Well, if you meant taking a log, there are plenty. The one I used is 'matlog'. You can get it from playstore.
rahul9999 said:
You could get some help from this post.. check by integrating this patch. https://forum.xda-developers.com/2015-moto-g/themes-apps/osprey-volte-patch-android-n-roms-t3527635
Edit - post added
Click to expand...
Click to collapse
I used this post and its patches always as a base for my test builds. Tried now the most current MM patch , which was uploaded in October - same result, does not work on my device.
shadowbone said:
It isn't that big a difference but perhaps I could provide you a log, if that could help.
Click to expand...
Click to collapse
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
MSe1969 said:
Hi, haven't really noticed anything unusual in the log, I also use afwall and Xprivacy. Only noticed you use a battery app, but log does not indicate any issues... So I am afraid I can't really help, as I can't reproduce this behavior on my device.
Click to expand...
Click to collapse
Yeah, I use the betterbatterystats from xda. I guess I will try and do a dalvik cache clear and if possible do a clean rom flash in the near future and try again. Else, it must be some device specific issue.
Anyway thanks a lot for your time. I appreciate it.
My daily ROM, please update.
The best ROM tk!
kurapika7 said:
My daily ROM, please update.
The best ROM tk!
Click to expand...
Click to collapse
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
melp57 said:
This is marshmallow, correct. Why is it better than
Nugget?
Thanks for sharing!
Also, your experience with no Google services.
Click to expand...
Click to collapse
have a better use of ram
This thread is discontinued - LineageOS 17.1 (Android 10) definitely has reached the boundary, of what an old medium range device can handle. Therefore, I have decided to go back to LineageOS 16.0 (see below - I have re-opened the linked LineageOS 16.0 thread).
This thread is dedicated to provide hardened Lineage-OS 17.1 builds with microG included for the Motorola Moto G 2015 (Osprey) with current security patches.
You can consider this thread as a successor of my LineageOS 16.0 Osprey thread
Different from my 16.0 thread, I do not offer a "standard variant", as there is an official LineageOS 17.1 version available for the Osprey device.
Security hardened microG build
Download here
Build is signed
Pre-installed microG and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables
Current release levels
Security string: 2021-12-05
AOSP tag: 10.0.0_r41
Bromite Webview: M96
Source-code and build instructions
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8916/tree/lineage-17.1 (official LineageOS)
Build manifest: https://github.com/lin17-microG/local_manifests/tree/lin-17.1-microG
Installation Instructions
YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.
Pre-Requisites
Get familiar with the hardware keys of the Motorola Moto G 2015 (osprey) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume key to the reboot recovery option and select with power key)
Activate the Developer options (Settings, about phone: tap 7 times on the build number), get into the new menu Developer options and activate, if available, the option "OEM unlocking")
Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
Download the most current .ZIP file of this ROM and place it to your phone's internal memory or SD card
An unlocked bootloader (read the warnings carefully and backup your data!)
Install TWRP recovery
If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it. However - I recommend to use the official TWRP recovery from the TWRP site. The following instructions are based on TWRP.
To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
Code:
fastboot flash recovery TWRP.img
Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and use the right hardware keys to get into recovery mode) - I recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
Advanced Wipe
ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.
NO GApps!
DO NOT attempt to flash GApps on this build! This build is "Google-free" comes with pre-installed AuroraStore and microG.
If you absolutely want Gapps, download and flash the official LineageOS build for this device instead.
Install the ROM
In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd). Choose the .ZIP file of the ROM and swipe to flash. If you update from a previous version of the ROM, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into our Lineage OS 17.1 - be patient, the first boot after flashing a new ROM takes quite long!
microG
After the first installation of this ROM, you need to setup microG.
Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"
Dealing with signed builds
Please note, that my build is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash".
Bug reports:
If you have a problem please create a post with these information:
Original Kernel shipped with this rom:
Build Date:
And try to get log as described here
Credits
Android Open Source project (AOSP)
LineageOS project
althafvly
chil360
microG project
csagan5 (Bromite)
Whyorean (AuroraStore)
Change log
2021-12-18
ASB Security String 2021-12-01
Bromite System Webview and Browser updated to 96.0.4664.54
microG 0.22.214516-21
2021-11-13
ASB Security string 2021-11-05
Bromite System Webview and Browser updated to 94.0.4606.109
2021-10-11
ASB Security string 2021-10-05
Bromite System Webview and Browser updated to 93.0.4577.83
2021-09-12
ASB Security string 2021-09-05
microG 0.2.22.212658-2
2021-08-07
ASB Security string 2021-08-05
Bromite System Webview and Browser updated to 92.0.4515.134
F-Droid updated to 1.13
Fix in WiFi randomization
2021-07-10
ASB Security string 2021-07-05
Bromite System Webview and Browser updated to 91.0.4472.146
microG 0.2.21.212158-2
AuroraStore 4.0.7
2021-06-14
ASB Security string 2021-06-05
Bromite System Webview and Browser updated to 91.0.4472.102
microG 0.2.19211515-9
2021-05-11
ASB Security string 2021-05-05
Bromite System Webview and Browser updated to 90.0.4430.204
microG upstreamed (no version upgrade)
Update: AuroraServices 1.1.1
2021-04-13
ASB Security string 2021-04-01
Bromite System Webview and Browser updated to 90.0.4430.59
F-Droid updated to 1.12
Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
2021-03-08
Security string 2021-03-05
Bromite System webview updated to 88.0.4324.207
Bromite Browser updated to 88.0.4324.207
F-Droid 1.11
microG 0.2.18.204714
2021-02-15
Security string 2021-02-05
Bromite System webview updated to 88.0.4324.141
Bromite Browser updated to 88.0.4324.141
F-Droid 1.10-alpha-234
microG 0.2.17.204714-5
2021-01-15 - Initial build
Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)
Pre-installed AuroraStore
Bromite as default browser (87.0.4280.131)
eSpeak TTS engine (FOSS TTS solution)
Additional security hardening features listed below
Cloudflare as default DNS (instead of Google)
Privacy-preferred default settings
Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
Firewall UI (under Trust)
Increased max. password length of 64
No submission of IMSI/phone number to Google when GPS is in use
Default hosts file with many blocked ad/tracking sites
Privacy-enhanced Bromite SystemWebView (87.0.4280.131)
Extra control of sensor access for additionally installed user apps (Special access under app permissions)
Constified JNI method tables
Hello, I dirty flashed and for now everything seems fine ! Even maybe a little snappier.
I will report any problem.
Thank you for your work !
I did a clean flash (just to be on the safe side) and every works correctly. Thanks!
I would like to discuss an observation I made feeling wise since your previous version based on lineage 16.
First, some context, I started with your ROM on lineage os 14, then 16 and now 17.
In my opinion the 14 had the best feeling. Fast, reactive, even with a load of apps.
Since 16, I have no bug (and thats great !) but the device seems slow, often unresponsive.
I don't have many app running maybe firefox which is RAM eater but if I check this when it's slow it show no more than 1.4go in use on 2.
I was searching what may be the reason and I realize that the 14 had a custom kernel by Squid, one I happily used on other roms too.
Could this be an idea ? Others people feeling the same ?
nodens76 said:
I would like to discuss an observation I made feeling wise since your previous version based on lineage 16.
First, some context, I started with your ROM on lineage os 14, then 16 and now 17.
In my opinion the 14 had the best feeling. Fast, reactive, even with a load of apps.
Since 16, I have no bug (and thats great !) but the device seems slow, often unresponsive.
I don't have many app running maybe firefox which is RAM eater but if I check this when it's slow it show no more than 1.4go in use on 2.
I was searching what may be the reason and I realize that the 14 had a custom kernel by Squid, one I happily used on other roms too.
Could this be an idea ? Others people feeling the same ?
Click to expand...
Click to collapse
Admitting, that the Osprey isn't my primary device, I didn't feel like 16.0 was slow - I was heavily testing 16.0 beginning of the year (as at that time, a couple of things weren't yet working properly) and I had a good impression. As the move to 17.1 wasn't too difficult (I mainly worked with an emulator first to bring up my 17.1 hardened build, which itself indeed was a lot of work), I did not really create "heavy load" on my Osprey for 17.1 - I however don't have a bad impression about the phone's behavior.
Yes, 14.1 had the Squid kernel (which doesn't work on higher releases), which was an excellent piece of work. The 16.0 build also had a Custom kernel (Hybrid-X fork), whilst 17.1 uses the "regular" LineageOS kernel, but I have the impression, that it is still maintained.
I am however no "kernel tuner" and also not good at that. I usually try to apply sec. patches (for which many others do not seem to have the necessary patience), if I maintain the kernel fork myself, but I am neither good at adapting a kernel to a device, nor at general kernel tuning.
If you can point me to a nice Custom kernel for the Osprey, which I can fork and where I would simply have to pick sec. patches, I can give it a try - I could also try chil360's Hybrid-X kernel used for android 10.0 as a base and pick the sec. patches from my 16.0 kernel to see and have you guys judge as well, whether this leads to a better result. However - this is not my highest priority, especially not when I am short on spare time.
But curious to see other people's opinions first.
Yeah may be slow wasn't appropriate, but it feels sometimes a little sluggish. This is my primary device and I tend to have dozen of firefox tabs open so this could be my fault !
My question wasn't to ask you more work, it was more an open question to request reports or advices.
I had a look on the kernel available on osprey and it seems that there're not plenty. I saw that Squid's one hasn't been updated. Thanks for the Hybrid-X, pointer, I will look into that.
I discovered also android GO which should be helpful on low memory devices. With 2go, osprey is not really in this category but who knows. I had a rapid look and found somes scripts which required a flag enabled during compilation. Are you aware of this ? Would this be interesting to dig ?
Nothing related to development, but Ospery in title has a typo error. Just noticed so pointed out
nodens76 said:
First, some context, I started with your ROM on lineage os 14, then 16 and now 17.
In my opinion the 14 had the best feeling. Fast, reactive, even with a load of apps.
Click to expand...
Click to collapse
Official LOS17 has always been laggy for me on osprey. Some people still build LOS14 with monthly security patches for osprey last I checked. They said the hardware can't really handle newer versions of android that well so they stick to nougat. I tested both for like half an hour and I think 14 is better, but I still stuck to 17 because of the automatic LOS updater.
Ritik99 said:
Nothing related to development, but Ospery in title has a typo error. Just noticed so pointed out
Click to expand...
Click to collapse
Thanks for the hint - fixed
knpk13 said:
Official LOS17 has always been laggy for me on osprey. Some people still build LOS14 with monthly security patches for osprey last I checked. They said the hardware can't really handle newer versions of android that well so they stick to nougat. I tested both for like half an hour and I think 14 is better, but I still stuck to 17 because of the automatic LOS updater.
Click to expand...
Click to collapse
@nodens76 @knpk13 (and whoever volunteers as well) - would you like to test something?
I have currently no access to my Osprey device (again next Sunday only) to test myself, but I have created a boot.img based on chil360's Android 10 Osprey kernel (https://github.com/chil360/android_kernel_motorola_msm8916) here:
https://sourceforge.net/projects/lin17-microg/files/MIGRATION/osprey_chil360_10_boot.img/download
The image does not contain the latest patches, but it should give an impression, whether the device is maybe more reactive than using the "official" LineageOS kernel.
To test, please proceed as follows:
Step 1:
Test, whether it boots at all (as indicated, I have currently no access to my Osprey device) - reboot to bootloader and enter the command fastboot boot osprey_chil360_10_boot.img
Step 2:
If step 1 works, reboot to recovery and flash the boot.img via TWRP or from fastboot via the command
fastboot flash boot osprey_chil360_10_boot.img
To get back to the shipped kernel, extract the boot.img from the ROM zip and flash it as described above.
Please let me know, whether you see any difference. If the chil360 kernel is considered "better", I'll apply the latest patches and will ship my build with this kernel in future.
Looking forward to your feedbacks.
Thanks @MSe1969 , I will try and report back.
I also tried on my side some apps cleaning and more agrssive ram managment which were successful to some points.
Edit :
Step 1 : Ok for me ;
Step 2 : Ok, I will use it for the week-end and make a report on monday.
I used the custom kernel for the lasts 3 days and everything works fine. I played a little with the governors of cpu and gpu and I think that the ui seems a litlle less laggy althought there is still some case where It feel very slow (opening spotify and switching on the bluetooth for example).
It's not a revolution but I think that's a little improvment and some fine tuning in the kernel can save a little battery too. I would say "Keep it"
nodens76 said:
I used the custom kernel for the lasts 3 days and everything works fine. I played a little with the governors of cpu and gpu and I think that the ui seems a litlle less laggy althought there is still some case where It feel very slow (opening spotify and switching on the bluetooth for example).
It's not a revolution but I think that's a little improvment and some fine tuning in the kernel can save a little battery too. I would say "Keep it"
Click to expand...
Click to collapse
Thanks a lot for testing. Then I'll patch it and make it part of the next build. Do you have some advice which settings to tweak?
I found lionfish governor has a very good ratio reactivity/battery consumption.
For gpu, I'm not sure, I tried powersave as I don't play but anyway it add lags so ...
I switched i/o schedulers to zen but it's hard to quantify the gain.
Do you have a github to the kernel ? I should try to disect squid's one ...
nodens76 said:
I found lionfish governor has a very good ratio reactivity/battery consumption.
For gpu, I'm not sure, I tried powersave as I don't play but anyway it add lags so ...
I switched i/o schedulers to zen but it's hard to quantify the gain.
Do you have a github to the kernel ? I should try to disect squid's one ...
Click to expand...
Click to collapse
I directly fetched chil360's kernel, but I will fork it and pick all the patches from the 16.0 one, so you could the create some PR's or I could even grant you access if you want...
Thanks for the offer, I first need to build my first kernel ... I'm not new in linux things but never done an android build so I need some practice and first some tooling !
MSe1969 said:
@nodens76 @knpk13 (and whoever volunteers as well) - would you like to test something?
I have currently no access to my Osprey device (again next Sunday only) to test myself
Click to expand...
Click to collapse
Sorry, I currently don't have access to my osprey either. I've lent it to my grandmother.
Quick question: I'm coming from the stock rom, do I have to install Android 6 before I can install your ROM?
r3dd0t said:
Quick question: I'm coming from the stock rom, do I have to install Android 6 before I can install your ROM?
Click to expand...
Click to collapse
Shouldn't there be a Stock Android 6 version available? Does your Stock ROM offer you an update?
I am not 100% sure whether you would have to upgrade to Android 6 first, I had on my Ospreys already Android 6 Stock, when I first flashed LineageOS on them. But in general, it is always a good thing to update, if possible, to the latest offered Stock ROM version.