• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP] CyanogenMod 7 | Android 2.3.5 | Last Version: CM7-Triumph-09182011 (discontinued)

Yeah, it pretty much has to be one of two things, since I now know that the baseband code is there, it is running, and Android can "see" it:

1. Those unhandled upbound calls are necessary for the code to init properly, and CM7 doesn't know what they are and how to handle them.

AND/OR

2. There's something you have to "poke" in the Baseband to tell it to init and attach properly, likely AGAIN something undocumented. This is entirely possible for a "home only" no-contract phone.

I'm digging through the Moto code to see if I can find the missing "bits". That may take some time, as this is my first aggressive attack on an Android device (I've got nearly 30 years under my belt as a software developer however, going back to Z-80 assembler) and as such I lack the environment-specific knowledge to know where to focus my attention; I'm quite-confident that the answers can be discovered and the results will come, whether by me or someone else.

Incidentally bluetooth is also no good in CM7 at present but some of the released software from Moto appears to relate to the bluetooth implementation, so that's likely resolvable too.
 
Message to :
isaacj87, and wsimon:
After Installing both update-cm-7.1.0-RC1-Triumph-KANG-signed and the updated one, I get the message "The application DSPManager(process com.bel.android.dspmanager) has stopped unexpectedly. -Force Close-
I Wipe data/factory reset, cleared cache, and dalvik cache.... Any reason why no 3g?
Other than that, Looks great!! +1
 
Ok, I think I know what's going on.

The CDMA radio code is dying on the vine, and I suspect the reason is that the MDN and MIN are not set somewhere in the code. Remember, the Virgin CDMA system requires you to PROGRAM those - they have their "activation" thing but even that doesn't set them to zero (or undefined values).

I attempted to transplant the Virgin APK to do this and it loads but won't run (the "original" Virgin apks are in the "hidden" directory on the base load they provide) - so there's something missing - probably a library somewhere - that's required. The interesting thing is that it says the phone is unactivated now - on a reboot with the bits I found and transplanted it comes up, sees the network and shows the "activate" icon on the status bar which means it thinks it's not activated but I can't get into the application - it blows up as soon as I try to run it.

Here's the fragment from the base code load that's pertinent:

Code: 
D/RILJ ( 315): [0003]< BASEBAND_VERSION M76XX-AAABQOLYM-1200-001200-00^M
D/RILJ ( 315): [0004]> RIL_REQUEST_DEVICE_IDENTITY^M
D/RILC ( 93): UI --- RIL_REQUEST_DEVICE_IDENTITY (98) ---> RIL [RID 0, token id 4, data len 0]^M
D/RILC ( 93): RID 0 nv srv 3GPP(1): modem id=0, ma=Multimode(0), net pref=CDMA EVDO(4)^M
D/RILJ ( 315): [0005]> RIL_REQUEST_GET_ACTIVE_PROFILE^M
D/RILC ( 93): RID 0 nv srv 3GPP2(0): modem id=0, ma=Multimode(0), net pref=CDMA EVDO(4)^M
D/RILC ( 93): RID 0 NV is the CDMA subscription source^M
D/CDMA ( 315): Event EVENT_RADIO_OFF_OR_NOT_AVAILABLE Received^M
V/PHONE ( 315): [PhoneProxy] EVENT_RADIO_STATE_CHANGED : newState = RADIO_OFF^M
D/RILC ( 93): Reply to RIL --> SIWA key xxxxxxxxxxxxxxxxxxx^M
D/RILC ( 93): Reply to RIL --> IMEI 00xxxxxxxxxxxxxx, IMEISV 00, ESN xxxxxxxx, MEID xxxxxxxxxxxxx^M
D/RILC ( 93): UI <--- RIL_REQUEST_DEVICE_IDENTITY (98) Complete --- RIL [RID 0, Token 4, Success, Len 20 ]^M
D/RILC ( 93): UI --- RIL_REQUEST_GET_ACTIVE_PROFILE (109) ---> RIL [RID 0, token id 5, data len 0]^M
D/RILC ( 93): RID 0 nv srv Common(2): modem id=0, ma=Multimode(0), net pref=CDMA EVDO(4)^M
D/RILJ ( 315): [0004]< RIL_REQUEST_DEVICE_IDENTITY {00xxxxxxxxxxxxx, 00, xxxxxxxx, xxxxxxxxxxxxxxx, xxxxxxxxxxxxxxxxxxxxxxxxx}^M
V/PHONE ( 315): [PhoneProxy] setPowerStateToDesired : mDesiredPowerState = true, getRadioState() = RADIO_OFF^M
Ok, so far this looks like the below example - more or less. But then we have this...

