Related
As we now the fingerprint in new kernel work but not in ROM because the framework and binarys is incompitable for cyanogenmod ICS. So some months ago I started to port fingerprint in my free time and finaly I stoped to GfxEngine.apk error "Incorectly signed". At this point I undersood that there need to get correct signature or hack this verification down, and yes I made it yesterday(20.08.2013) . So now I had hacked GfxEngine.apk, FingerprintSensor.apk and incomplete framework for ICS from GB. (22.09.2013) We had gained fingerprint support on lockscreen whit some bugs need cleenup and bug reports
All sources and binarys for fp here: https://github.com/firecode95/
To clear all doubt what works for now:
Fingerprint sensor navigation
Fingerprint database managment
Fingerprint lockscreen set up
Fingerprint lockscreen finaly
Known bugs:
after instaling rom first boot makes fc on authentech apk then need to wait ~15 sec and press ok, and if framework is went down need reboot phone
if fp is enabled then after turing on phone need to relock phone with power button to activate fingerprint sensor
fingerprint lock setup setings section gives fc after setup and can't change lock methode anymore
Flashing:
Went from older build, just flash new build on top of it.
Went from other rom? Make full wipe and flash this then.
Fingerprint ROM's are located there, so want to test download latest build and if catch bug report it on this therad whit reproduction steps and logcat. Flash it on clean phone (full wipe).
Want to experiment and maybe make a bugfix for something build it yourself. Initialize android build enviroment(search in net just too many guides already) use official Cyanogenmod ICS source and add the local manifest download there, sync repo and type standart android building comands
Update (22.08.2013)
The finger lock now sets up right just settings apk crashes imediately after setup, and phone goes in soft reboot loop after locking phone because lock screen isn't finished and the new logcat, local_manifest add too + updated github.
Update (22.09.2013)
Today I am proud to say that fingerprint finaly works in cm-9 it's whit some bugs and doesn't show mesages about good or bad swipe in unlock screen but it works, need to swipe finger for 3 - 5 times(if that finger is in database it will work) the source will be available tomorow on my github acount.
Update (4.10.2013)
So I tryed to port it for JB but there is incompitability issues for GfxEngine.apk so need add fix in apk source but there comes dificult part, firs need reverse it to source (.java files) but its quiet difficult, I had decompiled many classes but some classes don't exactly 6 classes in booth apk's (fingerprintsensor.apk and GfxEngine.apk), I will try use different apk's but I think that it will not help and if someone want to help the JB (cm10.1) unfinished source will be available after 1 - 2 days in my github.
In attachment is some pics of what I got
The goal is to make ICS with fingerprint support and leater got port this to JB
And please do not ask or spam whit request when this will be merged in official Olympus kernel ICS rom because this is just a sketch and I am only kernel tester for new kernel. This thread is opened to got solution and every help will be higly evaluated.
Thanks go to @BravoMotorola for providing authentech SDK.
It's a great new! But i have a doubt, why use the frameworks from GB if we have the ones for ICS in AtrICS and works good?
douglasroos said:
It's a great new! But i have a doubt, why use the frameworks from GB if we have the ones for ICS in AtrICS and works good?
Click to expand...
Click to collapse
I will give you example. If we took the Settings.apk from AtrICS (leaked rom) the settings apk will crashes in 99,9% because they are system apk and is build with moto stuff not CM and will try to find things that doesn't exist in cm or if exist is diffrent resulting crash and and this is reason why the app hacking was already done.
Wrong Signature problem...
Thx. for your firecode, I know there were sample codes for GB laying on Atrix-Dev-Team, just too lazy to port it to cm-10.1
Anyway, you are saying 'invalid signature', i might help with this
Did you grab all the proprietaries directly from the leaked img??? i.e.
#fingerprint
bin/am2server
etc/am2server.pubkey
lib/libAuthUDMDrv_1750A100.so
lib/libam2app.so
lib/libam2server.so
app/GfxEngine.apk
app/FingerprintSensor.apk
The invalid signature will RING if you have a missigned GfxEngine.apk
E & M have extracted those proprietaries and made them available in Vendor git, BUT there are RESIGNED with testkey.pk8 for new ICS & JB platform
So you have to use the ORIGINAL GfxEngine.apk from the ORIGINAL leaked ICS img signed with Moto key
Hope you can make a JB port as well, Thx. in advance
Zn7mkUKzN1r8aCIV said:
So you have to use the ORIGINAL GfxEngine.apk from the ORIGINAL leaked ICS img signed with Moto key
Click to expand...
Click to collapse
I already used original moto GfxEngine.apk but it gived same error, the itself worked just whe thye used gfxservice class they crashed, and its no more actual because signature check is reversed now, if wrong signature apk goes right if right signature apk crashes . I think this comes up because in leak rom is apk named MotoSignatureApp.apk
Great work.
I hope you don't mind: https://github.com/CyanogenMod-Atri...mmit/fe050430b040e7cef6338433c543ae2e20fffff0
epinter said:
Great work.
I hope you don't mind: https://github.com/CyanogenMod-Atri...mmit/fe050430b040e7cef6338433c543ae2e20fffff0
Click to expand...
Click to collapse
I've tested AtrICS with new kernel, Fingerprint Sensor works good.
But I am not going to ask a dumb question like:
"Why don't you try to get it from Leaked Rom." cz ofc you already know it so I assume you cannot do such thing.:laugh:
status?
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Nd
Zn7mkUKzN1r8aCIV said:
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Click to expand...
Click to collapse
Not jet. The navigation and database administration works but finger lock screen need lot of work the resources and code itself need to be port so they looks and works like pattern lock screen. Gingerbred is quiet different lock functions and the time that need to spent for this is next problem because I am quite busy in these days.
Zn7mkUKzN1r8aCIV said:
Firecode, is your github code completed for ics (navigation & fingerperint)? am planning to use in cm-10.1, Thx.
Click to expand...
Click to collapse
I though epinter already included this stuff in the cm-10.1 repo?
ravilov said:
I though epinter already included this stuff in the cm-10.1 repo?
Click to expand...
Click to collapse
They just included hacked apk's but not android core framework for fingerprint, in my pc is scrach for cm10.1 but there thing go in new level from just dedicated lock screens they are converted to lock widgets and source for it is took from ics so to build cm10.1 from ginger fp code first need to make ics code.
I just posted this to cm10.1's thread, but i think it fits here as well
https://www.youtube.com/watch?v=eZUSBCZZA6c
Thanks firecode95 for your hard work!
Sent from my MB860 using xda app-developers app
andresrivas said:
I just posted this to cm10.1's thread, but i think it fits here as well
https://www.youtube.com/watch?v=eZUSBCZZA6c
Thanks firecode95 for your hard work!
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
nice i installed it but my fingerprint sensor refuses to work at times... i seriously dont know why :/ it works well while charging mostly but after i unplug it no response
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
Take into consideration that those are GB libs hacked to work on a OS 3 releases above, like triying to run win 98/me drivers on windows 7
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
Forget jcrahul message, I think your answer is here:
firecode95 said:
Not jet. The navigation and database administration works but finger lock screen need lot of work the resources and code itself need to be port so they looks and works like pattern lock screen. Gingerbred is quiet different lock functions and the time that need to spent for this is next problem because I am quite busy in these days.
Click to expand...
Click to collapse
Fingerprint naviguation: OK
Fingerprint lockscreen: needs lot of work because "resources and code need to be ported"
I know it but leaked ics framework isn't working properly, IF the ported libs n framework don't work properly either, that may means the problem is on newer versions of Android and their hardware management
johnannis said:
So the problem with not responding sensor isn't solved by using the ported libs? It was my last hope for a properly working fingerprint sensor
Click to expand...
Click to collapse
How do you mean not responding fp sensor? The seansor works fully just need lot of work in fp source integration for lock screen. And in leak rom isn't any problems with fp. If you had problems it culd be due hardware, try change fp sensor.
P.S
I think that I litle misunderstood you and this is more for @jcrahul
I realy need development account acces for authentech or documentation with SDK's for fingerprint, it's most important for now, because just trying figure out from code how all works is hard and time compsuming process. So please anyone who has this try to give a helping finger
Hmm, so you say that this not responding issue doesn't affect your device?
In mine this issue really exists and on some others too. It's like you don't even swipe your finger. And it happens as said above, when it shows up the only way to stop it is to plug in the charger, and most of the times after next deepsleep it shows up again.
For example, one day I tried using fp and worked well from the morning till the afternoon (when I got home to charge it). But after removing the charger it showed up.
I think I had go back to GB to test it but I ll do it again.
EDIT: So I went back to GB rom. Unlikely for my ATRIX but likely for the project the issue is still here. So it must be hardware related,I ll sent it for service (its still in warranty )
Update
The ROM manifest and source updated. The testing can start now and if found a bug please repot it
Here is the Discussion thread for SM T110 Kernel Port, suspended temporally as few files need to be written from scratch.
Will start after my exams
RULES
1. Please use tags.
[ANS] for answer
[OTH] for others
2. Please quote properly
3. Please don't post unnecessarily
These rules are set just to keep the development area clear.
Notice:
Seems like we will have to port only Display driver, camera driver and the Shared memory driver
Developers who wants to help leave a comment here with green text as " HELP "
thanks god blessed you
Good job if you need help i will always try it
But keep in mind i am not that good in kernels
Hello!
How about this program?
We haven't got a Cm Rom yet.
Stock Rom is too boring.
This one makes no sense anymore we have a working T110 port
[OTH] OTG support will be available ?
Waiting your return. I need a custom kernel in my tab. Thanks
Enviado de meu SM-T110 usando Tapatalk
You could include OTG support?
If you could include whether the driver of the usb modem zte whether type of orange?
Would be great if possible as we could have in our tablet 3g usb modem connecting an application using pppwiget
hello .
is there anybody that has baked a working kernel for the T110 so i can configure the governuer mode or is this Modell out of date ?!? im asking coz i have a very hot table. so hot that the touch is not properly working.
restinpeace said:
hello .
is there anybody that has baked a working kernel for the T110 so i can configure the governuer mode or is this Modell out of date ?!? im asking coz i have a very hot table. so hot that the touch is not properly working.
Click to expand...
Click to collapse
Root your tab and install the trickster Mode.app. With this app you can change the Governore to conservative and Scheduler to cfg or noop.
Take a look to this post
http://forum.xda-developers.com/showpost.php?p=50833415&postcount=426
dead
this project is presumed dead.
it is not even tagged "T110". Also the OP did not state from where towards where he intended to port.
R.I.P. , kernel !
I have tried existenz 6.5.0 which is android 4.3 . Is it possible to port z2 stock to our z and does it require a locked bootloader?. Just to get 4.4
Sent from my C6603 using Tapatalk
pjgowtham said:
I have tried existenz 6.5.0 which is android 4.3 . Is it possible to port z2 stock to our z and does it require a locked bootloader?. Just to get 4.4
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Impossible as Z2 has different chipset
And for now if we want to use Android 4.4,we will need to unlock bootloader
You have to wait for a signed Kernel from Sony.
Gesendet von meinem C6603 mit Tapatalk
Unlock the bootloader and what modifications are necessary to port it?. If anyone can teach me dev things i ll be greatful . Need a teacher to teach me. @spyfly @Ben Ling And porting the z2 kernel to z is possible?
pjgowtham said:
Unlock the bootloader and what modifications are necessary to port it?. If anyone can teach me dev things i ll be greatful . Need a teacher to teach me. @spyfly @Ben Ling And porting the z2 kernel to z is possible?
Click to expand...
Click to collapse
i'm not very sure as i don't modify kernel or build ROM
as i know there is no way to port a different hardware kernel to a different hardware device
Ben Ling said:
i'm not very sure as i don't modify kernel or build ROM
as i know there is no way to port a different hardware kernel to a different hardware device
Click to expand...
Click to collapse
Porting Kitkat certainly requires Unlocked bootloader as Ben Ling said.. And for porting, you need to download kernel sources from Z2's latest build.. And also Kernel sources of our XZ's 4.3 and compile a kernel.. You've to mod ramdisk and replace drivers of Z2 with our XZ's.. And try.. There are lots of changes to be made in the ramdisk.. Its like 30000 lines of coding, hence no one tries porting fw's.. Instead they port the apps individually because its easier..
tOrNadO™ said:
Porting Kitkat certainly requires Unlocked bootloader as Ben Ling said.. And for porting, you need to download kernel sources from Z2's latest build.. And also Kernel sources of our XZ's 4.3 and compile a kernel.. You've to mod ramdisk and replace drivers of Z2 with our XZ's.. And try.. There are lots of changes to be made in the ramdisk.. Its like 30000 lines of coding, hence no one tries porting fw's.. Instead they port the apps individually because its easier..
Click to expand...
Click to collapse
Haha. I would wait for one more month to get 4.4 instead. I was tryinf to learn something outa this mainly, I was bored. I have some unanswered questions
When I decrypted kernel.sin, I got a kernel.elf file then I got 2 .elf files and a ramdisk.tar.gz. how do I compare it with boot.img files which come in the other custom Roms? Is there any way to breakdown elf files into files like boot.img?
I dont know the meanings of folders. I know whats app,framework,fonts folders but whats tts,usr,vendor,lib,bin and what all contain drivers/need to be replaced basically ? Hope drivers is the right word..
Sent from my C6603 using Tapatalk
pjgowtham said:
Haha. I would wait for one more month to get 4.4 instead. I was tryinf to learn something outa this mainly, I was bored. I have some unanswered questions
When I decrypted kernel.sin, I got a kernel.elf file then I got 2 .elf files and a ramdisk.tar.gz. how do I compare it with boot.img files which come in the other custom Roms? Is there any way to breakdown elf files into files like boot.img?
I dont know the meanings of folders. I know whats app,framework,fonts folders but whats tts,usr,vendor,lib,bin and what all contain drivers/need to be replaced basically ? Hope drivers is the right word..
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
For all Xperia devices after 2012, kernel.sin or kernel.elf has to be renamed to boot.img and then extract using a tool from letama.. Google it.. U will find a lot of answers.. For XDA devs to learn, Google Search is the most important thing.. Use it to clear all your doubts.. Even the tiniest things are easily searchable in Google.. So use it as much as u can.. U will find all the answers.. Although not for some deep things inside the kernel, but still enough to learn about development.. And yes drivers is the right word.. It includes display drivers, audio blobs, camera blobs, wifi modules, bluetooth and wifi related drivers and battery management as well..
Nah im bored Of that update its should be updated from the first day of march
Hi. I would create a ROM for Samsung galaxy grand prime g531f. Cianogenmod not give you support and I'm reading a lot lately about how. Use Windows and Ubuntu. And I find manuals are old. I you could lend a hand or give links to manuals? ? do not know if Android 5.1 to 6 or recommend me? And as you do?
Enviado desde mi SM-G531F mediante Tapatalk
Thaxx for starting porting cm12 or 13 do it fast bro
@chaudharyjatin115 Don't rush him!
@linusin87 The worst part at porting is making the vendor tree which I'm unable to do so porting for me is off limits. I wish I could help but I don't understand the vendor tree thingy
Hola como es una ardua labor he abierto un hilo en HTC manía donde voy poniendo todos mis avances. http://www.htcmania.com/showthread.php?t=1196428
Enviado desde mi SM-G531F mediante Tapatalk
Any good news?
I have readed your HTC mania page I think you are near to port cm12
can you use twrp device tree for building cm
Sent from my SM-G531F using Tapatalk
---------- Post added at 12:06 PM ---------- Previous post was at 12:05 PM ----------
The device tree is here https://github.com/TeamWin/android_device_samsung_grandprimevelte?_e_pi_=7,PAGE_ID10,4857405931
Sent from my SM-G531F using Tapatalk
http://source.android.com/source for building device tree the source code is here http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=G531F
Any good news
Sent from my SM-G531F using Tapatalk
Any good news?
any news, bro?
Guy's, stop asking for news and updates, it is against XDA rules.
And it's incredibly rude.
Hey, I have built a custom kernel for the G531F, I only managed to set SELinux to permissive, that's something. But our biggest enemy is the FRP lock, which gets enabled after adding a Google account, and blocks any custom kernel. There's no way to turn it off. I can upload the kernel source to GitHub if you want.
dadziokPL said:
Hey, I have built a custom kernel for the G531F, I only managed to set SELinux to permissive, that's something. But our biggest enemy is the FRP lock, which gets enabled after adding a Google account, and blocks any custom kernel. There's no way to turn it off. I can upload the kernel source to GitHub if you want.
Click to expand...
Click to collapse
Tick OEM unlock, delete Google account and disable lock screen patern. Then it's off.
playitlouder said:
Tick OEM unlock, delete Google account and disable lock screen patern. Then it's off.
Click to expand...
Click to collapse
Yeah, How am I supposed to use it without a Google account? That's a no-go for me
dadziokPL said:
Yeah, How am I supposed to use it without a Google account? That's a no-go for me
Click to expand...
Click to collapse
You only need to live without an Google account, until you build a kernel that doesn't enforce the Factory Unlock Protection
playitlouder said:
You only need to live without an Google account, until you build a kernel that doesn't enforce the Factory Unlock Protection
Click to expand...
Click to collapse
I've looked around kernel files and configs, and there seems to be nothing about FRP. Maybe it's not managed by the kernel, but by the bootloader, which has no source code.
dadziokPL said:
I've looked around kernel files and configs, and there seems to be nothing about FRP. Maybe it's not managed by the kernel, but by the bootloader, which has no source code.
Click to expand...
Click to collapse
There are people who have done it
http://forum.xda-developers.com/ver...p-factory-reset-protect-unlock-t3414590/page6
There has to be a piece of codes that sets the bit in the bootloader, probably with root permissions.
dadziokPL said:
Hey, I have built a custom kernel for the G531F, I only managed to set SELinux to permissive, that's something. But our biggest enemy is the FRP lock, which gets enabled after adding a Google account, and blocks any custom kernel. There's no way to turn it off. I can upload the kernel source to GitHub if you want.
Click to expand...
Click to collapse
Please upload it so the other developers can now create cm 12.1 for our variant
---------- Post added at 02:47 AM ---------- Previous post was at 02:46 AM ----------
Any good news?
I Got Answer
dadziokPL said:
Hey, I have built a custom kernel for the G531F, I only managed to set SELinux to permissive, that's something. But our biggest enemy is the FRP lock, which gets enabled after adding a Google account, and blocks any custom kernel. There's no way to turn it off. I can upload the kernel source to GitHub if you want.
Click to expand...
Click to collapse
Jestem Z Polski Zobacz Moj Post [Guide] How to disable FRP Lock Re-enabling after adding google account
Po angielsku ale pomocne
Wymagania to Root, dziala na kazdym urzadzeniu z google play services
Hello everybody!
here's my problem:
I'm running MIUI Global 10.2.13 (rooted and with xposed framework installed) on my MI9 and I would like to keep my phone unlocked when connected to my car radio. Well, I can only add Xiaomi stuff as trusted devices, i.e. I can use my Amazfit watch to unlock the phone but not the the car radio even if is correctly connected.
Searching in XDA or googling didn't helped so much, according to the thread on official MIUI forum (http://en.miui.com/thread-1332307-1-1.html) this is a normal behaviour for Xiaomi stock rom and someone suggested the use of some xposed module to correct it
So my question is: there's a way to add non xiaomi bluetooth device to the trusted device list? could someone point me to that "mighty" xposed module?
thanks a lot to the whole community!
The only way I know it's too get away from MIUI Rom. One of the reasons I unlocked and installed Lineage on my old Mi5S and will probably do on my new Mi9 soon.
Sent from my MI 9 using Tapatalk
Thanks for the suggestion templeka: I've been there before, installed Pixel Experience, AEX, even the early beta of android Q: they all look very promising but still at early stages: none of them can achieve the smoothness of the stock fingerprint unlock and none of them have the "ok google" working, as far as I know.
I'm looking for a temporary workaround until the our Great Masters of Android (thanks a lot for your hard work!) get this beast at their feet!
I would suggest using the "Feedback" app to report this.
If there is any chance of them listening to someone is doing so to the people that bought the phone and are not pleased with something.
don't really believe they roam forums and such to gather information.
According to the thread on official forum I've reported in OP, Xiaomi seem to consider this not as a bug but as a Feature (!) so, I didn't tried to report to them.
Anyway thank you for your interest and support!
Looking for the same thing! I also prefer to stay on stock. There is a way to do this with Xposed but I'm not sure it's working anymore... I use Xiaomi.eu ROM. Might be something they can patch on their end maybe?
I wanted that feature is well, but then I saw that mi9 is lacking pocket mode feature, so keep the device unlock in my pocket resulted in calling unwanted people.
So instead I choose to unlock using face, pattern and fingerprint.
dualcaliber said:
So my question is: there's a way to add non xiaomi bluetooth device to the trusted device list? could someone point me to that "mighty" xposed module?
thanks a lot to the whole community!
Click to expand...
Click to collapse
This module name is CustoMIUIzer and you can find it on XDA. This is powerful module with a lot of options and one of them is "unlock phone by bluetooth device" - working very good.
Lashe said:
This module name is CustoMIUIzer and you can find it on XDA. This is powerful module with a lot of options and one of them is "unlock phone by bluetooth device" - working very good.
Click to expand...
Click to collapse
Thank you very much man! you solved my problem!
What if I tell you I've got that module installed but never seen the option you've pointed me to?
the full path to the setting is:
custoMIUIzer > system > lock screen > Disable screen lock:
here toggle "Enable mod" on, then under "Disable screen lock" select "Disable on trusted network/devices:
go back and under "Trusted bluetooth devices" select the device you want to unlock the phone.
thank you all again and special thanks @Lashe: never underestimate junior members!:good::good:
in miui 11 eea, it unlocks me but every time I go into configuration, the xposed module gives me an error
Hi, same thing here on mi9 lite. Very annoying this setting from Mi
I encourage users to submit a feedback request to Xiaomi asking for the functionality to be extended to non-Xiaomi bluetooth devices.
Mi11 5g + Mi Watch dont work either. Submitted feedback. It finds my old mi band ok, not mi watch. Beyond annoying on a phone with unreliable under screen fingerprint reader
seems insane to me that they dont allow Bluetooth unlock on third party Bluetooth devices on their global ROMs when most of their Bluetooth devices like Mi watch dont have global roms so some of the functionality does not work outside of china.
dualcaliber said:
Thank you very much man! you solved my problem!
What if I tell you I've got that module installed but never seen the option you've pointed me to?
the full path to the setting is:
custoMIUIzer > system > lock screen > Disable screen lock:
here toggle "Enable mod" on, then under "Disable screen lock" select "Disable on trusted network/devices:
go back and under "Trusted bluetooth devices" select the device you want to unlock the phone.
thank you all again and special thanks @Lashe: never underestimate junior members!:good::good:
Click to expand...
Click to collapse
Hi, After pretty hardwork i have managed to install customiuizer(for miui13) for my Mi 11x running on MIUI13. But it does not fetch any bluetooth device. Any help will be appreciated.
Updated: Toggled "enable module" in Lsposed, rebooted and it worked.
Hello everyone,
can someone help a noobie ?
I've a Xiaomi Mi 11 ultra and want to use my garmin venu 2+ on it, but the smart lock is very unuseful with MIUI. You're comment gives me hope
I'm on MIUI14 (android 13).
If i understant correctly, i have to :
- root my phone with magisk => I found this thread
Root Mi 11 Ultra
Want to confirm before proceeding, I find this instruction. https://www.ytechb.com/how-to-root-mi-11-ultra-and-unlock-bootloader/ I've already unlocked the bootloader, want to make sure it is safe to do so (won't brick etc)
forum.xda-developers.com
- Install (ED)Xposed
- Install CustoMIUIser
- Configure them both with correct settings for the smart lock
But it seems that (Ed)Xposed is for android 11
I've found that for Android 13 (Xposed only)
[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+
This is a mixed Xposed+Magisk module, which is made to allow customizations that are not originally designed in AOSP (Android Open Source Project). Features: Currently, AOSP Mods offers customizations on different aspects of system framework and...
forum.xda-developers.com
Can it works ?
Is it very different from (ED)Xposed ? => same options ?
Or Do I try with the (ED)Xposed even if it doesn't "fit" with android 13 ? => seems risky for me
Or Do I wait some months (Ed)Xposed update for compatiblity with Android 13 ?
Thanks in advance for your answers
Best Regards
Fabrice
NB : hope my english is not so bad...
Old EdXposed causes many problems with new Magisk - use Zygisk-LSposed module instead
And CustoMIUIzer14 for MIUI 13 and 14- SmartLock with BT and WiFi works perfectly:
GitHub - MonwF/customiuizer: customiuizer14(米客)
customiuizer14(米客). Contribute to MonwF/customiuizer development by creating an account on GitHub.
github.com
Thanks for your help zgfg !!
I've "successfully" install Zygisk but when I run magisk, it says "Module suspended because Zygisk is not active"
How I do turn it active ??
pitchoun401 said:
Thanks for your help zgfg !!
I've "successfully" install Zygisk but when I run magisk, it says "Module suspended because Zygisk is not active"
How I do turn it active ??
Click to expand...
Click to collapse
I've found it myself in the settings of magisk...sorry for the question
EDIT :
It works finally !! but it take at least 10 seconds to my watch to launch google assistant. That's better than nothing
Thanks a lot for you help guys !!
EDIT 2 : last questions : since the double installation, all menu systems (contacts, agendas, phonecall...) are in red (fonts and background in dark-red). I've tried to change the themes but nothing change. I've tried in the MIUI menu but there's nothing. Is it because of Magisk ? Lsposed ? CustoMIUIzer ? Where can i change this parameter ? Thanks !!
EDIT 3 : finally it was a theme pb... sorry for borring you guys...