Related
LineageOS 14.1 by ivanichFeatures:
3.4 kernel with latest patches
USB-OTG
Stable enough to be daily driver
Fully working camera
Bugs:
Major:
Minor:
Bt pairing
All LineageOS upstream bugs
Downloads:
CM14
GAPPS
Sources:
ivanich's GitHub
Changelog:
Kernel Changelog
ROM Changelog
TWRP Recovery:
Download
No more builds or development for this device. RIP
XDA:DevDB Information
LineageOS-14.1 by ivanich, ROM for the HTC Sensation
Contributors
ivanich, shantur
Source Code: https://github.com/ivanich?tab=repositories
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 1.27/1.29
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-10-11
Last Updated 2017-08-15
FAQ
Q. I've got bootloop when flashing using TWRP
A. Current TWRP is not fully compatible with cm14, you should flash ROM 2-3 times in a row to make it boot.
Do not use TWRP from https://twrp.me/ it will brick your phone - use this TWRP
Too good too be true!
Is this really stable to be used as daily driver already?
Any known bug?
What about disk space? Has anything changed compared to cm13? Could we use hinxnz's SD mods?
Thanks Ivanich!
Hi, can you please include this webview patch from opengapps into the ROM ?
http://opengapps.org/blog/post/2016/10/06/nougat-webview/
Thank you for your development!
andreipaval said:
Hi, can you please include this webview patch from opengapps into the ROM ?
http://opengapps.org/blog/post/2016/10/06/nougat-webview/
Thank you for your development!
Click to expand...
Click to collapse
No, I can't. Cyanogenmod devs can. And stop spamming with this crap.
bootloop when flashing using TWRP 2.8
not working
RoboDan918 said:
bootloop when flashing using TWRP 2.8
not working
Click to expand...
Click to collapse
Current TWRP is not fully compatible with cm14, you should flash ROM 2-3 times in a row to make it boot.
I flashed cm14 1011 version together with opengapps stock with a custom config (that definitely fits into /system), it boots fine, but after
the "Turn on cellular data" screen, I get "Google Play services keeps stopping" error and I can't get pass this screen.
I've tried opengapps from different days, it's always the same. Any advice?, maybe someone got the same error. Thank you.
If I use a nano opengapps then it works, but I'm not happy with this config, wasted space in / system.
andreipaval said:
I flashed cm14 1011 version together with opengapps stock with a custom config (that definitely fits into /system), it boots fine, but after
the "Turn on cellular data" screen, I get "Google Play services keeps stopping" error and I can't get pass this screen.
I've tried opengapps from different days, it's always the same. Any advice?, maybe someone got the same error. Thank you.
If I use a nano opengapps then it works, but I'm not happy with this config, wasted space in / system.
Click to expand...
Click to collapse
The problem is in Google WebView, CM14 not fully support it yet, just create gapps-config.txt and disable it (see in OpenGapps faq how to do it)
@ivanich
First time thank you for the ROME.
But with the builds from (02. - 05. - 11.) I have memory card problems, with the build of (01.10.) But does not change.
2 Problem (see picture).
Sorry for the bad english, all translated with Google.
ivanich said:
FAQ
Q. I've got bootloop when flashing using TWRP
A. Current TWRP is not fully compatible with cm14, you should flash ROM 2-3 times in a row to make it boot.
Click to expand...
Click to collapse
A when flash 2-3 times, need to wipe cache/dalvik or no? thx
After 2-3 times flash with TWRP finally done and no major bugs until today. All function rynning well and Smith just a bit hot when used the phone more then 30 minuets. Everything is well. Thx ivanic
[/url][/IMG]
[/url][/IMG]
Report
I can't flashing it.It has error(7).I'm using TWRP-3.0.M5.0.
How can I do it?
Now,my device is in bootloop.I will flashing back CM13.
Whoa, sensation got nougat? That was fast. Thank you for this rom ivanich. I would like to try it right now but I doubt my sister would allow me to play with her sensation. I will flash it in the future for sure. Your roms are always great, stable and fast. I loved them. I miss your cm11 roms. Those were good times I spent with sensation. Keep up with good work!
Chenye Jin said:
I can't flashing it.It has error(7).I'm using TWRP-3.0.M5.0.
How can I do it?
Now,my device is in bootloop.I will flashing back CM13.
Click to expand...
Click to collapse
Look in CM13 thread in the FAQ items, just try to install a couple of times. This is for now normal behavior.
already flash latest build. 10.22
so far sd card permision seem already fixed but need several testing..
minor bug still pointed out but still ok for daily driver..
thank you ivanich
On cm13 I used the Adoptable storage feature of Android, by adopting the SD card as "internal storage",
and I could move to the adoptable storage almost any app, there were very few that did not move.
But now on cm14 I adopted the SD card the same way, but I can only move very few apps.
I think that now only the apps which have in the AndroidManifest app location to external or auto can be moved.
Is it a bug in cm14 of a feature of Android 7 ?
andreipaval said:
On cm13 I used the Adoptable storage feature of Android, by adopting the SD card as "internal storage",
and I could move to the adoptable storage almost any app, there were very few that did not move.
But now on cm14 I adopted the SD card the same way, but I can only move very few apps.
I think that now only the apps which have in the AndroidManifest app location to external or auto can be moved.
Is it a bug in cm14 of a feature of Android 7 ?
Click to expand...
Click to collapse
I've hacked framework in cm13 in order to allow moving most of the apps to the adopted storage, looks like I need to do the same thing with cm14.
Wait for the next build...
What's the difference between the 'Adaptable storage space' and using 'Hinxnz SD-ext boot mods'?
Which one do you prefer? why?
Newest nigtly 23.10:
- Sd card issues has been fixed
- torch is working
- video recording(22.10)
Послато са Sensation уз помоћ Тапатока
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review.
Download Links
LineageOS:
Downloads: https://download.lineageos.org/d2vzw
Google apps addon:
OpenGapps: http://opengapps.org/ (you'll want a zip for the ARM platform, Android version 7.1)
HEADS UP: Be sure you flash the gapps package with your rom. If you boot your rom, then go back and try to flash gapps after the fact, you're gonna have a bad time.
Firmware:
Your best bet is to be on the MF1 bootstack/NE1 modem combo. Here's a flashable zip (this only needs to be done once): http://www.invisiblek.org/firmware/d2/d2vzw_MF1_firmware_NE1_modem.zip
Misc Links
Changelog:
Link: https://download.lineageos.org/d2vzw/changes/
Learn to build yourself:
Link: https://wiki.lineageos.org/devices/d2vzw/build
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[ROM][OFFICIAL] LineageOS 14.1 Nightlies for the Verizon Samsung Galaxy S3 (d2vzw), ROM for the Verizon Samsung Galaxy S III
Contributors
invisiblek
Source Code: http://github.com/LineageOS
ROM OS Version: 7.x Nougat
Version Information
Status: Nightly
Created 2016-12-05
Last Updated 2016-12-05
reserved
Hallelujah!
Is this the eighth or ninth life of this great phone?
@invisiblek, are there plans for the release of a Snapshot of CM13.0 for the d2vzw?
Congratulations on the "official" release!! Thank you for such an excellent and stable ROM for our ooooold, but no longer irrelevant, s3!
Nice job! Wich partitions can I mount as f2fs?
Just out of curiosity regarding the CM14.1...
Anyone having issue with internet connectivity specifically with the Play Store only (downloaded from Open GApps)?
Also, is anyone having issues with their external MicroSD. Though the external MicroSD can be viewed and can browse it, I'm Specifically stating the inability to execute, open, write to, etc...?
I had already sent the issues I'm having along with all my log files to @invisiblek and was curious as to any others experiencing the same/similar issues I experienced.
Thank you all for your time and understanding!
Thank you @invisiblek and other contributors. This is a great rom for this old phone. My DD is a LG G4, again, I went back to that after three Note 7's and all that drama. It's sad when a years old Galaxy S3 is running the latest and greatest but my LG G4 is still on last years Android! Yikes
I'm only using the SGS3 as a Wifi device so I can't comment on Cell radio functions but it's very smooth and seems markedly faster than when I was last using it as a DD. The only issue I've had and it may not even be related to this rom... I wanted to use Chainfire's PryFi to stick it to Kohls and Walmart that use WiFi Mac trackers, but when I launch PryFi and turn it on, it almost immediately crashes no matter what I do. Wipe cache, dalvik, reset and I get the same thing.
Thanks for the great work. Much appreciated!
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Ibuprophen said:
@invisiblek, I'm reading elsewhere that the CM14.x should be installed first, then after the setup is accomplished, reboot back in to the recovery, then flash the GApps package.
Is this correct?
I just wanted to be sure in regards to the unconventional method of flashing the CM and the GApps together then reboot.
But, as you may know, after installing the 2 conventionally, I'm having trouble with the Play Store as well as the External MicroSD after setup.
I'd really appreciate your confirmation.
Thanks a Bunch!
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Master Cylinder said:
I had a problem installing the first time - I put build+Open GApps Aroma in the que and when the Aroma install was supposed to come up everything went black but the phone was still on. I flashed one and then the other without booting and it booted into initial setup normally.
But, I created a Nandroid with TWRP 2.8.7.0 and tried to restore the last Unofficial 14.1 build nandroid that worked normally but I couldn't get the sim card to work. Same when I tried to restore the new official. I tried numerous different ways to hold my mouth but it would never mount the SIM and settings was crapped out. I was able to restore my last MM nandroid and have it work normally. I've just switched to the latest TWRP 3.x.x.x. Don't know if that has anything to do with it....
I'm clean installing the new official again! It got stuck on boot (wrong boot animation, too) but pulling the batt and restarting, it went normally. (My Tibu settings were in the /data wipe. Gotta mount one and pull them )
Click to expand...
Click to collapse
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Ibuprophen said:
Thank you for your response!
I always had the latest TWRP 3.0.2-0 installed.
I flashed the CM14.1 20161207, Open GApps Pico 20161207 and, at first, SuperSU 2.78 Stable then when I retried a fresh install, i used SuperSU 2.78 SR5.
The same issues occurred (primarily) with the Play Store not being able to access the Internet the Internet and being able to see everything on my External MicroSD but, still not being able to read, write, move copy, install, etc...
I did see, during the initial bootup where you have the initial setup of CM & Google, the Google setup went fine but, I did notice that the carrier name reflected "no service" or "unknown" or something similar. I had ventured in to the network settings and did see everything needed in there so I didn't give it another thought.
To be honest, my opinion is that i really don't think that the release of the OFFICIAL CM14.1 Nightly was not ready yet.
I had to E-mailed @invisiblek the list of issues along with the installation log files from both the CM14.1 and the GApps but, I haven't even received an acknowledgement of at least a thank you.
@invisiblek is listed as the primary point of contact for Cyanogenmod and other than e-mailing him along with posting the issue here to his attention, I'm not sure how else to report any issues/feedback to Cyanogenmod... Cyanogenmod doesn't really pay attention to their own forums that has resulted in most individuals not even bothering with posting anything there anymore.
I'm personally going to put CM14.1 on hold till there's either some indication of improvement or finding some information reflecting my issues with some fixes, tryouts, solutions, etc...
I'm real disappointed with this...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Stealth111 said:
I'll attempt to try to help with some of the issues here, as I have direct contact with invisiblek pretty much daily. First I will start off with a few questions, NOT poking, just asking, this also may address some previous posts as well... You have a verizon SCH-I535 correct, and not another variant? Just making sure. And to start you wiped data in TWRP (wipe to install new ROM option basically). Told it to flash your 12/07 build? Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps? After it rebooted, it sometimes takes a while to get the setup to actually start and display, sometimes it goes to a black screen for minutes, but be patient, it will come.. At that point in time, it will initialize sim card and be connected, as this was my experience on all 3 of my S3 phones in my household. Then proceed through setup...
Is your external card formatted as "portable storage", or is it formatted as "Adopted storage". Also what type of filesystem do you have the card formatted with? What file manager are you using to try to access your card with? There was some expected changes that might have to be worked out as the "unofficial" roms were running Selinux in permissive mode, and the "official" roms are running it in Enforcing mode. That is bound to cause some small differences in the way the 2 roms behave. Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom? There might be some issues being caused by that in itself.
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials. Also, I have had limited luck with the built in file manager. I have used ES File Explorer forever, and it continues to behave well on this rom. Also, even if you are going to nandroid back and forth between official and unofficial, it is best to do a wipe of DATA before the nandroid... As far as the play store goes, I haven't experienced any lack of connectivity. I do get very small intermittent blips where it seems like it isn't connected for a second or 2, but it is very rare, and it has always been like that as far as I can remember.. Part of the reason that is for me is because I use a network extender, and it has always been the achilles heel with CM.
Try going into TWRP, do the "wipe to install new rom", add the cm zip, and ALSO add the latest "Opengapps arm 7.1 pico or micro" (your choice) build into the zip queue so that they are flashed in succession. Let it rip, and see if that offers you any different results. After you get it initially setup, go into developer options and enable root as needed. Give it a run and see what issue are still present, if any. I am surprised to hear some of these issues, as between myself, my kids, and a handful of friends, everyone is super stoked at how well these early builds are running... I myself have less than 3 reported issues from friends that we are looking into, and they are all just cosmetic bugs so far... I will be glad to try to help in any way possible..
P.S. There have been quite a few things resolved/changed between TWRP 2.8.7.0 and 3.0.2-0, I would highly suggest not only upgrading to the latest TWRP version, but also making sure you are on the firmware versions that are mentioned in the OP.
Stealth111
Click to expand...
Click to collapse
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Q: Is your external card formatted as "portable storage", or is it formatted as "Adopted storage".
A: Portable Storage.
Q: Also what type of filesystem do you have the card formatted with?
A: VFAT
Q: What file manager are you using to try to access your card with?
A: Stock & ES File Explorer Pro
Q: Also, I need to ask why you are trying to install SuperSU on a rom that already has Root (and the ability to manage it) built into the rom?
A: I'm aware of the stock root manager but, i've always preferred SuperSU's root management.
I really appreciate your assistance and please don't hesitate to defer to @invisiblek if necessary.
Also, please keep in mind that I'm not in a race. Take your time because patience is a virtue...
Thank you very much!!!
I wonder if the GApps issue is the underlying issue. I hope @MastahF & @Rapper_skull is aware of and working on it?
Sent from my d2vzw using XDA Labs
Stealth111 said:
I know that personally BusyBox (I rely on it daily) will NOT install on the official for me, but installs fine on the unofficials.
Stealth111
Click to expand...
Click to collapse
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Ibuprophen said:
Okay... I tried to sort out and answer all the questions the best i could.
I also attached the log files. They are dated according to the Nightly releases.
Q: You have a verizon SCH-I535 correct, and not another variant?
A: Yes. I have an SCH-I535.
Q: And to start you wiped data in TWRP (wipe to install new ROM option basically).
A: 1) Factory Reset. 2) Wipe Dalvik, Data, Internal Storage, Cache and System. 3) Format Data. Then Restart Recovery back to TWRP.
Q: Told it to flash your 12/07 build?
Did you ADD the "opengapps 7.1 ARM Pico" build to the multiple flash option, or did you flash rom, then go back in and flash opengapps?
A: Install and select CM14.1 12/07 build then the Open GApps 7.1 ARM Pico. To add... I tried flashing the 2 above only, then tried the same 2 above with SuperSU 2.78 Stable, lastly the 2 above with SuperSU 2.78 SR5. All resulted with the same issues.
Click to expand...
Click to collapse
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
Click to expand...
Click to collapse
I have the same version as well. I go to the store, click install on the Pro version. It installs just fine... I then go in and open the program, it immediately asks for the needed root permissions, which I promptly give it, then I close the welcome message. When I actually then click install from within the program, it then tries to install for about 2 seconds and then says "oops, it looks like the installation was unsuccessful, maybe try a different location"....
Who knows.... :laugh:
Other than that, I agree, purring like a kitten!
Stealth111
Master Cylinder said:
I installed Stericson BusyBox Pro using Google Play and it works fine! Lucky me!
I know this may sound funny but I've had this EXACT response from clean installs using the tiny GApps packages. Try one of the larger ones or the Aroma installer. (I know it's annoying if you want to keep all that crap off your phone ...)
As I said, I installed without using the qeue. I also wiped Dalvik/cache AFTER the installations, as per the OpenGApps instructions.
Oh, and my phone is purring like a kitten with 12/7 on it! XD
PS - Except for that dang restore issue. Scared to try it again but I gotta try it again eventually.
Click to expand...
Click to collapse
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Sent from my Pixel using XDA Forums Pro.
Ibuprophen said:
I tried the nano on one attempt thinking that pico was the culprit but, the same issue...
Sent from my d2vzw using XDA Labs
Click to expand...
Click to collapse
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Pierre2324 said:
Sorry to ask this again but wich partitions should be remounted as f2fs for better performance?
Click to expand...
Click to collapse
Here's a link that, i believe, will answer your question:
http://forum.xda-developers.com/showthread.php?t=2537119
Good Luck!
Sent from my d2vzw using XDA Labs
---------- Post added at 02:14 AM ---------- Previous post was at 01:54 AM ----------
Master Cylinder said:
I had the same problem with Nano. If you're gonna spend the time to do it, go big. Bigger rather than smaller.
Click to expand...
Click to collapse
There was a member in the GApps thread who had mentioned that he had a similar issue.
He stated that what worked for him was flashing a GApps Pico package on from about 30 days ago.
I believe that others had to flash their GApps packages from about 30 days ago had worked for them.
I know that this is an issue for many others who also reported it to the Dev(s).
I can't think of what in the world is going on...
Sent from my d2vzw using XDA Labs
Running smooth as ice.......only issue I've had was a single browser hicup. Incredible work, makes me smile knowing I have a newer version on my ancient phone than most of the $700+ flagship phones. Invisablek you sir are the man:good:
[ROM][4.4.4/4.3.1][Hummingbird][EMMC][UNOFFICIAL] LineageOS 11 & CM 11 & CM 10.2.3
Download link is found under the "Downloads" tab on the top left of this post / thread.
Or, https://forum.xda-developers.com/devdb/project/?id=22294#downloads
Changelog:
The 2017-12-09 build is a must need update. It contains the latest security patch and removed the browser for security reasons. The browser is now replaced with Lightning Browser +. lineage-11-20171209-UNOFFICIAL-hummingbird.zip
The 2017-12-10 build contains a needed update to the user interface instead of the userdebug interface. This is being added due to security reasons with the old browser and the userdebug interface. lineage-11-20171210-UNOFFICIAL-hummingbird.zip
The 2017-12-29 build contains, fixed fonts, fixed the boot animation file, and updated webview stuff. lineage-11-20171229-UNOFFICIAL-hummingbird.zip
The 2017-12-29 #2 build contains, removed Lighting Browser + because it crashes, and added a safer browser. lineage-11-20171229-UNOFFICIAL-hummingbird.zip
The 2017-12-30 build contains, removed Browser for crashing reasons (download your own browser). lineage-11-20171230-UNOFFICIAL-hummingbird.zip
The 2017-12-31 build contains, updated CM apps. lineage-11-20171231-UNOFFICIAL-hummingbird.zip
The 2018-01-10 build contains, updated security patch. lineage-11-20180110-UNOFFICIAL-hummingbird.zip
The 2018-01-16 build contains, fixed system apps, priv-apps, and framework. This update fixes the UI crashes after each reboot or shut down. lineage-11-20180116-UNOFFICIAL-hummingbird.zip
The CyanogenMod 11 2018-01-23 build contains, updated everything, this is the first release. cm-11-20180123-NIGHTLY-hummingbird.zip
The CyanogenMod 11 2018-01-23 build #2 contains, fixed boot animation on start ups. cm-11-20180123-NIGHTLY-hummingbird.zip
The LineageOS 11 2018-02-07 build contains, updated webview stuff, added .so files, updated CM apps, updated .so files, removed Lightning Browser+, updated the security patch, and added Prebuilt Chromium browser. (Thanks to @Android-Andi for creating Prebuilt Chromium browser. Which it can be found here, https://github.com/andi34/prebuilts_chromium) lineage-11-20180207-UNOFFICIAL-hummingbird.zip
The CyanogenMod 11 2018-02-26 builds contains, updated webview stuff, updated security patch, and updated CM apps. cm-11-20180226-NIGHTLY-hummingbird.zip
The Testing #1 build of CyanogenMod 10.2.3 2018-03-02 build contains, FIRST RELEASE.
cm-10.2.3-hummingbird.zip
CyanogenMod 11 2018-09-18: Updated CyanogenMod apps, updated webview stuff, updated security patch, fixed some security issues within the system, and added these unofficial builds changes into the change-log. cm-11-20180918-NIGHTLY-hummingbird.zip
CyanogenMod 11 2019-03-23: Updated security patch, updated webview stuff, and fixed some system security issues. cm-11-20190323-NIGHTLY-hummingbird.zip
XDA:DevDB Information
[ROM][4.4.4/4.3.1][Hummingbird][EMMC][UNOFFICIAL] LineageOS 11 & CM 11 & CM 10.2.3, ROM for the Barnes & Noble Nook HD
Contributors
secretwolf98, LineageOS, and CyanogenMod
Source Code: https://forum.xda-developers.com/devdb/project/?id=22294#downloads
ROM OS Version: 4.4.4 KitKat (KK) & 4.3.1 JellyBean (JB)
Based On: LineageOS 11 & CyanogenMod 11 & CyanogenMod 10.2.3
Version Information
Status: Stable
Stable Release Date: 2018-02-07 (LineageOS 11) & 2019-03-23 (CyanogenMod 11) & 2018-03-02 (CyanogenMod 10.2.3)
Created 2017-08-30
Last Updated 2019-03-23
@secretwolf98 This is a placeholder.... soon to be closed if nothing tangible appears. Why start a thread with no build to offer?
LenAsh said:
@secretwolf98 This is a placeholder.... soon to be closed if nothing tangible appears. Why start a thread with no build to offer?
Click to expand...
Click to collapse
I am going to add download link ASAP after school (about 1 hour I get home)
I had gotten kinda busy. Sorry
Don't suppose you could do an Ovation build as well?
twiztid_ said:
Don't suppose you could do an Ovation build as well?
Click to expand...
Click to collapse
Sure, let me finish Acclaim build, and I will start Ovation build.
But I don't have a Nook HD+, so I need you to help me test it.
twiztid_ said:
Don't suppose you could do an Ovation build as well?
Click to expand...
Click to collapse
Check your XDA messages. I had sent you a Ovation test build.
secretwolf98 said:
Check your XDA messages. I had sent you a Ovation test build.
Click to expand...
Click to collapse
Install went smoothly, and the system itself runs fine aside from a few long standing issues (Advanced Reboot -> Reboot to Recovery, plugging in the Nook will make it boot up).
Issues using this build vs verygreen's EMMC CM11 install 141129:
On initial boot it will prompt you to set up a Google account, even without a GApps package installed. This causes a CM Updater "crash" both with and without a Gapps package.
Both GApps packages I've tried have crashes on startup: PAGapps which worked on verygreen's (Now gives "There was a problem communicating with Google servers."), and OpenGApps ARM 4.4 Pico which had crashing issues before.
Amazon Underground (Amazon's App Store) crashes after logging in.
Given those two issues, it's hard to further test any other crashes/problems.
twiztid_ said:
Install went smoothly, and the system itself runs fine aside from a few long standing issues (Advanced Reboot -> Reboot to Recovery, plugging in the Nook will make it boot up).
Issues using this build vs verygreen's EMMC CM11 install 141129:
On initial boot it will prompt you to set up a Google account, even without a GApps package installed. This causes a CM Updater "crash" both with and without a Gapps package.
Both GApps packages I've tried have crashes on startup: PAGapps which worked on verygreen's (Now gives "There was a problem communicating with Google servers."), and OpenGApps ARM 4.4 Pico which had crashing issues before.
Amazon Underground (Amazon's App Store) crashes after logging in.
Given those two issues, it's hard to further test any other crashes/problems.
Click to expand...
Click to collapse
Would you by the chance have the CyanogenMod 11 Ovation Nightly 8-15-2016 build (latest one)? Maybe I can take some sources out of that.
***EDIT***
I had found latest build on, https://www.mediafire.com/folder/6f68b2wtf6db4/NookHD+
I will look into this problem. I will have another test build done later tonight or tomorrow.
Thanks for your feedback.
twiztid_ said:
Install went smoothly, and the system itself runs fine aside from a few long standing issues (Advanced Reboot -> Reboot to Recovery, plugging in the Nook will make it boot up).
Issues using this build vs verygreen's EMMC CM11 install 141129:
On initial boot it will prompt you to set up a Google account, even without a GApps package installed. This causes a CM Updater "crash" both with and without a Gapps package.
Both GApps packages I've tried have crashes on startup: PAGapps which worked on verygreen's (Now gives "There was a problem communicating with Google servers."), and OpenGApps ARM 4.4 Pico which had crashing issues before.
Amazon Underground (Amazon's App Store) crashes after logging in.
Given those two issues, it's hard to further test any other crashes/problems.
Click to expand...
Click to collapse
Test 2 is done. I had sent you link threw XDA messages.
secretwolf98 said:
Test 2 is done. I had sent you link threw XDA messages.
Click to expand...
Click to collapse
I haven't tested much, but so far: Flawless.
Again, no errors during install/boot.
For the second wipe/install I installed the PA Gapps immediately after LNOS (no reboot), setup went fine but with one minor hiccup; everything worked, but kept offering to set up my Google account after I had logged into it. I simply hit Skip and the setup continued as normal, and everything was fine including Google Account/Play Store. -- This may have been a one-time 'accident', I didn't try to reproduce it because it wasn't a significant issue.
I did a second fresh install with GApps, this time installed OpenGApps ARM 4.4 Pico, and had zero issues. Everything set up perfectly fine.
After booting to the 'desktop' I installed my cable TV provider's app and the SyFy app (TV Station), logged in to both, and played a show without any problems for either app (aside from my Cable provider complaining about USB Debugging, after turning it off it was fine). I don't have Netflix/Hulu, but it seems there are no apparent problems with codecs/DRM.
Thank you so much for your work, and super fast turn around on this!
What, exactly, is the value of putting this on our nooks instead of the current go-to ROM? I'm curious because I've been out of the loop with my nook for several months. Is this a more memory friendly but with the tweaks that the newer one has included, or is it just a matter of preference?
ieatabiscuit said:
What, exactly, is the value of putting this on our nooks instead of the current go-to ROM? I'm curious because I've been out of the loop with my nook for several months. Is this a more memory friendly but with the tweaks that the newer one has included, or is it just a matter of preference?
Click to expand...
Click to collapse
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
twiztid_ said:
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
Click to expand...
Click to collapse
That's what I was curious about. The M/N builds are great, but it just feels like the nook's showing it's age more with them. How does this new build rate against some of the now-dead KK builds? Does it feel newer, or is it just the latest release of the old stuff? Does the ROM use any of the newer tweaks from LNOS backported? Does it have that annoying screen flicker most older ROMs had? And how does youtube play on it (I have always had issues with it freezing during playback)? I might have to hop in line with you to be a tester for this on my ovation too!
ieatabiscuit said:
How does this new build rate against some of the now-dead KK builds? Does it feel newer, or is it just the latest release of the old stuff?
Click to expand...
Click to collapse
I'd say it's a "LNOSified" version of the CM11 ROM.
From the bit I've used it, feels just as good as the CM11 in verygreen's post... which is surprisingly good. I hopped back to 4.4 (well, 4.3, then 4.4) because the GUI of some apps I was using, and the UI itself at times, were feeling sluggish. I'm not sure I'd say it feels "newer" in the sense of KitKat vs Android L/M/N interface, but it does in terms of overall "snappyness" where things feel more responsive. I'm guessing it has some newer versions/commits of files, but that might be all.
The rest of your questions I'll answer without quotes to save on length:
I don't believe it uses any of the LNOS (or even CM) tweaks from 5.0+, but I don't know for sure.
I can't say how into this secretwolf98 wants to get, but so far I'm not sure if it "needs" any tweeks.
I never had the screen flickering issue untill Lollipop builds, and that was something Amaces fixed completely(?) in the M builds I think.
I didn't get to try out Youtube (yet), but I did try out my Cable Co.'s TV App (Live TV and On-Demand) and the SyFy app (On-Demand) and had no issues. I'll give that a shot tonight and give you an update on this post.
Just watched an 18ish minute video on YouTube, and didn't have any buffering issues.
twiztid_ said:
I'd say it's a "LNOSified" version of the CM11 ROM.
From the bit I've used it, feels just as good as the CM11 in verygreen's post... which is surprisingly good. I hopped back to 4.4 (well, 4.3, then 4.4) because the GUI of some apps I was using, and the UI itself at times, were feeling sluggish. I'm not sure I'd say it feels "newer" in the sense of KitKat vs Android L/M/N interface, but it does in terms of overall "snappyness" where things feel more responsive. I'm guessing it has some newer versions/commits of files, but that might be all.
The rest of your questions I'll answer without quotes to save on length:
I don't believe it uses any of the LNOS (or even CM) tweaks from 5.0+, but I don't know for sure.
I can't say how into this secretwolf98 wants to get, but so far I'm not sure if it "needs" any tweeks.
I never had the screen flickering issue untill Lollipop builds, and that was something Amaces fixed completely(?) in the M builds I think.
I didn't get to try out Youtube (yet), but I did try out my Cable Co.'s TV App (Live TV and On-Demand) and the SyFy app (On-Demand) and had no issues. I'll give that a shot tonight and give you an update on this post.
Click to expand...
Click to collapse
Nice, I might have to look into this more, and poke at secretwolf98 to see what I can learn. Thanks!
ieatabiscuit said:
Nice, I might have to look into this more, and poke at secretwolf98 to see what I can learn. Thanks!
Click to expand...
Click to collapse
If you want Ovation, I will be posting it here soon as a thread in XDA. Stay tuned!
twiztid_ said:
I haven't tested much, but so far: Flawless.
Again, no errors during install/boot.
For the second wipe/install I installed the PA Gapps immediately after LNOS (no reboot), setup went fine but with one minor hiccup; everything worked, but kept offering to set up my Google account after I had logged into it. I simply hit Skip and the setup continued as normal, and everything was fine including Google Account/Play Store. -- This may have been a one-time 'accident', I didn't try to reproduce it because it wasn't a significant issue.
I did a second fresh install with GApps, this time installed OpenGApps ARM 4.4 Pico, and had zero issues. Everything set up perfectly fine.
After booting to the 'desktop' I installed my cable TV provider's app and the SyFy app (TV Station), logged in to both, and played a show without any problems for either app (aside from my Cable provider complaining about USB Debugging, after turning it off it was fine). I don't have Netflix/Hulu, but it seems there are no apparent problems with codecs/DRM.
Thank you so much for your work, and super fast turn around on this!
Click to expand...
Click to collapse
Your welcome
ieatabiscuit said:
Nice, I might have to look into this more, and poke at secretwolf98 to see what I can learn. Thanks!
Click to expand...
Click to collapse
Here is the post link, https://forum.xda-developers.com/nook-hd/general/rom-lineageos-11-t3668779
twiztid_ said:
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
Click to expand...
Click to collapse
Here is the post link, https://forum.xda-developers.com/nook-hd/general/rom-lineageos-11-t3668779
twiztid_ said:
I'm using 4.4 because it feels faster than M/N builds, the response/loading times feel more snappy.
Click to expand...
Click to collapse
For me CM11 was great and fast but the lack of memory was more apparent than with current M/N builds. Typical is Firefox (with uBlock installed). With CM11 you can't sometimes even open single tab with some heavy page (like some long blog with lot of youtube videos) without running out of memory and crashing. Latest builds have zram swapping enabled and even a bit more physical memory available so Firefox works just fine even with many tabs. But yes swaping means it is sometimes slow when memory gets tight but it does not crash. Maybe CM11 with same memory layout and zram swapping enabled and tuned in same way would be even better? Haven't tried this build, maybe it already has some tuning like that?
Edit: This is with Ovation, most probably the memory pressure with Hummingbird is not so bad due to lower display resolution.
Code:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
AospExtended 6.7
Properties
Selinux mode: Enforcing by default
Build type: user
Gapps: not included
Known issues
Some users report non-functional mobile data after clean flash, reportedly works after manually adding APN or dirty flashing from Official AospExtended build
Notes
Dirty flash from Official ROM not tested, backup EVERYTHING before flashing!
Downloads
21.1.2020
Download
Checksum: a83c665feace3066580f2344af38fc1d
Older builds
14.12.2019
Download
Checksum: f44bdbc961fe2b64a281ec0785975f21
23.11.2019
Download
Checksum: a4043774306c86b3968c826b9ca1ba98
13.10.2019
Download
Checksum: d85208f4ead011dc0e9488b9591ac5d6
Working apps
OpenGapps
MicroG
Magisk
JamesDSP
Sources
ROM
Device tree
Kernel
Vendor
Credits
AospExtended team - ROM
dotOS team - device sources
@gadmei.tw - mobile data fix
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][MIDO] AospExtended 6.7, ROM for the Xiaomi Redmi Note 4
Contributors
Golbinex
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Based On: AospExtended
Version Information
Status: Stable
Created 2019-11-02
Last Updated 2020-02-04
Reserved
Changelog
21.1.2020
January security patches
14.12.2019
December security patches
23.11.2019
November security patches
Mobile data tryfix - @gadmei.tw
13.10.2019
Initial build
October security patches
Dirty flashed from AospExtended Official without issues.
:laugh:tks, :good::good:
Only upgrade OCT security patch on offical AEX Rom-0822-mido , right?
i will guess AEX 7.0(Android 10) release stable ver. in Jan 2020:laugh:
Any changes
Changelog
grvkrsaini said:
Changelog
Click to expand...
Click to collapse
3rd post above yours.
gadmei.tw said:
:laugh:tks, :good::good:
Only upgrade OCT security patch on offical AEX Rom-0822-mido , right?
i will guess AEX 7.0(Android 10) release stable ver. in Jan 2020:laugh:
Click to expand...
Click to collapse
Device sources are also different because official ones aren't updated at all, so maybe kernel version and behaviour will be little different.
martinknl said:
Dirty flashed from AospExtended Official without issues.
Click to expand...
Click to collapse
Same here. Rom works great and latest security patch is included. Thanks @Developer
A very good rom
Hello,
I've tried this rom, and it's a good idea , it' works fine !
Very thanks for the developers.
Great ROM
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
WareWareX said:
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
Click to expand...
Click to collapse
OTA is generally not included in unofficial build
WareWareX said:
I can't see the OTA updates section in settings, if this ROM will have updates in futute where can i download it?
Click to expand...
Click to collapse
Updates will be available in this thread, there will be probably one update per month.
Audio playing on multiple outputs
Hi All,
Firstly thank you very much for providing this ROM with the latest security fixes - everything important is working fine and I have also better battery life than in the AOSP Extended 8 ROMs.
However I have one problem that did not exist in the previous ROM. I use AirAudio (in combination with the Magisk AirAudio module) to stream any sound from the phone to a DLNA audio output. Usually when I activate the AirAudio streaming the sound on the phone stops and the output is redirected to the DLNA speaker. In this ROM though the audio plays on the phone and also on the DLNA speaker.
I contacted the AirAudio developers and they responded that this is a problem with an incorrect audio implementation in the custom ROM I'm using as they have seen this before. This is what they wrote:
-------
I assume you have a custom ROM, eg. Pixel Experience installed?
There are some ROMs around at the moment that have a broken implementation of the audio-driver.
Android-devices MUST only play the audio locally _or_ remote via AirAudio, this is defined by Google.
I think you have to wait for an update of your ROM or switch to another ROM like others did :-/
-------
Is this something that could possibly be taken into consideration for a future update as this means I cannot stream audio from all sources (e.g radio apps and Spotify)to any DLNA output.
I really like AOSP Extended and would rather not switch to a different ROM.
Many thanks,
herges
herges said:
Hi All,
Firstly thank you very much for providing this ROM with the latest security fixes - everything important is working fine and I have also better battery life than in the AOSP Extended 8 ROMs.
However I have one problem that did not exist in the previous ROM. I use AirAudio (in combination with the Magisk AirAudio module) to stream any sound from the phone to a DLNA audio output. Usually when I activate the AirAudio streaming the sound on the phone stops and the output is redirected to the DLNA speaker. In this ROM though the audio plays on the phone and also on the DLNA speaker.
I contacted the AirAudio developers and they responded that this is a problem with an incorrect audio implementation in the custom ROM I'm using as they have seen this before. This is what they wrote:
-------
I assume you have a custom ROM, eg. Pixel Experience installed?
There are some ROMs around at the moment that have a broken implementation of the audio-driver.
Android-devices MUST only play the audio locally _or_ remote via AirAudio, this is defined by Google.
I think you have to wait for an update of your ROM or switch to another ROM like others did :-/
-------
Is this something that could possibly be taken into consideration for a future update as this means I cannot stream audio from all sources (e.g radio apps and Spotify)to any DLNA output.
I really like AOSP Extended and would rather not switch to a different ROM.
Many thanks,
herges
Click to expand...
Click to collapse
I only compile unofficial builds. You can try to contact AospExtended devs, but mind that Pie entered final state and they're focusing on Android 10 now. However if the problem can be fixed with some simple patch in sources and it wouldn't affect anything else in negative way, I am willing to apply it to my builds.
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
I dirty flashed this ROM over official build yesterday and everything was fine, but today I was just checking out LOS 17, and then decided to roll back to this ROM, so I clean flashed this ROM, but after clean flashing the mobile data wasn't turning on.
And my SD card wasn't getting detected either. It lead to a lot of mess because I was not able to flash the official build either which was also in the SD card, I can't connect my phone to computer either because the USB port of the phone is bit defected, when I did managed the SD card to get detected, the recovery wasn't installing the official build. I tried to install los17 again and it worked.
Right now I am using los 17 and I would really like to go back to aex pie (official or unofficial) can someone help?
Golbinex said:
I only compile unofficial builds. You can try to contact AospExtended devs, but mind that Pie entered final state and they're focusing on Android 10 now. However if the problem can be fixed with some simple patch in sources and it wouldn't affect anything else in negative way, I am willing to apply it to my builds.
Click to expand...
Click to collapse
Hi,
I went and installed the official ROM and there the audio routing using AirAudio works correctly so something must have got broken when you recompiled this using the latest security fixes.
mobihack said:
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
Click to expand...
Click to collapse
It works for me, make sure you don't have any app with root access, which can block it.
BlackWhale2108 said:
I dirty flashed this ROM over official build yesterday and everything was fine, but today I was just checking out LOS 17, and then decided to roll back to this ROM, so I clean flashed this ROM, but after clean flashing the mobile data wasn't turning on.
And my SD card wasn't getting detected either. It lead to a lot of mess because I was not able to flash the official build either which was also in the SD card, I can't connect my phone to computer either because the USB port of the phone is bit defected, when I did managed the SD card to get detected, the recovery wasn't installing the official build. I tried to install los17 again and it worked.
Right now I am using los 17 and I would really like to go back to aex pie (official or unofficial) can someone help?
Click to expand...
Click to collapse
I think you broke your firmware partition so network drivers (wifi, mobile data) don't work. Try to flash official xiaomi firmware (not ROM). https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917
herges said:
Hi,
I went and installed the official ROM and there the audio routing using AirAudio works correctly so something must have got broken when you recompiled this using the latest security fixes.
Click to expand...
Click to collapse
This ROM is different than official one, because it has different device sources, the issue is caused by dotOS device sources. You can try to contact devs of some ROM where AirAudio works and ask them how they fixed it or use official one.
Golbinex said:
I think you broke your firmware partition so network drivers (wifi, mobile data) don't work. Try to flash official xiaomi firmware (not ROM). https://forum.xda-developers.com/re...lopment/firmware-xiaomi-redmi-note-4-t3760917
Click to expand...
Click to collapse
I think firmware does not get affected when ROM is changed/messed with, also the mobile data was working when I was using the los 17 (which I flashed after this rom wasn't turning on the mobile data).
I did a lot of things that I don't remember now (rebooting into recovery couple of times helped with the sd card detection issue), but in the end I was able to clean flash the official build with opengapps.
I can't be sure but I think bitGapps is responsible for this mess, which I used with LOS 17.
The order of ROMs on my phone from yesterday is aex official (everything fine)> aex unofficial (fine)> los 17 (I think the problem started here when I flashed bitGapps)> aex unofficial (no mobile data)> los 17 (mobile data works)> aex official (everything fine).
Thanks anyway for your help.
mobihack said:
Mobile data is not turning off from QS. I have to click airplane to switch it off completely.
Click to expand...
Click to collapse
For me, mobile data is not turning on
---------- Post added at 10:46 PM ---------- Previous post was at 10:30 PM ----------
BlackWhale2108 said:
I think firmware does not get affected when ROM is changed/messed with, also the mobile data was working when I was using the los 17 (which I flashed after this rom wasn't turning on the mobile data).
I did a lot of things that I don't remember now (rebooting into recovery couple of times helped with the sd card detection issue), but in the end I was able to clean flash the official build with opengapps.
I can't be sure but I think bitGapps is responsible for this mess, which I used with LOS 17.
The order of ROMs on my phone from yesterday is aex official (everything fine)> aex unofficial (fine)> los 17 (I think the problem started here when I flashed bitGapps)> aex unofficial (no mobile data)> los 17 (mobile data works)> aex official (everything fine).
Thanks anyway for your help.
Click to expand...
Click to collapse
Mobile data does not work only with this rom.
Flashed Pixel Experience and mobile data worked. Flashed AEX unofficial again and it doesn't.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
Special thanks to Exynos5420 team and LineageOS for all the sources.
Use SM-T900 build at your own risk. I can't guarantee you it will work, because I have no device to test it on.
Work
Almost everything
It has pretty much the same functionality as Lineage 14.1
Known Issues
Built in mic not working
USB problems
You tell me...
Installation:
1. Flash latest official Samsung Firmware with ODIN
2. Flash latest TWRP Recovery: SM-T520 - SM-T900
3. Backup all partitions
4. Wipe Cache and Data
5. Install ROM.ZIP
6. Install latest GApps (ARM/Android10) https://opengapps.org/
7. Reboot and Enjoy
8. Optional: Install Magisk
For SM-T520 TWRP recoveries 3.1.1.0 and older will not flash this rom ending up with error 7: incompatible device.
Make sure to flash TWRP mentioned above.
Download:
SM-T520
SM-T900
I ll probably create builds with updated security and device code patches occasionally.
Enjoy fresh new Android!
Sources:
https://github.com/LineageOS (LineageOS 17.1)
https://github.com/exynos5420/ (Kernel, Device, Vendor)
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
manix01 said:
@TechDriver can You build a LineageOS 17.1 ROM for SM-T900 who is used the same Exynos5420 CPU?
If is necessary I can be a beta tester.
Click to expand...
Click to collapse
You got it there try it out!
Larision said:
Damn!! Just installed and working.
Really good work! Thanks!!!!
i found a bit problem, starting android it loops between voice assistant and set lock for tablet. i needed connect earphones with microphone to finish voice assistant configuration and then it continued.
Thanks for rom!
Click to expand...
Click to collapse
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
pjotrski1000 said:
Did you install on the t520 or the t900? Did you really go back to the Samsung official build first? (I'm on t900 lineage 14.1)
Click to expand...
Click to collapse
You don't need to go stock, just backup your data using TWRP and follow installation steps above. I am little unsure about build for T900 because I do not own this device, so I wait for someone who can report me if it works or not.
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
kb8no said:
@TechDriver Clean flashed 17.1 over 14.1 without flashing stock on T900 using twrp-3.5.1_9-0 and it flashed great. I plugged in a headset but my Hey Google was already recorded and didn't give me any trouble. I don't know what would have happened if I hadn't plugged in the headset. Play Store does not recognize my already purchased apps. This usually means something is not right and I wonder if not flashing stock first is related to this? Can be very smooth but can be a little glitchy as well. Still experimenting and trying things. Bluetooth Keyboard and Mouse work great. Thank you for this.
Click to expand...
Click to collapse
It has probably something to do with missing play protect certification. I will try to sign device for certification but need someone with T900 who will cooperate with me. For now easiest way to avoid problem is going to browser version of play store and installing paid app to specific device from there. It should work fine. Also thanks for testing and reporting that T900 build works.
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
@TechDriver SELinux is not enforcing. That may be why Google Play does not recognized my purchased apps. Installing purchased apps trick from Google Play on the web worked as expected. Booting tablet, it does not accept passcode on the first try, but works on second try. This is repeatable. I will be happy to be your T900 tester if you make some test builds.
hamudistan said:
Just for understanding, these are still 32 bit builds, vor did you switch to arm_64?
Click to expand...
Click to collapse
Exynos5420 is 32bit SoC. It doesn't support arm64
@TechDriver The pass code works the first time if you are not impatient and click the accept arrow before the last number changes to a dot. There is a delay and the passcode entry is laggy and you have to be patient for a few seconds. twrp-3.5.1_9-0 is able to back up and restore 17.1 with no problem.
@TechDriver The first login with PIN after booting will fail. The second and future screen saver logins will work with the caveat that you are patient until the last number turns into a dot.
Pixel launcher does not work correctly with mouse clicks and has a focus graphics glitch. It works right as long as you don't click the mouse. If you click with the mouse to open a group of icons in a folder it leaves a residual grey box behind. You can see this same grey box where the PIN numbers appear on the screen saver as well. I changed to Nova Launcher and the problem improved with the grey box occurring if I open the icon folder and actually open an app but then disappearing on moving into a different folder. This is all with the exception of the PIN screen saver which causes the same grey box on both launchers. Something is not quite right with the graphics using mouse.
I mostly use this tablet with keyboard and mouse and Nova is more acceptable now. I prefer Nova Launcher anyway as it is much better at using the whole screen.
The camera is extremely basic. Open Camera seems to be an improvement. Any Google Camera port available that might work?
Just to make things clear, I am not developer of code and not skilled enough to make changes in it. For this job, there is team exynos5420 and other cool contributors to make device sources. I use their device sources from exynos5420 and LineageOS github to build together final product... Rom.zip you install on device. I can't fix bugs, i only can wait until some contributor fixes it and I will build rom with fixes and updated security patches included.
@TechDriver Got it. Will the devs be watching this thread for feedback?
kb8no said:
@TechDriver Got it. Will the devs be watching this thread for feedback?
Click to expand...
Click to collapse
I am unsure about that, most of original devs for n2awifi and v2awifi stopped developing code for this devices. Keep an eye on exynos542X github for new commits.
First of all I want to thank you for the this ROM.
I tried this ROM with the latest TWRP version for two days and I want to inform that it is working good with some small non-conformities:
I had some random reboots and the system crashed and freezing
After rebooting there is a long time after entering the unlock pattern, sometimes it is necessary to enter the pattern several times.
I have installed ROM, gapps nano rebooted and after that install Magisk 22.1
my model is SM-T900
@TechDriver ,Great work on this build! Never thought I would see this accomplished. Many thanks and keep up the good work. This is fully usable with Nova beta 7.0.27.
Works perfectly on my T900, many thanks! Keep up the good work!
stanl56 said:
@TechDriver ,Great work on this build! Never This is fully usable with Nova beta 7.0.27.
Click to expand...
Click to collapse
Can you provide a link for this latest Nova beta? APK mirror seems booked.
Nova 7.0.27 Works smoother and scrolling and moving icons is better. PIN screen on first login is same problem and will not work on the first try. Mouse clicks and mouse related screen painting remains an issue. If you don't use a mouse you may not notice any problems other than first login. Come to think about it, 7.1 had issues with the mouse most noticeable when I used Collabora and I had attributed it to the app.