Database Users

[Guide] A complete MiniCM9-3.0.4 how-to

Hi guys
This post is essentially going to be an aggregation of info regarding MiniCM9, bringing together in one place all the random bits and pieces I found to get things working at their best. I originally started writing this for myself (to keep track of things when updating/reinstalling) but as I've responded to questions here and there I thought it might be good to have one place to link to, rather than trying to find my previous posts.
MiniCM9 basic setup
SD card:
Create an ext4 swap partition from CWM; (at least 128M, I recommend 256M+)
How to get a swap partition of any size OR configure swap separately from an sd-ext partition:
Follow this basic tutorial
If you just want to adjust the size of your swap partition and/or sd-ext partition, it's not necessary to completely erase your SD card/remove all partitions and start from scratch
You can work with the Resize/Move options and still get what you want.
System setup:
Flash minicm9 and gapps as normal (in the installer, choose only apps you use; would not recommend Apollo)
Boot up your system, grab your favourite root browser from Google Play, and remove remaining unwanted applications and services (e.g. for me, Google Talk, FM radio, etc.) by deleting them from system/app.
Do not 'install a2sd' via console
System configuration:
Set up your autobrightness settings like this
Test your pulse notification light. If it stops flashing after a couple of seconds, go to system/lib/hw via your root file manager and delete/rename lights.shakira.so. Once you reboot, your notification light should work normally.
Disable Google's location service unless you need it as it may drain battery (GPS is okay)
Min CPU: 320MHz (important!); Max CPU: whatever you feel like (provided your phone can handle it)
Governor: SMARTASSV2
No Undervolt
Disable zRam
Do not enable 'Allow purging of assets'
Do not enable Kernel samepage merging
Surface dithering: Yes
16bit transparency: No
Disable boot animation: No
NB: minicm9 settings will not pick up on your swap partition (claiming swap is disabled). Open terminal emulator and type in 'free' to see your available memory, it should correctly show the size of your swap partition.
Further performance tweaks:
Do NOT use Supercharger.
Move large apps that are not usually running to SD (e.g. Opera) via Settings»Apps»Move to SD. If this option is greyed out, follow this guide to move them anyway (NB: the command for the ICS platform is set-install-location rather than setInstallLocation). You do not need App2SD.
Optimise your SD card's read ahead cache (significantly increases read/write speeds on higher end SD cards). There are two ways to do this; by manually creating a script (recommended) or by installing a third party application.
To do it via application, install SD-Booster and a SD card speed test of your choice. Adjust the cache until you get an optimal read/write speed (for me, this is at 4096KB) – more is not always better. You can uninstall the speed tester once you're done
To manually set your SD read ahead cache on boot, go to this thread and follow the instructions for Version 1. Replace 128 with the optimal value for your SD card (determined as above).
Set swappiness:
You can customise your swappiness by creating/adding the following to userinit.sh in data/local/
Code:
#!/system/bin/sh
#Swap
swapon dev/block/mmcblk0p3
echo [COLOR="Red"]50[/COLOR] > /proc/sys/vm/swappiness
Red value ranges from 0 (don't swap unless you run out of memory) to 100 (swap from the get go). Feel free to experiment; in my experience performance is most stable around 50. Don't forget to set permissions (to rwxr-xr-x).
You should now have a beautifully smooth, stable miniCM9 on Trebuchet (battery life should be good). Stock browser should run fine thanks to swap, apps will stay in memory and load quickly. Make sure to free up apps via home button » swipe if you no longer need them, especially if running on less swap memory. ​
How do I get ... working? / Extras
Set custom lock screen icons:
After selecting your application, tap on the icon to get a menu allowing you to choose from your gallery or system (white lock screen-styled icons)
Enable lock screen rotation:
Follow this guide to patch your framework-res.apk to allow lock screen rotation, or replace yours with the one attached (but first, make sure you are using the same version of miniCM9! the apk is for 3.0.4). In either case, backing up is a good idea, folks
framework-res.apk for miniCM9-3.0.4
Fix Japanese font rendering on ICS:
Probably not something that concerns most people; but if you are using Japanese on your android, you will have noticed that by default, Chinese versions of unicode unified ideograms are rendered (which can be less than optimal at times). To get proper Japanese text output across applications, you will have to install the Japanese Droid font (DroidSansJapanese) and insert a reference to it in your font fallback .xml.
To make your life easier, I have included the files in a zip for your perusal:
Extract the files
Copy DroidSansJapanese.ttf to system/fonts
Replace your fallback_fonts.xml in system/etc with the one provided
Japanese font files for ICS
Dark Holo themed apps:
If you like the dark Holo ICS theme, and want your applications to suit the rest of your system, you can find various inverted google apps for ICS-based roms around the web. I've included the ones I use and work well on miniCM9 on our X8 here for convenience.
Extract the files
Replace your apps in system/app with the ones included
Reboot & enjoy a true ICS UI
Dark Holo ICS themed apps for miniCM9
Get voice input working on miniCM9:
If you've ever used voice input features, you will have noticed these (while present) fail to work after installing the rom. So will any type of android-based voice recognition. To get basic voice functionality working (sadly not ICS flavoured) do the following:
in system/app delete your voice search apk
reboot your system
now find Google Voice Search 2.1.4 (for Android 2.2+) on Google Play and install it.
voice search and recognition should now work as it did on older roms.
To get voice typing working you will have to replace your input method (or install it as an additional IME to switch to when you want to use voice typing).
install IceCream Sandwich-ICS Keyboard by VLLWP from Google Play (for Android 1.6+). DO NOT UPDATE this, as its Jelly Bean version or other ICS keyboards will not work with voice typing.
enable and select it as an input type and hit the microphone key. Confirm the prompt, and you should be able to use basic android speech recognition in any text form you like.
Lightweight Jelly Bean keyboard:
More of a recommendation, but what it says on the tin;
get this app from Google Play (keep in mind like stock keyboard it won't work with voice input, so you might want to run it in addition to the aforementioned) and install it -- once you're all set you can now safely remove LatinIME.apk from your system/app
you save memory (both in usage footprint and SD card space) and get a fully featured Jelly Bean keyboard with functional word prediction in exchange, which is a fair trade, no?
​
... and that is all I can think of right now. May update this thread as things change

Nice! I want to ask you something. Is the way to check if swap work? I am not sure
1. Create partizion (256 mb)
2. Create file userinit.sh and added it into sdcard
3. Copy and paste it into data/local/
4. Set permission
5. Reboot
Correct?

Does it improve battery saving or performances ???

Thank u for ur efforts...
It really helps.
To the modslease make this thread sticky.

Xerdox said:
Nice! I want to ask you something. Is the way to check if swap work? I am not sure
1. Create partizion (256 mb)
2. Create file userinit.sh and added it into sdcard
3. Copy and paste it into data/local/
4. Set permission
5. Reboot
Correct?
Click to expand...
Click to collapse
Swap should work as soon as you have a partition on current versions. The userinit is just if you want to set swappiness/specifics.
The way to check is going to terminal emulator and typing in 'free'. You should see your swap space listed.
{
"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"
}
(note swap size in the 'total' column)
LEDelete said:
Does it improve battery saving or performances ???
Click to expand...
Click to collapse
Does what improve battery life/performance? Both are more than decent with the settings provided, if that's what you mean. I'll see about adding screenshots.

Can i change the size of the swap partition¿ i have 128 and want 256... thanks
Sent from my E15i using xda premium

IAmNice said:
Why would you disable KSM? Ksm improves performance. It only drains a bit of battery and doesnt harm anything.
Click to expand...
Click to collapse
Have not extensively tested it with the latest build so it may have been fixed since, but last I tried it caused performance/stability issues for me aside from the battery drain.
zlqtt said:
Can i change the size of the swap partition¿ i have 128 and want 256... thanks
Click to expand...
Click to collapse
Yes, using gparted (see linked tutorial) you can resize your existing partition.

did any1 faced with lag on calls? ei: when i'm reciving call, the screen is black for 2-5secs, and after lights on. i dont have any idea whats the problem, maybe can it be the low cpu freq?

Do i need to enable swap on performance settings?
Sent from my E15i using xda premium

zlqtt said:
Do i need to enable swap on performance settings?
Click to expand...
Click to collapse
Not if you have a partition, no.

nice broo..!! About swap,I must download swaper2 from market ??? or use from system rom only ???

The first post says it all.
You don't need anything except the rom (+ kernel) itself.

The apps on my phone often take 2-5 seconds to start. I thought it is because some of them are on the ext4 partition, but even the settings app does the same, and it is really annoying. When I click on an app, the ICS gradient dark background is shown for some seconds, then it is loaded. Is there a solution for this? Or is MiniCM9 just like that?

The first time you open apps might take a second to load (depending on your settings)
After that they should remain cached in normal use and open more or less instantly, without the empty screen.

[Guide] Enable LTE Icon on Unrooted Mate 9

Hey guys, rather than make an article for what I feel is a minor change, I decided to just post a quick thread on this.
Some users have reported that despite the fact that they have LTE service, their phone does not show the LTE icon in the status bar. This is because Huawei uses your Mobile Country Code (see: https://en.wikipedia.org/wiki/Mobile_country_code) to determine whether or not to show LTE. All you have to do is edit a system property and add your MCC. For example, I'm in the U.S. so my MCC is 310.
First download the ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) and get the drivers for your own (Hisuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html). Next open up a command prompt and type the following:
adb shell settings get system hw_show_lte
This should be a semi-colon separated list of MCCs. By default my Mate 9 only had the value of 260 (Poland), so I had to edit it to add U.S. as such:
adb shell
And then type (for some reason if you combine the two commands it doesn't work):
settings put system hw_show_lte "260;310"
Try that and see if it works. I did this trick a while back so I don't remember if it's the MCC or the MNC (mobile network code) that has to be input lol, but try either and it should work. I've been using my European Mate 9 in the U.S. and it shows LTE for me after I did this trick.

MishaalRahman said:
Hey guys, rather than make an article for what I feel is a minor change, I decided to just post a quick thread on this.
Some users have reported that despite the fact that they have LTE service, their phone does not show the LTE icon in the status bar. This is because Huawei uses your Mobile Country Code (see: https://en.wikipedia.org/wiki/Mobile_country_code) to determine whether or not to show LTE. All you have to do is edit a system property and add your MCC. For example, I'm in the U.S. so my MCC is 310.
First download the ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) and get the drivers for your own (Hisuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html). Next open up a command prompt and type the following:
adb shell settings get system hw_show_lte
This should be a semi-colon separated list of MCCs. By default my Mate 9 only had the value of 260 (Poland), so I had to edit it to add U.S. as such:
adb shell settings put system hw_show_lte "260;310"
Try that and see if it works. I did this trick a while back so I don't remember if it's the MCC or the MNC (mobile network code) that has to be input lol, but try either and it should work. I've been using my European Mate 9 in the U.S. and it shows LTE for me after I did this trick.
Click to expand...
Click to collapse
It's also in the cust folder in the local.prop file you can change it to true to have the icon show 4GLTE.

ajsmsg78 said:
It's also in the cust folder in the local.prop file you can change it to true to have the icon show 4GLTE.
Click to expand...
Click to collapse
That requires root access doesn't it? This method doesn't.

Hey there thanks again! But when I try to enter your input I get /system/bin/sh: 220: not found and when I enter just adb shell settings get system hw_show_lte it shows 260.
hmm what could be the issue

Coolyou said:
Hey there thanks again! But when I try to enter your input I get /system/bin/sh: 220: not found and when I enter just adb shell settings get system hw_show_lte it shows 260.
hmm what could be the issue
Click to expand...
Click to collapse
Sorry, it's been awhile since I did this. Let me double check the syntax.
Edit: I double checked my syntax, and it is correct. Please double check you are entering it exactly as I wrote.

MishaalRahman said:
Sorry, it's been awhile since I did this. Let me double check the syntax.
Edit: I double checked my syntax, and it is correct. Please double check you are entering it exactly as I wrote.
Click to expand...
Click to collapse
I tried several times and also copied your text without any space here is the output:
{
"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"
}

Very interesting. For some reason when you combine "adb shell" and "settings put system hw_show_lte" it doesn't work. Do this instead and it will work:
Type
adb shell
to enter the shell. Then type
settings put system hw_show_lte "260;310"
This should work. I edited my OP to reflect this change.

MishaalRahman said:
Very interesting. For some reason when you combine "adb shell" and "settings put system hw_show_lte" it doesn't work. Do this instead and it will work:
Type
adb shell
to enter the shell. Then type
settings put system hw_show_lte "260;310"
This should work. I edited my OP to reflect this change.
Click to expand...
Click to collapse
it seems like it worked now, no errors shown, I restarted my phone but however still no 4G icon as shown below:

This change doesn't add a 4g LTE icon to the quick tiles. It adds the icon to the status bar.

MishaalRahman said:
This change doesn't add a 4g LTE icon to the quick tiles. It adds the icon to the status bar.
Click to expand...
Click to collapse
Oh, you misunderstood me then. Sorry for troubling you all the way. I was talking about that icon in notifications tile how you called it. I unlocked my phone from c66 to c432 on c66 I had it, now on c432 it's non-existant.

Oooo...will give this a try and get back to you. I am in US on AT&T network...I thought I would get LTE by default, but only showing 4G. I have the L29C185B138 international version...

MishaalRahman said:
Hey guys, rather than make an article for what I feel is a minor change, I decided to just post a quick thread on this.
Some users have reported that despite the fact that they have LTE service, their phone does not show the LTE icon in the status bar. This is because Huawei uses your Mobile Country Code (see: https://en.wikipedia.org/wiki/Mobile_country_code) to determine whether or not to show LTE. All you have to do is edit a system property and add your MCC. For example, I'm in the U.S. so my MCC is 310.
First download the ADB binaries (https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/) and get the drivers for your own (Hisuite: http://consumer.huawei.com/minisite/HiSuite_en/index.html). Next open up a command prompt and type the following:
adb shell settings get system hw_show_lte
This should be a semi-colon separated list of MCCs. By default my Mate 9 only had the value of 260 (Poland), so I had to edit it to add U.S. as such:
adb shell
And then type (for some reason if you combine the two commands it doesn't work):
settings put system hw_show_lte "260;310"
Try that and see if it works. I did this trick a while back so I don't remember if it's the MCC or the MNC (mobile network code) that has to be input lol, but try either and it should work. I've been using my European Mate 9 in the U.S. and it shows LTE for me after I did this trick.
Click to expand...
Click to collapse
Thank you!!! Worked like a charm!! I'm on AT&T and now I can see LTE instead of 4G in my status bar!! Great find!

I don't get people 4G and LTE is the same thing just different names.

albertobom said:
I don't get people 4G and LTE is the same thing just different names.
Click to expand...
Click to collapse
Agreed! But when you're used to seeing 'LTE' instead of '4G', it helps that there's a way to bring it back... [emoji12] [emoji12]
Sent from my MHA-L29 using Tapatalk

baddison said:
Agreed! But when you're used to seeing 'LTE' instead of '4G', it helps that there's a way to bring it back... [emoji12] [emoji12]
Click to expand...
Click to collapse
I know just teasing you guys.

baddison said:
Thank you!!! Worked like a charm!! I'm on AT&T and now I can see LTE instead of 4G in my status bar!! Great find!
Click to expand...
Click to collapse
Glad it worked for you. This trick makes 0 difference in functionality, but for some people the lack of an LTE icon is jarring.

When I run "adb shell settings get system hw_show_lte" I just got the answer "null".
Is it save to continue and run the next command? In my case will be something like:
settings put system hw_show_lte "226"

dancrow said:
When I run "adb shell settings get system hw_show_lte" I just got the answer "null".
Is it save to continue and run the next command? In my case will be something like:
settings put system hw_show_lte "226"
Click to expand...
Click to collapse
Yes, be all good . Im using c636 got null , then change to 302 and 310

How does it work with the MHA-L29C432B182?

MishaalRahman said:
Glad it worked for you. This trick makes 0 difference in functionality, but for some people the lack of an LTE icon is jarring.
Click to expand...
Click to collapse
Hey Mishaal I sent you a PM but I don't think you are reading those so I'll ask here
I spoke with your about LTE shell and I'm aware that you are very good with adb shell commands. So wanted to ask is it possible to change this option without rooting with adb shell?
The correct path is /system/emui/lite/prop/local.prop and you have to set ro.build.hw_emui_lite.enable=false
I tried with adb shell settings put system hw_emui_lite false via cmd but it doesn't work :/ If someone has experience with ADB write here
EDIT 1: adb shell settings put system hw_emui_lite.enable false - doesn't wor

[GUIDE] How to properly change / remove zoom error in eui/miuipro

Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:

Guys you can also use this to properly change DPI in eui and miui pro without font or clock glitches.:good:

Gautham V said:
Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:
Click to expand...
Click to collapse
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.

emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
It does still say zoomed in settings but it is not

emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
You wil fund the line ro.sf.lcd_density in all ROM except eUI, in eUI you can search for persist.ro.sf.lcd_density
Or similar to this one but that line start with persist

after doing this trick in miui pro rom i am continuously getting an error that system stopped

Rajashekar0675 said:
after doing this trick in miui pro rom i am continuously getting an error that system stopped
Click to expand...
Click to collapse
You must have messed somewhere

I tried the fix and didnt get any errors, but it still randomly switches from zoom mode to normal when opening apps. I really only notice it in gmail and chrome.

Guess changing the DPI has resulted in zoomed in pictures when cropping, cropping happens right as the markers indicate but the crop preview is zoomed in which makes it impossible to edit pictures. Is there a solution/hack for this?

[How to] - Get VoLTE working for T-Mobile US (yes, it actually works)

Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2. run the following commands (note that you MUST be rooted to enable this. The mod survives returning to stock unrooted, and even survives OTA so you can unroot when finished if you want.):
'''
adb shell
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
'''
3. once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
4. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
5. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
6. click the load button and select the mcfg_sw.mbn you downloaded earlier.
7. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
8. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
9. on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
10. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
{
"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"
}

Can this phone work on Metro PCS network

I tried and tried, but i cannot get PST to see my phone. I loaded qualcomm drivers and ADB drivers, nothing. Any suggestions?
Daha3ker said:
Unlocking more bands (specifically band 12) is on the way, please be patient as there are a lot of bugs with having a modified modem firmware.
I AM NOT RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR DEVICE! YOUR WARRANTY IS VOID IF YOU FOLLOW THIS TUTORIAL!
This took like 2 weeks to figure out, I was about to give up, but then it worked. VoLTE on band 4 and 2 for T-Mobile in the USA!!
I have only tested this on my phone, but it should work on others (assuming it is still an A2). I have not verified if this works for phones converted to the 6X so if you want to try please be careful.
Alright, enough with the warnings and stuff.
1. First, enable usb debugging and plug your phone into your computer.
1. Download qpst and install it. You will also need this file . Just save it somewhere, we will use it in a minute.
2.once installed there should be an entry in your start menu. open the folder labelled qpst and select the program "PDC".
3. click the Device dropdown and select the Qualcomm device. (it may not show up first time, make sure you have installed the drivers for your device)
4. once you select your device you should see a lost of items, this can take a minute depending on the speed of your computer.
5. click the load button and select the mcfg_sw.mbn you downloaded earlier.
6. "Commercial-TMO" should now be a listing in the description. Highlight it and right click on it, hover over "SetSelectedConfig" and select "sub0". Let it load for a bit.
7. it should now say pending on the Sub0 column of the Commercial-TMO. Now click activate and let it load.
8.on your phone, you must disable reigon checking. To do so go to your phone app and type in the following: *#*#86583#*#*
9. reboot your phone.
This worked for me, I have not verified that it works for others yet, so if it works for you, please let me know. Also let me know of any bugs.
Shreenshots below
Click to expand...
Click to collapse

This sounds scary. I thought volte works on band 12. If the band is missing how would it work. How can you confirm it actually works.

Hi!
I am running into the same issue of two computers (Win 7 and Win 10) that cannot see the phone. Anyone willing to help in getting PDC to see the phone? Thanks!

I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.

mymeatb18 said:
I have a couple questions for OP
Will this prevent any OTA?
Could you also take a screenshot of 4g while on a call?
What bugs do you experience?
I definitely see that your method unlocks some options in phone info, in the screenshots, but it doesn't necessarily prove anything if you can't see 4g while in a call and see a difference in speed. I notice the difference in speed when trying to do things on a call while on 3g, so if I were to do this I would definitely be able to tell it worked or not.
Click to expand...
Click to collapse
I would like to know this as well.

Ulver said:
I would like to know this as well.
Click to expand...
Click to collapse
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config diag,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.

Hi Daha3ker,
I tried to enable with the mentioned commands and still PDC cannot see my phone.
Daha3ker said:
If you want a specific screenshot let me know, I have been using this for a while though with no issues. The Band 12 has a lot of tuning data required and may not be compatible with all a2 devices without buying tuning equipment. (I used a friend's and hoped this was not the case) :/ I will keep working on it though. All is not lost yet.
As for the device not showing in the computer, it does require root as of the pie update because xiaomi disabled diag mode by default... :/
To enable it in the pie update you need to enter the following in adb shell for it to show up in qpst:
su
setprop sys.usb.config acm,diag,mtp,adb
setprop persist.sys.usb.config acm,diag,mtp,adb
Note, do not reboot yet, rebooting resets these values..
Then re- insert the phone into your computer and it should show up.
The nice thing is that this survives ota and root removal once put on so if you want ota you can have it, just unroot once you get the mod working.
Click to expand...
Click to collapse

Can't seem to make the phone appear in PDC as well, I've rooted the device with magisk and have tried to input the commands as suggested but it is still not being detected...

This is what I have

Any word on this?

Update, with stock you need to enter the command
setprop sys.usb.config diag,adb
While the phone is plugged in to the computer for it to work. I was using a different set of debug tools.

I had to use the following command to get PDC to work.
su
setenforce 0
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Im running Pixel Experience 20190320 rom with Magisk 18.1.
QPST 2.7.460
I used the QUD.WIN.1.1 Installer-10040.5 drivers on Windows 10 x64.

Could you unroot and relock bootloader and have this continue working and survive OTA updates?
---------- Post added at 11:18 PM ---------- Previous post was at 10:25 PM ----------
Looks like this survives a complete fastboot flash/relock. How would you reverse this and go back to stock?
---------- Post added at 11:30 PM ---------- Previous post was at 11:18 PM ----------
I want to switch back because sometimes when I make calls, it's high pitched and quiet. I can turn off voLTE to go back to the way it was, but would be nice to be stock again.

What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)

joaomiguelsm said:
What bands it's unlocked?
In Brazil is primordial that b28 is unlocked to use Volte (700 MHz)
Click to expand...
Click to collapse
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.

Ulver said:
Doesn't unlock any bands, just enables voLTE on T-Mobile in the USA. Unfortunately, it's pretty buggy, maybe due to recent updates.
Click to expand...
Click to collapse
Oh, sad
This is the worst thin of Xiaomi in Brazil

PDC not recognizing phone
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike

mtrohan said:
Hi,
I've been trying to get this working off and on for a couple of weeks. I can't get PDC to populate the drop down menu. I am able to get QPST to recognize the phone after doing :
su
setprop sys.usb.config diag,adb in an adb shell. After those commands, the Qualcomm driver loads (according to device manager). QPST configuration finds the phone on COM9. But when I load PDC I get nothing. Any thoughts? The voice calling on 2g in New York is horrible.
Thanks, Mike
Click to expand...
Click to collapse
im getting same problem... can solve??
pleaaaase... need help.

Changan Uni-T 2022 - s202_ica_spm8666p1_64_car

Hello everyone,
I have this model and its head unit is really buggy with apple car play, it would work once and stop working several times or just randomly disconnect from time to time. a pain to use honestly so I started scouring around for means of either fixing the buggy apple car play or experimenting with ways to make android auto work.
I tried the android box and it works fine, but its dependent on apple car play, and just yesterday I got this message:
{
"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"
}
And regardless of how many times i tried to reset the screen it kept on happening.
anyhow after some digging i found a thread somewhere that had the code for the developer mode.
Steps :
You go
- On the phone app press *#*#888 then press the call key
- A password prompt would come up the password is : 369875
Then a menu with full chinese text will be present, i tried everything until i found a settings button,
at first its an empty menu but if you swipe left or right you get taken into the default android settings menu, i tried starting developer mode and that works but there is no developer options menu in the main menu, probably disabled by the manufacturer.
i did find out that its running Android 9
and that this is the model code for the Headunit : s202_ica_spm8666p1_64_car
No idea if anything is possible at this point, but sharing just in case someone knows.
For as far as i know without toggling on USB debugging its not possible to sideload anything.
Anyone have any clue on where to go with this ?
Thanks

thanks for sharing this information, I have Changan Uni k 2023, and I used same steps you mentioned, and I got chinese panel, however, I found if you go to the second tab USB you'll find 2 options 1- using usb as an input, 2- using usb in ADB mode, I activated the ADB mode but still my laptop didn't recognize my car unit,
hope you or someone else can help us from here.

it worth to mention that if you go to the tab above cpu, it will show you 2 options, the first one "Settings" it will open Android settings, from there I went to last option "about" and to last item on it which's "IMEI" I think, if you click on it 7 times it will activate developer mode
then you will go back to main page of Android's settings, then advanced settings, then click the tab to show more advanced options, you'll find developer mode
I went there activated USB debugging, and change USB to file transfer, yet nothing happened!

be advised that I did all these steps in order to connect my car head unit to my computer so I can install file manger app by ADB then I can install any apps I wanted in this unit, so if your goal is different and you wanna just fix car play errors, you will need only to go to system settings in main page of the car then resetting,
it will work just fine!

Actually i started for just fixing the car play issue, but then i decided its better if i just go the ADB route and install a file manager app or some sort of store to download apks directly.
Did you get to make it work in the end ?

Actually I made progress !
If you go into the developer options there is a default USB connection thing that you can set to data transfer, and then if you do go ahead and go to the menu outside and set ADB from that other button it will connect to a pc.
So i tried the following command with ADB tools,
.\adb.exe install -g "C:\Users\vx_10\Desktop\platform-tools\android_auto.apk"
but keep getting errors
I must be missing a step or something, but hey progress made !

I did same steps but no luck, you have to make sure that your pc actually connected to your car by listening the connected devices by this command:
adb devices
then try install command
mine show 0 devices connected

maybe you need a different kind of cable, mine actually shows the device, i am only having this issue with the install about the password

god knows tried multiple cables
try this pass
aDB36987

all small letters
adb36987

EY3_2023 said:
all small letters
adb36987
Click to expand...
Click to collapse
where to input the password ? right after the file name ?

TheOneTheOnlyTheOne said:
where to input the password ? right after the file name ?
Click to expand...
Click to collapse
when ever password is requested as the picture you shared, or try:
adb root
adb shell
then enter the password

Thanks man ! i did a lot of progress, finally figured how to install stuff, but after doing so they do not show up in the apps, so i am trying to launch them with shell commands, i downloaded android auto and a browser
This worked for installing :
spm8666p1_64_car:/data/local/tmp $ pm install Browser_for_Android_2.3.5_Apkpure.apk
trying this command to launch them
spm8666p1_64_car:/data/local/tmp $ am start Browser_for_Android_2.3.5_Apkpure.apk
But getting this error
spm8666p1_64_car:/data/local/tmp $ am start Browser_for_Android_2.3.5_Apkpure.apk
Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] pkg=Browser_for_Android_2.3.5_Apkpure.apk }
Error: Activity not started, unable to resolve Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=Browser_for_Android_2.3.5_Apkpure.apk }
Gonna try doing this next pm enable --user 0 package.name.example <<

dunno if this helps in anything but this is the full package list just in case someone is curious
spm8666p1_64_car:/data/local/tmp $ pm list packages
package:com.incall.updateserver
package:com.android.providers.telephony
package:com.huawei.dmsdpdevice
package:com.android.providers.media
package: org.easyweb.browser
package:com.mediatek.location.lppe.main
package:com.njda.carplay
package:com.huawei.nearby
package:com.vecentek.decoreapp
package:com.android.externalstorage
package:com.incall.apps.airconditioner
package:com.zhonghong.radio
package:com.mediatek.ygps
package:com.incall.apps.configservice
package:com.mediatek.engineermode
package:android.car.cluster.loggingrenderer
package:com.android.defcontainer
package:com.incall.welscreen
package:com.iflytek.cutefly.speechclient.hmi
package:com.android.certinstaller
package:com.incall.apps.btphone
package:android
package:video.evs.camera
package:com.incall.coreserver
package:com.android.car
package:com.zhonghong.usb.copy
package:com.chinatsp.tfactoryapp
package:com.iflytek.autofly.launcher
package:com.incall.apps.softmanager
package:com.android.provision
package:com.android.statementservice
package:com.android.providers.settings
package:com.incall.apps.logreport
package:com.android.webview
package:com.incall.apps.filemanager
package:com.bytedance.byteautoservice
package:com.neusoft.na.navigation
package:android.ext.shared
package:com.mediatek.nlpservice
package:com.incall.apps.commonservice
package:android.ext.services
package:com.android.packageinstaller
package:com.incall.service.MediaScanner
package:com.android.inputmethod.latin
package:com.incall.naviadapter
package:com.huawei.hisight
package:com.mediatek.thermalmanager
package:com.chinatsp.dvrcamera
package:com.incall.bluetooth
package:com.incall.apps.setting
package:com.baidu.map.location
package:com.android.settings
package:com.zhonghong.autotest
package:com.google.android.projection.gearhead
package:com.iflytek.autofly.carinfo
package:com.mediatek.lbs.em2.ui
package:com.eryanet.vlink
package:com.incall.apps.diagnose4G
package:com.incall.tboxservice
package:com.iflytek.autofly.platformservice
package:com.incall.interactive
package:com.android.shell
package:com.android.providers.userdictionary
package:com.incall.apps.vehiclesetting
package:com.android.location.fused
package:com.android.systemui
package:com.incall.network
package:com.mediatek.location.mtknlp
package:com.mediatek.mtklogger
package:com.huawei.hiviewlite
package:com.zhonghong.compass
package:com.android.bluetooth
package:com.android.providers.contacts
package:com.chinatsp.dvr.builtin
package:com.incall.radio
package:com.iflytek.autofly.mediagroup

that's great man!
for your issue I believe there 2 options, install luncher and make it default home, or you can look for the circle dot app it stays on your screen and put your favorite apps to show whenever you click on it.

Dude thank you so much for your help ! launcher did end up working
its awesome with wifi and all, pretty much an android device, but you have to do all the steps to get into it, and the screen is partially obscured by the overlay from one of the UI apps, so you cant press back or return, tried disabling but could not do that from the android system, probably i could from ADB.
Android auto is giving me a similar error
i did try to install them through the web browser but no go, although a lot of progress made, still could not fix the apple car play or get android to work.
Man i love troubleshooting
Also i noticed that when i connect an android mobile through USB, its not detected by anything, maybe i should look for an app that acts like android auto and connects to a phone and check what happens. or i am missing something i dunno.

no problem, I searched about the circle is called EasyTouch
try to find apk and install it, it will save you time reaching out to your apps and adding home and back buttons
also try to install google play apk

also install ES file browser, is good file manger and you can install apps directly with it using usb drive

EY3_2023 said:
no problem, I searched about the circle is called EasyTouch
try to find apk and install it, it will save you time reaching out to your apps and adding home and back buttons
also try to install google play apk
Click to expand...
Click to collapse
Easytouch is like magic ! such a good recommendation !
beyond that google play store crashes on startup, maps freezes on startup, waze also, i think some core services that android uses are not installed or something, needs more digging, but overall i found that apkpure is a good alternative for the app store for now.
Android Auto mentions some missing apps but crashes when you try to install them, will try to install them prior and checking again, this was a long journey !

EY3_2023 said:
god knows tried multiple cables
try this pass
aDB36987
Click to expand...
Click to collapse
Did you manage to make it work ?
Which apps did you end up installing ?