Code: 
D/RILC ( 93): Reply to RIL --> ACTIVE_PROFILE 1^M
D/RILC ( 93): UI <--- RIL_REQUEST_GET_ACTIVE_PROFILE (109) Complete --- RIL [RID 0, Token 5, Success, Len 4 ]^M
D/RILJ ( 315): [0005]< RIL_REQUEST_GET_ACTIVE_PROFILE {1}^M
Nothing in the CM7 code appears to try to set that. And I bet that "Active Profile 1" is the MDN/MID. The rest of this corresponds - more or less - with the below, right up until it blows up.... read through
Code: 
D/RILJ ( 315): [0006]> RADIO_POWER^M
D/RILC ( 93): UI --- RIL_REQUEST_RADIO_POWER (23) ---> RIL [RID 0, token id 6, data len 4]^M
D/RILC ( 93): PBM oprt mode check enabled^M
D/RILC ( 93): RID 0 ph srv Common(2): modem id=0, ma=Multimode(0), net_pref=CDMA EVDO(4)^M
D/RILC ( 93): Request Radio On^M
D/RILC ( 93): MID 0 curr oprt_mode 6 exp oprt_mode 5^M
D/RILC ( 93): [RID 0] ReqList entries :^M
D/RILC ( 93): RIL_REQUEST_RADIO_POWER (23), token id 6^M
D/RILC ( 93): RID 0 MID 0 Received CM_PH_COMMAND_CALLBACK : Req ID 1^M
D/RILC ( 93): RID 0 MID 0 Queued event CM_COMMAND_CALLBACK (16 bytes)^M
D/RILC ( 93): qcril_event_main(): 1 items on queue^M
D/RILC ( 93): RID 0 MID 0 De-queued event CM_COMMAND_CALLBACK (65537)^M
D/RILC ( 93): RIL <--- CM_COMMAND_CALLBACK(65537), RID 0, MID 0 --- AMSS^M
D/RILC ( 93): Change the state of ReqList entry to AWAITING_MORE_AMSS_EVENTS state : RIL_REQUEST_RADIO_POWER (23), Token ID 6, pending CM_PH_EVENT_OPRT_MODE (69632)^M
D/RILC ( 93): qcril_event_main(): Waiting...^M
D/RIL_IccCardProxy( 315): Received Cdma subscription source from NV: true^M
D/RIL_IccCardProxy( 315): Switching to QuiteMode.^M
E/RIL_IccCardProxy( 315): Broadcasting intent ACTION_SIM_STATE_CHANGED READY reason null^M
D/RILC ( 93): RID 0 MID 0 Received phonesvc event : CM_PH_EVENT_OPRT_MODE (69632)^M
D/RILC ( 93): RID 0 MID 0 Queued event CM_PH_EVENT_OPRT_MODE (6744 bytes)^M
D/RILC ( 93): qcril_event_main(): 1 items on queue^M
And then a bunch of other messages ending with the registration information and we're good.

CM7 does this:

Code: 
D/RILJ    (  300): [0004]> BASEBAND_VERSION
D/RILJ    (  300): [0005]> RIL_REQUEST_DEVICE_IDENTITY
D/RILJ    (  300): [0004]< BASEBAND_VERSION M76XX-AAABQOLYM-1200-001200-00
D/CDMA    (  300): Baseband version: M76XX-AAABQOLYM-1200-001200-00
D/RILJ    (  300): [0005]< RIL_REQUEST_DEVICE_IDENTITY {00xxxxxxxxxxxxxxxxxxxx, 00, xxxxxxxxxxxx, xxxxxxxxxxxxxx, xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx}
Note: NO PROFILE REQUEST! And now we try to turn it on and....

