1. test .zip file for integrity.I cannot install it via TWRP. After "Checking for Digest file . . ." its says:
"Failed to map file " and "Error installation zip file"
2. install latest TWRP (which is 3.3.1).
1. test .zip file for integrity.I cannot install it via TWRP. After "Checking for Digest file . . ." its says:
"Failed to map file " and "Error installation zip file"
The zip-file unzips without problems on my Laptop (Linux)1. test .zip file for integrity.
2. install latest TWRP (which is 3.3.1).
The zip-file unzips without problems on my Laptop (Linux)
Also I reloaded it again to be sure.
I had already TWRP 3.3.1 loaded just yesterday .
use twrp 3.2....i already test the latest twrp and the installion error so i go back to twrp 3.2 hope it will help
As others have mentioned TWRP 3.3.1.0 gives errors when installing this rom.
TWRP 3.2.3-0 worked fine for me installing this rom.
Changelog
3.01.2020 - build #5
- Sources update (December 2019 ASB)
- New kernel based on 3.0 (i9100) - credits to @rINanDO
- LiveDisplay fix
- SIM detection fix
Known bugs:
- GPS
- LED charging indication doesn't work
- Gralloc sometimes runs out of ION memory. This can cause uncorrect work of some WebView or 3D applications.
Download:
https://androidfilehost.com/?fid=4349826312261692243
Changelog
3.01.2020 - build #5
- Sources update (December 2019 ASB)
- New kernel based on 3.0 (i9100) - credits to @rINanDO
- LiveDisplay fix
- SIM detection fix
Known bugs:
- GPS
- LED charging indication doesn't work
- Gralloc sometimes runs out of ION memory. This can cause uncorrect work of some WebView or 3D applications.
Download:
https://androidfilehost.com/?fid=4349826312261692243
[*]initial release
[/LIST]
i hope, not. because LED charging light is the most annoying feature. if it's returned, at least, there should be a way to disable it.LED charging indication doesn't work and i hope will be fixed by you in future updates .
It's an intentional change. As a lot of batteries are discharging completely at 20-30%, better to adjust charge level accordingly. In the worst case scenario, the battery will just last longer than usually at 0%.@ChronoMonochrome
Good day. I'm not sure whether this has been mentioned already, but the latest version of this ROM shows a battery level lower than the one reported by a 7.1 Nougat LOS ROM or even TWRP. The difference is of roughly 20 points percent. The battery is an original Samsung one for I9300.
GPS works but takes a long time for a fix and had constant accuracy issues during my testing. I have not used the ROM with a SIM/mobile connection.
Thanks for confirming it to work, good to know it works at least for anyone.i dnt knw how others GPS not work properly but my phones GPS works fine and fast in google maps web view .
Ok, I guess I could include it as an optional feature while keeping it disabled by default.LED charging indication doesn't work and i hope will be fixed by you in future updates .
Thanks, I didn't notice that.also please edit title of thread, the date is typed wrong : [3.12.2020]
[ROM][UNOFFICIAL][9.0.0] LineageOS 16.0 [BETA][3.12.2020]
i hope, not. because LED charging light is the most annoying feature. if it's returned, at least, there should be a way to disable it.
Ok, I guess I could include it as an optional feature while keeping it disabled by default.
Thanks, I didn't notice that.
Even now, it took me a minute to realize what's wrong with the date :laugh:
It's an intentional change. As a lot of batteries are discharging completely at 20-30%, better to adjust charge level accordingly. In the worst case scenario, the battery will just last longer than usually at 0%.
The thing is that the kernel switched back to 3.0.101, I should have considered it earlier, as any newer kernels just works much worse on this hardware for some reasons.i installed this rom 2 days ago and charged battery full after that , 1 night with wifi and gps [On] battery lost 13 percent of power , other roms loose power of 50 percent or much more, i used it regularly and less and after 2 days still i have power and battery is 43 percent without entering charger . I want to say that
this rom's battery keeping is very good and when you keep it on stand by you can use it longer .
I should mention, it's not my work, it's taken from S2 kernel (the authorship of the currently used kernel and this patch belongs to @rINanDO).
Thanks for the observation!also i noticed that when your phone is ringing in your pocket or if you hold your finger on the proximity sens , the proximity sensor is activate by ringing phone , and this is the black screen that some guys talking about that . i hope you fix this too and delay the activation of proximity sensor after an answering the call and hold it near your ear .
I didn't consider adding an UI patch to activate this, since I thought it's only usable for the microG (which IIRC already has such an option).By the way, I noticed that the ROM supports signature spoofing out of the box, but there's currently no UI to grant the permission to selected apps, even if one could achieve this via "pm grant".
Do you plan to add a toggle in the future, or will you strip the spoofing altogether?
I don't currently have a way to test this out myself, and as I was already aware that there were some difficulties while porting exFAT to 3.0.101 discovered in S2 thread, I've just decided to opt out of exFAT for now. I might re-visit this in the future.Edit: it appears that the kernel you picked doesn't support exFAT, as Android offered to format my card when opting to use it as portable storage, and it is now formatted as vFAT, which I assume to be a plain old FAT32.
I didn't consider adding an UI patch to activate this, since I thought it's only usable for the microG (which IIRC already has such an option).
Are there other usage cases besides of microG?
/*
* Your (probably expired) 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.
*/
su
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
A rough timestamp of when the issue occurred is also useful.
to quickly & easily capture logcat (Main log), Kernel log (dmesg) & Last Kernel log (last_kmsg which is important in case of unwanted reboot) without using a computer + adb or use a Terminal emulator on the phone:
Done! And make the dev happy.
- Root the phone
- Developer Options > Store logger data persistently on device > select All. More info about it here on developer.android.com
- Install the free SysLog. (screenshot)
View attachment 4644180
- Reboot the phone & reproduce the problem(s).
- Open Syslog & select logcat, dmesg & last_kmsg. Add some significant keywords in the bottom including in Notes describing the bug & hit Take log.
- The individual logs + a .zip of all of them will be saved in /sdcard/Syslog. You must rename them .txt to be able to attach them to an XDA post like logcat.log > logcat_log.txt for example. Or you can choose Share which will .zip them & then you can attach to a post or upload somewhere & link to in your post if the .zip is too big for XDA's attachment service (20 MB max).
***
Bug Reports & Logs?
If the phone is not rooted you can grant this permission to enable Syslog using ADB (15 seconds ADB Installer) & a computer:
You can also install an app like MatLog to analyse the logcat, filter it, search in it, export files etc but Syslog is fast & easy. If not rooted grant permission for MatLog:
- adb shell pm grant com.tortel.syslog android.permission.READ_LOGS
***
- adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Mr @ChronoMonochrome
Given that the lineageos team has begun merging LOS 16 to LOS 17 ...
Will you be back to this device(S3 i9300) with Android 10?