Related
I'm just wondering if someone can list any ROMs or flashing methods/guides that work on Bell I9000M phones without losing the 850mhz band.
I'd really like to give Tayutama's SuperLite version a go (for example), but I need the 850mhz band; is it safe? If not is there something we can do to re-enable it without going back to a stock ROM?
I've looked around the forum and not seen any clear answer to this.
Input is appreciated!
I second this.. But im thinking ill be disappointed as ive read a few places that the bell galaxy s cant be flashed with the i9000 roms out there without minor to major issues
i believe if you flash only the pda and leave jh2 modem and jh2 csc. you can flash any of the newer roms 2.1 eclair.. but havent tried it myself.. my one exerience with jm7 when i didnt do this and only kept the csc i lost my 850 mhz.
lgkahn said:
i believe if you flash only the pda and leave jh2 modem and jh2 csc. you can flash any of the newer roms 2.1 eclair.. but havent tried it myself.. my one exerience with jm7 when i didnt do this and only kept the csc i lost my 850 mhz.
Click to expand...
Click to collapse
Does it have to be Eclair ROMs only?
I just spent the night trying various ones and got squat. I did find this post here (forum.xda-developers.com/showpost.php?p=8299301&postcount=18) but it seems to be older and references the JH2 files, and not necessarily a specific ROM.
If I find one that works, I'll post it here.
For now, I'm heading back down to 2.1 stock version (ugh).
http://lmgtfy.com/?q=site:+xda-developers.com+"i9000m"+froyo
I would also like to know as well... I am quite interested in trying Darky's Froyo rom
(Apparently it is safe, will probably give it a shot today at some point)
if you flash only the pda of a rom, and the jh2 modem/csc files, know that you may experience battery drain issues because they do not match. i flashed jpk with jh2 modem/csc for few days and the battery drain was insane. only fix was to flash the full jpk, then re-enable all the bands.
Would love to get an answer for this as well.
Phone crashed on first day from the store. Touchwiz issue had to wipe. So i dont see the down side to flashing when the stock can crash too.
And no gps which is such a letdown. Cant lock location ever.
Sent from my GT-I9000M using XDA App
Okay here are some straight facts - you can flash any of the new roms on a Bell SGS. You need the Bell version of the modem to maintain 850 - it works with 2.2 - it may or may not not be fully optimized for 2.2 but it works just as well as it does on 2.1. It just doesn't matter that much in the grans scheme of things.
All other so-called issues with battery drain, SD card, bricking, weird behavour, etc. are not caused by the ROMs either but rather the execution of underlying apps - usually optimization and timing related issues - if you have a problem it is most likely software related - i.e the app has not been optimized under FROYO.
Seriously, this is not rocket science. You cannot permanently brick your phone from FROYO - it is impossible.
If you want to successfully implement Froyo but are skeptical, pick a ROM, flash the Bell modem and then try it out for a week or two BEFORE dumping a bunch of new apps on it. Then decide if you want to keep it - which you will. Then start finding apps that are Froyo optimized and you will have no issues. Seriously.
rdenis said:
Okay here are someme straight facts - you can flash any of the new roms on a Bell SGS. You need the Bell version of the modem to maintain 850 - it works with 2.2 - it may or may not not be fully optimized for 2.2 but it works just as well as it does on 2.1. It just doesn't matter that much in the grans scheme of things.
All other so-called issues with battery drain, SD card, bricking, weird behavour, etc. are not caused by the ROMs either but rather the execution of underlying apps - usually optimization and timing related issues - if you have a problem it is most likely software related - i.e the app has not been optimized under FROYO.
Seriously, this is not rocket science. You cannot permanently brick your phone from FROYO - it is impossible.
If you want to successfully implement Froyo but are skeptical, pick a ROM, flash the Bell modem and then try it out for a week or two BEFORE dumping a bunch of new apps on it. Then decide if you want to keep it - which you will. Then start finding apps that are Froyo optimized and you will have no issues. Seriously.
Click to expand...
Click to collapse
I didn't flash a bell specific modem. I used the one that came packaged in Docs JPM froyo. Works perfect with no loss of any 850mhz 3G band.
Good job and clarification - as long as the modem supports 850 it does not need to be Bell.
First off for those that think you have WCDMA 850 working after a rom flash designed for another region, make sure you actually try and run only the WCDMA 850 band to see if you actually have it. If your not running on Bell and your network doesn't have WCDMA 850 available to you then you can't check and it won't matter. Any rom designed for a region that doesn't use WCDMA 850 will not give you WCDMA 850 and why should it.
Install whatever rom you want and simply flash your JH2 modem to get your WCDMA 850 back. After the modem flash make sure you put your phone into automatic mode and select all to refresh the modem band availability.
If your able to flash your modem AND your csc you might even get your product code back.... maybe.
For Bell users it would be nice to have a Froyo modem that will support WCDMA 1900 and 850. The 2.1 JH2 works fine though with Froyo.
MKVFTW said:
I didn't flash a bell specific modem. I used the one that came packaged in Docs JPM froyo. Works perfect with no loss of any 850mhz 3G band.
Click to expand...
Click to collapse
Are you sure that you have the WCDMA 850 band functional with the JPM modem? Didn't work for me. Are you on Bell's network?
So is there a way to get the gps working? I can wait on Froyo but the GPS issue is terrible. Also any way to do a true backup of the phone. like an image.
stnd said:
So is there a way to get the gps working? I can wait on Froyo but the GPS issue is terrible. Also any way to do a true backup of the phone. like an image.
Click to expand...
Click to collapse
Can someone confirm whether there is or is not a GPS fix for I9000M for Bell?
opensourcefan said:
Are you sure that you have the WCDMA 850 band functional with the JPM modem? Didn't work for me. Are you on Bell's network?
Click to expand...
Click to collapse
No, im not on bells network. I am on rogers network. Rogers in my area only has 850mhz 3G in this area. I have 3G service and in service mode it says WCDMA 850 Band 5. It works. Its also working on the girlfriends.
Version info:
PDA: i9000XWJP6
PHONE: I9000XXJPM
CSC: I9000XEEJP4
Build: 2010.10
As for the GPS its a bit better but still sucks.
I've never had a GPS problem so I can't tell you if its an issue with the hardware/software/location/interference, etc. Since day 1 (three months ago) I have had no issues locking satellites to 10m accuracy, regardless of firmware. Actually the only time I had an issue was on Osoyoos lake but I suspect that may have had more to do with the proximity to the border crossing.
rdenis said:
I've never had a GPS problem so I can't tell you if its an issue with the hardware/software/location/interference, etc. Since day 1 (three months ago) I have had no issues locking satellites to 10m accuracy, regardless of firmware. Actually the only time I had an issue was on Osoyoos lake but I suspect that may have had more to do with the proximity to the border crossing.
Click to expand...
Click to collapse
Getting a fix isn't the issue. Its active tracking.
Active tracking has been a-o-k the whole time as well which I thought was implied by using the "locking to 10m accuracy" terminology.
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.
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).
I have the 4G version, is this specific model have a working CM10 ROM? I know the Wi-Fi model does, just want to make sure this won't brick mine or anything.
I'm new to this, just got this today!
It does not. Our version (i957) uses a different chipset then the Wi-Fi version. Best to not flash.
Sent from my Galaxy Nexus using Tapatalk 2
CM10 will eventually support this device -- In fact, the device tree was just created by cyanogen yesterday @ https://github.com/CyanogenMod/android_device_samsung_p5att -- However, work still remains to get this code to even boot, let alone be functional as a daily driver. It will get there, eventually.
The ICS (4.0.4) ROM from Samsung for this device is currently in test with the carriers. The Korean variant (SHV-140) just received the ICS update a few weeks ago, and some of that code might help speed along the Cyanogen update.
The CM10 code currently on github does build, but the kernel does not seem to fully boot -- Locks up just after displaying the initlogo, with adb unavailable, so I have no idea how to get the dmesg. I suspect there are some needle-in-a-haystack sort of details that need to get ironed out, the kind of which probably will require some hardware hacking (ie: serial and/or jtag access) to get at... or for the official i957 kernel to get released.
The shv rom has to be out there somewhere
Sent from my SGH-I727 using xda premium
In for the first screenshot of a p5att (SGH-I957) running jellybean, in case you need some encouragement you won't be stuck on honeycomb forever...
No, it's not even close to stable.
Yes, pretty much everything is broken. IE no LTE, audio, and probably everything else I didn't try.
works: wifi, touchscreen.
No, I won't be maintaining a release for this, the people way smarter than me on the cyanogen team did all the real work on this.. I just built and kludged until I got it to boot with graphics If things go well you'll see a real release from the CM team sometime. For all I know they'll run into a horrible problem and give up, but you know how those guys are.. totally badass.
basic idea:
- breakfast cm_p5att-userdebug
- replace msm-8660-common kernel with code from jb-full branch
- *** edit to update: it seems there is no longer a jb-full branch, there is now just jellybean and jb-old. I'm guessing the out of date msm8660-common kernel from what was jellybean is now jb-old, and jb-full has become jellybean.. hmm.. working on seeing if this is the case (need to clone/build/boot it)
- hack p5att boardconfig
- pick your combination of samsung proprietary files, good luck, the note and/or skyrocket CM10 releases are your best starting point
- brunch p5att, consume more coffee and stuffs
- hack resulting .zip to remove assert for 957 (TWRP has wrong product ID lulz)
- hack ramdisk to enable adb on boot so you can debug why it doesnt come up
- hack proprietary files until you get working graphics
** (not for the faint of heart)
nrvate said:
In for the first screenshot of a p5att (SGH-I957) running jellybean, in case you need some encouragement you won't be stuck on honeycomb forever...
No, it's not even close to stable.
Yes, pretty much everything is broken. IE no LTE, audio, and probably everything else I didn't try.
works: wifi, touchscreen.
No, I won't be maintaining a release for this, the people way smarter than me on the cyanogen team did all the real work on this.. I just built and kludged until I got it to boot with graphics If things go well you'll see a real release from the CM team sometime. For all I know they'll run into a horrible problem and give up, but you know how those guys are.. totally badass.
basic idea:
lunch cm_p5att-userdebug
replace msm-8660-common kernel with code from jb-full tree
hack p5att boardconfig
pick your combination of samsung proprietary files, good luck, the note and/or skyrocket CM10 releases are your best starting point
brunch p5att, consume more coffee and stuffs
hack resulting .zip to remove assert for 957 (TWRP has wrong product ID lulz)
hack ramdisk to enable adb on boot so you can debug why it doesnt come up
hack proprietary files until you get working graphics
(not for the faint of heart)
Click to expand...
Click to collapse
nice job man!
EDIT: I created a separate thread for doing the CM10 build: http://forum.xda-developers.com/showthread.php?t=1867579
Cheers!
Still hacking stuff.. lol.. using the file list from the msm-8660 common proprietary file list, i grabbed that set of files from the CM10 i717 ROM and dropped them onto the i957. Working audio! Don't know about the mic, but it plays sound now. Also, it almost got LTE working... logcat -b radio shows the LTE radio finding the LTE cell and reporting signal strength, but the data session doesn't actually establish, even with the proper APN config. GPS looks like it might even eventually lock on, it found 2 sats after a while, but didn't get a lock. I suspect when full 4G comes up, it'll be able to use SUPL to get it's initial location then actually get a fix.
Downloading the gigantic i717 stock image, going to see if 4G plays nicer with the note radios, since I'm using the note RIL now.. Dan had mentioned he had successfully got the note radios running on the tab 8.9 LTE in an attempt to get voice calls up... the honeycomb RIL stuff just results in lots of errors, so thats straight fail.
I didn't realize how many software pieces go into the cellular data connectivity, yikes!
The more I delve into code and binary packages... the more it appears the 957 is very close to a supersized note! sweet.
Also, bluetooth finds my neighbors macbook, so it probably works, but my headset is at work and I haven't been there in a while (hence having time to do this fun stuff).
If anyone has any suggestions on getting LTE up, I'm all ears. If I can get LTE working, I might be tempted to try to package this beast up.
More fun...
Good grief, it looks like the userdebug variant compiles with all the radio debug flags on, thousands and thousands of lines of everything from verbose text to hex dumps!
i957 honeycomb radio: baseband shows unknown, isn't worth anything
i717 ICS radios, both UCLF5 and 6: entire tablet slows to a crawl once rild starts, fail! Nothing useful in the logs as to why, nothing hogging CPU time... no idea, abort
i727 skyrocket ICS radio I727UCALC4 (no idea how current or valid this radio really is): gets HSPA+ on old 3G "wap.cingular" SIM, no luck with tablet only LTE "Broadband" APN SIM. ~2-2.5mbit download speed.
i727 skyrocket ICS radio UCLD2: Obtained HSPA+ with Broadband APN data-only SIM. ~4.0-5 mbit download speeds. After ~10 minutes, found an LTE cell and pulled 30-35mbit down. After each radio reset (reboot, airplane mode, etc) it takes the 3-10 minute period to get LTE again, and it's also slow (10-50 seconds) to get on HSPA. All around sluggish to jump on a cell, but returns nice speeds once it does so.
i727 skyrocket ICS radio UCLF6 (latest I could find): Pretty much the same as UCLD2 above, similar speeds, but seemed to jump on LTE quicker after a reboot, but still takes a while when coming back from airplane mode. It's the latest, i think, and it works, so it's probably the way to go.
Pending investigation: RIL files -- going to try the skyrocket UCLF6 RIL and see how it works out. Currently still using the note RIL files. Tried UCALC4 skyrocket RIL and it didn't work at all, will try UCLF6 from stock skyrocket ICS release...
Looks like it doesn't like the Broadband APN on a tablet (data-plan-only) SIM. I tossed in a "old school phone SIM" from the 3G days, which is set up on an unlimited phone/data plan (as you could get ages ago) and gave it wap.cingular, and whamo, HSPA+ connectivity. Looks more like a configuration issue and/or the phone RIL/radio combination refuse to play nice with data-only SIM.
I've never tried to debug getting onto 3G/4G service at the RIL radio log level, so not totally sure what to look for, but... guessing it's trying to set up a voice bearer and the UMTS system says F you. need foods, sleep, etc... haha.
And more fun... Skyrocket UCLD2 radio returns HSPA+ connectivity on data-only SIM with Broadband APN, but no LTE. Set APN type to "supl" to enable SUPL, got the first GPS fix in about 2 minutes, after 5 more minutes found 12 sats and obtained 12m accuracy.. sweet!
Update: UCLD2 radio, after sitting around idling for 10 minutes while I made some munchies, decided it would pick up an LTE cell. No idea why it took so long, I'm really close to an LTE cell and both my other LTE devices have never (and don't presently) exhibit this behavior at my location. I suspect this is probably normal behavior of UCLD2 or UCLD2 plays less than optimally with the i957 radio... which should be the same as a skyrocket radio, considering both identify as an M8260 when inquired with "ati" via ttyACM0. Whatever the case, 50ms ping and 30 mbit down works for me...
I really should go to bed sometime...... and make a backup of this device before I bust something!
Adding a little more info: I modified device/samsung/p5att/BoardConfig.mk a little before building... Other devices with no SD card slot had BOARD_HAS_SD_CARD_INTERNAL defined, so i tossed that in. The BOARD_SDCARD_DEVICE_PRIMARY, BOARD_SDCARD_DEVICE_SECONDARY and BOARD_SDEXT_DEVICE_SDEXT values seemed bogus, and I knew the init scripts would set up /sdcard as a fuse device on the /data partition anyways, so I just commented them out.
I don't know if anything uses the 3 values I commented out, but since there's no actual mmcblk device for the fuse (filesystem in user space) emulated sdcard, it doesn't seem a valid value could be found, so, why set one.... Seems to work!
BOARD_HAS_SDCARD_INTERNAL := true
#BOARD_SDCARD_DEVICE_PRIMARY := /dev/block/mmcblk1p1
#BOARD_SDCARD_DEVICE_SECONDARY := /dev/block/mmcblk0p28
#BOARD_SDEXT_DEVICE := /dev/block/mmcblk1p2
Click to expand...
Click to collapse
But, this is my first attempt at hacking cyanogenmod onto a half-baked device, so... don't take my word for it
And before anyone asks, yes, I plan on releasing a flashable update for this, but first... figuring out enough to start from a fresh source tree and build from scratch so I can document how I did this... Let's beat the carriers to jellybean and forget ICS
(yes, I'm editing this post a bazillion times as try stuff, I'll put together something a little more coherent soon)
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?