[SELFKANG AOSP ROM] CyanogenMod 7.1 GSM Version [UPDATE 10/23 AM] - Motorola Droid 3

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).

Related

[Q] Sprint Tab; want Gingerbread; don't care about phone service

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.

Samsung Galaxy 8.9" 4G Jelly Bean?

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)

[Q] No 3g with CM 10.1 plus some other less severe issues

Greetings,
Just a few days ago I installed the most recent CM 10.1 nightly, first 20130319 and now updated to 20130323. For the most part, my phone is working well, but I do not have any 3g data service nor have I had it since installing CM 10.1.
I have a Droid 3 XT862 being used in the US on Verizon's CDMA network and placing and receiving calls works. I *can* send and receive SMS as well, although in a test I did toay I sent very short 25 character text from my Droid 3 on the Verizon network to another Android device on the Sprint network and it arrived a mere 2h15m later.
I have read many messages on this forum and others, but either the problem addressed is too far removed or the ideas/changes suggested are offered with little explantion as to why, so I am unsure if making any of these changes would be a good idea. I did read through the build.prop on my device and it certainly appears that it is more or less configured and ready for CDMA usage. I have performed a *228 PRL update, but it did not appear to help. CM 10.1 makes available, unlike the stock ROM, a menu/page full of mobile network settings. I have tried to work with some of these settings, toggles, preferred network types, and so on, but again none of these changes seems to have had an effect on my 3g data connection.
Am I doing something wrong? Does anybody know how to fix this? Or perhaps it is a new/temporary bug in CM 10.1?
As for the operation of everything else under CM 10.1, I like it very much. It is a very big step up from before, when I was first using stock Android 2.3.4 followed by the Maverick ROM, which, while better, sure liked to crash/reboot when under memory pressure. I do have a few issues that I hope others might be able to help with:
* The hardware keyboard's ALT key does not appear to work anymore which rules out half the symbols on the keyboard, making it far less useful. I also cannot use it any longer with VX ConnectBot as some of the mappings do not seem to work. For example, the "OK" key used to work as a CTRL key. Maybe these are related? Any idea how to fix this?
* The backlight on the hard buttons and on the keyboard was, previously, triggered by a light sensor (I think). Now the backlight comes on when there is any tapping, swiping, or button/key activity. That's fine, except that the timeout for the light is extremely short, on the order of about two seconds. In a dark environment, this can be annoying.
* It's slow... my god is it slow! I think this is due almost entirely to a severe lack of free RAM on the device, but I don't know what to do about it. Some programs, like GMail, take forever to start, while many others are just very slow to use/respond. I see the "Not Responding" popup appear *much* more than ever before, but, as I know these apps are just slow and not dead, I always just tap on "wait" and go on with what I was doing.
I really don't think I have that much running in the background or foreground to use all of this RAM. I have replaced Trebuchet with NemusLauncher in hopes of freeing some memory. I have three widgets only: a clock/weather widget, the standard calendar widget, and the Google Voice inbox widget. In the background, besides whatever Android and CM run, I have Google Voice and imo (the instant messanger) running. I believe that is it. Is there *anything* I can do to improve the speed issue? I understand how Android handles memory, so it is clearly not about just increasing the "free RAM" value. That said, however, it seems that if there were fewer apps trying to use the limited memory then this would naturally be higher to begin with.
I have a decent collection of apps, but the number is much smaller than in the past and most all of them should remain dormant unless I actually run them... or so I believe.
Okay, so those are the issues. I could add battery life and the camera to that list, but I have read on the forum that, no thanks to Motorola, the camera is unlikely to be available anytime soon, and I have also read that the battery issues should be resolved soon.
So, um... please help! And great many thanks to all of the hard working devs who bring us better software and especially to those who help those of us with devices that are practically *new* and yet abandoned by the carriers. Extra kudos to those finding ways to work around locked bootloaders and proprietary binary blobs.
--John Gruenenfelder
Can you force it to EVDO only? And what happens in a stock ROM?
In the mobile network settings page, as mentioned above, I can, and have, tried many of the options. Among them is the preferred network type.
It defaults to 'global' which actually sets it to LTE/CDMA, though this is not an LTE device. I have tried all of the options that make sense (i.e. nothing GSM related). I have tried Evdo-only and currently have it set to 'CDMA/Evdo auto'.
None of these settings has changed anything. To test, I disable WiFi and see if I have a Net connection.
With the stock ROM, as well as the Maverick ROM, when I have 3g, the letters '3g' appear in the status bar next to the mobile signal strength icon and there are two small arrows to indicate I/O. This is what I expected to happen with CM.
-Sent from my XT862 using xda app-developers app
I have a 3g update, but no solution yet.
In the mobile net settings page I have the network set to 'CDMA/EvDo auto'. Then I turn on airplane mode to force the radio off, then turn airplane mode back off.
The radio comes back and as it does I can see the network strength icon briefly add an R, presumably meaning reconnecting, followed by a 1x, and finally by a 3g. Then the 3g disappears. This entire sequence takes only about 3 to 5 seconds. If I do this while viewing Settings->About->Phone, I can see the current radio/network states change. Of course, I do all of this with my local wifi connection off.
Also, I did try a network type of 'EvDo only' and the above sequence still occurred but without the 1x step. However, this sequence didn't seem to occur as reliably as when the network is set to 'CDMA/EvDo auto'. For reference, the phone info page under settings indicates that this phone or network is 'CDMA - EvDo rev. A:6'.
So, it would seem 3g is at least possible, if fleeting. What should I do now? I really don't want to stop using CM 10.1.
--John Gruenenfelder
Same issue here. No 3g. In the system status, it will briefly show the mobile network status as "connecting" then drop back to disconnected.
If you reboot into stock it works right?
MrObvious said:
If you reboot into stock it works right?
Click to expand...
Click to collapse
Me or rocksolid99?
In my case, I, well, did not follow the correct Safestrap update procedure when I went from 1.x to 3.05. As such, I *think* my stock ROM may be slightly hosed. I *do* have a complete backup of the original stock that I created with Safestrap 1.x, but 3.05 does not "see" it when I tap on the "Restore" button in recovery. So, I have it, I'm just not sure what I should do if I really need to restore that backup.
However, I have installed the Minimoto 1.7 ROM into slot 2 in Safestrap 3.05 and if I use that ROM (which is a super stripped down Droid 3 stock) then 3g works just fine. I did not have any network/connection issues and did not need to take any extra steps to get 3g to work.
--John Gruenenfelder
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium
Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Click to expand...
Click to collapse
Really? Good to know. Thanks for the info.
If I might reiterate on my other CM 10.1 problem, they keyboard? Right now, the ALT key does not work which means that I cannot access most of the punctuation keys. Strangely, in many apps when I press ALT I will see the cursor change with the upside down triangle at the top of the cursor bar indicating that ALT has been pressed. Good, but if I press any other key it is not recognized. It is as though I had not pressed anything. The ALT indicator doesn't even change or go away. The only thing I can do is continue to press the ALT key to cycle through its states (off, one-key, locked). Could this also be a bug in CM 10.1?
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Thanks again!
--John Gruenenfelder
JetpackJohn said:
Is there a better or more correct location to submit these issues? Since these issues are/may be bugs in CM 10.1, should I not submit a bug report directly?
Click to expand...
Click to collapse
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
Beyond the 3g/data and keyboard issue is the RAM usage. It uses a *lot* of RAM. Is this just the way it is? The Droid 3 lacks enough RAM to really make a serious go at Android 4.2?
Click to expand...
Click to collapse
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.
doogald said:
As a matter of fact, there is: http://androidhosting.org:8050/projects/device-motorola-droid-3-xt862
Hashcode tweeted that last night...
When Motorola hinted that this was the reason why the D3 and X2 would not get ICS, nobody believed them.
I think it's pretty clear that CM on the Droid 3 at the moment is alpha/beta status. If you want stability and full features, you need a Gingerbread ROM. Minimoto is best for me.
Click to expand...
Click to collapse
+1 anything above gingerbread is not stable. Some people manage to use them for daily drivers but they have to deal with the bugs. Myself, I need a camera and I need my phone to work all day, I use it for my job. As such, I run minimoto, as it is quite stable, and any bugs that do arise can be dealt with as it's based on gingerbread, which is stable on our devices. Liberty is also a good rom to use, it's based on an older system version but it's quite stable and has lots of features, as opposed to Minimotos minimalist goal.
Sent from my XT860 using xda premium
has anyone tried making a swap partition for cm10.1 ?
I made it and it seems to be much much faster or the latest nightly (04/07/2013) is quicker.
anyhow I have it up only for about an hour it remains to be seen during the day how it's reacting
regards
Endoroid said:
I'm pretty sure data has not worked in cm10.1 since 3/11 build.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Have you (or has anyone) successfully booted CM10.1 on the XT860? I just get bootloops after install. MiniMoto has been working great for me though.