Code: 
D/RILJ    (  300): [0006]> RADIO_POWER
D/RILJ    (  300): [0006]< RADIO_POWER
D/RILJ    (  300): [UNSL]< UNSOL_RESPONSE_RADIO_STATE_CHANGED SIM_NOT_READY
D/RILB    (  300): Notifying: Radio On
D/RILB    (  300): Notifying: radio technology change CDMA OFF to GSM
Boom!
Code: 
D/CDMA    (  300): [CdmaServiceStateTracker] Radio Technology Change ongoing, setting SS to off
D/RILJ    (  300): [0007]> GET_CURRENT_CALLS
D/CDMA    (  300): Event EVENT_RADIO_ON Received
D/PHONE   (  300): [PhoneProxy] Switching phone from CDMAPhone to GSMPhone
D/PHONE   (  300): [PhoneProxy] Make a new GSMPhone and destroy the old CDMAPhone.

Which is a pretty good indication that the baseband code comes up, sees something independently (like the MDN/MID and/or everything else!) it doesn't like or doesn't understand, and then sends up an unsolicited "Screw you, no service possible" up the stack.

The other point is that CDMA workshop sees everything when I connect to the phone with CM7 running... but still, it looks like we've got something here that the baseband code wants sent up to the stack (perhaps this odd Virgin "Activation" stuff) and since it doesn't get it's not happy. This might also explain the "unhandled" async upbound message.
 
bradhoschar said:
Message to :
isaacj87, and wsimon:
After Installing both update-cm-7.1.0-RC1-Triumph-KANG-signed and the updated one, I get the message "The application DSPManager(process com.bel.android.dspmanager) has stopped unexpectedly. -Force Close-
I Wipe data/factory reset, cleared cache, and dalvik cache.... Any reason why no 3g?
Other than that, Looks great!! +1
Click to expand...

