[Xperia Play Android Development] Mills00013:
Zero, I want to do what I can to help you get this working on CDMA devices. I'm tired of the drama going on in the CM7 forums.Time for something fresh.... and you know I know what I'm talking about when it comes to these devices.

I've got your system copied across, it looks like the installation went without a hitch. I pushed out a new build prop to my phone (since the CM7 that I was using had a r800i identifier). The first time it installed wrong (again cause of the prop) and then it installed just fine. I didnt notice that the installation script mentioned patching things on the GSM build (or the fact that it wasnt needed). This leads me to believe that it should have patched something for CDMA, which never seemed to occur. This could be part of the problem.

Secondly, the crash is happening while the boot is still trying to hand off. We never actually get to starting ADB so theres no way to run logcat and dump a log and of course its not going to do you any good accessing adb in recovery. Let me play around with your system a bit and see what I can tinker with to see if there is any ray of light here. I really want to use your build....

If you have any ideas on what I can try, let me know. I'm ready to get this going for all the CDMA users who want to ditch stock and the drama over at the CM7 thread.

Edit: Just for the record, with the build prob set to r800i, the installation (which is of course GSM) does go through and the device does boot. It cannot find the network right off the bat, which is of course expected, but just thought I'd eliminate the kernel being bad or something like that occurring.

Edit Two: I've been examining the install script and I see where I noticed the patch line. I see now that you are copying over the CDMA specific files on top of the GSM ones. I'm going to see what happens when I push these files individually. One thing I did notice (although this shouldnt make any difference as far as getting the boot to begin with) but there are no frameworks for the phone like the Telephony apk. This may or may not be an issue once we can get the system to boot.

Edit Three: I merged the CDMA data files directly into the regular system and data files and the system boots. I no longer have the error message at the top that we cannot find service.... Still investigating....

Edit Four: Zero, get in here. I need your help :D I'm attaching a logcat of whats going on. Its the first 1200 lines or so of the boot process (about to where the launcher would load). I do not have a launcher. I have a bar at the top with your battery tool, and I can pull up the power menu by holding the power button and I can pull down the notification window. It says I have no service in the ERI area, but its not saying it like it was when I flashed the raw GSM version. To eliminate any other issues here, I've now flashed your original GSM build (while identifying myself through the build prop to be an r800i) and in the update.zip I replaced the SemcPhone.apk with one that we know works for CDMA devices (actually pulled from chevy's patch for Frasertags FTS rom). This gets me to the same place that I was when I directly copied your CDMA files into the regular build areas and removed the checks in the update script. So... this means that first off, the reason we couldn't boot is because something goes wrong in the flash. Something isnt copied right. I havn't investigated it, i've just worked around it. second, it means that we need something in addition to the SemcPhone.apk to get CDMA users going correctly. The full logcat is attached. The only mention of the term CDMA is somewhere around like line 688. Line 975 is also interesting... There are a few mentions of the telephony apk running, but nothing that looks erroneous. And sorry for the zip. XDA thinks that 80k is an appropriate maximum size for txt files.... grr....

Edit Five: I just wanted to clarify again where I've gotten to: the phone boots. It doesnt tell me that it cant find a mobile network, but it does tell me there is no service in the ERI are in the pull down menu. LauncherPro does not open at start up. I can open applications manually from the shell with no issues (ie. "am start -a android.intent.action.MAIN -n com.android.settings/.Settings"). Wifi works, browser works. Things look to all work fine except for actual calling and for the Launcher to Launch at start up.

Edit Six: Just a short update here to anyone wondering, LauncherPro works fine, but you do have to invoke it manually: "am start -a android.intent.action.MAIN -n com.fede.launcher/.Launcher" from the shell. You can easily open everything else from there, and like I said, everything works if you're on wifi, but there is no telephone. Zero.... this ROM is sick, my friend. Let's get this going.

Edit Seven: Last update for the night... I copied over all of the proprietary RIL files from a working CM7 install into the system for zero. It looks like there has been no change or difference in the radio working at all. Getting closer though.... Much closer....