Related
Afters many hours searching the net and xda i could not find answers to these questions.
1) Does the rogers dream/g1 GPS work without a data plan? (using a standalone GPS app for example: CoPilot)
2) Does rogers Dream/G1 require data in order to initially find the satellites?
3) If you have no data plan are you able to get a lock on the satellites?
4) Can i manually enter my coordinates (longitude/latitude) for my gps in order to find the satellites quicker?
Here is what happened, i got fed up with rogers and decided to cancel my data plan (its just not worth paying 25$ for just 500mb per month). But since i canceled i noticed i am unable to find satellites for my GPS. Using multiple apps (GPS Test, GPS Status, CoPilot, etc...) none of them could get a lock on any satellites or even find one for that matter. I had my phone outside in a clear view of the sky when i was trying these apps.
By the way its not a hardware issue, because it worked before i canceled the data plan. I purchased the standalone map software called CoPilot in order for me to use when i canceled my data plan. (The US/CANADA maps are already installed on my sdcard).
Data was not important to me, since i quite often use my wifi, but not having my GPS working because i canceled my data is really making a paper weight out of my phone
Any help with this would be greatly appreciated!, as i am sure that there are many other users who would like to have these questions answered before making the decision to cancel their data plan.
1) Yes.
2) No.
3) Yes.
4) No.
Note that robbers really screwed some things up badly on the latest "update" that they sent out for DREAM hardware -- along with locking the thing down to prevent you from fixing it yourself. I think they want to make it look like crap and be locked in to its obsolete version of Android permanently. They are obviously fishing for more service contracts. I wouldn't be surprised if they broke GPS.
Note: It could be that you just aren't in a spot to easily receive GPS.
Thank you for the response!!! lbcoder, and i am happy you kept your answers to a yes or no (that was exactly what i was looking for).
I was wondering if you could help me some more. Instead of doing the robbers 911 update, i followed the instructions from cyanogen to bypass this since i already had my phone rooted, i used this guide wiki.cyanogenmod.com/index.php/Upgrade_Rogers_Dream_Radio
Before i did this update i was running enomther rom and also wesgarner rom. Both worked flawlessly and GPS also worked with both. But once rogers sent out the 911 update, that's when i cancelled my data plan, and followed cyanogen instructions to bypass this.
1) Could it be that its cyanogen new v4.2.14.1 rom that is causing the issue of my gps not working?
2) What are other roms i can try that works with cyanogen new radio update?
Thanks again for your help!
ifactory said:
1) Could it be that its cyanogen new v4.2.14.1 rom that is causing the issue of my gps not working?
Click to expand...
Click to collapse
Possible. Cyanogen isn't known for being particularly stable.
2) What are other roms i can try that works with cyanogen new radio update?
Click to expand...
Click to collapse
I believe that you should be able to use ANY ROM that you like. The only issue is that the kernel you use must be compatible with that radio (i.e. built from the HTC source).
There is no guarantee, but there is a high likelihood that the appropriate kernel will work with pretty much any system image. So you should be able to switch out the boot.img and any kmods from any rom to make something that works.
Just be sure that you don't go messing with the radio or spl on your phone and keep a good nandroid backup in case you need to backtrack.
Now if you aren't comfortable making this kind of modification (i.e., if you have to ask....), then you might want to go searching for ROMs that are specifically listed as compatible. I don't have any robbers hardware, so I don't know which specific roms to suggest to you.
I was able to install two roms aside from cyanogen, using the new radio. One was by wesgarner and the other by benbuchacher. Both roms are not able to find any satellites for the gps.
So i can confirm this issue has nothing to do with the roms.
CAN ANYBODY CONFIRM THAT THEY ARE ABLE TO USE THEIR GPS WITH A ROGERS DREAM PHONE, WITH THEIR DATA PLAN CANCELED?
The G1 GPS uses ASSISTED location when it can, meaning when you use the GPS along with the data services it will be able to lock onto a signal pretty much instantaneously. If you turn off your data, if can take the GPS a LONG time to find location (I've seen it take upwards of 5 minutes.)
lbcoder said:
Possible. Cyanogen isn't known for being particularly stable.
.
Click to expand...
Click to collapse
not sure which version were you using but Cyanogen is one of the best roms and stable ones, maybe you used the experimental version
lbcoder said:
Possible. Cyanogen isn't known for being particularly stable.
Click to expand...
Click to collapse
GPS is working fine with & without data for the version of cyanogenmod mentioned.
pk198105 said:
not sure which version were you using but Cyanogen is one of the best roms and stable ones, maybe you used the experimental version
Click to expand...
Click to collapse
Any of them. They're all bloated piggish things that barely work at all. Fine if you like bleeding edge and useless features. Not if you actually want your something productive.
it works fine.
I have a Sprint tab. I wan't to upgrade to gingerbread, and I don't care about CDMA service, but I have to have wifi. GPS would be preferred but I can live without it. It would also be nice if it wasn't a brick afterwards.
What are my options? Can I just flash Overcome without a modem file? Is there some sort of null modem file I can flash? Is there a different ROM or kernel I should use?
http://forum.xda-developers.com/showthread.php?t=1020167
jiminitaur said:
I have a Sprint tab. I wan't to upgrade to gingerbread, and I don't care about CDMA service, but I have to have wifi. GPS would be preferred but I can live without it. It would also be nice if it wasn't a brick afterwards.
What are my options? Can I just flash Overcome without a modem file? Is there some sort of null modem file I can flash? Is there a different ROM or kernel I should use?
Click to expand...
Click to collapse
Also very interested in this.
I recently put quite a bit of effort into getting GB to run on my Sprint tab. I use WIFI only so I was not concerned with a working CDMA radio. I attempted to flash the European GSM firmware to my device. I tried flashing the kernel and system only, leaving the CDMA radio file intact. I also tried flashing several GSM radio files to the device. In the end I was unsuccessful, and it took several hours to recover the device to an operational state.
If you WERE to get GSM GB working, there is a good chance that GPS and BT wouldn't function. That's kind of a deal breaker for me.
tldr; Sprint users are screwed until the official release of GB because the Overcome team doesn't care about us and the only guy who seems to know how to work the CDMA is making a crappy honeycomb build instead.
IMHO other devs should make a version of the ROM with all data taken out because it'll work for Sprint users and GSM users who tether instead of paying out the rear for a data plan on their tab.
----------------------------
tonman23: Thanks, but i was looking for gingerbread, not honeycomb. It's great that spacemoose can prove it in concept, but I don't like the honeycomb interface, and I'm not interested in flashing a half broken version of it to my phone. I want a stable gingerbread build for the improved performance and minor UI features.
etvaugha: BT & GPS are handled by chips completely independent of the modem. I can't post a link because I'm still new here but the ifixit galaxy tab teardown shows clearly that GSM tabs have distinct BT/WLAN & GPS chips. That's pretty standard fair for android devices, so I doubt they changed it simply for the CDMA models.
It also clearly shows that the modem is a GSM only chip, so the bin files are completely incompatible. The only solution is ROMs that will boot even if the modem isn't working right.
----------------------------
According the the Overcome 2.0 FAQ, the problem is that the phone won't finish booting if a valid modem.bin is not installed. Apparently the phone waits indefinitely (one user, PFOI, mentioned something about it working after 30 min or so) or crashes during the boot because it doesn't get a proper response from the modem chip.
This could easily be overcome if the devs would compile a WIFI only version of the rom/kernel, that doesn't require or support either modem (CDMA nor GSM). It seems to me that the this would be good for both sides, as the data plans for tabs are a rip off and smart users are going to tether their tabs in a mobile situation anyway. It would also probably be better for battery life considering there'd be one less chip running and less bus activity.
I'd imagine all that would be required is removing the modem initialization during the boot sequence. There might be a need to replace the functions that query the modem's status with static value return statements, but when the tab first boots it reports no service, so it's got an inherent ability to deal with not having network access. All that's needed is a couple little snippets to tell the device it doesn't, and to keep it from trying to get it.
Just a question to all the Kaiser users out there.
Do you use the Kaiser with only Android installed as your main phone?
Those that do, have you had any "bad" experiences while using the phone that are NOT caused by network discrepancies (i.e.: dropped calls, bad signal, etc.)?
I ask because I do use mine as my main form of communication on a daily basis, and I had my first dropped call today due to a hard lock. This is after almost a year of use, on the same phone, in different parts of the country with only a couple of days of non-use for screen replacement (scratched/damaged touchscreen).
I know we're all hanging on to old technology for different reasons, wether it be cost, availability, or that certain "wow" factor that comes from completely changing something that was never meant to be changed. I have become fond of my Kaisers for obvious reasons, but if I cannot trust it when I need it I may need to move on.
Thoughts?
I use it as the main phone . I dont have any problems except the camera and the WiFi . Hope to get it rectified soon though :/
TheMadxtremist said:
I use it as the main phone . I dont have any problems except the camera and the WiFi . Hope to get it rectified soon though :/
Click to expand...
Click to collapse
Man, you still didn't manage to get WiFi to work ?
Dude my kernel !!
and because of exams i cant get that repaired !!
IDK if your kernel is the issue or not because the radio rom also has a lot to do with some aspects of the hardware controls (phone, wifi, audio, camera, etc.).
Other than checking your wifi.ko file with root explorer or some other text viewer, the only option is to change your rom. I have had a 99% success rate with my Kaiser using only Scoots kernel with 25mb of cache, the 8/29/11 rom from sourceforge and LauncherPro plus (from my personal stash). I have the kernel setting the clock to 500MHz on start up and I usually end up underclocking to 480 for a week or so to check stability against the previous weeks settings.
My camera works, my wifi works, bluetooth works, tethering/hot spot works, but video doesn't (not like I'll EVER use this thing for videos)...
PoXFreak said:
Just a question to all the Kaiser users out there.
Do you use the Kaiser with only Android installed as your main phone?
Those that do, have you had any "bad" experiences while using the phone that are NOT caused by network discrepancies (i.e.: dropped calls, bad signal, etc.)?
I ask because I do use mine as my main form of communication on a daily basis, and I had my first dropped call today due to a hard lock. This is after almost a year of use, on the same phone, in different parts of the country with only a couple of days of non-use for screen replacement (scratched/damaged touchscreen).
I know we're all hanging on to old technology for different reasons, wether it be cost, availability, or that certain "wow" factor that comes from completely changing something that was never meant to be changed. I have become fond of my Kaisers for obvious reasons, but if I cannot trust it when I need it I may need to move on.
Thoughts?
Click to expand...
Click to collapse
Hi!
I use it as my main phone. After the imap push deactivation i hadn't got any hard lock.
But i use gmail sync, and sometimes i got a screen of death. But it's very very rare (maybe one in a month). I think if i didn't use anything thats related to 3G network, this lock up wouldn't appear.
This is my work phone so it must be stable. I'm satisfied with it.
Hi there. I'm looking to replace my Xperia X Compact as it does not support t-mobile WiFi calling. I'm looking to purchase an xz1 compact as I absolutely hate Sony's new childish, rounded handset look. However I'm very concerned that I will be able to get all the features working that I require, especially with the latest firmware. I would appreciate some up to date information as well as any links to guides to accomplish all of my requirements.
What I require:
1. Root is a must. I do a lot of automation with Tasker and want to have full access to my device. Obviously I'd also like to install recovery and ensure that the camera and all apps and features are fully functional.
2. Fingerprint scanner functionality is required. I use a password manager and have no desire to ever be without this feature.
3. I live in an area with mediocre coverage and frequently visit places with minimal coverage. Thus I have realized that I have need of T-mobile us WiFi calling, band 12 support, VO-LTE, etc.
I have read that with some minimal editing of the firmware files you can flash a modified UK firmware to allow both the fingerprint scanner and WiFi calling but I'm concerned that I might lose one or both if rooted. Furthermore I'm concerned that with the latest OTA I won't be able to accomplish all three. I'm obviously not willing to lose any of these features.
I'd appreciate any updated information and would love if you could point me to any guides.
Thanks in advance.
POMF2K said:
Hi there. I'm looking to replace my Xperia X Compact as it does not support t-mobile WiFi calling. I'm looking to purchase an xz1 compact as I absolutely hate Sony's new childish, rounded handset look. However I'm very concerned that I will be able to get all the features working that I require, especially with the latest firmware. I would appreciate some up to date information as well as any links to guides to accomplish all of my requirements.
What I require:
1. Root is a must. I do a lot of automation with Tasker and want to have full access to my device. Obviously I'd also like to install recovery and ensure that the camera and all apps and features are fully functional.
2. Fingerprint scanner functionality is required. I use a password manager and have no desire to ever be without this feature.
3. I live in an area with mediocre coverage and frequently visit places with minimal coverage. Thus I have realized that I have need of T-mobile us WiFi calling, band 12 support, VO-LTE, etc.
I have read that with some minimal editing of the firmware files you can flash a modified UK firmware to allow both the fingerprint scanner and WiFi calling but I'm concerned that I might lose one or both if rooted. Furthermore I'm concerned that with the latest OTA I won't be able to accomplish all three. I'm obviously not willing to lose any of these features.
I'd appreciate any updated information and would love if you could point me to any guides.
Thanks in advance.
Click to expand...
Click to collapse
All good questions. I was kind of in the same boat, although in the end, I sacrificed root access and settled on only having fingerprint and TMo VoLTE/WiFi calling (mostly because I didn't have the guts to unlock the bootloader with only a questionable DRM fix method available).
I used the information in this thread to get fingerprint and TMo stuff working together. It was pretty simple, and worked great the first time. However, I'm pretty sure OTA updates will break that functionality and you'll have to go through the process again if you want to update the OS and keep fingerprint/TMo stuff working.
As far as root, you will need to unlock the bootloader, and then you will need some sort of DRM fix to keep the camera working. There are a few methods in this forum scattered around, but none of them had enough positive results reported back for me to feel confident in trying them. Remember, once you unlock your bootloader, there is no going back, so you're stuck with a non-working camera until you can find a DRM fix method that works. The most widely used root / DRM fix method that I know of currently is Xperifix, although since it is a paid for tool, there is no dedicated thread here on XDA. There are some discussions on xperifix.com, and a lot of people have had success using this. However, a lot of people have struggled with this as well, so I didn't feel confident enough to try it.
As far as how the DRM fix works with the cobbled together firmware for TMo/fingerprint, I can't say, and I don't think I've read of anyone reporting that here on the forums. I suspect everything would work together just fine, but can't say for sure.
Good luck, and if you do end up getting everything working together with root, please do report back here, I would definitely be interested in hearing about it.
camaro322hp said:
All good questions. I was kind of in the same boat, although in the end, I sacrificed root access and settled on only having fingerprint and TMo VoLTE/WiFi calling (mostly because I didn't have the guts to unlock the bootloader with only a questionable DRM fix method available).
I used the information in this thread to get fingerprint and TMo stuff working together. It was pretty simple, and worked great the first time. However, I'm pretty sure OTA updates will break that functionality and you'll have to go through the process again if you want to update the OS and keep fingerprint/TMo stuff working.
As far as root, you will need to unlock the bootloader, and then you will need some sort of DRM fix to keep the camera working. There are a few methods in this forum scattered around, but none of them had enough positive results reported back for me to feel confident in trying them. Remember, once you unlock your bootloader, there is no going back, so you're stuck with a non-working camera until you can find a DRM fix method that works. The most widely used root / DRM fix method that I know of currently is Xperifix, although since it is a paid for tool, there is no dedicated thread here on XDA. There are some discussions on xperifix.com, and a lot of people have had success using this. However, a lot of people have struggled with this as well, so I didn't feel confident enough to try it.
As far as how the DRM fix works with the cobbled together firmware for TMo/fingerprint, I can't say, and I don't think I've read of anyone reporting that here on the forums. I suspect everything would work together just fine, but can't say for sure.
Good luck, and if you do end up getting everything working together with root, please do report back here, I would definitely be interested in hearing about it.
Click to expand...
Click to collapse
At this point it's pretty much a gaurantee that you can root and add the DRM fix easily. But now I'm hearing something about the pictures will still not be the same quality???
I'm curious how do you keep the device from getting OTA updates without root access?
I'm really not okay with having a device without root access. The ability to make my own recovery images is an absolute must. I'm also too invested in tasker automation to stop now.
POMF2K said:
At this point it's pretty much a gaurantee that you can root and add the DRM fix easily. But now I'm hearing something about the pictures will still not be the same quality???
Click to expand...
Click to collapse
No, has nothing to do with picture quality. The camera either works or it doesn't. When you unlock bootloader, the camera stops working (solid green pictures). When you apply DRM fix, it starts working again as it did originally.
POMF2K said:
I'm curious how do you keep the device from getting OTA updates without root access?
Click to expand...
Click to collapse
I disabled the update centre and update service using this method - no root required.
Does anyone know if this method to keep the wifi calling and fingerprint reader simultaneously active works after recent ota updates?
Still searching for someone on T-mobile US with this device that can verify that I can achieve all 3 at once (Root, Fingerprint Sensor, T-mobile Wifi Calling).
Please help.
If you're in US and using XZ1c, which carrier are you with? I'm interested in carriers that work for docomo/SO-02k models as well as G8441; whether data, or calls, or both work properly.
Not sure of any that work with the docomo, I think there is a thread here for those. But for the g8441 models, T-mobile and Verizon in that order. Used to work great on ATT but they added a whitelist for devices sadly so doesn't work on there anymore. T-mobile works more than fine. Verizon, will take some time getting on it. You need to change your modem and have the sim provisioned for an LTE only device. So far I have gotten data working on it but nothing further. Someday Ill get around to badgering verizonn support more and get it worked out.
I'm pretty sure you won't be able to get it working on Verizon. It supports the AT&T bands, but they've not whitelisted it, as you say.
But Verizon uses entirely different LTE bands, which the XZ1C doesn't have.
Or maybe that's what you mean by "change your modem", but I'm not sure how you've done that, as it's a hardware thing, not software.
tonsofquestions said:
I'm pretty sure you won't be able to get it working on Verizon. It supports the AT&T bands, but they've not whitelisted it, as you say.
But Verizon uses entirely different LTE bands, which the XZ1C doesn't have.
Or maybe that's what you mean by "change your modem", but I'm not sure how you've done that, as it's a hardware thing, not software.
Click to expand...
Click to collapse
Nope, it supports all the verizon bands now since 3G was sunset there. You can use it on Verizon as an LTE only device. You initially gotta get a phone with LTE only provisioned on the network and then switch sims to the xz1c. A guy already got it working and I did have data working too.
No the modem is a software thing. I'll do a write up someday. Actually I use the ir51_ir92 modem for T-Mobile too.
Oh, interesting. That's good to know. I've been having issues with T-Mobile lately, less LTE (more Edge) even though the XZ1c should do LTE. Perhaps Verizon would be better for me.
I'm definitely interested in the other modem software if it has a chance of improving things. Make sure to include steps to roll back, please!
Try the modem. Download quick selector from the play store, then make a new widget from it and select "modem switcher". Make sure debug = true in the build.props. Then from the modems select ir51_ir92_ims. It should help getting more LTE from T-Mobile from my experience.
I'm not seeing an app by the name "quick selector". Can you give me an id/link?
What is it doing? Is it installing something, or changing some configuration on my phone? How can I be sure this modem option won't break something?
tonsofquestions said:
I'm not seeing an app by the name "quick selector". Can you give me an id/link?
What is it doing? Is it installing something, or changing some configuration on my phone? How can I be sure this modem option won't break something?
Click to expand...
Click to collapse
QuickShortcutMaker - Apps on Google Play
Create shortcuts quickly and launch your favorite actions quickly.
play.google.com
Opens an activity. No it won't, I've done this on two phones, it just changes the modem.
I'm feeling more at a loss today time than usual, probably because I'm misunderstanding something key, or because of our ROM differences.
I've installed the app, but the search (which doesn't work on normal mode) doesn't have anything under "modem" or "switcher".
I've added debug=true to my build.props, but I'm guessing there isn't actually a top-level one, and that you wanted a more specific one ... but I'm not clear which.
What am I missing?
Also, to be clear: Is this something to be done once, or on every boot? I'm assuming the former. It seems like there should be another way of getting to the configuration, rather than having to install apps to trigger specific intents.
tonsofquestions said:
I'm feeling more at a loss today time than usual, probably because I'm misunderstanding something key, or because of our ROM differences.
I've installed the app, but the search (which doesn't work on normal mode) doesn't have anything under "modem" or "switcher".
I've added debug=true to my build.props, but I'm guessing there isn't actually a top-level one, and that you wanted a more specific one ... but I'm not clear which.
What am I missing?
Also, to be clear: Is this something to be done once, or on every boot? I'm assuming the former. It seems like there should be another way of getting to the configuration, rather than having to install apps to trigger specific intents.
Click to expand...
Click to collapse
What rom are you using? Just once it has to be done.
I'm running an older Oreo AEX rom - this one, to be precise. https://forum.xda-developers.com/t/aospextended.3859655/
I know it's pretty old, but any upgrade path will require a fair amount of backup/reconfiguration - not to mention experimentation to figure out which new ROM to use. I've had a lot on my plate for a while, and this is my daily driver.
tonsofquestions said:
I'm running an older Oreo AEX rom - this one, to be precise. https://forum.xda-developers.com/t/aospextended.3859655/
I know it's pretty old, but any upgrade path will require a fair amount of backup/reconfiguration - not to mention experimentation to figure out which new ROM to use. I've had a lot on my plate for a while, and this is my daily driver.
Click to expand...
Click to collapse
Strange, I'm running https://forum.xda-developers.com/t/g8441-xz1c-8-1-resurrection-remix-v6-2-1-oreo.4085427/ so that shouldn't be a problem. Try "CustomizationSelector" and then under it select the one with "Modem Switcher"
Do you mean this Sony app? I don't have it on my phone. The rom didn't come with it, and I'm not able to install it (really, the older version that's compatible with Oreo).
If I try (via a terminal, to see the error), I get the following message:
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY: Package couldn't be installed in /data/app/com.sonymobile.customizationselector: Package com.sonymobile.customizationselector requires unavailable shared library semc_bootinfoif; failing!]
Click to expand...
Click to collapse
and I'm not sure where I'd even find that, let alone properly install it on the rom. Maybe via Magisk?
Any other ideas or suggestions on things to try? I feel like there should be some way to do ti.
It might be that one. Um, have to install that shared library, whatever it is. Maybe I could even just copy it and share it with you.
I have the G8441 (with US ROM oem.sin) on both MetroPCS and T-Mobile.
If your running the US stock sony rom on latest Pie:
T-Mobile works very well, both LTE and VoLTE. No problems.
Same used to work for me also on MetroPCS, but now VoLTE does not work on their network right now. IMS Registration: Not Registered. Looks like Metro now 'tricks' the phone to use the default non-tmobile modem. This happened just recently. Should be (fairly) easily fixable if I can gain temproot and force the t-mobile MVNO's modem config id.
If your running a stock non-US rom (specifically non-US oem.sin), LTE will work but poorly, and VoLTE will not work at all on both MetroPCS and TMobile.
The phone should work equally well on Mint Mobile too, unless they are playing tricks like Metro.
tonsofquestions said:
I'm not seeing an app by the name "quick selector". Can you give me an id/link?
What is it doing? Is it installing something, or changing some configuration on my phone? How can I be sure this modem option won't break something?
Click to expand...
Click to collapse
Flash the latest Pie US sony stock rom on it. Tick the 'IMS' APN, restart the phone twice, wait a half hour, and you're LTE will work like a champ on T-Mobile.
Once on the US rom:
Dial '*#*#7378423#*#*' and click Service info > Software info > Scroll all the way to the bottom and you'll see 'Current Modem Config'.
The correct modem config for TMobile with LTE and fully functional VoLTE will read exactly /system/etc/customization/modem/amss_fsg_lilac_tmobile_us_ims_tar.mbn
The incorrect (default) firmware (likely) will read /system/etc/customization/modem/amss_fsg_lilac_tar.mbn. This modem config will not work correctly on TMobile. You'll get poor signal and performance on LTE, and VoLTE will not work at all.
eparr said:
If your running the US stock sony rom on latest Pie:
Flash the latest Pie US sony stock rom on it. Tick the 'IMS' APN, restart the phone twice, wait a half hour, and you're LTE will work like a champ on T-Mobile.
Click to expand...
Click to collapse
Did you see my comment half a dozen posts back where I said I _wasn't_ running stock, or Pie?
I'm not going to flash that to get this to work - I need other features. And while I'm willing to upgrade, I can't spend the time to do go through that right now since I have some personal stuff going on. But I'm still not going to a stock rom.
I cannot use that service code because I don't have the APK that powers it - it's again dependent on a stock rom. There was a separate discussion about that here.
I don't even have a /system/etc/customization/ folder, let alone any mbn files in it.
I would happily install some extra software (a magisk module, perhaps?) to get it. Do you have the mbn files anywhere, or know where I could obtain them?
tonsofquestions said:
Did you see my comment half a dozen posts back where I said I _wasn't_ running stock, or Pie?
I'm not going to flash that to get this to work - I need other features. And while I'm willing to upgrade, I can't spend the time to do go through that right now since I have some personal stuff going on. But I'm still not going to a stock rom.
I cannot use that service code because I don't have the APK that powers it - it's again dependent on a stock rom. There was a separate discussion about that here.
I don't even have a /system/etc/customization/ folder, let alone any mbn files in it.
I would happily install some extra software (a magisk module, perhaps?) to get it. Do you have the mbn files anywhere, or know where I could obtain them?
Click to expand...
Click to collapse
I did. My post #15 you have quoted wasn't to you. That is a response to the OP 4qx.
My second post #16 was to you.
In reading thru dev notes on the custom roms (Havoc mostly, but lineage too), it seems the devs say the device has to be wired up and running on the correct modem firmware and with VoLTE fully functional on stock before installing their custom roms. That seems counterintuitive to me, but thats what I get from their posts.
You can obtain the stock Pie roms with Xperifirm. Which contain the modem files. Finding older Oreo ones will require a bit of internet digging.
Do you know if you can force a new modem onto your custom rom and it will work? I've looked for a clear answer to that myself and still question what i have read.
If you can force the correct .mbn, would you need the modem from Oreo or from Pie? Oreo's modem is named kudo (if i remember right). Pie's is Lilac (T-Mobile's VoLTE is exactly named amss_fsg_lilac_tmobile_us_ims_tar.mbn). Then Maple and Poplar too which is 10 and 11 (i think). I have the sony stock Pie US rom here unsin'ed and in apktools right now, so i could probably find the lilac modem for you if thats the one you need. Let me know and i'll see if i can extract it.
I know the stock Pie 9.0 amss_fsg_lilac_tmobile_us_ims_tar.mbn works 100% with T-Mobile VoLTE. I bought a T-Mobile sim this week specifically to check it. I'm trying to get this same modem running on a T-Mobile MVNO in Pie. But in my case, i have the modem files in place, but Sony didn't add the code to specificically enable the modem config id's for T-Mobile MVNO's, so im trying to write it in, than inject it into an unrooted pie while retaining bootlock..
There is a catch i noticed, and it might throw you when you install the correct modem. When I put in a TMobile sim into the phone, it takes up to around 20 minutes for T-Mobile to provision VoLTE to the device. IMS Registration status will say 'Not Registered' (on stock) until T-Mobile triggers the provisioning, which seems to happen on some sort of schedule. They are probably checking to see who is running a proper modem before enabling VoLTE provisioning to the device. Its not instant. When you believe you have the correct config and modem files, and think it should work, i'd give TMobile a solid 20 minutes before assuming it's not working.
Here you go.
From US Pie stock rom, the modem files are in the system_X-FLASH-ALL-C93B.sin file. I used unsin to extract them to .ext4. Then used 7zip to extract the .mbn files from the .ext4 file. The mbn files are found in the directory \etc\customization\modem\. If you need the .mbn files from other versions, they probably will be in the same location.
There were 3 Pie modem files related to T-Mobile. Attached in the zip below. The ims one is T-Mobiles VoLTE for Pie.
Yes, the one I quoted was unattributed, but in the other post (#16) you specifically said to flash PIE, which had been talked about.
I suspect it depends a little on what kind of ROM it is and what it builds on under the hood. I thought mine had the right stuff initially, but it was a long time ago.
Do you know if you can force a new modem onto your custom rom and it will work? I've looked for a clear answer to that myself and still question what i have read.
Click to expand...
Click to collapse
I have no idea about this. I'm happy to try and see what works, but I've likewise found little in the way of instructions - even where the files would go. Again, I don't have that /system/etc/customization/ folder, and I believe some kind of overlay/binaries needs to exist to pick it up. I suspect just adding the files won't work.
As far as I understand it, the codenames are not related to OS version but rather which model of phone it is.
Poplar is the XZ1, and Lilac is the XZ1C. A search shows that Maple is the XZ Premium.
I can't find any information about a 'kudo' (it's also not a type of tree).
There's a Kumano platform, analagous to Yoshino (XZ*), but I don't think that's what you mean, either. I would hope the modem files are independent of OS vesion. I do have an Oreo sin somewhere around on an older drive that i could dig up to compare.
But the challenge remains that I still have no idea what to do with them...
I appreciate your copy of them, though. Any other thoughts?