How can I say this nicely? Read the first post. >:(

Yeah but seriously, he states that nothing radio wise works, no calling no text no 3g
 
tickerguy said:
Ok, I think I know what's going on.

The CDMA radio code is dying on the vine, and I suspect the reason is that the MDN and MIN are not set somewhere in the code. Remember, the Virgin CDMA system requires you to PROGRAM those - they have their "activation" thing but even that doesn't set them to zero (or undefined values).

<snip>
Click to expand...

Great find! Maybe this overlay from the OV CM7 port may help? https://github.com/inferiorhumanorg...70/packages/apps/Phone/res/values/strings.xml

EDIT: This could also be applicable: https://github.com/inferiorhumanorg...48382b1f3fd84868c4ac8f80dd2557102c3cb#overlay

Also, some build props that I haven't tried yet for provisioning: https://github.com/inferiorhumanorg...af19f0e800a91aa82d9bf4200609625074fa2#overlay

(Obviously, not Sprint's info, but same general idea.)

My Ubuntu installation went in the crapper. I decided to go with Fedora, but I have to reinstall everything. I'll try implementing some of this stuff tomorrow. I have to re-download the source, but I'll push my idea soon.
 
No, ##Virgin# doesn't do anything on CM7; I transplanted the apk and accessed it (well, tried to) off the app in the drawer.
 
Ok, I'm making some progress here...

First, we have some missing proprietary files in the build. I pushed them - among them were bin/rild, lib/libril.so and a few others. So first question is this: Why are files that are in the proprietary directory getting overwritten in the final product output? That obviously has to be fixed.

But now I get an exception on the 1033 and 1035 setup messages:

Code: 
D/CDMA ( 607): Baseband version: M76XX-AAABQOLYM-1200-001200-00
D/CDMA ( 607): Event EVENT_POLL_CALLS_RESULT Received
D/CDMA ( 607): [CdmaCallTracker] update phone state, old=IDLE new=IDLE
D/RILJ ( 607): [0010]> GET_CURRENT_CALLS
D/RILJ ( 607): [0010]< GET_CURRENT_CALLS 
D/RILJ ( 607): [0011]> OPERATOR
D/RILJ ( 607): [0011]< OPERATOR {, , }
D/RILJ ( 607): [0012]> GPRS_REGISTRATION_STATE
D/RILJ ( 607): [0012]< GPRS_REGISTRATION_STATE {4, null, null, 0, null, null, null, 0, null, null, null, null, null, 0}
D/RILJ ( 607): [0013]> REGISTRATION_STATE
D/RILJ ( 607): [0013]< REGISTRATION_STATE {4, null, null, 0, null, null, null, 0, null, null, null, null, null, 0}
D/RILJ ( 607): [0014]> QUERY_NETWORK_SELECTION_MODE
D/RILJ ( 607): [0014]< QUERY_NETWORK_SELECTION_MODE error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/GSM ( 607): [DataConnection] Stop poll NetStat
D/GSM ( 607): [DSAC DEB] trySetupData with mIsPsRestricted=false
D/RILJ ( 607): [0015]> BASEBAND_VERSION
D/RILJ ( 607): [0016]> GET_IMEI
D/RILJ ( 607): [0017]> GET_IMEISV
D/RILJ ( 607): [0015]< BASEBAND_VERSION M76XX-AAABQOLYM-1200-001200-00
D/RILJ ( 607): [0016]< GET_IMEI 
D/RILJ ( 607): [0017]< GET_IMEISV 
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_NITZ_TIME_RECEIVED 11/08/21,16:56:15-600,00
I'm now getting the carrier name from the firmware (not from the pre-set name, which is slightly different) so the radio IS talking to me.

Code: 
D/RILJ    (  702): [0011]< OPERATOR {VirginMobileY`n, , 310000}

I'm also getting THIS!

Code: 
D/RILJ    (  923): [UNSL]< UNSOL_NITZ_TIME_RECEIVED 11/08/21,17:07:59-600,00
D/PHONE   (  923): PhoneSubInfo finalized
D/CDMA    (  923): RuimSmsInterfaceManager finalized
D/CDMA    (  923): RuimPhoneBookInterfaceManager finalized
D/CDMA    (  923): IccCard finalized
D/CDMA    (  923): RuimRecords finalized
D/CDMA    (  923): RuimFileHandler finalized
D/CDMA    (  923): [CdmaServiceStateTracker] CdmaServiceStateTracker finalized
D/RILJ    (  923): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ    (  923): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ    (  923): [UNSL]< UNSOL_NITZ_TIME_RECEIVED 11/08/21,17:09:00-20,01
So we're UP, other than handling these damned 1033/1035 upbound messages.

We're missing a proprietary file or three yet, and I bet this comes up. We need to know what handles those network state messages. Anyone have an educated guess?

Incidentally the network thinks I'm registered; it will take a call and try to ring my phone, so it thinks I'm "there". This means the radio itself IS talking to the carrier and IS registered with my MDN and MID.

Oh, pushing those libs blows me up now when I try to press the volume keys... so I screwed something up. Don't try this one at home :-)
 
tickerguy said:
Ok, I'm making some progress here...

First, we have some missing proprietary files in the build. I pushed them - among them were bin/rild, lib/libril.so and a few others. So first question is this: Why are files that are in the proprietary directory getting overwritten in the final product output? That obviously has to be fixed.

But now I get an exception on the 1033 and 1035 setup messages:

Code: 
D/CDMA ( 607): Baseband version: M76XX-AAABQOLYM-1200-001200-00
D/CDMA ( 607): Event EVENT_POLL_CALLS_RESULT Received
D/CDMA ( 607): [CdmaCallTracker] update phone state, old=IDLE new=IDLE
D/RILJ ( 607): [0010]> GET_CURRENT_CALLS
D/RILJ ( 607): [0010]< GET_CURRENT_CALLS 
D/RILJ ( 607): [0011]> OPERATOR
D/RILJ ( 607): [0011]< OPERATOR {, , }
D/RILJ ( 607): [0012]> GPRS_REGISTRATION_STATE
D/RILJ ( 607): [0012]< GPRS_REGISTRATION_STATE {4, null, null, 0, null, null, null, 0, null, null, null, null, null, 0}
D/RILJ ( 607): [0013]> REGISTRATION_STATE
D/RILJ ( 607): [0013]< REGISTRATION_STATE {4, null, null, 0, null, null, null, 0, null, null, null, null, null, 0}
D/RILJ ( 607): [0014]> QUERY_NETWORK_SELECTION_MODE
D/RILJ ( 607): [0014]< QUERY_NETWORK_SELECTION_MODE error: com.android.internal.telephony.CommandException: GENERIC_FAILURE
D/GSM ( 607): [DataConnection] Stop poll NetStat
D/GSM ( 607): [DSAC DEB] trySetupData with mIsPsRestricted=false
D/RILJ ( 607): [0015]> BASEBAND_VERSION
D/RILJ ( 607): [0016]> GET_IMEI
D/RILJ ( 607): [0017]> GET_IMEISV
D/RILJ ( 607): [0015]< BASEBAND_VERSION M76XX-AAABQOLYM-1200-001200-00
D/RILJ ( 607): [0016]< GET_IMEI 
D/RILJ ( 607): [0017]< GET_IMEISV 
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ ( 607): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ ( 607): [UNSL]< UNSOL_NITZ_TIME_RECEIVED 11/08/21,16:56:15-600,00
I'm now getting the carrier name from the firmware (not from the pre-set name, which is slightly different) so the radio IS talking to me.

Code: 
D/RILJ    (  702): [0011]< OPERATOR {VirginMobileY`n, , 310000}
I'm also getting THIS!

Code: 
D/RILJ    (  923): [UNSL]< UNSOL_NITZ_TIME_RECEIVED 11/08/21,17:07:59-600,00
D/PHONE   (  923): PhoneSubInfo finalized
D/CDMA    (  923): RuimSmsInterfaceManager finalized
D/CDMA    (  923): RuimPhoneBookInterfaceManager finalized
D/CDMA    (  923): IccCard finalized
D/CDMA    (  923): RuimRecords finalized
D/CDMA    (  923): RuimFileHandler finalized
D/CDMA    (  923): [CdmaServiceStateTracker] CdmaServiceStateTracker finalized
D/RILJ    (  923): [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
E/RILJ    (  923): Exception processing unsol response: 1033Exception:java.lang.RuntimeException: Unrecognized unsol response: 1033
D/RILJ    (  923): [UNSL]< UNSOL_NITZ_TIME_RECEIVED 11/08/21,17:09:00-20,01
So we're UP, other than handling these damned 1033/1035 upbound messages.

We're missing a proprietary file or three yet, and I bet this comes up. We need to know what handles those network state messages. Anyone have an educated guess?

Incidentally the network thinks I'm registered; it will take a call and try to ring my phone, so it thinks I'm "there". This means the radio itself IS talking to the carrier and IS registered with my MDN and MID.

Oh, pushing those libs blows me up now when I try to press the volume keys... so I screwed something up. Don't try this one at home :-)
Click to expand...

I've already been dealing with the output for awhile. I pushed some changes to the repo. I also pushed changes to the extract-files script, so you'll need to run that again.
 
Cool - will resync, pull again, pull all the base files (first) and keep at it.... if I'm simply duplicating work then I'll try to refocus a bit ;-)
 
Just so you know it was your CM7 build being put out this amazingly fast for the triumph that insipred me to start contributing to these forums man the work you have put in as well as everyone that has contributed makes me a firm believer in the android as the correct choice for anyone. If anyone has read my post entitled "Video Series" I'm planning on making videos of pretty much everything Triumph and putting them up on youtube. I'm not entirely sure on the formalities but if i dont need to i wont bug people about this in the future but Isaac would you be ok with my making a tutorial of your CM7 for how-to's and walk through's for your build? Of course all credit goes to you bro your the MAN!!! PLEASE keep up the amazing work!
 
tickerguy said:
Cool - will resync, pull again, pull all the base files (first) and keep at it.... if I'm simply duplicating work then I'll try to refocus a bit ;-)
Click to expand...

I start school this coming week, so if you have anything good, you can reach me on my Github.

Also, if you're pushing rild and libril from the stock ROM, you're just repeating yourself. The extract-files script pulls those files off already.

I appreciate your help. It may have something to do with the kernel, but it's going to take some investigating. I'll ask around as well.

EDIT: If you could post the disassembled virgin apk somewhere, I'd appreciate it.
 
Looks like the repository is broken right now, but I'll keep trying; it's blowing up in the camera code at present.

I know the extract script was pulling rild and the libril.so and related bits, but they weren't going into the built ROM! I checked it on the device and the checksums and sizes were from the object directories, not from the pulled files. Those weren't the only ones either - and at first blush I'm not sure why (that's gotta be something in the makefiles but I decided to push things over to see if I could get it operating.) What clued me in was the unimplemented and un-noted upcalls - those ARE in the libraries and rild, which led me down that road.

