{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello everybody,
Lineage OS 18.1 (Android 11) finally arrived officially with Lineage OS Recovery and discontinued Lineage OS 17.1. If you want to take security and bug fixes updates you need to use Lineage OS 18.1.
New Features!
Security patches from April 2020 to March 2021 have been merged to LineageOS 15.1 through 18.1.
18.1 builds are currently based on the android-11.0.0_r32 tag, which is the Pixel series unified tag.
Wi-Fi display is available for newer Qualcomm devices, on a device-by-device basis.
WebView has been updated to Chromium 89.0.4389.105.
Our Recorder app has been vastly improved in more ways than can be counted, go leave yourself a voice-memo so you don’t forget that great idea!
Screen recording has been moved to a QS tile to match AOSP’s behavior.
The user interface has been revamped and there’s also now a UI for easily viewing, managing, and sharing your voice notes.
It’s now possible to choose the quality of your audio recordings to save space.
It’s now possible to pause and resume recordings.
The FOSS Etar app has been forked, improved, and shipped in place of the stagnant and largely unmaintained AOSP calendar.
The Calyx institute’s FOSS Seedvault application has been included as a built-in backup solution.
To use it, navigate to Settings -> System -> Backup, and “Change backup provider” to Seedvault. You can then click “Seedvault Backup” to configure, schedule, and encrypt backups!
Backups created with Seedvault can be uploaded on your Nextcloud instance, an external USB drive or kept on your local storage.
There is now an option on non-A/B devices to update the recovery image alongside the OS, just as the stock OS would!
To use this, either enable the option during the initial device setup or navigate to Settings -> System -> (Show More) Updater -> Three Dot Menu in the top right -> and check “Update recovery alongside OS”.
Our music app, Eleven now has a more up-to-date UI and integrates nicely with all the new android features for music players such as seeking from the notification.
All LineageOS apps now have support for dark mode.
(17.1 too) Our recovery now has a new, colorful, and fun UI that is much more accessible.
(17.1 too) The firewall can block all connections now by making apps think that the device is in airplane mode.
(17.1 too) We’ve introduced a new expandable volume dialog UI that allows you to control multiple volume streams more easily.
(17.1 too) The partial screenshot feature has been improved with a new UI that’s easier to use. On 18.1 it also integrates nicely with the new Android’s “instant screenshot”. Long press the screenshot button in the power menu and give it a try!
(17.1 too) Trebuchet now supports icon packs.
(17.1 too) ADB root was reworked to ensure compatibility with other 3rd party root solutions.
Known Bugs:
-NFC (Unfixeable)
-Reading Mode (Unfixeable)
-Wifi Direct(You need to turn on gps if you want to use wifi direct)
-Some minor issues
Links:
Samsung Sensor (s3ve3gjv)
Sony Sensor (s3ve3gxx)
Dual Sim (s3ve3gds)
Strongly recommend to use Lineage OS Recovery for updates!!
Note: Use Magisk for root
Changelog:
Samsung Sensor (s3ve3gjv)
Sony Sensor (s3ve3gxx)
Dual Sim (s3ve3gds)
Previous LineageOS Roms:
LineageOS 17.1
LineageOS 16
Version Information
ROM OS Version: 11 R
Status: Stable
Created: 2021-10-25
Last Updated: 2023-XX-XX (Keeps getting Updates every month)
Rez
Rez
kanka türksün dimi bi baksana benim telefon kurulum ekranında kalıyor yardımcı olur musun
Translated by GT: bro, you are turkish, take a look, my phone stays on the setup screen, can you help me?
Hi! Maybe LineageOS website have a typo? I have Samsung Galaxy S III NEO and in system information it shows model [s3ve3gxx]. In service menu it shows Samsung camera.
By LineageOS info I should have Sony camera. Who should I believe?
Hi,
wondering what TWRP version works with this. I had troubles with backup & restore by using twrp-3.3.1-1-s3ve3g on LineageOS 17.1 and struggled to make it work, see:
[ROM][OFFICIAL][DISCONTINUED][10] LineageOS 17.1 for S3 Neo
Hello everybody, If you haven't heard it already, LineageOS 17.1 (Android 10) finally arrived officially with LineageOS Recovery Links: Samsung Sensor (s3ve3gjv) Sony Sensor (s3ve3gxx) Dual Sim (s3ve3gds) Note: Use Magisk for root. This rom...
forum.xda-developers.com
Edit:
Just noticed the there's a new twrp-3.6.0_9-0-s3ve3g.img for S3 Neo officially available at:
Download TWRP for s3ve3g
Download TWRP Open Recovery for s3ve3g
dl.twrp.me
Has anyone tested this with LineageOS 18.1 ? I'm more intersted in properly handling the partitions and the backup & restore procedure.
4ipon4ik said:
Hi! Maybe LineageOS website have a typo? I have Samsung Galaxy S III NEO and in system information it shows model [s3ve3gxx]. In service menu it shows Samsung camera.
By LineageOS info I should have Sony camera. Who should I believe?
Click to expand...
Click to collapse
try these methods: https://forum.xda-developers.com/t/...mera-sensor-you-have-sony-or-samsung.3759213/
helloyello said:
Hi,
wondering what TWRP version works with this. I had troubles with backup & restore by using twrp-3.3.1-1-s3ve3g on LineageOS 17.1 and struggled to make it work, see:
[ROM][OFFICIAL][DISCONTINUED][10] LineageOS 17.1 for S3 Neo
Hello everybody, If you haven't heard it already, LineageOS 17.1 (Android 10) finally arrived officially with LineageOS Recovery Links: Samsung Sensor (s3ve3gjv) Sony Sensor (s3ve3gxx) Dual Sim (s3ve3gds) Note: Use Magisk for root. This rom...
forum.xda-developers.com
Edit:
Just noticed the there's a new twrp-3.6.0_9-0-s3ve3g.img for S3 Neo officially available at:
Download TWRP for s3ve3g
Download TWRP Open Recovery for s3ve3g
dl.twrp.me
Has anyone tested this with LineageOS 18.1 ? I'm more intersted in properly handling the partitions and the backup & restore procedure.
Click to expand...
Click to collapse
lineageOS doesn't support twrp backup and restore if you want to backup use titanium backup, google backup, lineage os seedvault or try this https://wiki.lineageos.org/devices/s3ve3gxx/upgrade
semih67x said:
kanka türksün dimi bi baksana benim telefon kurulum ekranında kalıyor yardımcı olur musun
Translated by GT: bro, you are turkish, take a look, my phone stays on the setup screen, can you help me?
Click to expand...
Click to collapse
Bende aynı sorunu yaşıyorum yardımcı olabilir misin
Translated by GT: I have the same problem can you help me
4ipon4ik said:
Hi! Maybe LineageOS website have a typo? I have Samsung Galaxy S III NEO and in system information it shows model [s3ve3gxx]. In service menu it shows Samsung camera.
By LineageOS info I should have Sony camera. Who should I believe?
Click to expand...
Click to collapse
Try s3ve3gxx if you encounter any problem (especially bootloop) try s3ve3gjv version
I have some WiFi issues. 2.4ghz is slow and sometimes S3 is not connecting.
Update: it's strange behaviour, certain apps say that phone is not connected to internet while others are working fine at the same moment.
Anyone else facing this?
do you have the latest bootloader?, it is recommended to have the latest firmware, for example Greek firmware:
samsung sensor:
COS-I9301IXCUARA1-Firmware Halabtech.zip
drive.google.com
sony sensor:
https://samfrew.com/it/download/GALAXY__S__%E2%85%A2__Neo__/6ip1/COS/I9301IXXUAQL1/I9301ICOSAQL1/
you can also have hardware problems, right?
in the house we have 2 s3 neo one sony the other samsung, no problem,with los 18.1.
BiG_FooT said:
I have some WiFi issues. 2.4ghz is slow and sometimes S3 is not connecting.
Update: it's strange behaviour, certain apps say that phone is not connected to internet while others are working fine at the same moment.
Anyone else facing this?
Click to expand...
Click to collapse
I'm having these issues since I updated to 18.1.
5Ghz only sees one of my APs and 2.4GHz is sloooww and always dropping
Also my baseband is: I9301IXXUAPG1
WOW this one is not working for me either. Every time phone starts, it goes up until setup wizard and then restarts. I've tried reinstalling again but still same problem.
Here's what I did
- did factory reset
- wiped dalvik/system/data/internal storage/cache/preload
- installed s3ve3gjv version
- rebooted to recovery (to keep twrp)
- rebooted to system
My TWRP version is above 3.0.0 (the latest one).
Why could I be experiencing this problem. Both this and Android 12 ROM are giving the exact same problem. But when flash LineageOS android 10 s3ve3gjv image, I experience no problem. What should I do?
I can confirm the issues reported with the WiFi connectivity on both 2,4GHz & 5 GHz and I presume it's a driver issue that was not addressed properly.
I'm not getting disconnected, and the signal strength is pretty stable, but as soon as the phone enters standby(doze) while connected on WiFi, when waking up, the connection is broken. It still looks connected, and can disable WiFi & reconnect on both networks, but after the WiFi handshake, the phone RX is broken - doesn't receive packets & doesn't answer to pings. A reboot helps as workaround. And, everything is working ok if you avoid standby during WiFi connectivity.
I tested all this on an OpenWRT router with tcpdump & ping.
I also remember some discussions in the LOS16 thread, where the devs said that they needed to disable power saving on the WiFi, because the driver is messed up. Maybe this should be also done in LOS 18.1.
Some other LOS18.1 observations - experiences:
- apart from the WiFi issue, it looks solid
- there's still the persistent (LOS16/LOS17) bug with BT & WiFi (2,4GHz only) not able to coexist (turned on and in use), WiFi get's disconnected if a BT Headset is used. I guess it's a driver/firmware issue.
- the new TWRP 3.6.0 works OK - get it from:
Samsung Galaxy S3 Neo i9301i
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Download TWRP for s3ve3g
Download TWRP Open Recovery for s3ve3g
eu.dl.twrp.me
- ViperFX - the classic installation way doesn't work anymore, but it works well with the Magisk Module and the instructions presented here:
[APP][ALL ROOT SOLUTIONS][6.0+]ViPER4Android FX 2.7
ViPER4Android FX By pittvandewitt and MrWhite214 Introduction Many users are enhancing their smartphone audio experience with the popular ViPER4Android software, but some of us have a hard time installing the driver or they don't like the look...
forum.xda-developers.com
Finally, I made a TWRP full backup of my LOS18.1 installation (a lot of work for the configuration) and reverted to LOS 17.1 (TWRP backup).
I'm considering LOS 18.1 broken and would be thankful if the devs take some time to look into the WiFi issue and fix it.
cannot connect to open wifi,
cross-posting this here
https://forum.xda-developers.com/t/...-for-s3-neo-beta.4399567/page-5#post-86747557
Phone running extremely slow it's almost unusable on this ROM and optimization is bad.
EDIT: SOLVED
Hello,
I have installed latest build (20220425) for my
Samsung Sensor (s3ve3gjv) and I do not have any camera app,
Device Info HW has reported both cameras are from Samsung, the ROM works well, except there is no camera app, and even Whatsapp can't initialize it.
I have installed MindTheGaaps version (11.0.0-arm-20210212_145641), right after flashing the ROM in recovery, setup wizard went smoothly..
Which Camera app do you use, and how?
In settings app --> Installed Apps list, I can see 'Camera', but there is no launcher icon for it..
package name: org.lineageos.snap
version: 2.02.082 (0188f6d9ec-30)
( I'll also post on lineage support, and see if they have an insight )
Edit: Just found this, might be the same issue, I didn't test camera on first boot,
I'll try and install snap from 17.1:
Camera app (org.lineageos.snap) disappears after fresh installation of most recent LineageOS nightlies (#4295) · Issues · LineageOS / issues / android · GitLab
Expected Behavior Lineage camera app should remain at bottom of launcher screen and should also be accessible from apps drawer.
gitlab.com
Edit #2: I clean flashed 17.1 for the Sony Sensor (s3ve3gxx),
without installing MindTheGaaps, and camera app showed up, and both cams are working fine..
I'm unsure if the issue was that I actually have the Sony sensor S3 Neo, while software reported Samsung sensors,
or if installing MindTheGaaps after flashing the ROM caused the camera app to now show up at all..
in between, I did install 17.1 for Samsung Sensor but I also installed MindTheGaaps in the flash session..
Edit #3: It seems it was the ROM, even though Method #4 of the Samsung vs Sony thread reported I have 2 Samsung sensors, only the Sony Sensor ROM shows camera icon for me, while Samsung Sensor ROM didn't, Also note I am now on Lineage 17.1, because I dont mind staying a bit behind, and I dont have any more time to fiddle with flashing 18.1 Sony and testing it..
i need last twrp for s3ve3gdsxx
wher is download odin versian for s3ve3gdsxx ?
sajjads24 said:
i need last twrp for s3ve3gdsxx
wher is download odin versian for s3ve3gdsxx ?
Click to expand...
Click to collapse
There's a unified TWRP for all s3ve3g on twrp.me
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto g7
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto g7, codename river.
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
None.
Notes:
Official Lineage OS builds for river ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK29, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll find no support for these.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto G7
Contributors
npjohnson, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Firmware Required: Newest firmware available for your variant
Version Information
Status: Stable
Created 2020-04-01
Last Updated 2020-04-15
Awesome!
VoLTE working?
Edit 4/3: Like the unofficial releases, still no Wifi calling on Fi. Would be great if we could get that working.
Just an imporant FYI - ICYDK Community
https://www.androidpolice.com/2020/...-android-10-builds-will-probably-launch-soon/
At the time of this writing - there are some signing issues related to LineageOS 10 Roms (including river), so the link provided will take you to only version 16. Rest assured though, the team is working on it. The above link to android police, explained it all for me, hopefully for you as well. A screenshot is included in case the above link with the reference points disappear. Thank you for npjohnson for taking the time to support this. At last the river gets Android 10
LineageOS 17.1 works wonderfully however the Trebuchet Launcher does not seem to work as it crashes even upon first boot but any other launcher works perfectly.
The FM Radio does not work at all unfortunately, neither on LineageOS 16 nor 17.1, I hope that gets resolved soon.
Other than that, great work!
Very great to see this release. I have 2 questions:
- 1. Does this pass safetynet by just installing? I mean I don't want to install Magisk and Magisk hide
- 2. Does it work without any risks with the Februrary 2020 security update? I heard that if you are in that security update and then make a wrong move with formatting a partition there is no way to recover a brick / no blankflash available?
Thank you in advance!
Almost full Pixel Experience
No issues so far, running smooth and fast. I feel that this device is running faster than my Stock Pixel 3a XL. Magisk is working, so I'm using it as a daily driver from now on. Thanks a lot :good:
@npjohnson
This sounds nuts but this actually boots on the Moto G7 Play too. This tells me that 64bit builds can be ported to our device. The only thing that would need to be changed (I think) are touchscreen drivers, and gpio keys. I was able to boot into LOS recovery by changing river to channel in the default prop and flashing it. The screen is split and mostly unreadable but it is recognized by adb. Flashing the dtbo allows the boot logo to display properly with some flickering. Everything after that is still split however.
Given this info; Would you have any interest in trying to build for us too?
Also, would you have any idea how to resize a vendor partition? I think if I flash the vendor.img, it might fix the touchscreen. Right now twrp says it's bigger than my target device. (Which is a load of crap, I have 22gb free.)
Phone calls on Google Fi do not work when connected to T-Mobile, only Sprint
Is the upgrade procedure from 16.0 to 17.1 supposed to erase my data ?
Is there any specific procedure to install magisk?
So from what I've experienced so far, calling doesn't work when using Google Fi on T-Mobile and location also doesn't work either on any app. OTAs also fail via the LineageOS Updater and the FM Radio is broken too
So I and like other people that have been reporting on Reddit, my device powers down a few seconds it boots into Los 17.1 i can't be certain but I think it started powering off and rebooting into TWRP 3.3.1.2. This has been from a clear flash/install.
Formated/erased everything
Followed Los 17.1 instructions to install Os and Gapps, Magisk
Device Boots into L.o.s 17.1 Gapps updates then devices powers down and reboots back in twrp
The device now just reboots after booting into L.o.s 17.1
farscaper11 said:
So I and like other people that have been reporting on Reddit, my device powers down a few seconds it boots into Los 17.1 i can't be certain but I think it started powering off and rebooting into TWRP 3.3.1.2. This has been from a clear flash/install.
Formated/erased everything
Followed Los 17.1 instructions to install Os and Gapps, Magisk
Device Boots into L.o.s 17.1 Gapps updates then devices powers down and reboots back in twrp
The device now just reboots after booting into L.o.s 17.1
Click to expand...
Click to collapse
fastboot -w (formats data, internal SD so back them up before doing this)
AgentICS said:
So from what I've experienced so far, calling doesn't work when using Google Fi on T-Mobile and location also doesn't work either on any app. OTAs also fail via the LineageOS Updater and the FM Radio is broken too
Click to expand...
Click to collapse
I can also confirm the issues with the FM Radio and the OTA updates failing. Originally I thought it may be due flashing over 16.1, but both issues persist after a complete wipe.
Anyone have an idea what to do if LineageOS is preventing any sort of mobile data connection? I'm using a Fi phone that I've flashed the standard retail update on before to get the Android Update to Feb 1. I'm using A Sprint MNO called Tello that works fine on Stock, any ideas?
cybersecuritystudy said:
Anyone have an idea what to do if LineageOS is preventing any sort of mobile data connection? I'm using a Fi phone that I've flashed the standard retail update on before to get the Android Update to Feb 1. I'm using A Sprint MNO called Tello that works fine on Stock, any ideas?
Click to expand...
Click to collapse
Did you check for the correct apn settings?
jman315 said:
Did you check for the correct apn settings?
Click to expand...
Click to collapse
Thanks for the reply. I've researched that, and can't seem to quite find how to make a change in that. The standard procedures for doing anything with Access Point Names did not seem to show up in either Lineage 16.0 or 17.1. I found info on my carrier site (Tello), but have no idea how to change it since it doesn't show up as an option to change in the mobile network settings.
cybersecuritystudy said:
Thanks for the reply. I've researched that, and can't seem to quite find how to make a change in that. The standard procedures for doing anything with Access Point Names did not seem to show up in either Lineage 16.0 or 17.1. I found info on my carrier site (Tello), but have no idea how to change it since it doesn't show up as an option to change in the mobile network settings.
Click to expand...
Click to collapse
For me the APN settings can be found under...
Settings -> Network & Internet -> Mobile network -> Advanced -> Access Point Names
or
I can also find it by just searching for "access point names"
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
The 4-12 nightly OTA was the first to apply successfully. One other thing I have noticed that does not work since coming from LOS 16 is night light.
AgentICS said:
Phone calls on Google Fi do not work when connected to T-Mobile, only Sprint
Click to expand...
Click to collapse
Likely the way you setup Gapps
Google Fi Requires some extra packages to function correctly
you can find my personal Gapps Fi Pico package here:
https://www.androidfilehost.com/?w=files&flid=306318
jman315 said:
For me the APN settings can be found under...
Settings -> Network & Internet -> Mobile network -> Advanced -> Access Point Names
or
I can also find it by just searching for "access point names"
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
The 4-12 nightly OTA was the first to apply successfully. One other thing I have noticed that does not work since coming from LOS 16 is night light.
Click to expand...
Click to collapse
Thanks for the info. It's not in that location, all I have is Settings Version, Wi-Fi Calling, Carrier Video Calling, System Select, CDMA Subscription, and Carrier Settings.
The good news is, it looks like its working as of the 4-17 version I retried last night without needing to change anything. Thanks!
Also on a side note, I noticed there is no superuser download option for this version of LineageOS yet. Is this something that is coming down the line, or is there just a problem with doing this on the OS level?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 16.0 for Xiaomi Redmi Note 2 (HERMES)
ABOUT:
ROM Version: Beta
Device: Xiaomi Redmi Note 2 (HERMES)
Maintainer: @ibilux
Build Status: Unofficial
DISCLAIMER:
I am not responsible for anything that may happen to your phone as a result of installing custom ROMs and/or kernels.
You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
FEATURES:
• Working:
Adjustable brightness
Audio
Auto brightness
RIL (calls & mobile data & ussd)
Video
Gallery
Mic
Wi-Fi
FM-Radio
Bluetooth
Internet
GPS (need to flash this patch)
Hotspot
SD Card
Online/Offline charging
Built-in Signature Spoofing (for MicroG)
USB tethering
IR Blaster
Vibration
Rotation sensor
MTP and Mass Storage modes
Lights
Camera (Photos & Video recording) [It's better to use Open Camera or Footej Camera Apps]
DT2W support.
• NOT working:
?
• Bugs:
?
PRECAUTION:
Read the entire OP before posting, downloading, or flashing ANYTHING
Follow all instructions
Please use the search function and read back a few pages before you post any questions
ALWAYS MAKE A NANDROID BACKUP
ALWAYS MAKE AN EXTERNAL BACKUP OF ALL DATA
INSTRUCTIONS:
NOTE:
If you are using the old unofficial Build make a clean flash and don't dirty flash.
CLEAN FLASH:
Reboot into the latest version of TWRP (from here)
Make a NANDROID backup and copy it an external medium (laptop, flash drive, etc) just in case something goes wrong!
Wipe Dalvik/ART cache, system, data, and cache partitions (ANY LESS IS NOT A CLEAN FLASH!)
Flash build
Wipe Cache [Not Necessary]
OPTIONAL: If you want root access, flash Addon SU or from official LineageOS extras
Reboot
DIRTY FLASH:
Reboot into the latest version of TWRP (from here)
Make a NANDROID backup and copy it an external medium (laptop, flash drive, etc) just in case something goes wrong!
Flash build
Wipe Cache [Necessary]
OPTIONAL: If you want root access, flash Addon SU or from official LineageOS extras
Reboot
DOWNLOADS:
ROM
GPS FIX
Audio playback via Bluetooth FIX
TWRP 3.3.1
BUG REPORTING:
DO NOT REPORT BUGS IF YOU HAVE FLASHED MAGISK, XPOSED, A CUSTOM KERNEL, OR ANY OTHER UNSUPPORTED THIRD-PARTY MODS
The very first step will be to attempt a new download and CLEAN FLASH (WIPE DALVIK/ART CACHE, SYSTEM, DATA, AND CACHE).
Pull an ADB LOGCAT and copy & paste it to HASTEBIN .
Save the log and copy the URL.
Visit HERMES (REDMI NOTE 2 / 2 PRO) - OFFICIAL GROUP and post your issue with the HASTEBIN link of your bug.
Please also tell us what device you're running, what date the build is from, if it was a release build, what packages you flashed with it (what Gapps package, Magisk version, etc).
You may also report bugs in this thread.
Join us at Telegram:
https://t.me/joinchat/AAAAAEAcYGMW9RpRIW2-XQ
Credits
Maintainer: @Bilux
This is all based on the work of @Dinolek and the help of other developers.
Thanks to @Dargons10 For building the roms.
XDA:DevDB Information
LineageOS 16.0 for Xiaomi Redmi Note 2 (HERMES), ROM for the Redmi Note 2
Contributors
ibilux, Dinolek
Source Code: https://github.com/ibilux/android_device_tree_hermes
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader & Latest TWRP Recovery
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.0.0
Beta Release Date: 2020-04-29
Created 2020-05-04
Last Updated 2020-05-04
TWRP:
MUST FLASH LATEST VERSION OF TWRP TO FLASH THIS BUILD, OR ELSE WILL GET THIS ERROR
DOWNLOAD TWRP 3.3.1
CUSTOM KERNEL: [TESTING]
It may fix some problems for some devices. Flash via TWRP.
Kernel LOS-16.0
Thank you so much
dirty flash didn't work for me so i flashed the rom cleanly. magisk and EdXposed work so well. the default wallpaper picker is limiting me from cropping an image the way i want to so i used wallpaper picker from GApps, battery life is as good as the oreo rom you just released recently. navigation bar menu wasn't found in the setting although i can search it and it shows where it is. currently running gravitybox and greenify on EdXposed and redmi note 2 tool to optimize my battery life. instagram still stutters every time a video and or a live feed is being played
update :
instagram stutter issue is not as bad as the one in the LOS 15.1, battery life is slightly worse than LOS 15.1's, substratum doesn't work as good as in the LOS 15.1
OMG... this phone still alive !! amazing, good work !!
The phone got a new life! Thank you!
But there is a serious problem - it is impossible to connect to a hidden wifi access point. In advanced settings support for a hidden access point is on.
if make AP visible SSID then phone may connected, but if make AP hidden SSID then phone not see this AP and not connect even if AP name was saved!
WiFi Analyzer application installed on this phone shows hidden APs without SSID.
I had this problem and with lineage-15.1-20200422 firmware too.
Please fix this problem! I need it very much!
Random reboot on my hermes
Hi friend, is possible to fix it.
want to share my experience using this rom.
previously i was using miuipro so more or less i compare these 2 roms.
PROS:
1 pretty good battery life
2 better performance
3 it's lighter
4 better than lollipop
CONS:
1 it reboots randomly (more than 10 times in a day)
2 the sim cards sometimes not detected, when detected the signal have X mark sign
3 confusing settings menu for me
4 not support non-mainstream icon app in status bar
5 can't play media (music, YouTube) from BT speaker
after all really appreciate your work
thanks
For random reboot i tested to suitch in development option the android system web view, for now no random reboot, continue the test.
Kinderjoy said:
want to share my experience using this rom.
previously i was using miuipro so more or less i compare these 2 roms.
PROS:
1 pretty good battery life
2 better performance
3 it's lighter
4 better than lollipop
CONS:
1 it reboots randomly (more than 10 times in a day)
2 the sim cards sometimes not detected, when detected the signal have X mark sign
3 confusing settings menu for me
4 not support non-mainstream icon app in status bar
5 can't play media (music, YouTube) from BT speaker
after all really appreciate your work
thanks
Click to expand...
Click to collapse
it's still in beta so we may experience some bugs along the way. you might wanna try the more stable LOS 15.1 released by him as well last month. it has better battery life and it's easier to install magisk and xposed in that very rom. though i like how substratum works in this LOS 16, i still have better experience overall in LOS 15.1 as it's more stable and the only bug i encountered was some stuttering on instagram in both vanilla and modded app. i don't really use it though, so it's not a big of a deal for me
Problem with audio recording in WhatsApp, audio some time distorted
Please at least press 'thanks' to OP at first post as a minimal support !
ibilux said:
CUSTOM KERNEL: [TESTING]
It may fix some problems for some devices. Flash via TWRP.
Kernel LOS-16.0
Click to expand...
Click to collapse
can you tell us what problems it will be fixed?
rocka10023 said:
For random reboot i tested to suitch in development option the android system web view, for now no random reboot, continue the test.
Click to expand...
Click to collapse
sorry i don't fully understand because i looked to development option>system webview there was only 1 option then i installed android system webview from play store so i switch to the new one and the problem was still there
PapaMoZ said:
it's still in beta so we may experience some bugs along the way. you might wanna try the more stable LOS 15.1 released by him as well last month. it has better battery life and it's easier to install magisk and xposed in that very rom. though i like how substratum works in this LOS 16, i still have better experience overall in LOS 15.1 as it's more stable and the only bug i encountered was some stuttering on instagram in both vanilla and modded app. i don't really use it though, so it's not a big of a deal for me
Click to expand...
Click to collapse
thanks for the advice
ibilux said:
CUSTOM KERNEL: [TESTING]
It may fix some problems for some devices. Flash via TWRP.
Kernel LOS-16.0
Click to expand...
Click to collapse
Pls read 2nd post from dev, there's a fix by custom kernel.
Thank you so much for reviving my secondary phone.
I was searching and waiting for updates and now it is there! All problems with auto rebooting is easy to fix. Just flash kernel in thread bellow and ROM will run normally. I hope updates will rollout in future .
anyone done a dirty flash from lineageOS15.1 from the same dev??? if so how well did it go?
delete
google camera is not working
unicunic said:
for those with problematic mobile data not to connect sim2:
edit build.prop change : ro.mtk_enable_md1 = 1
to
ro.mtk_enable_md2 = 1
or just add :
persist.radio.default.sim=0
Click to expand...
Click to collapse
What was the problem exactly ? sim2 didn't detected? no calls ? or no internet connection ? or something else?
and from where did u get this idea ?
ibilux said:
What was the problem exactly ? sim2 didn't detected? no calls ? or no internet connection ? or something else?
and from where did u get this idea ?
Click to expand...
Click to collapse
if you use mobile data from sim 2 it can't connect often, it has to restart repeatedly, sorry master if it interferes, just delete my unnecessary post,
note: i love your incredible rom. thank you, master
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Warning !
Installing a custom ROM on your device can sometimes be difficult and also with unwanted consequences! Therefore, make sure that you understand exactly what risks this operation entails - you are the only one responsible for all actions taken on your device.
What's Working :
Touchscreen
Audio & Video
Hardware video decoder
Wi-Fi
Bluetooth
Lights
Camera
Internal/External Storage
USB/ADB/MTP/OTG
Off-mode Charging
DRM enabled ( the same Level L3 like on Stock EMUI Firmware )
Sensors
Notification light
Fingerprint scanner
RIL & LTE data connection
What's Not Working :
WiFi tethering
SELinux Disabled
Encryption
GPS
Instructions :
Install the new TWRP 3.3.1-1 ( needed for Android Pie/Q )
Reboot to TWRP 3.3.1-1
Perform a clean wipe for the first install
Flash the latest build available and gapps
Reboot
Downloads :
Final Build : 07/03/2021 : LineageOS-16.0-BTV
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
DEV: Information
Contributors
surdu_petru
Kernel Source Code: android_kernel_huawei_btv
ROM OS Version: LineageOS 16.0 - Android Pie
Version Information
Status: CLOSED
Created 2020-11-22
Last Updated 2020-12-06
TWRP 3.3.1-1
TWRP 3.3.1-1
Downloads :
twrp-3.3.1-1.img md5: 5267939dc15954d4538855743e100ed7
*** reserved ***
Oooo
Very exciting news!
question: Why are you working on Android 9 instead of jumping to Android 10? (i think i saw in the other thread that you already managed to boot it up on your tablet)
Awesome! Btw encryption is listed as not working, does this mean android adoptable storage won't work?
Been using it for half a day now. I'm amazed that it's not laggy/buggy for a testing build.The build is fluid and smooth. I thought it'll random reboot every 5 minutes. No force closes or reboots until now. I might be spesking too soon though.
For rotation I used *rotation control* app from the play store and the controls are pinned in the notifications.
And Because it felt that stable I went and installed magisk and safetynet passed with the same steps explained in the Oreo thread.
Pie gestures are there for who cares about it. And you can enable A10 gestures with magisk and an app.. You can google (Android 10 gestures for android pie) and it's worth it tbh.
ofc If I encounter any bug first thing I'd do is removing magisk.
Appreciate your work man. Hope working on the Oreo builds helped a little in bringing Pie. We saw a glimpse of the huge efforts you made to bring Oreo and you keep pushing through.. Hope you're getting enough sleep n rest.
---------- Post added at 11:13 AM ---------- Previous post was at 11:08 AM ----------
ravedave2005 said:
Very exciting news!
question: Why are you working on Android 9 instead of jumping to Android 10? (i think i saw in the other thread that you already managed to boot it up on your tablet)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83888223&postcount=686
orangpelupa said:
Awesome! Btw encryption is listed as not working, does this mean android adoptable storage won't work?
Click to expand...
Click to collapse
Yes, unfortunately it doesn't work ... I guess it's working in the same way like in LOS 15.1.
I'll spend a few days in the near future to see why it doesn't work and maybe I'll find a solution.
Half Alive said:
Been using it for half a day now. I'm amazed that it's not laggy/buggy for a testing build.The build is fluid and smooth. I thought it'll random reboot every 5 minutes. No force closes or reboots until now. I might be spesking too soon though.
For rotation I used *rotation control* app from the play store and the controls are pinned in the notifications.
And Because it felt that stable I went and installed magisk and safetynet passed with the same steps explained in the Oreo thread.
Pie gestures are there for who cares about it. And you can enable A10 gestures with magisk and an app.. You can google (Android 10 gestures for android pie) and it's worth it tbh.
ofc If I encounter any bug first thing I'd do is removing magisk.
Appreciate your work man. Hope working on the Oreo builds helped a little in bringing Pie. We saw a glimpse of the huge efforts you made to bring Oreo and you keep pushing through.. Hope you're getting enough sleep n rest.
Click to expand...
Click to collapse
Thank you very much for your feedback
Update !
All sensors are working now on LOS 16.0
Hi !
Fingerprint sensor it's also fixed right now
Unfortunately the camera does not seem to be able to activate very easily ...
Starting now to build Android 11 , Lineage OS 18 ... if I manage to boot successfully, I guess I'll abandon this project ( and also I'll skip Android 10 ) and I'll start working on the last Android !
Why Android 9 without Camera working, instead Android 11 without Camera working, right ?
Anyway, I'll keep you updated ...
Hello,
First of all, I want to thank you for your amazing work. I really appreciate it.
Bugs in my btvdl09:
1) My bluetooth keyboard (logitech k380) connects but the tablet suddenly shuts down and boots into eRecovery. I'm having the same issue in LOS 15.1 and mentioned this issue in the thread. For LOS 15.1 I managed to resolve the issue by flashing your boot_lte_4.3.img kernel but I got the well-known wifi + bluetooth speed problem back!
The Google drive links of console-ramoops-0 and dmesg-ramoops-0 files (I don't know how to attach files to posts in threads.):
https://drive.google.com/file/d/1ObE1tOuG-5y50rDNMh5ZCJE6MrQP2cs8/view?usp=drivesdk
https://drive.google.com/file/d/1Oi5Od8U3If28GszdlRuZ6r8FNbJ58DPK/view?usp=drivesdk
2) When I insert a flash drive, everything works fine but as soon as i unplug the flash drive, it suddenly shuts down.
The links of console-ramoops-0 and dmesg-ramoops-0 files:
https://drive.google.com/file/d/1OskZOuvi0cc6nxI2fKNga9lamJEF5l6S/view?usp=drivesdk
https://drive.google.com/file/d/1OuHnnerAwUema7ufClNibt9XnByIIhLw/view?usp=drivesdk
3) I noticed that the display becomes snowy from time to time. It happens often under rather heavy tasks like surfing the web with 15 tabs open or installing something etc.
Below is the log file and a screenshot of the incident.
https://drive.google.com/file/d/1pp1CjEYiV-nvrfetfauQ1okFwsSBIEuk/view?usp=drivesdk
Userusing said:
Hello,
First of all, I want to thank you for your amazing work. I really appreciate it.
Bugs in my btvdl09:
1) My bluetooth keyboard (logitech k380) connects but the tablet suddenly shuts down and boots into eRecovery. I'm having the same issue in LOS 15.1 and mentioned this issue in the thread. For LOS 15.1 I managed to resolve the issue by flashing your boot_lte_4.3.img kernel but I got the well-known wifi + bluetooth speed problem back!
The Google drive links of console-ramoops-0 and dmesg-ramoops-0 files (I don't know how to attach files to posts in threads.):
https://drive.google.com/file/d/1ObE1tOuG-5y50rDNMh5ZCJE6MrQP2cs8/view?usp=drivesdk
https://drive.google.com/file/d/1Oi5Od8U3If28GszdlRuZ6r8FNbJ58DPK/view?usp=drivesdk
2) When I insert a flash drive, everything works fine but as soon as i unplug the flash drive, it suddenly shuts down.
The links of console-ramoops-0 and dmesg-ramoops-0 files:
https://drive.google.com/file/d/1OskZOuvi0cc6nxI2fKNga9lamJEF5l6S/view?usp=drivesdk
https://drive.google.com/file/d/1OuHnnerAwUema7ufClNibt9XnByIIhLw/view?usp=drivesdk
3) I noticed that the display becomes snowy from time to time. It happens often under rather heavy tasks like surfing the web with 15 tabs open or installing something etc.
Below is the log file and a screenshot of the incident.
https://drive.google.com/file/d/1pp1CjEYiV-nvrfetfauQ1okFwsSBIEuk/view?usp=drivesdk
Click to expand...
Click to collapse
Ok, I know your issues, unfortunately I can't do anything to fix your bluetooth keyboard.
New Update !
The links from OP are removed and will be updated asap !
You can download from here a second test of LOS 16.0 Android Pie .
Changelog:
All sensors fixed
Fingerprint sensor fixed
Downloads :
lineage-16.0.0-btv.zip
boot_w09.img
Thank you very much for your attention !
Did a total wipe, 9.0 nano gaaps, booted fine, restoring programs now, thanks!
friedsonjm said:
Did a total wipe, 9.0 nano gaaps, booted fine, restoring programs now, thanks!
Click to expand...
Click to collapse
OK, adoptable storage does not seem to work; formats card to 20% then reboots. Have to create partition on SD card using my PC, then format SD card to portable storage on M3 I am not able to download books using Amazon Kindle, I've uninstalled and reinstalled, won't download to main or SD Card. Other apps seem able to download OK Kindle error is 'Device Storage is Full' 19GB free on main, and 32GB free on SD Card
EDIT: And, I missed the part about the new TWRP version... time to start over.
OK, starting over, have confirmed that adopted storage still does not work.
SIM fixed right now on LOS 16.0 Android Pie !
Info not concerned to the WiFi devices.
The fix will be added to the next update !
Wooow.. U did it Los 16 for the M3...
Thank u so much for your hard work...
OK, new TWRP, fresh app installations, SD Card as portable storage, same problem with Kindle (on internal storage) being able to download.
EDIT: Apparently, when Kindle was restored, it did not automatically get storage permissions. Fixed that, and now working fine!
Will now try to download a Google Maps 'offline map' to internal.
This is strange... gboard installs, but voice typing does not work. Have checked permissions, that's not the issue. When I try to use it, says 'initializing' then that stops and does not allow voice input.
The problem may be that I don't have 'Voice Typing' showing under setting, even though gboard is installed... maybe because I used pico gaaps? Thinking about installing a larger package...
EDIT: Downloading the Micro GAAPS package added voice typing back into the system... I've turned on all permissions for board, set Google Voice typing to 'on,' and still not working.
I'm open to suggestions!
friedsonjm said:
This is strange... gboard installs, but voice typing does not work. Have checked permissions, that's not the issue. When I try to use it, says 'initializing' then that stops and does not allow voice input.
The problem may be that I don't have 'Voice Typing' showing under setting, even though gboard is installed... maybe because I used pico gaaps? Thinking about installing a larger package...
EDIT: Downloading the Micro GAAPS package added voice typing back into the system... I've turned on all permissions for board, set Google Voice typing to 'on,' and still not working.
I'm open to suggestions!
Click to expand...
Click to collapse
Well, on Android 9 our hal Audio ( we still using stock hal Audio from EMUI 5.x, Android 7 ) it's not fully working ... in fact wasn't working at all at beginning but I managed to find a hack to enable audio working but only partially as you can see !
Headset and also voice call on LTE devices it's not working due to this issue ... and ofcourse your related audio issues !
I'm sorry I wasn't clear from the beginning .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello everybody,
If you haven't heard it already, LineageOS 17.1 (Android 10) finally arrived officially with LineageOS Recovery
Links:
Samsung Sensor (s3ve3gjv)
Sony Sensor (s3ve3gxx)
Dual Sim (s3ve3gds)
Note: Use Magisk for root. This rom discontinued because of LineageOS 18.1 Releases.If you want to use LineageOS 18.1 or 16 (LineageOS 16 is discontinued too for the same reason) here is the link:
LineageOS 18.1
LineageOS 16
Version Information
ROM OS Version: 10 Q
Status: Stable
Created: 2021-01-25
Last Updated: 2021-10-17
thank you for your hard work u is an example of excellence
Does anyone have any comment on this Rom? Any bug report or something else? How does it compare with lineage 16?
it does reboot sometimes out of the blue
and it Discharge too quickly and if you want to charge the phone you have to close it or shut it off and youtube app keep loading
Dede525 said:
Does anyone have any comment on this Rom? Any bug report or something else? How does it compare with lineage 16?
Click to expand...
Click to collapse
I found some bugs on this rom
-Wifi Direct not working
-Reading mode not working
-Vibration not working on notifications
Hi thanks for the Rom.
I have the dual SIM (s3ve3gds).
Anyone has problem: very slow charging and buggy charging like need to restart to start charging?
I just installed the new ROM. Works great so far. Thanks a lot to the devs!
error bluetooth and slow charge . how fix error ?
I haven't voice during a call on both simcards for dual sim version. have you any idea for this problem?
hello, is working good this version of Lineage 17? It is okey for every day use? I'm steel on the LOS 16..
I would like to install lineage-17.1 (s3ve3gxx) on my GT-I9301I but the bootloader doesn't match the version the installation guide of the LineageOS Wiki demands:
Your device must be on bootloader version GT-I9301I = I9301IXCUARA1 […], otherwise the instructions found in this page will not work.
Click to expand...
Click to collapse
The Software-Update of the Stock Rom says I have already the newest Version installed but the Bootloader is I9301IXXUAQL1 (Baseband Version I9301IXXUAPG1).
Can I flash Lineageos with that bootloader?
If not: How do I get the bootloader I9301IXCUARA1 on my device?
According to this page:
Samsung GT-I9301I Galaxy S3 Neo - Sfirmware.com
Download the latest version of Samsung firmware GT-I9301I for your region for free. Please go to the firmware download page.
sfirmware.com
The firmware / bootloader for I9301IXCUARA1 appears to be specific to Greece country model.
Speaking from my experience only:
Since I am using a different country model, I did not pay attention to that at all.
However, I am not using Lineage Recovery. Rather I am using TWRP as recovery:
TWRP for S3 Neo: https://twrp.me/samsung/samsunggalaxys3neo.html
So I am not exactly following 100% of all the instructions in LineageOS Wiki. You mileage may vary though.
Hello everybody! There are many combinations in the mobile network settings that are not supported by our smartphone. For example, LTE, CDMA etc. Is it possible to remove networks that are not supported by the device, so as not to confuse the user? Thanks
I've been using LOS16 until some days ago, being reluctant to try LOS17.1, given how "subversive" the switch from LOS16-LOS17 was done (and I was missing @Humaxxx ). However, it looks working, but might need some fine tuning.
First the bad news:
- the issue with the WiFi driver is still persisting from LOS16 - if WiFi is connected on 2.4GHz and the BT is active, connected to a BT Headset and in use during a normal GSM call, it's enough to send a ping from the phone (ADB or a console) to the router or Internet (or initiate some traffic manually - update weather) and the WiFi connection bounces (disconnects - reconnects). This doesn't happen if the phone is connected on WiFi 5GHz. I reported this in the LOS16 thread some time ago, but at that time I thought it's only happening in VoIP applications while on 2,4GHz and using BT audio, it turns out a ping is enough to cause the issue. And, it looks like Wifi 2.4GHz and BT Audio (BT is also on 2,4GHz and from the same chip) cannot get used both at the same time, WiFi bounces.
- then BT Audio is still suffering interrupts randomly- loosing the microphone output, still able to hear the other party I'm speaking with. I noticed that this happens more often while moving fast around the phone (phone on the desk) or in narrow places like corridors or room corners- reflections/interference? Should be handled properly by the driver/firmware. It doesn't happen on stock ROM (stock driver/firmware).
- the LOS loading is faster, but as soon as it reaches the SIM PIN dialogue, after entering the PIN, it hangs a few dozen seconds. By the time it shows the unlock screen, the screen is already timing out - more of an annoyance.
- on the first run Android didn't copy my contacts from the SIM Card into the phone memory, I had to use an external App for this
- TWRP twrp-3.3.1-1-s3ve3g (the last one) is not compatible with Android 10, thus, it creates the backup OK, but it corrupts the name of the SDCard (corrigible manually - reformatting the SDCard on an external system) and what's worse it soft bricks the phone after restoring a backup. But there is a workaround - just tested it now and it's 100% working on the S3 Neo. You need to fix the root filesystem after the restoration, and someone has packed a simple script for doing so into an image that you need to install immediately after restoring the backup (don't exit TWRP!) and BEFORE the first reboot:
fix_rootfs_label
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
and the XDA Thread from where I got it:
[ROM][I9190/I9192/I9195/L520/R890][Unofficial][10.0.0] LineageOS 17.1 for S4 Mini
Android 10 is here! Took a while, but here's Lineage 17.1 builds, based on Android 10. Everything should work AFAIK, but let me know if something doesn't. If you run into problems installing Gapps, you might need an updated TWRP build. It needed...
forum.xda-developers.com
Some other threads discussing how TWRP cannot work (yet) with Android 10:
Softbrick after Restore of TWRP-Backup of lineageOS 17.1 (Galaxy Note 3 SM-N9005)
I never had problems when restoring TWRP-Backups on my Galaxy Note 3 SM-N9005 while running lineageOS 16 (rooted with Magisk). During the last weeks I quite often (approx. 7 times!) installed lineageOS 17.1 - which runs without any problems...
forum.xda-developers.com
TWRP restore and Lineage 17.1
I have TWRP 3.4.0.1 and I have recently installed Lineage 17.1 Before the Lineage instalaton I made a backup of my Stock Android 6.0. My installation Lineage 17.1 + gapps pico 10.0 was straightforward but I seem to be havinga problem in using...
forum.xda-developers.com
Full Nandroid Backup Solution for LineageOS 17??
I got Lineage 17 w/ Magisk root running now neat and great and I want to perform a full NANDroid Backup. After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM...
forum.xda-developers.com
tips for preserving twrp from Pie to Q
hi i'm not an expert so sorry maybe for foolish question but coudn't find a clear answer yet.. i'm still on pie and twrp 3.3.1.1; i'd like to upgade to ten but preserving twrp (maybe upgrading to 3.4.0 if necessary) which are the steps to keep...
forum.xda-developers.com
- some cosmetics: the trebuchet icons are HUGE and too close to each other on the Homescreen. When choosing some more condensed Grid, it won't apply to the applications drawer, but only for the Homescreen (really dumb)
- then, for the Dark Theme - the black background for the Settings, Phone App, Messages, Application Drawer is actually dark grey and not "OLED-friendly" pure black
- oh, just noticed, the notification LED doesn't change the color while the phone charges over 80-90% if the screen is off. Only after waking up the screen, then the LED changes the color
Now the good news, LOS17.1 looks stable and working fine - using it extensively for a few days now - cheers to the devs!. Worth mentioning that I started with lineage-17.1-20210503-nightly-s3ve3gxx-signed.zip and I flashed it over LOS16 - like:
- booted the phone in TWRP
- went on Wipe -> Format Data
- then again on Wipe > Advanced Wipe -> and wiped system & data & cache & Dalvik cache
- then got into the Install menu and chose the lineage-17.1 file from the SDCard and flashed it & rebooted
- that's it
Finally:
- I'm still restarting the phone after a full charge, as it was advised under LOS16, not knowing if the issue with the proper sleep/doze mode was resolved in LOS17.1
- there was a post in this thread where a user complained about "Slow charging". I saw that status message myself after the first LOS17.1 reboot, but it vanished after I started configuring the phone and performing some more reboots. Now it says "charging". I guess it's some default thing from Android 10 - just telling that the phone isn't capable of fast charging.
- then , recently there was some exchange related to the boot loader version required for LOS17.1. Well I suppose it's the same required for LOS16 - the I9301IXCUARA1 from the Greek ROM:
I9301IXCUARA1_I9301ICOSARA1_I9301IXXUAPG1_HOME.tar
I have this boot image version from before I started using LOS16. Besides, you might need to flash that stock ROM several times - or use some App to check if the boot was updated after the first flashing. And, that Greek ROM is heavily bloated (COSMOTE mobile operator), but that shouldn't bother anyone, it's just useful for the latest boot loader, anyway you flash LOS17.1 over it
Some updates:
- managed to find a better Homescreen Icons fit/aspect ratio by choosing the 7x5 Grid (need to scroll down to be able to see the option - well hidden). On 6x6 Android will try to arrange the lower icons (Phone/Messages/Camera) automatically from left to right (alphabetical order) and it won't stop
- the default font is also really tiny, even for my (good) eyes, I set the font on Large now
- the charging LED does turn to a different color after charging the Battery over 90%. It looks like the Homescreen editing messes up the whole Android and I'd advise to restart the phone after goofing around with the Homescreen (inconsistent behavior there when editing - deleted icons reappearing, auto arrangements, etc.).
- the Dialer - Favorites Tab doesn't get populated, it only shows two of my contacts that are starred.
- lock screen is activated immediately after the screen turns off, regardless of the waiting time I configured
hi MehmetSaitTR
i have S3 neo Dual Sim (s3ve3gds) gt-i9300i version android 4.4.4 bootloader i9300ixxsbpf1 twrp 3.3.1.1
i need tutorial to flash my phone with this lineage-16 or last lineage-17 ( sdcard 16 go )
thx
hi i flashed the rom
but there is no signal! in settings it says no sim card
i have flashed this file via odin: https://shell.boxwares.com/Download.aspx?L=1716
nothing happened after that
any help?
thanks
MehmetSaitTR said:
Hello everybody,
If you haven't heard it already, Lineage os 17.1 (Android 10) finally arrived officially with lineage os recovery
links:
Samsung Sensor (s3ve3gjv): https://download.lineageos.org/s3ve3gjv
Sony Sensor (s3ve3gxx): https://download.lineageos.org/s3ve3gxx
Dual Sim (s3ve3gds): https://download.lineageos.org/s3ve3gds
Note: Use Magisk for root
Click to expand...
Click to collapse
A big thank u to u !! I bought 6 NEOs on ebay (~30€) and flashed lineage on it, change (new) battery, bought new display shelter (tempered glass), used cases and sent the phones to my relatives in west africa. All are very happy with the phones ! All in all for every phone I had to pay ~50€. Here in germany the 3G frequency is more and more unsupported till the end of the year - but in west-africa it is still possilble to use and not switched off. So: your work makes active recycling possible and second gives people in a developing country the first chance for being connected digitally. (And I am a working class guy; I cannot spend so much money for a new phone ...) My wife is now connected by video calls and this has an amazing (voice- and video-) quality. Thank u very much !
WiFi doesn't seem to like staying connected, for too long.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.0 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads
Here
Flashing instructions
Here
Sources
LineageOS
I was struggling with passing safetynet + cts in particular but in the end this seems to have worked (if anyone is sturggling with this):
- magisk 24 + zygisk + hide magisk app
- denylist: google play services cms + cms.unstable
- universal safetyfix 2.2.1
- hide props: Google Pixel 5 A11
What Magisk modules are working in this ROM?
Guaymas said:
What Magisk modules are working in this ROM?
Click to expand...
Click to collapse
I'm using MagiskHide Props Config, Systemless Hosts and Viper4Android. Magisk 23.
Does the 64 megapixel camera work? ANX bootlooped my LineageOS 17.x unofficial build nomatter what. I've just flashed the latest MIUI to update to Android 11 before flahing this, and it's horrible. Apart from the camera working, which is amazing.
Revelle said:
Does the 64 megapixel camera work? ANX bootlooped my LineageOS 17.x unofficial build nomatter what. I've just flashed the latest MIUI to update to Android 11 before flahing this, and it's horrible. Apart from the camera working, which is amazing.
Click to expand...
Click to collapse
This build didnt support anx, which version you install Will gave bootloop, gcam now eis video work
Media speaker volume is too low
Any fix for that?
Viper4android Magisk module worked for me.
godjob said:
This build didnt support anx, which version you install Will gave bootloop, gcam now eis video work
Click to expand...
Click to collapse
Which gcam has EIS?
Hi there I've got redmi 9s and just successfully installed lineageos 18.1
It's working fine but any messaging app ( for example telegram/ signal) are able to preview and select pictures from the gallery but not send/ attach them to any message.
If sending Files, Contact Cards or even the images as files in uncompressed form, it works, but the Gallery Function seems to have a problem.
It just gives a red error signal but won't Even try to upload pictures although I believe the apps have the necessary permissions ( access to storage)
Any ideas/ suggestions / help on how to approach this bug / where to start the trouble shooting?
I found something that could help me get on the right track to fix this issue, it seems that perhaps it has to do with a new access right scheme in Android 11 (https://developer.android.com/about/versions/11/privacy/storage)
I found some User Messages about this in Bug Reports.
Does somebody have an idea for a workaround, or how to change this in the current lineageOS Version?
Here are some quotes from the Bug Reports, I will provide the links to the threads further below.
Thanks for your help.
P.S.: Just to clarify this problem for me is including the option to send images from the gallery function, to save photos to gallery and to auto-save photos to gallery.
"There's a limit introduced in Android 11 called "Scoped Storage". This is the reason."
"This! This right here is the deal. Telegram is not adjusted for the new access right scheme. It is only allowing media-folders."
"You're right, they just moved "Telegram" folder from root of sdcard to another folder that they have permission to write there but it's not visible to user. I think auto-save option only removes ".nomedia" file from "Telegram" folder so media will be visible in gallery when Telegram is in /sdcard/Telegram, but with scoped storage it's moved to /sdcard/Android/org.telegram.messanger so it won't be visible even without ".nomedia". instead they should save media in /sdcard/Pictures/Telegram when auto-save option is on."
"Attention! Perhaps due to restrictions on Android 11 on access to the "Android - data" folders, media files from Telegram are not saved to the gallery."
"I suspect it relates to the way media-folder access was changed in the newer Android versions (for security reasons)"
[Android 11+/SDK 30+] Auto save to gallery does not work
Despite the fact the 'Save to Gallery' option is enabled in Settings > Chat Settings, still I don't see media in my phone's gallery. Steps to reproduce 1. Enable 'Save to Gallery' in Settings > Chat Settings 2. Open any chat where you see media 3. Check…
bugs.telegram.org
Automatic saving of incoming photos doesn't work
Workaround Disable Automatic Media Download and manually download the images. Automatic saving of incoming photos doesn't work, after the February update (v 7.5) Sometimes random old photo from telegram chat is downloaded to the gallery. Steps to reproduce…
bugs.telegram.org
Manual "Save to gallery" command does not work
Steps to reproduce 1. Open any chat 2. Select a picture or a video, press "..." and choose "Save to gallery". 3. Notyhing is saved to gallery. Device info Telegram Android 8.2.1 (24627), Samsung Galaxy S20 FE 5G, 11 R? (30) Telegram Android 8.2.1 (24627)…
bugs.telegram.org
I was thinking that maybe if I moved the folder or designated it as a media folder, maybe could work? Open for any help and suggestions! Thank You Community!
starseedsawake said:
Hi there I've got redmi 9s and just successfully installed lineageos 18.1
It's working fine but any messaging app ( for example telegram/ signal) are able to preview and select pictures from the gallery but not send/ attach them to any message.
If sending Files, Contact Cards or even the images as files in uncompressed form, it works, but the Gallery Function seems to have a problem.
It just gives a red error signal but won't Even try to upload pictures although I believe the apps have the necessary permissions ( access to storage)
Any ideas/ suggestions / help on how to approach this bug / where to start the trouble shooting?
Click to expand...
Click to collapse
dereference23 said:
Flashing instructions
Click to expand...
Click to collapse
Best camera option for the 64mp note 9 pro (joyeusE)?
I'm thinking gcam port 8.3 for the note 9 pro max?
hmm?
i already did a clean reflash and it didn't fix that problem... assuming that you meant for me to reflash with your reply?
It's a great rom, but battery light brightness level doesn't change when i move the slider. Can you fix that?
starseedsawake said:
hmm?
i already did a clean reflash and it didn't fix that problem... assuming that you meant for me to reflash with your reply?
Click to expand...
Click to collapse
Did you flash from the stated stock ROM version?
starseedsawake said:
hmm?
i already did a clean reflash and it didn't fix that problem... assuming that you meant for me to reflash with your reply?
Click to expand...
Click to collapse
I'm having the exact problem with Telegram app..and also some other Apps are behaving strange.
Please let me know if you found any solution.
I did clean flash, gapps and without gapps, problem is the same. I'm on latest global curtana android 11 firmware (before flashing Lineage OS).
@DyXen @starseedsawake
Just wanting to say that I can post media in messengers like Telegram without issues.
My setup:
- Curtana
- MIUI rom before installing LOS: curtana_global_images_V12.0.4.0.RJWMIXM_20210723.0000.00_11.0_global
- No firmware updates after that
- Latest LineageOS recovery
- Latest LOS
- Magisk
Maybe this rom just doesn't work with the latest firmware? I'd try it out, but it just works too nicely to throw it all away. Maybe give it a try with the MIUI rom from above!
@dereference23
I feel like "rom version that needs to be installed before flashing LOS" is really something that should be part of the lineageos install instructions. It's almost always missing, or vague ("Latest Android 11 firmware" etc.). Every other phone I try to install LineageOS on gives me some kind of trouble that can usually be solved by downgrading the firmware. What MIUI rom where you on before flashing? Can you add that info to the los install page?
But anyways really great work! Absolutely smooth and bug free for me. Thank you.
Last but not least: If anyone got a GCam or ANXCamera version that supports 48MP (or 64MP for those with the better cameras) on this rom let me know! That is literally the only thing I still miss.
I always install latest firmware when upgrading LineageOS and have no problems.
I coudn't find any camera port that worked to even access the different lenses, let alone 64mpx. Note 9 Pro Global, from LineageOS 17.x to joyeuse_global_images_V12.5.3.0.RJZMIXM_20211223.0000.00_11.0_global_adcfb0b103 then this + MindTheGAPPs. Lineage 17.x unofficial worked with OpenCam for me but with no 64mp. Have gone back to MIUI for now just for the camera. Everything else worked perfectly.
Maybe it's because I'm on Joyeuse not Miatoll.