'Unfortunately, that is unavailable with this device' - Assistant - OnePlus 6 Questions & Answers

Hey all,
Over the last few months, I haven't been able to get Google assistant to make phone calls or send text messages. All other functions work.
When I say, 'call my wife', or 'send text message to wife', it tells me that function is unavailable.
It used to work flawlessly.
I have changed nothing to cause it. I just woke up one morning and it didn't work.
So far I have tried:
-Factory reset
-clear cache, etc
-Magisk hide on assistant app, call manager, Google play services and google text to speech
I am on latest stable Oos with latest XxX Rom.
The issue started around 3 months ago.
Where should i be looking to fix this?
Thanks in advance for any help.

Does anyone know of any other forums I can post this question? I can't post in the OnePlus forums yet because of new member restrictions. I'm just trying to get more coverage for my issue so that I can get help solving it.

Do you know what day this happened?

spr33 said:
Do you know what day this happened?
Click to expand...
Click to collapse
I'm not sure. It was roughly 3 months ago.

cubic25 said:
Does anyone know of any other forums I can post this question? I can't post in the OnePlus forums yet because of new member restrictions. I'm just trying to get more coverage for my issue so that I can get help solving it.
Click to expand...
Click to collapse
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files DO NOT REBOOT
3. Flash latest oos either 9.0.9 or beta Q is up to you DO NOT REBOOT
4. Flash twrp REBOOT
You'll all set if you need root just flash magisk
Let me know if it worked for you

J0nhy said:
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files
3. Flash latest oos either 9.0.9 or beta Q is up to you
4. Flash twrp
You'll all set if you need root just flash magisk
Let me know if it worked for you
Click to expand...
Click to collapse
I did all this on Sunday hoping that it would fix the issue. It hasn't.
Additional info: I have also just discovered that if I open the assistant app and type in 'call.........' or 'message........' , it says there is no app installed to perform that function.

J0nhy said:
Not sure but that happened to me too but here's what i did
1. Boot into twrp
2. Wipe system, vendor and cache no need to wipe data unless you don't care losing your files DO NOT REBOOT
3. Flash latest oos either 9.0.9 or beta Q is up to you DO NOT REBOOT
4. Flash twrp REBOOT
You'll all set if you need root just flash magisk
Let me know if it worked for you
Click to expand...
Click to collapse
Don't think this will be useful, this is an Assistant issue, reflashing the ROM probably won't help.
cubic25 said:
I did all this on Sunday hoping that it would fix the issue. It hasn't.
Additional info: I have also just discovered that if I open the assistant app and type in 'call.........' or 'message........' , it says there is no app installed to perform that function.
Click to expand...
Click to collapse
Can you check in the settings, under Apps, and Default Apps, if you correctly have a Phone app and an SMS app set as default ? Or maybe the Google App does not have the permissions it needs (Phone Calls and SMS permissions), you could also check that. This is probably a little thing like this, it's 99% sure it's an app or configuration issue.

Both apps are set as default and all apps have all permissions ticked.

I too have the issue and have tried several things with no luck.

I've also been experiencing this. It's been pretty frustrating when trying to use the assistant with android auto.

What ROM are you guys running? I wonder if there is any similarities between our devices.

cubic25 said:
What ROM are you guys running? I wonder if there is any similarities between our devices.
Click to expand...
Click to collapse
I'm on beta 28

Well today I installed Android Auto, I was also able to install Google speech to text and bam, I'm able to use Okay Google to text and call again.

Related

GApps not working with CM7 ROM