There's another apparent problem with the build environment - I see you pulled over cnd - or think you did - but file doesn't get pulled. Yes, it's in there in the makefile. No, it doesn't wind up in the proprietary directory. The file above it (hdmid) does. I found that one in extract-files.sh and fixed it, but don't know the proper syntax to check it out for mod and then queue it back to you for the git repository (the repo command and working with git is new to me - I'm a cvsup sort of guy ;-))

I'll see what I can find out with ripping apart the Virgin bits. There are some interdependencies there that I'm not clear on at present; there are a couple of apparent dependencies that I found but they won't install as apks. It appears that Virgin did us a bit of a favor in that all of their "special" bits look to have original copies (before install) in /hidden - there may be missing pieces, but the base apks anyway are in there.
 
Hey all, super good work so far on the CM7, I know it'll make the Triumph a beast of a phone. I'm super excited to get something stable and leave my AOSPCmod Optimus V in the dust.

Isaacj87: Got no reason to think you aren't, BUT, make sure you pay attention to getting that silly piece of paper. Employers rarely give you a second look without it. You are a bright dude and rockin' so many ports, but without the 'Stamp of Approval', no one hardly cares. With that paper, you'll have a bright future, and a heck of a resume to land sweet job right out of the gate. Good luck and thanks for all your hard work.
 
