Hi,
I'm looking a way to enable AHSA protocol to device that are on official Android 10 with official updates from manufacturer
Last year Google has annouced Android 10 will support Hearing Aids with ASHA Protocol, specification are open, but i think integration to Android 10 phone is not mandatory
I have a Oneplus 5 and recently Android 10 has been released out to this device by OnePlus
Sadly, i can't stream music directly to my hearing aids.
As far i know Pixel 3 and Samsung devices are compatible, i've tested with a Samsung S10e and this is working great.
Google provide a technical specification for ASHA Protocol, i dont know if this for dev or something ? https://source.android.com/devices/bluetooth/asha
So what i've found so far when playing around with my OnePlus 5 :
- I've decompilled the bluetooth apk from my OnePlus 5 phone and there some files related to hearing aids in the bluetooth apk bluetooth.app/sources/com/android/bluetooth/hearingaid
- Found a file text in /System/etc/bluetooth/
in bt_profile.conf at the end of the file
Code:
#Hearing Aid profile and its configurable features
# hearing_aid_support with default value false
[HEARING_AID]
[B]hearing_aid_support = false[/B]
I've rooted my device with Magisk and i've tried to change to "true" and reboot but changes are reverted back maybe because /system is read-only ?
i want to know if someone can dump the file from a pixel 3 or a Samsung S10/S20 device and share here ?
@johnstinks
Only to have mentioned it:
Android's hearing-aid setting is stored in Android's settings.db under System: It's either 0 or 1.
https://android.googlesource.com/pl...e/+/master/core/res/res/values/config.xml#131
Try setting this to true using an overlay?
sorry .., i've no idea how to do, i've never compiled a rom or anthing
my message is a bottle sent to the sea, sharing idea to enable / force the support for hearing aids for phones on Android 10.
I would also be interested in a way to activate this in custom roms. I'm waiting until it's more widely available before I get my next phone
Bumping up this thread. My dad just received his new hearing aid, and initially the audiologist told us direct streaming is only supported on iPhone, but upon closer checking, I found that selected Android phone models are also supported. Sadly, his Huawei P30 Pro is not on the list.
I tried pairing his hearing aids with my sister's Samsung S10 and it worked like a charm, it even has the hearing aid icon beside the bluetooth device. Although the P30 Pro supports Bluetooth 5 and has Android 10, it doesn't recognise the hearing aid.
Hoping that some experts here can share if it's as simple as rooting and enabling the setting, or is there something in the bluetooth APK that needs rework in order for the hearing aid function to work?
Hello,
I need this feature really, too.
Does someone got a way to enable it on a rooted smartphone?
Best regards
bump !
any idea, maybe with magisk module we can enable the feature ?
Best Regards.
Trying to find the solution for my son with his Xiaomi Black Shark 3, anyway so far I didnt find any ASHA solution, so I am going to check Phonak hearing aid which should support BT connection via A2DP and HFP, so it could be temoporary workaround without ASHA support on phone (seems to just on few Samsung and Google models at the moment). Anyway ASHA is final solution of course, all advices would be really appriciated.
On my OnePlus 5 i tried a custom rom called "ArrowOS" this rom does have a experimental flag "settings_bluetooth_hearing_aid" i enabled this flag and i have hearing aids support !
Now i have to found what actually does this flag when i enable it. ( what file is modified)
here some link from the android source code where the flag is found:
if we understand how to enable the feature we can maybe create a magisk module that enable ASHA for any phone on Android 10-11
https://android.googlesource.com/pl.../core/java/android/util/FeatureFlagUtils.java
https://android.googlesource.com/pl...c/com/android/settings/core/FeatureFlags.java
johnstinks said:
On my OnePlus 5 i tried a custom rom called "ArrowOS" this rom does have a experimental flag "settings_bluetooth_hearing_aid" i enabled this flag and i have hearing aids support !
Now i have to found what actually does this flag when i enable it. ( what file is modified)
here some link from the android source code where the flag is found:
if we understand how to enable the feature we can maybe create a magisk module that enable ASHA for any phone on Android 10-11
https://android.googlesource.com/pl.../core/java/android/util/FeatureFlagUtils.java
https://android.googlesource.com/pl...c/com/android/settings/core/FeatureFlags.java
Click to expand...
Click to collapse
Hi I just came across this post as I also want to enable ASHA on an 5t. Does it still work for you with ArrowOS?
know how to enable this feature???
I'm adding my name to the list of folks that want to do this as well (I have an Umidigi A9, but it sounds like the same basic issue applies).
johnstinks said:
if we understand how to enable the feature we can maybe create a magisk module that enable ASHA for any phone on Android 10-11
Click to expand...
Click to collapse
This would be really great.
Following. Thix is really interesting
As ASHA is mainly enabled on the software side (given your hardware matches the requirements), does this mean that custom ROMs on Android >= 10 supports hearing aids streaming ?
As soon as I received my Widex Moment headset, I have been using a hearing aid since I was a child, I feel very sad living in a world where technology was for everyone, adding walls for the sake of money, back to top, I also use the Redmi Note 9 Pro which uses Android 10 and BLE but doesn't pair, I tried a lot of things. Why should I have to buy a new phone instead of fixing it, 2 years have passed and they have not fix it or update about this. I have spoken with Widex & Xiaomi support, the 1st one told me that will add more mobile devices to his list, the 2nd one seems not to be so interested since he does not reply to my email. Once again I feel so bad, I hope someone will can give a solution to that.
I will try Service and Feedback from my phone also
johnstinks said:
On my OnePlus 5 i tried a custom rom called "ArrowOS" this rom does have a experimental flag "settings_bluetooth_hearing_aid" i enabled this flag and i have hearing aids support !
Now i have to found what actually does this flag when i enable it. ( what file is modified)
here some link from the android source code where the flag is found:
if we understand how to enable the feature we can maybe create a magisk module that enable ASHA for any phone on Android 10-11
https://android.googlesource.com/pl.../core/java/android/util/FeatureFlagUtils.java
https://android.googlesource.com/pl...c/com/android/settings/core/FeatureFlags.java
Click to expand...
Click to collapse
Below adb command enabled the hearing aid option in my rooted realme x running on Android 11 device but could not stream audio to hearing.
adb shell settings put global settings_bluetooth_hearing_aid true
Alpha78 said:
Bumping up this thread. My dad just received his new hearing aid, and initially the audiologist told us direct streaming is only supported on iPhone, but upon closer checking, I found that selected Android phone models are also supported. Sadly, his Huawei P30 Pro is not on the list.
I tried pairing his hearing aids with my sister's Samsung S10 and it worked like a charm, it even has the hearing aid icon beside the bluetooth device. Although the P30 Pro supports Bluetooth 5 and has Android 10, it doesn't recognise the hearing aid.
Hoping that some experts here can share if it's as simple as rooting and enabling the setting, or is there something in the bluetooth APK that needs rework in order for the hearing aid function to work?
Click to expand...
Click to collapse
In the same boat here, with same phone. I am about to get cochlear implant activated.
The problem with P30Pro afaik is that Huawei have disabled unlocking of our phones meaning we will never get custom roms or install 'hacks' which is pretty ****.
One would think after all these years of ASHA protocol spec being available it would be implemented more, but no. Outside Pixel, Samsung and Apple its pretty dead in the water and I don't know why since it appears to be just editing one or two lines of code to activate it.
At this stage we can only petition to Huawei to enable this feature.
johnstinks said:
bump !
any idea, maybe with magisk module we can enable the feature ?
Best Regards.
Click to expand...
Click to collapse
jokergermany said:
This would be really great.
Click to expand...
Click to collapse
hi,
some news for the OnePlus5T and the ASHA ?
Please, if you can help me for my hearing aid.
My phone is Root, (twrp and Magisk )
Related
Hi all
We use a few rugged android devices at work as glorified GPS and mapping units. They work great however today I found out that our main data collection service is updating their android application to use TLSv1.2. From my research it looks like all android devices beyond API level 16 (Jellybean) CAN support TLSv1.2, however it is not turned on by default (whatever that means) before API level 20/21 (KitKat wearable/Lollipop). We have devices running 4.1.1, 4.2.1 and 4.4.4.
There is literally zero chance of getting these devices upgraded to Lollipop. They are made by Getac and Aspera - both small companies. Anyone that uses rugged devices knows that you trade in your access to updates and custom roms etc when you opt for one. They are too much of a niche product to attract developers and the manufactures just want a stable device, not the latest and greatest. They also generally run lower end specifications, so updating to newer OS is not always desired. We have a Getac z710 (http://us.getac.com/tablets/Z710/features.html), one Aspera R5 (http://asperamobile.com/products/aspera-r5/) and three Aspera R6s (http://asperamobile.com/products/aspera-r6/). I am not even sure if they have root solutions available for them...
So does anyone out there with a kind heart and some knowledge want to help see if there is anything that can be done on my end to turn on support for TLSv1.2? Here is some stuff I found so far, but most of it seems like it needs to be done on the server side, not client side.
http://stackoverflow.com/questions/24357863/making-sslengine-use-tlsv1-2-on-android-4-4-2
http://www.jordanrejaud.com/android/2015/09/19/android-tls-ssl-engine.html
None of these devices are rooted, so everything needs to be done via adb, or i need a root solution...
bump...
Did you ever find a solution for this? I'm trying looking into this myself but haven't found anything that would modify it for the whole OS, only something that would require modifying the source code for an app.
I have the same problem/question:
GetBackersBH said:
Did you ever find a solution for this? I'm trying looking into this myself but haven't found anything that would modify it for the whole OS, only something that would require modifying the source code for an app.
Click to expand...
Click to collapse
Is there a known solution that would modify the whole OS, not just an app through a code? I would need TLS 1.2 permanently enabled on Android 4.4.2 KitKat. The phone is rooted, BTW.
Hello,
I'm working for a telecommunications company in the UK, we are currently deploying a IMS / Volte solution, we have spoken to handset manufacturer vendors regarding the addition of our carrier configuration to support VoLTE, however this is proving difficult and long delays, I'm hoping someone is able to support us in editing or creating a new custom carrier configuration file with our specific parameters and settings,
We have access to various handsets, we have currently rooted a S9 and s9+ in the hope of creating these profiles but we can only view them, for example we installed EE UK CSC, but we can’t edit or add a new profile
Is anyone able to assist, your time and effort will be rewarded
Thanks, Regards
I feel for you, trying to get cooperation out of any of the manufacturers. One problem with what you're trying to do, though: Even if you were successful at modifying the rooted devices you have to accept your carrier IMS profile, that really won't help end users unless the manufacturer helps out. Whatever fix you would discover would no doubt require rooted access to the file system. That's something the vast majority of users won't be able/willing to do to apply the configuration.
I wish you the best. I can believe it's not easy to get them to help.
Thanks for the reply, it’s almost the chicken and egg scenario, we have completed installation of our IMS / VoLTE solution but need to test service, once we are confident on all the parameters and settings we need, we can provide this information to the manufacturers to add our carrier configuration to the OS, but the handset tech teams won’t be able to support until Q4 this year. Am I looking for a Google / Android developer for this?
Thanks, Regards
kieran_je said:
Thanks for the reply, it’s almost the chicken and egg scenario, we have completed installation of our IMS / VoLTE solution but need to test service, once we are confident on all the parameters and settings we need, we can provide this information to the manufacturers to add our carrier configuration to the OS, but the handset tech teams won’t be able to support until Q4 this year. Am I looking for a Google / Android developer for this?
Thanks, Regards
Click to expand...
Click to collapse
Ah, so then you're not looking to develop something for end users to deploy right now. You just want to get it working so you can tell the manufacturers what you need included in the stock OS. That makes way more sense. An Android developer would be useful, but mainly someone on the telecom side to know the parameters would be needed. It should just be editing stock configuration files, unless there's some weird authentication you need to do above and beyond the normal LTE stuff.
No. We're doing it in phases. We will allow inbound users on our network first. Then we'll open to our local customers after a period of time. We know what we need to configure to enable VOLTE, but we don't have access to those configuration files. Rooting obviously doesn't give enough access. Is there anyone online that would be able to support that you know off?
kieran_je said:
No. We're doing it in phases. We will allow inbound users on our network first. Then we'll open to our local customers after a period of time. We know what we need to configure to enable VOLTE, but we don't have access to those configuration files. Rooting obviously doesn't give enough access. Is there anyone online that would be able to support that you know off?
Click to expand...
Click to collapse
If there is, this would be the place to find them. Hopefully this is the forum. Sorry, I don't work for a manufacturer, or I'd help you out more directly.
BUMP, anyone able to support in this request. hoping to build a custom carrier configuration file to support a telecoms operator test VoLTE / IMS features
Thanks
kieran_je said:
Thanks for the reply, it’s almost the chicken and egg scenario, we have completed installation of our IMS / VoLTE solution but need to test service, once we are confident on all the parameters and settings we need, we can provide this information to the manufacturers to add our carrier configuration to the OS, but the handset tech teams won’t be able to support until Q4 this year. Am I looking for a Google / Android developer for this?
Thanks, Regards
Click to expand...
Click to collapse
I am interesting in this, i already pm you with my email . Let me know. thanks
If you know what files or folders you need to access, root does give you access. It sounds like you need to research some basic Unix commands and change permissions for the files/folders that you need to access. Root gives you full access to the entire system with super user (SU) privileges.
I wrote some free apps available through F-Droid. A user wrote me that my app "Unpopular Music Player" crashes on his device whenever trying to play music. I analysed the symptoms (app just stops) and crash log (some exception inside Android, without my code being involved).
Now I am at the end of my wisdom. Could perhaps somebody test my app on his/her/its device? The device claims to be Xiaomi Redmi 5 with Android 8.1. The app ist just straight-forward using standard Android calls. It is available via either F-Droid and PlayStore.
PS: No other device ever had that problem during the last three years.
Tested it from fdroid with AEX 6.3 Pie.
Yes it does crash. It starts playing music but then it crashes.
https://del.dog/esuxixamob
https://del.dog/hozagafuno
Also this device has several audio issues. So its definitely device issue.
xDoge said:
Tested it from fdroid with AEX 6.3 Pie.
(...)
Click to expand...
Click to collapse
Thank you very much!
In the meantime three friendly people with different devices also performed the test for me, and the result looks like this:
Huawei, Android 8.0: no problem
Motorola, Android 8.1: music plays, but GUI crashes
Nokia, Android 8.1: same as Motorola
So your device seems to behave like the other 8.1 devices. I already found a workaround that worked fine with the Motorola, so I am going to publish this, and I hope that the other 8.1 devices will then work as well.
Again, thanks for testing!!!
Technical background: There seems to be a backward compatibility problem in latest Google's SDK when calling a deprecated function with a newer OS. Strange...
PS: I just noticed that you did not test with Xiaomi's OS, but some "AOSP Extended". And it's not 8.1, but 9. But this is no problem, so at least I know that Android 9 behaves like 8.1.
Ahkah said:
Thank you very much!
In the meantime three friendly people with different devices also performed the test for me, and the result looks like this:
Huawei, Android 8.0: no problem
Motorola, Android 8.1: music plays, but GUI crashes
Nokia, Android 8.1: same as Motorola
So your device seems to behave like the other 8.1 devices. I already found a workaround that worked fine with the Motorola, so I am going to publish this, and I hope that the other 8.1 devices will then work as well.
Again, thanks for testing!!!
Technical background: There seems to be a backward compatibility problem in latest Google's SDK when calling a deprecated function with a newer OS. Strange...
PS: I just noticed that you did not test with Xiaomi's OS, but some "AOSP Extended". And it's not 8.1, but 9. But this is no problem, so at least I know that Android 9 behaves like 8.1.
Click to expand...
Click to collapse
Hello ,
Are you a App developer if so can I contact you I need your help
In some app development
Shreejoy Dash said:
Hello ,
Are you a App developer if so can I contact you I need your help
In some app development
Click to expand...
Click to collapse
Yes, you can, and you may, but I actually draw most of my wisdom from "stackoverlfow.com".
Addendum: some days ago I had repaired the program, and since today the new version is available on F-Droid. It should now longer crash during notification creation.
Ahkah said:
Addendum: some days ago I had repaired the program, and since today the new version is available on F-Droid. It should now longer crash during notification creation.
Click to expand...
Click to collapse
Works fine now. App is really smooth.
Please excuse me, but I've been looking for 3 hours now and, frankly, I'm now more utterly confused than ever - sorry
I am genuinely desperate to get back call recording to my S9 Plus for business purposes. I've seen that for some UK phones it is apparently now possible to record even with Pie but I can't, despite genuinely trying, find how I'd make that work.
It worked fine until Pie, so I fully understand I will have to go back to Oreo. I also understand I will have to lose all my data. I'll live with those little things. However, can someone PLEASE point me to:
oldest O2 UK Oreo firmware. I don't seem to be able to download from anywhere I've seen them advertised without 'signing up' to frankly dodgy looking sites
Instructions on how to actually do what I need to do
Thank you
Can help with part of your question...
The how to flash was posted at the link below. The instructions are actually pretty clear, they tell you what to do.. Click on the show content under the "how to flash the stock flashable odin firmware".
https://forum.xda-developers.com/showpost.php?p=75917820&postcount=1
Just be aware that you can only flash firmware that has a bootloader equal too or higher then what is installed on your phone right now. You can not flash firmware that has a bootloader version that is lower then what is currently on the phone.
To locate your bootloader version look under settings > about phone > software information > baseband version
Once you locate the baseband version count 5 characters in to the left (starting at the far right as character number 1). The number at the 5th character will be the bootloader version.
If you have a recently updated your phone to android pie then you will not be able to downgrade it to oreo... so from what I can tell if you installed android pie updates released after April 2019 you will not be able to downgrade to oreo
I used the link below to determine what firmware versions your looking for. Unfortunately I can not get the files you need, which is why I am only able to help with part of your request.
https://www.sammobile.com/samsung/galaxy-s9-plus/firmware/SM-G965F/O2U/
scottusa2008 said:
Can help with part of your question...
The how to flash was posted at the link below. The instructions are actually pretty clear, they tell you what to do.. Click on the show content under the "how to flash the stock flashable odin firmware".
https://forum.xda-developers.com/showpost.php?p=75917820&postcount=1
Just be aware that you can only flash firmware that has a bootloader equal too or higher then what is installed on your phone right now. You can not flash firmware that has a bootloader version that is lower then what is currently on the phone.
To locate your bootloader version look under settings > about phone > software information > baseband version
Once you locate the baseband version count 5 characters in to the left (starting at the far right as character number 1). The number at the 5th character will be the bootloader version.
If you have a recently updated your phone to android pie then you will not be able to downgrade it to oreo... so from what I can tell if you installed android pie updates released after April 2019 you will not be able to downgrade to oreo
I used the link below to determine what firmware versions your looking for. Unfortunately I can not get the files you need, which is why I am only able to help with part of your request.
https://www.sammobile.com/samsung/galaxy-s9-plus/firmware/SM-G965F/O2U/
Click to expand...
Click to collapse
Thanks Scott. I think.
I guess this is yet a further example of how consumers are being actively denied genuine choice whilst the companies tell us what is happening is in 'our' best interest. God help us.
I have read that Google are releasing new firmware updates to Pie for the UK that allows recording again. Does anyone know where I can get hold of it for my S9 plus please?
YorkshireDave said:
Thanks Scott. I think.
I guess this is yet a further example of how consumers are being actively denied genuine choice whilst the companies tell us what is happening is in 'our' best interest.
Click to expand...
Click to collapse
There's more to it then that, the updates we get contain security patches and the bootloader is always going to receive patches as well to curb vulnerabilities and etc.
If your phone is used for work they may have an IT policy that requires your phone to be updated as to be secure from vulnerabilities.. so I would check with them to be sure. Reason why i suggest this is because If your using call recording then the recording of customers calls would need to be kept updated so it's secure... If they don't have a policy then they should because it makes it that much easier for a data breach to happen running devices that are behind on patches/updates.
Maybe this will be of help to you in the meantime? You can use a PBX calling app with a voip provider (like voip.ms or one of the other ones). The PBX calling apps generally do have voice recording abilities that work really well. I ran my own PBX voice server with an older computer (used a voip provider for calling to/from landlines) to help filter spam calls, but I also recorded my calls since it was easier to remember important dates/info that way.
Also here's some info on the removal of the call recording API.. Originally it was done around android 6.0 for privacy reasons. It was the developers of 3rd party applications who found ways around the removal of the API to make call recording to work.. When Android Pie was released that the work around was patched. Also while our phone's are capable of native call recording, this is only enabled when it is allowed by your country/region/cellular provider (which is nothing Google can control).
In your case you could root your phone and modify it to accommodate call recording if you wanted (not sure if that is viable since you indicated your phone and a work environment).
Google has indicated they would like to return the api for call recording, but so far has only said it is on there roadmap. So I would hope someday they do but it doesn't look like it will be at the release of Android Q.
Link to the XDA article on Google adding call recording api back someday:
https://www.xda-developers.com/future-android-version-call-recording/
scottusa2008 said:
There's more to it then that, the updates we get contain security patches and the bootloader is always going to receive patches as well to curb vulnerabilities and etc.
If your phone is used for work they may have an IT policy that requires your phone to be updated as to be secure from vulnerabilities.. so I would check with them to be sure. Reason why i suggest this is because If your using call recording then the recording of customers calls would need to be kept updated so it's secure... If they don't have a policy then they should because it makes it that much easier for a data breach to happen running devices that are behind on patches/updates.
Maybe this will be of help to you in the meantime? You can use a PBX calling app with a voip provider (like voip.ms or one of the other ones). The PBX calling apps generally do have voice recording abilities that work really well. I ran my own PBX voice server with an older computer (used a voip provider for calling to/from landlines) to help filter spam calls, but I also recorded my calls since it was easier to remember important dates/info that way.
Also here's some info on the removal of the call recording API.. Originally it was done around android 6.0 for privacy reasons. It was the developers of 3rd party applications who found ways around the removal of the API to make call recording to work.. When Android Pie was released that the work around was patched. Also while our phone's are capable of native call recording, this is only enabled when it is allowed by your country/region/cellular provider (which is nothing Google can control).
In your case you could root your phone and modify it to accommodate call recording if you wanted (not sure if that is viable since you indicated your phone and a work environment).
Google has indicated they would like to return the api for call recording, but so far has only said it is on there roadmap. So I would hope someday they do but it doesn't look like it will be at the release of Android Q.
Link to the XDA article on Google adding call recording api back someday:
https://www.xda-developers.com/future-android-version-call-recording/
Click to expand...
Click to collapse
Hi Scott.
Whilst I mentioned 'work', it is my company so I control what goes on. Additionally, recording anything without informing the other party is perfectly legal in the UK so long as it is for personal use only. I even have a call recorded where the Information Commissioners Office told me this
As I am seriously desperate to record my calls, and my phone is now out of warranty, would you be kind enough to point me to a thread or two where I can find a well trodden and not too complicated rooting procedure pls?
YorkshireDave said:
Hi Scott.
Whilst I mentioned 'work', it is my company so I control what goes on. Additionally, recording anything without informing the other party is perfectly legal in the UK so long as it is for personal use only. I even have a call recorded where the Information Commissioners Office told me this
As I am seriously desperate to record my calls, and my phone is now out of warranty, would you be kind enough to point me to a thread or two where I can find a well trodden and not too complicated rooting procedure pls?
Click to expand...
Click to collapse
This thread deals with rooting the model you have.. perhaps it will be of use for you?
https://forum.xda-developers.com/galaxy-s9-plus/how-to/guide-root-s9-oem-fix-t3763974
Also the ability to add native call recording seems to be a csc feature tweak. Two ways you could try this:
1.) I am not sure if this still works or not, but you can try this. Edit the cscfeature.xml and add the following to it at the bottom:
Code:
<CscFeature_VoiceCall_ConfigRecording> RecordingAllowed </CscFeature_VoiceCall_ConfigRecording>
2.) Install a custom rom that has the feature as an optional addition. One rom I see mentioned often is this one
https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346
Others may have ideas too.. so before you do anything maybe consider waiting to see if others post ideas?
The Xiaomi Home app suffers from a problem with PUSH notifications not working. It is likely that the problem has been present for many years.
The problem is well known and widely commented on the internet both on forums and in comments on Google Play. For example https://c.mi.com/thread-3056817-1-0.html
At least part of the problem is due to the smartphone shutting down Xiaomi Home to save energy. Nevertheless, a large number of the reports come from people who are aware of how to configure the smartphone to not close the app.
An example of such a post accurately describing the problem is https://community.oneplus.com/thread?id=1455606
Searching the Internet, I discovered that people from all over the world are experiencing this problem. I found the problem described in English, French, Spanish and Italian forums. Interestingly, it also affects Xiaomi smartphone users. Multi-screen discussion and unfortunately no solutions.
My observations - PUSH notifications work on Bluestack (Android 7.x)
Xiaomi does not seem to notice the mentioned problem. I write on the XDA Forums because there are people here who have a good understanding of how Android works.
Questions for you guys:
- How to debug the problem to draw any conclusions? Determine what is failing.
- Is it possible that the problem is due to some kind of US/China sanctions?
- I have heard that PUSH notifications work differently on the Chinese market, they don't use Google's dedicated service there. Could this be related?
As far as I know, PUSH notifications do work differently on the Chinese market. The GCM/FCM as well as other Google's dedicated services do not work.
Possibly. However, it still seems very strange to me that Xiaomi sells devices tailored to, for example, the European market, has European servers and the app distributed by Google Play uses the PUSH system operating in the Chinese market.
Sounds quite unlikely, given the huge popularity of Xiaomi hardware outside China.
However, if this is true then Xiaomi Home probably supports only MiPush http://mipush.global.xiaomi.com/ so we would need something like a wrapper for MiPush to send notifications to GCM/FCM. Unfortunately I'm not an Android developer.
It still puzzles me why I was getting notifications from Xiaomi Home on Bluestacks 4 running Android 7.x. It looks like some mechanism compatible with other markets is implemented - just not working with newer Android?
Additional information: Notifications work on Xiaomi Mi 6 - Android 9
i have same issue.
any solution yet ?
i followed all steps in this video twice and didnt work
None of the old solutions work. Xiaomi Home does not like some regions. For example, European Android devices (from version 10 I think) present themselves with the region 'eea'. Xiaomi Home does not accept this ( three-letter problem?) region - initiating push notifications crashes, as you can see in the logs (see link below).
I think the closest to solving the problem is this answer https://forum.xda-developers.com/t/missing-push-notifications.4133417/
You can of course change the region in Android, but this requires root and is rather pointless. Other apps may not work properly.
I suppose it would take 1 day to fix the app. Why hasn't Xiaomi fixed this for several years? It remains a mystery.
If anyone knows a way to change the region without root, just for one application then please let me know.
Any solution yet? Still no notifications with oneplus 9 pro and android 13. I have done any "fix" I have found and nothing.