I installed the CM7 port and the GApps, but my Google apps don't show up. I've tried reflashing the ROM and the GApps package over and over and clearing all the caches to no avail. Help?
you have to flash GAPPS separately. refer original post of CM7 thread and you will find the link
That's what I did. I flashed the ROM then I flashed the GApps, but they're still not showing up.
Ok that's weird. Can you pinpoint the exact steps you performed from download to copying to erasing to booting up? Each and every step please.
Sure thing.
I downloaded the ROM and the GApps package from the ROM's thread and stored the files on my desktop. While the downloads were going, I booted my phone into recovery and mounted the USB storage. I then plugged the phone into my computer and copied the files over before ejecting the USB device and unplugging the phone. I then wiped the user data, the cache, and the Dalvik cache and flashed the ROM, then, straight after, the GApps. I wiped the user data again just to be safe then rebooted back into the OS.
After it didn't work the first time, I downloaded the GApps again and copied them to my phone again, this time within the OS instead of the recovery. Rebooted, wiped user data, cache, and Dalvik cache, flashed the GApps, and nothing.
Not being sure if it was the ROM or the GApps package, I flashed the MIUI beta then flashed the GApps (using the same sequence of steps mentioned above) and it still didn't work, so it doesn't seem to be specific to CM7.
Ok try these steps:
1. Download the ROM
2. Download GApps from here: http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
3. Wipe the big 3's (user data, cache and dalvik-cache).
4. Flash the ROM.
5. Flash Gapps.
6. Boot without erasing anything.
I followed your instructions exactly but I still have the same problem.
Interestingly, if I go into the list of installed applications in the settings, Market (but no other Google apps) shows up but it's greyed out and I don't have any options to run it or anything.
dftba said:
I followed your instructions exactly but I still have the same problem.
Interestingly, if I go into the list of installed applications in the settings, Market (but no other Google apps) shows up but it's greyed out and I don't have any options to run it or anything.
Click to expand...
Click to collapse
Crap. Something's really not right. Can you give it a try with the SuperOSR ROM? Need to see if it's specific to the CM build.
EDIT: Can you try searching for the Market .apk file around the forum and install it manually? It should be somewhere in Themes&Apps section. Give that a try before trying with the SuperOSR ROM. Wipe, re-flash ROM, flash Market.apk, reboot.
Reason: the gapps provided by CM team are old (v2 market) and it might be that Google does not support v2 anymore since they've switched to Play Store. (not sure).
I did try with the MIUI ROM and the same thing happened, I don't think it's specific to your ROM build. Perhaps my phone just doesn't like Cyanogen's GApps package? No idea why that would be though.
Anyway, I did as you suggested and installed an APK and it worked! I found this one on Redmond Pie and put in the SD and installed it with the file browser on the phone. Seems to work fine so far
dftba said:
I did try with the MIUI ROM and the same thing happened, I don't think it's specific to your ROM build. Perhaps my phone just doesn't like Cyanogen's GApps package? No idea why that would be though.
Anyway, I did as you suggested and installed an APK and it worked! I found this one on Redmond Pie and put in the SD and installed it with the file browser on the phone. Seems to work fine so far
Click to expand...
Click to collapse
Awesome!
While you're here, a bug I've noticed that's only popped up on your ROM is that, when I turn the phone off, sometimes the orange light stays on and the phone's completely frozen up until I pull the battery. It's only happened twice but I thought it might be something to look into.
Other than that, it's very good! I'm enjoying it, keep up the good work
dftba said:
While you're here, a bug I've noticed that's only popped up on your ROM is that, when I turn the phone off, sometimes the orange light stays on and the phone's completely frozen up until I pull the battery. It's only happened twice but I thought it might be something to look into.
Other than that, it's very good! I'm enjoying it, keep up the good work
Click to expand...
Click to collapse
It's a CWM based problem. Update your CWM recovery to the latest one from the CWM thread in the Dev section and you are good to go.
Way too many CWM's in two sentences..
I'll do that now, cheers
Glad to know you are up and running, but it's still quite strange. Every time I flashed CM7.2 (it it was quite a lot of times GApps were there, Market included. Just running the Market app would actualize it to Play Store automagically.
Of course, as Alex says, it may not be supported by Google anymore, but still you should have gmail, etc from the zip file even without a working Play Store...
The issue was probably related to CWM, if you have an old enough version it could be messing up with the zip internals, but sometimes it's just anything else... (I installed the first CM9 alpha rom w/o problem, the second one wouldn't install, one week later, doing exactly the same with the same zip file, it installed flawlessly)
It may also be related to the specific terminal, I have noticed that depending on the device type (country of release, free or network operator locked, and so on) terminals behave a little bit different in some aspects (e.g. my GPS stopped working after unlocking the bootloader and was only fixed when I reflashed the radio firmware after getting S-OFF; and now, with the CM9 alpha, my keyboard won't get backlight while it's dark outside but adxl's is working fine, which is bad for debugging purposes, of course )
If you could make a backup and install SuperOSR and see if everything works fine the first time (even if you go back to CM afterwards, as I did) it may help to understand the issue better... Or maybe just posting your phone's specific data (model, build, country, etc) may give us a hint.
We know that free UK terminals are somewhat different to Spain free terminals, and those are a bit different from Orange or Yoigo locked terminals... It may be related to hardware batches out fro the factory, who knows?
Enjoy your ChaChaCha!
I think the problem was my CWM in the end. After I upgraded it (that alone included some trial and error, eventually the fastboot method worked) the GApps zips worked fine.
So if anyone else has this problem, check your CWM version and upgrade it if you need to
Can i Upgrade CWM without any change of my current OS ?
i actually couldnt go to Market after i flashed GServices. I downloaded newest Google Play in HTC Chacha apps, installed it and it work until now (of course wit GService flashed before).
Btw, how can i check my current CWM. Thanks!
Similar problem...
dftba said:
I installed the CM7 port and the GApps, but my Google apps don't show up. I've tried reflashing the ROM and the GApps package over and over and clearing all the caches to no avail. Help?
Click to expand...
Click to collapse
Hello there!
I've came by to add my issue, similar to yours.
I was on CM7 too and wanted to try the SuperOSR ROM. I used the common steps for flash it (all cache Wiping and factory reseting, ROM installing, Gapps installing), rebooting my phone, connect it with a Google account, launched Gmail and then when I've arrived at a certain level of my mails, the app crash...
For the Google Play app, I've got a server connexion error...
It's like if all the Google's framework was here but totally not stable...
I've tried with an another ROM, the MUI ROM and everything works...
Like I said, I came from the CM7 ROM wich was working...
Alex C. said:
Ok try these steps:
1. Download the ROM
2. Download GApps from here: http://cmw.22aaf3.com/gapps/gapps-gb-20110828-signed.zip
3. Wipe the big 3's (user data, cache and dalvik-cache).
4. Flash the ROM.
5. Flash Gapps.
6. Boot without erasing anything.
Click to expand...
Click to collapse
I thinks I will try to do those steps and if it does not work...
dftba said:
I did try with the MIUI ROM and the same thing happened, I don't think it's specific to your ROM build. Perhaps my phone just doesn't like Cyanogen's GApps package? No idea why that would be though.
Anyway, I did as you suggested and installed an APK and it worked! I found this one on Redmond Pie and put in the SD and installed it with the file browser on the phone. Seems to work fine so far
Click to expand...
Click to collapse
... this one.
After that you can install from market any google app you want (talk, search, etc.).
Alex C. said:
After that you can install from market any google app you want (talk, search, etc.).
Click to expand...
Click to collapse
Strange... Was not working when I flashed the Gapps but worked when I've only flashed the ROM...
Alex C. said:
Ok try these steps:
1. Download the ROM
2. Download GApps (your link)
3. Wipe the big 3's (user data, cache and dalvik-cache).
4. Flash the ROM.
5. Flash Gapps.
6. Boot without erasing anything.
Click to expand...
Click to collapse
Hi, I registered in this forum just to say THANK YOU SO MUCH! I was searching for that appropriate GApps for the CM7 I installed previously with the GApps for Ginger Bread (not the same with this link you posted) and it gave me a headache too. I tried flashing for 3x & the Gapps were not working. Then I tried this link and VOILA! Now my smile is from ear to ear.. so SALAMAT! (Tagalog word for THANK YOU). I'm from Philippines anyway. I bookmarked this page for future reference. A million thanks to XDA Developers and it's helpful members & thanks for welcoming me even I'm a noob.. :laugh::laugh:

ADMIN: delete me

Answered in previous post. Please delete.
go into developer options and set root to apps and adb.
to enable developer options click 7x on buildnumber.
Android-Andi said:
go into developer options and set root to apps and adb.
to enable developer options click 7x on buildnumber.
Click to expand...
Click to collapse
Really? I did put CM10.2 on my phone, really like it. So I checked your recommendations on the phone. Yeah, just what you said, root adb and applications. My phone is enabled and I never lost root on it. You get a Thanks.
Now how to update to 10.2 on the Tab. CWM only lets you flash one zip at a time where Safe Strap will allow you to stack the rom and gapps. I got CWM Pro and don't see anyway to flash more than one zip at a time and this gave a system 7 error. The update is there in about phone, if I allow unstable and nightlies, but installing it dumps me into recovery. Safe Strap on phone, piece of cake. One zip at a time in ClockworkMod, not so easy. Any ideas?
Awesome. I went into CWM Rom Manager and decided to use TWRP instead of CWM, used the update in Settings/About Phone/Update. It did work! But everything is crashing, I had to install new gapps. So I went back and flashed the new gapps. Problem is, playstore is broke, errors everytime it tries to install or update, would not connect at all until new gapps. Wiped data, still not working right. Others had this problem, any ideas on how to restore playstore functionality? Thanks, you guys rock!
Found the answer here, and it works!
I tried everything form everywhere. Nothing worked until I did this. Following the steps below.
RPC:AEC:0 error is known as CPU/RAM/Device/Identity failure.
Only possible way you can follow to get rid off this error is,
Go to settings ? application ? Play Store ? Clear Data & Clear Cache.
Go to accounts ? Google ? Remove account.
Reboot device.
edited Feb 13 at 8:44
Ivan Feric
answered Feb 13 at 8:23
Worked for me, Google updating away. This is awesome everybody.
If I helped, click the Thanks Button.

[ROM] [MEDIAPAD X2] [5.1.1] B112 Rooted with GAPPS

Rom depreciated, op removed.
Thanks
ajsmsg78 said:
Here is a stock rooted B106 ROM with the Google Play Store and Contacts Sync preinstalled. This is great for those of you who have a hard time getting the Google Apps to work. Flash this in TWRP. Thanks to the HRT Team for their hard work. Their thread is located here: http://cn.club.vmall.com/thread-5911144-1-1.html
Features & Mods:
Removed unstall_apk.xml files from the cust folder
Removed mms_config.xml files from the cust folder
Added in the Google Play Store & Google Contacts Sync Adapter
SuperSU is installed by default
The ROM is also slightly debloated. Some of the Huawei bloat was removed
Download Link:
https://drive.google.com/open?id=0B5I_q70mNuR4cGJTaTN3N3Z0Tlk
Steps to flash. Follow these instructions or the ROM flash will fail:
1) Boot into TWRP
2) Do a factory reset
3) Reboot recovery
4) Mount System, Cache, Data, cust, splash2 and newsys
5) Flash the ROM
6) Reboot System
7) Profit!
This should work regardless of what build you are currently on (B106, B107, B108, B109)
Click to expand...
Click to collapse
I had to uncheck "System, Cache, Data, cust, splash2 and newsys" in TWRP to get this to install...
Pre-requisite to flash
ajsmsg78 said:
Here is a stock rooted B106 ROM with the Google Play Store and Contacts Sync preinstalled. This is great for those of you who have a hard time getting the Google Apps to work. Flash this in TWRP. Thanks to the HRT Team for their hard work. Their thread is located here: http://cn.club.vmall.com/thread-5911144-1-1.html
Features & Mods:
Removed unstall_apk.xml files from the cust folder
Removed mms_config.xml files from the cust folder
Added in the Google Play Store & Google Contacts Sync Adapter
SuperSU is installed by default
The ROM is also slightly debloated. Some of the Huawei bloat was removed
Download Link:
https://drive.google.com/open?id=0B5I_q70mNuR4cGJTaTN3N3Z0Tlk
Steps to flash. Follow these instructions or the ROM flash will fail:
1) Boot into TWRP
2) Do a factory reset
3) Reboot recovery
4) Mount System, Cache, Data, cust, splash2 and newsys
5) Flash the ROM
6) Reboot System
7) Profit!
This should work regardless of what build you are currently on (B106, B107, B108, B109)
Click to expand...
Click to collapse
Hi
Before doing the above must the 703L be already on stock B106 ROM or can flash this directly from B015 ?
kpcheang2 said:
Hi
Before doing the above must the 703L be already on stock B106 ROM or can flash this directly from B015 ?
Click to expand...
Click to collapse
It should work if you are on b015. Make sure you do a backup in TWRP first. The ROM flashes the boot, system and cust.
twrp version
ajsmsg78 said:
It should work if you are on b015. Make sure you do a backup in TWRP first. The ROM flashes the boot, system and cust.
Click to expand...
Click to collapse
Which twrp version did you use successfully for this ? The 5.1 or the 5.1.1 ?
kpcheang2 said:
Which twrp version did you use successfully for this ? The 5.1 or the 5.1.1 ?
Click to expand...
Click to collapse
I'm using the 5.1.1 one.
Steamer2499 said:
I had to uncheck "System, Cache, Data, cust, splash2 and newsys" in TWRP to get this to install...
Click to expand...
Click to collapse
I unchecked all these, as well. Also, I had the message "error retrieving information from server rpc s-7 aec-7" when attempting to install anything from the Google Play store. In case anyone else runs into this, I followed the directions from this site:
http://www.fixerrs.com/2015/02/error-retrieving-information-from-server-rpc-s-7-aec-7.html
After the reboot, I had to log back into my Google account through the Play Store. I wasn't able to add the account under Settings->Accounts->Google.
Otherwise, so far so good. Thanks for the ROM!
wpennhokie said:
I unchecked all these, as well. Also, I had the message "error retrieving information from server rpc s-7 aec-7" when attempting to install anything from the Google Play store. In case anyone else runs into this, I followed the directions from this site:
http://www.fixerrs.com/2015/02/error-retrieving-information-from-server-rpc-s-7-aec-7.html
After the reboot, I had to log back into my Google account through the Play Store. I wasn't able to add the account under Settings->Accounts->Google.
Otherwise, so far so good. Thanks for the ROM!
Click to expand...
Click to collapse
When I tested the ROM before I posted it I didn't have that problem. I'll install it again a few times to see if I can recreate that problem. Did you do a wipe before you flashed or did you flash it over an already installed ROM?
wpennhokie said:
I unchecked all these, as well. Also, I had the message "error retrieving information from server rpc s-7 aec-7" when attempting to install anything from the Google Play store. In case anyone else runs into this, I followed the directions from this site:
http://www.fixerrs.com/2015/02/error-retrieving-information-from-server-rpc-s-7-aec-7.html
After the reboot, I had to log back into my Google account through the Play Store. I wasn't able to add the account under Settings->Accounts->Google.
Otherwise, so far so good. Thanks for the ROM!
Click to expand...
Click to collapse
None of the X2 ROM's I have ever run was I able to add a Google account through Accounts. For some reason it just doesn't show up even after I added GoogleAccountManager.apk. To add a second account go to settings, backup and reset, hit Backup account and hit Add account.
ajsmsg78 said:
It should work if you are on b015. Make sure you do a backup in TWRP first. The ROM flashes the boot, system and cust.
Click to expand...
Click to collapse
I managed to get the b015 stock ROM working on my 702L but this is as far as it gets.
I flashed the 5.1.1. twrp_cn but it couldn't reboot into recovery and instead it went on a boot loop.
I then flashed 5.1 twrp_cn (previous version before Android 5.1.1) and managed to get into custom recovery from b015 on my 702L. Using this twrp I then flashed this custom B106 rom and it inidcated success.
However after reboot it simply went into boot loop. Not sure is it because my device is still 702L though I managed to get b015 703L stock rom on my 702L. Neither could I flash into stock B106.
kpcheang2 said:
I managed to get the b015 stock ROM working on my 702L but this is as far as it gets.
I flashed the 5.1.1. twrp_cn but it couldn't reboot into recovery and instead it went on a boot loop.
I then flashed 5.1 twrp_cn (previous version before Android 5.1.1) and managed to get into custom recovery from b015 on my 702L. Using this twrp I then flashed this custom B106 rom and it inidcated success.
However after reboot it simply went into boot loop. Not sure is it because my device is still 702L though I managed to get b015 703L stock rom on my 702L. Neither could I flash into stock B106.
Click to expand...
Click to collapse
Did you wipe before you flashed or did you dirty flash over your existing ROM? You may have to wait until the 702L gets Android 5.1.1 then try flashing the 703L ROM after that.
ajsmsg78 said:
When I tested the ROM before I posted it I didn't have that problem. I'll install it again a few times to see if I can recreate that problem. Did you do a wipe before you flashed or did you flash it over an already installed ROM?
Click to expand...
Click to collapse
I did the factory reset, per the instructions. I didn't wipe anything beyond that.
After a few days, everything has continued to be great. It's probably just my imagination, but I feel this ROM is running much faster and smoother than the KangVIP ROM I was using previously. Of course, that ROM was based on B108, so that might have been the issue, too.
wpennhokie said:
I did the factory reset, per the instructions. I didn't wipe anything beyond that.
After a few days, everything has continued to be great. It's probably just my imagination, but I feel this ROM is running much faster and smoother than the KangVIP ROM I was using previously. Of course, that ROM was based on B108, so that might have been the issue, too.
Click to expand...
Click to collapse
Yeah it's a bit smoother than KangVIP for me too. It's a lot more debloated than KangVIP so that's why it's faster. I installed it a few times and the Play Store worked for me the first time on each reload. I'm hoping to get a b109 version so I can mod it as well.
I have had a few minor issues pop up over the last few days, and I was wondering if anyone else has had similar issues or solutions.
1. I listen to audiobooks via the Overdrive app during my commute and trudge from the parking lot to work. In the past, when I've shut off the bluetooth connection, the audio has stopped. I have to do this when switching between my headset and the car stereo and vise versa. Lately, I've noticed when I shut off the devices, my audio pauses for a second or so, then starts playing over the phone speaker. Since it's both devices, I don't believe it's an issue with the devices. Oddly enough, autoplay starts up just fine when I connect to a device, but auto-pause (auto-stop?) doesn't.
2. The other issue is alarms. I'm using Google clock, mostly so I can easily move my alarms between phones. In the past, when I've re-imaged my phone and restored the Clock app and data via TB, I've had to go in and toggle the alarms off and on to get them to work the first time. After that, they worked fine after every reboot. Lately, I've noticed when I reboot, none of my alarms work. They don't show as pending in the notification bar, on either the left or right side. Once I go in and toggle them on and off, they work fine again until the next reboot. The problem is that I run a Llama task around 3:00 AM every morning to reboot the phone (Auto Reboot stopped working for me). So, every morning I have to go in and toggle them again. Once I do, any pending alarms show up on the left side of the notification center, and I get notification that I have alarms set on the right side as well. I have the Huawei clock app frozen via TB, but unfreezing it didn't stop the issue. I guess I can stop rebooting every day, but I'd prefer not to. As for the setup, I've double checked, and Clock is added to both Protected Apps and Startup Apps. I even tried setting the clock app to open on reboot via Llama, and while it opened up, the alarms still didn't work until I toggled them.
Thanks in advance for any help.
---------- Post added at 04:53 PM ---------- Previous post was at 04:38 PM ----------
As a quick follow up, the Bluetooth appears to be an app-specific issue. I was just trying it with some other apps while I had the phone connected to a Bluetooth speaker at home. The other apps paused just fine. I finally found audio player settings (not in the General settings, but only when the audio player is being used) in the Overdrive app. It had a toggle to turn the feature on and off. I toggled it, and it seems to be working now.
ajsmsg78 said:
Yeah it's a bit smoother than KangVIP for me too. It's a lot more debloated than KangVIP so that's why it's faster. I installed it a few times and the Play Store worked for me the first time on each reload. I'm hoping to get a b109 version so I can mod it as well.
Click to expand...
Click to collapse
AJ
Is there any word on b105 or greater on the 702?
To follow up on the alarm issue I was having above, I uninstalled the Google clock app, reinstalled it from the Play store, and the restored the data only from TB. After a couple if test reboots (full and hot), it appears to be sticking. I'll keep my fingers crossed.
And just to say it one more time, this ROM is still working great for me.
Rudolpht said:
AJ
Is there any word on b105 or greater on the 702?
Click to expand...
Click to collapse
I don't have a 702L to fool around with or I'd try doing it myself.
I've been playing around with and reading a lot of what it takes to make ROM'S. I made a stock B109 TWRP flashable Debloated ROM with Gapps included. I'm testing it out now and will post it as soon as everything is working correctly. The only thing not working at the moment is the SIM card switching.
ajsmsg78 said:
I've been playing around with and reading a lot of what it takes to make ROM'S. I made a stock B109 TWRP flashable Debloated ROM with Gapps included. I'm testing it out now and will post it as soon as everything is working correctly. The only thing not working at the moment is the SIM card switching.
Click to expand...
Click to collapse
Great !
I was wondering whether the clue to the SIM card switching could lie on certain prop files ? I can't recall exactly the full file name but I even saw "Dual SIM Settings" being associated with "dsdsxxxx" file ?
I asked because if you recall in my other post few days back I managed to do OTA upgrade from stock B106 to B109 on my 702L so I'd think the radio baseband kernell would have been flashed properly albeit on a different hardware.
And the fact that my 702 continues to work fine in dual SIM mode......

