I have an Umidigi F1 that has been working very well with multiple GSI roms, but I have never been able to get VoLTE or VoWiFi working on any of them. Everything else seems to be working great right off the bat, with the exception of obvious things like WiFi tethering. I’m currently on Bliss Rom GSI, as it has VoLte and WiFi calling baked in, but placing or receiving a call results in falling back to H or H+ and attempting a WiFi call while in airplane mode results in a failure.
I’m on T-Mobile in the USA and VoLTE and WiFi calling both work on other phones, as well as on the F1 with the stock OS out of the box. I’m in a bit over my head and don’t have a ton of knowledge in the area, but here is what I have tried so far:
1. Installed the ims.apk that is floating around, having no effect when installed as a user app or a system app. I’m assuming there is a chance that the Mediatek chip is the hangup here.
2. Extracted ImsService.apk and WfoService.apk from the stock rom and copied to system (trying both /system/app and /system/priv-app separately) and set permissions accordingly. /app folder has no effect, /priv-app folder results in complete loss of cellular signal.
3. Copied entire folders for ImsService and WfoService which include the apk files in addition to odex and vdex files and set permissions accordingly.
4. Installed the (now defunct) VoEnabler Magisk module, which I believe simply edits the build.prop
5. Attempted to install the two apk files as user apps which results in a failure.
Again, I’m not tremendously knowledgeable in this area, so not sure where to turn next. From all the reading I’ve done, I’m thinking the issue may have something to do with either the build.prop or the vendor img, but I wouldn’t know where to begin with either of those. I could do without the WiFi calling, but VoLTE is fairly important in my area, as 3G & 2G fallback is pretty weak where I am and results in a lot of dropped calls.
Sorry for the length. Any ideas would be greatly appreciated. Thanks in advance.
I'm guessing it's a MediaTek SoC, I don't remember seeing Umidigi putting Qualcomm in any of their phones.
voLTE does not work on any GSI ROMs when installed on any MediaTek device. I've not seen anything about voWiFi with MediaTek phones, so that could be specific to the Umidigi
Thanks for the reply. Unfortunately, I'm starting to think you're right about VoLTE and Mediatek. I was hopeful that I would be able to push a few APKs, edit the build prop, or create some kind of overlay in an attempt to get it working. The latter is clearly way beyond my capabilities, but after using the SP Flash Tool for the first time, I'm now pretty willing to repeatedly brick the device in an attempt to make something work!
It's fairly frustrating as these features work well in the buggy stock rom. Unfortunately all of my digging and reading has turned up a lot of dead ends. I'm not too hopeful, but if anyone has any other ideas, I'd love to hear em.
Thanks
Robbo.5000 said:
I'm guessing it's a MediaTek SoC, I don't remember seeing Umidigi putting Qualcomm in any of their phones.
voLTE does not work on any GSI ROMs when installed on any MediaTek device. I've not seen anything about voWiFi with MediaTek phones, so that could be specific to the Umidigi
Click to expand...
Click to collapse
I would actually guess that it relates to some changes that the GSI makes compared to the stock image. If I'm right, t-mobile likely grants access to base features on its network to any device, yet reserves more advanced features to authorized devices.
I'm like you, however, in that I'm not knowledgeable enough to know for sure. I say this because I'm experiencing a similar issue (same device, the Umidigi F1) with my carrier, Verizon Wireless. Everything is fine on stock ROM but no data or advanced features on AOSP roms (derived by phhusson's work so far). Verizon seems to be stricter with devices on their network, yet I believe our issues have a similar root cause.
Makes sense... I've never used Verizon, but I know it's a bit stickier than T-Mobile and some of the other GSM carriers with regard to unauthorized devices.
I just haven't been able to find a ton of information about these specific issues while using a Mediatek phone. I've randomly moved files from the stock rom over to GSI roms with no luck. Again, in over my head, but I've grabbed anything related to volte or ims from /bin /app /priv-app /framework, etc... and had no luck.
Veiran said:
I would actually guess that it relates to some changes that the GSI makes compared to the stock image. If I'm right, t-mobile likely grants access to base features on its network to any device, yet reserves more advanced features to authorized devices.
I'm like you, however, in that I'm not knowledgeable enough to know for sure. I say this because I'm experiencing a similar issue (same device, the Umidigi F1) with my carrier, Verizon Wireless. Everything is fine on stock ROM but no data or advanced features on AOSP roms (derived by phhusson's work so far). Verizon seems to be stricter with devices on their network, yet I believe our issues have a similar root cause.
Click to expand...
Click to collapse
Related
hi,
well i'm against that policy, not able to post at developer threads under 10 posts, else I would have question that directly,...
I've tried several roms and ended at slim beam, first to 4.2.1 which states at stable but also tested the new one 4.2.2 build 2.5
actually i'm fine with the roms, also slim bean but I do have a 3 major issues with all of them which may be related to S3 and asop/cm:
1.) problem using my apple iphone earbuds (yes I'm a iphone user too)
sometimes after mute the microphone, it won't work after de-mute, keep on muted !
microphone not working after re-connecting earbud on a running call, sometimes no audio on earbuds too, sometimes audio even do not work for the whole device -> reboot etc,...
I've found several possible solutions, non of them has worked.
why android doesn't work with that kind of TRRS earbuds, are they incompatible from hardware point of view, do I need special ones which will work on S3.
2.) problem with direct dialing from calendar, not respecting RFC2806
i really need this very often to join conference calls, sometimes the host creates an conf call and including a number with pin as the location.
well almost every mobile os recognizes this and i'm able to direct dial in on selecting the string: iphone, win, even blackberry, but not android.
i know there might be additional apps which can handle this, but it should be implemented into core apps as this is a well known standard and specified in a RFC.
3.) not recognize AP with highest signal strengh within same SSID
it seems that android devices are not able to seamless switch over to different AP within a wifi network with same SSID.
if moving out of range of AP1 and into range of AP2, android devices for some reason are not able to switch to AP2 (with higher signal strengh), therefore it states at AP1 without beeing able to establish any connectivity (because AP1 out of range). as workaround users needs to disable/enable wifi ;-(
this is also something where I have to find a workaround in my current project (creating huge wifi network over europe), because market share of androids is that high and it still have this serious annoying bug.
thanks,
nean
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
10 post rule is there to protect developers from spam and users not knowing what belongs in a development thread and what belongs in Q&A
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
CNexus said:
1. Headphones > Most likely thats just an issue with roms that are version > 4.1.2. Not all the bugs have been worked out, see if you can replicate it with another pair of headphones.
2. I suspect the same thing is going on here, or you would need some more powerful calendar sort of app.
3. This isnt because it doesnt recognize, its because Android is still connected to the last network and says to itself "no need to scan again, I'm already connected". This has to do with how the OS is implemented, not because its a bug with Android. I'm also fairly sure that most other devices do the same thing
Click to expand...
Click to collapse
thanks for the reply.
ad 1,2,3.) hmmm, is this working on googles stock os and eg on nexus?
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
nean24 said:
ad 3.) this is only related to android devices, as tested in the lab with several other handheld devices with different kind of os'es. ios, blackberry, windows mobile, etc, all work and do seamless switchover except android. well the last known network and the new one is actually the same wifi network which is specified due SSID, so if android's rescan logic is related to that kind of info it may be wise to consider acces point strength as well, just like all the other os'ses,....
Click to expand...
Click to collapse
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
tazfanatic said:
Did you test using stock os and not a AOSP rom like stated in the OP? You can't blame the OS for a issue if it is moded in any shape or form. Try using straight up stock TW and see if it works. AOSP and CM are not 100% designed to work on this phone flawlessly.
Click to expand...
Click to collapse
thats correct, but it doesn't work on galaxy stock os either, that's why I've tried custom roms just to find out if its related to samsung stock rom or if its a general android behavior. well the outcome was that it works on aosp/cm a bit "better" (shorter timeout) but not seamless.
my intention is not about to blame anyone, just like to find out where I can adress this issue, or do I need to get in contact with google?
rgrds
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
cognus said:
I hope to benefit from someone's WIFI expertise.
Bought for my wife a T-Mobile branded SGS3 replacing her older SGS4G ["S 4G"] model for more power, memory, etc etc. I noticed from the beginning that, compared to all my other handsets, tablets, PC/laptops, this one was troubled on WIFI connections. Found lots of posts around the web, read up on fixes. Gathered the tools together, erased the ROM completely, started from scratch with stock T-Mo ROM, rooted and debloated it. Made some of the standard changes to WIFI options: stopped scanning, disabled power-saving, reset the home/office WIFI to channel 11 , "N" band only. Things improved in that stable, controlled setting.
but 'on the road' with multiple hotspots, hotels, offices, T-mo data service, etc it is still very difficult to use. It will drop otherwise good WIFI connections, and hang in the midst of operating on WIFI. To give a simple example: go somewhere new, find WIFI, connect to WIFI, check EMAIL, Facebook, Messages - find 10 or so messages unread unresponded, try to download/read/respond and the device will get maybe one or two, then simply stop responding. Wait a minute or two and you get the "WIFI Connected" notice again. repeat, repeat...
What I wonder: how many variants of hardware have there been for T-mo, USA, GS3? Is there a model version I can get that avoids this issue?
Click to expand...
Click to collapse
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Aerowinder said:
Is the phone running full MD5 firmware?
Hardware issue if no restoring was done between devices.
Click to expand...
Click to collapse
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
cognus said:
yes, in fact I made utterly sure because somebody else asked the same question, same issue. still very flaky. no odd modems or other custom 'wares, just rooted and a few unnecessary apps uninstalled. how many models of this are there, were they made in different locales?
I assume the SoC is the same, but what about antennae, internal connections, etc? any evil interactions between radios? we don't use Bluetooth, so that one stays off all the time assuming the softswitch works
Click to expand...
Click to collapse
Well, as far as how many there are? A LOT! LOL! I'd imagine a few hundred thousand US variants, and for the T999 and its variants, close to a hundred thousand maybe? I really don't know, and those numbers did not come from anywhere but my head!
But as far as manufacturing, I am pretty sure they are all built in the same place. But, this does not mean that all of the components are from one location. In fact, from batch to batch of the same part, it can vary by where it was made, but also by what company made it. This is unlikely when dealing with the critcal parts such as the SoC, but the WiFi chip is a Broadcom chip. I have no idea if there are multiple manufacturing locations for it, but it is possible. The memory in all devices often varies greatly by the manufacturer.
Anyway, I do agree with Aerowinder. It is most likely hardware related. I'd look into a Warranty or Insurance exchange.
Disclosure: I own nothing hereI am not an expert romolgist. Just a guy that hates when buttons don't do anything.
Without a working US csc folder in the Rom it's all pretty much temporary.
Since support in current threads is non existent I'll do my best to show what I've done to get data and texting. It's still a bandaid for a weak design but it's enough to get things working for a couple hours.
Results will vary and this will be updated multiple times in the next week. I'm forgetting some details.
List of apps used.
SetEdit pro - helps remove bloated junk that's greyed out.
Radio Switcher - needs to be turned to cdma-auto and lte-cdma every time signal is lost
Region changer - gets the phone labeled as US but it's incomplete. More on that later
Root essentials - easiest way to get can and build prop in one place
Partitions backup - backup-/restore efs and radio
Aurora settings - adds necessary settings that rom builders left out
APNs backup - obvious reasons
Phone info+ - get into prl enable all LTE frequencies/ disable gsm band
They're pretty much necessary for every n7 port listed today.
Step one:
Backup efs/radio/apn from WORKING rom like MOAR or stock
Download with ADM. Speed was not a priority with these ports including downloads
Pick a Rom that you like the pictures of because words don't mean anything at this point. A 928p Rom doesn't mean it will work on a 928p so don't be afraid to experiment. Had better results from 930 and R4 Roms and kernels.
Hopefully you'll see the activation screen. If not you're gonna have a bad time.
Speaking of kernels use sky but uncheck the prop and other junk box on last setup page. These ports need extra junk just to stay running. I'll post a link to another kernel I like as well as some newer clones.
Step 2
Delete everything. Seriously. Data/system/whatever
Pull your flash drive after install or it tries to write there as well.
These things seem to write anywhere they want and old data has effected startup or install times.
Flash what you liked and hope for the best.
Pick whatever country is your favorite. Means nothing to US Sprint customers
Install as a 920.
Don't take the 928 option.
Install the note5 camera
Install whatever audio driver they added. Stock hasn't worked for me
If you don't see a restart at the Samsung splash screen or blue light stays on after restart it's a bad file. You want to see a jogging pace with the dimming of the logo. Anything less than that and it's going to crash sooner than later. For US Sprint customers it's usually at the connection check.
Step 3
Be patient. These are as temperamental as the builders and require constant maintenance to avoid memory leaks and signal loss. When you read claims about battery life it's because it's missing basic functions necessary to run reliably on us Sprint towers.
Step 4
Hopefully it's showing signal. If not the only workaround is injecting a US csc to the Rom itself as well as 90% of someone else's build props and csc files. I'll show what were used once the owner gives permission.
Restore apn/efs/radio
Root explorer systen/csc/sales_code mount as rw and edit to say XAS
Change region to US
Restart
From there I'll use radio switcher and connect to cdma-auto and wait for signal. Once signal is established and you see your phone number switch it to cdma/LTE auto and restart. Verify the settings stuck. If they didn't try playing with different connections. This sometimes works. Also needed for signal loss and probably every restart.
Once data is working try editing csc until it matches a good Rom.
*added xposed that works with lam7.3
https://mega.nz/#!tdF0FKjR Aurora apk
Reserved for download links
Here's what I like. Results will vary
https://mega.nz/#!oUVxSSKb Lamlazy 7.3
https://mega.nz/#!0EFCGAob duelbootgraceux kernel
https://mega.nz/#!tBNBXCgY hidden menu
https://mega.nz/#!wM0V2LyT some beta crap that gets good LTE but needs dialers or it it comes unglued
https://mega.nz/#F!oA9Q0QyS More links including 925 and 920 combo files
Reserved for cat pictures
Got synapse to load this morning. Day and night difference after cleanup and adjustments to little cores. Loaded a MOAR profile for shiggles and both roms freeze. Knew results would probably go that way but it's fun to try and break these things instead of the usual self destruct.
Testing with this phone might be done. Charging port is pretty lose and I don't want it fixed. If anyone can add to this please do I'll keep the links alive.
I have determined that I at least will need to unlock my bootloader which I am already loathing since that means everything on my phone will get reset. We also don't even have signed firmware for this device. I don't care about root, but I also don't use any of this pay nonsense. I do play a certain game that will moan about my phone being modified though. I was already looking at the nougat thread regarding root and passing everything but I'm not interested in magisk and the headache that comes with having to deal with safetynet updates.
Far as I understand:
1. Get TWRP, can I get away with just booting it and not actually flashing?
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
2. I guess tomparr's zimage kernel zip found here: https://www.androidfilehost.com/?fid=457095661767134479 is required since the system is going to be changed for what I want to do
3. Steps somewhere a long the lines of this http://www.theandroidsoul.com/enable-tethering-nougat-alongside-android-pay/
a. Add the net.tethering.noprovisioning=true line
b. Open Terminal emulator on your device and issue the following commands one-by-one:su
settings put global tether_dun_required 0
exit
If I am understanding anything wrong or anyone wants to point me at anything else to read that would be great.
[rant] What an annoying experience this has been, before a few hours ago I praised motorola(lenovo) for what an amazing phone this was, that is until I got that ridiculous update pushed to my phone. Yes, it is definitely snappier and more responsive, but I'm not giving up functionality because the developer of the dammed OS caved into pressure from carriers. I bought an unlocked phone an no carrier has any right to restrict any of my phones features just because they think they can. I work in an office where login into the wif is a thing and I will have multiple devices with me sometimes, so I used to just bluetooth tether the other devices from my main phone and not have to deal with mutliple logins, there are also times when out and about where my gf's signal isn't great and she will use my data to be able to keep using her phone. DAMMIT THIS IS FRUSTRATING.... [/rant]
Hello. I got infinix note7 X690b MTK6768 android10 device on which I'm trying to use GSI ROM based on android11. One of the dev made an overlay for my device and committed to THH trebble project at github.com/phhusson/treble_experimentations
so the overlay is present in THH releases. But still, I am facing the following:
1. Unusual battery consumption and battery usage stats unavailable.
2. Slow speed on mobile data connection with even full strength of LTE signals.
3. Fake third sim slot with a carrier name "china unicom", where my device don't support e-sim and has only 2 physical sim slots.
Except these issues, ROM is performing perfectly without any performance problem. But these major issues driving me crazy. Could anyone suggest something how to handle? I am struggling to find a way for several months, not found any clew till today. I have also posted new issues on official THH git, but still nothing.
I'm attaching my logs as well, hoping for very tiny help from such a largest community.