Related
SlimLP
[#LOLLI]
[#ESPRESSONAME]
[#WHATSSLIM]
[#WARRANTY]
Download:
[#DLGITHUBIO]
[#INFOSLIM]
Disclaimer: SlimRoms are not responsible for any damages to your device.
[#DONATETOME]
XDA:DevDB Information
[unified] SlimLP, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi, SlimRoms
Source Code: https://github.com/SlimRoms/kernel_samsung_espresso10
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2014-12-10
Last Updated 2017-04-30
Reserved
Screenshots attached
Kudos and thanks to all the special Devs let the tablet have new life. [emoji106] [emoji106] [emoji106]
GT- N7100 with Dr.Ketan Hindocha Rom Android 4.4.2
That's great, nice move thank You @Android-Andi :good:
Great!! Thanks dude!!
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Android-Andi said:
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
Tomorrow morning!
Thank you for making this possible!
All the best for you
Working well for me on my p3110 - brilliant job, well done and many thanks
Sent from my BN NookHD+ using XDA Free mobile app
Android-Andi said:
Initial P3100 build available now Not sure if it works/boots - you will let me know
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
@Android-Andi I will try now your work ... Feedback in an hour. (I hope it boot ☺)
EDIT:
It boot. I'm writing from tab2 P3100 with slimlp 0.8.
First boot take some time and the boot animation is not fluid.
I now try to install SuperSU and restart the system.
After I try adb shell (from terminal?)
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Android-Andi said:
Someone on P3100 please get out some information for me,
you need su permissions (please flash latest SuperSU from Chainfire):
Code:
adb shell su -c dmesg | grep 'avc: '
Also please upload a complete dmesg for me.
Click to expand...
Click to collapse
Should i do this also on P3110?
Android-Andi said:
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Click to expand...
Click to collapse
@Android-Andi, can i use my terminal in my iMac with the same command you give us? in this case, my tab should be in download mode, right?
SlimShady's said:
Should i do this also on P3110?
Click to expand...
Click to collapse
You can test from time from time if you get an output for "avc:", it will show if there are some denial because of selinux. If i get the output i am able to add a policy to fix it. Hope we can switch to enforced soon
Send from OnePlus One using Tapatalk
MARKBOARD NETSET said:
@Android-Andi, can i use my terminal in my iMac with the same command you give us? in this case, my tab should be in download mode, right?
Click to expand...
Click to collapse
No, device need to boot android.
http://m.youtube.com/watch?v=TMcMVDUbpis
Send from OnePlus One using Tapatalk
Android-Andi said:
You can test from time from time if you get an output for "avc:", it will show if there are some denial because of selinux. If i get the output i am able to add a policy to fix it. Hope we can switch to enforced soon
Send from OnePlus One using Tapatalk
Click to expand...
Click to collapse
My brain stopped working at "if you get an" xD
Edit: Oh, okay I got it. Will do this tomorrow
Android-Andi said:
@philidor thanks a lot
adb shell from your PC, need adb binary on your pc.
You can also use Terminal Emulator on your device (but don't type "adb shell").
Edit:
mobile data works?
Click to expand...
Click to collapse
@android-Andy Tanks YOU a lot!! Sorry I can only help you as a tester.
3G not working. (See picture) I can receive SMS but can't send.
Problem with root binaries. SuperSU installed give me some minutes.
After I will try your commands. Have you some tests for me?
Android-Andi said:
@philidor thanks a lot
Edit:
mobile data works?
Click to expand...
Click to collapse
yes:highfive::good:
jak978 said:
yes:highfive::good:
Click to expand...
Click to collapse
No mobile data don't work for me. I can receive SMS and have my normal signal bars
This is your grep command @Android-Andi
[email protected]:/ $ su -c dmesg | grep 'avc: '
[ 4.256500] C0 [ init] avc: granted { set } for property=net.rmnet0.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.256958] C0 [ init] avc: granted { set } for property=net.rmnet0.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.257263] C0 [ init] avc: granted { set } for property=net.rmnet0.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.258392] C0 [ init] avc: granted { set } for property=net.rmnet1.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.258728] C0 [ init] avc: granted { set } for property=net.rmnet1.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.259002] C0 [ init] avc: granted { set } for property=net.rmnet1.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260101] C0 [ init] avc: granted { set } for property=net.rmnet2.dns1 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260437] C0 [ init] avc: granted { set } for property=net.rmnet2.dns2 scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 4.260742] C0 [ init] avc: granted { set } for property=net.rmnet2.gw scontext=u:r:rild:s0 tcontext=ubject_r:net_radio_prop:s0 tclass=property_service
[ 5.750274] C1 [ init] avc: denied { set } for property=supolicy.loaded scontext=u:r:sysinit:s0 tcontext=ubject_r:default_prop:s0 tclass=property_service
[email protected]:/ $
Flashed this as soon when saw that P3100 port also ready. Thanks AndroidAndi! U are really really awesome! Straight change the P3113 version to this version. All working even YouTube able to load video.
What work
- Everything
- Video Player works too. No need 3rd party
Not Working
- 3G Maybe? (haven't tried)
- Recent tab, card stack works perfectly in landscape. When change to portrait, it turns to black color. But, not bothering
Issue fixed, thanks for all the feedback and report!!!
Hello, as many of you should be aware, the latest Magisk Manager (v4.2.5) crashes only on Samsung devices.
Here are the logs users submitted through Play Store:
Code:
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
at com.android.internal.policy.multiwindow.Docking.<init>(Docking.java)
at com.android.internal.policy.MultiPhoneWindow.<init>(MultiPhoneWindow.java)
at android.app.Activity.makeNewWindow(Activity.java)
at android.app.Activity.attach(Activity.java)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java)
at android.app.ActivityThread.access$1100(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java)
at android.os.Handler.dispatchMessage(Handler.java)
at android.os.Looper.loop(Looper.java)
at android.app.ActivityThread.main(ActivityThread.java)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java)
As you might realize that according to the backtrace, non of them involves my code (which should start with com.topjohnwu.magisk.*), all of them are errors within internal and Zygote, and Samsung's multiwindow internal calls.
I am not able to identify where it crashes, and which part of the Magisk Manager code is breaking it, so of course without knowing why, I have no idea how to fix it. What makes the situation even worse is that I don't own any of the devices, so I cannot properly debug the issue.
This thread is for seeking help from users with a modern Samsung device, as I need more details.
Please describe when do the crash occurs (does splash screen even shows up?), and please upload a full logcat recording the FC.
Also, I'm looking for Samsung experts who are willing to assist me more in Samsung support for Magisk, as I never bought Sammy so I have little experience, but they seem to cause the most problems.
OT, I'm actually willing to buy a Sammy flagship, but I never buy outdated devices (older than 2 months = outdated IMO lol), so I might get the S8. The next Pixel device is already on my list, guess I'll have to spend all my tutor money on smartphones....
For Pixel support, I'll borrow my friend's Pixel XL for a couple of weeks to try things out, but this might not happen soon since school is quite busy.
@topjohnwu
it crash on opening the app, so unable to opeen the app it self
new root programs are unable to use root as it will crash when trying to enable root in the apps
old programs that use root already keep function
my device is
Samsng Galaxy s6 edge+ SM-G928F
Rom: Audax 13 Android MM 6.0.1
Kernel: Arter97
i don't know how to provide anymore info or how to use this logcat
so if you tell me how i can gather more info i do it with pleasure
From what I can tell it only happens in the versions after 4.1 so the problem is in one of the changes after 4.1. A Wild guesses that may or may not could help is that you could set a flag that tells the Samsung framework that it isn't compatible with multi window.
Gesendet von meinem SM-G925F mit Tapatalk
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Didgeridoohan said:
Logcats requested... If you don't know how, here's some hand-holding:
https://forum.xda-developers.com/showthread.php?t=1726238
Edit: Clarification... Start logcat, open app, watch it crash, stop logcat, upload file.
Click to expand...
Click to collapse
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Hello topjohnwu, first of all I would like to thank you for you amazing work, really it made life simplier to many of us, so on behalf of everyone using Magisk I would like to say : THANK YOU.
To answer your question, when launching Magisk Manager, yes there's the splash screen before the crash.
I've attached a logcat to my post which shows "Magisk Manager v4.2.5" behaviour when crashing.
1 - Here are some informations about my device configuration :
- Device: Galaxy S7 Edge G935F (Exynos)
- Rom: Decent Ultralite 5.0 (Android 6.0.1) Based on TouchWiz (Stock Samsung)
- Kernel: SuperStock Kernel by Tkkg1994 (It's the stock Samsung kernel with only one change : SELINUX set to Permissive instead of Enforcing)
- Root: MagiskSU
- Recovery: TWRP v3.0.2.4
2 - Now some infos about my Magisk Config :
- Modules : Emoji One, Unified Hosts Adblock, Xposed Framework (SDK 23).
- Magisk Hide : Only Snapchat (which I don't even use lol)
- Settings Enabled : BusyBox, Magisk Hide, Systemless hosts
3 - Just in case, my modules of Xposed are :
- BootManager
- GalaxyXMod
- Greenify
- Unicon
- XInternalSD
That's it, if you need any more informations, I'm here.
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
ken2802 said:
I already added my logcat in the old thread, if it helps.
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Better to post it or a link here so topjohnwu doesn't have to search too much.
Didgeridoohan said:
Better to post it or a link here so topjohnwu doesn't have to search too much.
Click to expand...
Click to collapse
I made a new one.
https://drive.google.com/file/d/0B94u0_R6vixWbmtuUmFYQzhfWXM/view?usp=drivesdk
here is my logcat s7 edge android 6.0.1
I/Timeline( 5058): Timeline: Activity_launch_request id:com.topjohnwu.magisk time:68806449
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/MultiWindowPolicy( 4137): Gamemode - return 0, when calling identifyForegroundApp(com.topjohnwu.magisk)
V/WindowManager( 4137): addAppToken: AppWindowToken{d07f2779e token=Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594}}} to stack=1 task=594 at 0
D/ISSUE_DEBUG( 4137): InputChannelName : 9fd4a02 Starting com.topjohnwu.magisk
D/ActivityManager( 4137): Launching com.topjohnwu.magisk, updated priority
D/GameManagerService( 4137): NotifyRunnable. pkg: com.topjohnwu.magisk, type: 4, isMinimized: false, isTunableApp: false
E/AndroidRuntime(13507): Process: com.topjohnwu.magisk, PID: 13507
E/AndroidRuntime(13507): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.topjohnwu.magisk/com.topjohnwu.magisk.SplashActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
W/ResourcesManager(13507): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.topjohnwu.magisk rsrc of package com.topjohnwu.magisk
V/MARsPolicyManager( 4137): updatePackagesScore PackageInfo name -- com.topjohnwu.magisk
W/ActivityManager( 4137): Force finishing activity com.topjohnwu.magisk/.SplashActivity
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
V/WindowStateAnimator( 4137): Finishing drawing window Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
I/WindowManager( 4137): Screenshot max retries 4 of Token{81ce1d9 ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}} appWin=Window{9fd4a02 u0 d0 Starting com.topjohnwu.magisk} drawState=3
D/ISSUE_DEBUG( 4137): InputChannelName : 852d82d Application Error: com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/GameManagerService( 4137): identifyGamePackage. com.topjohnwu.magisk
D/StatusBarManagerService( 4137): manageDisableList userId=0 what=0x0 pkg=Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=DRAW_PENDING
V/WindowStateAnimator( 4137): Finishing drawing window Window{852d82d u0 d0 Application Error: com.topjohnwu.magisk}: mDrawState=HAS_DRAWN
W/ActivityManager( 4137): Activity pause timeout for ActivityRecord{6fff420 u0 com.topjohnwu.magisk/.SplashActivity t594 f}
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mServices
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mProviders
D/PackageManager( 4137): getComponentMetadataForIconTray : com.topjohnwu.magisk.SplashActivity does not exist in mReceivers
I/ApplicationPackageManager( 4751): load=com.topjohnwu.magisk, bg=192-192, dr=192-192
W/ResourcesManager( 4751): getTopLevelResources: /data/app/com.topjohnwu.magisk-2/base.apk / 1.0 running in com.android.systemui rsrc of package com.topjohnwu.magisk
I/ActivityManager( 4137): Process com.topjohnwu.magisk (pid 13507)(adj 9) has died(267,1161)
D/ActivityManager( 4137): isAutoRunBlockedApp:: com.topjohnwu.magisk, Auto Run ON
Click to expand...
Click to collapse
I'm gonna try to find out which build breaks it.
Does v4.1 works?
4.1 is the last that works on my s6 edge g925f
Gesendet von meinem SM-G925F mit Tapatalk
topjohnwu said:
I'm gonna try to find out which build breaks it.
Does v4.1 works?
Click to expand...
Click to collapse
Yes it works.
ok i hope ive done it right, i used catlog and saved log after crash magisk
hope its helpfull
see attachment
Samsung Galaxy S6 (SM-G920F) Alexis Rom 8.1, Arter97: Works
Samsung Galaxy S4 (GT-I9505) AICP 12.1: Works
Samsung Galaxy Tab S (SM-T800) IronRom 3.2: Doesn't Work
Samsung Galaxy S4 Mini (GT-I9195) AICP 12.1: Will check when battery is full again
Will try to get log cats from all and the crash occurs during the splash screen of Magisk Manager
edit: Added the log files dunno if they are properly for you.
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
aforss said:
here is my logcat s7 edge android 6.0.1
Click to expand...
Click to collapse
I would like to discuss with you about an issue on the S7 Edge, can you check you PMs ?
I don't want to pollute this thread.
Thank You
apc said:
@topjohnwu - there was a problem with the refactoring you did before v4.2 with getting the application context out of the activity classes.
I made a quick fix you can find here: https://github.com/maclarsson/MagiskManager/commit/dbb7cb90529d1c9b9c95d1a0a8479c8f25464869
this works now with my S6, but certainly not the best programming style - so I leave it to you to resolve it up to your standards... :angel:
Click to expand...
Click to collapse
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
topjohnwu said:
Thanks, if it's the context issue.....
To all:
Here is a test build in the attachments, please try it out and check if it crashes for you.
(Re-uploaded)
Click to expand...
Click to collapse
It works
No FCs
Works perfectly now
Working great (again) on my Galaxy S5 SM-G900F. Earlier (before MagiskSU) I had removed root to pass SN because Magisk had CTS profile mismatch error. But now SN is passed and I couldn't be happier. Thank you so much topjohnwu . Running RR-N rom 11 Feb 17 build with stock RR kernel, twrp 3.0.2-2
lahceneamine said:
P.S: Myself and another member (@koko115) are experiencing and issue since Magisk v11.1 : a very long reboot time (about 1m42sec), when you'll have time, I would like to talk more about it, thank you.
Click to expand...
Click to collapse
@topjohnwu
I've also noticed slow bootup times since Magisk v11.1 on a Samsung Galaxy Note 3 (stock android 5.0). It hangs at the first screen you see when you turn on the phone (before the Samsung logo screen). It eventually boots up and seems to work fine, but I didn't see this delay on earlier versions of Magisk.
Edit:
I'm using MagiskSU with no extra modules.
DISCLAIMER
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.
*/
Unofficial LineageOS 13.0 builds for the SGH-T679, ancora_tmo
This ROM currently has reboot issues. There is a list below that lists what works and what doesn't
What works:
Boots
Bluetooth
System Sounds
SD Card
Sensors like accelerometer, light sensor, etc.
Everything else that should work
What doesn't work:
WiFi
RIL (SIM)
Camera
Media Sounds (I think)
Reboots
Probably some sensors...
Other things I'm forgetting...
The current build that we are testing is available to download from the Downloads section of this thread. You will also need the boot.img downloaded too as it needs to be flashed RIGHT AFTER the ROM to the boot partition. ** NOTE: Before installing this ROM, you need to wipe all partitions in TWRP besides the SD Card, then flash! **
To flash this ROM, you will need cars1189's TWRP OS2SD recovery. It can be downloaded here:
https://www.androidfilehost.com/?fid=95916177934529908
We want your feedback here in the thread! PLEASE post things that are not working in the ROM besides the ones that we currently have listed! **We want help from dev that can get us logs through "adb logcat" to help fix bugs, etc.**
We also have a Telegram group chat setup for you guys to join if you like. The goal there is the same here, test, report, and fix. Logs can be sent to us here as well. You can join here:https://t.me/exhibitdev
XDA:DevDB Information
LineageOS 13.0 for Galaxy Exhibit II 4G, ROM for the Samsung Galaxy Exhibit 4G
Contributors
SJR (Sam), androidlover5842, cars1189
Source Code: http://www.github.com/ancora-tmo
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2017-06-03
Last Updated 2017-06-07
Reserved
Changelog
Changelog is a work in progress, it will be appearing soon...
Reserved
Interesting effort.
It seems like there will be two kinds of issues with this effort: hardware support issues and footprint issues (because the device only has 512MB RAM).
Regarding hardware support: Did you start from "scratch" somehow, or from @cars1189's device tree? The git history at least doesn't reflect that. Since cars1189 had most of the hardware working I would have expected someone to start from there.
For the footprint side, although it may be somewhat counter-intuitive I would guess that you might have better luck with LineageOS 14.1 rather than LineageOS 13. Two data points: nexus 7 "grouper" (with 1GB RAM) seems to perform better with Nougat than with Marshmallow... and also, a new device "jelly" is being released via kickstarter with 512MB RAM and Nougat.
aaopt said:
Interesting effort.
It seems like there will be two kinds of issues with this effort: hardware support issues and footprint issues (because the device only has 512MB RAM).
Regarding hardware support: Did you start from "scratch" somehow, or from @cars1189's device tree? The git history at least doesn't reflect that. Since cars1189 had most of the hardware working I would have expected someone to start from there.
For the footprint side, although it may be somewhat counter-intuitive I would guess that you might have better luck with LineageOS 14.1 rather than LineageOS 13. Two data points: nexus 7 "grouper" (with 1GB RAM) seems to perform better with Nougat than with Marshmallow... and also, a new device "jelly" is being released via kickstarter with 512MB RAM and Nougat.
Click to expand...
Click to collapse
Thanks for the reply! We started with a mix of @sirmordred's and @cars1189's trees and kernels respectively. We are reworking the hardware that doesn't work from some scratch and already written stuff to make it work nicely. @cars1189 cm12.1 was like 100% stable but it wasn't even close when we initially went to build it with LOS13. Nougat would be good to try but MM needs a stable base for now if you get what I mean. We are optimizing RAM as much as possible, currently the system reads 423MB. We are planning some more optimization soon but we are working on fixing rebooting, SE Policy, and such. Otherwise the system UI runs pretty quick right now. In general, MM will be more usable than Nougat but I'll talk to AndroidLover, my helper/dev and bug fixer, and we will figure something out!
aaopt said:
Interesting effort.
It seems like there will be two kinds of issues with this effort: hardware support issues and footprint issues (because the device only has 512MB RAM).
Regarding hardware support: Did you start from "scratch" somehow, or from @cars1189's device tree? The git history at least doesn't reflect that. Since cars1189 had most of the hardware working I would have expected someone to start from there.
For the footprint side, although it may be somewhat counter-intuitive I would guess that you might have better luck with LineageOS 14.1 rather than LineageOS 13. Two data points: nexus 7 "grouper" (with 1GB RAM) seems to perform better with Nougat than with Marshmallow... and also, a new device "jelly" is being released via kickstarter with 512MB RAM and Nougat.
Click to expand...
Click to collapse
SJR (Sam) said:
Thanks for the reply! We started with a mix of @sirmondred's and @cars1189's trees and kernels respectively. We are reworking the hardware that doesn't work from some scratch and already written stuff to make it work nicely. @cars1189 cm12.1 was like 100% stable but it wasn't even close when we initially went to build it with LOS13. Nougat would be good to try but MM needs a stable base for now if you get what I mean. We are optimizing RAM as much as possible, currently the system reads 423MB. We are planning some more optimization soon but we are working on fixing rebooting, SE Policy, and such. Otherwise the system UI runs pretty quick right now. In general, MM will be more usable than Nougat but I'll talk to AndroidLover, my helper/dev and bug fixer, and we will figure something out!
Click to expand...
Click to collapse
Nice to see someone still working on this. Theres definitely many things that need fixing if someone is to update for newer android versions. Last i left off the sensors where being moved open source and while they work on older versions even 5.1.1 had issues with some of them. If anyone wants help or for me to try a build(if you have a bootable base) id be more then happy to help test, I just dont have much time for development. Good Luck!
cars1189 said:
Nice to see someone still working on this. Theres definitely many things that need fixing if someone is to update for newer android versions. Last i left off the sensors where being moved open source and while they work on older versions even 5.1.1 had issues with some of them. If anyone wants help or for me to try a build(if you have a bootable base) id be more then happy to help test, I just dont have much time for development. Good Luck!
Click to expand...
Click to collapse
It would be great to help us out! There is a test build that boots but has some rebooting issues. In the Downloads section of this thread. So yeah, we need a hand with testing and stuf!
Thanks!
Sam
SJR (Sam) said:
It would be great to help us out! There is a test build that boots but has some rebooting issues. In the Downloads section of this thread. So yeah, we need a hand with testing and stuf!
Thanks!
Sam
Click to expand...
Click to collapse
Below is what i found of things that need to be addressed. I however am no able to get it to boot it just keep restarting at the boot animation. Seems like theres still alot to be done.
Code:
#1 ZN7android11MediaPlayer13setDataSourceEPKcPKNS_11KeyedVectorINS_7String8ES4_EE
add /system/lib/libseccameraadaptor.so|libshim_native.so
maybe more after you add this?
Lot of selinux issues id recomment trying with permisive
06-06 09:42:57.670 1 1 I init : type=1400 audit(0.0:3): avc: denied { mounton } for path="/sys/kernel/debug" dev="debugfs" ino=1 scontext=u:r:init:s0 tcontext=u:object_r:debugfs:s0 tclass=dir permissive=1
06-06 09:42:58.270 1 1 I init : type=1400 audit(0.0:4): avc: denied { setattr } for name="mmcblk0p14" dev="tmpfs" ino=4049 scontext=u:r:init:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:5): avc: denied { read } for name="mmcblk0p15" dev="tmpfs" ino=4052 scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:6): avc: denied { open } for name="mmcblk0p15" dev="tmpfs" ino=4052 scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:7): avc: denied { write } for name="mmcblk0p15" dev="tmpfs" ino=4052 scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.500 134 134 I e2fsck : type=1400 audit(0.0:8): avc: denied { ioctl } for path="/dev/block/mmcblk0p15" dev="tmpfs" ino=4052 ioctlcmd=127c scontext=u:r:fsck:s0 tcontext=u:object_r:block_device:s0 tclass=blk_file permissive=1
06-06 09:42:58.600 126 126 I multipdp: type=1400 audit(0.0:9): avc: denied { read write } for name="dpram1" dev="tmpfs" ino=3807 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:42:58.600 126 126 I multipdp: type=1400 audit(0.0:10): avc: denied { open } for name="dpram1" dev="tmpfs" ino=3807 scontext=u:r:kernel:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:42:59.991 1 1 I init : type=1400 audit(0.0:11): avc: denied { getattr } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.011 175 175 I init : type=1400 audit(0.0:12): avc: denied { execute } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.011 175 175 I init : type=1400 audit(0.0:13): avc: denied { read open } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.011 175 175 I init : type=1400 audit(0.0:14): avc: denied { execute_no_trans } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:00.141 179 179 I init : type=1400 audit(0.0:15): avc: denied { execute_no_trans } for path="/system/bin/get_macaddrs" dev="mmcblk0p17" ino=354 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
06-06 09:43:00.381 183 183 I expr : type=1400 audit(0.0:16): avc: denied { write } for path="pipe:[4523]" dev="pipefs" ino=4523 scontext=u:r:toolbox:s0 tcontext=u:r:init:s0 tclass=fifo_file permissive=1
06-06 09:43:01.052 160 160 I surfaceflinger: type=1400 audit(0.0:18): avc: denied { read write } for name="kgsl-2d0" dev="tmpfs" ino=4104 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:43:01.052 160 160 I : type=1400 audit(0.0:19): avc: denied { open } for name="kgsl-2d0" dev="tmpfs" ino=4104 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:device:s0 tclass=chr_file permissive=1
06-06 09:43:04.876 1 1 I init : type=1400 audit(0.0:25): avc: denied { getattr } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:04.886 249 249 I init : type=1400 audit(0.0:26): avc: denied { execute } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:04.896 249 249 I init : type=1400 audit(0.0:27): avc: denied { read open } for name="sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:04.896 249 249 I init : type=1400 audit(0.0:28): avc: denied { execute_no_trans } for path="/system/bin/sdcard" dev="mmcblk0p17" ino=501 scontext=u:r:init:s0 tcontext=u:object_r:sdcardd_exec:s0 tclass=file permissive=1
06-06 09:43:05.046 168 168 I mediaserver: type=1400 audit(0.0:29): avc: denied { execmod } for path="/system/lib/libaudioalsa.so" dev="mmcblk0p17" ino=1204 scontext=u:r:mediaserver:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=1
[ 10.267028] type=1400 audit(1496742028.465:23): avc: denied { read write } for pid=160 comm="surfaceflinger" name="msm_rotator" dev="tmpfs" ino=3978 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:audio_device:s0 tclass=chr_file permissive=1
[ 10.338684] type=1400 audit(1496742028.465:24): avc: denied { open } for pid=160 comm="surfaceflinger" name="msm_rotator" dev="tmpfs" ino=3978 scontext=u:r:surfaceflinger:s0 tcontext=u:object_r:audio_device:s0 tclass=chr_file permissive=1
Service sdcard needs a SELinux domain defined
LineageOS Version: '13.0-20170526-UNOFFICIAL-ancora_tmo'
cars1189 said:
Below is what i found of things that need to be addressed. I however am no able to get it to boot it just keep restarting at the boot animation. Seems like theres still alot to be done.
Click to expand...
Click to collapse
Oh, sorry! I should include a built boot.img from our cm12 kernel(yours that got androidlover to get it to boot it for now.) THE boot.img is now available in the downloads section. Also if logcat can be posted a zip file or text file, that would be great, or we will find another way to share them.
Sam
Hey all, I added a link to the first post. It includes out new Telegram groupchat link to talk about the phone, etc. in there. Go join it if you like!
We are planning to push out a new build in a day or so that will be much better. Stay posted!! Write us any questions and I will read them!
I'm building tonight, will have a build up tomorrow morning POST around 10ish if it works without build errors. Any of you guys have questions about the ROM, etc. ?
New build is available for download in the threads download section. I'll update the changelog soon. Let me know what works/doesn't work in the new build!
*EDIT* The build I uploaded DOES NOT BOOT! I will reupload tomorrow with a working one. Sorry!
Currently having trouble with libs and things, we are playing around with things to get stuff working, anyone have suggestions?
Hey all, been busy but I want to get back to this phone this week with 13.0 if it's possible for me, anyone want to help me? That would be awesome!
Sam
Hey man, I would love to help, I am not a developer or anything but I can try the builds if you wish. Tried the one in the downloads section but didn't read that it didn't boot so if you have one that I could try I can get back to you and report everything.
Sorry for double posting, was really interested in this and was wondering if you got any news or if you are still working in this, would love a build to play with! hahah ? and thanks to you for this!
Szand said:
Sorry for double posting, was really interested in this and was wondering if you got any news or if you are still working in this, would love a build to play with! hahah ? and thanks to you for this!
Click to expand...
Click to collapse
I really want to get back to this phone, something keeps bringing me back. I'm trying to get a few other devices I have done. For now though, I've been looking at 14.1 as that seems promising. I'll see what I can do any help with development too is much appreciated
SJR (Sam) said:
I really want to get back to this phone, something keeps bringing me back. I'm trying to get a few other devices I have done. For now though, I've been looking at 14.1 as that seems promising. I'll see what I can do any help with development too is much appreciated
Click to expand...
Click to collapse
Thanks man and I would love to help with development but I really don't have any knowledge in it, but I'm looking forward to learning and would if you could tell me where to start. :victory:
Any news?
{
"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 a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
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 in the LineageOS GitHub organization. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. You can also view the changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/pioneer/install
Downloads :
https://download.lineageos.org/pioneer
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel, or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thank you !
Just tested lineage-19.0-20220219_132428-UNOFFICIAL-pioneer.zip
A pretty good start for Android 12.
Tested and working :
- fingerprint sensor
- WiFi
- video playback on youtube with default browser
- camera front and rear + video recording + flash light
- USB MTP
- Gyroscope
Comments :
- audio playback working but crackles a bit when at maximum
- The settings menu overlaps the 3 buttons controls
Not tested :
- SIM card and everything related (calls, SMS, ...)
- Bluetooth
- GPS
- GApps
And other things.
Really love to see Android 12 on this one.
Android 12 on my sony xa2 will not boot past the lineage os logo even after changing a/b and factory resetting it is there a fix?
Rolling the lineage-19.0-20220301_131228-UNOFFICIAL-pioneer.zip with firmware 50.2.A.3.77
Tested and working:
- Wifi
- 4g / lte
- rear camera
Flakie :
- selfie camera is not working when switching from back, but then is working
When switching from back to selfie camera :
Code:
[ 627.762250] type=1400 audit(1646511939.837:2926): avc: denied { read } for comm="[email protected]" name="u:object_r:bootanim_system_prop:s0" dev="tmpfs" ino=13144 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:bootanim_system_prop:s0 tclass=file permissive=0
[ 627.763506] type=1400 audit(1646511939.837:2927): avc: denied { read } for comm="[email protected]" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 627.763858] type=1400 audit(1646511939.837:2928): avc: denied { read } for comm="[email protected]" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 627.782361] PU: mGpioCnt[4]: 1
[ 627.793963] PU: mGpioCnt[5]: 1
[ 627.817922] msm_cci_init:1439: hw_version = 0x10060000
[ 627.818168] msm_sensor_match_id CAM_ID_8M: 0
[ 627.823084] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800
[ 627.853709] msm_vfe47_process_error_status: camif error status: 0x264
[ 627.853760] 0x0000: 00000001 00000040 00000000 098f0cbf
[ 627.853769] 0x0010: 00000cbf 0000098f 00000000 00001f1f
[ 627.853779] 0x0020: ffffffff ffffffff 0014095d 00000264
[ 627.853786] 0x0030: 00000000 00000001 00000001
[ 627.953623] msm_isp_process_overflow_irq: vfe 1 overflowmask 10,bus_error 3f93
[ 627.953655] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 0
[ 627.953689] overflow processed
[ 627.988483] msm_isp_axi_halt: VFE1 Bus overflow detected: start recovery!
[ 627.988686] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 1
[ 627.989818] msm_ispif_restart_frame_boundary: ISPIF reset hw done, Restarting
[ 628.020401] msm_vfe47_process_error_status: camif error status: 0x264
[ 628.020452] 0x0000: 00000001 00000040 00000000 098f0cbf
[ 628.020462] 0x0010: 00000cbf 0000098f 00000000 00001f1f
[ 628.020471] 0x0020: ffffffff ffffffff 0014095d 00000264
[ 628.020479] 0x0030: 00000000 0000000f 0000000f
[ 628.053631] msm_isp_process_overflow_irq: vfe 1 overflowmask 10,bus_error 3f93
[ 628.053667] msm_vfe47_axi_halt: VFE1 halt for recovery, blocking 0
[ 628.053700] overflow processed
[ 628.910196] FG: fg_somc_get_real_temp: batt:257 aux:-2730 -> real battery temp:257
[ 628.910263] FG: fg_somc_jeita_step_charge_work: [Charging] RTEMP:257 IBATT:-40mA VBATT:3981mV VCELL:3982mV VCELL_MAX:4034
[ 628.910340] PMI: smblib_somc_handle_jeita_step_fv: set fv:4380000
[ 630.264121] q6asm_callback: payload size of 8 is less than expected.
[ 630.422670] msm_private_ioctl:Notifying subdevs about potential sof freeze
[ 630.422783] MSM-SENSOR-INIT msm_sensor_init_subdev_ioctl:119 default\x0a
[ 630.422965] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0xff
[ 630.423006] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR0 = 0x0
[ 630.423021] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR1 = 0x1
[ 630.423037] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR2 = 0x0
[ 630.423051] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR3 = 0x20
[ 630.423065] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR4 = 0x0
[ 630.423079] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR5 = 0x0
[ 630.423094] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR6 = 0x4
[ 630.423109] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR7 = 0x0
[ 630.423123] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR8 = 0x80
[ 630.423138] msm_csiphy_irq CSIPHY2_IRQ_STATUS_ADDR9 = 0x40
[ 630.426309] type=1400 audit(1646511942.497:2929): avc: denied { read } for comm="CAM_mct_freeze" name="clk" dev="debugfs" ino=4921 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:debugfs:s0 tclass=dir permissive=0
[ 630.454176] ispif_process_irq: PIX0 frame id: 2383
[ 630.488551] ispif_process_irq: PIX0 frame id: 2384
[ 630.521908] ispif_process_irq: PIX0 frame id: 2385
[ 630.555239] ispif_process_irq: PIX0 frame id: 2386
[ 630.587439] ispif_process_irq: PIX0 frame id: 2387
When closing camera app, re-opening, selfie is working but following trace :
Code:
[ 520.236493] type=1400 audit(1646511832.307:2918): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:bootanim_system_prop:s0" dev="tmpfs" ino=13144 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:bootanim_system_prop:s0 tclass=file permissive=0
[ 520.238093] type=1400 audit(1646511832.307:2919): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 520.238408] type=1400 audit(1646511832.307:2920): avc: denied { read } for comm="HwBinder:832_2" name="u:object_r:default_prop:s0" dev="tmpfs" ino=13201 scontext=u:r:hal_camera_default:s0 tcontext=u:object_r:default_prop:s0 tclass=file permissive=0
[ 520.252543] PU: mGpioCnt[4]: 1
[ 520.263611] PU: mGpioCnt[5]: 1
[ 520.290503] msm_cci_init:1439: hw_version = 0x10060000
[ 520.291319] msm_sensor_match_id CAM_ID_8M: 0
[ 520.362722] msm_csid_irq CSID2_IRQ_STATUS_ADDR = 0x800
Had a issue on first boot after flash :
- top menu was not acessible (nothing when pulling down)
- only back button was showing on the "virtual button" down
Fixed after a reboot.
You mind sharing your build configs? You are rolling this kernel : https://github.com/luk1337/android_kernel_sony_sdm660/tree/lineage-19.0
With main branch 19.0 of lineage official repo ?
lecler_i said:
You mind sharing your build configs? You are rolling this kernel : https://github.com/luk1337/android_kernel_sony_sdm660/tree/lineage-19.0
With main branch 19.0 of lineage official repo ?
Click to expand...
Click to collapse
Everything you need is either on my github, LineageOS github/gerrit, or TheMuppets.
Hi
Thx for making Android 12 possible on my XA2
Anyway i somehow cant connect properly to wifi!
So i logged into my wifi in the setup (I installed NikGapps) but even tho he says "Connected" he doesnt let me go to the second step of setup. I already tried different Wlans but still nothing.
Hope someone can help me.
Try BiTGApps
Hello
Just installed the latest version available (19.1 - 26/03) and it worked fine. The problem is that, when I went to TWRR to flash gapps, TWRP did not ask for the device encryption password and thus it did not work. I don't know how to proceed.
Ok so I installed the latest version and installed NikGapps through lineage recovery. It works indeed!
Tested:
SIM and SMS
WiFi
Camera
Gapps (I had some problems with Bromite System Webview but disabling the module solved it)
Torch
Location
Cell data
Magisk canary
I miss an option to select the system accent instead of the adaptive one that selects it based on the wallpaper, but everything else is fine.
TWRP still does not ask for a pin and the data keeps encrypted so it is not usable, but as I said flashing through lineage recovery works (at least for gapps)
Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
Is the ROM still under development?
Thank You in advance.
kereth said:
Does SMSs, Wi-Fi and other stuff work also without GApps or is it required to install it?
Is the ROM still under development?
Thank You in advance.
Click to expand...
Click to collapse
Everything you asked for works absolutely fine without any issues.
You don't need gApps for that.
I can't say how active the developers are, but an update was released just yesterday (16.04)
Thanks a lot @LuK1337
Should I clean flash updates or can I dirty flash them without losing any data?
Now that LineageOS 19 is officially out, will this thread be converted to one for the official build or will there be a separate thread that we have to join?
Don't know about you guys but I have a mixed feeling about the theming in Android 12. Anyone know if there is a way to choose the colour I want the system to use like we had in the previous versions?
@LuK1337
LOS 19.1... Great ROM, and now it's official. Have many thanks for that!!
One (first?) question:
I see, the camera app has changed from former snap-camera to standard android-camera now. How can I switch this camera into silent mode? I can't find any switch for that.
Or, is it possible to have snap-camera even in LOS 19.1, as in former LOS-releases?
Thanks a lot,
samhhmobil
k2helix said:
Should I clean flash updates or can I dirty flash them without losing any data?
Click to expand...
Click to collapse
I did an update from 18.1 and it surprisingly worked well, but it's not recommended to do.
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
@LuK1337 do you have any advice what I can try to make TWRP working again and recognize the encryption?
has anyone tried to go to TWRP after updating?
emc02 said:
I did an update from 18.1 and it surprisingly worked well, but it's not recommended to do.
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
@LuK1337 do you have any advice what I can try to make TWRP working again and recognize the encryption?
has anyone tried to go to TWRP after updating?
Click to expand...
Click to collapse
The version of twrp I last used is 3.5.1_9. This time I just used the LineageOS recovery.
malerocks said:
The version of twrp I last used is 3.5.1_9. This time I just used the LineageOS recovery.
Click to expand...
Click to collapse
ok, with 18.1 I had issues using the LOS recovery, so I flashed always with TWRP. But I've installed it now on the other partition with LOS recovery and it's working well.
So you think a normal OTA Update of LOS will work now out of the box?
Yes. I tried an OTA today and it went all fine. I never had issues with OTAs with the previous LineageOS version either.
emc02 said:
I've got one issue with TWRP, but I don't know if this is related to my dirty flash or some issue with TWRP itself:
I've tried to update the second/other partition of the A/B, but on trying to boot to TWRP with fastboot command, TWRP does not recognize the encryption and shows weird folders and files.
I was using the latest version of TWRP (2.6.1_9)
[...]Has anyone tried to go to TWRP after updating?
Click to expand...
Click to collapse
You're right, since installing LOS 19.1, TWRP (even the newest one, but the older ones too) cannot decrypt the user data.
samhhmobil
HI
does anybody know how to get rid of this error:
Code:
1|ASUS_I006D:/sdcard/Download # id
uid=0(root) gid=0(root) groups=0(root) context=u:r:magisk:s0
ASUS_I006D:/sdcard/Download # pm install $PWD/SMMI_TEST.apk
avc: denied { read } for scontext=u:r:system_server:s0 tcontext=u:object_r:fuse:s0 tclass=file permissive=1
Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE: Reconciliation failed...: Reconcile failed: Package com.asus.atd.smmitest has no signatures that match those in shared user android.uid.system; ignoring!]
1|ASUS_I006D:/sdcard/Download #
SMMI_TEST.apk is an app from the original Android for the ASUS Zenfone 8 and I want install it in OmniROM 12 .
regards
Bernd
Update 15.06.2022
Looks like this error can only be fixed by signing the app with the private key used in the running ROM
Update 22.06.2022
The test app works fine on a custom ROM if signed with the private key for that ROM (tested with a self compiled version of OmniROM 12)
Update 25.06.2022
"Resolved" by compiling my own CustomROM -- see How to use the Hardware Test App from ASUS on a Zenfone running a CustomROM
from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest
gothta said:
from AndroifManifest.xml remove android:sharedUserId="android.uid.system" from manifest
Click to expand...
Click to collapse
... without that permission the app can be executed but can not do anything anymore