[FIRMWARE-ONLY][MI MIX][LITHIUM] Developer ROM Firmware

News :
Starting today, i'll just upload the firmware if it has a change in it.
So you know there's no need to update the firmware if there's no change in it, save the hassle.
Tips :
* I've added checksum file for each firmware-only files in google drive, so you guys can see what's changed on every firmware-only release.
* If you experience sim card not detected after flashing firmware, don't worry, it's normal. do this, plug out and plug in your sim card tray, and restart your device.
[FIRMWARE-ONLY]
Recommended : 9.2.21
Latest : 9.2.21
https://drive.google.com/drive/folders/1PGmzEcmgG0XhRB7110CDDTgMwmw4N3MM
[ROMS - CHINA]
http://www.miui.com/download-323.html
[ROMS - GLOBAL]
http://en.miui.com/download-317.html
yep i believe the Miui10 is in Alpha and currently being tested by a closed group of users. we should see public Beta releases towards the end of June.
Im just curious if there is any difference in battery consumption to previous version of MIUI.
I've tried it a couple of days ago. There are some visual changes like new notifications panel UI, recents UI, In-call UI etc. A bit more IOS-ish as some say.
First of all, if you consider flashing it;
- You need the Raupe/Blunden twrp to flash it, other recoveries end up with error 7.
- After flashing this build; twrp will ask for a decrypt password and no password will be correct. So your internal storage won't be mounted on twrp no way to fix it at the moment.
- Magisk 16.4 is able to root it, don't know about previous ones.
- If you consider flashing other roms, you have to do factory reset(format data) to get your internal be able to mount on twrp again.
- It doesn't have google apps as it's China specific, so you need to install google apps manually by Google installer apk or there are zip files for miui 10 ported gapps which give force closes randomly.
- Can be a daily driver since all is working.
- Xposed won't work.
Other than these hick ups, it's good initial build. Fast and smooth, can't tell about battery life since I haven't used it for a long time. There are secondary releases(8.6.5) for some devices so can be around for Mix too. Cheers.
Sent from my Xiaomi Mi Mix using XDA Labs
Konstantine34 said:
I've tried it a couple of days ago. There are some visual changes like new notifications panel UI, recents UI, In-call UI etc. A bit more IOS-ish as some say.
First of all, if you consider flashing it;
- You need the Raupe/Blunden twrp to flash it, other recoveries end up with error 7.
- After flashing this build; twrp will ask for a decrypt password and no password will be correct. So your internal storage won't be mounted on twrp no way to fix it at the moment.
- Magisk 16.4 is able to root it, don't know about previous ones.
- If you consider flashing other roms, you have to do factory reset(format data) to get your internal be able to mount on twrp again.
- It doesn't have google apps as it's China specific, so you need to install google apps manually by Google installer apk or there are zip files for miui 10 ported gapps which give force closes randomly.
- Can be a daily driver since all is working.
- Xposed won't work.
Other than these hick ups, it's good initial build. Fast and smooth, can't tell about battery life since I haven't used it for a long time. There are secondary releases(8.6.5) for some devices so can be around for Mix too. Cheers.
Click to expand...
Click to collapse
I'm willing to give this a shot, thanks for the input ??
Ok trying it now and everything seems to be working good. A little laggy at the moment so I'm just letting it set in. I was hoping the camera would've gotten updated but same old crappy camera software from previous MIUI firmware. Hopefully when they do release the final version we'll get a updated camera but all in all this is a keeper till we get updated version on here, hopefully...
juggaknot77 said:
Ok trying it now and everything seems to be working good. A little laggy at the moment so I'm just letting it set in. I was hoping the camera would've gotten updated but same old crappy camera software from previous MIUI firmware. Hopefully when they do release the final version we'll get a updated camera but all in all this is a keeper till we get updated version on here, hopefully...
Click to expand...
Click to collapse
Have face unlock maybe?
zrzatore said:
Have face unlock maybe?
Click to expand...
Click to collapse
Haven't tried that but I'll look into it today and report back.
---------- Post added at 04:27 PM ---------- Previous post was at 03:36 PM ----------
Ok going through settings and as far as I can tell I don't see face unlock feature. I highly doubt the mix will get seeing as how old it is now, I never use it anyway on other devices so it's not a big deal to me. Everything is running very smooth and fast, I'm liking the Android P style look a lot, more than how it looks on the pixel but that's just me.
How did you go past decrypt after flashing via TWRP?
Wmateria said:
How did you go past decrypt after flashing via TWRP?
Click to expand...
Click to collapse
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Sent from my Xiaomi Mi Mix using XDA Labs
Konstantine34 said:
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Click to expand...
Click to collapse
Oh yes yes, I always use OTG just in case. Thanks for the info.
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Konstantine34 said:
You just cancel it and internal storage will be unable to use on twrp. If you flash other things, you need to do it by an OTG.
Sent from my Xiaomi Mi Mix using XDA Labs
Click to expand...
Click to collapse
doesn't it will be solved just by formatting data?
fatouraee said:
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Click to expand...
Click to collapse
i think you should flash this file in twrp :
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
after that the recovery shouldn't get replaced anymore.
That's weird I don't have any issues seeing my storage in TWRP, everything works.
juggaknot77 said:
That's weird I don't have any issues seeing my storage in TWRP, everything works.
Click to expand...
Click to collapse
really? can you show us the screenshot of the storage in twrp? what twrp version did you use? what other procedure did you perform in order not to encrypt storage? thanks
Thanks. That seems to have worked.
fatouraee said:
I installed it, but I keep loosing the recovery, when I reboot it goes to the Miui recovery.
Is there a way to disable the factory recovery overwriting the twrp.
Appreciate any help.
Thanks.
Click to expand...
Click to collapse
You need to delete
- system/etc/recovery-resource.dat
- system/bin/install-recovery.sh
- system/recovery-from-boot.p
rhong said:
really? can you show us the screenshot of the storage in twrp? what twrp version did you use? what other procedure did you perform in order not to encrypt storage? thanks
Click to expand...
Click to collapse
Honestly I didn't do anything different, followed the instructions on the 1st post, everything works on my end.
juggaknot77 said:
Honestly I didn't do anything different, followed the instructions on the 1st post, everything works on my end.
Click to expand...
Click to collapse
i think he should need to format his Data and Internal Storage.
i can't remember the detail, but i once encountered this too, and i read that something about F2FS not supported or whatsoever.
heindrix said:
i think he should need to format his Data and Internal Storage.
i can't remember the detail, but i once encountered this too, and i read that something about F2FS not supported or whatsoever.
Click to expand...
Click to collapse
It's weird I didn't format anything, just updated twrp, backed up my rom, wiped everything, installed new miui 10, installed magisk, wiped cache and dalvik and everything works perfectly...

OB4 - com.android.phone keeps stopping?

Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
krakout said:
Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
Click to expand...
Click to collapse
I'm on latest beta 4 using a IN2025 OP8Pro. I used the full ROM not the incremental update to upgrade from OB3. I am rooted also. No issues you are experiencing. Sounds like you need to flash the full ROM from fastboot mode and complete wipe for a clean install and start from there.
./
Thanks for the input. How big is the partial update? Because the one I flashed was almost 3GB...
So, no real way to downgrade to OB3 again?
3gb is full ROM not the incremental update.
So that's not the explanation then... I wonder if factory resetting will fix the problem?
Any ideas anyone?

Categories

Resources