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?
Related
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.
Hi guys (and girls),
I'm going slightly mad trying to figure out a stable setup for my O2X. I have been switching between the latest CM7 nightlies, and MoDaCo FR19. In general, CM7 gives me quite frequent black screens, and FR19 seems quite stable. However, there is one issue that is present in both ROMs.
I am unable to get a stable mobile data connection when I switch from WiFi. Sometimes it works, and sometimes it doesn't. To get it to work again, it sometimes works to switch to 2G only (and possibly back again). I have tried several different radios recently: 218, 606, and 622, all with the appropriate RIL. The mobile data connection for 218 drops in and out at random without any clear pattern. For the other two radios switching on or off 2G only seems to achieve stable connection. However, it does not actually seem to affect whether I get a 3G or 2G signal. The display can say H or G, even when 2G only is checked. Bluetooth did not work correctly with 606.
To top everything off, the GPS does not seem to behave consistently for a all the different radio versions.
I guess that people have different experience with different radios, so which radio are the guys in Norway using? Do I really have to slog through every released radio and spend the day checking each one of them? Can I expect to find a radio/from combination that blacks to give me a stable GPS and mobile data connectivity, as well as good WiFi?
I know this has been discussed numerous times before, but people never seem to reach any conclusions. I'm just looking for advice on how to proceed to fix my problem.
I'm on cm7 .77 and i honestly havent had a blackscreen since i flashed it (yesterday morning) + battery is good now. For me this is the most stable nightly so ill stick with it for 2 weeks on my holiday )
Edit: bb .502 ril 218(i think) dont have any problems with network switching btw
Sent from my Optimus 2X using XDA App
kolaf said:
Hi guys (and girls),
Do I really have to slog through every released radio and spend the day checking each one of them?
Click to expand...
Click to collapse
You probably have to, yes. This sounds more like a problem with the specific coverage in your area and how the phone interacts with the cell-towers than an actual problem with the phone. You may be in an area with weak signals from several stations, you may be in an area suffering from sudden bursts of noise, there could be a lot of reasons for why this is happening.
First thing I'd try is to upgrade to the latest official firmware (10C - 0622 for Norway), just to have a baseline for comparison. In theory this firwmare (and baseband) has recently been validated by the norwegian carriers, and should have the best chance of success.
Then you should probably do a manual scan (in phone settings) for networks, and pick one manually.
Also try using the INFO menu (*#*#4636#*#*) and see if choosing a specific protocol helps.
If you're still unable to maintain a stable connection, I'd say that'd be grounds for returning the phone for a replacement.
Weak advice, I know, sometimes there just aren't any quick solutions.
::Trym
TrymHansen said:
First thing I'd try is to upgrade to the latest official firmware (10C - 0622 for Norway), just to have a baseline for comparison. In theory this firwmare (and baseband) has recently been validated by the norwegian carriers, and should have the best chance of success.
::Trym
Click to expand...
Click to collapse
Thanks for your reply. Do you by any chance have a link to the firmware?
kolaf said:
Thanks for your reply. Do you by any chance have a link to the firmware?
Click to expand...
Click to collapse
Sort of. In this thread http://forum.xda-developers.com/showthread.php?t=1035041 you'll find complete ROMs of the previous versions. Install one of those with SmartFlash, then run the LG Mobile Update tool to get the latest.
::Trym
Okay, I see, downloading now. So it is good enough to use one of the smartflash files, I don't have to use nvflash?
kolaf said:
Okay, I see, downloading now. So it is good enough to use one of the smartflash files, I don't have to use nvflash?
Click to expand...
Click to collapse
No, you don't have to use NVFlash. The advantage of using the smartflash method is that you get a completely "factory fresh" phone, with all the stock content present (movies, music, pre-installed apps) and you're sure to get a matching baseband and ROM.
Note that you have to flash both files, both the baseband and the ROM. The LG update tool won't update if you have a "new" baseband on an old ROM.
::Trym
So the firmwares from that post do not include the baseband? Anyway, I'm currently running baseband 405, so I guess this is sufficient to get the new update. And the new update will then overwrite everything to the latest official version, both ROM and baseband, correct?
kolaf said:
So the firmwares from that post do not include the baseband? Anyway, I'm currently running baseband 405, so I guess this is sufficient to get the new update. And the new update will then overwrite everything to the latest official version, both ROM and baseband, correct?
Click to expand...
Click to collapse
Yes, it does. Each firmware pack comes with TWO files, the baseband and the ROM. To make sure you avoid any trouble, just flash them both, though, as you say, you can probably stay on the one you have, as yes, the LG Mobile Update tool will overwrite both the baseband and the ROM with the new versions.
::Trym
Flashing of old firmware, with subsequent upgrade to latest release for Norway is complete.
I got version V10c, with baseband 1035.21_20110622, kernel 2.6.32.9. My mobile data seems to be enabled as soon as I get mobile coverage (which admittedly is poor right where I live). Even though it pains me, I guess I should leave it as stock for a day or so to see how it behaves.
I guess rooting it shouldn't affect performance in any way?
My initial experience is that it is much more snappy than the stock firmware that the phone came with, but time will show
kolaf said:
Flashing of old firmware, with subsequent upgrade to latest release for Norway is complete.
I got version V10c, with baseband 1035.21_20110622, kernel 2.6.32.9. My mobile data seems to be enabled as soon as I get mobile coverage (which admittedly is poor right where I live). Even though it pains me, I guess I should leave it as stock for a day or so to see how it behaves.
Click to expand...
Click to collapse
Yeah, you probably should, as your mission right now is to find out whether you can get a stable mobile data connection or not.
kolaf said:
I guess rooting it shouldn't affect performance in any way?
Click to expand...
Click to collapse
Not to my knowledge, but I'd still advise you to wait a few days while sorting out the connection issue. Not that I think rooting it would affect that one way or another, but if you can't get it work as it is, you can return the phone in the state it is now, factory fresh.
kolaf said:
My initial experience is that it is much more snappy than the stock firmware that the phone came with, but time will show
Click to expand...
Click to collapse
It certainly is. It also *stays* snappy over time, which can't be said for the 10a/b versions.
::Trym
The first test drive with the new firmware has been completed. On the way out it switched to mobile data flawlessly, but a longer drive it started falling out and reappearing for only short periods. When we stopped at the destination seemed to stabilise with a 3G connection again.
For the return trip I selected use only 2G network. The network connection remained stable for the entire journey.
I will have to test more, but the conclusion seems to be that it has trouble switching between the 2G and 3G networks when moving. I will try the same trip with a Telenor SIM card, and with different combinations of enabling 2G and 3G modes.
By the way, what is the difference between forcing 2G in the regular settings menu and in the special information menu?
kolaf said:
I will have to test more, but the conclusion seems to be that it has trouble switching between the 2G and 3G networks when moving. I will try the same trip with a Telenor SIM card, and with different combinations of enabling 2G and 3G modes.
By the way, what is the difference between forcing 2G in the regular settings menu and in the special information menu?
Click to expand...
Click to collapse
The 2G only setting in the phone menu equals the "GSM only" setting in the INFO-menu. I'm far from an expert in these matters, this thread has an overview: http://forum.xda-developers.com/showthread.php?t=675136& of what the different modes do.
::Trym
More testing seems to indicate that as long as i leave "use 2G only" check, my mobile data connection seems to be pretty stable. It even switches between 2G and 3G, although apparently a bit more conservatively.
I guess I get to keep my phone anyway
Now for some rooting...
Just an update on the results from my testing. The second time I went out my mobile connection never appeared. This was with only 2G checked in the settings menu. In the Info menu, this corresponded to GSM only.
I then changed it to GSM auto (PRL), and then I got my intermittent mobile data again. I then change it to WCDMA preferred, and my data connection seems to be stable for now. This apparently requires much more testing...
F another chapter in the connectivity saga. Having WCDMA preferred selected in the Info menu, things mostly work, although the data connection drops sometimes.
Another problem I'm noticing with the stock ROM is that it usually is unable to reconnect to my home WiFi network when it comes within range. I have the money was selected to reconnect. Sometimes I even find it disabled in the list.
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).
Hi,
Can anybody suggest a ROM that will work well in the UK, and provides a stock-like experience with a reasonably up to date version of Android. It doesn't have to be bleeding edge - I'd rather have everything working rather than access to the very latest features.
I've currently got a stock ICS, and so wonder if somebody could point me to easy step by step instructions on how to flash the suggested ROM. There's a lot of jargon about safe straps, and so on, and some of the instructions seem to expect a level of knowledge that I don't have (I'm happy to learn if somebody would be good enough to point me in the direction of some documentation).
It's not that I'm overly unhappy with the stock ICS, but there are a few things that aren't working that well for me (MMS, Hotspot, etc) and an annoyance or two (unknown sim source message, and unnecessary Verizon apps) that are making me think I should re-flash to something cleaner.
Cheers,
Steve.
StevePritchard said:
Hi,
Can anybody suggest a ROM that will work well in the UK, and provides a stock-like experience with a reasonably up to date version of Android. It doesn't have to be bleeding edge - I'd rather have everything working rather than access to the very latest features.
I've currently got a stock ICS, and so wonder if somebody could point me to easy step by step instructions on how to flash the suggested ROM. There's a lot of jargon about safe straps, and so on, and some of the instructions seem to expect a level of knowledge that I don't have (I'm happy to learn if somebody would be good enough to point me in the direction of some documentation).
It's not that I'm overly unhappy with the stock ICS, but there are a few things that aren't working that well for me (MMS, Hotspot, etc) and an annoyance or two (unknown sim source message, and unnecessary Verizon apps) that are making me think I should re-flash to something cleaner.
Cheers,
Steve.
Click to expand...
Click to collapse
MMS and hotspot are easy to fix.
I'm not sure who your carrier is, but make sure your APN has MMS in it. When it comes to Hotspot, find my thread on enabling hotspot to work on Rogers wireless, it should give you some ideas. It involves you disabling the entitlement check and then adding (through the same program) a DUN apn type which allows for wireless hotspot to function properly.
I just find ICS slow, and I've loaded up Hashcode's CM10 port. Working pretty well so far, but I do miss a few things about blur.
danifunker said:
MMS and hotspot are easy to fix.
I'm not sure who your carrier is, but make sure your APN has MMS in it. When it comes to Hotspot, find my thread on enabling hotspot to work on Rogers wireless, it should give you some ideas. It involves you disabling the entitlement check and then adding (through the same program) a DUN apn type which allows for wireless hotspot to function properly.
I just find ICS slow, and I've loaded up Hashcode's CM10 port. Working pretty well so far, but I do miss a few things about blur.
Click to expand...
Click to collapse
Thanks - I've rooted now, and managed to get the hotspot working (I think, it's untested, but it at least runs now). I've also got MMS working, which turned out to be a Handcent problem, although the only reason I have Handcent is that stock simply won't work, which is really confusing, because you would expect them to use the same settings.
I also have got rid of the semi-annoying "sim card from an unknown source" message too, and because the phone is rooted, I can get it to reboot daily automatically, which I think will probably help with some of the other weird behaviours I occasionally see.
I guess this has taken the pressure off flashing something new, but if there is a stock-like Jelly Bean ROM then I could be tempted. Presumably because I've rooted, when the official JB comes I'll have to do something special to get it to install, but I guess that will be half the fun.
Cheers,
Steve.
Tether was working fine on Nougat, after adjusting Windows with TTL, a changed user-agent, etc., and then in Android adding the "dun" parameter to my APN, but with any Oreo or Pie ROM, it gets incredibly slow, as if I do not have "dun" in my APN, even when using ROMs that allow "dun" in APN.
I'd really like to upgrade from Nougat, but don't want to give up tether.
Has anyone else faced this issue and prevailed?
EDIT:
I flashed OOS Oreo, tried what settings I could with no good results, then flashed 4.5.1 firmware and modem into it to see if older firmware was the solution, tried what settings I could to no avail.
Back on Nougat now, which does the job just fine.
Alas however, I may never be able to buy a new phone, unless Nougat can be installed onto it.
You're certainly not the only one. Tethering support is getting harder as carriers find ways of making it more restricted. There are ROMs and Devs that have worked on it with mixed results. It's possible with enough leg work you might get it working on a particular ROM, if you can get the dev to work with you on it. Otherwise it's luck of the draw whether you can find a ROM that will work in your particular case.
Telephony is getting complicated and there are more people concerned with VoLTE and the like. Look what a mess that still is on custom ROMs.
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
pbergonzi said:
Does anyone know of any ROMs where this is actively being fixed? That is, one can tether without degradation, as one used to be able to do in Nougat? Tethering works, it's just horribly slow.
Click to expand...
Click to collapse
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Dirk said:
NLOS is your best bet. If it's not working already the dev is willing to work with users to resolve issues.
Here's an example of Tethering restrictions getting worse, with Google leading the charge:
https://www.reddit.com/r/Android/comments/9r6r13/tether_dun_required_no_longer_works_on_pixel_3_xl/
I'm surprised Google don't get whiplash in their haste to bow to pressure from US Carriers.
Click to expand...
Click to collapse
Thank you @Dirk, and agreed--I'm surprised google doesn't get backlash--maybe not enough people tether?
Also surprised that more devs didn't just immediately address that--maybe not enough devs tether?
I may try NLOS, or the Magisk module--it might work.
Does anyone using NLOS know if tether works properly? I will ask in that thread also.