I know one of the great points on Z line is the quite untouched Google ROM. MIUI is my favorite customized ROM by manufacturer.
So, why don't give a option to use both? Will you like my idea and will use it?
Thanks for your opinion.
Enviado de meu XT1650 usando Tapatalk
Totally. I don't know if I would use it as my daily since I'm a flashaholic, but will try it for days/weeks depending on how smooth/stable it is. I've had some nice experiences before, so I'm having high hopes on this.
Not bad idea, go for it, i really like MIUI
The only problem is that my Bootloader is upgraded, so I cannot test since MIUI isn't in 7.0 version. I will wait for MIUI 9 because of that, because develop a port that the developer cannot test isn't a good idea in my view
Enviado de meu XT1650 usando Tapatalk
andregarcia_1 said:
I know one of the great points on Z line is the quite untouched Google ROM. MIUI is my favorite customized ROM by manufacturer.
So, why don't give a option to use both? Will you like my idea and will use it?
Thanks for your opinion.
Enviado de meu XT1650 usando Tapatalk
Click to expand...
Click to collapse
Hey last month i started to port MIUI8.2 7.0 from Mi5 firmware to our device and i had some progress
i'm not with my PC for a month, i thought to share my work for interested devs
here's my ROM and superR kitchain Project FIles : Download Folder
it's Not Booting (Do NOT INSTALL if you are NOT Dev)
here's Error Log : Unable to open socket for UEventObserver
it Happens Because of NetLink Socket Opening. I couldn't fix this (tried netd, ipacm & iptables), someone smarter than me should take a look. i don't know what i missed (probably it's kernel side)
i really like MIUI i'll appreciate if you have look
Notes :
+ this rom has 6.0.1 moto Kernel so it's not booting on new bootloaders. and when i updated to 7.0 kernel(and dt) i got this error crashes surfaceflinger while booting:
Code:
Adreno-GSL: <ioctl_kgsl_driver_entry:562>: open(/dev/kgsl-3d0) failed: errno 5. I/O error
No idea why!
+ all blobs(except apps) taken from here and ipacm from here
+ selinux files is compiled from cm14.0 source with needed permissions on griffin device tree
+ adbd is starting on init at init.rc to debug and shell access on bootloops just replace "adb_keys" if adb needs permissions
+ i replaced all needed HALs and ETC folder files
+ if you have any Questions PM me
If someone can do the port is going to be excellent, I'm waiting.
sam564 said:
If someone can do the port is going to be excellent, I'm waiting.
Click to expand...
Click to collapse
+1
++1
+1
1+:good:
Is this project still in the works? I'd love to use this!
+1
I wan MIUI too.
Hello again guys
today i just wanted to play with treble and CLT so i decided to boot MIUI from leaked oreo 8.1 firmware : https://www.xda-developers.com/xiaomi-redmi-note-5-pro-android-oreo-stable/
and after all it's booted on griffin
i'll upload my twrp backup from system partition
bugs : very very unstable :
* for boot need to enter "wificond" in adb shell and to get adb access you need run this command on adb shell from twrp : "cd ~/.android && adb push adbkey.pub /data/misc/adb/adb_keys"
* wifi broken
* ril broken
* camera broken
whats working :
* few things like BT and sensors ...
twrp backup : https://www.androidfilehost.com/?fid=890129502657599583
flash lineage
restore backup
flash premssiver.zip
---------------------------------------------------
how is it booted?
i'm going to explain from beginning, porting it is not very hard
got leaked miui and latest lineage and started CLT on it
then i got miui with griffin vendor inside
flashed on device with clean (not magisked) boot.img from lineage
and enabled premissive selinux
edited prop.default and build.prop to remove device specific props and enabled adb + pm.dexopt (see props.zip)
build.prop for /system/
and prop.default for /system/etc/
>>> First try to boot failed by rebooting to bootloader
by generating multiple times the spammy console-remoops, finally i found out reboots because of selinux problems
i didn't want to mess with it so i directly adb pushed lineage /system/etc/selinux dir to my device
>>> booted to bootanimation
here i got huge errors as usual
/bin/keystore was looking for vendor.qti.hardware.wifi.keystore...._vendor.so and we don't have it because that miui rom is built from full CAF source and we are using aosp keystore in lineage so i replaced it with lineage /bin/keystore
wificond had missing symbol which is coming from qsap_sdk so i just replaced miui wificond with lineage one
and cameraserver is spamming here
>>> nothing much same on bootanimation
now zygote dies because can't find power_profile.xml in res/xml
actually this miui is not enabled RRO in that build so theres no framework-res__auto_generated_rro.apk in vendor, everything is on system framework-res.apk
so i removed my framework-res__auto_generated_rro.apk
need to wipe data
>>> failed again
libstagefright had some issues
i replaced it with lineage one with some other media libs (sorry i don't remember names)
>>> i guess booted this time :fingers-crossed: but soft reboots on setupwizard on trying to search for wifis with this error:
Code:
04-23 11:04:56.499 893 1505 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiScanningService
04-23 11:04:56.499 893 1505 E AndroidRuntime: java.lang.IllegalArgumentException
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.BinderProxy.transactNative(Native Method)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.BinderProxy.transact(Binder.java:767)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.net.wifi.IWifiScannerImpl$Stub$Proxy.scan(IWifiScannerImpl.java:310)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.WificondControl.scan(WificondControl.java:600)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.WifiNative.scan(WifiNative.java:351)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WificondScannerImpl.processPendingScans(WificondScannerImpl.java:452)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WificondScannerImpl.startSingleScan(WificondScannerImpl.java:203)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.HalWifiScannerImpl.startSingleScan(HalWifiScannerImpl.java:78)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WifiScanningServiceImpl$WifiSingleScanStateMachine.tryToStartNewScan(WifiScanningServiceImpl.java:851)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.server.wifi.scanner.WifiScanningServiceImpl$WifiSingleScanStateMachine$DriverStartedState.processMessage(WifiScanningServiceImpl.java:650)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:992)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:809)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
04-23 11:04:56.499 893 1505 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:65)
you can stop rebooting by entering "wificond" in adb shell
now setupwizard after sim detect stops with black screen
---
in logs we can see it's looking for 2 services miui.shell and miui.fdpp :silly:
they have some ramdisk scripts related to miui in boot.img but all we need is init.miui.rc
import it in your init.qcom.rc and add to /vendor/etc/init/hw/
almost done but you need to clear file_contexts of this 2 bin because we're using lineage sepolicies : /system/xbin/shelld and /system/bin/fdpp
>>> setupwizard goes further
but i couldn't finish it so simply removed it from /priv-app
booted but system is not very usable
so i took this TWRP backup and tried flashing gapps
finished setupwizard
and restored backup
>>> now miui is fully booted
i don't know any better way to bypass setupwizard
Wow,,MIUI coming.. :victory::victory:
I love you man!
@erfanoabdi,. You working on miui?
rakee said:
@erfanoabdi,. You working on miui?
Click to expand...
Click to collapse
No i just did it for my treble testing and actually fun
Maybe after release of one official miui with Android 8.1 i can start working on it
erfanoabdi said:
No i just did it for my treble testing and actually fun
Maybe after release of one official miui with Android 8.1 i can start working on it
Click to expand...
Click to collapse
MIUI from leaked oreo 8.1 firmware is already quite stable, right?
https://www.xda-developers.com/xiaomi-mi-6x-china-dual-cameras-snapdragon-660/ @erfanoabdi
Its MIUI 9.5 on top of Android 8.1 Oreo
Related
I cannot download any files on my Le Max 2 x829 EUI 5.8.016S.
Here is the logcat. I rooted and uninstalled LeShare app (which seems like what is crashing) so I did a Nandroid restore and the problem still exists. When I wiped I removed everything besides internal storage but still have the problem.
06-30 14:48:32.885 8953-8953/? E/ActivityThread: Failed to find provider info for com.android.leShare
06-30 14:48:32.887 8953-8953/? E/ActivityThread: Failed to find provider info for com.android.leShare
--------- beginning of crash
06-30 14:48:32.889 8953-8953/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: system:ui, PID: 8953
java.lang.IllegalArgumentException: Unknown URL content://com.android.leShare/leShareTable
at android.content.ContentResolver.insert(ContentResolver.java:1230)
at com.android.internal.app.ResolverActivity.insertDB(ResolverActivity.java:2581)
at com.android.internal.app.ResolverActivity.getClickCounts(ResolverActivity.java:2600)
at com.android.internal.app.ResolverActivity.insertCounts(ResolverActivity.java:2640)
at com.android.internal.app.ResolverActivity.startSelected(ResolverActivity.java:789)
at com.android.internal.app.ResolverActivity$11.onClick(ResolverActivity.java:2470)
at android.view.View.performClick(View.java:5226)
at android.view.View$PerformClick.run(View.java:21350)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5571)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
Does anyone know how to fix it? Thanks.
Update your 16S rom, we are in 2017
Enviado desde mi LEX820 mediante Tapatalk
Hello, I have my Honor since a week and I'm pretty happy with it apart from a what seemed to be a random reboot problem. I think I cornered it and would like your advices and/or confirmation (which I think won't be easy because of the EAP-SIM context )
So my operator (Freemobile from france) offers a wifi service using EAP-SIM as authentication scheme and it seems to be the cause of my reboots. Here are the logs :
Code:
07-20 09:06:56.924 21718 21718 W Mms_TXM_SVC: ConnectivityBroadcastReceiver.onReceive() action: android.net.conn.CONNECTIVITY_CHANGE
07-20 09:06:56.929 12020 12020 I wpa_supp: wlan0: CTRL-REQ-SIM-5:GSM-AUTH:4a83551f630844118559a95f76fe5606:bdb35e342afaa846b3efe0791b00e0d3:cdd2604853124f009a16addcd439afae needed for SSID FreeWifi_secure
--------- beginning of crash
07-20 09:06:56.931 11374 11734 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: WifiStateMachine
07-20 09:06:56.931 11374 11734 E AndroidRuntime: java.lang.NullPointerException: Attempt to read from field 'android.net.wifi.WifiEnterpriseConfig android.net.wifi.WifiConfiguration.enterpriseConfig' on a null object reference
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at com.android.server.wifi.WifiStateMachine.getEapSubId(WifiStateMachine.java:10098)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at com.android.server.wifi.WifiStateMachine.getGsmSimAuthResponse(WifiStateMachine.java:9789)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at com.android.server.wifi.WifiStateMachine.handleGsmAuthRequest(WifiStateMachine.java:9849)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at com.android.server.wifi.WifiStateMachine$ConnectModeState.processMessage(WifiStateMachine.java:6787)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.processMsg(StateMachine.java:987)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at com.android.internal.util.StateMachine$SmHandler.handleMessage(StateMachine.java:803)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:105)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at android.os.Looper.loop(Looper.java:156)
07-20 09:06:56.931 11374 11734 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:61)
07-20 09:06:57.015 11374 11374 I SendBroadcastPermission: action:android.intent.action.DROPBOX_ENTRY_ADDED, mPermissionType:0
07-20 09:06:57.015 529 1070 I logserver: handle_logfile_events, Object Path:/data/system/dropbox/, mask=0x00000080
07-20 09:06:57.015 529 1070 I logserver: process_one_event, event->len=48, [email protected]
07-20 09:06:57.016 529 1070 I logserver: [find_first_match 2764] commercial versoin(1), beta version(0): 1
07-20 09:06:57.016 529 1070 I logserver: find_first_match: find match, plogs(type=3, pfile=/data/system/dropbox/, match=system_server_crash)
07-20 09:06:57.016 529 1070 I iMonitor: create: 901000000
07-20 09:06:57.016 529 1070 I logserver: process_event_by_imonitor, pos=0, type=SSfalt, event_id=901000000
07-20 09:06:57.017 529 1070 E logserver: imonitor_add_dynamic_path, path:/data/system/dropbox/[email protected]
By the way, what is this dropbox thing ? Is Honor using dropbox to collect crash logs ?
Thx
Is your firmware the latest version? And no, that's not the cloud storage you're thinking. I see that dropbox folder since Gingerbread. It's a folder that Android uses to store some logs, traces and ANRs.
Sent from my Honor 8 using XDA Labs
I don't see any dropbox file in my honor, it might have been installed and uninstalled previously
PalakMi said:
I don't see any dropbox file in my honor, it might have been installed and uninstalled previously
Click to expand...
Click to collapse
Installed and uninstalled previously? Look harder. You will find it.
Sent from my Honor 8 using XDA Labs
Do you have over heating issue before reboot or any software issue, like very lag when open? Have you tried to factory reset your phone? If factory reset cannot resolve this, then I would suspect a hardware failure...
I looked again, nothing at all
PalakMi said:
I looked again, nothing at all
Click to expand...
Click to collapse
It's not a file. It's a folder inside /data/system. SMH.
Sent from my Honor 8 using XDA Labs
adriansticoid said:
It's not a file. It's a folder inside /data/system. SMH.
Click to expand...
Click to collapse
Ah, it's in system, Thanks
Hello,
I had the same problem (random reboot on honor 9 with Free operator), just download "Messagerie Vocale Free" on the Playstore, go to tools and deactivate 'Freewifi' option (in the tools tab), then Honor 9 will no more randomly reboot.
Best regards.
Yep, same problem here too with EAP-SIM with Free operator .
De-activating eap-sim through free app tools menu works just like de-activating WiFi while on the go. However this doesn't really solve the problem and should you really need the feature, you're played .
Did anyone tried to see if it was fixed with the latest B130 update ?
No pb since B130 update
lillepingu59 said:
Yep, same problem here too with EAP-SIM with Free operator .
De-activating eap-sim through free app tools menu works just like de-activating WiFi while on the go. However this doesn't really solve the problem and should you really need the feature, you're played .
Did anyone tried to see if it was fixed with the latest B130 update ?
Click to expand...
Click to collapse
Didn't have any random reboot since updating to B130. Could you confirm Twister42?
Changed my phone from H8 to H9, experiencing the same problem here (never had random reboots with my H8). Disable freeWifi-secure option in Tools menu didn't solve the issue (go back in application again, free wifi is automatically re-enabled). Still in B100, waiting B130 to check the problem is figured out.
I can confirm now, B130 solved the issue.
jcdid said:
I can confirm now, B130 solved the issue.
Click to expand...
Click to collapse
B130 or b130a?!
PalakMi said:
B130 or b130a?!
Click to expand...
Click to collapse
Just B130 (STF-L09 EUR)
jcdid said:
Just B130 (STF-L09 EUR)
Click to expand...
Click to collapse
Ah, there's b130a
LineageOS 14.1
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Prerequisites
Bootloader unlock > HERE
Recovery twrp > squid2 or sevenmaxs
What works
RIL (dual sim, volte)
WIFI
Tethering
Camera
Bluetooth
Sensors
MTP
Sound
Fingerprint
NFC
MotoActions
- - SELinux: enforcing
Todo
Fix "Enable on-screen nav-bar" toggling option.
Download
https://www.androidfilehost.com/?w=files&flid=251047 AFH LOS7 Files
https://opengapps.org/ OpenGApps - Choose ARM/7.1/PICO or NANO
Source
Device: https://github.com/kayesk/android_device_motorola_montana
Vendor: https://github.com/kayesk/android_vendor_motorola_montana
Branch: cm-14.1
How to install the rom ?
Copy the rom to your G5S.
Restart in recovery (squid or Sevenmaxs)
Take a backup of existing ROM.
Wipe clean (Cache, Data, Dalvik/ART, System)
Install ROM.
Make a wipe cache.
Reboot System.
Initial load would take time.
Contributions :
@GoldeneyeS2 for fixing OEM bloatware, NFC and releasetools script.
THANKS TO :
@squid2 for twrp
@SevenMaxs for twrp
All other users who provided support, valuable suggestions and productive comments.
Report bugs with proper logcat details.
Device is unrooted. Root using Magisk works.
Thanks
KS
Nice,happy new year!
customs on g5s incomming
Thanks, HAPPY NEW YEAR
good job my friend and thank you for your work
Happy new year .
Video recording - FIXED
FIXED another issue with MTP.
NFC selinux rules are added - SOMEONE PLEASE VERIFY IF IT WORKS.
NEW BUILD: lineage-14.1-20171231_060004-UNOFFICIAL-montana.zip
Link: Same as in topic.
Thanks
KS
Awesome work! Works fine, no bugs until right now, BUT
one thing about the moto devices that i love, is the moto actions and the moto display, how to keep them?
Have some flashable lib from stock? Can you Add or teach how to use it? I need one hand navigation on the fingerprint sensor.
Thx
Great work...i was trying for this but failed...now u can expect Oreo ROMs too
kalyansundhar said:
Video recording - FIXED
FIXED another issue with MTP.
NFC selinux rules are added - SOMEONE PLEASE VERIFY IF IT WORKS.
NEW BUILD: lineage-14.1-20171231_060004-UNOFFICIAL-montana.zip
Link: Same as in topic.
Thanks
KS
Click to expand...
Click to collapse
can u please push kernel sources...i can help fixing moto acions
Happy new year.
NFC is not working. I don't see it in the settings.
Tomorrow more time....
Anyone drop screenshots
govind1233 said:
Anyone drop screenshots
Click to expand...
Click to collapse
Tomorrow I will do. But its just lineage 14.1.
The ROM is based on the stock version. Some services are still from Motorola.
Following bug I found:
The first time you watch a full screen video. You will get a message about it. Portrait modes there is no problem but in landscape you will see a weird thing happening with the message and the video.
Thanks so much for developping a rom for this device, because not a lot a developper make something for this device contrary to the dev arround the moto g5s plus. And happy new year.
govind1233 said:
Anyone drop screenshots
Click to expand...
Click to collapse
Done.
GoldeneyeS2 said:
Tomorrow I will do. But its just lineage 14.1.
The ROM is based on the stock version. Some services are still from Motorola.
Following bug I found:
The first time you watch a full screen video. You will get a message about it. Portrait modes there is no problem but in landscape you will see a weird thing happening with the message and the video.
Click to expand...
Click to collapse
Thank you very much for making a rom for the Moto G5S. Are you aware of the bug in the developer options and Moto Actios does not work? Sorry for any mistake in English.
Doug.97 said:
Thank you very much for making a rom for the Moto G5S. Are you aware of the bug in the developer options and Moto Actios does not work? Sorry for any mistake in English.
Click to expand...
Click to collapse
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Please release kernel sources
kalyansundhar said:
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
KS
Click to expand...
Click to collapse
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
kalyansundhar said:
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Click to expand...
Click to collapse
Thanks bro
---------- Post added at 04:35 PM ---------- Previous post was at 03:35 PM ----------
kalyansundhar said:
Yes. I am aware of the issues you mentioned.
@govind1233, I have published kernel code as well https://github.com/kayesk/android_kernel_motorola_msm8937.
Can someone confirm NFC support in this device? Mine is XT1795 (India) and I don't see NFC support.
Also I have one confusion. If I add MotoActions apk to code, will it interfere with CMActions?
Thanks
KS
Click to expand...
Click to collapse
For Moto actions to work u need proper commits for cmactions
GoldeneyeS2 said:
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
Click to expand...
Click to collapse
Well, I am doing little bit here and there with whatever limited experience I have.
My main concern now is my lack of understanding on how everything fits in the big picture. And without knowing it if I make some change that shouldn't be screwing up something which works fine.
I think it is better for me to stop here, so that good developers could take it further. Anyway the repositories are public.
I cannot push system.img to github because of file size limitation. File size is 900MB and allowed limit is 100MB.
I would share it in my onedrive account and publish the link.
Bugs so far:
1) Developer options - Getting selinux permission issue which is blocked by global rule. I don't know how to override a global rule.
2) Moto Actions - Not working.
3) NFC - Getting zygote error related to seapp_context.
Code:
01-02 21:32:58.857 1534 1593 E ActivityManager: android.util.Log$TerribleFailure: Removing process that hasn't been killed: ProcessRecord{ffc4c99 8487:com.android.nfc/1027}
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.util.Log.wtf(Log.java:295)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.util.Slog.wtfStack(Slog.java:98)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.removeLruProcessLocked(ActivityManagerService.java:3419)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.processStartTimedOutLocked(ActivityManagerService.java:6611)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService.-wrap13(ActivityManagerService.java)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.am.ActivityManagerService$MainHandler.handleMessage(ActivityManagerService.java:1895)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.Handler.dispatchMessage(Handler.java:102)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.Looper.loop(Looper.java:154)
01-02 21:32:58.857 1534 1593 E ActivityManager: at android.os.HandlerThread.run(HandlerThread.java:61)
01-02 21:32:58.857 1534 1593 E ActivityManager: at com.android.server.ServiceThread.run(ServiceThread.java:46)
01-02 21:32:58.872 8500 8500 E SELinux : seapp_context_lookup: No match for app with uid 1027, seinfo default, name com.android.nfc
01-02 21:32:58.873 8500 8500 E SELinux : selinux_android_setcontext: Error setting context for app with uid 1027, seinfo default: No such file or directory
01-02 21:32:58.873 8500 8500 E Zygote : selinux_android_setcontext(1027, 0, "default", "com.android.nfc") failed
01-02 21:32:58.873 8500 8500 F art : art/runtime/jni_internal.cc:492] JNI FatalError called: frameworks/base/core/jni/com_android_internal_os_Zygote.cpp:631: selinux_android_setcontext failed
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] Runtime aborting...
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] Aborting thread:
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] "main" prio=5 tid=1 Native
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | group="" sCount=0 dsCount=0 obj=0x73784268 self=0xa5a05400
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | sysTid=555 nice=0 cgrp=default sched=0/0 handle=0xa86de534
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | state=? schedstat=( 0 0 0 ) utm=0 stm=0 core=0 HZ=100
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | stack=0xbe70f000-0xbe711000 stackSize=8MB
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] | held mutexes= "abort lock"
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] kernel: (couldn't read /proc/self/task/555/stack)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] native: (backtrace::Unwind failed for thread 555: Thread doesn't exist)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.Zygote.nativeForkAndSpecialize(Native method)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.Zygote.forkAndSpecialize(Zygote.java:95)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteConnection.runOnce(ZygoteConnection.java:225)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteInit.runSelectLoop(ZygoteInit.java:853)
01-02 21:32:58.905 8500 8500 F art : art/runtime/runtime.cc:422] at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:775)
Looks like all 3 issues boils down to selinux, file contexts, uevent permissions.
Thanks,
KS
GoldeneyeS2 said:
I have the XT1794 with NFC. I dont see the nfc in settings.
I also try to get it working.
Maybe its something with settings.apk??? Did you also copy that from the G5???
@kalyansundhar
Are now working building or still copying and pasting? you can better upload your system.img and boot.img to github(extract).
Click to expand...
Click to collapse
Uploaded boot-20180102.img and system-20180102.img to onedrive. https://1drv.ms/f/s!Ahq68S0B7zYZjmVhmIHwvYGoz3gq. Please find it within build_images subdirectory.
Thanks
KS
Hello!
I have compiled Lineage for x2. Now I'm wondering if it would be hard to port new ROM (let's say XOSP) based on trees for other one. I heard, that it's hard to port CAF-based ROM (like XOSP is) on CM trees.
AFAIR @shivatejapeddi already tried to port XOSP to x2.
Can somebody tell me if it's possible to port ROM without deeper knowledge of AOSP guts? Or, maybe, where should I begin learning AOSP build process, if it's too hard for someone inexperienced?
Thanks!
remixn said:
Hello!
I have compiled Lineage for x2. Now I'm wondering if it would be hard to port new ROM (let's say XOSP) based on trees for other one. I heard, that it's hard to port CAF-based ROM (like XOSP is) on CM trees.
AFAIR @shivatejapeddi already tried to port XOSP to x2.
Can somebody tell me if it's possible to port ROM without deeper knowledge of AOSP guts? Or, maybe, where should I begin learning AOSP build process, if it's too hard for someone inexperienced?
Thanks!
Click to expand...
Click to collapse
if you compiled los from source then there is also source for xosp ( https://github.com/XOSP-Project/manifest ) anyway there is build of xosp ( https://androidfilehost.com/?w=files&flid=185291 ) anyway when i flashed it screen was blinking and i wasnt able even use phone.
kihope12 said:
if you compiled los from source then there is also source for xosp ( [ur l]h ttps : //gi thub.com/ XOSP-Project/m anifest[/ur l] ) anyway there is build of xosp ( [ur l]h tt ps :// an droidfilehost. com/? w=files&flid=185291[/u rl] ) anyway when i flashed it screen was blinking and i wasnt able even use phone.
Click to expand...
Click to collapse
Thank you for reply!
I already know that there is a build on AFH. I also know that there are sources for XOSP. In fact, I tried to compile XOSP using several slightly modified device trees (without success). When I was lurking across @shivatejapeddi's sources on GH, I saw that there is a modified display driver. That's one of things that make me curious.
Heyyo, eh tbh from what I've seen? It's not overly too hard. Please take a look at andr68rus dirty unicorns or his Paranoid Android which are both CAF based.
There's a chance that ROM might have a different CAF display than a different ROM (prevalent right meow in 8.1 custom ROMs such as LineageOS having a lot of changes whilst OmniROM is more of a minimal approach)
OK. Just compiled the ROM.
I'm surprised, that build process took only 20 minutes on old CPU.
Now, to the point. Flashed the ROM. Doesn't boot at all. Just freezes at bootloader screen (LeEco…). Make hasn't errored at all.
So, I have no idea, what should I do now…
UPDATE:
A kind of problem with RIL, I guess?
Hmm have you tried building with -eng build instead of userdebug or user to see if you can get ADB logcat via a PC and USB cable?
If you suspect it's RIL then yeah you could always try to swap it to CAF variant and delete the device specific variant or check what other devices on xosp use
remixn said:
OK. Just compiled the ROM.
I'm surprised, that build process took only 20 minutes on old CPU.
Now, to the point. Flashed the ROM. Doesn't boot at all. Just freezes at bootloader screen (LeEco…). Make hasn't errored at all.
So, I have no idea, what should I do now…
UPDATE:
A kind of problem with RIL, I guess?
Click to expand...
Click to collapse
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
kihope12 said:
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
Click to expand...
Click to collapse
Eh from my experiences with ROMs anything can cause issues. I've gotten bootloops from sensors and Bluetooth lol
kihope12 said:
only 20 minut? that is wierd, and RIL as i know (maybe i am wrong) is about singnal and sim, i dont think it can couse no boot, and you didnt event pass oem logo, you should try re-compile it maybe.
Click to expand...
Click to collapse
After recompiling it took ~40 mins. Still stuck on OEM logo :/
remixn said:
After recompiling it took ~40 mins. Still stuck on OEM logo :/
Click to expand...
Click to collapse
what edits of device tree you did?
kihope12 said:
what edits of device tree you did?
Click to expand...
Click to collapse
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
remixn said:
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
Click to expand...
Click to collapse
Man i am not dev, i just know very basic i can atleas give you xda thread where is how build rom from source
kihope12 said:
Man i am not dev, i just know very basic i can atleas give you xda thread where is how build rom from source
Click to expand...
Click to collapse
I've read several threads already. Also, I've changed only several makefiles. Nothing directly related to programming. Anyway, I'll try to fix something, then compile it again, and again…
remixn said:
This is modified device tree: attps://github.com/remi6397/android_device_leeco_x2/tree/xosp-n-rebase
This is modified kernel: attps://github.com/remi6397/android_kernel_leeco_msm8996/tree/xosp-n-rebase
Modified LeEco vendor files are here: attps://github.com/remi6397/proprietary_vendor_leeco_x2/tree/xosp-n-rebase
Thank you!
Click to expand...
Click to collapse
Heyyo, it's the kernel. That's the AOSPA Le Pro3 kernel that is made by GalaticStryder that isn't ported to the Le Max2 yet. I tried but ran out of personal time... It would require quite a bit of work to get functional for the Le Max2. Boot DTS files, firmware, missing drivers and so on.
Also, andr68rus based ROMs are not EAS compatible just in case that's something you really want.
I'd recommend using this kernel instead:
https://github.com/1nfrag/android_kernel_leeco_msm8996/tree/bsi?files=1
Or if you want EAS based kernel I'd recommend checking out SlimRoms For EAS compatible device tree, kernel and vendor blobs.
https://github.com/slim-x2
Sorry I should have been a little more specific with my information on that first post. My bad.
Ok… I've got several errors on boot, mainly from surfaceflinger.
Log: https://pastebin.com/sXDB1u0Y
Vendor: attps://github.com/slim-x2/proprietary_vendor_leeco-2
Device tree: attps://github.com/slim-x2/android_device_leeco_x2-old
----
Now I'm trying with device: attps://github.com/slim-x2/android_device_leeco_x2 + attps://github.com/slim-x2/device_leeco_msm8996-common
I've got a compile error:
Code:
ninja: error: '/home/remi/android-buildenv/xosp/out/target/product/x2/obj_arm/SHARED_LIBRARIES/libsrsprocessing_intermediates/export_includes', needed by '/home/remi/android-buildenv/xosp/out/target/product/x2/obj_arm/SHARED_LIBRARIES/libaudioflinger_intermediates/import_includes', missing and no known rule to make it
or without SRS_TRUEMEDIA:
Code:
ninja: error: 'vendor/leeco/x2/proprietary/vendor/etc/audio_output_policy_letv.conf', needed by '/home/remi/android-buildenv/xosp/out/target/product/x2/system/vendor/etc/audio_output_policy_letv.conf', missing and no known rule to make it
Heyyo, @moto999999 can you please give him some directions as to which branches he should be using?
I better play it safe and ask him directly just to help things along
Ok. Now it boots… and almost works (it even makes a sound ). System dies leaving a huge amount of logs behind itself:
Here is an important part (IMO):
Code:
--------- beginning of crash
06-20 13:41:46.873 1629 1629 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
06-20 13:41:46.873 1629 1629 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: library "libgnsspps.so" not found
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:989)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1562)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.qualcomm.location.izatserviceprovider.service.IzatServiceBase.<clinit>(IzatServiceBase.java:199)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.Class.newInstance(Native Method)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread.handleCreateService(ActivityThread.java:3198)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread.-wrap5(ActivityThread.java)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1586)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:102)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at android.os.Looper.loop(Looper.java:154)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:378)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:232)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
06-20 13:41:46.873 1629 1629 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
So… There is a missing GPS blob (GLONASS?). I will try stealing that from some other device.
ThE_MarD said:
Heyyo, @moto999999 can you please give him some directions as to which branches he should be using?
I better play it safe and ask him directly just to help things along
Click to expand...
Click to collapse
Sure, always happy to help
remixn said:
Ok. Now it boots… and almost works (it even makes a sound ). System dies leaving a huge amount of logs behind itself:
Here is an important part (IMO):
So… There is a missing GPS blob (GLONASS?). I will try stealing that from some other device.
Click to expand...
Click to collapse
Are you trying to build nougat or oreo?
moto999999 said:
Are you trying to build nougat or oreo?
Click to expand...
Click to collapse
Nougat.
Now compiled with your slim device tree forked from LineageOS. It was a huge amount of work (never tried something like that before ) Everything I've tested so far works fine. I need to make some more tests, but maybe tomorrow.
PS: Thank you for your contributions to this device tree.
remixn said:
Nougat.
Now compiled with your slim device tree forked from LineageOS. It was a huge amount of work (never tried something like that before ) Everything I've tested so far works fine. I need to make some more tests, but maybe tomorrow.
PS: Thank you for your contributions to this device tree.
Click to expand...
Click to collapse
You should use this tree https://github.com/slim-x2/android_device_leeco_x2-old
Kernel https://github.com/moto999999/kernel_leeco_msm8996 (nougat branch)
Vendor https://github.com/slim-x2/proprietary_vendor_leeco
I don't recommend that you use my tree forked from lineage, it isn't the one I use. The forked one was just for testing
I've installed Lineage OS on the Mi MIX 4 and I cannot be happier after getting rid of MIUI, but now I'm left without a proper camera app. I installed GCAM but not everything works at the moment.
I would like to try to install the official MIUI camera app and see if by any chance it works, but I forgot to extract the apk before flashing Lineage OS.
Can someone who has MIUI installed upload the apk in this thread, or know where I can get it? For example using an extractor like this one:
Apk Extractor - Apps on Google Play
Extracts installed applications on your device and places them on your SD card.
play.google.com
Thanks a lot!
You can find the Xiaomi Camera apk on apkmirror.
Let us know if this works!
Aleksanderbjorn said:
You can find the Xiaomi Camera apk on apkmirror.
Let us know if this works!
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, it crashes on launch (I installed this one).
Stacktrace:
Spoiler: Stacktrace
Code:
2022-03-17 08:03:05.314 31800-31800/? D/MiCameraAlgo: init: E
2022-03-17 08:03:05.314 31800-31800/? D/MiCameraAlgo: init: application file path to algorithm lib: /data/user/0/com.android.camera/files
2022-03-17 08:03:05.314 31800-31800/? E/MiCamAlgoInterfaceJNI: start loading camera_algoup_jni.xiaomi
2022-03-17 08:03:05.316 31800-31800/? E/MiCamAlgoInterfaceJNI: can not load library:camera_algoup_jni.xiaomi : java.lang.UnsatisfiedLinkError: dlopen failed: library "libcamera_algoup_jni.xiaomi.so" not found
at java.lang.Runtime.loadLibrary0(Runtime.java:1087)
at java.lang.Runtime.loadLibrary0(Runtime.java:1008)
at java.lang.System.loadLibrary(System.java:1664)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.<clinit>(MiCamAlgoInterfaceJNI.java:3)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2022-03-17 08:03:05.316 31800-31800/? E/.android.camer: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
2022-03-17 08:03:05.316 31800-31800/? D/AndroidRuntime: Shutting down VM
2022-03-17 08:03:05.316 813-31855/? E/CamX: [ERROR][SENSOR ] camximagesensordata.cpp:1635 GetI2CCmdSizeForEarlySetting() EarlySettingFunc total size = 536
2022-03-17 08:03:05.316 31800-31800/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.camera, PID: 31800
java.lang.UnsatisfiedLinkError: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
2022-03-17 08:03:05.317 31800-31800/? E/CAM_CameraFCHandler: Camera FC, @Module = 163 And @CameraId = 0
2022-03-17 08:03:05.317 31800-31800/? E/CAM_MqsHelper: [K_PROCESS]: Error occur the reason is that CameraApp Mode:Photo[163] CameraId:0 Error:Java Crash
2022-03-17 08:03:05.318 31800-31800/? D/CAM_AfterSales: aftersales record not enable in this device
2022-03-17 08:03:05.318 31800-31800/? E/CAM_CameraFCHandler: Camera FC, msg=No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
java.lang.UnsatisfiedLinkError: No implementation found for int com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(java.lang.String) (tried Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init and Java_com_xiaomi_engine_MiCamAlgoInterfaceJNI_init__Ljava_lang_String_2)
at com.xiaomi.engine.MiCamAlgoInterfaceJNI.init(Native Method)
at com.xiaomi.engine.MiCameraAlgo.init(MiCameraAlgo.java:4)
at com.android.camera.LocalParallelService$LocalBinder.initMiviEngine(LocalParallelService.java:4)
at com.android.camera.LocalParallelService$LocalBinder.<init>(LocalParallelService.java:9)
at com.android.camera.LocalParallelService.onCreate(LocalParallelService.java:5)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:4186)
at android.app.ActivityThread.access$1500(ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1932)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
Looks like the apk only works on MIUI... Try ANXCamera, must be installed through Magisk or TWRP.
Aleksanderbjorn said:
Looks like the apk only works on MIUI... Try ANXCamera, must be installed through Magisk or TWRP.
Click to expand...
Click to collapse
Nice suggestion, thanks again.
I've tried the different builds for Android 11 via TWRP and all of them hang during installation, the phone is also not yet listed as officially supported.
If I manage to make it work somehow I will post it in this thread (also if I find any other good alternative).
At the moment only GCAM works, but not fully.
xatok said:
Nice suggestion, thanks again.
I've tried the different builds for Android 11 via TWRP and all of them hang during installation, the phone is also not yet listed as officially supported.
If I manage to make it work somehow I will post it in this thread (also if I find any other good alternative).
At the moment only GCAM works, but not fully.
Click to expand...
Click to collapse
I have also tried with multiple ANXCamera combinations - none work :/ It installs OK but the camera view is black