Related
AOSP - Android 6.0.1 - MOB31H
NO LONGER SUPPORTED
This is a pure build of AOSP Android 6.0 Marshmallow, the goal is to have a pure AOSP rom, so it is not the objective of this project to include any functionality that is not native to Android AOSP.
And to make the experience more consistent and simplify some issues related to Android Marshmallow, this ROM has a basic versions of Google Apps (Gapps) pre-installed, additional apps can be installed via Play Store.
Download:
ROM: http://forum.xda-developers.com/devdb/project/dl/?id=20977
Instructions:
Install TWRP (download here)
Boot into recovery and flash the ROM.
For Root flash SuperSU (download here)
Note: Systemless supersu will not work with our device. The latest official release that will work is 2.52, but any system based version will work.
Code:
/*
* Your warranty is now void.
*
* 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.
*/
XDA:DevDB Information
AOSP Android 6.0 Marshmallow, ROM for the LG G Pad 8.3
Contributors
adrianom
Source Code: https://github.com/AdrianoMartins/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Stable
Created 2015-10-29
Last Updated 2016-11-17
Changelog
2016-10-18:
Update to Android 6.0.1 Release 70 (MOB31H)
Fix audio output problem in specific apps
2016-09-17:
Update to Android 6.0.1 Release 66 (MOB31E)
Other minor changes in kernel and rom
2016-09-11:
Only a clean build
2016-08-04:
Update to Android 6.0.1 Release 61
2016-07-17:
Fix Skype error
Fix and optimization patchs
Build with new toolchain (optimization)
Fix audio and video bad quality (update adreno and audio blobs) - thanks to @Deltadroid
2016-07-08:
Update to Android 6.0.1 Release 52 (MOB30R)
2016-06-16:
Update Google Apps (fix 2016-06-12 error)
2016-06-12:
Revert 2016-05-05 file system and storage management changes
2016-06-10:
Update to Android 6.0.1_r46
2016-05-07:
Update Gapps and Fix Setup Wizard
2016-05-05:
Update to Android 6.0.1_r43
Internal updates and patches focused in file system and storage management
2016-03-25:
Update to Android 6.0.1_r17
Update kernel with some CAF patchs (should fix the forced unmount of sdcard)
2016-02-07:
Update to Android 6.0.1_r13
Build with a new toolchain (GCC 5.3 and cortex-a15 optimization)
Other minor changes to the kernel, framework and camera
2016-01-08:
Update to Android 6.0.1_r10
2015-12-22:
Fix Play Store apps displaying as incompatible
Fix exFAT mount Support (need test)
Add AOSP Camera and remove Google Camera due to problem in switch to video mode (can be install from Play Store)
2015-12-17:
Update to Android 6.0.1
Fix Camera HDR mode
Add exFAT mount Support (need test)
Other small updates and internal patches
2015-11-18:
Update Gapps and Fix Google Calendar Sync
Update Setup Wizard to Tablet Version
Remove some applications intended solely for phones.
2015-11-15:
Use OpenGapps as Gapps source
Wifi: re-add default country code (BR)
Tweak display gamma configuration
Other small or internal patches
2015-11-12:
Tweak Wifi Settings
Change Kernel Power Management (fix wifi drop on sleep mode and optimize power savings mode)
Other small or internal patches
2015-11-07:
Update/Rollback to Android 6.0.0_r5 (MRA58V): the r26 for now is only intent for Nexus 5x e 6p, and this was having some issue in other devices, including:
Microphone not be detected
High battery consumption
With the change to default release branch (and 6.0.0_r5) this problems was fix.
Update Adreno Driver (fix Antutu error)
Build with a 5.2 (ROM) and 4.9 (Kernel) Toolchain compile by me with A15/FPU optimization
Remove Exchange2 and AOSP Email (default to Gmail and Google Exchange version)
Update Gapps
Other small or internal patches (including sdcard)
2015-11-04:
Update to Android 6.0.0_r26 (MDB08M)
Optminizations
Build with UBER Toolchain 5.2 (ROM) and A15 optimized 4.9 (Kernel)
Enable Strict Aliasing, Krait Tunings, GCC Tunings, Graphite, A15/Neon-vfpv4 Optminizations
Kernel Update:
Enable dynamic wireless regulatory domain
Enable support for features that have been disabled in the first versions (BFQ, SIO, ZEN, INTELLIDEMAND and others)
Enable lcd color temperature calibration
2015-10-31:
Enable Offline Charger
Enable SD Card Adoptable Storage (and fix access problem)
Fix Native Tap To Wake Setting Option
Add Calendar Sync
Enable clear all recents button
Enable SystemUI Tuner
Cleanup duplicate ringtones/alarms
Update the default wallpaper
Show Optimizing app dialog on first boot
Other small or internal patches
2015-10-29:
First release
.
Download History
2016-09-17: http://forum.xda-developers.com/devd...t/dl/?id=20460
2016-09-11: http://forum.xda-developers.com/devdb/project/dl/?id=20358
2016-08-04: http://forum.xda-developers.com/devdb/project/dl/?id=19659
2016-07-17: http://forum.xda-developers.com/devdb/project/dl/?id=19369
2016-07-08: http://forum.xda-developers.com/devdb/project/dl/?id=19247
2016-06-16: http://forum.xda-developers.com/devdb/project/dl/?id=18909
2016-06-12: http://forum.xda-developers.com/devdb/project/dl/?id=18864
2016-06-10: http://forum.xda-developers.com/devdb/project/dl/?id=18842
2016-05-07: http://forum.xda-developers.com/devdb/project/dl/?id=18267
2016-05-05: http://forum.xda-developers.com/devdb/project/dl/?id=18239
2016-03-25: http://forum.xda-developers.com/devdb/project/dl/?id=17547
2016-02-07: http://forum.xda-developers.com/devdb/project/dl/?id=16689
2016-01-08: http://forum.xda-developers.com/devdb/project/dl/?id=16132
2015-12-22: http://forum.xda-developers.com/devdb/project/dl/?id=15825
2015-12-17: http://forum.xda-developers.com/devdb/project/dl/?id=15735
2015-11-18: http://forum.xda-developers.com/devdb/project/dl/?id=15277
2015-11-15: http://forum.xda-developers.com/devdb/project/dl/?id=15239
2015-11-12: https://www.androidfilehost.com/?fid=24269982086994042
2015-11-07: http://forum.xda-developers.com/devdb/project/dl/?id=15067&task=get
2015-11-04: https://www.androidfilehost.com/?fid=24269982086987956
2015-10-31: https://www.androidfilehost.com/?fid=24052804347851183
2015-10-29: https://www.androidfilehost.com/?fid=24052804347848935
.
To build from source:
Code:
repo init -u https://github.com/AdrianoMartins/aosp_manifest.git -b android-X (replace with desired version)
repo sync
. build/envsetup.sh
lunch aosp_v500-userdebug
make -j4 otapackage
Credits:
The kernel is base on @ckret, @Rick Roll and @fefifofum kernel source, with additional patches from all community.
The device repo is based on the @fefifofum source for CM with my changes to AOSP and Marshmallow.
.
...
great, Im gona try it, keep up the great work man, hats off !
Oh my days!!!!!!!!!!!gonna flash it and give feed back. Thank you
@adrianom
Thank you for MM sweetness for our G Pad. Downloading now. Will report back for any issues.
Does wifi have issues like on cm11/12 when download speed is not higher 50mbps
Okay i got a random RESTART during the first charge cycle of this rom.... Still a lot to test tho
takis said:
Okay i got a random RESTART during the first charge cycle of this rom.... Still a lot to test tho
Click to expand...
Click to collapse
In offline charge (powered off)? If so, it was not yet implemented and reboot to os is the standard.
It was while the device was on
So, what I just did:
- Full backup of apps with TB
- Download MM version and SuperSu 2.52
- Reboot into Recovery
- Wipe everything but data partition
- Install ROM
- Install SuperSu
- Reboot
- Restore all apps with TB
Wifi working, camera working, flawless victory so far !
regards, mistersixt
mistersixt said:
So, what I just did:
- Full backup of apps with TB
- Download MM version and SuperSu 2.52
- Reboot into Recovery
- Wipe everything but data partition
- Install ROM
- Install SuperSu
- Reboot
- Restore all apps with TB
Wifi working, camera working, flawless victory so far !
regards, mistersixt
Click to expand...
Click to collapse
Couldn't restore app with TB, had to it manually. Fortunately don't have a lot of apps.
One issue I have found is that apps are unable to detect my sd card but in MMs Settings sd card shows all fine and can even be able to browse.
I'm using sandisk class 10 64gb card. It was running all fine in previous 5.1.1 Aosp rom.
adrianom said:
In offline charge (powered off)? If so, it was not yet implemented and reboot to os is the standard.
Click to expand...
Click to collapse
i also exercised the device on reboots on your last lollipop rom.
20-80% everything is fine, then 80-95 ~7 reboots, I lately use twrp to charge.
so maybe not an MM specific issue.
i will flash MM tomorrow, if it happens again i will send a log
I have also tested most of the basic tablet functions if not all and they seem to work.... I have a feeling that only charge/reboot/storage problems will have to be fixed ....
Darkmasterhk said:
i also exercised the device on reboots on your last lollipop rom.
20-80% everything is fine, then 80-95 ~7 reboots, I lately use twrp to charge.
so maybe not an MM specific issue.
i will flash MM tomorrow, if it happens again i will send a log
Click to expand...
Click to collapse
This information is very important, this indicate that maybe is a heat alarm when the device reach this level.
One question, you are using the standard charger?
Test the Marshmallow version and if it occurs, report with a log, I'll check this.
adrianom said:
This information is very important, this indicate that maybe is a heat alarm when the device reach this level.
One question, you are using the standard charger?
Test the Marshmallow version and if it occurs, report with a log, I'll check this.
Click to expand...
Click to collapse
yes/no its the v3 edition shipped with my g4 but basically the same. (same power)
will try it with stock one tomorrow.
rshahzad17 said:
One issue I have found is that apps are unable to detect my sd card but in MMs Settings sd card shows all fine and can even be able to browse.
I'm using sandisk class 10 64gb card. It was running all fine in previous 5.1.1 Aosp rom.
Click to expand...
Click to collapse
Same here. Apps can't detect SD card.. But able to see and browse through settings. I have Sandisk 32GB Class 10 card.
Not a deal breaker to me.
Nokia X6 TA-1099 (China variant)
Code:
Code name: DRG
Android version: 8.1.0
Android security patch level: May 1, 2018
Build number: 00CN_2_21F
Android version: 8.1.0
Android security patch level: June 1, 2018
Build number: 00CN_2_29D
Size:[URL="https://ota-filesite.c2dms.com/SWUpdate/500001630"]428.27MB[/URL]
Android version: 8.1.0
Android security patch level: August 1, 2018
Build number: 00CN_2_37E
Size:[URL="https://ota-filesite.c2dms.com/SWUpdate/500001863"]554.67MB[/URL]
Nokia 6.1 Plus TA-1103 (Hongkong & Taiwan variant)
Code:
Code name: DRG_sprout
Android version: 8.1.0
Android security patch level: June 1, 2018
Build number: 00WW_2_29D
Android 8.1 - 9 Pie (V2.29D-V3.45B) Full OTA
Android security patch level: December 1, 2018
Build number: 00WW_3_45B
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/cee1598f44af889a2e20e1c10eddde5b069bff9d.zip
”]1.31GB[/URL]
Rename: DRG-345B-0-00WW-B03-229D-0-00WW-B01-update.zip
Android version: 8.1.0
Android security patch level: August 1, 2018
Build number: 00WW_2_50A
Size: [URL="https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/30ea3979e38ad7927630b1fd21304e164974f2cd.zip"]487.9MB[/URL]
Rename: DRG-250A-0-00WW-B05-229D-0-00WW-B01-update.zip
Android version: 8.1.0
Android security patch level: September 1, 2018
Build number: 00WW_2_50A_SP01
Size: [URL="https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/1d1323a664bb45ced934169d65de4036f6ce71ff.zip"]71.8MB[/URL]
Rename: DRG-250B-0-00WW-B01-250A-0-00WW-B05-update.zip
[STRIKE]Android 9 Pie Beta (V3.25B)
Android security patch level: October 1, 2018
Build number: 00WW_3_25B
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/1688e76cb291e70ce372134e59c481e5cb571f5d.zip”]1258MB[/URL]
Rename: DRG-325B-0-00WW-B05-250B-0-00WW-B01-update.zip[/STRIKE]
Thanks to XDA member @gksrbgh capture OTA links.
Android 9 Pie Stable (V3.30B)
Android security patch level: October 1, 2018
Build number: 00WW_3_30B
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/5b5ef80dac7bcd5c16c169f8c1a3f401b4fa7d28.zip”]1349.5MB[/URL]
Rename: DRG-330B-0-00WW-B04-250B-0-00WW-B01-update.zip
Thanks to XDA member @gksrbgh capture OTA links.
Android 9 Pie (V3.30C)
Android security patch level: November 1, 2018
Build number: 00WW_3_30C
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/8e5b4c4a78c00dc579708fdc1e76c631fa2d5dec.zip”]68.6MB[/URL]
Rename: DRG-330C-0-00WW-B01-330B-0-00WW-B04-update.zip
Android 9 Pie (V3.45B)
Android security patch level: December 1, 2018
Build number: 00WW_3_45B
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/4f9b123bb58ce9c4383d5bbeac5c5607d22074be.zip”]314MB[/URL]
Rename: DRG-345B-0-00WW-B03-330C-0-00WW-B01-update.zip
Android 9 Pie (V3.45D)
Android security patch level: January 1, 2019
Build number: 00WW_3_45D
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/e46b00a257fc362bf71ad088f32269e46f41b38e.zip”]60.9MB[/URL]
Rename: DRG-345B-0-00WW-B03-330C-0-00WW-B01-update.zip
Android 9 Pie (V3.45E)
Android security patch level: February 1, 2019
Build number: 00WW_3_45E
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/f18f60ea0c302ea185e9169fcb02e8b08f10dbcd.zip”]62.2MB[/URL]
Rename: DRG-345E-0-00WW-B01-345D-0-00WW-B01-update.zip
Android 9 Pie (V3.51F)
Android security patch level: March 1, 2019
Build number: 00WW_3_51F
Size: [URL=“https://android.googleapis.com/packages/ota-api/nokia_drgsprout_dragon00ww/2dd33a621901050fb301724925100223fe1b024c.zip”]339MB[/URL]
Rename: DRG-351F-0-00WW-B04-345E-0-00WW-B01-update.zip
Nokia 6.1 Plus TA-1116 (Vietnam variant)
Code:
Code name: DRG_sprout
Android version: 8.1.0
Android security patch level: July 1, 2018
Build number: 00WW_2_37B
Nokia 6.1 Plus TA-1083 (Indian variant)
Code:
Code name: DRG_sprout
Android version: 8.1.0
Android security patch level: August 1, 2018
Build number: 00WW_2_50A
How to Capture OTA Update URL for your Android
Welcome to capture OTA and comments
1. Download the corresponding OTA pack and rename according to naming conventions;
2. Boot Nokia 6.1 Plus to recovery mode, apply update from ADB with 'adb sideload';
3. Enjoy~
Camera Problem NOKIA X6 TA-1099
Hi all, i Purchased 2pcs of Nokia x6 TA-1099 from China and I'm residing in Kenya. The phones are working perfectly fine. Only one problem is one of the phone when i open camera app, the rear camera has redish lines which appear especially in close up. The problem is not there in the other unit which i am using. What maybe the problem? Kindly assist. Do i do factory reset to see if it helps? That phone is used by my sister-in-law and I feel bad because i ordered 2 phones, one for myself and one for her and her unit has a problem. Kindly advice
nimeshbpan said:
Hi all, i Purchased 2pcs of Nokia x6 TA-1099 from China and I'm residing in Kenya. The phones are working perfectly fine. Only one problem is one of the phone when i open camera app, the rear camera has redish lines which appear especially in close up. The problem is not there in the other unit which i am using. What maybe the problem? Kindly assist. Do i do factory reset to see if it helps? That phone is used by my sister-in-law and I feel bad because i ordered 2 phones, one for myself and one for her and her unit has a problem. Kindly advice
Click to expand...
Click to collapse
Updated to "00CN_2_37E"
Xkernels said:
Updated to "00CN_2_37E"
Click to expand...
Click to collapse
Yes. Its updated to the latest android
nimeshbpan said:
Yes. Its updated to the latest android
Click to expand...
Click to collapse
Hallo, i bougth nokia x6 from china market. First immpresion when i look this phone is awesome. But when i try to power on this phone appear message "your device has loaded a different operating system" i think my phone using costum rom. My question is can my phone restore to original firmware (china version) ? Abd anyone give link tutorial to restore my phone? Thanks
PujaseraID said:
Hallo, i bougth nokia x6 from china market. First immpresion when i look this phone is awesome. But when i try to power on this phone appear message "your device has loaded a different operating system" i think my phone using costum rom. My question is can my phone restore to original firmware (china version) ? Abd anyone give link tutorial to restore my phone? Thanks
Click to expand...
Click to collapse
Yes, you can. Please refer here.
https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
Xkernels said:
Yes, you can. Please refer here.
https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
Click to expand...
Click to collapse
Thanks for your answer, one more question. Should i connect to internet during installation my phone?
PujaseraID said:
Thanks for your answer, one more question. Should i connect to internet during installation my phone?
Click to expand...
Click to collapse
It's irrelevant with internet. Good luck.
Xkernels said:
Nokia X6
Model: TA-1099 (China variant)
Code name: DRG
Android version: 8.1.0
Android security patch level: August 1, 2018
Build number: 00CN_2_37E
Nokia 6.1 Plus
Model: TA-1103 (Hongkong & Taiwan variant)
Code name: DRG_sprout
Android version: 8.1.0
Android security patch level: June 1, 2018
Build number: 00WW_2_29D
Nokia 6.1 Plus
Model: TA-1116 (Vietnam variant)
Code name: DRG_sprout
Android version: 8.1.0
Android security patch level: July 1, 2018
Build number: unknown
Nokia 6.1 Plus
Model: TA-1083 (Indian variant)
Code name: DRG_sprout
Android version: 8.1.0
Android security patch level: August 1, 2018
Build number: 00WW_2_37E
Welcome to comment and update info.
Click to expand...
Click to collapse
Do you have anyway to change variant? I want to change from TA-1099 to TA-1116
lhttin said:
Do you have anyway to change variant? I want to change from TA-1099 to TA-1116
Click to expand...
Click to collapse
Waiting for those stock rom release, then you can convert to Android One.
Does anyone have TA-1103(HK variant, Android One) firmware?
Xkernels said:
Yes, you can. Please refer here.
https://forum.xda-developers.com/nokia-6/help/nokia-x6-nokia-6-1-plus-global-rom-t3822657
Click to expand...
Click to collapse
How to unlock bootloader in Nokia x6(Chinese variant)?
antor999 said:
How to unlock bootloader in Nokia x6(Chinese variant)?
Click to expand...
Click to collapse
You can google it with key: "How to unlock bootloader Nokia 2018", you have to pay 5$ for unlock file.
How to connect Nokia X6 with PC
Hi all
I have one Nokia X6 China Variant, now i want to up Hong Kong Variant.
However, i can not connect Nokia X6 with my PC to copy rom or using adb command to set languages.
Tks so much
https://forum.xda-developers.com/nokia-6-2018/how-to/ota-nokia-6-1-plus-k-nokia-x6-codename-t3839398
You can refer my guide for updating OS.
Hello All,
I appear to have a mish-mash of a spec!
Box says X6
Phone says 6.1 Plus
Model TA-1099
Build 00WW_2_50A
Android One 8.1.0
So, from the look of it, I have the international build (I'm guessing the WW = Worldwide vs CN = China), but I'm confused by the mix of the International "6 Plus" name & the Chinese model number of TA-1099
Can anyone explain? I'm ultimately hoping to be able to flash the phone to get LTE B20 (800Mhz) added to the Baseband, but need to know what I've got to start with.
Thanks.
Camera x2 tele
Can Nokia x6 camera support x2 telephone mode? As it is dual camera. This will be very handy.
Simon75T said:
Hello All,
I appear to have a mish-mash of a spec!
Box says X6
Phone says 6.1 Plus
Model TA-1099
Build 00WW_2_50A
Android One 8.1.0
So, from the look of it, I have the international build (I'm guessing the WW = Worldwide vs CN = China), but I'm confused by the mix of the International "6 Plus" name & the Chinese model number of TA-1099
Can anyone explain? I'm ultimately hoping to be able to flash the phone to get LTE B20 (800Mhz) added to the Baseband, but need to know what I've got to start with.
Thanks.[/QUOTE
Me iether , i want to flash a rom that enable the band 20 lte 800 mhz, there's anyone who can help us?
Click to expand...
Click to collapse
Please which model I can set the language to spanish, The Honk Kong and Taiwan TA1103? Thanks
---------- Post added at 11:07 AM ---------- Previous post was at 10:28 AM ----------
Hello i have exactly the same model and build and the same question, how is it possible to have TA1099 with building ww and Android one? When the updates will end because i read it runs from the release date of the phone and the worldwide model released After the china one , i am in france and the only 4g antenna near my home is a 800Mhz, but it is n't a hardware component ? I dream i could have LTE B20!
Hi
Every time I try to upgrade to LineageOS 16 (Android 9), or any other android version above 7, these are the problems I keep having:
- Microphone from plugged in earphones or headphones does not work. (They work fine on stock android 7 and LightROM android 7 - it's not my hardware)
- Terrible feedback to person on the other end when in a call using speaker (The earphones mic never works, so speaker is the only option. Works fine on android 7 / LightROM)
- GPS usually does not work (always shows me somewhere in the arctic or under china, in an ocean) - I say usually because I haven't bothered testing - whenever I have the earphone problem, the GPS also does not work - but the headphone and speaker feedback thing is most important to me
What I've tried:
- Upgrading baseband/firmware version to latest
- Making sure it's not the hardware. It's not the hardware.
- Checking permissions. They're fine.
- No, I don't have Xposed installed, but when I do, nothing changes
I'll be unimaginably grateful to anyone that helps me solve this...
I've had similar problems even in ResurrectionRemix and LineageOS 15.1 - seems that I have similar problems any time I use a version different than android 7.
Everything else is great, but if the only way I can have a call is by holding the phone up to my ear all the time, no thanks...
bluetooth connections for output or input do not work either...
Here are my android settings currently on LineageOS 16:
Android version
9
LineageOS version
16.0-20190816-UNOFFICIAL-zerofltexx
LineageOS API level
llama (9)
Android security patch level
1 August 2019
Vendor security patch level
1 January 2019
Baseband version
G920FXXU6ESG2
Kernel version
3.10.108-Hyper-flx-gec59af9
#2 Fri Aug 16 03:57:52 UTC 2019
Build date
Fri Aug 16 17:52:49 UTC 2019
Build number
zerofltexx-userdebug 9 PQ3A.
190801.002 eng.enes_a.
20190816.174418 test-keys
As I said several times, if someone starts to build the current version of the lineage that I do, I completely close the project.
In May, I closed the port, based on 10 android and now the time to completely close all work on exynos7870. There was only one reason why I didn't do it earlier - I promised to fix the sound during calls in the LTE version. Now all done, I dont have any desire and motivation to do anything for the exynos7870.
This decision is final, I switched now to the work on note pro 12.2 wifi variant, my smart home and think about starting tab s6.
Thanks to everyone who has been with me all these years, I will see you on other projects.
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!
If you want to check firmware - please make backup.
Instructions
1. Install latest TWRP
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
almost all
Known Issues
Lineage Builds
SM-T580
15. 20200815: august security patch: https://drive.google.com/file/d/1m67wMYmMbQOCoNLxalgJ9Pv6T7ruQ2G6/view?usp=sharing
14. 20200630: june security patch, review device tree, switch to samsung stock sound: https://drive.google.com/file/d/1xgvXjydnklYZeVHz6Mumgf7jUAm6oSEz/view?usp=sharing
13. 20200412: april security patch: https://drive.google.com/file/d/1Isqa8WAlghmCGTMSGnKEsfUX9dUicM0n/view?usp=sharing
12. 20200211: latest sources, February security patch: https://drive.google.com/file/d/1jY2riYpLUJ8EFtOMFSXo9o57_Ijr-qVm/view?usp=sharing
11. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1hnEUDgcugxBLbhQw5d-q9mU75rierlZX/view?usp=sharing
10. 20191202: rollback video driver to r22, merge kernel up to 3.18.140 (thanks @followmsi), aptx driver (thanks @followmsi): https://drive.google.com/file/d/1K_K6yfJHmjCNJSR12eAh46-7FhagcT4Z/view?usp=sharing
9. 20191116: november security update: https://drive.google.com/file/d/1CcX6FnTon8OxM99qbUad9NW6rPrJbUgw/view?usp=sharing
8. 20191114: beta version: update video driver up to r28, update omx codecs, latest updates from @followmsi: https://drive.google.com/file/d/18axNa2sq6ekZeADBzTZeXlOOaJ1dg8WN/view?usp=sharing
7. 20191028: disable Codec2.0 components (long delay on start youtube) (thanks @followmsi), fix vulkan libs (thanks @followmsi): https://drive.google.com/file/d/1mAAEstZz9sOSCFWZiujaGKv-kkslIEwV/view?usp=sharing
6. 20191013: audio from sources: https://drive.google.com/file/d/1R6JDLG-H8bP6eGvex7R2PTYsCbrfQpdu/view?usp=sharing
5. 20191007: fix sensors: https://drive.google.com/file/d/1XsQ5qlP22XBGFQK6o1zKT0GLbVd_WlC7/view?usp=sharing
4. 20191003: https://drive.google.com/file/d/1LpthwW1Lf4fJW0nGwsThnJcZ8ToTKpUf/view?usp=sharing
3. 20190929: improved stability: https://drive.google.com/file/d/1qfKSQhDOI4LkthCpOckJLew0zIAZHo67/view?usp=sharing
2. 20190928: fix charger, home button: https://drive.google.com/file/d/1HBaqEwLux9XjTVgHT3IGMXnrCuJaqgTw/view?usp=sharing
1. 20190926: https://drive.google.com/file/d/1z5VCwOX9M8-ckb1Wt75oON6aUjMpx2hT/view?usp=sharing
SM-T585
15. 20200815: august security patch: https://drive.google.com/file/d/1OgIcsnfRRr5bFx5gd1kvKvtb8lELIMQa/view?usp=sharing
14. 20200630: june security patch, review device tree, switch to samsung stock sound: https://drive.google.com/file/d/110Zz5mlotOnDuFAjtuC5vNKa4VU1N0_I/view?usp=sharing
13. 20200412: april security patch: https://drive.google.com/file/d/1-llAbO2lZQ2T1qq743MxXZNtuHp7eAUX/view?usp=sharing
12. 20200211: latest sources, February security patch: https://drive.google.com/file/d/1l0APlqEK20cgJIGbBzaaekBIJrNFkilr/view?usp=sharing
11. 20200113: latest sources, January security patch: https://drive.google.com/file/d/1OskSZS28m268HRcTeTqFO_HQKB7NgWky/view?usp=sharing
10. 20191202: rollback video driver to r22, merge kernel up to 3.18.140 (thanks @followmsi), aptx driver (thanks @followmsi), fix hotspot: https://drive.google.com/file/d/1hbwkqI1jpctUUitA0Zg1a3LPj02KfSTS/view?usp=sharing
9. 20191116: november security update: https://drive.google.com/file/d/1eb_RdaAw6JSCNb_EsSUsPQnvCqGF_OeF/view?usp=sharing
8. 20191114: beta version: update video driver up to r28, update omx codecs, latest updates from @followmsi: https://drive.google.com/file/d/1cewbOdJapapRjBbk1X8k2mv9B5viBPlD/view?usp=sharing
7. 20191028: disable Codec2.0 components (long delay on start youtube) (thanks @followmsi), fix vulkan libs (thanks @followmsi), fix hotspot (there is still a bug - you cannot turn on wifi after activating a hotspot? need reboot tablet, but at least hotspot working): https://drive.google.com/file/d/1mqsNknYnJSh5cbml7dQ-xd5m0a-KlyCm/view?usp=sharing
6. 20191013: audio from sources: https://drive.google.com/file/d/1ymo05w9m9xukDsfLrZz6iBJMKNgarF4x/view?usp=sharing
5. 20191007: fix sensors: https://drive.google.com/file/d/14jOLZjLPyClboBZ8H3C2O6Dt0kFmXghS/view?usp=sharing
4. 20191003: ril: https://drive.google.com/file/d/18ZPRh19Rao1xRPQ5zI9jz7WfYIdonLZ2/view?usp=sharing
3. 20190929: improved stability: https://drive.google.com/file/d/1H5iinjtP2MBObqE-QWqWP0IMN_rRqK9Y/view?usp=sharing
2. 20190928: fixed charger, home button: https://drive.google.com/file/d/1bog0dKKJ17eXa7vgu9cB0K1U8XWTqBzb/view?usp=sharing
1. 20190926: https://drive.google.com/file/d/1Inx1A-6VNqtJJhTO3rmodKL2tiS1x8LH/view?usp=sharing
Gapps
https://opengapps.org
Platform: ARM64
Android: 10.0
Root
Install latest magisk from canary channel (version 20.1+): https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
TWRP
official twrp:
SM-T580: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html
SM-T585: https://twrp.me/samsung/samsunggalaxytaba101lte2016.html
Sources
Sources: https://github.com/lineageos
Kernel: https://github.com/Valera1978/android_kernel_samsung_exynos7870
Device: https://github.com/Valera1978/android_device_samsung_gtaxllte and https://github.com/Valera1978/android_device_samsung_gtaxlwifi
Vendor: https://github.com/Valera1978/android_vendor_samsung_gtaxllte and https://github.com/Valera1978/android_vendor_samsung_gtaxlwifi
Thanks
Thanks to LineageOS team
XDA:DevDB Information
[ROM][SM-T580][SM-T585][UNOFFICIAL] Lineage 17.0 | Android 10 Q | 64bit, ROM for the Samsung Galaxy Tab A series
Contributors
Valera1978, Valera1978
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
Based On: lineage
Version Information
Status: Beta
Created 2019-09-27
Last Updated 2019-09-27
Finally, I finished the first version of the new android q.
Initially I thought it would be an easy walk. But google in the new version made a huge amount of changes. And I spend about weeks to made something working.
I rebuild the config, wrote a library with sensors from scratch, there were big problems with wifi and sound. For the sound, I had to build a 32bit version to get the missing libraries.
hello how r u?
thx for your great works,
i always try your roms and you are the best
please is there any bugs for t585 before i try it?
and can u tell me how can i backup all of my phone with internal storage like norton ghost on windows pc?
can u tell me your telegram channel?
Hi, thanks for your great work.
I have installed and tested. For now this I have found:
- Magisk 19.3 and 19.4 do not work. Do not start the rom after installation.
- The battery percentage cannot be displayed in the status bar.
Seems to work GREAT on the 580, the only problem i have is I cant use the home button to wake the tablet. I've tried to configure the buttons in setting but it doesn't work. Only the power button will wake it....
michaeljr10wv said:
Seems to work GREAT on the 580, the only problem i have is I cant use the home button to wake the tablet. I've tried to configure the buttons in setting but it doesn't work. Only the power button will wake it....
Click to expand...
Click to collapse
Same here thanks for rom Valera
When my T580 boots, I get a message saying there is an internal error and to contact the manufacturer. I just ignore it and everything seems to work ok. That and the battery % are the only two nits I've come across so far.
lewmur said:
When my T580 boots, I get a message saying there is an internal error and to contact the manufacturer. I just ignore it and everything seems to work ok. That and the battery % are the only two nits I've come across so far.
Click to expand...
Click to collapse
I have that fault also with SM-T580 and in the Xiaomi Mi A1. It is a fault of Lineage. Just ignore it.
Clash Royale and Brawl Stars work great. The tablet is very fluid.
Great rom, first custom rome redirects the music via usb to my external dac without
extra app!!! Thanks for your great work Valera1978!
Thanks Valera
It works much smoother than stock and earlier aosp.
In addition to what the colleagues mentioned, it happens to me that in Google Chrome I open two tabs and restart the tablet
On the other hand with Firefox in a quick test of several tabs this did not happen.
Thank you for your spectacular work.
Thanks for the Android 10. Fast rom but some random reboot.
This rom look awsome, i will flash it when i will be able to unlock my tablet with the home button
Reboots
Updated to the 09/28 version. Have a problem with the tablet rebooting. I'm trying to use AZ Recorder to record streams from Tubi TV. Start AZ and then Chrome and try to load the Tubi site and the tablet reboots. Did the same thing on the earlier version.
New version 20190929. Hope random reboots now gone away. Was done set of fixes.
Checking few hrs, no any reboots.
Magisk 19.3 and 19.4 unsupported
Nuzza said:
Magisk 19.3 and 19.4 unsupported
Click to expand...
Click to collapse
Yes, checked a bit, magisk modifing init in the boot and somehow corrupt it and then on load init cann't get partitions information from dtb.
And internal su also not finished yet.
My primary phone is xiaomi mi9 - more then month I'm on android q and magisk 19.3 working great here.
I'll back to check magisk soon, I need root too.
Nuzza said:
Magisk 19.3 and 19.4 unsupported
Click to expand...
Click to collapse
I thought Android 10 you need the Magisk 19.5, still canary builds so might have some issues.
Github Tree
Zip File
You can give it a try if you want
Thanks, valera. But dont' work accelerator.
Keeps giving random errors on the sm-t580
Thanks for update. Random reboot go away. I found few bug. Accelerator and recent files display issue. Thanks
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-T350, but I have only tested it for 24 hours. Problems will likley surface later?
BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.
What works.
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store - use pico apps
8. flip flap smart cover
9. audio over bluetooth
Note: first initial boot takes a bit longer, be patient.
Known problems.
1. Home screen text may look fuzzy.
Text on home screen looks funny/fuzzy. This only seems to affect the home screen and nowhere else. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.
Problem is with stock trebuchet launcher and/or its fonts. I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?
Rootless Pixel Launcher | F-Droid - Free and Open Source Android App Repository
F-Droid is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device.
f-droid.org
OR you can use nubianprince's crdroid 10.0 build for this tablet. He used his 9.0 repos and has no problems with fuzzy fonts/text. See
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
OR you can use a fairly recent 16.0 build which doesn't have the problem.
2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.
3. FM Radio is not support since this device doesn't have the LTE functionality.
4. Stock camera does not take picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work.
Open Camera | F-Droid - Free and Open Source Android App Repository
Camera App
f-droid.org
5. BOE panel
For people who get black or blank screens when trying to flash TWRP 3.3.1 or LineageOS or crDroid SM-T350 roms, it's likely you have a BOE sourced panel.
Code:
adb root
adb shell cat /proc/cmdline
The very last parameter will be mdss_mdp.panel. If you see BOE anywhere in that string, then you have a BOE panel. For example,
mdss_mdp.panel=1:dsi:0:ss_dsi_panel_S6D7AA0_LSL080AL03_BOE_WXGA:1:none
There is a fix as documented at
[ROM][SM-T350][UNOFFICIAL][crDroidAndroid-10.0][v6.17][ANDROID 10] Galaxy Tab A 8.0
Finally this thread is back :)
forum.xda-developers.com
Thanks/Credits
Thanks to @nubianprince and @lividhen99 for ideas and suggestions on getting this build to work. I used one of nubianprince's repos for this build.
FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.
Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-T350. You can try it on variations, but don't be surprised if you get bootloop or bricked hardware. In addition, I won't build it for the 355 (LTE) version.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.
Q3) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or 3.5.0.9. Get it from
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
Q6) What is the difference between this rom and crdroid?
A6) Use this rom, crdriod or stock. It's not a popularity contest, so use whatever fits your needs. I only offer this as an option for those who want or need a new rom. Most of the code is the same between this rom and crdroid, however, the way we implemented the fixes might be slightly different. In addition, if there is a bug in this rom, it may not be in crdroid due to coding differences and how it's fixed.
Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.
Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. I have uploaded the repo diff and roomservice.xml file. The kernel source files are at
Samsung MSM8916 Devices
Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.
github.com
The repo diff is what I changed compared to "stock" msm8916 code. The majority of the repo diff is because there's a bug in 17.1 WiredAccessoryManager.java and I reverted back to the 16.0 code. The bug prevents audio through the headphone jack. See
https://forum.xda-developers.com/showpost.php?p=83445681&postcount=13
Q9) Where can I download this rom?
A9) You can find the 2020 17.1 and 16.0 builds at
Downloads for : Samsung Galaxy Tab A 8.0 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.
2021 builds found at
retiredtab - Browse /SM-T350/17.1 at SourceForge.net
sourceforge.net
TODO
1. document and upload long list of fixes you need to build 17.1 if you want on your own.Done.
2. mirror nubianprince's repo in case it gets deleted.Done.
3. upload some files, fixes and documentation to github for future.Done.
Dec 13, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).
Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).
Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,700 files had to be recompiled).
Sept 17, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,500 files had to be recompiled).
Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 4500 files had to be recompiled).
July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).
June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 5400 files had to be recompiled).
May 10, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.
April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.
Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.
3. Stock camera does not save picture on front facing camera. Use open camera instead. I don't know when stock camera was broken, but when I tested the March 7, 2021 build, it doesn't work. I never use the camera or video recording on the tablets.
Release notes for Feb 10, 2021
1. Feb 5 security patches.
2. fixed audio over bluetooth. Huge thanks to @nubianprince for helping with suggestions and his repos. The problem was that some of the audio xml files weren't being copied over in 17.1 because of some directory changes to hardware/qcom.
3. Whatever LineageOS changed since last Jan 2021 update.
Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Dec 2020 update.
4. For some reason after flashing the rom, TWRP 3.3.1 now says "unable to mount storage". I had never seen that before. Nevertheless, if you reboot, the rom will work fine. I test all my builds before uploading.
Release notes for Dec 14, 2020
1. Dec 5 security patches.
2. Changed some error messages to verbose to stop spamming log files.
3. Whatever LineageOS changed since last Nov update.
4. Add timekeep functionality since SM-T350 has no real time clock. This allows the tablet to keep time when not used with a NTP (network time protocol) server. It works in Android OS and TWRP.
Nov 8 release
- Nov 5 security patches
Oct 8 release
- Oct 5 security patches
Sept 13 initial release
- Sept 5 security patches
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively - built into 17.1 kernel code
- based on stock github MSM8916 T350 code with a LOT of bug fixes and using one of nubianprince's repos
Oct 8 build released. See post #4 for changes.
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
See this logcat:
Code:
01-18 08:52:10.608 680 680 I SystemServer: StartAlarmManagerService
01-18 08:52:10.611 680 680 D AlarmManagerService: Kernel timezone updated to -480 minutes west of GMT
01-18 08:52:10.611 680 680 I AlarmManager: Current time only 1471930611, advancing to build time 1602188073000
01-18 08:52:10.611 680 680 D AlarmManagerService: Setting time of day to sec=1602188073
10-09 04:14:33.001 680 680 W AlarmManagerService: Unable to set rtc to 1602188073: Invalid argument
10-09 04:14:33.006 680 680 D SystemServerTiming: StartAlarmManagerService took to complete: 10ms
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them. The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Hope it could be solved.
Which TWRP image are you using? I've seen a couple different ones, but since there's no official support over at http://twrp.me/ I'd prefer to use the same one you're using to test this ROM installation...
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
I'll take a look, but right now I have a big project that I need to get finished by mid November so my time for building and troubleshooting roms is limited right now.
reukiodo said:
Which TWRP image are you using?
Click to expand...
Click to collapse
TWRP 3.3.1
Hexrotor said:
The logs about BOEpanel of crdroid are same with Los, but may be different in other places.
Click to expand...
Click to collapse
These messages
D modemanager: Panel Name: S6D7AA0_LSL080AL03_BOE_wxga_video_mode_dsi_panel
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: instantiateModeMgr: Failed to update default cache!
E modemanager: readXMLOp:Couldn't open OEM XML file!
E modemanager: retrieveMode: Failed to enumerate modes
E modemanager: in applyDefaultMode fail to retrieve default mode!
I modemanager: in applyDefaultMode ret = 0 mCurMode = -1
are from the proprietary module (which is why I couldn't find them in the AOSP code)
system/vendor/lib/libmm-qdcm.so
If you search for those keywords above, they all appear in this module.
At this time, I have no idea what the libmm-qdcm.so does and how it controls the backlight, if at all.
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
spiramedia said:
can someone provide link for twrp 3.3.1 for t350? i just can't find it.
Click to expand...
Click to collapse
From
https://forum.xda-developers.com/galaxy-tab-a/development/rom-galaxy-tab-8-0-t4158163
TWRP 3.3.1 is at
https://drive.google.com/file/d/14T99LQaKtEhGeglFxrUm0kMRw_RKopP5/view
me t350 just shut's down on his own. clean install.
spiramedia said:
me t350 just shut's down on his own. clean install.
Click to expand...
Click to collapse
Works fine for me and others.
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Hexrotor said:
@spiramedia Maybe your device is using BOE panel, try to Illuminate the screen with a flashlight.
Click to expand...
Click to collapse
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
spiramedia said:
mine is BOE. But i have no problem with this. The tablet just shuts down when using it. Maybe it overheats.
Click to expand...
Click to collapse
@spiramedia, when asking for help, it helps us if you provide maximum information. For example,
1) What are you running when the tablet shuts down? High performance gaming? Watching youtube?
2) How long does the tablet run before shutting down?
3) Maybe your battery is really old and weak especially if you used it daily for 5 years?
4) If you think it overheats, you can download several CPU apps that tell you the temperature of the CPU like
https://f-droid.org/en/packages/com.kgurgul.cpuinfo/
5) If the battery is old and weak, does it shutdown when you have the AC microusb adapter plugged in all the time?
6) When it shuts down, what is the battery percentage at?
7) Is your battery guage calibrated properly? If it says 30%, maybe it's really 0% and you have to discharge/recharge 2 or 3 times to recalibrate?
As you can see, I asked a lot of questions. The more info you can give, the better.
PS. If you have a BOE panel and backlight works, then I have no idea why my rom works with yours and not Hexrotor.
Hexrotor said:
I set the time to Oct 18 but it was changed to Jan 18 after reboot, then October 9. I remember that crdroid have the same issue.
Click to expand...
Click to collapse
@Hexrotor, does this happen if you date and time setup to "use network provided time".
If I turn "use network provided time" off, then yes, the tablet doesn't keep time properly. I think it's due to the Qualcomm RTC being read only? Searching the Internet, a possible fix might be
https://github.com/LineageOS/android_hardware_sony_timekeep
I might try incorporating that into the next rom build which will likely be sometime mid Nov when the next security patches are released.
I think it's defaulting to Oct 9 because the build date is Oct 8, but in your timezone, it might be Oct 9.
Hexrotor said:
Backlight problem is still in my BOE device. I don’t know which logs are necessary, so I kept most of them.
Click to expand...
Click to collapse
The error messages for the BOE panel are just before the system stops the boot animation and gives the 3 dots and says LineageOS. I find that to be confusing because I would think the kernel would enable BOE backlight at the very beginning so you can see what is on the display. It makes no sense to have the backlight completely dark and then enable it just before the 3 dots that says LineageOS.
And if spiramedia's BOE backlight works with my rom, then I don't know why it doesn't work with yours. Maybe there is something persistent in one of the persist partitions where a prop is set?
Hexrotor said:
Backlight problem is still in my BOE device.
Click to expand...
Click to collapse
@Hexrotor, you didn't specify in this thread or the original crdroid thread whether you tried downgrading the stock to marshmellow and then try crDroid 10 or LineageOS 17.1.
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
retiredtab said:
Apparently, it fixes the no backlight for some people? See
https://forum.xda-developers.com/showpost.php?p=83488241&postcount=41
It's possible the marshmallow firmware has something coded into the file system partitions that fixes the BOE? Maybe someting in the aboot partition?
Let me know if you have tried downgrading or not as per above.
Click to expand...
Click to collapse
Nope, I tried this way but no help. I flashed marshmallow firmware then Crdroid6.9 without clean, it was no display but heated up at boot. I waited for about 10min but it didn't boot complete. Edit: I tried again just now, it booted successfully but still no backlight. Now I'm using official marshmallow.
I don't know why this ROM works with spiramedia's BOE device. I have some friends who have T350/P350 BOE devices and all they have backlight problem with 3-part ROMs, that’s why I am sure that the backlight problem is related to BOE.
For Los 17 and Crdroid, my device has no backlight after the "Samsung Galaxy Tab A", but official marshmallow works fine.