Related
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
Direct device link
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Releases including and past 3.0.2-2 will work on both the L and M bootloader. The screen update issues plaguing unofficial 3.0.0 do not happen on these newer builds either. The OP is a little different from other TWRP threads because I don't want to keep updating the changelog and version numbers, but those can be found on the twrp homepage linked there. Enjoy.
Don't you love the smell of success in the morning? :laugh:
Finally, official status!
Nice! Nice! Nice!
Time for me to get some more roms out I guess
ro.product.device missing?
Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.
Can anyone care to confirm if this is an issue with the official recovery image?
DaveTheRave said:
Not sure if I'm an isolated case for this, but I couldn't flash anything with this recovery because the updater script in ROMs would fail at ro.product.device, basically instead of shieldtablet being there it was blank. Went back to unofficial TWRP and now no problems.
Can anyone care to confirm if this is an issue with the official recovery image?
Click to expand...
Click to collapse
Yes, It is an issue I am working on.. :good:
Thx for the feedback, I will be posting a working version soon..
Thx Josh
EDIT:
Can I get some feedback on this, seems to be working as expected... :good:
Changelog:
Remove vendor init, cm is able to install now.
TWRP 2.8.7.1 DOWNLOAD LINK !!
Thx Josh
Hi Josh,
I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
I tried using the
Code:
adb shell twrp decrypt <pin>
command to decrypt using adb, but get the following response:
Code:
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
el3ctrik said:
Hi Josh,
I'm trying to use the TWRP build on my new replacement device (received it last Monday). All I've done since unboxing is set a PIN and enable encryption. On booting, the /data partition isn't mounted, with the following error:
Code:
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E:Unable to mount '/data'
MTP Enabled
I tried using the
Code:
adb shell twrp decrypt <pin>
command to decrypt using adb, but get the following response:
Code:
Attempting to decrypt data partition via command line.
E:No crypto support was compiled into this build.
This is with both the 2.8.7.0 official build, and the 2.8.7.1 build you reference above. Is it possible to get crypto support enabled please?
Click to expand...
Click to collapse
Yes, this is a HUGE issue.....
I need to look at making this happen....
Thx Josh
EDIT:
Ok lets give this a go
Changelog:
Added decryption support.
TWRP 2.8.7.2 DOWNLOAD LINK !!
Thx Josh
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
philipp21897 said:
The recovery does not work with the Nvidia shield k1 tablet. It cant write to the system partition.
Click to expand...
Click to collapse
I am going to need just a bit more
Please run: adb pull /tmp/recovery.log
Upload or pastebin the output
Thx Josh
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:
http://forum.xda-developers.com/showthread.php?t=2877117
Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
Sent from my SHIELD Tablet using XDA Free mobile app
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.
@lj50036: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
An Droid said:
I'm a bit confused - how does this version relate (or not) to the version released in this previous thread?:
http://forum.xda-developers.com/showthread.php?t=2877117
Is it that this version has official status compared to the other (and is a newer version as well - 2.8.7.2 vs. 2..8.7.1 as of this post)?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
I started with a similar device tree, but did some cleaning up
The device tree is linked in post #2
Thx Josh
Steel01 said:
Correct. This is officially available on the TWRP website. The unofficial one should be almost exactly the same, but I don't think I've ever seen the device tree it was built from, so I can't say for certain.
@lj50036: I'm probably blind, but I can't find the source you're using for newer builds? Is it in a public repo somewhere? I'll want to pull the decryption support into the multirom twrp builds since I assume it's not enabled there either. Haven't tried, though.
Click to expand...
Click to collapse
Dont forget to check gerrit...
http://gerrit.twrp.me/#/c/1115/
Thx Josh
lj50036 said:
Dont forget to check gerrit...
http://gerrit.twrp.me/#/c/1115/
Click to expand...
Click to collapse
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.
*peruses changesets*
*is skeptical that it will work right*
I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.
Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?
The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
Steel01 said:
Oh duh. Though I'm not certain why I had to register to even look at it? Meh.
*peruses changesets*
*is skeptical that it will work right*
I put the vendor init in to make all the recoveries and roms run across all models. And I think just about every rom uses it now. Without it... I suppose most popular roms will install since they assert as shieldtablet. But if someone has one specifically for wx_na_wf or such, that won't work. Do you know why the vendor init isn't running? It works on my multirom twrp builds built in an omni 5.1.1 tree. But if you really want to revert to a non-unified build, you should add the fingerprints back and probably split to three separate builds, one for each model.
Also, why is selinux being removed? Won't that break labeling on install? Is there a bug/missing rule I'm missing?
The decryption support seems simple enough, one line. I'll pull that in tomorrow and credit you and the review for it. Maybe I can finagle a formatted patch into my repo to keep authorship and all.
Click to expand...
Click to collapse
Ok, that is a lot to take in......
I am more then willing to work with anyone that is willing to work with me.....
I am still learning everyday...
If you would like to join us on irc feel free, that is going to be the best for me....
Thx Josh
lj50036 said:
If you would like to join us on irc feel free, that is going to be the best for me...
Click to expand...
Click to collapse
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
Steel01 said:
Sure, I can do that. Which channel? I don't know twrp's infrastructure.
Click to expand...
Click to collapse
TWRP IRC
Network: freenode
Channel: #twrp
Thx Josh
EDIT:
Huge thx to @Steel01 for all his help with this project..... :good:
Changelog:
Reforked kernel source, vendor init is working as expected....
TWRP 2.8.7.3 DOWNLOAD LINK !!
Thx Josh
Hi Josh - just had a chance to test 2.8.7.3 on my encrypted device and working perfectly.
Thanks!
lj50036 said:
TWRP IRC
Network: freenode
Channel: #twrp
Thx Josh
EDIT:
Huge thx to @Steel01 for all his help with this project..... :good:
Changelog:
Reforked kernel source, vendor init is working as expected....
TWRP 2.8.7.3 DOWNLOAD LINK !!
Thx Josh
Click to expand...
Click to collapse
did you already saw this?
http://forum.xda-developers.com/showthread.php?p=64143425
ti fix just define the props correctly via override (i dont know if its shield or shieldtab or anything like that )
Sent from my Xperia T using XDA Free mobile app
Yeah,you heard it right!
The long awaited feature,ability to map keys for games that are originally developed for touchscreen enabled devices are coming to RemixOs.
The chinese version of RemixOs has a new version (2.0.401) dated 27th June 2016,which claims to support keymapping.
You can check the changelog at https://bbs.jide.com/forum.php?mod=viewthread&tid=7351
I wanted to give it a try.but the download was stucked due to the low bandwith offered by server,unfortunately.
If you are brave enough to take a early look,or can't wait for the global release. here are the download links.
1) http://pan.baidu.com/s/1bpibhZT
Code: gbku
2) https://yunpan.cn/OcRUtwhPNKenuX
Code: 938d
PS: Those files are hosted in chinese servers,so the bandwith is not super high. You're on your own,and ask google translate for help
Thisu said:
Yeah,you heard it right!
The long awaited feature,ability to map keys for games that are originally developed for touchscreen enabled devices are coming to RemixOs.
The chinese version of RemixOs has a new version (2.0.401) dated 27th June 2016,which claims to support keymapping.
You can check the changelog at https://bbs.jide.com/forum.php?mod=viewthread&tid=7351
I wanted to give it a try.but the download was stucked due to the low bandwith offered by server,unfortunately.
If you are brave enough to take a early look,or can't wait for the global release. here are the download links.
1) http://pan.baidu.com/s/1bpibhZT
Code: gbku
2) https://yunpan.cn/OcRUtwhPNKenuX
Code: 938d
PS: Those files are hosted in chinese servers,so the bandwith is not super high. You're on your own,and ask google translate for help
Click to expand...
Click to collapse
use the baidu link . download speed is ok
enter the code :gbku in the box before 提取文件. press enter.
click the file Remix OS PC版(64位). then put a tick on the box for the zip file and md5 file . now click on 下载 to download.
if you want to use alt+f1 , you need to go to setting , then experimental , you can enable alt+f1 there .
you need this to enable google play store
if you want root just replace the su file under system/xbin
tested working in virtualbox and harddisk
Ok, very nice and all but...will it support my nvidia card with the official nvidia driver?
or29544 said:
Ok, very nice and all but...will it support my nvidia card with the official nvidia driver?
Click to expand...
Click to collapse
it work fine on gtx 750 ti. there is only the open source driver no official nvidia driver.
I thought the next update would be 3.0......
The forum link isn't opening.. can u copy th changelog here?
modaifallah said:
The forum link isn't opening.. can u copy th changelog here?
Click to expand...
Click to collapse
Google Translate version of this page - https://bbs.jide.com/forum.php?mod=viewthread&tid=7351
Remix OS PC version added a keyboard mapping is user long-awaited things, a lot of people pretending Remix OS PC version of the original intention is to play the game, because they can not stand the card slow performance and poor compatibility simulator.
Last week, Remix OS PC version beta version added a keyboard mapping function to obtain beta users, no longer afraid of playing the game is not compatible.
Yes, today's main event is the keyboard mapping update was added, and now only for "vanity" and "human resource" adaptation keyboard mapping, follow-up will add more and more optimized game adaptation.
Upgrade:
You can check the OTA update system update
Download the full amount of the package
Baidu network disk || Click here to visit
the extraction code: gbku
360 cloud disk || Click to Visit
extraction code: 938d
Detailed update log:
new function:
Added "Apply recommendation", it recommended more suitable Remix OS applications
New image output, support output HDMI, DP and VGA interfaces, etc.
New settings - restore factory settings function
Add a button to switch your phone browser / computer mode functions
Added latest official recommended wallpaper
Latest update Remix OS boot animation
New low battery alerts
Optimize video playback, video playback support more formats
New gaming keyboard mapping support, recommend games to "vanity" and "human resource" can be installed in the application of Recommendation
Bug fix:
Enhance the stability of the system, the use of traditional mechanical hard disk, the system will be more fluent
Improve application compatibility, support for more applications running on the x86 platform, such as: Youku / Taobao / JX / Implosion / Yahoo Mail
Increased portion laptop touchpad right support
Improve Wi-Fi instability, adding support for more wireless network card, including Realtek / Broadcom / MediaTek
Optimization Nvidia graphics adapter problem
Optimization of temperature control notebook, laptop or tablet according to the temperature control system to prevent system crashes
When optimizing hard disk partition read, repair hard disk partition to mount, resulting in system issues Caton
Repair in some graphics cards cause the taskbar can display problems
Progress is inseparable from the system for your feedback, in order to better optimize Remix OS PC version, please stop for a moment, fill in the following three questionnaire to help us do a better Remix OS PC.
Remix OS PC version of the keyboard mapping gathering feedback || Click to Visit
Remix OS PC version of the perfect run hardware collection || Click to Visit
Applications Recommended || Click to Visit
Regnas said:
I thought the next update would be 3.0......
Click to expand...
Click to collapse
There're few bugs that stop Android-x86 6.0 from daily use. For example,Google play services always crash on Intel Gen8+ GPUs,which is not fixed yet.
But the devs at Jide are actively contributing to Android-x86 6.0 and you'll be able to see the results in near future. For instance,the issue of Time being reset in Windows is fixed
in the latest commit, Check the marshmallow-x86 branch at https://github.com/android-x86-mirror
Hmm...seems like a solid release. I will wait for the official announcement and update though. If it fixes my nvidia/wifi/sound issues I might actually start using this
Regnas said:
I thought the next update would be 3.0......
Click to expand...
Click to collapse
I think there is no remix os 3.0 for PC(x86) :crying: :crying: :crying: :crying:
I downloaded and installed it. My impression :
1 Locked DOWN, no more root command line
2 No Play Store option
3 Does include keymapping
4 Stock file manager can no longer read the partition on which Remix OS is installed
5 Maybe a little more quick because of changes to disk partition access
This may be because it is currently for Chinese users, hopefully there will be more flexibility with the release
EDIT 2016/07/01: After solving problems of getting into root command line, was able to deactivate jide app policy and then went on to install nova launcher, etc. Then using help from @HypoTurtle I was able to do systemless root. Everything now operating well. I will continue testing this 2.0.401 over the next few days for stability.
Summary:
1 No longer locked down
2 Play Store is activated
3 keymapping confirmed
4 Solid Explorer can read all disk partitions by using Stickmount
5 So far seems quicker than 2.0.205
Sent from my on Z00A using XDA Labs
Latest version is dated 29 June 2016..
For root , you need to replace the su file at system/xbin.
For play store option you need to got to setting , click on experimental ,on the alt+f1 option . You can active play store option .
Sent from my GT-N7105 using XDA-Developers mobile app
have anyone a working link/mirror to the new beta?
scanja500 said:
have anyone a working link/mirror to the new beta?
Click to expand...
Click to collapse
I have already posted this in two different threads, but here is a faster mirror, if anyone wishes to download.
https://mega.nz/#!9lkTWDiI!as99QTFGw2UYkFkHQWBVCX-pKpxkT7McLs27t-wfVHM
pengkoh1 said:
Latest version is dated 29 June 2016..
For root , you need to replace the su file at system/xbin.
For play store option you need to got to setting , click on experimental ,on the alt+f1 option . You can active play store option .
Click to expand...
Click to collapse
Thanks for explaining the experimental settings.
Was able to activate the Play Store
Pardon the noob question: where do I get the si file to replace the stock one?
Sent from my on Z00A using XDA Labs
lollyjay said:
Thanks for explaining the experimental settings.
Was able to activate the Play Store
Pardon the noob question: where do I get the si file to replace the stock one?
Sent from my on Z00A using XDA Labs
Click to expand...
Click to collapse
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
I used the remixroot.zip from here. I choose to install remix os in read write mode thus I can replaced the su file at system/xbin directly.
You have to follow the method describe in that thread if you install remix os in read only mode
Sent from my GT-N7105 using XDA-Developers mobile app
pengkoh1 said:
http://forum.xda-developers.com/remix/remix-os/remix-os-installation-rooting-t3293769
I used the remixroot.zip from here. I choose to install remix os in read write mode thus I can replaced the su file at system/xbin directly.
You have to follow the method describe in that thread if you install remix os in read only mode
Click to expand...
Click to collapse
Thanks. I installed Remix on a Windows computer so I cannot use Ubuntu method. Also I used the Remix installation tool so everything is stock install. Guess I will have to wait for a systemless root. @HypoTurtle are you onto this yet? (lol)
lollyjay said:
Thanks. I installed Remix on a Windows computer so I cannot use Ubuntu method. Also I used the Remix installation tool so everything is stock install. Guess I will have to wait for a systemless root. @HypoTurtle are you onto this yet? (lol)
Click to expand...
Click to collapse
If someone can post the ramdisk I'll compare to the previous version but regardless the current systemless root su/ramdisk.img should work fine; unless it's drastically different.
HypoTurtle said:
If someone can post the ramdisk I'll compare to the previous version but regardless the current systemless root su/ramdisk.img should work fine; unless it's drastically different.
Click to expand...
Click to collapse
I thought so too. But when I substitute the ramdisk.img I get to the RemixOS splashscreen and never boots further
lollyjay said:
I thought so too. But when I substitute the ramdisk.img I get to the RemixOS splashscreen and never boots further
Click to expand...
Click to collapse
In that case attach the ramdisk.img to a post here and I'll take a look.
edit. @lollyjay on your edit above -- you shouldn't need stickmount... check if the partitions are mounted to /mnt/media_rw/hdd*
This week's OTA update integrates Android M's latest security patch as well as Android-x86 rc2.
If you're new to Remix OS for PC, you can download it here: http://www.jide.com/remixos-for-pc#downloadNow
Here are the full release notes:
Remix OS for PC version: 3.0.201
Release date: August 16, 2016
Added latest Google Android M Security patch
Latest Android-x86 RC2 has been integrated and the highlighted features are as follows:
Fixed more Wi-Fi issues
Fixed more audio card loading issues
Fixed software rendering crashing issues on VM's like QEMU and VirtualBox
OTA support disabled if software was NOT installed by official Jide installer
Newly installed apps will have a small blue icon on it so they can be easily identified
As always, please give us your feedback here and help us continue to develop better!
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
Thanks!
I'm using 3.0.104, there is no ota update yet?
Sent from my Moto G using XDA Labs
Aguys said:
I'm using 3.0.104, there is no ota update yet?
Sent from my Moto G using XDA Labs
Click to expand...
Click to collapse
@Aguys Can you check again? From our end, it looks good. Thanks for your patience!
Fresh install :
find --set-root --ignore-floppies /menu.lst
error 15: File not found
Remix folder injured I can not delete.
krystyan84 said:
Fresh install :
find --set-root --ignore-floppies /menu.lst
error 15: File not found
Remix folder injured I can not delete.
Click to expand...
Click to collapse
@krystyan84 - Are you using UEFI or Legacy boot? Can you send us feedback and a screenshot here?
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
Thanks!
krystyan84 said:
Fresh install :
find --set-root --ignore-floppies /menu.lst
error 15: File not found
Remix folder injured I can not delete.
Click to expand...
Click to collapse
Run chkdsk on the partition.
@RemixOS_Jason These OTAs seem to take 1-2 days to show up for me; are they rolled out by location?
RemixOS_Jason said:
@krystyan84 - Are you using UEFI or Legacy boot? Can you send us feedback and a screenshot here?
https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
Thanks!
Click to expand...
Click to collapse
Sent :good:
Legacy boot Remix OS 3.0.201 (win10/remix dual boot 3.0.104 It worked well)
IMG
http://imgur.com/a/F1uZm
EDIT:
HypoTurtle:Run chkdsk on the partition.
This is interesting, chkdsk it was executed without error.
Reboot and Remix is boouted up :good:
krystyan84 said:
Sent :good:
Legacy boot Remix OS 3.0.201 (win10/remix dual boot 3.0.104 It worked well)
IMG
http://imgur.com/a/F1uZm
EDIT:
HypoTurtle:Run chkdsk on the partition.
This is interesting, chkdsk it was executed without error.
Reboot and Remix is boouted up :good:
Click to expand...
Click to collapse
In my case, when Remix OS running don't eject partition where Remix OS installed. If something wrong happens, that partition will not affected... CMIIW
Sent from my Moto G using XDA Labs
EDIT:
OTA update didn't work, I didn't wait and installed it once again on my Lenovo miix 700, but a HUGE DISAPPOINTMENT:
1) audio still not working (Realtek high definition audio),
2) no USB mount, it gives an error about a corrupted usb card.
3) YouTube doesn't work
4) kernel is not updated to 4.4.1.7
audio worked on Android x86 RC2
Any idea @RemixOS_Jason ?
Hi @RemixOS_Jason In my laptop, kernel verson is still 4.4.14 even after the update,Is it 4.4.17??? My update went fine and i'm on 3.0.201 now.
is over hdmi fixed? someone please try it.
KamaL said:
EDIT:
OTA update didn't work, I didn't wait and installed it once again on my Lenovo miix 700, but a HUGE DISAPPOINTMENT - audio still not working (Realtek high definition audio), no USB mount and now YouTube doesn't work.
audio worked on Android x86 RC2
Any idea @RemixOS_Jason
Click to expand...
Click to collapse
I thought your audio would be working with remix os since it's working on latest Android x86; that's very strange
Ludespeed said:
I thought your audio would be working with remix os since it's working on latest Android x86; that's very strange
Click to expand...
Click to collapse
unfortunately not... maybe because kernel isn't updated to the new version mentioned in the changelog
A clean install using Titanium Backup to restore apps. Very fast, smooth.
A few glitches:
1 phantom usb drive
2 no way to change the notifications
3 bluetooth doesn't work
still have the "sleep mode wake up hang" bug
KamaL said:
EDIT:
OTA update didn't work, I didn't wait and installed it once again on my Lenovo miix 700, but a HUGE DISAPPOINTMENT:
1) audio still not working (Realtek high definition audio),
2) no USB mount, it gives an error about a corrupted usb card.
3) YouTube doesn't work
4) kernel is not updated to 4.4.1.7
audio worked on Android x86 RC2
Any idea @RemixOS_Jason ?
Click to expand...
Click to collapse
1) audio still not working (Realtek high definition audio) - We are still working on more support for audio cards. Please be patient as this is still a continual work in progress.
2) no USB mount, it gives an error about a corrupted usb card - Our testers have shown that most external USB drives are supported. Can you send us your info through our user feedback form so we're aware of your specific device's issues? https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
3) YouTube doesn't work - I've been testing YouTube all day on my Remix OS for PC device. The app works fine. Watching on YouTube through Chrome has some issues, but on the whole, still works. Just not as well as the app. So, are you referring to the app or in browser experience?
4) kernel is not updated to 4.4.1.7 - I just checked with our PM and he stated that they're still testing this. Though we integrated rc2, this is one thing that was held back for testing to make sure it didn't affect overall system stability. However, stating it on the release notes was a mistake made on my part. There was miscommunication between myself and the PM and I listed this when it was still in our internal testing phase. I do apologize for this mistake and the confusion it may have caused!
HypoTurtle said:
Run chkdsk on the partition.
@RemixOS_Jason These OTAs seem to take 1-2 days to show up for me; are they rolled out by location?
Click to expand...
Click to collapse
@HypoTurtle It may be due to the servers in your location. Where are you writing to us from?
RemixOS_Jason said:
@HypoTurtle It may be due to the servers in your location. Where are you writing to us from?
Click to expand...
Click to collapse
The UK
where is the ota Update option in remix 3.0 32-bit , not find it.
RemixOS_Jason said:
1) audio still not working (Realtek high definition audio) - We are still working on more support for audio cards. Please be patient as this is still a continual work in progress.
2) no USB mount, it gives an error about a corrupted usb card - Our testers have shown that most external USB drives are supported. Can you send us your info through our user feedback form so we're aware of your specific device's issues? https://docs.google.com/forms/d/1cZNesOmnmO2esilFpvMzFZ874rvwsiKgWIX2fo9QsDk/viewform
3) YouTube doesn't work - I've been testing YouTube all day on my Remix OS for PC device. The app works fine. Watching on YouTube through Chrome has some issues, but on the whole, still works. Just not as well as the app. So, are you referring to the app or in browser experience?
4) kernel is not updated to 4.4.1.7 - I just checked with our PM and he stated that they're still testing this. Though we integrated rc2, this is one thing that was held back for testing to make sure it didn't affect overall system stability. However, stating it on the release notes was a mistake made on my part. There was miscommunication between myself and the PM and I listed this when it was still in our internal testing phase. I do apologize for this mistake and the confusion it may have caused!
Click to expand...
Click to collapse
Thank you for the detailed reply:
1) no audio - This is a popular sound card, and there are other threads on XDA and Google groups talking about this, so I hope it's high in your priority list. If you need me for any beta testing for this audio card, I'm in!
The fact that Android x86 RC2 has audio working gives hope it's not that difficult to implement it, right?
2) I was actually talking about a microSDXC card with exFAT format, a Kensington 64GB card, which doesn't mount. Is it a known bug?
3) Youtube doesn't work both using the standalone app and through browser. I don't know why.
4) This explains why it still shows the older kernel. Maybe this is the reason for missing audio???
Keep up the good work!!
https://mrchromebox.tech/#fwscript
To download and run the script, from a terminal/shell type:
cd; curl -LO https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
3. Install/Update Custom coreboot Firmware (Full ROM)
As this is a full replacement firmware, the script will offer users the option to back up their stock firmware on USB. Chromebox users have the option of a Legacy Boot or UEFI compatible firmware. When the Legacy Boot option is selected, users will have the option to set the default boot device (internal storage [default] or USB/SD); Haswell/Broadwell Chromebox users will also have the option to enable "headless" (no display attached) booting, as well as the option to enable PXE (Ethernet/network) booting via iPXE. If PXE support is enabled, it can also be set to be the default boot device. As before, changing any of these boot options requires re-running this script function.
Since Haswell/Broadwell/Baytrail Chromeboxes store their Ethernet MAC address in the VPD (vital product data) region of the stock firmware, the script will extract that region from the stock firmware and inject it into the new firmware ensuring the unique MAC address isn't lost. It will also persist the VPD region across firmware updates, so this is all transparent to the user.
After installing the Custom coreboot / Full ROM Firmware, your device will boot directly in UEFI (or Legacy) Mode; ChromeOS will not boot (though it will try to do so and fail, until a new OS is installed). Your ChromeOS device is now a "regular PC," and you can install the OS of your choice without any special instructions.
Supported Devices: All SandyBridge, IvyBridge, Haswell, Broadwell, Baytrail, Braswell, and Skylake ChromeOS devices, plus the 2018/Kabylake Chromeboxes
Requires firmware write-protect disabled: YES
Notes -
I am finally giving the middle finger to Google googledevs with their firmware restrictions on Acer Chreomebook C720P
1. Removed firmware protection screw from motherboard.
2. Ran the mrchromebox script above making sure to backup the original firmware to usb disk, in case of unfortunate bricking.
3. Reboot - I now have a fully functional UEFI PC with no firmware restrictions.
3. Can run Arnoldthebat v72 or FydeOS 6.0 with Kernel 4.14.83... or efi ubuntu, arch linux, (which I could already with seabios) etc.
4. Can run all variants of chromefied eve, nocturne, etc with Kernel 4.14.83 & FydeOS 6.0 or ATB v72 as base...
Next step - use the internal SSD to dd my Chrome OS of choice.
I am happy like a piglet in mud
Comment - this confirms that Google's firmware is crippleware to stop customers from updating their Chromebooks with unofficial ROMs
Background info: I own many ChromeOS devices (primarily used off eBay), including some older ones (Acer C720 and C720P), which -- as you know -- have expiring support in June 2019. In the meantime, I have plenty of experience running MrChromebox firmware enabling legacy dual-boot to my Linux-distro-of-choice -- either internally on a re-partitioned SSD, or an external USB stick. There is no great urgency to seeking out solutions to my soon-ending ChromeOS support, but your posts suggest that you are the 'expert' on the various options available for the C720P -- as noted in your post above.
Question: Have you considered the creation of an all-inclusive web page describing a C720P conversion -- not just the 'Full ROM/UEFI' change from MrChromebox, but everything else to get back an auto-update (?) ChromeOS with the latest features (Android/Linux) -- the stuff within #3 and #4 above?
darethehair said:
Background info: I own many ChromeOS devices (primarily used off eBay), including some older ones (Acer C720 and C720P), which -- as you know -- have expiring support in June 2019. In the meantime, I have plenty of experience running MrChromebox firmware enabling legacy dual-boot to my Linux-distro-of-choice -- either internally on a re-partitioned SSD, or an external USB stick. There is no great urgency to seeking out solutions to my soon-ending ChromeOS support, but your posts suggest that you are the 'expert' on the various options available for the C720P -- as noted in your post above.
Question: Have you considered the creation of an all-inclusive web page describing a C720P conversion -- not just the 'Full ROM/UEFI' change from MrChromebox, but everything else to get back an auto-update (?) ChromeOS with the latest features (Android/Linux) -- the stuff within #3 and #4 above?
Click to expand...
Click to collapse
You are welcome to give this a go - I do not have the expertise, or patience to set up an automated service of any sort, this is just a hobby to me, & owning a C720P, I just wanted it to be more useful to me despite the Acer & Google built in restrictions
Windows 10 To Go on Acer Chromebook C720P
This might become a thread if needed...
Soon after I purchased Acer CB C720P (in July 2014)- tinkerer hobbyist that I was, I tried to get Windows 8.1 to run from its USB 3.0 on it -
Of course this is a modest machine, so it was expected that they will try & discourage this as Windows 8.1, then later 10 laptops are more expensive, & this is supposed to be a Chrome OS machine, so running Windows on it will be made hard with lack of drivers & the sort...
Anyways, with the help of a few hackers posted advice, I managed to get it working with most functionalities, especially the trackpad.
As I have a Windows To Go 10 USB 3.0 SSD lying around, & after flashing the C720P firmware, just for fun, I tried to boot from it on the C720P...
& all the answers with drivers & howtos are published by coolstar (saving me having to find them) -
https://coolstar.org/chromebook/windows-install.html?device=peppy
Surprisingly, it became very stable with the latest iteration of Windows 10, with most drivers working, apart from trackpad & screen touch...
I will try & get these to work, & if so, will publish results & cooking here, with links to drivers I scavenge too...
coolstar did the work - head on here for resources, howtos & drivers -
https://coolstar.org/chromebook/windows-install.html?device=peppy
Hi, I've a question. I have Acer CXI3-I716GKM (on 8gen Intel) and I want to reflash windows and drivers. Should I use your recommendations when using modern Chromebox? Thank u in advance
This is LineageOS 18.1, which is based on Android 11, for the WiFi-only variants of the Samsung Galaxy Tab A 10.1" (2016), with model SM-T580 and codename gtaxlwifi, and the Galaxy Tab A 10.1" (2016) with S-Pen, with model SM-P580 and codename gtanotexlwifi. LineageOS doesn't need much of an introduction - It's a well-known custom firmware/Android distribution.
As was always planned, my LineageOS 18.1 builds continue on from @followmsi's LineageOS 18.1 builds that were intended for use by users. To update from his builds, my builds can simply be installed on top of an existing install from his builds without doing anything further (or "dirty flashed").
Downloads:
Note: While these builds are mainly intended to be used on the WiFi-only variants of these devices, they can be installed and used on LTE variants if you can go without mobile networking (of course), GPS and vibration.
Since I now have a T585, I've got LineageOS 19.1 builds for gtaxllte, and gtanotexllte as well, up in my 19.1 thread. I suggest using those.
For SM-T580/gtaxlwifi:
Latest build from 20221025 (with security patch level 20221005): https://drive.google.com/file/d/18PHMUSUW9A0ZfhjpSYCV0GiHW2Damskw/
Folder for builds (which contains a text file with a SHA256 checksum for the latest build, and a folder containing previous builds): https://drive.google.com/drive/folders/1wuirD9cyoguv7CQdEO5ymZ911k2ASKKD
For the T580, the latest official TWRP build from here should be used. If installing a build for the T580 to the LTE variant, with model SM-T585 and codename gtaxllte, keeping in mind some functionality will of course be missing as described in my note, the latest official TWRP build for gtaxllte from here can also be used.
For SM-P580/gtanotexlwifi:
Latest build from 20221025 (with security patch level 20221005): https://drive.google.com/file/d/11Iv75MtGAx4yvCWz-kN3wZOm-vgN4eE1/
Folder for builds (which contains a text file with a SHA256 checksum for the latest build, and a folder containing previous builds): https://drive.google.com/drive/folders/1fVGx1xGUxAtTvE0rG-OidwbXLM_93om2
For the P580, I've made unofficial TWRP builds from an updated device tree and the same kernel sources used for these LineageOS builds that must be used.
Download link for an image of my latest TWRP build: https://drive.google.com/file/d/1TAFLVpxdYQNvfvUPS_BGKx3imphR1Wd2/
Download link for a tar archive containing it for installation via Odin in the AP slot: https://drive.google.com/file/d/1Ay55ntZj7Uptzm--hiCaeG1C5lamQ1fG/
Changelogs:
Releases for 20221025:
Latest changes from LineageOS, including the 20221005 Android security updates.
The torch has been fixed.
Performance of animations and responsiveness has been improved slightly.
Configuration files for media codecs and profiles have been updated from Samsung's M105FDDS4CVG1 firmware, and audio codec support might be improved slightly (as the Codec 2.0 media codec framework has been fixed and is now used).
Some updates from the 4.9 Android common kernel have been applied to the kernel.
The WiFi drivers RX wakelock feature has been disabled - Heavy battery drain that occurred in sleep when connected to certain WiFi networks due to "qcom_rx_wakelock" wakelocks has been fixed.
Previous releases:
Releases for 20220903:
Latest changes from LineageOS, including the 20220805 Android security updates.
Some things that appeared that are only relevant for devices with mobile networking (such as the baseband version and SIM status sections in About tablet in settings) no longer appear.
The ZRAM size has been increased to 2GiB, and the swappiness is now set to 100.
A higher frequency (1246MHz, was 902MHz previously) is now set for the interactive CPU governors "hispeed_freq" value - This improves responsiveness slightly.
The sepolicy containing device-specific SELinux rules has been improved slightly.
Yet more miscellaneous cleanups have been done.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Releases for 20220803:
Latest changes from LineageOS, including the 20220705 Android security updates.
Some updates from the 4.9 Android common kernel have been applied to the kernel.
Releases for 20220628:
Latest changes from LineageOS, including the 20220605 Android security updates.
Many updates from the 4.9 Android common kernel, and some from a few other sources, have been applied to the kernel.
Releases for 20220526:
Latest changes from LineageOS, including the 20220505 Android security updates.
The problem where enabling the "Enable on-screen nav bar" option at Settings -> System -> Buttons caused touchscreen input to be disabled has been fixed.
Native support for IPsec tunnels has been enabled.
Support for Vulkan compute is now declared.
A new custom version of the open source Samsung audio HAL from Lineage's android_hardware_samsung repository is now used, rather than the stock, heavily-patched, proprietary Samsung audio HAL, with some fixes for a problem that made it unusable before where occasionally, audio would get outputted from both the speakers and the headphone jack.
The playback and low-latency capture period sizes have been reduced to 128 in the open source audio HAL, which reduces audio latency.
Pro audio support is now declared, since with the reduced period sizes, as well as with the use of the open source audio HAL, round-trip audio latency has been reduced enough for it.
Many updates from the 4.9 Android common kernel have been applied to the kernel.
Several fixes to the Sony HID driver in the 4.9 Android common kernel have been ported over to the kernel - Sony DualShock 4 controllers should now work properly.
Releases for 20220423:
Latest updates from Lineage, including the 20220405 Android security updates.
The tablet product characteristic has been added back after being mistakenly removed - Places where the device was referred to as a phone (such as the "About phone" section in settings) will now refer to it as a tablet again.
Some small improvements from my fixes for LineageOS 19.1 have been applied to the sepolicy containing the SELinux rules.
Some other miscellaneous cleanups have been done.
A few updates from the 4.9 Android common kernel and Samsung's A600FNXXU9CVB1 kernel sources have been applied to the kernel.
Releases for 20220325:
Latest updates from Lineage, including the 20220305 Android security updates.
The previously used 32-bit GPS blobs have been replaced with 64-bit blobs from Samsung's A810SKSS2CTI1 firmware.
The XTRA servers for Assisted GPS have been switched to the servers used in Samsung's stock firmwares - This fixes Assisted GPS, which turned out to actually not appear to work with the previous XTRA servers.
Even more small miscellaneous cleanups have been done.
There are some updates from the 4.9 Android common kernel to the kernel.
Releases for 20220224:
Latest updates from Lineage, including an increase of the Android security patch level to 20220205 (just an increase as interestingly, for this month, there aren't any (relevant) security updates).
The WiFi firmwares have been updated from Samsung's T395XXSDCVA1 firmware.
There are some final updates from the 4.4 Android common kernel (which is unfortunately now also discontinued along with Linux v4.4) and some updates from the 4.9 Android common kernel to the kernel.
[SM-P580/gtanotexlwifi only] Touch input and input from the back and recent apps keys is now ignored when the S-Pen is in use. (Thanks to @unknowwiiplayer for testing the changes for this)
Releases for 20220122:
Latest updates from Lineage, including the 20220105 Android security updates.
There are some updates from the 4.4 Android common kernel to the kernel.
Some changes have been applied to a few drivers specifically for Android in the kernel (mainly the binder driver) from the 4.19 Android common kernel for Q.
A few changes from the 3.18 Android common kernel that were missing from the kernel have been applied.
Releases for 20211222:
Latest updates from Lineage, including the 20211205 Android security updates.
There are some updates from the 4.4 Android common kernel to the kernel.
Releases for 20211114:
Latest updates from Lineage, including the 20211105 Android security updates.
The WiFi driver has been switched from being a kernel module to being built into the kernel. This may improve reliability for enabling and disabling WiFi and the WiFi hotspot very slightly.
The libexynoscamera3.so library has been updated from Samsung's P580ZSS1CTI1 stock firmware - This improves the situation with the issues with stretched/squashed camera previews for images and stretching/squashing in videos at some resolutions.
The MFC (Multi-Format Codec) firmware has been updated from Samsung's A305FDDU6CUI3 firmware.
As the oldest proprietary blobs are now as in Samsung's P580ZSS1CTI1 stock firmware (with a few exceptions), the vendor security patch level has been increased to 2020-09-01, which is the security patch level that firmware has.
Configuration files for media codecs and profiles have been updated from Samsung's T580XXS5CTK1 stock firmware.
Most SELinux rules that are technically not allowed (by neverallow rules) have been replaced with much better rules or removed.
There are some (final) updates from the (unfortunately now deprecated so no longer updated) 3.18 Android common kernel, some updates from Linux 4.4, and a few updates from Samsung's J600FPUUACUH2 and A720SKSU5CUJ2 kernel sources to the kernel.
Releases for 20211023:
Latest updates from Lineage, including the 20211001 Android security updates, and a fix for the issue where the media controls in the notification panel squash the quick settings tiles and make it impossible to swipe through them when in landscape.
Workarounds for an issue with rebooting to recovery and download mode from system using the advanced restart menu or the reboot command in a shell have been replaced with a proper fix.
Yet further slight miscellaneous cleanups have been done.
[SM-P580/gtanotexlwifi only] A problem where S-Pen input wasn't registering in the right directions in orientations other than portrait, as the axes for it didn't change on orientation changes accordingly, has been fixed by enabling orientation awareness for it (Thanks to @retiredtab for sharing that fix).
[SM-P580/gtanotexlwifi only] The cursor that appeared when using the S-Pen has effectively been disabled by setting the device type for the S-Pen input to a touchscreen (Thanks to @Acatzin for the hint for this).
[SM-T580/gtaxlwifi only] The system image size has been increased from 3072000000 bytes to 3145728000 bytes, which is the size of the system partition on Korean and Chinese variant T580s and T585s, and the smallest system partition size out of all T580s and T585s.
[SM-P580/gtanotexlwifi only] The system image size has been decreased from 3072000000 bytes to 3045064704 bytes, to accomodate for the SM-P583s system partition which has that size. With this change, it should now be possible to install this latest build for the P580 on the P583 and for it to boot fine, since the P583 basically seems to be a P580 but for China, although I can't be certain on that.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Releases for 20210922:
Latest updates from Lineage, including the 20210905 Android security updates.
The ZRAM size has been increased to 768MiB.
Even further miscellaneous cleanups have been done.
The 32-bit wcnss_filter binary, used for Bluetooth, that was used previously has been replaced with the 64-bit wcnss_filter binary from Samsung's A520FZTU4BRB1 firmware.
There are some updates from the 3.18 and 4.4 Android common kernels and Linux 4.4, a few changes backported from mainline Linux, and also a few other insignificant changes to the kernel.
An issue where there was additional extremely quiet high-pitched noise from the right speaker has been fixed. (Thanks to @Kostareka for reporting it. It likely would've gone unnoticed for at least a very long time into the future otherwise.)
First proper release for the P580.
Release for 20210810:
Latest updates from Lineage, including the 20210805 Android security updates.
This is my first build that is signed using my own release keys. This change was removed in the second build released for 20210810 (with "-R2-Test-keys" in the filename).
The BSP sources have been redone to closely match what has been done with the new exynos7880-specific part of Lineage's BSP sources, and with that, there are now more exynos7870-specific changes to the open source gralloc that is in use.
Some further small miscellaneous cleanups have been done.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel, and a few other insignificant changes.
Release for 20210709:
Latest updates from LineageOS.
Merges of the latest changes from AOSP for repositories forked by Lineage have been picked to skip the wait for them to be merged (repopick -t android-11.0.0_r39), and the rest of the repositories not forked by Lineage were additionally switched to the android-11.0.0_r39 tag, for the 20210705 Android security updates.
A patch to the PermissionController app has been applied that adds the FAKE_PACKAGE_SIGNATURE permission group to it - The signature spoofing permission can now be managed through the permission management interface at Settings -> Privacy -> Permission manager.
The audio outputted from the audio jack while playing media will now be noticeably louder, as the headset "DAC1 playback volume" for media has been increased to the maximum of 175 from 162.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
A few patches have been applied to the qcacld-2.0 WiFi driver in the kernel, which are mainly vulnerability fixes.
Release for 20210617:
Latest updates from LineageOS, including the 20210605 Android security updates.
The WiFi and Bluetooth firmwares have been updated from Samsung's A720SKSU5CTL2 firmware.
The qcom_cfg.ini configuration file for WiFi has been imported from Samsung's A720SKSU5CTL2 firmware - A change within it appears to have made WiFi more reliable.
The sensors.universal7870.so library has been updated from Samsung's stock P580ZSS1CTI1 firmware.
The health HAL has been upgraded to version 2.1.
There are a few other small miscellaneous changes (mostly small cleanups).
There are many updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Some unnecessary drivers have been disabled in the kernel.
The sdfat driver in the kernel, which is used for exFAT filesystem support, has been updated to version 2.4.5.
A few changes have been imported to the MMC block device driver in the kernel from Samsung's M105GDXS6CUD4 kernel that fix extremely rare kernel panics that occurred when there was an error with a MMC device (mainly with SD cards).
The fix for an issue where the duration of videos that are taken is lengthened by the time spent in deep sleep/suspended that was previously used has been replaced with a better fix in the Exynos fimc-is2 driver in the kernel.
Release for 20210508:
Latest updates from LineageOS, including the 20210505 Android security updates.
New SELinux denials with Android 11 have been addressed, and with that, SELinux is now set to enforcing by default, and the sepolicy, which contains the SELinux rules, has been rewritten almost entirely, and is now of much better quality.
Some changes have been imported to libbt-vendor from https://github.com/LineageOS/android_hardware_qcom_bt on branch lineage-18.1-caf.
BPF offloading for tethering has been disabled.
The audio HAL has been upgraded to version 6.0.
The rampatch_tlv_tf_1.1.tlv firmware for Bluetooth has been updated from Samsung's stock T585XXS6CTJ7 firmware.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Some tcp_info-related patches have been applied to the kernel, and with that, a workaround, a patch titled "TcpSocketTracker: Opt-out for TCP info parsing on legacy kernels", is no longer used since it's no longer necessary.
A workaround that was used to get USB tethering and Bluetooth tethering to work is no longer used, and has been replaced with a proper fix (enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel).
Release for 20210407 (My initial 18.1 build. This changelog continues on from @followmsi's last 18.1 build that was intended for use by users):
Latest changes from LineageOS. The crashes that occurred when setting a new wallpaper that were discussed earlier in this thread appear to have been fixed.
Merges of the latest changes from AOSP, including the 20210405 security updates, have been picked to skip the wait for them to be merged. (repopick -t android-11.0.0_r34)
The same workaround that was used on 17.1 to get USB tethering and Bluetooth internet access sharing to work has been forward-ported and applied.
vintf manifest override enforcement is now enabled.
The vendor/lib[64]/egl/libGLES_mali.so blobs are now symlinked to vendor/lib[64]/vulkan.exynos5.so, rather than copied to vendor/lib[64]/hw/vulkan.exynos5.so - This is a proper fix for Vulkan support.
RSA key verification for ADB is enabled again, and ADB isn't enabled by default and on boot anymore.
There are some updates from the 3.18 Android common kernel and Linux 4.4 to the kernel.
Known issues and workarounds (if any):
Issue 1: Occasionally, when trying to select quick settings tiles in the notification panel, it will crash to the lockscreen.
I have no idea about this issue. It seems like some type of generic systemui crashes. But regardless, it doesn't exist under Android 12 which I've moved onto, and it's here to stay for 11 unfortunately.
Issue 2: Camera previews for images to be taken at resolutions with aspect ratios other than 16:9 using the rear camera are squashed from 16:9 (while final saved images at any resolution are unaffected by any squashing), and videos taken at some resolutions are affected by similar issues with squashing in previews, and, in a smaller set of resolutions, also in final saved video files. (Note that these issues don't affect the front-facing camera)
Somewhat of a workaround to issue 2: Use resolutions at which there are no issues with squashing from 16:9.
To report further issues, get a log from logcat and dmesg. If you're unsure on how to get either, there's good documentation out there for how to do so.
Sources:
A manifest containing all of the necessary repositories to make a build for either the T580 or P580 is in this repository on branch lineage-18.1: https://github.com/TALUAtGitHub/gtaxlwifi-manifests
Thanks to:
@Valera1978 - for all of the previous work for the T580 (and T585) long ago, and for providing his old BSP sources without which the previously used open BSP sources wouldn't have been possible.
@followmsi - for fixes to various issues and other improvements, for useful information, and for working with me on much of this stuff.
Anyone who has previously tested anything new I've put up for testing, reported results, and gave details for me to get it working if it was necessary.
The Lineage team - for the Android distribution itself.
...and everyone else who has worked on anything that is in use.
Just installed it on a device that was still running stock. Works flawlessly, thanks!
Can I get md5 checksum?
ar0177417 said:
Can I get md5 checksum?
Click to expand...
Click to collapse
It's 382e0ae70a956deec826c6867cf80614 for lineage-18.1-20210508-UNOFFICIAL-gtaxlwifi.zip. Anything wrong?
I have a problem with connectivity since April I only get 2mb / s per second when I pay for one 20mbps
This problem is only in android 11 when I go back to some android 10 ROM there is no problem
there are the results of bliss roms
Thank you for your (and @followmsi 's) ongoing support for this device!
My T-580 never felt old to me because of you!
A couple of observations:
TALUAtXDA said:
Issue 3: the on-screen navigation bar feature that can be enabled with the option at Settings -> System -> Buttons -> "Enable on-screen nav bar" doesn't work properly.
Click to expand...
Click to collapse
-onscreen navigation bar works for me, just the "disable hardware buttons" part does not.
For workaround I use Srgrusso's patch from here.
-Safetynet fails where it hadn't before. (no biggie for me, just a thing I noticed)
Great rom!
I flashed this + Flame Gapps and Magisk 22.1.
The first custom rom for this device where Ableton Link works!!
Hi @TALUAtXDA and thanks for your your work ,and the other behind the release
My needs are very basic, I just need something stable, no need for root, sd-card storag etc..
Would this be the preferred ROM? Or is the 17x release a better for my needs?
Regarding Gapps, I noticed that users are using Flame Gapps and NikGapps, but I guess the regular Open Gapps could be an option as well.
What is the recommended Gapps variant?
Kind regards Erik
Issue 4: Adoptable storage (probably) doesn't work.
Somewhat of a workaround to issue 4: format and use your micro SD card with the exFAT filesystem (and a MBR parition table).
Click to expand...
Click to collapse
Anyone else check this yet? It's working for me on @TALUAtXDA's previous version (202010407). I use this feature quite a bit as internal storage is too small, don't want to lose it if I dirty flash this version.
autorage said:
-onscreen navigation bar works for me, just the "disable hardware buttons" part does not.
For workaround I use Srgrusso's patch from here.
Click to expand...
Click to collapse
I'm referring specifically to the "Enable on-screen nav bar" option at Settings -> System -> Buttons, that doesn't require any system-level changes as made by that package that you've linked. When enabling it, no touch input is accepted anymore for some reason. It needs to be locked and unlocked a few times for it to accept input and the on-screen navbar added through that feature to work temporarily.
autorage said:
-Safetynet fails where it hadn't before. (no biggie for me, just a thing I noticed)
Click to expand...
Click to collapse
I have no idea about this. I'd have thought that it's now more likely to pass.
n0j0e said:
The first custom rom for this device where Ableton Link works!!
Click to expand...
Click to collapse
Hmm, wow.... I didn't expect that to be fixed in this release. That's great. :)
gechu said:
My needs are very basic, I just need something stable, no need for root, sd-card storag etc..
Would this be the preferred ROM? Or is the 17x release a better for my needs?
Regarding Gapps, I noticed that users are using Flame Gapps and NikGapps, but I guess the regular Open Gapps could be an option as well.
What is the recommended Gapps variant?
Click to expand...
Click to collapse
For stability, 17.1 would be slightly better. With 18.1, there are certain occasional crashes (see issue 1) that I'm not sure about at the moment, which you may or may not be able to tolerate.
As for Google apps, it's whichever is the smallest variant. For nikgapps, that would be core, and for opengapps, that would be pico. Something to note is that opengapps seems to often be more problematic for Android 11 than other google app packages, so it could be better to go for something else.
jrollf said:
Anyone else check this yet? It's working for me on @TALUAtXDA's previous version (202010407). I use this feature quite a bit as internal storage is too small, don't want to lose it if I dirty flash this version.
Click to expand...
Click to collapse
I actually didn't know if adoptable storage was working in my previous release. I just assumed it didn't considering that it never worked properly with 17.1. Knowing that it did in my previous release of 18.1, it would probably(?) also work with my latest release.
autorage said:
[...]
-Safetynet fails where it hadn't before. (no biggie for me, just a thing I noticed)
Click to expand...
Click to collapse
With NikGAPPS core, SafetyNet passes succesfully in my case.
jrollf said:
Anyone else check this yet? It's working for me on @TALUAtXDA's previous version (202010407). I use this feature quite a bit as internal storage is too small, don't want to lose it if I dirty flash this version.
Click to expand...
Click to collapse
I actually didn't know if adoptable storage was working in my previous release. I just assumed it didn't considering that it never worked properly with 17.1. Knowing that it did in my previous release of 18.1, it will probably(?) also work with my latest release.
Click to expand...
Click to collapse
Ok, I just dirty flashed it, SD as Internal Storage seems to still be working. Thanks!
jrollf said:
Ok, I just dirty flashed it, SD as Internal Storage seems to still be working. Thanks!
Click to expand...
Click to collapse
Alright, thanks for the information. I've removed that from the list of issues. You're welcome.
One more question, does this rom impact supported widevine level?
Had similar question about safetynet, which at least one user claimed worked using NikGAPPS core. Anyway else with experience related to safetynet?
gechu said:
One more question, does this rom impact supported widevine level?
Click to expand...
Click to collapse
The widevine security level is L3, and always will be L3.
Found an issue: system recovery doesn't get overwritten when installing lineage-18.1-20210508-UNOFFICIAL-gtaxlwifi.zip. Might be related with SELinux.
Lumito said:
Found an issue: system recovery doesn't get overwritten when installing lineage-18.1-20210508-UNOFFICIAL-gtaxlwifi.zip. Might be related with SELinux.
Click to expand...
Click to collapse
Wouldn't that be what you would want so that you don't lose TWRP? We've specifically disabled that feature by setting the "persist.vendor.recovery_update" property to "false" since we don't want to use Lineage's recovery.
Maybe, it makes sense. TWRP is more powerful, and faster when installing updates.
TALUAtXDA said:
It's 382e0ae70a956deec826c6867cf80614 for lineage-18.1-20210508-UNOFFICIAL-gtaxlwifi.zip. Anything
Click to expand...
Click to collapse
The downloaded build was corrupted
I downloaded it again. Now it is working fine
Anyways, Thank you for such a great rom
n0j0e said:
Great rom!
I flashed this + Flame Gapps and Magisk 22.1.
The first custom rom for this device where Ableton Link works!!
Click to expand...
Click to collapse
..ok i rushed to fast. Ableton Link didn't sync correctly!
My guess there is something broken or missing in the LOS network stack or WiFi driver for the SM-T580 (gtaxlwifi).
I have an OnePlus 5T with LOS 18.1 (crDroid 7.6) and all apps with Ableton Link are in sync and stable over WiFi.
Here my message from planet-h.com forum:
Hi,
i have a Samsung Tablet SM-T580 WiFi and tried nearly every A10/A11 custom ROM, mostly LineageOS.
I can connect with other devices without trouble but if i start play in G-Stomper the sequencer LED's are flashing absolutely crazy and beats are rumbled.
Same with RemixLive but Snap from Reactable runs rock solid with Ableton Link!
Tried all audio drivers with various latency settings.
Tried switch some network options in the Developer options.
Tried various Devices with WiFi Hotspot or with Wifi AP.
Nothing helped. G-Stomper products & RemixLive connects but didn't sync correctly. Snap plays absolutely stable.
No Firewall, no custom DNS, no AdAway.