I've got a two-letter code for these builds. The first letter is the code base (A = AOSP & L = LineageOS) and the 2nd letter is the Android release (P = Android 9, Q = Android 10, R = Android 11).What is AQ?
I've got a two-letter code for these builds. The first letter is the code base (A = AOSP & L = LineageOS) and the 2nd letter is the Android release (P = Android 9, Q = Android 10, R = Android 11).What is AQ?
Hi @Magendanz, I was able to modify the lpm file that is inside /system/bin/ with the following code:I spent a few days experimenting with this when working on the cold charging fix. While I could get it to boot "normally" when the charger is connected, the kernel was still disabling the touch screen in LPM mode. So, this is possible, but would require kernel modifications. (Note that LPM does bypass the bootloader warning delay, which I'm sure you would appreciate.)
#!/system/bin/sh
su
/system/bin/reboot
It is LQ, is there also a AQ version.New release posted...
Downloads:
Based on LineageOS 17.1:
Nexus_Stock_LQ_T510XXU3BTH4-20201121.tar.md5 (Odin tarball)
Nexus_Stock_LQ_T510XXU3BTH4-20201121.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20201121:
Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
I'm working on it, but there hasn't been a new release of AOSP 10.0 GSI from @phhusson since August 6th. I suspect that some of the patches are outdated.It is LQ, is there also a AQ version?
Well, both BTFN and BTH4 are Android 10, so you can probably get away with loading either. If you hold on a few days, you'll probably have a BTH4 release of the AQ build, though. I just haven't had the time to get the GSI patches working with the latest AOSP 10.0 build.I am a little confused. I would like to put in the AQ_T510XXU3BTFN-20200807 build. Do I use T510xxU3BTFN or the T510xxU3BTH4 original stock rom to go from 9 to 10? I am currently running the Nexus stock 16 that you created and enjoy it thoroughly.
Yeah, that reboot is going to restart the bootloader regularly, not in lpm mode, and so you'll get the bootloader warning. I was calling class_stop charger and trigger late-init, which didn't cause a restart...but kept the touchscreen (and probably other devices) disabled. Ultimately, I think the best solution is going to be to build a custom kernel that completely ignores lpm mode.Hi @Magendanz, I was able to modify the lpm file that is inside /system/bin/ with the following code:
and now it boots into android when connecting usb charger and thankfully the touch screen is working as it shouldCode:#!/system/bin/sh su /system/bin/reboot
The only thing is that I am still getting the bootloader warning delay, do you know why?
Legend!!!New release posted...
Downloads:
Based on LineageOS 17.1:
Nexus_Stock_LQ_T510XXU3BTH4-20201121.tar.md5 (Odin tarball)
Nexus_Stock_LQ_T510XXU3BTH4-20201121.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20201121:
Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
What did you have on the tablets before flashing? I was running Nexus AQ from Aug and did a simple clean install from TWRP. Everything works fine.Updated two t510 tablets today with
Nexus_Stock_LQ_T510XXU3BTH4-20201121 both are now stuck on the G logo loading screen. First tried the twrp update method then wiped and did odin tarball install with same result.
Anyone have same problem or know what is wrong?
You can't go diriectly from ATB4 to the latest Nexus. You first have to flash the latest stock ROM via Odin, then the Nexus ROM via Odin, boot to TWRP and format (FORMAT not wipe) the data partion to get rid of the encryption, and then flash the Nexus ROM again, either via TWRP or Odin.@lewmur I was on LQ_T510XXS3ATB4-20200413 before this.
And tablets are trying to boot close to 20 mins now.
Did you flash Magisk after flashing the ROM?
Did you do a clean install or dirty? I did a dirty install and was scratching my head why the local user files were completely corrupted and gabbledegook (such as the Downloads folder being eehfhfhtjfu84747282927576fnvncyy4 for example).good day.
system ui crashes when I turn on WIFI or BLUETOOTH on the notification bar. any fix guys? thanks