Related
Hello everyone,
I was reading all the posts about Custom Roms and I wanted to make something like an "XDA-Rom"... Maybe it would be better if I explain what I mean
Beginning from the system, I'd say it should be a very lightweight Rom (like the Gilgamesh one), so, without almost all the LG crapware. But I'd keep only few things of this softwares:
- contact manager (so far it's the best one I've found, but maybe because I lack of experience)
- keyboard (on some videos they say it's the fastest one, but I may be in error)
- LG home and Home switcher, so that we can keep the mirroring app working when needed.
Then, I'd add the last MoDaCo kernel (the ROM should be working in EXT4, if I understtod correctly, this shall make the phone faster), maybe we could make a proper boot animation, and just few app that are (in my opinion) the only really needed, like the gmail app, the calendar one and only the basic things. We could even update the baseband and root the phone directly from the rom, so that after a fresh install it's already running. I'd replace even the LG lockscreen, that is really nice, but it's too slow (when I switch on the screen, I see the home and then the locked screen, this shouldn't happen with the default lockscreen).
Ofc, any suggestion is welcome
Thanks for reading, and I hope my idea is not that bad
I agree on the bootanimation.
Only on that? d'oh, I wrote for half an hour btw, I'd add Root Explorer as default as well... but I don't know how to do, I mean, would be enough to create the ROM with the kitchen (really a nice tool!) and then edit the *img files adding the software I want in the /system/app directory? Maybe this is a noobish question, but it's the first time I even get closer to creating a custom rom
Oh, integrate BLN to have notifications would be a great idea ! (if you touch the kernel)
tiwiz said:
Only on that? d'oh, I wrote for half an hour btw, I'd add Root Explorer as default as well... but I don't know how to do, I mean, would be enough to create the ROM with the kitchen (really a nice tool!) and then edit the *img files adding the software I want in the /system/app directory? Maybe this is a noobish question, but it's the first time I even get closer to creating a custom rom
Click to expand...
Click to collapse
the root explorer is not for free.. so forget about this
Why? Install modaco and use filexplorer and delete all thing u dont want instead
Sent from my LG-P990 using XDA Premium App
For the experience, I'd like to test
Just use the online kitchen...
I was actually 30 mins from posting a pretty close ROM to what you mention here yesterday, but built the one I'd like online instead (except for some tweaks I put in laster on).
If people is more open for a ROM like this for direct download, I'm happy to compile/maintain it Just thought that it wasn't needed...
I have ported Oreo for Mi mix , wifi working , sound , bluetooth , camera , nfc , android pay but i keep getting com.android.phone error and don´t know how to fix it. Yes im noob and i have learnt to compile using xda guides and youtube tutorials so please dont be too hard with me i beg you . Thanks for the help . I´ll give donations to helpers.
Hi @YazumiWuHung,
sorry with that little information it's somewhat impossible to assist you :_/
I'd like to advice the 2 things as followed:
- head over to the ROMs section (https://forum.xda-developers.com/mi-mix/development) and post your question and if possible an downloas/test possibility there
- create at least an log of the error in the timeslot it apperars -> HowTo: https://developer.android.com/studio/command-line/logcat.html
Good luck!
Could be any (but not limited to) of the following:
- permission/folder issues in ramdisk (for example for the modem part)
- missing/incorrect config xmls in overlay (framework, or Phone package)
- missing/incorrect parameters in *props
As suggested by raupe, a logcat could point in the right direction.
willing to test for you if you want that..
thanks for your efforts to bring oreo to us!
Found Nazmul hasan on Androidfilehost.
He has worked on mi mix Oreo.
https://androidfilehost.com/?fid=745849072291680983
He might help you.
All the credits goes to respective developers.
I have not tried the rom yet so don't ask me what's working or not.
Hey guys, so obviously there hasn't been much development here.
My question, however, is what kind of barriers do we even have with this device?
I thought I saw a bootloader unlock menu item in the dev settings. So that should hopefully be fairly easy hopefully.
Is it then just a matter of porting an existing ROM here or modifying an existing Nokia7Plus ROM to add features / changes?
bballs91 said:
Hey guys, so obviously there hasn't been much development here.
My question, however, is what kind of barriers do we even have with this device?
I thought I saw a bootloader unlock menu item in the dev settings. So that should hopefully be fairly easy hopefully.
Is it then just a matter of porting an existing ROM here or modifying an existing Nokia7Plus ROM to add features / changes?
Click to expand...
Click to collapse
Well, Nokia 7 plus supports phh treble, if you already unlocked your phone, you can try
Lineage OS : https://forum.xda-developers.com/pr...evice-development/lineage-phh-treble-t3767690
RR : https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688
There is no way of unlocking the bootloader currently.
Question for Kernel Devs, Re: Hotspot, DUN, "Carrier does not allow type 'dun'."
Devs of kernels, ever since Android O, attempting to add dun to APN, results in error "Carrier does not allow type 'dun.'", ever since Google baked it in for the benefit of carriers (in this particular case, T-mobile) to prevent hotspot tethering.
That's very nice of them, but not helpful for me, who must stay on Android N for my hotspot to work properly.
Can one of you kernel devs modify this so that hotspot will once again work properly, or tell me of a kernel or ROM on which it already works the way it used to?
You can let me know via DM if you don't want to reply here.
pbergonzi said:
Devs of kernels, ever since Android O, attempting to add dun to APN, results in error "Carrier does not allow type 'dun.'", ever since Google baked it in for the benefit of carriers (in this particular case, T-mobile) to prevent hotspot tethering.
That's very nice of them, but not helpful for me, who must stay on Android N for my hotspot to work properly.
Can one of you kernel devs modify this so that hotspot will once again work properly, or tell me of a kernel or ROM on which it already works the way it used to?
You can let me know via DM if you don't want to reply here.
Click to expand...
Click to collapse
There has been work on this in LOS. Particularly @nvertigo67 has got a good understanding of the issue and has been endeavoring to enable the functionality on a case by case basis. I'd begin there if i were you.
Dirk said:
There has been work on this in LOS. Particularly @nvertigo67 has got a good understanding of the issue and has been endeavoring to enable the functionality on a case by case basis. I'd begin there if i were you.
Click to expand...
Click to collapse
Thank you.
@nvertigo67 made a custom confs file that we tested on LOS 16--while it did indeed install dun parameter, the result was still non-functional.
He is still researching, however we both believe google baked in the functionality, and it needs a kernel dev to find it. There were articles a while back (the advent of Oreo?) that refer to google having done so.
pbergonzi said:
Thank you.
@nvertigo67 made a custom confs file that we tested on LOS 16--while it did indeed install dun parameter, the result was still non-functional.
He is still researching, however we both believe google baked in the functionality, and it needs a kernel dev to find it. There were articles a while back (the advent of Oreo?) that refer to google having done so.
Click to expand...
Click to collapse
I've stated it's "more complecated" then adding dun - I've never stated it's kernel related, and I don't think it's kernel related!
I've stoped dealing with this, because I'm tired of begging for information. When we tried the modified apns-conf.xml, you told me it's not not working, but it's working unusable slowly ("like before without the modified apns-conf.xml")...
Again: this is NOT related to the kernel.
nvertigo67 said:
I've stated it's "more complecated" then adding dun - I've never stated it's kernel related, and I don't think it's kernel related!
I've stoped dealing with this, because I'm tired of begging for information. When we tried the modified apns-conf.xml, you told me it's not not working, but it's working unusable slowly ("like before without the modified apns-conf.xml")...
Again: this is NOT related to the kernel.
Click to expand...
Click to collapse
I apologize for misunderstanding.
Thank you for the clarification and your efforts.
nvertigo67 said:
I've stated it's "more complecated"
Click to expand...
Click to collapse
Found another solution--sold OP3T and got OP6T. Surprisingly, it connects properly with pie, using stock or modded ROMs.
Phew.
pbergonzi said:
Found another solution--sold OP3T and got OP6T. Surprisingly, it connects properly with pie, using stock or modded ROMs.
Phew.
Click to expand...
Click to collapse
Which proofes, you were wrong with the dun change you've ask me to do - on los op6t and op3/t use the very same apns-conf.xml file... Perhaps because it's more complecated... *lol*
nvertigo67 said:
Which proofes, you were wrong with the dun change you've ask me to do - on los op6t and op3/t use the very same apns-conf.xml file... Perhaps because it's more complecated... *lol*
Click to expand...
Click to collapse
Yes, thank you.
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...