Droid 3 XT860 gsm/XT862

JUST A WARNING! if you attempt this i will not be held accountable for any issues. you have been warned!
Long story short, looking for roms to try. i found this while searching http://d-h.st/Ici, [Liquidsmoothv3.0 4.4.2 Kitkat] No camera, not sure on other issues!
I downloaded it and it runs rather well, a few hiccups. it seems to run only on GSM though, but i could be wrong. if needed i could upload a few pictures to thread. however ( i know this is the case with some gb roms with gsm fixes, same with ics and jellybean, as needed with build.prop tweaks) but for the life of me cannot get gsm to activate data, it can receive and make calls, send sms. it doesnt seem to like saving apns, theres a mod called
http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
it lets me save apns, but if i add to many things. the apn doesnt save. but if i out the basic info i need to activate data on any other rom, it doesnt activate at all. if anyone tries this and gets data working. please let me know! goodluck
LiL_Assassin said:
JUST A WARNING! if you attempt this i will not be held accountable for any issues. you have been warned!
Long story short, looking for roms to try. i found this while searching http://d-h.st/Ici, [Liquidsmoothv3.0 4.4.2 Kitkat] No camera, not sure on other issues!
I downloaded it and it runs rather well, a few hiccups. it seems to run only on GSM though, but i could be wrong. if needed i could upload a few pictures to thread. however ( i know this is the case with some gb roms with gsm fixes, same with ics and jellybean, as needed with build.prop tweaks) but for the life of me cannot get gsm to activate data, it can receive and make calls, send sms. it doesnt seem to like saving apns, theres a mod called
http://www.internauta37.altervista.org/how-and-patch-fully-enable-gsm-verizon-cdma-phones-android
it lets me save apns, but if i add to many things. the apn doesnt save. but if i out the basic info i need to activate data on any other rom, it doesnt activate at all. if anyone tries this and gets data working. please let me know! goodluck
Click to expand...
Click to collapse
There is a thread for that rom http://forum.xda-developers.com/showthread.php?t=2674609&page=3
I just added a wifi fix to the rom, I never tried 3g just wifi.
sd_shadow said:
There is a thread for that rom http://forum.xda-developers.com/showthread.php?t=2674609&page=3
I just added a wifi fix to the rom, I never tried 3g just wifi.
Click to expand...
Click to collapse
Hey mate, i know. im sorry i should have quoted you on that fact, Wifi works really well. I dont suppose you could take a look at the 3g/data. i could help debug it if you need to. as weird as it sounds, its a really smooth rom, no pun intended lol. every other rom i have tried lags :/

Carriers for Xperia XZ1 Compact in US?

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?

Categories

Resources