Related
Guys, we have pushed Remix OS 2.0.307 to your Remix Mini. Please feel free to share your experience with the rest of Remix Community.
Added feature: Activate/turn off factory set functions
Added feature: New keyboard shortkey Win+Shift to change physical layout of keys
Added feature: Addition of Remix Central as a preloaded application
Fixed: Issue with Citrix Receiver being unable to respond to mouse right-click
Fixed: Issue with Memory Clearing function ending all applications running
Fixed: Issue with closing Notifications list
Fixed: Issue with flashing Settings Menu
Fixed: Bugs & errors that resulted in system crashes resolved
Fixed: System tray message errors in English, French and Arabic now resolved
You can also find it here http://support.jide.com/hc/en-us/articles/218742278-Remix-OS-Update-2-0-307
RemixOS_Cameron said:
Guys, we have pushed Remix OS 2.0.307 to your Remix Mini. Please feel free to share your experience with the rest of Remix Community.
Added feature: Activate/turn off factory set functions
Added feature: New keyboard shortkey Win+Shift to change physical layout of keys
Added feature: Addition of Remix Central as a preloaded application
Fixed: Issue with Citrix Receiver being unable to respond to mouse right-click
Fixed: Issue with Memory Clearing function ending all applications running
Fixed: Issue with closing Notifications list
Fixed: Issue with flashing Settings Menu
Fixed: Bugs & errors that resulted in system crashes resolved
Fixed: System tray message errors in English, French and Arabic now resolved
You can also find it here http://support.jide.com/hc/en-us/articles/218742278-Remix-OS-Update-2-0-307
Click to expand...
Click to collapse
my mini is on 206 and says it's up to date. Guess this is a beta version and not a "stable" release?
Why did you not mention removing Google Apps? Also do you have a proper explanation as to why it has been removed? http://support.jide.com/hc/en-us/articles/218436148
IIIIkoolaidIIII said:
Why did you not mention removing Google Apps? Also do you have a proper explanation as to why it has been removed? http://support.jide.com/hc/en-us/articles/218436148
Click to expand...
Click to collapse
Google has asked them to remove play services because some apps don't work properly, but you can still install play services through the remix market so no worries.
Remix Central? what's so darn central about it? gives you access to a few apps but no info to make Mini more useful or troubleshoot problems like jinky video or the black screen flashes or the IR problems. No info on good Kodi builds for the Mini. And we are talking about it here, not on "Remix Central"! Not even half baked, yet installed automatically.
I have used a Cube i6 with original Remix much more effectively than the mini is working. Jide must have a cannabis supplier next door.
Oh no, did I piss off the Remix gods by whining about Remix "Central"?
Now after update, Mini says "optimizing app", takes several minutes, then shuts down. Once got it to go for about 10 minutes before shutdown. WTF?
Try to wipe cache in recovery
Hello. My Remix is restarted when opening applications Smart karaoke player Pro
Remix not support VOB file
I would like to know if root will be available? I am well aware of voiding my warrnaty. However this RemixMini is worthless without being able to use Adaway and most of all Apps to External SD. Why bother incluiding ports for sdcards and usb drives otherwise? 16gb is not enough, far from it.
I bought this feeling that while new devolopment would increase. But then notice how deceptive Jide was regarding the Google Play Services announcment. To me without root it is a bricked box, so what is there to loose other than my hard earned cash?
1. Jide is pushing PC Remix completley free - So to help your continuing efforts I bought it.
2. Freely can root - slice, dice and customize PC Remix, as I wish, but not to those who paid or stuck with it since Kickstarter...No we got kicked in the nutz.
4. Remix Mini is dead. Notice the rooted, double the space and on some double the power under the hood on Amazon? Same price or cheaper. I feel you have all but abaonded Mini since Play was yanked. So I guess I will crack it open and glitch to get root. WHat a waste of money.
5. NEVER AGIAN
Remix OS UEFI Boot from Mac Mini (Late 2012)
Does this version have issue installing to extFAT file system as 3.0.204 had?.
As I'm using MAC Mini (Late 2012) with i5 (2.5GHz) and 8GB RAM.
Below are my Configuration on Mac Mini 500GB Hdd.
Partition 1 : 400 (MAC OSX Partition)
Partition 2 : 60GB (FAT32) - Also Tested for REMIX OS 3 testing
Partition 3 : 32GB (for Remix) - Formatted with Fat32, exFAT, NTFS, ext4...
### for Partition 3, only Fat32 & exFAT can be detected as UEFI drive from Mac Mini, but only FAT32 success boot the REMIX 3.
- But The Problem of this are FAT32 can only generated max 4GB data.img on 32GB fat32 partition.
- exFAT won't boot the selection menu " Guess / Resident " just able to boot to minimal GRUB Command...
- NTFS and ext4 won't even detect on my MAC Mini as UEFI Drive.
p/s : anyone know if there are indeed another method that can either make exFAT work for REMIX OS or route the data.img location
to another partiton?.
Has anyone managed to install version 8.1.A.0.12 on XZ1? I have LOS 15.1 running (that's 8.1) and it just wouldn't install. I just place the file in the internal storage and install it from TWRP. It proceeds and there are no errors, but the app is not installed when I boot the phone up.
Previously I tried your way and got same problem - nothing installed. If you want to continue that way you should mount system partition in twrp (I'm section mount) before anything flashed.
I tried this way and be haply on lineageos16:
Sony apps enabler and Xperia keyboard from apkmirror
https://forum.xda-developers.com/an...-sony-apps-enabler-install-sony-apps-t3590477
https://www.apkmirror.com/apk/sony-mobile-communications/xperia-keyboard/
8.0.a.110 worked for me
Have fun
There are also "standalone" Xperia Keyboard application modifications available here on XDA which work also on the LineageOS 16 and older ones without need for Sony Apps Enabler or any other additional applications. For last several years, since about CyanogenMod 11, I use Xperia Keyboard as my default keyboard. I haven't tested it with LineageOS 17. I currently use on LineageOS 16 on Sony Xperia XZ1 Compact version 8.0.A.0.110 from this thread.
This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. Installing google apps requires some apps to move to data partition because of limited system size. See install description for more info.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-The camera preview image sometimes shakes at random
Download
https://mega.nz/#F!5fBWlIAQ!Jlq9Bj789iJ0iIIptK00tg
Update
If you already run an earlier version of this rom, just boot to twrp and install the latest flashable zip file
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz link is in section download)
5. If you want to install opengapps or need system partition space for other things. Install the move_to_data.zip file from the attachments. This will move the Webview and the LatinIME app to data partition.
6. Choose one of the following options:
-either install google apps (download form https://opengapps.org/. Choose x86 9.0 nano or pico)
-or install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360) this is lighter in ram and cpu usage but you will get problems with google chrome and other apps
7. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
8. Reboot the phone. First reboot will take some time
Changelog
Code:
20191018:
fixed problem with sms receiving
20191012:
mobile network connection works now after boot
Fixed problems with network switching
Show taps option is working now
intel art extension enabled
Call recording enabled
text relocation warnings disbaled
(untested) encryption. Needs special configuration (see below)
20190819:
SELinux is now enforcing
Notification access feature enabled
solved crashes with houdini emulated apps
20190713:
usb configuration works properly
battery light works now
July security patches
20190704:
first stable release of this rom
DATA Encryption
If you want to enable data encryption this would break the pds partition backup. To prevent this, the cache partition can be used as backup location:
-edit /system/bin/pdsbackup.sh
-change PDS_FILE=/data/misc/pds/pdsdata.img to PDS_FILE=/cache/misc/pds/pdsdata.img
-resize data partition in TWRP:
Code:
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk0p17
resize2fs /dev/block/mmcblk0p17 1367079
-reboot the phone
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-08-19
Created 2019-07-04
Last Updated 2019-08-19
This if I did not expect it, I'll try to see how it goes. Thank you.
Download links and install description are up now. Download from mega.nz because xda download section is broken at the moment. I'm waiting for your test reports
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
BTW, performance is really great, seems to be almost same as Lineage 11.
dumkm said:
It's really great works, thank you!!
I quickly tried and found several points.
- USB connection with PC
All USB connection option including File Transfer, USB tethering, PTP are grayed out.
Disabling/Enabling android debug in setting didn't work.
Click to expand...
Click to collapse
I also noticed that. Will see how this can be fixed. It is just a problem with the option dialog. Usb connection works fine. As a workaround you can set a default USB configuration in developer options
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I have not tested storage encryption yet. Will have a look at it later
dumkm said:
- SElinux
Although it is designated as permissive in device.mk, it's actually worked as "disabled".
I'm not sure it's related or not, however, when building "user build", it's failed with "ERROR: permissive domains not allowed in user builds".
I know "user build" is not officially supported in Lineage release, however, it's really helpful if we can do it for AFW usage.
Previously I could use Lineage 14.1 smi build for AFW and safetynet app with user build.
Click to expand...
Click to collapse
I think lineage trust doesn't differentiate between permissive and disabled. Selinux support is planned for future releases
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
dumkm said:
Thank you for quick check.
Regarding USB connection, I also confirmed that Ubuntu can recognize as external storage with above option, besides Windows still does not recognize. Maybe depending on my environment.
Also I noticed that Chrome, Chrome Beta and Chrome Canary (therefore another Chrome based apps such as Maps Go) always crash. This is also maybe my environment only, though. BTW, I could install MicroG, besides couldn't install OpenGapps 9.0 pico due to partition size limit.
Additionally, I couldn't find any LED settings, currently LED is always off during charge or any notification.
Click to expand...
Click to collapse
Notification Led should work. Can be configured under settings->apps and notifications->notifications->notification light. I don't know what happened with the battery light. It will hopefully come back if I upgrade the driver to hidl.
Google Chrome is a known problem with MicroG. It requires official gapps. I will check if some of the unprivileged lineage apps can be moved to data partition to make place for google apps
Newbie question
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
dumkm said:
Regarding LED, maybe it became working after modifying some option of notification light. Battery connection light is still always off.
Regarding opengapps, I moved webview and LatinIME from app directory to external SD in TWRP, then installed as normal app after system boot. Webview worked fine besides LatinIME always crash. I'm using different IME, so it's no problem. With this environment, opengapps nano can be installed, then Chrome, Maps and other google apps worked.
Click to expand...
Click to collapse
That's good. Than we can make a flashable zip to automatically move and symlink them to data partition.
I will provide a new build till end of the week with improved usb and notification LED implementation. I already got it working in my local setup
flameseewa said:
Hi all, I know someone who's selling her old RAZR i XT890 and I'm interested (for experimental reasons but also the oddity that it's Intel powered). I've never owned a RAZR i so I've got some questions:
-The phone is from 2012 so quite old and has 1GB RAM, does it work well with this Lineage 16? Because usually newer software would perform bad on older SoC (I used to have iOS 7 on iPhone 4 back in the day and it was painfully slow compared to 6).
-On Lineage 16, can it run any Android app as a standard new Android Pie phone? I ask because this is an Intel x86 CPU, so can it still run Android apps as normal or are most of them only designed for ARM and therefore unusable?
If I get the good news, I may buy the phone and try this Lineage OS custom ROM.
Click to expand...
Click to collapse
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
julianwi said:
Newer android versions have been designed while keeping low ram devices in mind. Ram hungry special features like the picture in picture mode are excluded from builds for older device. So the situation is much better then on iOS. But a newer phone would run better thought.
Most android apps are available for x86. But some are still arm only and get automatically emulated. The intel houdini emulator integrates these apps natively into the system but they are a bit slower then x86 apps. These are for example Skype and a few unity based games
Click to expand...
Click to collapse
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
TWRP error 70
julianwi said:
This is an unofficial build of LineageOS 16.0 for the Motorola razr I, (XT890/SMI).
Lots of thanks to Hazou. This rom is based on his los-14 rom and I got help from him with los-16.
This rom has full hardware support and should run stable. It has been tested by me in daily use. I'm using the rom without google apps, but with microg. I don't know how smooth it runs with official gapps.
Special Features
-All features of Hazous 14.1 rom
-MicroG signature spoofing patch is included.
-Adaptive icons can be disabled in homescreen settings.
I can include more features if requested
Known Bugs
-Mobile cell connection doesn't connect after boot. You have to turn airplane mode on and off to let it work.
-selinux is set to permissive for now (reduced security)
Please report more bugs if you test this rom
Install
1. Backup everything you don't want to loose.
2. Download and install TWRP 3.2.3 (download in attachments. Can be flashed with fastboot or with another recovery)
3. If you come from another rom do a full wipe with twrp
4. Download and install the rom flashable zip (download from mega.nz https://mega.nz/#!ICwXRC6D!VZqe3o5zeWbmMiZvka_BtUTW5T_V7_OdMS57Oe9CbMk)
5. Choose one of the following options:
-either install MicroG (can be installed with the unofficial installer https://forum.xda-developers.com/android/development/microg-unofficial-installer-t3432360)
-or install google apps (download form https://opengapps.org/. Choose x86 9.0 pico)
6. If you want root access install the addonsu-16.0-x86.zip (download in the attachments)
7. Reboot the phone. First reboot will take some time
XDA:DevDB Information
unonfficial LineageOS 16.0, ROM for the Motorola RAZR i
Contributors
julianwi, Hazou
Source Code: https://github.com/julianwi/android_device_motorola_smi/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Stable
Stable Release Date: 2019-07-04
Created 2019-07-04
Last Updated 2019-07-05
Click to expand...
Click to collapse
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Kazvko said:
I've installed the OS without problems, but when i try to get GApps Pico or any other version TWRP prompt error 70. How should i proceed? There is any additional configuration needed?
Click to expand...
Click to collapse
Yes, system partition size is limited on this phone. To install GApps some files need to be moved to data partition.
I created a flashable zip to automate this process. Take a look at the modified install description in the first post
New build is up now.
flameseewa said:
Thanks for the response. So I should be alright with it then, hopefully. I just hope it won't lag on that old SoC. I'd love if you could upload a quick video of it in action.
Click to expand...
Click to collapse
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
julianwi said:
New build is up now.
Sorry don't have enough time to make a video in the near future. Maybe someone else can record a video of it
Click to expand...
Click to collapse
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
dumkm said:
I could confirm that notification LED and USB storage works fine with lineage-16.0-20190713-UNOFFICIAL-smi. Thanks.
Still WiFi with storage encryption does not work.
Click to expand...
Click to collapse
I know, haven't looked at the storage encryption for now. It will maybe be in the next update next month
flameseewa said:
Alright, thanks. I bought my friend's RAZR i and I am planning to use it as a daily driver with this ROM (I'm a light user anyway), I can't thank you enough for making this LineageOS for such an old device. I wonder if such a recent Lineage has been developed for the 2011 Atrix, haven't seen one.
I have questions though, firstly I've never used a custom ROM before, can I simply follow the instructions on this thread to get it working, or is there anything that has to be done beforehand like rooting? Secondly, are any other OSs successfully booting on this x86 phone, as I can't find it on XDA? (it surprisingly hasn't gotten much attention as a hackable device like HTC HD2 or Nokia N900 got).
Click to expand...
Click to collapse
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
julianwi said:
If the phone never had a custom rom yet, you have to unlock the bootloader first. Description is in this thread: https://forum.xda-developers.com/showthread.php?t=1928551
Click to expand...
Click to collapse
That's an old guide, will everything still work?
flameseewa said:
That's an old guide, will everything still work?
Click to expand...
Click to collapse
Yes, it should still work the same. If some links are outdated you can google them yourself
Thank you for bringing my old RAZR i back to life! I really appreciate the time and effort you spent for this obselete phone. Looking forward for more updates and for a bug free ROM. Using it now
dumkm said:
- Wifi with storage encryption
When you enable storage encryption, WiFi always become disabled, not be able to enable.
Just FYI, it required deleting /system/bin/pdsbackup.sh AND reducing partition size of 'data' (/dev/block/mmcblk0p17).
Click to expand...
Click to collapse
I'm not sure if I misunderstood but when you said "it required deleting....." and "reducing partition size of data", did you mean you can get WiFi to work if you do those things? I'm no expert at these but I can atleast apply the "fix" (if it really is) given that you guide me, if it's okay with you. Thanks!
Recently I've been having issues with my Xperia Z (C6603), the device is crashing (hard reboot), but only with certain apps/app versions.
The apps that always crash the device are:
- Firefox Focus (org.mozilla.focus): 8.0.25 works, anything recent doesn't
- Firefox Preview (org.mozilla.fenix): 2.2.0 works, anything recent doesn't
- Reddit (com.reddit.frontpage) (never had an older version than current)
Things I've tried:
- Official Lineage 15.1 2020-02-21:
-- Device crashes
- Unofficial Lineage 16.0 2019-10-20; Phone wiped with only GApps Micro installed:
-- Device crashes
- Stock 5.1.1 10.7.A.0.228; Phone wiped, bootloader locked:
-- Works fine, the apps do not crash the device
- I've looked at logcat but don't see any errors, it just starts the activity and then shuts down. I am not an expert on debugging however...
- From what I've seen, any other app (~157 user apps installed) works perfectly fine
Is anyone else experiencing this (with specific apps) and do you know if any of the recent unofficial LineageOS 16 ROMs don't have this problem?
What other steps could I take to pin down this problem?
I prefer to run an official Lineage ROM, or at least something recent that is built in a transparent way.
Thanks in advance ?
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.