{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is a combined thread for the A series Exynos7580 based devices.
What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP for your device
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
Flash the latest LineageOS 18.1
Opengapps
(Magisk if required)
Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
Make a full backup
Flash in this order:
LineageOS-18.1
OpenGapps 11
(Magisk if required)
And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE
Thanks
@Stricted
@dariotr
@Androbots
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present
If you like my work consider buying me a coffee:
Source Code: https://github.com/LineageOS
Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_a7xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common
Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580
ROM OS Version: Android 11
Based On: LineageOS
Version Information
Status: Stable
Created 2020-08-20
Last Updated 2022-06-15
Changelog:
Changes 09-04-2023:
Synced to latest LineageOS source (including March security patch)
Changes 18-01-2023:
Synced to latest LineageOS source (including January security patch)
Included patches missed in last build
Changes 19-08-2022:
Synced to latest LineageOS source (including August security patch)
Changes 15-06-2022:
Synced to latest LineageOS source (including June security patch)
ZRAM now mounted with discard option (thanks @JPCastillo2000 for the link)
Changes 26-04-2022:
Synced to latest LineageOS source (including April security patch)
Changes 15-03-2022:
Synced to latest LineageOS source (including march security patch)
Spoiler: Older changelog
Changes 20-01-2022 (all devices):
Synced to latest source (January security patch)
Enable WiFi display
Switch to GNSS HIDL service (improves GPS stability, thanks @retiredtab @impasta)
Fixed power profile switching (restores correct CPU speed when going back to balanced mode)
Changes 20-01-2022 (A510F/A710F):
Enable fastcharge hal (allows disabling fastcharge)
Changes 19-10-2021:
Synced to latest Lineageos (October security patch)
Changes 25-09-2021:
Fixed SDFat bug that caused reboots when accessing sd card (thanks to Ícaro Albuquerque for testing)
Changes 21-09-2021:
Resysnced source (includes updated webview)
Fixed Wi-Fi hotspot (broken in last build)
Added slow/fast charging detection (indicates on lock screen)
Changes 16-09-2021:
Synced LineageOS sources (includes September security patch and AOSP WFD)
Fixed WiFi direct
Added further ZRAM improvements (thanks @alexax66)
Changes 28-08-2021:
Updated ZRAM implementation from Linux 4.1.52
Switched to LZ4 ZRAM compression (should be faster and better)
Changes 24-08-2021:
Synced latest LineageOS sources (includes new lineageos charger animation)
Cleaned up device overlays
Fixed tethering overlays
Disabled BPF offload for tethering (as we dont support it)
Added a7xelte to thread
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
vrobo said:
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
Click to expand...
Click to collapse
Hi,
A search on XDA reveals this write up:
LineageOS 18.1 based on Android 11 is here for nearly 60 devices
LineageOS 18.1 builds based on Android 11 are now available for dozens of smartphones. Here's the changelog and supported devices list!
www.xda-developers.com
On top of this we have a lot of fixes for our devices from security to ram management. The list is too long, if you are interested take a look at the device trees and kernel source on GitHub.
With regards to app compatibility, Android 11 has been out for nearly a year now. If an app you use isn't compatible then to be honest it isn't worth using.
Kind regards,
Danny
vrobo said:
Sorry for my ignorance, could you tell a brief changelog - what are the main differences between Android 10 (LineageOS 17) and Android 11 (LineageOS 18) please?
Any major changes that break app compatibility?
Click to expand...
Click to collapse
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
kurtn said:
Mail app is missing. Make sure you have your mail account details to setup a different client. I recommend FairEmail
Click to expand...
Click to collapse
probably because the Email app is broken?
I've been using FairEmail since I've spotted this problem: https://forum.xda-developers.com/t/...7-1-for-a5-2016.4036151/page-35#post-85302601
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.
How are the plans for going official? That determines how to handle forks with signature spoofing.
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.
So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.
Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.
No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.
Edit:
the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
danwood76 said:
Introduction
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11.0, which is designed to increase performance and reliability over stock Android for your device. The port for the Exynos7580 based devices was created by @Stricted and I along with many contributions from other people in the Android community.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This is a combined thread for the A series Exynos7580 based devices.
What works
Everything
What doesn't work
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Any issues will be ignored if you do not provide:
a) Logcat
b) /proc/last_kmsg
c) LineageOS bug report
d) dmesg
Also do not under any circumstances post bug reports if you are using substratum themes or unsupported magisk modules or you have performed any system modifications
Installation
Install the latest TWRP for your device
Make a full backup (just in case something goes wrong)
Do a full wipe (Cache, Data, System)
If this is your first time on a LineageOS ROM format data, you also need to have been running your latest stock OS version
Flash the latest LineageOS 18.1
Opengapps
(Magisk if required)
Do NOT install the TWRP app if prompted, this will most likely cause a bootloop
Upgrade from official 17.1
Make a full backup
Flash in this order:
LineageOS-18.1
OpenGapps 11
(Magisk if required)
And then this migration zip available HERE
Downloads
Latest unofficial releases HERE
OpenGapps HERE
TWRP is available HERE
Magisk is available HERE
Thanks
@Stricted
@dariotr
The LineageOS team
All the testers on the Discord group (https://discord.gg/8fp9cr7)
And all others who have contributed to the Exynos projects past and present
If you like my work consider buying me a coffee:
Source Code: https://github.com/LineageOS
Device trees:
https://github.com/LineageOS/android_device_samsung_a3xelte
https://github.com/LineageOS/android_device_samsung_a5xelte
https://github.com/LineageOS/android_device_samsung_universal7580-common
Kernel: https://github.com/LineageOS/android_kernel_samsung_universal7580
ROM OS Version: Android 11
Based On: LineageOS
Version Information
Status: Stable
Created 2020-08-20
Last Updated 2020-08-20
Click to expand...
Click to collapse
Hi
Why was it not Build for (a7xelte) A710 2016?
setecastronomy said:
Thanks for the build! I tried compiling on my own a week ago but it failed at the kernel.
So far the experimental 18.1 release works "okay". The system performance is slightly better compared to 17.1. It's still not great but I guess this is the best one can expect from an underpowered phone. At least the responsiveness of the inputs has improved, e.g. keyboard is not totally locked while swapping right after start of Maps. And the swap usage in "top" is not jumping crazy between 300-900mb like before, now about 250mb after startup (previously: ~500mb) and remains at around 500mb after a while.
Also, could you please cherry-pick https://review.lineageos.org/c/LineageOS/android_system_vold/+/258169 ? My MicroSD is reported as Unsupported, I saw that mentioned somewhere in the search results of 17.1 thread. I also have an ext4 filesystem there and would like to continue without converting it to exfat.
No glitches found yet apart from the mentioned SD issue. The update from 17.1 went almost smoothly. There was a scary message in TWRP output (something like "mount: command not found") in the teardown process, but it was eventually reported as success.
Edit:
the recommended Magisk source is https://forum.xda-developers.com/t/magisk-the-magic-mask-for-android.3473445/ ? I used that one since it wasn't linked in the top post here. Sadly, its documentation now declares the simple just-sideload-the-apk-file method deprecated but it worked for me just fine.
Click to expand...
Click to collapse
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
mihancad said:
Hi
Why was it not Build for (a7xelte) A710 2016?
Click to expand...
Click to collapse
I will add the a7 on Tuesday, although I am not the maintainer of that device.
kurtn said:
A3 2016 Upgrading from lineage.microg.org 17.1 to this unofficial 18.1 (no GApps) went smoother as expected. Only one error in flashing the migration zip. No problem with booting.
How are the plans for going official? That determines how to handle forks with signature spoofing.
Click to expand...
Click to collapse
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.
Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).
Kind regards,
Danny
Thank you, my brother, I look forward to it
Thanks a lot for developing new OS for our A310f, Dan. Great work, I runs fine, flowing perfect!!
danwood76 said:
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card.
Click to expand...
Click to collapse
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).
And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.
danwood76 said:
You are much better off switching to exfat.
Click to expand...
Click to collapse
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2
08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096
08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space
08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67)
--------- beginning of kernel
(and the boot sequence, apparently)
After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.
So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
setecastronomy said:
So they told me but I beg to disagree. The card is almost 6yo, no IO errors found yet, reading/writing speed maxes out the USB2.0 speed. It's good Samsung PRO. Its predecessor (some AData model) was almost trashed within two years (almost means: no IO errors but so slow in certain regions that it's not fun to use anymore).
And the reason for using ext4 is the storage API madness which has hit Google devs with Android 6.0 or so, using this (for permission management) and a specific user as filesystem owner made the life a lot easier.
And so I tried. tar everything, mkfs to exfat, untar. Results: tried to configure the card as "portable storage" and it worked Kind of. Navi app fails to use it's data folder there, music app (MortPlayer) finds to find the media data there. File manager can browse through the files, though.
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
08-23 19:43:03.737 2275 2275 D vold : exfatprogs version : 1.1.2
08-23 19:43:03.738 2275 2275 D vold : ERROR: /Android/data/net.osmand.plus/files/rendering/default.render.xml: first cluster is wrong. Truncate (y/N)? n
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: checking stopped. directories 1256, files 12597
08-23 19:43:03.738 2275 2275 D vold : /dev/block/vold/public:179,33: files corrupted 1, files fixed 0
then some other stuff and after few minutes this:
08-23 19:55:04.231 2479 2494 D installd: Device /data has 129531904 free; requested 1048576000; needed 919044096
08-23 19:55:04.633 2479 2494 D installd: Refusing to clear cached data in reserved space
08-23 19:55:04.634 2479 2494 E installd: Failed to free up 1048576000 on /data; final free space 129531904: Success
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: java.io.IOException: Failed to free 1048576000 on storage device at /data
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:5200)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:193)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService.access$100(DeviceStorageMonitorService.java:72)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:257)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Handler.dispatchMessage(Handler.java:106)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.Looper.loop(Looper.java:223)
08-23 19:55:04.637 2593 2691 W DeviceStorageMonitorService: at android.os.HandlerThread.run(HandlerThread.java:67)
--------- beginning of kernel
(and the boot sequence, apparently)
After the reboot, there is the "card setup" wizard coming back, asking again "portable storage" or "internal". Selecting "portable" tells that the card needs to be formatted. WAT? How did it work the first time? I went to the shell, and I can mount the block device just fine and read random files from there.
So now, I am at the brink of formatting it as "internal storage" to have my peace again. Google managed to kill this Android feature, it took a while but they got me.
Click to expand...
Click to collapse
Try formatting the card from the phone. I have had issues formatting using Linux and Windows before, even for my stock S9.
Kind regards,
Danny
danwood76 said:
The SD issue you have is a very bad setup. Journaling filesystems (like ext4, NTFS) will trash an SD card. You are much better off switching to exfat. The patch you linked will not be added to LineageOS 18.1.
I will add the a7 on Tuesday, although I am not the maintainer of that device.
The error on the migration zip is actually because of a difference between TWRP and lineage recovery, ignore it.
Official status is going to happen, just need some thorough testing and I haven't had the time to start a thread (until now).
Kind regards,
Danny
Click to expand...
Click to collapse
Will it be ready for download for A7 (a7xelte) today?
mihancad said:
Will it be ready for download for A7 (a7xelte) today?
Click to expand...
Click to collapse
Asking for ETAs is rude. I have already said that I will make a build for the A7 today. But it will be much later on.
setecastronomy said:
When I tried some options with OsmAnd, hopping to configure it use map data from portable memory, it reported something about OS not accepting write permissions (but there was no permission question dialog from the OS!), and that it has to change settings and restart the app. Okay, did so. After the app was restarted, it got stuck for about 10 seconds and then the whole phone suddenly rebooted.
Tried to investigate what happened, and cannot see much, only this:
Click to expand...
Click to collapse
I have just done this on my test A5 and everything worked perfectly, I downloaded 300MB of maps of my region and it all works well. There was a permissions pop up when I first opened the app which i accepted.
The card is my old Samsung 64GB, I wiped the card in my desktop and then allowed the phone to format it, I think Windows/Linux sets some exFAT options that android doesn't like so it is best to let the phone do it.
Kind regards,
Danny
I have just uploaded a small update and added the a7xelte build.
Changes 24-08-2021:
Synced latest LineageOS sources (includes new lineageos charger animation)
Cleaned up device overlays
Fixed tethering overlays
Disabled BPF offload for tethering (as we dont support it)
Added a7xelte to thread
Kind regards,
Danny
danwood76 said:
Asking for ETAs is rude. I have already said that I will make a build for the A7 today. But it will be much later on.
Click to expand...
Click to collapse
I'm sorry, I'm using Google Translate, I just informed you as a reminder.
Thank you very much for your kindness, dear Danny
Just wanted to say that the A510F works very well, except that sometimes the camera doesn't connect.
Thank you for your effort @danwood76 (and maybe others )!
Related
I9100 CyanogenMod 13
Powered with: Linaro and SaberMod!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In brightest day, in blackest night, no lag shall escape my sight. Let those who worship Apple's might, beware my power, Green Lantern's light!
Click to expand...
Click to collapse
cm-13.0-20161216-MARKOX89-i9100 is UP!
Download Folder on AndroidFileHost
AFH calculates md5sum for every build: please, always check it before flashing!
Highlights of the main features:
Kernel is compiled with latest Linaro arm-eabi-4.9 toolchain
Source:
https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/tree/cm-13.0
ROM is compiled with latest SaberMod arm-linux-androideabi-4.9 toolchain
Source:
https://github.com/CyanogenMod
https://github.com/CyanogenMod/android_device_samsung_i9100/tree/cm-13.0
https://github.com/CyanogenMod/android_device_samsung_galaxys2-common/tree/cm-13.0
ART tweaks for devices with less memory, as provided by arter97 and JustArchi
Fix for Google Play Services crashes, as provided by fusionjack
Fix for the infamous "music bug", as provided by Lanchon and zeitferne
Support for Screen Mirroring through Chromecast
Changelog:
BACKPORT: perf: Allow the PMU driver to choose the CPU on which to install events CyanogenMod/android_kernel_samsung_smdk4412
BACKPORT: perf: Introduce perf_pmu_migrate_context() CyanogenMod/android_kernel_samsung_smdk4412
BACKPORT: lockdep: Silence warning if CONFIG_LOCKDEP isn't set CyanogenMod/android_kernel_samsung_smdk4412
BACKPORT: perf: Fix event->ctx locking CyanogenMod/android_kernel_samsung_smdk4412
perf: protect group_leader from races that cause ctx double-free CyanogenMod/android_kernel_samsung_smdk4412
net: ping: Fix stack buffer overflow in ping_common_sendmsg() CyanogenMod/android_kernel_samsung_smdk4412
fbmem: Check failure of FBIOPUTCMAP ioctl CyanogenMod/android_kernel_samsung_smdk4412
fbcmap: Remove unnecessary condition check CyanogenMod/android_kernel_samsung_smdk4412
drivers: video: Add bounds checking in fb_cmap_to_user CyanogenMod/android_kernel_samsung_smdk4412
netfilter: Change %p to %pK in debug messages CyanogenMod/android_kernel_samsung_smdk4412
smdk4412-kernel : do not ignore COB wifi chips CyanogenMod/android_kernel_samsung_smdk4412
smdk4412-kernel : kona wifi module is COB type CyanogenMod/android_kernel_samsung_smdk4412
mobicore: Fix pointer narrowing issues CyanogenMod/android_hardware_samsung_slsi-cm_exynos7420
soundtrigger: fix memory corruption CyanogenMod/android_frameworks_av
version: Set version string to 13.0.5 to reflect security update CyanogenMod/android_vendor_cm
Updating Security String to 2016-12-01 CyanogenMod/android_build
Fix out of bound access in libziparchive CyanogenMod/android_system_core
Unexport OmtpMessageReceiver CyanogenMod/android_packages_services_Telephony
Restrict SipProfiles to profiles directory CyanogenMod/android_packages_services_Telephony
mm-video-v4l2: vdec: Disallow input usebuffer for secure case CyanogenMod/android_hardware_qcom_media
Fix potential NULL dereference in Visualizer effect CyanogenMod/android_hardware_qcom_audio
Handle color bounds correctly in GIF decode. CyanogenMod/android_frameworks_ex
ExifInterface: Close the file when an exception happens CyanogenMod/android_frameworks_base
Isolated processes don't get precached system service binders CyanogenMod/android_frameworks_base
Fix divide by zero CyanogenMod/android_frameworks_av
Fix potential NULL dereference in Visualizer effect CyanogenMod/android_frameworks_av
Decoder: Fixes in handling errors in Mbaff clips. CyanogenMod/android_external_libavc
Decoder: Ignore few dpb errors CyanogenMod/android_external_libavc
resolve merge conflicts of 849c5c7 to mnc-dev CyanogenMod/android_frameworks_opt_net_wifi
wifinative jni: check array length to prevent stack overflow CyanogenMod/android_frameworks_opt_net_wifi
wl12xx: Common WLAN KM build target for reuse by devices CyanogenMod/android_hardware_ti_wlan
Add Reliance Jio India IMS volte apn's CyanogenMod/android_vendor_cm
Fix Reliance Jio India APNs. CyanogenMod/android_vendor_cm
Enable support for groups in External contacts accounts CyanogenMod/android_packages_apps_ContactsCommon
macloader : add n5120 murata MAC address CyanogenMod/android_hardware_samsung
macloader : add n5110 murata MAC address CyanogenMod/android_hardware_samsung
build: repopick: Avoid failing on commits lookup CyanogenMod/android_build
vendor: cm: Add some more BQ maintainers/devices CyanogenMod/android_vendor_cm
build: repopick: Support squashed commits for Change-Id detection CyanogenMod/android_build
build: repopick: Support projects with less than 10 commits CyanogenMod/android_build
repopick: handle revisions with slashes CyanogenMod/android_build
repopick: don't re-pick duplicate changes CyanogenMod/android_build
repopick: try to use remote's default revision CyanogenMod/android_build
Settings: Fix the failing strings CyanogenMod/android_packages_apps_Settings
Contributors: Add maintainer for Xiaomi Redmi 3/Prime (ido) CyanogenMod/android_vendor_cm
SystemUI: Don't vibrate on touchscreen camera gesture CyanogenMod/android_frameworks_base
ActivityControler: Fix BadPacelableException in certain scenarios CyanogenMod/android_packages_apps_UnifiedEmail
Check if Volte is enabled in ImsManager to determine Volte support CyanogenMod/android_packages_apps_PhoneCommon
cmhw: Account for devices that don't use manager0 sysfs paths CyanogenMod/android_hardware_ti_omap4
Support for MODE_ASK in commandline CyanogenMod/android_frameworks_base
AppOps: Do not prune apps that are not present CyanogenMod/android_frameworks_base
cm: Add more Mi 5 maintainers CyanogenMod/android_vendor_cm
Contributors: Add Xiaomi Mi 5 maintainer CyanogenMod/android_vendor_cm
More...
Buildbot:
CPU: Intel Core 2 Quad Q8300 2.50 GHz
MotherBoard: ASUS P5K
RAM: 4 GB Corsair DDR2 667 MHz
Main HD: SanDisk SSD SDSSDP-128G 128 GB SATA 6 GB/s
ccache HD: Western Digital Raptor WD1500ADFD 150 GB SATA 1.5 GB/s
OS: Linux Lubuntu 16.04 "Xenial Xerus" x64
Kernel version: 4.4.0
Donations:
If you're enjoying my work you may consider sending a small donation using this link
Special Thanks:
CyanogenMod Dev Team
Linaro Dev Team
sparksco and the whole SaberMod Dev Team
IAmTheOneTheyCallNeo
Lysergic Acid
JustArchi
fusionjack
Android-Andi
Ziyan
tuxafgmur
Infected_
-Grift-
prace86
jamal2367
XDA:DevDB Information
[ROM][I9100][MM][6.0.1][Linaro][SaberMod] CyanogenMod 13, ROM for the Samsung Galaxy S II
Contributors
Markox89
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
ROM Firmware Required: CWM Recovery
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: CyanogenMod 13
Created 2014-03-19
Last Updated 2016-12-17
How to: Installation and Bug Reporting
Disclaimer (read it before installing the ROM for the first time):
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.
Regarding the compatibility with mods or apps, these builds are as compatibile as official CyanogenMod nightly builds.
Click to expand...
Click to collapse
Installing CyanogenMod 13 on your Galaxy S II:
Copy CyanogenMod 13 zip and a light GApps package of your choosing to your Internal or External SD card;
Make sure you are not running a kernel with the MMC-Superbrick-Bug and you are using latest version of a MarshMallow compatible recovery;
Boot into recovery;
Flash CM 13 zip;
Flash GApps package;
If you're coming from another non-CyanogenMod ROM do a Data Wipe / Factory Reset (otherwise your device will be stuck at boot);
Reboot.
Posting Bug Reports (comply these requisites is mandatory, otherwise your report won't be considered):
Use the newly added Bug Reports tab;
I always test my builds before releasing them and use the latest build as daily ROM for my devices: do not claim it doesn't boot or it gives you force close loops (if this is your case it's either a corrupted download or your phone needs a full wipe);
Clearly state which build are you using (for reporting a bug it needs to be the latest);
Clearly state that you're using the kernel that comes with the build and not a modded one (if you're experiencing issues using a modded kernel, you should refer to the kernel's developer thread);
Clearly state which mods are you using (e.g. Xposed Framework): try to remove the mod and see if the bug is still there;
Clearly state which runtime are you using (e.g. Dalvik or ART); if you're using ART try to switch to Dalvik and see if the bug is still there;
In addition before posting bug reports, test if your bug is also present in the same day's official CyanogenMod nightly; if it is present there, wait until the CyanogenMod Team fixes it or report directly to them;
As a small courtesy, please don't report bugs that can easily be fixed with well known patches (e.g. CWM zips);
GApps related crashes should be reported to GApps package maintainer (at least at first).
F.A.Q (Frequently Asked Questions)
Uff, our device is slow and Screen Mirroring is laggy, can you fix this?
Nope, our device is old and OEM support lacks.
You shouldn't complain about the overall performance or about the performance of some specific features (e.g. Screen Mirroring through ChromeCast).
Your latest build isn't working at all, can you fix it?
I personally test every build before releasing it, so the device will always be usable.
If you experience weird issues or something that's a showstopper for you, you should consider switching to CyanogenMod's official builds, or to another ROM: your device or setup may be incompatible with my builds.
Where can I find CyanogenMod's official builds?
If you're looking for something common or some common infos, you should definitely use xda search engine or Google.
May you give me some informations about your builds?
All the infos about my builds (e.g. technical compilation infos, features and installation guide) are in the first three posts: you should definitely read them before posting.
I saw this cool feature on another ROM, can you include it in your builds?
Nope, sorry, I'm not taking Feature Requests (see that the correspondent tab is missing from OP): you should make Feature Requests to CyanogenMod Team in the ways you prefer.
In addition, you can look for some Xposed Module, maybe you'll find one that can add to my builds what you're looking for.
A new "SnapShot" build is out! When you'll compile a build based on it?
Never, sorry. My builds are compiled from the nightly branch. The "SnapShot" builds are compiled from a dedicated branch; "SnapShot" releases doesn't influence in any way my builds.
I need some technical explanation about the tools you're using, may you provide them?
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124. Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
What is Linaro?
Linaro is the place where engineers from the world's leading technology companies define the future of Linux on ARM. The company is a not-for-profit engineering organization with over 120 engineers working on consolidating and optimizing open source software for the ARM architecture, including the GCC toolchain, the Linux kernel, ARM power management, graphics and multimedia interfaces.
Click to expand...
Click to collapse
Source: http://www.linaro.org/linux-on-arm/
Glad to see you're on your feet now. Good. Looking forward to some good cooking from you. All the best.
Sent from my GT-I9100 using Tapatalk
Glad to see your own thread! :laugh:
Glad to see you in your own new house Markox89 ! Im downloading and trying your new build 1603 :good:
Dear colleagues, my friend has a problem. After installing the firmware and restore applications using Titanium Backup is a window appeared. Today it has been updated on a regular nightly, but it reappeared window. Can this be fixed without full wipe?
blinoff82 said:
Dear colleagues, my friend has a problem. After installing the firmware and restore applications using Titanium Backup is a window appeared. Today it has been updated on a regular nightly, but it reappeared window. Can this be fixed without full wipe?
Click to expand...
Click to collapse
Have a look at this
Hey @Markox89......
Glad to see you here fella.....keep up the DAMN FINE work.......
Sent from my Markox powered, KitKatted S2.....
Nicely Done :good:
New thread, niiice
via Tapatalk
drdays said:
Glad to see you're on your feet now. Good. Looking forward to some good cooking from you. All the best.
Click to expand...
Click to collapse
blinoff82 said:
Glad to see your own thread! :laugh:
Click to expand...
Click to collapse
aiyeumiforever said:
Glad to see you in your own new house Markox89 ! Im downloading and trying your new build 1603 :good:
Click to expand...
Click to collapse
keithross39 said:
Hey @Markox89......
Glad to see you here fella.....keep up the DAMN FINE work...
Click to expand...
Click to collapse
scorpion.hbs said:
Nicely Done :good:
Click to expand...
Click to collapse
MPL92 said:
New thread, niiice
Click to expand...
Click to collapse
Many thanks to all of you...this means a lot to me, for real :')
great work
but this rom better than slimkat and EHNDROIX
amrtare said:
great work
but this rom better than slimkat and EHNDROIX
Click to expand...
Click to collapse
@Markox89 Well done! Sorry to keep you awake to build.
@Markox89 Good luck and thank you for still supporting our s2 [emoji106][emoji106]
I updated from 2014-02-28 build to 03-16 but camera is always crashing while opening... Even after clearing the Caches again and clearing camera app Data... Is there a fix?
cubflyer said:
I updated from 2014-02-28 build to 03-16 but camera is always crashing while opening... Even after clearing the Caches again and clearing camera app Data... Is there a fix?
Click to expand...
Click to collapse
Try replacing the Camera apk with this one, or the one extracted from latest official nightly
Next build should fix the issue, but this can be a good workaround
Sent from my GT-P5110 using Tapatalk
@Markox89 Thanks man!
Thanks for this cook.
Will put an eye on it. Will Try it in the next future.
Any screenshots, or known bugs?
Sent from my GT-I9100 using Tapatalk 2
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LP), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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.
*
*/
BEFORE INSTALLING THIS ROM, MAKE SURE YOUR DEVICE MODEL IS THE SAME AS TITLE
IF YOU ASK ANY QUESTIONS LIKE "IS THIS FOR MODEL BLABLABLA" THEY WILL BE ALL IGNORGED
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
We'll not support users and answer questions from users which:
are running a custom kernel
have flashed mods
modified system files
didn't follow our intructions word by word
are unfriendly
And most important: DON'T READ THE OP
What's working:
Wifi (connection, tethering, etc)
Bluetooth
Camera, video codecs
RIL (Calls, SMS, mobile data)
Storage (both internal and external)
MTP storage (both internal and external)
Offline charging
zRAM (compressed-RAM swap)
GAPPS
Tethering (USB, Wifi, Bluetooth)
GPS
Sound recording
Torch (flashlight)
BUGS/Not working :
There're lots of bugs, but main are
(SM-G313ML) Mobile data doesn't work
Switching to other fonts will get bootloops after restart. In this case, if you use TWRP recovery, go to File Manager >> delete "themes" from /data/system would help you escape this without factory reset
Distorted Bluetooth sound on calls
First time installing CyanogenMod 12.1 to your Galaxy V, or coming from another ROM:
Install TWRP Recovery
Reboot into Recovery using 3-button-combo (Vol-up+Home+Power)
Do a Nandroid backup! (Optional and only if you weren't running TouchWiz before)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)*
Install the ROM from sdcard using TWRP Recovery
Optionally install the Google Apps ( get it here: https://opengapps.org ) (pico GAPPS recommended)
INSTALLATION VIDEO
DEAR KANGERS
Click to expand...
Click to collapse
If you're going to reuse our work, be kind and give proper credits
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-source doesn't mean "out of respect"
DOWNLOADS:
Click to expand...
Click to collapse
In Downloads section
Mirror: Beta 3 Update 1
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy Ace 4
Contributors
doesntexits, ngoquang2708
Source Code: https://github.com/ngoquang2708/android_device_samsung_vivalto3gvn/tree/cm-12.1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock 4.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 3 Update 1
Beta Release Date: 2016-05-28
Created 2016-02-16
Last Updated 2016-06-12
CHANGELOG:
- ALPHA-1
Initial release
- ALPHA-2
Fixed ION driver, now camera, video codecs, etc are working
Fixed audio
Dual-SIM is dead for now
Reserved zRAM size to 128MB
- ALPHA-3
Fully fixed RIL (thanks to @ngoquang2708), will switch to beta on next builds
Fully fixed Bluetooth
- BETA-1
Faster app installation, but slower app startup, a trade-off!
Improve media playback: some media app can play flawlessly, but not YouTube, sorry
zRAM size now can be set in build.prop
thanks to @ngoquang2708
- BETA-2
Fixed audio stuffs
Fixed video decoding stuffs (included YouTube)
Fixed video recording
Don't remember list start, blah blah...
- BETA-3
Updated sources, Android security patch version 2016-04-01
Switched memory allocator to dlmalloc(), which increase performance a lot
Odexed apps now will be in /system partition, not in /data/dalvik-cache anymore (significantly save internal storage, as this thingy eats up to 300MB of our internal storage)
Powered by OC Kernel (unexpectedly compiled )
- BETA-3 update 1: Fixed random reboots, switched to stock kernel
F.A.Q
Q: ROM startup too slow?
A: This device is just a single-core phone, so the first startup is super-duper slow, and some lags are expected during usage
Q: ETAs?
A: See here: Link
Q: Anymore models supported?
A: SM-G313ML, SM-G313H
Q: Is init.d supported on this ROM?
A: Every CyanogenMod ROMs support init.d, so be free at scriptings
Q: Can you include ABCXYZ feature / Samsung Apps here?
A: NO!
Q: Can i use your ROM as a base for portings?
A: Yes, you could, but give proper credits
Q: Status 7 when installing the ROM?
A: Use TWRP recovery to install the ROM, as CWM is not supported yet
Q: Server error in Google Play Store?
A: Install latest Google Play Services manually first (might take long time, due to Lollipop's nature), then you can install apps from GG Play as usual
Finally, I've waiting for a long time for this cm 12.:good:
Cool nice to see more spredtrum device get cm
great work
btw is audio working ?
Dreamstar said:
Cool nice to see more spredtrum device get cm
great work
btw is audio working ?
Click to expand...
Click to collapse
Yes, it's working
Remove audio CFLAGS from BoardConfig.mk and use audio_policy.default, it still working. IDK why
@corphish
A little bit weird here. The coreprimveve3g's binder doesn't have MemoryHeapIon. Just do some "grep", you'll see it.
doesntexits said:
@corphish
A little bit weird here. The coreprimveve3g's binder doesn't have MemoryHeapIon. Just do some "grep", you'll see it.
Click to expand...
Click to collapse
Well grep through Camera or HWC HAL and see whether they are dependent on those symbols or not:/
Anyways, I had a confusion about HWRendering and HWC. I still have tho.
SWRendering means running the system on CPU only, on HWRendering, its done by GPU (and CPU probably). HWC plays a part in it, if HWC is broken, I don't think HWRendering will necessarily be broken. So you were right earlier .
So if on egl.cfg, you are on mali renderer and no kernel.qemu flag set, and everything is fine, then HWRendering works, you would probably mention that HWC is not working. Anyway if that's the case, have you applied this icu4c patch?
Because we have applied it and boom, HWRendering is broken badly. We are on SWRendering now, and its so sluggish.
corphish said:
Well grep through Camera or HWC HAL and see whether they are dependent on those symbols or not:/
Anyways, I had a confusion about HWRendering and HWC. I still have tho.
SWRendering means running the system on CPU only, on HWRendering, its done by GPU (and CPU probably). HWC plays a part in it, if HWC is broken, I don't think HWRendering will necessarily be broken. So you were right earlier .
So if on egl.cfg, you are on mali renderer and no kernel.qemu flag set, and everything is fine, then HWRendering works, you would probably mention that HWC is not working. Anyway if that's the case, have you applied this icu4c patch?
Because we have applied it and boom, HWRendering is broken badly. We are on SWRendering now, and its so sluggish.
Click to expand...
Click to collapse
I haven't patched anything. Just used the source and it still works. Our HW rendering seems working fine, but it's very sluggish if in low RAM mode (damn laggy, lockscreen goes black). IDK why that CPVE works with HWC? Maybe some more "grep"?
Btw, our camera already gives missing symbol in logcat. It disappeared from Trebuchet and if open it from lockscreen, it FCs, so everything related to ION driver are broken for now. IDK why codecs needs ION (failed allocating)
Another question: How to make a link in makefile? Prebuilt webview doesn't work if missing a link to /system/app/webview/lib/arm
Edit: I got wrong question The coreprimeve3g HAL requires those symbols:
Code:
[email protected]:~/Downloads/hw$ strings hwcomposer.sc8830.so | grep Ion
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj
Camera HAL:
Code:
_ZN7android13MemoryHeapIon16IOMMU_is_enabledEi
_ZN7android13MemoryHeapIon9free_iovaEimj
_ZN7android2spINS_13MemoryHeapIonEED2Ev
_ZN7android2spINS_13MemoryHeapIonEED1Ev
_ZN7android2spINS_13MemoryHeapIonEEaSEPS1_
_ZN7android13MemoryHeapIonC1EPKcjjm
_ZNK7android13MemoryHeapIon9getHeapIDEv
_ZN7android13MemoryHeapIon21get_phy_addr_from_ionEPmPj
_ZN7android13MemoryHeapIon8get_iovaEiPmPj
_ZNK7android13MemoryHeapIon7getBaseEv
_ZN7android13MemoryHeapIon9Free_iovaEiimj
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj
_ZN7android13MemoryHeapIon8Get_iovaEiiPmPj
_ZN7android13MemoryHeapIon16flush_ion_bufferEPvS1_j
MemoryHeapIon::Get_mm_ion: %d addr 0x%x size 0x%x
MemoryHeapIon::Get_mm_iova: %d
allocCameraMem: error pHeapIon is null.
allocCameraMem: error get pHeapIon addr - method %d result 0x%x
MemoryHeapIon::Get_mm_ion: %d addr 0x%lx size 0x%x
But... with libbinder:
Code:
[email protected]:~/Downloads$ strings libbinder.so | grep Ion
[email protected]:~/Downloads$
Nothing shown. IDK why. Maybe Sammy has applied ION driver inside those HAL blobs :/
doesntexits said:
I haven't patched anything. Just used the source and it still works. Our HW rendering seems working fine, but it's very sluggish if in low RAM mode (damn laggy, lockscreen goes black). IDK why that CPVE works with HWC? Maybe some more "grep"?
Btw, our camera already gives missing symbol in logcat. It disappeared from Trebuchet and if open it from lockscreen, it FCs, so everything related to ION driver are broken for now. IDK why codecs needs ION (failed allocating)
Another question: How to make a link in makefile? Prebuilt webview doesn't work if missing a link to /system/app/webview/lib/arm
Edit: I got wrong question The coreprimeve3g HAL requires those symbols:
Code:
[email protected]:~/Downloads/hw$ strings hwcomposer.sc8830.so | grep Ion
_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPmPj
But... with libbinder:
Code:
[email protected]:~/Downloads$ strings libbinder.so | grep Ion
[email protected]:~/Downloads$
Nothing shown. IDK why
Click to expand...
Click to collapse
Alright..recursive grep through lib folder
Code:
cd system/lib
grep -R Ion
You mean symbolic link?
Code:
$(shell ln [-OPTIONS] <source> <target>)
corphish said:
Alright..recursive grep through lib folder
Code:
cd system/lib
grep -R Ion
Click to expand...
Click to collapse
Haha, we got our result. MemoryHeapIon is being used as seperate lib.
Code:
[email protected]:~/Downloads/lib$ grep -R Ion
Binary file libstagefright_sprd_h264enc.so matches
Binary file libstagefright_sprd_vpxdec.so matches
Binary file libstagefright_sprd_h264dec.so matches
Binary file hw/camera.sc8830.so matches
Binary file hw/hwcomposer.sc8830.so matches
Binary file libstagefright_sprd_mpeg4enc.so matches
Binary file libomxvpu.so matches
Binary file libstagefrighthw.so matches
Binary file libvpu.so matches
Binary file libstagefright_sprd_mpeg4dec.so matches
Binary file libmemoryheapion.so matches
[email protected]:~/Downloads/lib$
I thought it must be in binder, but we've all wrong
doesntexits said:
Haha, we got our result. MemoryHeapIon is being used as seperate lib.
Code:
[email protected]:~/Downloads/lib$ grep -R Ion
Binary file libstagefright_sprd_h264enc.so matches
Binary file libstagefright_sprd_vpxdec.so matches
Binary file libstagefright_sprd_h264dec.so matches
Binary file hw/camera.sc8830.so matches
Binary file hw/hwcomposer.sc8830.so matches
Binary file libstagefright_sprd_mpeg4enc.so matches
Binary file libomxvpu.so matches
Binary file libstagefrighthw.so matches
Binary file libvpu.so matches
Binary file libstagefright_sprd_mpeg4dec.so matches
Binary file libmemoryheapion.so matches
[email protected]:~/Downloads/lib$
I thought it must be in binder, but we've all wrong
Click to expand...
Click to collapse
Get me that blob plox..and see my earlier post..I did not see your query abt webview
Edit @ doesntexits
Add it and see logs, HWC and Camera HAL should load.
You will probably need a factory reset to make Camera App visible, and the torch toggle too.
Because during first boot, if Camera HAL fails to load, no camera app in system will be viewed even tho its fixed later.
corphish said:
Get me that blob plox..and see my earlier post..I did not see your query abt webview
Click to expand...
Click to collapse
Change it to .so
corphish said:
Edit @ doesntexits
Add it and see logs, HWC and Camera HAL should load.
You will probably need a factory reset to make Camera App visible, and the torch toggle too.
Because during first boot, if Camera HAL fails to load, no camera app in system will be viewed even tho its fixed later.
Click to expand...
Click to collapse
But...
Code:
E/HAL ( 178): load: module=/system/lib/hw/camera.scx15.so
E/HAL ( 178): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIonC1EPKcjjm" referenced by "camera.scx15.so"...
E/CameraService( 178): Could not load camera HAL module
and...
Code:
E/HAL ( 124): load: module=/system/lib/hw/hwcomposer.scx15.so
E/HAL ( 124): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPiS1_" referenced by "hwcomposer.scx15.so"...
E/SurfaceFlinger( 124): hwcomposer module not found
Edit: I "grep"ed again, and those symbols from our libs is different than libmemoryheapion.so. Looks like we've to re-build it for ourselves
doesntexits said:
But...
Code:
E/HAL ( 178): load: module=/system/lib/hw/camera.scx15.so
E/HAL ( 178): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIonC1EPKcjjm" referenced by "camera.scx15.so"...
E/CameraService( 178): Could not load camera HAL module
and...
Code:
E/HAL ( 124): load: module=/system/lib/hw/hwcomposer.scx15.so
E/HAL ( 124): dlopen failed: cannot locate symbol "_ZN7android13MemoryHeapIon21Get_phy_addr_from_ionEiPiS1_" referenced by "hwcomposer.scx15.so"...
E/SurfaceFlinger( 124): hwcomposer module not found
Edit: I "grep"ed again, and those symbols from our libs is different than libmemoryheapion.so. Looks like we've to re-build it for ourselves
Click to expand...
Click to collapse
Alright.
I really liked what Sammy did here, ship memory heap ion as a separate unit. In this way they dont have to adapt binder.
I will do the same too. I will however build on cm11 tree as I dont have cm12.1 tree. Probably you could try and let me know if it builds or not.
Is for smg316m model?
noelpalacios said:
is for smg316m model?
Click to expand...
Click to collapse
read carefully the op please
before installing this rom, make sure your device model is the same as title
Click to expand...
Click to collapse
doesntexits Is most likely the fastest moving developer I have seen. CM11 just stable and a almost stable CM12.
The moment Mobile Data is resolved Ill flash for further testing, unfortunately cant flash without mobile data else work and wife looses contact with me.
tjvvuuren said:
doesntexits Is most likely the fastest moving developer I have seen. CM11 just stable and a almost stable CM12.
The moment Mobile Data is resolved Ill flash for further testing, unfortunately cant flash without mobile data else work and wife looses contact with me.
Click to expand...
Click to collapse
Agree with you.
tjvvuuren said:
doesntexits Is most likely the fastest moving developer I have seen. CM11 just stable and a almost stable CM12.
The moment Mobile Data is resolved Ill flash for further testing, unfortunately cant flash without mobile data else work and wife looses contact with me.
Click to expand...
Click to collapse
Actually, CM12.1 just missing ION driver, which makes camera, codecs and some thingies work. We just need that, else mobile data could be fixed later.
The Prehistory of UltimateROM
About a month ago I decided to set out to improve the performance of my phone with a more optimized build. I had already begun building OmniROM 5.1.1 with a some set of optimizations based on the work of OptiPop Team, and shortly after some the major issues on Marshmallow on our devices were resolved, this idea to create an ultimatively optimized AOSP-based ROM has born.
Why Should You Use UltimateROM? What makes it different?!
Honestly, I don't necessarily care, how many users or downloads my ROM has. Most importantly, and what I do care about is people liking and enjoying their phone; if you try UltimateROM and you like it, great! I'm glad you enjoy it. If you don't, maybe leave some feedback on how I can improve it, and go try something else in the meantime. If you'd like to know, what I've done that makes this ROM unique, here is a list:
Highly optimized. similar to Linaro(and in many ways, better than), build, resulting in a smoother Android
Compeletely developed in the open, everything I do is right on my GitHub for anybody to use and improve upon.
A unique kernel which attempts to balance features, stability, and of course, performance
Almost the sources, excluding apps, the SystemUI and some more, are based on CyanogenMod ones, which means there are more fixes and support for our legacy devices (even though CyanogenMod itself doesn't really support any devices like our, anyway google doesn't even do that minimal support as CM Team does)
Disabled SELinux. Looking backward on how many issues SELinux was causing and still causing for people that use it on MM, it seems to me a ridiculuos how google promotes and implements it everywhere, without any proof of improving anything rather than making worse.
Current Information
Everything I do with UltimateROM I always test personally on my phone, but anyway...
Code:
#include <disclaimer.h>
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or the current economic crisis caused by you following these
* directions. YOU are choosing to make these modifications, and
* if you point your finger at me for messing up your device, I will
* laugh at you.
*/
Please also note that currently I don't test installation with the Gapps. So far installation is only tested as dualboot ROM - though, the uploaded build is an usual one, - please let me know if the uploaded build has issues with booting, even though normally this should not happen.
What's working:
RIL (phone/SMS/3G)
Video (playback & recording)
Audio (playback & recording)
Wi-fi
Bluetooth
Camera (Front and rear)
2D/3D HW Acceleration
USB, MTP, ADB
all native tethers (Wifi/BT/USB)
external storage
What's not
Formatting SDcard as adoptable storage will screw it up (don't format / encrypt)
MTP bug with doubled folders in sdcard root folder
ROM features:
Dark Marshmallow Theme
long volume press to skip track
PA Pie control
SlimRecents / improved AOSP recents
Re-added task manager
Navigation Bar
System UI tuner
expanded desktop
storages are swapped by default
extended reboot menu
customizable button backlight settings
Viper4Android FX
superuser embedded
Download
UltimateROM
Installation
Before installation, make sure that you have enough free space on partition /system. AT LEAST 540 Mb is required for this build if installing WITHOUT any Gapps. If you don't have enough space, follow repartition manual. (at your own responsibility for any kind of possible damage. Be sure to measure twice and cut once!). There is a CWM ReParted zip that was tested by @Culateralligator.
wipe cache
make sure you're using TWRP 2.8.6.0. All the below is only tested on this recovery. Philz is not supported by this ROM and not planned to in the near future. Note that TWRP from the linked topic requires preinstalled chrono kernel.
install ROM first
install latest chrono kernel
install gapps (optional), if you do so, make sure you are not running of space on /system ( about GApps )
Sources:
https://github.com/UltimateROM/android_manifest
Thank Yous
SergeyL - many-many thanks for an initial set of patches, device tree and TWRP 3.0.0.0! Also thanks for helping me implementing some features to this ROM.
JDCTeam, BenzoROM - thanks for great cherry-picks!
MWisBest - this project was heavily inspired by his FML (Fork My Life) ROM
OptiPop - an initial set of optimizations that the currently used by me is based upon
@Meticulus - thanks for his great contributions on our devices!
@AGONTUK - thanks for an initial Marshmallow bring up!
@nieltg - Sources for Galaxy Ace 2 device
@golden-guy - thanks for great cherry-picks !
@TeamCanjica - vendor and hardware sources
@Unjustified Dev - Audio fixes
Google
CyanogenMod
AOKP
SlimROMs
EuphoriaOS
OmniROM
AOSPA
Viper4AndRroid Team
And many other devs, I could forget (please write me if I did so).
Special Thanks
@shaqman89 - for providing the build server
@S.AMU - for providing FTP server
XDA:DevDB Information
UltimateROM, ROM for the Samsung Galaxy Ace II
Contributors
ChronoMonochrome, SergeyL, JDCTeam, OptiPop Team, BenzoROM, OmniROM, AOKP, CyanogenMod, SlimRoms, AOSPA, Temasek.
Source Code: https://github.com/UltimateROM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 4.1.2 ROM or up + kitkat-compatible recovery
Based On: AOSP, CyanogenMod
Version Information
Status: Stable
Created 2016-03-20
Last Updated 2018-08-20
Changelogs
Changelog
20.08.2018 - build #13
sources update
switch to opensource sensors
switch more device libs to open source base
unified codina / janice build
02.12.2017 - build #12
fixed native moving apps to SDcard
APP2SD and similar apps now should work correctly *
fixed second incoming call not to crash rild (not tested, needs confirmation), thanks to @SergeyL
small RIL fixes
NOTE: installation method was updated. Flash latest chrono kernel build after this ROM install.
02.04.2017 - build #11
kernel updated to r5.0
sdcard mount fixes
integrated an unofficial build of the Xposed framework
ported the utility mtools *
* for repairing the broken sdcard label you can move the file /system/bin/mtools to /system/xbin folder, then type in the terminal emulator mlabel/i]. It will show the current sdcard label and will prompt to type the new one.
27.02.2017 - build #10
updated sources to 6.0.1_r78
added an initial support of the PowerHAL *
ported some changes from Resurrection Remix 7.1.1 build (thanks to SergeyL for patches)
updated kernel to r5.x.x (mostly updates from google android-3.4 kernel)
changed recovery to TWRP 3.x.x
unstable MySQL optimizations are reverted
changed buttons backlight mode - backlight is only enabled when buttons are pressed
experimental change scheduling policy of the surfaceflinger to FIFO
maybe, something yet
* at the moment there's no support of changing the PowerHAL profiles from the Settings, however, you can change profile in a file /system/etc/init.d/999powerhal
Proceed installation of this build only with data wipe.
20.09.2016 - build #9
Fully switched to an opensource RIL! Many thanks to Meticulus for finding the working RIL sources and fixing it, also I'd like to thank millosr and mickybart from Nozomi (Xperia S) forum for fixing the crash when performing a call and providing patches for debugging the proprietary libril!
More libs now are built from source - credit goes to Meticulus
Added sdcardfs support (requires at least build r4.8 of Chrono Kernel)
Added home key press to accept the incoming call and power key press to end the active call features from CyanogenMod - thanks to SergeyL for helping with finding those patches
Changed LowMemoryKiller tunables to the more aggressive + increased zram size to 400Mb - multitasking should be (hopefully) better
Changed Dynamic governor tunables to be more aggressive
Various minor fixes that improves the stability of ROM
We've also finally got rid of all shim (i.e. interposed) libraries that were needed in order for some features (camera, GPS etc) to work
30.05.2016 - build #8
updated wifi autoconnection fix (fixed the battery stats)
fixed SystemUI FC when switching USB mode via status bar notification
fixed GSM / WCDMA preferred / WCDMA Only switching
fixed soft reboot when switching 2G/3G with an enabled mobile data
added Pie Control from Paranoid Android
added SlimRecents
updated AOSP recents implementation ("clear all" button doesn't properly work, so don't enable it or use SlimRecents)
added task manager
allowed disabling of brighness slider disabling
revert AOSP camera to 5.1.1 (fixed the photo cropping issue)
added FAT images mounting via UMS support (use
sys.config.opt_sd0device=full_path_to_the_image.img build.prop setting to override the device mounted as Sdcard0 or sys.config.opt_sd1device for Sdcard1)
26.05.2016 - build #7
Work around wifi autoconnection issue
Fixed video encoding issue by some apps (instagram video upload etc) - thanks to Meticulus for the original patch
Added LockClock back
Added option to show the weather in the status bar
Various small improvements, tweaks etc.
23.05.2016 - build #6
More ROM modules compiled with GCC instead of Clang (GCC supports more optimizations)
Almost ROM modules compiled with Link Time Optimizations
Enabled graphite optimizations for more ROM modules
Added autovectorization optimization on per-modular base
More modules built in ARM mode
Allowed disabling of FC notification
Added time-context custom header images feature
Added customization of the carrier label
Added SystemUI tuner
Added display autorotation setting
19.05.2016 - build #5
updated kernel to r4.4.1
added and enabled by default UMS (USB Mass Storage) mode
re-added some default AOSP optimizations
added navigation bar
added battery level icon customization setting
added long back press to kill app feature
remove 3 secs delay in Superuser before to give the app permissions
added feature of disabling mediascaner at boot
added Sqilte performance improvements
disabled an unnecessary debug
another fixes / improvements
fixed graphical glitches in some apps caused by new UMP lib
resized bootanication (thanks Lemu @ 4pda.ru)
fixed init.d scripts
added aggresive Dynamic governor settings
13.05.2016 - build #4
cleaned up the default google optimizations, removed unnecessary flags
disabled forcible ARM mode optimization - until I revisit this again
added performance settings from OmniROM
added CM Filemanager
added a few more opensource code to libUMP, replacing calls to old library
fxed up an inadeqate CPU time consumption caused by logd process
6.05.2016 - build #3
updated sources to 6.0.1_r30
kernel update to r4.3.1
switched to GCC 5.3 toolchain by UBER
enabled graphite, fast math, loop nest, unsafe loop and some more optimizations
entire build is compiled in ARM mode
switched to opensource RIL libraries (based on CyanogenMod repos)
UMP (Unified Memory Provider) library now is mostly opensource - based upon CM sources
Attempt to fix storage permission issues in some apps such as browser - not tested
fixup for RIL java code - thanks to @SergeyL
disabled scrolling cache
SQLite code optimizations
Reduced various delays
many other fixes and improvements - thanks to SergeyL for patches
20.03.2016 - build #2
fixed APN editor crash
added removed fonts back
removed Gallery, Calendar and PrintSpooler
Viper4Android driver post-install (no need to install manually anymore)
Fixed busybox related issues
20.03.2016 - build #1
initial release
Miscellaneous
reserved
Take some time to try this ROM, and now there are some issues
1.there are lost 4 opentype fonts (compared with Sergeyl's CM13)(JP,KR,SC,TC-Regular),so Simplified Chinese display likes XXX
2.V4A needs to works with busybox, lol...
But ROM works smooth
fim5646 said:
Take some time to try this ROM, and now there are some issues
1.there are lost 4 opentype fonts (compared with Sergeyl's CM13)(JP,KR,SC,TC-Regular),so Simplified Chinese display likes XXX
Click to expand...
Click to collapse
These are removed, because of overly sized ROM. Are these fonts only that support these languages? If so, I'll of course re-add them. I was comparing this ROM to my OmniROM and haven't found these fonts, so I thought they can be safely removed.
2.V4A needs to works with busybox, lol...
Click to expand...
Click to collapse
I guess, it's common 6.0.x problem, as busybox has got partially replaced by toolbox and toybox from AOSP, thus making some apps confused.
ChronoMonochrome said:
These are removed, because of overly sized ROM. Are these fonts only that support these languages? If so, I'll of course re-add them. I was comparing this ROM to my OmniROM and haven't found these fonts, so I thought they can be safely removed.
Click to expand...
Click to collapse
Yeah,these 4 fonts only support Janpanese,Korean,Simplified Chinese and Traditional Chinese,(lastest outdated AOSP 6.0 has same problem...）Maybe OmniROM has different font files
ChronoMonochrome said:
I guess, it's common 6.0.x problem, as busybox has got partially replaced by toolbox and toybox from AOSP, thus making some apps confused.
Click to expand...
Click to collapse
Yeah....
Is there any way to fix sdcard problem?
And thanks for this awesome rom.
Fake2Dead said:
Is there any way to fix sdcard problem?
Click to expand...
Click to collapse
What problem exactly?
What GApps should we install, these modified by SergeyL? open_gapps-arm-6.0-pico-20160204.zip
https://yadi.sk/d/HX0CiHNnoGiC5
Culateralligator said:
What GApps should we install, these modified by SergeyL? open_gapps-arm-6.0-pico-20160204.zip
https://yadi.sk/d/HX0CiHNnoGiC5
Click to expand...
Click to collapse
GApps aren't personally tested by me, but I guess, you'll need those provided by SergeyL else keyboard will crash.
ChronoMonochrome said:
What problem exactly?
Click to expand...
Click to collapse
phone says sandisk sd card is corrupted. I tried to format from phone but it didn't work. Also i can't use my camera without external sdcard. And why extsdcard is sdcard0
"Sorry for my english if a have a fault"
Fake2Dead said:
phone says sandisk sd card is corrupted. I tried to format from phone but it didn't work. Also i can't use my camera without external sdcard. And why extsdcard is sdcard0
"Sorry for my english if a have a fault"
Click to expand...
Click to collapse
Did you format your sdcard as adoptable(internal) storage? This is something you actually shouldn't do and it's explicitly mentioned in the issues list as it doesn't work properly on our devices. SDcard should normally work without formatting (in case of M - which also performs encrypting of it), thanks to @SergeyL work. Now you have to format sdcard from Windows / *nix / whatever other OS; if even this won't help, we'll probably need a volunteer to test it. Personally for me sdcard works, but you may want to try SergeyL's CM13 to see if it's working there.
WiFi is unstable, lost connection from time to time, Web Browser is crashing. And any of gapps do not work - do not fit in system. Yes, i readed first post, i have orginally partitioned internal card and do not want touch it. SergeyL's CM13 work with smallest gapps
ChronoMonochrome said:
Did you format your sdcard as adoptable(internal) storage? This is something you actually shouldn't do and it's explicitly mentioned in the issues list as it doesn't work properly on our devices. SDcard should normally work without formatting (in case of M - which also performs encrypting of it), thanks to @SergeyL work. Now you have to format sdcard from Windows / *nix / whatever other OS; if even this won't help, we'll probably need a volunteer to test it. Personally for me sdcard works, but you may want to try SergeyL's CM13 to see if it's working there.
Click to expand...
Click to collapse
Thank you so much for help. I tried to format from windows(exfat) and it worked!
Edit: Don't try to format sdcard as fat32 it didn't worked on me
Pastorious said:
WiFi is unstable, lost connection from time to time, Web Browser is crashing. And any of gapps do not work - do not fit in system. Yes, i readed first post, i have orginally partitioned internal card and do not want touch it. SergeyL's CM13 work with smallest gapps
Click to expand...
Click to collapse
I can confirm Web Browser is unstable.
I haven't those WiFi problems yet, but I'm testing for little time.
What do you mean with smallest GApps?
I've tried no repartition + SergeyL GApps and I get ERROR CODE 70 -not enough system space-.
Culateralligator said:
I
What do you mean with smallest GApps?
Click to expand...
Click to collapse
I found somewhere gapps ~45MB, still too big for install, i have no idea how install Play shop
New build is 20.03.2016(#2) UP!
Changelog
fixed APN editor crash
added removed fonts back
removed Gallery, Calendar and PrintSpooler to free up some space
Viper4Android driver post-install (no need to install manually anymore)
Fixed busybox related issues
Might fix GApps not being fitted on /system issue in the future, but I'll need a volunteer to test the new partition scheme. If anyone knows how to modify CWM repartition scheme zip and create a new one with ~700-750Mb on /system, it would be even much great, because right now I have absolutely no time for this.
Enjoy!
Something weird... I've connected phone to PC 5-6 times.
Last 2 times appears sdcard1 with 1,09GB (real internal sd).
However, I have access to files of real external sd. But when I try to paste a file, it says I have no space for it.
Succesfully installed gapps removed printspooler webbrowser gallery calendar clock and 1 more thing and i found 48 mb gapps
Culateralligator said:
Something weird... I've connected phone to PC 5-6 times.
Last 2 times appears sdcard1 with 1,09GB (real internal sd).
However, I have access to files of real external sd. But when I try to paste a file, it says I have no space for it.
Click to expand...
Click to collapse
Indeed, it seems that I have misapplied one fix to the vold binary. Does this issue also appear on CM13?
P.s. it's possible that vold from CM13 will also work, because UltimateROM use same sources as CM. Can anyone try replacing /system/bin/vold and check if it helps?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available on github : LineageOS Github repo.
Unofficial build of LineageOS 14.1 (Android 7.1.2) for the M2 Note
Code:
#include
/*
* 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!
*/
Working features:
Hardware acceleration
RIL for SMS/Calls/Internet
GPS
WiFi
Vibration
Audio
Bluetooth / A2DP
MTP and Mass Storage mode
External SD
Camera (Videos & Photos)
Gestures
Gamepads support
All Sensors
Tethering
USB Otg
mBack button!
LiveDisplay (natively)
Power-On Alarms (wakes the device 1m30 before an alarm)
Sdcardfs (default)
Ext4 backported from 3.18 with crypto and lazytime
F2FS latest stable with lazytime
Zram (w/ LZ4 comp.)
Offline-Charging Mode
Signed build (user/release-keys)
Selinux enforcing :fingers-crossed:
Security Patch September 2019
Thanks to Prasenjit Roy for the quick-review video :highfive:
https://www.youtube.com/watch?v=Uy1sVlSeYks
Download:
Build 25 (Stable 9 "PrettyLate") : HERE (Gdrive link)
md5: fadd90ec9ec6dded055231386c7186e2
[lineage] sources updated as of today, includes September 2019 security bulletin
[device] fixed orientation sensor (still works after a week without reboots)
[kernel] upstream updates, small fixes and CVEs
Build 24 (Stable 8 "Late") : Here(temp. Gdrive link)
[lineage] sources updated as of today, includes November 2018 security bulletin
[device] fixed hardware HEVC encoding/decoding, should make some audio/video apps more stable
[kernel] upstream updates, small fixes and CVEs from November '18 for the wifi driver included.
Build 23 (Stable 7 "Spring") :
[lineage] sources updated as of today, includes May 2018 security bulletin
[device] enabling the virtual navbar will now disable the hardware button (for those with a broken buttons <3 )
[kernel] upstream updates, fixed exfat kernel drivers
Build 22 (Stable 6 "M'lady") :
[lineage] sources updated as of today, includes January 2018 security bulletin
[device] lights HAL built from source, leds settings cleaned (battery notification was not on stock rom, the settings were unused), mtk omx settings were fine-tuned (should reduce the lag when playing HQ videos), broken ffmpeg VIDEO (and aac) codecs were removed to keep things tidy.
[storage] encryption AND "formatting an sdcard as internal storage" should now properly work (updated kernel and TWRP)
[kernel] upstream updates, fully upstreamed encryption, ext4, dm, md and sdcardfs drivers, fixed encryption and sd as internal storage for ext4 & f2fs, a few tweaks/cleanup. NFS was reverted from the kernel, CIFS is now built, I'm not sure if I want to build both as NFS might not be used if by any of us, if anyone wants kernel support for NFS, voice yourself.
[blobs] removed a couple unused blobs, updated md_init / nvram_daemon to prevent crashes during modem start/stop/restart and during encryption process.
[doze] doze package was fixed by Dinolek ( hand-wave to wake and co, features) and now works properly
[shim] updated shim for graphic buffers by Dinolek, mtk_agps is now shim-free and was updated to a Nougat blob.
How to report Issues
If you find a bug please check if an exisiting issue is already mentioned and create one with details and logs here : Bug reports @ Github issues
Make sure you fit those criteria first :
Make a backup, do a "Wipe Clean" install
Make sure you don't use MODifications (flash clean, try again)
Check the open/closed issues (most of the problems faced should have a mention about how it was fixed or how to workaround rare bugs)
Check google first, there might already be solutions, there's also "howto" (for making logs, using a different i/o scheduler, etc.. )
Explain and give details, add logs as much as possible (and please take the time to search how to do those tasks, I know most of you are well intentioned when asking "how can I make logs", but you're not helping only me, you're helping yourself and everyone else who might/has the same issue :good: )
Issues
First boot and bluetooth :
NOTE: for those having issues with bluetooth not enabling, you need to actually copy/paste the file :
"/data/nvram/APCFG/APRDEB/BT_Addr" to "/data/", it should look like "/data/BT_Addr".
For some reasons (I couldn't find the definitive solution so far), it seems nvram can't access the "BT_Addr" in nvram and falls back to reading it from /data/BT_Addr (which is just a copy of BT_Addr). Using enforcing makes the nvram_daemon unallowed to create files in /data, which is why you need to copy it yourself. If anyone wants to make a small flashable fix.zip, I'll link it here
First boot and camera :
You can flash from TWRP this little fix : CameraFix-Dinolek-Los14.1.zip (Download section)
Proximity Sensor :
If your proximity sensor doesn't work and/or you have a black screen after hanging a call, you can find a flashable zip named "Mtk-prox.sensor.FIX.v2.zip" under the download section.
Flash this zip will install the small proximity calibration helper written by xen0n (here - thanks to him )
[*] V2: should be automatic on boot/reboot, if not see the note for V1.
[*] V1: Usage is simple, if you need to calibrate your proximity sensor, just open terminal app (you can enable Terminal app in Settings>DevOptions), start the terminal and type :
"meizupshelper c" ( c as in Calibration)
Voilà !
How to install Recovery / TWRP :
Use the recovery linked in the download section of this thread
-> How to install TWRP <- I don't support unlocking bootloader AND installing TWRP, check the corresponding threads :highfive:
How to install G-apps :
LineageOS now recommends these G-apps package : click here, I installed the corresponding package to our rom : "Nougat Base Gapps package for 7.1.2 (arm64)", seems fine so far
Open-Gapps should work too, refer to lineageOS wiki for more infos.
Don't be cruel:
If you want to mirror the rom or port it to another device, go ahead! Just do the right things and give proper credits. Thank you!
XDA:DevDB Information
[Stable] LineageOS-14.1 for Meizu M2 Note [7.1.2], ROM for the Meizu M2 Note
Contributors
Moyster, Fire855
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-09-12
Created 2017-10-21
Last Updated 2019-09-15
Old changelog :
Build 21 (Stable 5 "Santa2note") changelog :
[lineage] sources updated as of today
[device] audio HALs updated to properly support the new bluetooth drivers, and xml audio policies
[rootdir] our octo-core m2note has now properly defined cpusets, as well as a bunch of tweaks/optimisations for smoothness / reactivity and fast app-opening.
[blobs] device specific blobs were all moved to /vendor instead of /system, which allowed to update a few more binaries (like thermal_manager) and figure that ClearMotion is broken and now disabled.
[kernel] see the changelog on github, there's been a lot since last changelog ion/binder/smi/fliper and a lot of drivers were updated, a lot of CVEs were patched, arm optimized crypto algos are now used (for SHA*/chacha20/etc..), NFS is enabled and supported, exfat/f2fs/sdcardfs were updated, some small battery-performance optimizations were merged (shouldn't be that big but still).
Build 19 (Stable 3 "FracturedWaduhek") :
[krack] wpa_supplicant fix in lineage source and kernel fixes
[device] updated MeizuDoze and CMActions (gesture implementation)
[sepolicy] cleanup and fix a few more denials
[security] hardened kernel config, extra entropy gather during boot,
[kernel] upstream f2fs updates, zram/zsmalloc drivers from 4.1 kernel
[misc] cleaned unused services/props
Build 18 (Stable 2 "Ruhr") changelog :
[backport] kernel backported uid_sys_stats, binder from 4.9
[camera] might not be new, but HDR is back since a few releases
[charger] switched to AOSP/Lineage charger (using healthd) / remove mediatek charger (kpoc_charger)
[config] added gps.conf to remove a few warnings, newer SPNs (from MAD and leskal)
[device] cleaned unused props and settings
[drivers] kernel libvsprintf, vmstat, fiq_debugger, f2fs, sdcardfs, ion, maxx77819(charger driver), fsync, LowMemoryKiller driver cleanup, fix and updates; removed mlog drivers, less debug/xlog/aee/custom code from mediatek, removed logspam from most mediatek drivers
[flaw] BlueBorne fixed (android & kernel)
[fs] ntfs & exfat kernel native drivers
[gamepad] xbox360-one / usb gamepad support (using an OTG cable, you can navigate / open apps, play games, etc..)
[gapps] fixed TrustedFace (unlock with your front camera should work now, thanks to MAD team)
[gps] GPS drivers from N, GPS binaries from N, properly reworked AGPS shim
[kernel] kernel upstream fixes and CVEs corrections, bug squashing and improvements (a problematic/spammy backtrace finally was fixed in task_mmu, meizu battery logs were removed, check and delete this file : /data/fuelgauge_datalog.txt to gain some free space in /data), code sanity updates (moving to __FUNCTION__ > __func__, no more seq_printf (increases overall security))
[misc] blob removed unused libs (libjtranscode), removed kpoc_charger, libshowlogo
[os] Android Security Bulletin to September 2017
[permission] added SIP permissions (should enable SIP if available)
[power] powerHAL made compatible for passthrough HIDL design
[ril] readded REFRESH_SESSION_RESET
[sepolicy] cleanup unused rules (mdlog, fuelgauge_data_file), fixed a few denials
[shim] libshim cleaned, removed libshim_asc and the AndroidSurfaceControl symbols
[rootdir] clean, rebased init files, added path for e/frandom to uevent
[vendor] Mediatek security fixes up to September 2017, kernel various mediatek bugfixes and memleaks fixed (backported to 3.10 from Mediatek 3.18 maintained kernel)
Build 17 (Stable 1.1 "Arewederyet") changelog :
[android] Security Bulletin from "5 August 2017"
[kernel] cmdq, gud, smi, ext4 drivers update & a bunch of CVEs
[lineage] rebased to latest sources up to 12/08/17
Build 16 (Stable 1 "XmasisSoon") changelog :
[kernel] updated 3.10.106 -> 3.10.107 & additional CVEs
[lineage] Security Bulletin from "5 july 2017"
[misc] smaller tweaks and fixes (sepolicy & doze)
Build 15 (RC 5 "Summertime") changelog :
[kernel] updated 3.10.105 -> 3.10.106
[lineage] Security Bulletin from "5 june 2017"
[device] smaller tweaks and fixes (sepolicy & initramfs)
[hotspot] Works natively (without editing build.prop )
Build 14 (RC 4 "Proxima") changelog :
[camera] fixed a couple bugs, exposure, white-balance, brightness/contrast settings should work properly, better picture quality (still missing HDR, for reasons)
[video-recorder] fix a bug where recording with the flash on crashed, video recording is not extra dark anymore
[netd] properly supporting firewalls / iptables rules / per app restrictions :highfive:
[kernel] netfilter rules cleaned, less latency, now using "cubic" as tcp congestion algorithm (faster internet)
[kernel²] includes every modifications/fixes done during the "kernel tests release" (memory management fixed, ext4&f2fs security&performance update, optimised FS mount flags (incl. lazytime))
[lineage] rebased sources as of today "5 june 2017" ~3pm
[misc] small cleanups/improvements
Build 13 (RC 3 "Datupdat") changelog :
[bluetooth] config update
[kernel] new drivers (uid_sys_stat, mlog, some mtk drivers fixes), f2fs updates, net updates, now using MEMCG instead of kernel LMK, more CVEs fixed, reworked config, and various small tweaks/updates.
[lineage] latest sources from los, note: they moved from Gello to Jelly (a lighter/easier to maintain browser)
[misc] small fixes for sepolicy / device tree (f2fs fstab support)
[sdcardfs] moar fixes!
Build 12 (RC 2 "ICanHazSpeed") changelog :
[omx] omx blobs and some camera-related blobs were updated, should work a bit better and give a better picture quality
[bluetooth] now using N omx blobs
[kernel] security updates, performance tweaks, net/wifi should connect faster.
[scheduler] changed from "deadline" to "bfq" as default
[performance] io scheduler and readahead values tweaked for boot / boot complete (faster boot, better UI fluidity)
[sdcardfs] moar fixes!
[security] A whole new Sepolicy to finally get rid of the small little bugs (touch unresponsive, etc...)
Build 11 (RC 1 "Anougat") changelog :
[release] Builds have reached the "Release Candidate" state, any feedback for broken features (things working before this build) is welcomed !
[gps] mtk agpsd crash fixed (should stop some battery drain/bug)
[kernel] security updates, stability updates, cleanup
[power] fixed "energy saver mode", device won't crash by enabling then disabling it
[sdcardfs] fixed mismerge, downloading files larger than 40mb works
[security] Selinux policy fixed, Selinux is now using "enforcing" mode :highfive:
Build 10 (Beta 10 "AnewFone") changelog :
[alarm] Power Off Alarms fixed (phone turned off will wake 1 minute and a half before any alarm defined )
[android] lineage rebased to 7.1.2_r2 :highfive:
[blobs] latest modems and blobs from Flyme6
[camera] for real this time, no more "camera fix" to flash :fingers-crossed:
[gapps] LineageOS now recommends these G-apps package : click here, I installed the corresponding package to our rom : "Nougat Base Gapps package for 7.1.2 (arm64)", seems fine so far
[kernel] a lot of updates / cleanup / fixes (including most of the recent security fixes)
[overlays] various fixes/cleanup
[PinnerService] pinned correctly some frameworks, should improve a bit performance
[sdcardfs] enabled by default, better performance for both internal storage and sdcards (should also fix permissions errors during copy)
[selinux] some sepolicy denials fix / cleanup
[shim] now using force_shim_lib instead of removing cap_sys_nice on surfaceflinger
[*][f2fs] experimental: the rom should support f2fs, untested feature, take caution (not enabled by default, requires formating partitions to f2fs in twrp, I don't know if the twrp we use supports it correctly)
see here : https://github.com/Moyster/nougat_device_meizu_m2note/blob/los-14.1/rootdir/fstab.mt6735
f2fs allowed on /userdata and /cache partitions, improvements unknown
Build 9 (Beta 9 "Joke'sOnYou") changelog :
[camera] no more patch required, proper release
[video-recording] fixed a bug who crashed the camera if recording a video longer than 24sec
Build 8 (Beta 8 "StillNoJoke") changelog :
same as build 7
[omx] N omx blobs, fixes a lot of issues regarding A/V (Snapchat works )
[camera] no more legacy hal flag, more secure :highfive:
[wifi] hidden wifi should work
Build 7 (Beta 7 "IsNoJoke") changelog :
[kernel] global updates, performance, security (CVEs), sdcardFS/F2FS fixes, backported driver from 3.18 (Wifi / Gps / Bluetooth)
[proximity-sensor] should be fixed, uploaded a v2 that should apply on reboot automatically (added sepolicy, thanks to divis1969 & KevinMX for testing/fixing this)
[rom] lineage update
Build 6 (Beta 6 "BreathOfTheWild") changelog :
[android] LineageOS rebase to 7.1.1_r25 (March Security Bulletin)
[kernel] CVEs from March 2017 Sec Bulletin, more sdcardFS fixes
[hotspot] reverted to working state
Build 5 (Beta 5 "Damerge") changelog :
[android] LineageOS rebase to 7.1.1_r21 (05/02/17 security patch)
[sdcard] kernel/rom now supports "sdcardFS" but not used by default
[kernel] more security updates (more CVEs from february 2017 patch), kernel updated to 3.10.105
[misc] updates / cleanup / various little things
Build 4 (Beta 4 "Ixemo") changelog :
[netd] Data Counting fixed
[kernel] security updates (some CVEs from february 2017 patch)
[device] blobs update with native Nougat blobs
[shim] sensors are now shimmed (less patches on android sources)
[OMX] Cleanup (should fix a few crashes)
Build 3 (Beta 3 "Kameha") changelog :
[camera] touch to focus is fixed
[recording] 720p profile should be working properly now
[device] blobs cleanup / some camera blobs were updated from Flyme 6.7.1.17
[shim] audio is now shimmed (less patches on android sources)
[OMX] FLAC is now working
Build 2 (Beta 2 "Ohemix") changelog :
[perf] performance and battery should feel noticeably better
[kernel] some drivers were updated
[device] services / blobs cleanup, more free ram
[shim] libmtk_symbols was turned into a shim lib, symbols trimmed to only what's needed.
[OMX] fully working, no more legacy support, no additional package to flash, stability improvements (no more mp3 crashes)
[OCM] Offline charging mode fully working, it displays the battery charge and puts the screen to sleep after timeout
[bonus] Google Assistant trick ( ro.opa.eligible_product=true) added for easier G-assistant activation
Build 1 (Beta 1 "GOFALCONS") changelog :
Initial release
Bring-up basic functionalities
First !
Thanks a lot Moyster !
this is great! ??
Download:
Build 19 (Stable 3 "FracturedWaduhek") : Here
[krack] wpa_supplicant fix in lineage source and kernel fixes
[device] updated MeizuDoze and CMActions (gesture implementation)
[sepolicy] cleanup and fix a few more denials
[security] hardened kernel config, extra entropy gather during boot,
[kernel] upstream f2fs updates, zram/zsmalloc drivers from 4.1 kernel
[misc] cleaned unused services/props
Enjoy
wow.. thanks for the update ..
Everything is going well the last update feels faster than build 18 ? thanks
thank you very much
Stable ? and fast.. Everything great.. Anyway the proximity fix doesn't work..
camera fix
what about camera , he work in new beta 19, with the new zip flash file?
Hi, thanks for the update, but I can't root it flashing the v2.79 SuperSu zip. I've also tried with v2.82 but with the same result. How can I root it?
Edit: ok flashed Magisk and no problems. Everything is working fine.
Thanks a lot for the update @Moyster,please update the twrp recovery so that it will work for all users,for me it doesnt work, it cant clean up cache or system and i end up with broken partition.
Alucard said:
Thanks a lot for the update @Moyster,please update the twrp recovery so that it will work for all users,for me it doesnt work, it cant clean up cache or system and i end up with broken partition.
Click to expand...
Click to collapse
i use the twrp 3.1.1 ，when you wipe cacher and system,you should to waite about ten minites,it will be work[COLOR="Silver"[COLOR="Silver"]
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
[/COLOR]thanks to update.
i find the charging animation is reversed when shutting down the phone to charge
what a good job we thank you for all your great monster effort
My first go at installing a custom ROM. Took a backup. Crossing fingers. Thanks for this!
zty915 said:
i use the twrp 3.1.1 ，when you wipe cacher and system,you should to waite about ten minites,it will be work[COLOR="Silver"[COLOR="Silver"]
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
[/COLOR]thanks to update.
i find the charging animation is reversed when shutting down the phone to charge
Click to expand...
Click to collapse
Oh i didnt wait that long,but with older twrp recoveries there is no such issue,i think its a lot of time to wipe partitions and must be fixed but thats up to the developer ,im just hopig he will see my request.
Alucard said:
Oh i didnt wait that long,but with older twrp recoveries there is no such issue,i think its a lot of time to wipe partitions and must be fixed but thats up to the developer ,im just hopig he will see my request.
Click to expand...
Click to collapse
Go to settings in twrp and check the "use rm instead of formatting" it will format instantly
My flash failed
Trying to flash lineage-14.1-20171021-UNOFFICIAL-m2note.zip' onto my phone for the first time (had Flyme this morning).
Code:
I:operation_start: 'Flashing'
Installing zip file '/extSdCard/lineage-14.1-20171021-UNOFFICIAL-m2note.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
I:Zip does not contain SELinux file_contexts file in its root.
I:Legacy property environment initialized.
Target: Meizu/lineage_m2note/m2note:7.1.2/NJH47F/1a8158dae2:user/release-keys
Target: Meizu/lineage_m2note/m2note:7.1.2/NJH47F/1a8158dae2:user/release-keys
could not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system, assuming ext4
could not detect filesystem for /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system at /system: No such file or directory
mount: failed to mount /dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system at /system: No such file or directory
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
unmount of /system failed; no such volume
unmount of /system failed; no such volume
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
Patching system image unconditionally...
performing update
Patching system image unconditionally...
open "/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system" failed: No such file or directory
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.
E:unknown command [log]
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
Error installing zip file '/extSdCard/lineage-14.1-20171021-UNOFFICIAL-m2note.zip'
Updating partition details...
I:Data backup size is 0MB, free: 8661MB.
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
...done
I:Set page: 'flash_done'
Any ideas?
EDIT: Seems to be the same problem as https://forum.xda-developers.com/showpost.php?p=74046296&postcount=1308, so I applied the same solution. Seems to have worked... still waiting for first time boot...
numpea said:
Go to settings in twrp and check the "use rm instead of formatting" it will format instantly
Click to expand...
Click to collapse
Thanks i ll try,what does this option do,is it another way of formatting?
eduardo579 said:
Hi, thanks for the update, but I can't root it flashing the v2.79 SuperSu zip. I've also tried with v2.82 but with the same result. How can I root it?
Edit: ok flashed Magisk and no problems. Everything is working fine.
Click to expand...
Click to collapse
I had the same problem > thanks for the Magisk tip > now i'm rooted
All works fine!
LineageOS 20.0 64-bit for Samsung Galaxy Tab A 10.5 (2018) WiFi
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.
Click to expand...
Click to collapse
By using this ROM, you acknowledge that you understand what running work-in-progress software means. You might lose all your data stored on the device due to a bug, the device might freeze / crash at any time, nothing is guaranteed; you are basically a beta tester. Also, this is my personal project which I decided to share here, I'm not a developer but an average user like you. Most likely I can't and will not solve your issues with VoLTE not working, Angry Birds crashing, etc.
Installation:
-----
Notes for SM-T595 users
The ROM has been modified to work on the LTE variant too, with the same level of functionality as the WiFi-only variant. This means that the LTE modem will not be usable in this ROM, and the device will appear as SM-T590 everywhere.
Also, SM-T595 has lots of hardware versions with different partition sizes, so there is a possibility that the installer will fail with one of the following error messages: E1001: Failed to update system image / E2001: Failed to update vendor image.
In case it fails, I will need the output of the following commands to make the installer compatible with that specific version too:
adb shell blockdev --getsize64 /dev/block/by-name/system
adb shell blockdev --getsize64 /dev/block/by-name/vendor
-----
- Reboot the tablet in download mode
- Flash TWRP in the AP slot using Odin
- Right after Odin finished flashing, hold Volume Up while the tablet is rebooting to get into TWRP
- Skip the warning by swiping to allow modifications
- Wipe -> Format Data -> type yes and confirm
- Reboot -> Recovery
- Skip the warning again
- On your PC, open a command prompt and copy LineageOS to the device using adb push lineage-20.0-20230514-UNOFFICIAL-gta2xlwifi.zip /sdcard/
- Alternatively, you can use a Micro SD card or USB OTG, MTP isn't recommended- In TWRP, select Install -> lineage-20.0-20230514-UNOFFICIAL-gta2xlwifi.zip and swipe to confirm
- Optionally, you can install Magisk now, make sure to use the latest version from GitHub
- Optionally, you can install GApps now but Aurora Store with MicroG is a better alternative, they use way less RAM than Play Services
Downloads:
LineageOS 20.0:
https://github.com/UDPSendToFailed/OTA/releases
TWRP 3.7.0:
https://github.com/UDPSendToFailed/twrp_device_samsung_gta2xlwifi/releases
Changelog:
2023. 05. 14.
Edit: Not recommended to download. This build has issues with WiFi after reboot because of the in-kernel WLAN driver change which I did as an attempt to fix the randomly occurring kernel panics. As it turned out, the WLAN kernel driver has nothing to do with the random reboots, so I will revert to the previous configuration in the next build.
- Switched to in-kernel WLAN driver
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-04-17+before:2023-05-14)
- May security patch
Spoiler: More changelogs...
2023. 04. 17.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-04-05+before:2023-04-17)
- April security patch
2023. 04. 05.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-02-27+before:2023-04-05)
- Switched to LineageOS-UL for frameworks_av and frameworks_base
- March security patch
2023. 02. 27.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2023-01-24+before:2023-02-27)
- February security patch
2023. 01. 24.
- Synced with the latest LineageOS sources (https://review.lineageos.org/q/branch:lineage-20.0+status:merged+after:2022-12-28+before:2023-01-24)
- January security patch
2022. 12. 29.
- Synced with the latest LineageOS sources
- December security patch
2022. 11. 15.
- Synced with the latest LineageOS sources
- November security patch
2022. 10. 05.
-----
!TWRP update and data wipe is required to enable FBE!
Steps to update from previous versions:
- Download TWRP 3.7.0
- Update TWRP using Odin
- Boot into TWRP -> Wipe -> Format Data -> type yes and confirm
- Reboot -> Recovery
- Flash the latest ROM zip (20221005)
-----
- Enabled FBE (File-Based Encryption)
- Fixed some Bluetooth-related issues
- New camera app with video recording support
- Synced with the latest LineageOS sources, most of the features from 19.1 have been merged
- October security patch
- TWRP: Updated to the latest 12.1 branch
- TWRP: FBE decryption support
2022. 09. 30.
-----
LineageOS 19.1 (Android 12L) builds are now discontinued as it would be complicated to keep testing an older version, and I don't have a build server to store and update the source code either. Personal builds can still be done by anyone who wants to keep using 19.1, all the required sources are available on my GitHub.
-----
- Added Signature Spoofing support, LSPosed and FakeGApps aren't required anymore for MicroG
- Added Natural and Boosted display color profiles
- Extended Night Light color temperature range
- UI and color flickering has been fixed
- The Restrict USB option under Settings -> Privacy -> Trust is now working properly
2022. 09. 16.
- Significantly improved multitasking performance with proper ZRAM setup
(Random reboots might still happen, please report them with a description of what caused the crash and /proc/last_kmsg & logcat output attached)
- Added KTweak script (more info here and here)
- Added Dolby Settings
- Added Memory Usage stats to App Info in Settings
- Added audioloader
(Experimental quad speaker mode, can be enabled with running audioloader in Terminal Emulator or adb shell. To revert the temporarily set parameter, restart the tablet. Ideas on how to fix the sound quality are welcome)
- Fixed Network Speed indicator and Data Usage stats
- Disabled ALAC codec support as it had a critical CVE vulnerability
- Reverted to SkiaGL renderer as SkiaVK had issues with WebView v104+
- Removed some LTE-only features
- September security patch
2022. 08. 14.
- Added System Navigation options under Settings -> System -> Gestures
- Added theme color customization under Settings -> Wallpaper & Style
- Merged changes from various msm8953-based device trees
- August security patch
2022. 07. 12.
- Added CRT screen off animation
- Added tinymix (in case anyone wants to experiment with fixing the quad speakers)
- Added hidden and protected apps feature to the launcher
- Added pure black theme option
- Light theme changes
- Removed Audible app (Samsung bloatware from the odm partition)
- July security patch
2022. 06. 12.
- Headphone jack fixed
- Microphones fixed
- Double Tap to Wake should work reliably now
- Switched to Vulkan renderer to improve the smoothness of the UI
- June security patch
2022. 05. 29.
- MTP fixed
- Widevine DRM fixed
- Removed the "internal problem" warning on boot
- TWRP updated to 3.6.2
2022. 05. 25.
After a long time without updates, a new, non-GSI version is here!
- Freezes and crashes have been eliminated
- Keystore is fixed so you can use a screen lock
- This update will give your device an extra 106MB of RAM (by freeing up the memory that was allocated for the non-existent modem)
- MSM hotplug is enabled by default to improve the battery life by dynamically powering down cores based on CPU load
- May security patch
2022. 04. 08.
- Device type changed to tablet
- April security patch
Known issues:
- WiFi hotspot crashes
- Bluetooth audio
- 2 of 4 speakers are working
- GPS
- Freezes / crashes with some SD cards, in case the ROM installation fails with black screen or the setup process keeps freezing, try removing the SD card
- SELinux permissive
32-bit vs 64-bit mode performance comparison:
https://browser.geekbench.com/v5/cpu/compare/15116230?baseline=14600296
Thanks to:
lsswizard for the 64-bit kernel, this all wouldn't be possible without his work
lsswizard for the TWRP tree
@quent1du58 for the commits to the device tree
LineageOS team for the base ROM
LineageOS-UL team for keeping the camera HALv1 patches alive
Sources:
Kernel: 3.18.140
64-bit vendor libraries from Galaxy A20s firmware (A207FXXU2BUD4)
https://github.com/UDPSendToFailed/
https://github.com/LineageOS
https://github.com/LineageOS-UL
https://github.com/TeamWin/android_bootable_recovery
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
aIecxs said:
looking forward to see flashable zip for deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw
Click to expand...
Click to collapse
They are already removed from the provided vendor.img but sadly that didn't fix the problem, I will look for a solution.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Many thanks for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.
I've found only three problems so far:
The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.
Only half of the speakers are working (but still not a deal breaker).
My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
quent1du58 said:
Many thanks for all your work. My SM-T590 is running on it for almost a day now (with MicroG and Magisk). Installation was not straightforward (I've had to factory reset after flashing LineageOS since the setup process kept freezing), but definitely easier than with the other GSI images. Not really sure if it is also related to the 32 vs 64 bits kernel, but the tablet definitely feels snappier than with BloatUI OneUI.
I've found only three problems so far:
The tablet does indeed randomly freeze from time to time. It does seems related to Magisk, but definitely not a huge deal since it rarely happens. I'll try to pinpoint the problem with a logcat if I have some time.
Only half of the speakers are working (but still not a deal breaker).
My book cover does not wakes up or put the tablet into sleep. It seems that one of the sensors is not working properly.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm working on a non-GSI variant since I couldn't fix the keystore errors and other issues on GSI.
However I have no previous experience on Android builds, and our device has no custom ROMs or device trees to begin with, so it might take a long time to fix everything. Also the 3.18 kernel is really old for Android 12.
Currently basic functionality like WiFi, Bluetooth, OpenGL, sensors, and lock screen are working, but there is still a lot more left like DRM, cameras, audio, GPS, etc.
As for your 3rd issue, I would suggest enabling double tap to wake in Phh Treble Settings.
That's some great news. I've also tried to port LineageOS to this device (mostly as a way to learn new things, since Android/LineageOS/kernel aren't really my areas of expertise) using both Rupansh and heavily customised Xiaomi Redmi 5 (Rosy) sources trees without any success.
Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree. Build went fine, I've even managed to flash and to boot into recovery (which needs fstab fixes), but no way to boot a freshly flashed zip for now. I'm going to continue my research and will share any progress.
quent1du58 said:
Have you managed to boot a non GSI build? I've tried to compile LineageOS 19 Using your device and kernel trees, plus Rupansh vendor tree.
Click to expand...
Click to collapse
Yes, currently my tablet runs a build based on my device tree on GitHub but it's highly experimental. Basically I use GitHub only to have some revisions of the device tree for backup and testing purposes, that's why all the commits are named asd.
I guess your issue will be that you use vendor files from Rupansh (since that's missing 64-bit stuff from Galaxy A20s vendor), here I have uploaded the ones I'm using: https://mega.nz/folder/zXZzVZaL#95t8V7DSr0rX7W0lTZmhHQ
Copy them to a folder named ~/system_dump for example, create a subfolder named system and another subfolder named vendor under the previously created system folder. Then you can use the commands below to extract the required proprietary files from system.img and vendor.img. Assuming you have everything in ~/system_dump folder:
sudo mount -o loop,rw system.img system
sudo mount -o loop,rw vendor.img system/vendor
Then go to your downloaded LineageOS source/devices/samsung/gta2xlwifi and run:
chmod +x extract-files.sh
chmod +x setup-makefiles.sh
bash extract-files.sh ~/system_dump/
Also you will need to apply some patches to the LineageOS 19.1 source to bypass eBPF requirement which is not available on our 3.18 kernel. Download Treble patches from here: https://github.com/phhusson/treble_...ases/download/v413/patches-for-developers.zip
Apply patches/platform_system_bpf/0001-Support-no-bpf-usecase.patch to system/bpf and patches/platform_system_netd/0001-Support-no-bpf-usecase.patch to system/netd in the source using git apply /path/to/.patch. You can also apply the Camera2 API patches mentioned in the first post but the camera doesn't work anyway currently.
The resulting build is barely usable, working stuff are mentioned in my previous comment. Feel free to try different versions in device.mk and add / remove stuff in proprietary-files.txt, I guess I messed up lots of things since I never built a device tree before.
Thank you for all those details, I've managed to build a working image. I still experience the same problems so far:
UI crashes a lot shortly after rebooting
Inserting a SD card freezes the system
But since I now have a way to build my own releases, I'll try to fix things. Since I've forked your repositories on Github, I'll send you pull requests when needed.
Glad you managed to get it work!
Yep, the UI hangs and crashes are happening here too, haven't found the cause yet. Logcat shows a blocked state and dumps tons of lines from the kernel. The interesting part is that sometimes, like in 2 of 10 reboots it starts up correctly without any freezes.
If I have some time I will continue fixing the tree as there are lots of randomly added and unfinished stuff which I did for testing purposes.
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
seeiu said:
I tried to flash twrp in the download mode but it showed "only official binaries are allowed to be flashed". What's wrong?
Click to expand...
Click to collapse
You need to flash TWRP using a patched version of odin.
Thanks for the great tutorial. The Rom runs so far quite well.
But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.
When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.
Although, the tab is recognized by the PC.
Is there a trick or do I have to live with it.
DerSammler said:
But when I want to flash microG_Installer_Revived with TWRP I get a 235 error.
Click to expand...
Click to collapse
I just updated the first post with some instructions about MicroG. Basically you will have to flash it as a Magisk module, also use FakeGApps to have Signature Spoofing support.
DerSammler said:
When I connect the tab to the PC, the internal memory and SD card is not shown to me on the PC.
Click to expand...
Click to collapse
Yea, that's a known issue with both GSI and non-GSI variants, it'll be fixed as I find the cause. Alternatively you can use adb or some wireless file transfer app like AirDroid.
What do I do if I want to go back to stock Rom?
Can I simply flash with Odin original Android 10? Or is there anything else I need to consider.
Thank you very much.
DerSammler said:
Can I simply flash with Odin original Android 10?
Click to expand...
Click to collapse
Exactly, it's enough to flash the latest stock ROM with Odin to revert the changes.
I have installed lineage-19.1-20220525-UNOFFICIAL-gta2xlwifi according to the new instructions
unfortunately, when I start the tab, I get a red message—kernel is not seandroid enforcing -.
Afterwards, when the tab is started, I also get the following message on the home screen
Android System
There is an internal problem with your device. Please contact the manufacturer regarding this.
Are these two messages normal? Or am I doing something wrong. I have now installed LOS_19.1_64 again. Thank you very much.
DerSammler said:
Are these two messages normal?
Click to expand...
Click to collapse
Yes, these messages are completely normal in the ROM's current state and can be ignored, they won't cause any further issues.
The kernel message is related to the SELinux permissive state which is listed under known issues, the other one shows up simply because I haven't patched the LineageOS source code to hide it.
Disable AVB check · phhusson/[email protected]
This avoids the message "There's an internal problem with your device. Contact your manufacturer for details." on some AVB 1.0 devices. Change-Id: Ia54b857a3e98e2639d6bcc0ba713809704...
github.com
Thanks a lot for your help.
I find the Rom really great, super work you do. The system is really faster.
To transfer data I have MyPhoneExplorer and that works very well with it.
I'm curious what there will be updates for this Rom.
Wish you a quiet Sunday.
Greetings: Dirk
DerSammler said:
I find the Rom really great, super work you do. The system is really faster.
Click to expand...
Click to collapse
Thanks for the feedback!
DerSammler said:
I'm curious what there will be updates for this Rom.
Click to expand...
Click to collapse
Yea, I'll try to improve things but as I stated in my previous posts, I'm just an average user with no Android porting experience, so it might take a while. I'll post new releases with monthly security updates from Google and maybe some fixes.
Also please note that the ROM isn't secure yet, the lock screen can be easily bypassed with TWRP since encryption isn't enforced, and adb with root access is enabled by default for debugging purposes.
I have a question about the GSI Roms?
Which roms can I flash on the Galaxy Tab A (T-590).
The roms must be Binder compatible, I know that.
Can I only flash Binder a64, or can I also use the Binder arm 64 Rom?
Thank you very much.