The repository is hosed at present; it builds without errors but what it builds will not boot. It doesn't come up at all, so there's no log available; wherever it's failing it's before the kernel loads to the point that it can communicate.
 
LucaBrassi said:
Just so you know it was your CM7 build being put out this amazingly fast for the triumph that insipred me to start contributing to these forums man the work you have put in as well as everyone that has contributed makes me a firm believer in the android as the correct choice for anyone. If anyone has read my post entitled "Video Series" I'm planning on making videos of pretty much everything Triumph and putting them up on youtube. I'm not entirely sure on the formalities but if i dont need to i wont bug people about this in the future but Isaac would you be ok with my making a tutorial of your CM7 for how-to's and walk through's for your build? Of course all credit goes to you bro your the MAN!!! PLEASE keep up the amazing work!
Click to expand...

It was pointed out to me that i missed tickerguy in my big thank you so again thank you tickerguy and anyone that has helped make this dream a reality if i forgot anyone i apologize and please let me know before i make the video so i make sure to give you all proper credit for your work :D
 
tickerguy said:
Looks like the repository is broken right now, but I'll keep trying; it's blowing up in the camera code at present.

I know the extract script was pulling rild and the libril.so and related bits, but they weren't going into the built ROM! I checked it on the device and the checksums and sizes were from the object directories, not from the pulled files. Those weren't the only ones either - and at first blush I'm not sure why (that's gotta be something in the makefiles but I decided to push things over to see if I could get it operating.) What clued me in was the unimplemented and un-noted upcalls - those ARE in the libraries and rild, which led me down that road.

There's another apparent problem with the build environment - I see you pulled over cnd - or think you did - but file doesn't get pulled. Yes, it's in there in the makefile. No, it doesn't wind up in the proprietary directory. The file above it (hdmid) does. I found that one in extract-files.sh and fixed it, but don't know the proper syntax to check it out for mod and then queue it back to you for the git repository (the repo command and working with git is new to me - I'm a cvsup sort of guy ;-))

I'll see what I can find out with ripping apart the Virgin bits. There are some interdependencies there that I'm not clear on at present; there are a couple of apparent dependencies that I found but they won't install as apks. It appears that Virgin did us a bit of a favor in that all of their "special" bits look to have original copies (before install) in /hidden - there may be missing pieces, but the base apks anyway are in there.
Click to expand...

Fixed. Make sure to delete vender/motorola and start over. I removed building against the froyo camera libs.
 
I tried rebuilding this morning and what I got built properly but won't boot - it locks on the splash screen and never gets up far enough to be able to connect to it (e.g. the kernel never starts.)

I'll give it another shot.
 
Just removed the vendor area, repo sync and build - failed at the camera.

(Earlier today it was completing but would not boot.)

Will do a make clean and try again.
 
First, we have some missing proprietary files in the build. I pushed them - among them were bin/rild, lib/libril.so and a few others.
Click to expand...

I think the most important file is the lib/libril-qc-1.so. Do you end up pushing this file as well?

Then I believe in the build.prop it should be set to:

Code: 
rild.libpath=/system/lib/libril-qc-1.so

Maybe give this a shot. Of course I could totally be wrong.

I haven't even loaded the alpha build to my phone yet.

Regards,
 
You must log in or register to reply here.
Back
Top Bottom