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 need a Vogue user who wants to install VaniljEclair RLS9 and then add the update attached in this post: http://forum.xda-developers.com/showpost.php?p=7511486&postcount=612
I want to now a few things before I push the changes in libhtcgeneric-ril.so to the repo.
1. Does the cell tower location changes break anything for Vogue users (I'm pretty sure cell tower location won't work on Vogues but as long as the changes doesn't break Vogue compability then the change would be OK to push)
To test this, just make sure phone calls and data traffic works.
2. Does the pin code changes work on Vogue, at least I'm pretty sure they shouldn't break anything but it would be nice to know if it works on Vogues aswell.
To test this, enable pincode security in Windows mobile (or use another phone to do it) and see if accepts your pincode in android.
If you want to try changing the pincode you propably should use a spare SIM card. It worked fine for me on my Kaiser but I guess there is a risk involved.
I could try and test this, but 1 main question:
I use Sprint network - so my vogue's do NOT have a SIM card?
Would loading this provide any useful testing?
Or does the testing require a phone with SIM card?
Does_It_Matter said:
I could try and test this, but 1 main question:
I use Sprint network - so my vogue's do NOT have a SIM card?
Would loading this provide any useful testing?
Or does the testing require a phone with SIM card?
Click to expand...
Click to collapse
Testing would still be helpful, just to now it still works just as it did before the update.
OK, will try it out after I backup some of my stuff on the phone.
1 More question:
I'm currently running Incubus Release 12 Froyo with the 7/26/10 NBH file
Can I just go ahead and install Eclair?
Or do I actually need to flash an eclair NBH?
kallt_kaffe,
I'm running Froyo RLS 12 from Incubus
I saw your androidupdate.tar file only had this 1 file changed: libhtcgeneric-ril.so
I said what the hell, and just went and applied the update to Froyo RLS 12
Rebooted the phone - no issues, can still make phone calls and can still do data/internet
Is that a good enough test?
Or does Eclair specifically have to be installed on the phone?
Does_It_Matter said:
kallt_kaffe,
I'm running Froyo RLS 12 from Incubus
I saw your androidupdate.tar file only had this 1 file changed: libhtcgeneric-ril.so
I said what the hell, and just went and applied the update to Froyo RLS 12
Rebooted the phone - no issues, can still make phone calls and can still do data/internet
Is that a good enough test?
Or does Eclair specifically have to be installed on the phone?
Click to expand...
Click to collapse
Interesting... I didn't think Froyo would run with a libhtcgeneric-ril.so compiled for Eclair. I've tried the other way around and it left me without any data or phone connetion.
As for your previous question. You can use the froyo kernel on VaniljEclair RLS9. And if it isn't to much trouble, then please test it with eclair too even thought the Froyo test propably proves it works on Vogues.
hey K_K i can test it my vogue isnt active though, if you still need people to test it only problem is i wouldnt be able to do it till later tonight
thoughtlesskyle said:
hey K_K i can test it my vogue isnt active though, if you still need people to test it only problem is i wouldnt be able to do it till later tonight
Click to expand...
Click to collapse
That's OK. Let me know how it goes.
I've been running your Vanilla Eclair full time since release 8, IMHO it is the fastest and most reliable 2.1/2.2 build out there. I will load the update and let you know if I see any issues.
Mike
Well I can confirm that the cell tower location does NOT work for me (Vogue on Verizon CDMA), which I believe was expected. I noticed no other issues with phone/data service though.
Mike
kallt_kaffe said:
Interesting... I didn't think Froyo would run with a libhtcgeneric-ril.so compiled for Eclair. I've tried the other way around and it left me without any data or phone connetion.
As for your previous question. You can use the froyo kernel on VaniljEclair RLS9. And if it isn't to much trouble, then please test it with eclair too even thought the Froyo test propably proves it works on Vogues.
Click to expand...
Click to collapse
Yep - HTC Touch Vogue - Sprint Service
Works without any problems using your fixed file
Data works, calls work, and hell, it even works on Froyo RLS 12 as an update!
Nice one.
golfnz34me said:
Well I can confirm that the cell tower location does NOT work for me (Vogue on Verizon CDMA), which I believe was expected. I noticed no other issues with phone/data service though.
Mike
Click to expand...
Click to collapse
I believe he's just trying to see if the changes he made affect Vogue users at all. The changes were for cell tower location on GSM networks, and since Vogues use CDMA it won't work. He just wants to make sure that CDMA doesn't break. You shouldn't expect to see anything new, just that everything is working as it used to, and it's a good sign that it is.
Thanks everyone who has tested. I'll consider the test to be over and I'll push the new code today.
I was sent this by XDA user: coreless88 who asked me to post this in the dev section (he doesn't have enough posts yet).
** WARNING: I HAVE NOT TESTED THIS PERSONALLY -- USE AT YOUR OWN RISK -- KEEP A BACKUP HANDY **
** THIS ROM IS INSTALLED WITH SAFESTRAP BOOTSTRAP. DO NOT USE KOUSH'S BOOTSTRAP OR YOU WILL SOFTBRICK YOUR DEVICE **
I dabbled in files for some time, twaked the build.prop a little (added some generally known hacks into it for faster touch reaction, better HSPA reception etc.), and added some files .lib/.ro files from Droid 2 Global.
It all worked out nicely. However, as I cannot use a CDMA network (I live in Turkey, so I have only GSM access), I cannot guarantee this will work with CDMA too. I will appriciate it if someone can test it.
Also, Your GSM card will be recognized instantly, but you need to activate the 3G network form the settings, you will need to add your APN manually, atleast in my case I had to put my carriers APN into the list, so this might not be necessary."
Here is the link: http://www.mediafire.com/?d17l4z4885ph4ov
Thanks needs to go to Hashcode, as I just modified and added a missing feature to it.
Click to expand...
Click to collapse
Thanks for the help Hashcode!
I got my clearence to Dev forums, so I will try to contribute even more to this community =] .
First of all, as in my quote in the first post, I cannot guarantee this will work in CDMA network, Hashcode will inspect the files and try to integrate the GSM feature to his original release.
You can find a screenshot of my phone working under the GSM network and 3G enabled.
!!!However, just like any other custom rom, I cannot accept any responsibilities if this rom bricks your phone. !!!
For installing, just use Hashcode's safestrap, for the rest i think you know the drill.
BUGS:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken,
Also be aware, notification and ringtone sounds are silent by default, you just need to go to settings menu and choose a ringtone for yourself =] .
Edit: Also as I have only 1 Droid 3 at the moment, I need as much testers as I can find for checking if this works for all Europe SIM Cards.
Referved for future use/updates/etc...
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
thank YOU !! Hashcode and Coreless88
No thank you guys, for trying it and giving me an easy breath as it is my very first development attempt!
nikeusfr said:
Awesome, very thanks to both Hascode and Coreless88
All work fine in france the signal bdm hspda is very good, than the xt883 rom. Exept the camera all work fine for me.
I'm test, if you want, all other release in france, on bouygues telecom.....
Click to expand...
Click to collapse
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Right now bluetooth doesn't work, but GPU and CPU working properly, if not better than before.
Here are some more screenshots, for Quadrant, SpeedTest, and A Samurai Vengance 2 (BTW Game runs incredibly smooth).
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
nikeusfr said:
one another bug, i'haven't delivery report on sms/mms, there's no sound in the build speaker when i phone or receive call, and the sound is very quiet in the speaker phone or handset.
Click to expand...
Click to collapse
Hi,
First of all, thanks for your input. I need your opinions to make this better. So here we go,
All notifications and ringtones are silent by default.
You need to get to:
"settings>sounds>ring tone/notification tone" menus and choose your ringtones from there.
Sounds are in this built generally low, because there isn't any proper sound resources prepared with OMAP 4 series of SoC's. I will try to enhance them, but I will need time.
But you can make the phone louder on the speaker by going to:
settings>cyanogenmod settings>sound menu then choose the settings you like the most.
What "general" GSM build.prop tweaks are we talking about here?
DoubleYouPee said:
What "general" GSM build.prop tweaks are we talking about here?
Click to expand...
Click to collapse
Hi,
I've added Tweaks for getting stronger reception, making the GSM default network at the boot, tweaks for faster response, etc... You can download the file and look at the system>build.prop (open it via wordpad if you are on windows) and compare it to Hashcode's build.prop.
BTW I am experimenting with audio and video files right now. Post I will post the results when I finish the testing.
Could I apply these build.prop changes my XT862 rom?
Or did you use droid 2 global hacks like someone tried before?
DoubleYouPee said:
Could I apply these build.prop changes my XT862 rom?
Click to expand...
Click to collapse
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
coreless88 said:
Why not, this is a free world, and as long as you know what you are doing you will be safe, but if you're not...
Be aware, "build.prop" is a very risky file to touch, and has a central role for the Android to run correctly. I had to use RSD to get back to original software because I stuck at the Motorola logo after some changes. So I took the hit for you allready =].
My advice, directly flash this rom and don't do any editing. Because I did not just edited the build.prop, also added several library files, done a lot of testing, finded new libraries or edited them to make it work.
It will include lots of time, effort, patience and hell of a risk.
Click to expand...
Click to collapse
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
DoubleYouPee said:
Well I would love to use this mod, but because:
Videos dont run,
Sound is low,
Bluetooth is broken,
Camera is broken
I'd rather have a GSM-fix for the my current ROM, (kinda like XT883, but then easier)
Click to expand...
Click to collapse
Oh!
I completely misunderstand you, I thought you were asking about Hashcode's Cyanogen release. You cannot use these fixes for Motorola roms or any rom that based on a Motorola rom. These fixes and libraries are only for Cyanogen builds, at least thats what I think, as I don't have any development experience with any Motorola rom.
You may try, but that will only make the risk even bigger.
Please be patient, I am trying to fix camera and sound problems right now, and I will try to fix bluetooth in a later date, as I didn't see anyone using bluetooth for ages =] .
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
coreless88 said:
Also I forgot to mention, my tweaks and Cyanogen codes makes GSM reception and HSDPA signal is much more improved than the stock XT862 Rom.
Click to expand...
Click to collapse
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Willis111 said:
Giving this a whirl on my xt860 right now, will edit this post with results. Very nice fellas, thank you both very much! Just want to make sure, this is built for Hashcodes safestrap?
Seems to be doing the same as previous on my bell phone, loops on the first screen, I'm not getting to the boot animation.
Click to expand...
Click to collapse
Hi,
Your thanks are appriciated, and I am sorry for this rom also did not worked for your XT860 =/ . I guess Motorola did everything they possibly can to protect their region based software versions.
I guess the fix will be simple, but I am afraid either Canadian Android developers are rare (BTW I don't think so), or they don't want to develop for / they don't have this device.
The Solutor said:
Yes, as I wrote elsewere looks like the wrong signal measurement is a purposely limit introduced by verizon request.
On D2g is the same, the Cyanogen rom, with the same radio have the correct measurement, the XT883 too.
So could be interesting to understand where that three bars are lost and if a quick fix for the stock ROMS could be possible.
Click to expand...
Click to collapse
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
coreless88 said:
Indeed, It seems low GSM signal was the goal for them. Either for the purpose of making the Verizon "look like" superior to European Networks, or just for making it a Verizon semi-exclusive and a pain in the ass for any other carrier.
Click to expand...
Click to collapse
Indeed this is the only reasonable explanation, the same behavior in five ROMs can't be a bug.
The problem is the Verizon's firmware itself, for example, even the non-US devices (XT860, XT883... you name it) are listed by "cdma_solano" in the build.props, and while those files are filled with CDMA codes, there are hardly more than 6 lines of GSM related codes. So my simple tweaks does nothing to improve the signal (tested/proven).
Click to expand...
Click to collapse
Maybe is omething hardcoded in the libril or whatever in the userland, surely is not the radio itself.
XT883 is not affected, so we should try to replace some piece to spot the culprit, BTW this process would be easier when the bootstrap will be fixed to work on XT883, (why doesn't work on that rom is a another nice mystery).
Indeed, a GSM ROM would be great
FYI, audio and video codec issues are being addressed in my next build of CM7.
I'm going to give the GSM ROM a test drive and see how the CDMA stuff is affected. As well as look at the differences by file.
Hopefully, i can incorporate coreless88's changes back into the main ROM so that we don't end up with 2 CM7 ROMs (CDMA and GSM).
Ive tried with stock 2.3.6, CM7 and CM6 and although the CM roms improved wifi reception by leaps and bounds, my N1 will still not recognize some very necessary wifi SSIDs, namely the one at work. On my laptop, my old phone (Optimus T), and everyone elses smartphones there is no problem connecting at work. The access point is provided by a Fortiwifi 60c server. fortinet.com/products/fortiwifi/60C.html
Has anyone else had this problem or know the right direction for a solution? Wifi at work is a must!
it's not an adhoc network is it?
try moving closer to the source and see if other android phones can see it too
No, the network in question is not an ad-hoc. Yes, as I said in my original post, other smartphones and wireless devices have no problem making this connection.
I flashed and upgraded my phone's baseband radio to the most up-to-date version and my phone still doesn't see the network in question. I'm just about out of ideas.
Radio has nothing to do with WiFi.
Try different kernels.
Make sure that the visible access point isn't Wifi N.
Thanks for the experienced suggestion, thats just what I needed. Is there much risk involved in flashing kernels like there is with radios? Is the process the same, boot into recovery then install zip? Ill do the research myself here in a few hours when Ill have the free time but I'd like your input as well, Jack_R1, since it sounds to me like you know what you're talking about here. I'm hoping that you'll reply before I give this a try.
There is no risk when flashing kernels - in the worst case, if the flash went wrong, you can always boot to recovery and flash again.
The process is the same.
Kernel should be compatible with your type of ROM (AOSP GB/AOSP ICS/CM7/CM9/MIUI/etc).
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?