Related
Hello,
I've been trying to create a widget, and i've been using my phone to do the testing.
For some reason the phone keeps rembering an old version of the widget.
I uninstall the widget every time i re-deploy it but it still remembers the old one.
the only way i've found to get it to work is to change the package name and then install it and then it works fine.
Anybody else come across this issue ? or dose any body know how to stop this from happening ?
bobs79 said:
Hello,
I've been trying to create a widget, and i've been using my phone to do the testing.
For some reason the phone keeps rembering an old version of the widget.
I uninstall the widget every time i re-deploy it but it still remembers the old one.
the only way i've found to get it to work is to change the package name and then install it and then it works fine.
Anybody else come across this issue ? or dose any body know how to stop this from happening ?
Click to expand...
Click to collapse
Don't know if this if any help but worth trying:
I've had problems like yours when I had a multiuser setup. Uninstalling my developped app that was installed signed with the debug keystore didn't really uninstall: Playstore couldn't install the officially signed variant that was on the playstore, even though I unstalled the test app.
The only way to properly uninstall the test-app and allow the playstore to install the official one was:
Code:
adb uninstall my.package.name
. Uninstalling from the phones settings-apps-uninstall appearently was not a full uninstall
Yes, @Zatta is right. It is no full install. However, you can do that from the settings app:
Use the first user you have created when you got your phone. Then open the settings of the app. In the action bar there should be an icon. If you click it, there should be an option to uninstall it for all users.
nikwen said:
Yes, @Zatta is right. It is no full install. However, you can do that from the settings app:
Use the first user you have created when you got your phone. Then open the settings of the app. In the action bar there should be an icon. If you click it, there should be an option to uninstall it for all users.
Click to expand...
Click to collapse
unforchantly this isnt the case for me, i dont have a multi profile set up. It is really strange tho.
But implimenting the pageange name each time is annoying.
could it be somthing to do with eclipse ? is there an altertive compiler i could use ?
any suggests are welcome
Did you try uninstalling with adb? Do you van any reminants in /data/data?
is your app still present in the PackageManager?:
Code:
PackageManager mPm;
List apps = mPm.getInstalledApplications(PackageManager.GET_UNINSTALLED_PACKAGES | PackageManager.GET_DISABLED_COMPONENTS);
If you are rooted, there will also be the method to uninstall it in an adb shell or in Terminal emulator:
Code:
su
pm uninstall <package>
Just wanted to mention that the official Android L launcher works on our Tabs
I have attached the .apk
You have to change the build.prop to get the new UI
set ro.build.version.codename to L and reboot
It works also as a system app, no FC's.
Supports 4.2.2 / 4.3 / 4.4.2
Note: You have to update/download the latest Google Search app and Google Mail may force closing
Proceed with caution, you may end up having boot-loops !
Thanks go to:
@ivan123
@Ashutos1997
thanks
good to know, thanks!
Not quite...
UA,
hi i would ask that you amend your post to mention this launcher requires google search to be functional.
As per your instructions I did so and the launcher does not register as system app without google search,
and on regular install call for updated google search to function.
thank you for reading.
m
moonbutt74 said:
UA,
hi i would ask that you amend your post to mention this launcher requires google search to be functional.
As per your instructions I did so and the launcher does not register as system app without google search,
and on regular install call for updated google search to function.
thank you for reading.
m
Click to expand...
Click to collapse
Thanks,
I have added this information
Works perfectly!
notice
UAdeveloper said:
Just wanted to mention that the official Android L launcher works on our Tabs
I have attached the .apk
You have to change the build.prop to get the new UI
set ro.build.version.codename to L and reboot
It works also as a system app, no FC's.
Note: You have to update/download the latest Google Search app
Thanks go to:
@ivan123
@Ashutos1997
Click to expand...
Click to collapse
Hi I noticed after doing this sometimes gmail would force close untell I reboot
dsilx said:
Hi I noticed after doing this sometimes gmail would force close untell I reboot
Click to expand...
Click to collapse
Thank you for that information. (This problem appears on my tab, too)
UAdeveloper said:
Thanks,
I have added this information
Click to expand...
Click to collapse
Doesnt work for me, it just keeps rebooting.
Im running the latest version of Nolekat.
DuceTheTruth said:
Doesnt work for me, it just keeps rebooting.
Im running the latest version of Nolekat.
Click to expand...
Click to collapse
Did you first download the latest Google search app ?
Screenshots?
F1Fanatic27 said:
Screenshots?
Click to expand...
Click to collapse
Good idea,
will post them on friday.
UAdeveloper said:
Just wanted to mention that the official Android L launcher works on our Tabs
I have attached the .apk
You have to change the build.prop to get the new UI
set ro.build.version.codename to L and reboot
It works also as a system app, no FC's.
Supports 4.2.2 / 4.3 / 4.4.2
Note: You have to update/download the latest Google Search app and Google Mail may force closing
Thanks go to:
@ivan123
@Ashutos1997
Click to expand...
Click to collapse
When you say, "set it to L", you ARE referring to the property value under where it says ro.build.etc.... correct?
jonstowe78 said:
When you say, "set it to L", you ARE referring to the property value under where it says ro.build.etc.... correct?
Click to expand...
Click to collapse
Yes, you have to set the value for ro.build.version.codename to the letter L.
PHP:
ro.build.version.codename=L
I've installed this apk, changed the build.prop, and after a reboot, the tab just keeps rebooting every time it starts a system. i cant get to do anything, it just reboots again and again... help??? :S
crnjaz said:
I've installed this apk, changed the build.prop, and after a reboot, the tab just keeps rebooting every time it starts a system. i cant get to do anything, it just reboots again and again... help??? :S
Click to expand...
Click to collapse
What device do you have?
What Android is it running?
Did you deinstall, Touchwiz (Samsung stock) launcher?
Did you set the launcher as a system app?
UAdeveloper said:
What device do you have?
What Android is it running?
Did you deinstall, Touchwiz (Samsung stock) launcher?
Did you set the launcher as a system app?
Click to expand...
Click to collapse
gt-5200, 4.4.2 deodexed stock...
No i did not, i just installed given apk (it updated current google now launcher), and changed build.prop
anyway, i tryed to fix premisions, and delete the google launcher from the app folder from recovery, but still rebooting continued.
and while trying to fix the build.prop from the recovery, i funked the system a bit, so a reflashed the whole rom again, so I'm back at the begining... (no new launcher, but tab works fine...)
crnjaz said:
gt-5200, 4.4.2 deodexed stock...
No i did not, i just installed given apk (it updated current google now launcher), and changed build.prop
anyway, i tryed to fix premisions, and delete the google launcher from the app folder from recovery, but still rebooting continued.
and while trying to fix the build.prop from the recovery, i funked the system a bit, so a reflashed the whole rom again, so I'm back at the begining... (no new launcher, but tab works fine...)
Click to expand...
Click to collapse
It seems like, you screwed up inside the build.prop
Or, it only works as a system app on 4.4.2, that would be bad.
I will check that, thank you for trying and sorry if you got any problems because of me.
UAdeveloper said:
It seems like, you screwed up inside the build.prop
Or, it only works as a system app on 4.4.2, that would be bad.
I will check that, thank you for trying and sorry if you got any problems because of me.
Click to expand...
Click to collapse
well, i used root explorer to edit build.prop, and i didnt change anything except switch REL with L...
but i guess build.prop was screwed somehow, it managed to stay on for a while before the reboot a few times (for about half a minute), but it kept giving the fc error screens for play services, mail, etc, and then restarted again.
I will try it in a few minutes!
UAdeveloper said:
Yes, you have to set the value for ro.build.version.codename to the letter L.
PHP:
ro.build.version.codename=L
Click to expand...
Click to collapse
When first time I installed this launcher I changed the build.prob as u said....
And after a week I came to know that gmail is get fc's every time
I saw the log of gmail and came to know that the changes made in the build.prob coz of that gmail app getting fc...
Then I changed it to og value in build.prob
From then everything is working totally fine
So I don't think that we should change the codename, without changing it everything is working fine...even gmail app
Sent from my SM-T311 using XDA Free mobile app
Hello to everyone,
as promised in my old thread, here is a first version of the automatic script to replace the launcher.
For now, firelauncher will be replaced with cyanogenmod's trebuchet.
If you want to use a different launcher, just replace the apk in the folder. (Remember to rename your new file to trebuchet.apk.)
No root is required for this to work.
This will not work with regular updates to 5.1.1!
Only for those who kept the old bootloader.
I will update the script to work with 5.1.1 later today
Remember to enable usb-debugging before running the script and make sure your PC is authorized.
There are automatic delays in the script, but check the necessary points when asked to do so, because boot-time can be really long sometimes.
As no one complained about the original script, I do believe that the basic steps are working properly.
However: I'm not responsible if anything goes wrong, please keep that in mind.
Credits go to @csolanol for finding root, @Awesomeslayerg for summing up the manual steps (If you don't like scripts, just take a look at his thread, it's good too), and to all those other people that were involved in working on boot.img and root.
Trebuchet is a cyanogenmod app, please refer to their website and xda-posts for further information.
Changelog:
V1.1:
Added some automatic delays and reduced the "pause"-commands, runs with a little less user-interaction.
Let's sum it up as more one.click.
V1.0:
Initial release
Planned features:
Allow the user to choose between trebuchet and any other launcher he copies into a special folder.
Make it easier, more documentation, clean up
Thanks for the package could come in handy for me with my daughters fire I did mine the longer way
Sent from my HTC One_M8 using Tapatalk
Okay good, should work for you as you already know the steps
If anything goes wrong booting the boot-firelauncher.img again and copying firelauncher.apk back in place will fix it.
But that should only be needed if connection is lost or any other unusual thing happens.
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
cryophil said:
Hi, I'm new here. How can you write to the system folder and replace/rename a system launcher APK without root? I will try this on my fresh Ford running 5.0.1 later tonight.
Click to expand...
Click to collapse
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Vlasp said:
With a custom boot.img that makes the system r/w.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
cryophil said:
Thanks. If I use the custom boot.img to replace the launcher, Can I later recover my factory/standard tablet setup by erasing and resetting in the settings? Does the custom boot.img change the tablet permanently?
Click to expand...
Click to collapse
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Vlasp said:
You can reset it, by just ADB sideloading the firmware.bin through recovery. The custom Boot.img is temporary and only lasts for 1 boot, and will reset after you reboot.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
No problem, and good luck!
Sent from my KFFOWI using Tapatalk
cryophil said:
Ah, okay. I think I am learning. I read that a boot.img was also used to root the device. I assumed that changes were permanent. I think the difference is, the changes made after the boot.img can be made permanent using SU/root. But in this launcher replacement case, it is just a boot difference for that one boot-up.
It's a great way to test if I like the setup, then if so, I can root and change to that launcher/setup permanently using the root method discovered last weekend.
Thank you very much to all involved. I bought the five-pack+1 to give as gifts for the holidays, anticipating that developers would root and hack. I probably don't even need a custom recovery/boot-loader. Just being able to permanently replace the launcher and getting around the Firelauncher is good enough for my gift recipients.
Thanks mucho!
Click to expand...
Click to collapse
Just to clarify, for the launcher replacement, the boot.img is used just to make the system partition r/w so that the changes can be made to replace the launcher. So the r/w mounting of the system partition will only last for that one boot, but the replacement of the launcher will be "permanent," in that it will persist after reboot. The rooting procedure uses the same method to copy the necessary su binaries to the device and set permissions.
So if you follow this procedure for replacing the launcher, it will be permanent with no need to then also root the device in order to make it permanent. Of course, you can also then root the device if you want, but you don't need to in order to replace the launcher.
Will the home button work after running this? I had read in some other threads about replacing the home screen messing up the home button.
Yes, the home button will work after using this.
Even widgets should work.
Maybe I'm missing something, but I don't see the script anywhere.
Was due to updating, you can find the new version 1.1 in the first post.
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Enviado desde mi KFFOWI mediante Tapatalk
Darkside1984 said:
I replace firelauncher by Google Now as default launcher with the script posted in this forum. Could it be a problem for your Trebuchet script?
Click to expand...
Click to collapse
So you want to replace the trebuchet.apk with google now launcher and use that as your default?
If you rename your apk file to trebuchet.apk that will work.
But google now launcher is reported to be rather unstable as default one somewhere else in this forum, so it might be a better idea to install trebuchet using the script and then google now launcher from play store.
That should allow you to choose between the two and set now launcher as default one, but with a fallback to trebuchet.
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
below seems to be "USER ERROR"
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
a1yet said:
Live wallpaper does not work
example
https://play.google.com/store/apps/details?id=com.style_7.analogclocklivewallpaper_7&hl=en
starts to open then crashes
....................................................................
videos in google play-store dont work gives error
"The requested action is not permitted. check Parental controls settings and retry"
example
https://play.google.com/store/apps/details?id=ch.bitspin.timely&hl=en
.
Click to expand...
Click to collapse
I can confirm the first issue, but it also exists if you replace the launcher manually (as I did), will look at were it comes from tomorrow.
The second one appears like you ran pm hide on the default video player and should not be related to the script.
ChrBeck said:
you ran pm hide on the default video player
Click to expand...
Click to collapse
thank you
i installed VLC after hide should it not use it as my default video player ?
or do i have to unhide the default one ?
All credit goes to @brianelv and @FaserF
https://goo.gl/seMFLJ
I only used the manual edits to the build prop on my Nexus 9 16GB Wifi and I have not checked the flashable zips (try at your own risk)
Requirements:
-must be running 7.0+
-must be rooted
-Google app version should be at least 6.5.35.21 or newer
How-to:
-Back up your build.prop
-Add the following line to your build prop
Code:
ro.opa.eligible_device=true
Replace the following in your build.prop
Code:
ro.product.model=Nexus 9
by
Code:
ro.product.model=Pixel
-Save your edited build.prop
-Go to Settings>Apps>Google App>Storage click on "Manage Space", click on "Clear All Data"
Reboot in Recovery (TWRP) Choose Wipe>Advanced Wipe select Wipe "Cache" and "Dalvik/ART Cache"
Reboot System
Profit!
You should now have a fully working Google Assistant! Set it up by pressing and holding the "home" button
Thanks for the heads up that it works on the N9!
A word for anyone else trying it: after following the instructions, it seemed to not work. I waited 15 minutes or so, tried again, and it launched the Assistant.
borxnx said:
Thanks for the heads up that it works on the N9!
A word for anyone else trying it: after following the instructions, it seemed to not work. I waited 15 minutes or so, tried again, and it launched the Assistant.
Click to expand...
Click to collapse
What launcher are you using?
Google Now/Experience or whatever. Not Pixel
Sent from my XT1575 using Tapatalk
Got things working on Marshmallow PureNexus
How do you edit build.prop? I tried manually editing the text of the file within Amaze file manager, but it always reverts back to the original. I even tried saving an alternate and deleting the original and it won't work...
fredsbassett said:
How do you edit build.prop? I tried manually editing the text of the file within Amaze file manager, but it always reverts back to the original. I even tried saving an alternate and deleting the original and it won't work...
Click to expand...
Click to collapse
Be sure you are using a file manager that has root access enabled. It sounds like when you try to edit the file it's just not editing, which could be because it doesn't have root permission. Also be sure you click "Save". I used Solid Explorer and it worked no problem.
borxnx said:
Be sure you are using a file manager that has root access enabled. It sounds like when you try to edit the file it's just not editing, which could be because it doesn't have root permission. Also be sure you click "Save". I used Solid Explorer and it worked no problem.
Click to expand...
Click to collapse
I used two other file explorers (both with root access) and even tried pushing the file with adb and it didn't work, but Solid Explorer worked. Thanks!
Just got it working without changing the Model name. Stock 7.1.1
corkiejp said:
Just got it working without changing the Model name. Stock 7.1.1
Click to expand...
Click to collapse
Nice!
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
I'm glad you got it working!
borxnx said:
Nice!
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
I'm glad you got it working!
Click to expand...
Click to collapse
Yes I'm aware, but it is only been activated in limited countries. I'm in Ireland. I got it working on my Redmi Note 3 (Kenzo) by using a US VPN. The same trick didn't work for the Nexus 9, but using "ro.opa.eligible_device=true" activated it on that.
borxnx said:
Did you know that the Google Assistant is now officially available on any Android device running Marshmallow and up, and it has been for like a week now?
Click to expand...
Click to collapse
Phones only, not tablets.
Google confirms to us that the wider Assistant rollout will not reach tablets.
So the only way to activate it on the Nexus 9, is to use "ro.opa.eligible_device=true"!
SOME OF THIS MIGHT BE A BIT OUTDATED.
I haven't checked Riru for some time now. My school is killing me with assignments. When I have a bit of free time I will check everything and update this post.
Hello!!
In this thread I'm gonna show you how to install root with Magisk and install xposed.
First off all. This is how I did it. I'm going to explain it to the best of my abilities. However, if this does not work for you, or it resolves into a brick, its not my fault. Everything you do to your device it your own doing.
With that being said. Lets start!!
My setup:
Phone: Poco F2 Pro
Rom: xiaomi.eu Stable for Poco F2 Pro/Redmi K30 Pro
Android version: 10
Root: Magisk 21
Edxposed version: EdXposed-YAHFA-v0.4.6.2.4529.-release
Riru core version: magisk-riru-v21.3
EdXposed manager version: EdXposedManager-4.5.7-45700
What did i do?
I installed xiaomi.eu weekly first. But quickly after finding out that root doesn't work on Android 11 yet, I installed the stable which was still on Android 10.
So here are the steps what i did to install EdXposed
The files should be attached to this post as a zip, if you don't see them here is a link
1: Install latest Magisk 21.1
2: Install magisk-riru-v21.3.zip
3: Install EdXposed-YAHFA-v0.4.6.2.4529.-release.zip
4: Reboot phone
5: Install EdXposed installer
After I did this Chrome stopped working. Every time I wanted to open Chrome it just closed on its own. So I did a little search on Google and found a fix.
Thanks to Reddit user lkn194 for explaining how to fix this issue.
A quick step-by-step on how he/she did it:
In EdXposed Installer:
1: Go to settings> Framework> activate APP LIST MODE
2: Go to applications (Black list)> Leave enabled for:
• Android Services Library;
• Chrome;
• Google service structure;
• Google play services;
• Google play services for AR
3: Restart your device. After that you're done and Chrome is working
The first module I installed was CustoMIUIzer. Its an amazing addon mod for MIUI devices. You should definitely check that out.
This is the link
I hope this works for you as well as it does for me.
If you have any questions, be sure to say so.
Thanks for checking this out and have a great day!!
Welp the files weren't attached to that post, so here they are.
paulo boë said:
Hello!!
In this thread I'm gonna show you how to install root with Magisk and install xposed.
First off all. This is how I did it. I'm going to explain it to the best of my abilities. However, if this does not work for you, or it resolves into a brick, its not my fault. Everything you do to your device it your own doing.
With that being said. Lets start!!
My setup:
Phone: Poco F2 Pro
Rom: xiaomi.eu Stable for Poco F2 Pro/Redmi K30 Pro
Android version: 10
Root: Magisk 20.4
Edxposed version: EdXposed-YAHFA-v0.4.6.2.4529.-release
Riru core version: magisk-riru-v21.3
EdXposed manager version: EdXposedManager-4.5.7-45700
What did i do?
I installed xiaomi.eu weekly first. But quickly after finding out that root doesn't work on Android 11 yet, I installed the stable which was still on Android 10.
So here are the steps what i did to install EdXposed
The files should be attached to this post as a zip, if you don't see them here is a link
1: Install latest Magisk 20.4
2: Install magisk-riru-v21.3.zip
3: Install EdXposed-YAHFA-v0.4.6.2.4529.-release.zip
4: Reboot phone
5: Install EdXposed installer
After I did this Chrome stopped working. Every time I wanted to open Chrome it just closed on its own. So I did a little search on Google and found a fix.
Thanks to Reddit user lkn194 for explaining how to fix this issue.
A quick step-by-step on how he/she did it:
In EdXposed Installer:
1: Go to settings> Framework> activate APP LIST MODE
2: Go to applications (Black list)> Leave enabled for:
• Android Services Library;
• Chrome;
• Google service structure;
• Google play services;
• Google play services for AR
3: Restart your device. After that you're done and Chrome is working
The first module I installed was CustoMIUIzer. Its an amazing addon mod for MIUI devices. You should definitely check that out.
This is the link
I hope this works for you as well as it does for me.
If you have any questions, be sure to say so.
Thanks for checking this out and have a great day!!
Click to expand...
Click to collapse
Thanks for the tutorial, but just wondering; does Customiuizer work well for you if you've got phone security enabled? I ask because I tried it earlier after correctly installing edxposed on the latest stable MIUI EU, but once I had customised the settings through the app and rebooted to have them applied, all I got was an onscreen 'please wait' warning that just hung there forever.
After doing some online research, I found out that if the phones encrypted (fingerprint or password), the Customiuizer app gets stuck on load for some strange reason. If all security options are disabled, then the app will apply the customisations just fine (although at the moment not all features seem to work on Miui12), so just wanted to know if this happens to you as well... Thanks again.
krilok said:
Thanks for the tutorial, but just wondering; does Customiuizer work well for you if you've got phone security enabled? I ask because I tried it earlier after correctly installing edxposed on the latest stable MIUI EU, but once I had customised the settings through the app and rebooted to have them applied, all I got was an onscreen 'please wait' warning that just hung there forever.
After doing some online research, I found out that if the phones encrypted (fingerprint or password), the Customiuizer app gets stuck on load for some strange reason. If all security options are disabled, then the app will apply the customisations just fine (although at the moment not all features seem to work on Miui12), so just wanted to know if this happens to you as well... Thanks again.
Click to expand...
Click to collapse
Hmm. To be honest, I've never encountered that. I always disable the MIUI security checks. So everything works fine for me from the get-go. I guess you have to disable the security to get it working. I'm sorry to say so, I'm not much help here...
paulo boë said:
Hmm. To be honest, I've never encountered that. I always disable the MIUI security checks. So everything works fine for me from the get-go. I guess you have to disable the security to get it working. I'm sorry to say so, I'm not much help here...
Click to expand...
Click to collapse
Thanks for the reply, but when you say you disable MIUI security checks, which options are you referring to? Is it something within the customiuizer app itself, or on phone settings?
krilok said:
Thanks for the reply, but when you say you disable MIUI security checks, which options are you referring to? Is it something within the customiuizer app itself, or on phone settings?
Click to expand...
Click to collapse
I'm sorry, i didnt say what. I was referring to disabling the security checks on installing apk's. That all i disabled. I also did nothing with the Security app. I haven't even actually opend that app.
Try disabling the security for apk's check by going into
Security app --> settings --> Security Scan --> disable "Scan before installing".
I also didn't click on any "agree" button cus like i said, i dont use the Security app
Thats what i have. Nothing more nothing less.
paulo boë said:
I'm sorry, i didnt say what. I was referring to disabling the security checks on installing apk's. That all i disabled. I also did nothing with the Security app. I haven't even actually opend that app.
Try disabling the security for apk's check by going into
Security app --> settings --> Security Scan --> disable "Scan before installing".
I also didn't click on any "agree" button cus like i said, i dont use the Security app
Thats what i have. Nothing more nothing less.
Click to expand...
Click to collapse
Thanks, but I had already disabled "Scan before installing". I guess it's something to do with the device being encrypted, because once I remove any passwords or fingerprints, some of the app's functions do indeed work (eg.: advanced reboot, volume keys media playback control). I guess for the moment it's either no security at all or no CustoMIUIzer...
A small request if I may; if you have the time, could you kindly check if album art is displaying on your lock-screen while paying music? The option to activate this feature is under 'lock-screen' mods within the CustoMIUIzer app... Thanks in advance.
krilok said:
Thanks, but I had already disabled "Scan before installing". I guess it's something to do with the device being encrypted, because once I remove any passwords or fingerprints, some of the app's functions do indeed work (eg.: advanced reboot, volume keys media playback control). I guess for the moment it's either no security at all or no CustoMIUIzer...
A small request if I may; if you have the time, could you kindly check if album art is displaying on your lock-screen while paying music? The option to activate this feature is under 'lock-screen' mods within the CustoMIUIzer app... Thanks in advance.
Click to expand...
Click to collapse
Hmm. What rom are you using?
As for your request, i can confirm its working
paulo boë said:
Hmm. What rom are you using?
As for your request, i can confirm its working
Click to expand...
Click to collapse
Thanks for the confirmation. Album art didn't seem to work when I tried yesterday...
In any event, it's all quite strange since I'm also using the same rom and configuration as you are:
Xiaomi.eu Stable for Poco F2 Pro/Redmi K30 Pro
Magisk 20.4
EdXposed-YAHFA-v0.4.6.2.4529.-release.zip
Do you have any password / PIN / fingerprint enabled?
krilok said:
Thanks for the confirmation. Album art didn't seem to work when I tried yesterday...
In any event, it's all quite strange since I'm also using the same rom and configuration as you are:
Xiaomi.eu Stable for Poco F2 Pro/Redmi K30 Pro
Magisk 20.4
EdXposed-YAHFA-v0.4.6.2.4529.-release.zip
Do you have any password / PIN / fingerprint enabled?
Click to expand...
Click to collapse
I do, i have a pattern lock with fingerprint and face unlock. Super strange...
paulo boë said:
I do, i have a pattern lock with fingerprint and face unlock. Super strange...
Click to expand...
Click to collapse
Really weird... :silly:
Anyhow, will try and reinstall the app again later today and fiddle around with it a bit to see what could be causing the issue then...
Thanks anyhow for the help. :good:
Update: Tried it all again starting over from scratch, and this time the CustoMIUIzer app worked perfectly without any hangs. What I did differently was verify all permissions had been granted for the app and also enabled it to auto-start as well, and so far, it seems to be working fine.
Had a problem with the album art on lock-screen not applying, though, but after a few tries I managed to figure out that it was because of some compatibility issue with the default MIUI theme; it worked when I set the 'Classic' theme as default, and also used a static wallpaper instead of a live one...
krilok said:
Update: Tried it all again starting over from scratch, and this time the CustoMIUIzer app worked perfectly without any hangs. What I did differently was verify all permissions had been granted for the app and also enabled it to auto-start as well, and so far, it seems to be working fine.
Had a problem with the album art on lock-screen not applying, though, but after a few tries I managed to figure out that it was because of some compatibility issue with the default MIUI theme; it worked when I set the 'Classic' theme as default, and also used a static wallpaper instead of a live one...
Click to expand...
Click to collapse
That's good to hear. Im glad its working for you now.
I have no idea when you edited this post, so srry if i responded to late.
paulo boë said:
That's good to hear. Im glad its working for you now.
I have no idea what you edit this post, so srry if i responded to late.
Click to expand...
Click to collapse
No problem, thanks for replying anyhow.
BTW, I found out why the app was freezing... Seems it was because I had activated the 'no password after boot' option under the apps lockscreen settings... ?
Why not use Edxposed canary (5.0.6)?
Curunir said:
Why not use Edxposed canary (5.0.6)?
Click to expand...
Click to collapse
Because for me, it didnt work.
Just wondering if you'd still suggest using the stable ROM instead of the weekly.
oroboros74 said:
Just wondering if you'd still suggest using the stable ROM instead of the weekly.
Click to expand...
Click to collapse
As of now, root in its whole doesn't work on Android 11. And because it only works for Android 10 there is no other option but only to use this on Stable.
Unless you want no root and just want check out the new features. I suggest the Stable.
paulo boë said:
As of now, root in its whole doesn't work on Android 11. And because it only works for Android 10 there is no other option but only to use this on Stable.
Unless you want no root and just want check out the new features. I suggest the Stable.
Click to expand...
Click to collapse
Just curious, as it seems people have gotten root on it :
https://forum.xda-developers.com/po...-android-11-discussions-t4165065/post83542945
Or am I missing something?
oroboros74 said:
Just curious, as it seems people have gotten root on it :
https://forum.xda-developers.com/po...-android-11-discussions-t4165065/post83542945
Or am I missing something?
Click to expand...
Click to collapse
I dont know anything about root on Android 11. When i tried to install it on beta it didnt work. And so far I've seen only one person who said he/she had been able to acquire root on 11. If someone else can confirm this that would be great. I cant test it rn, cus of personal reasons, I need a stable phone.
for what you use Xposed?
.