Be VERY careful flashing a GSM rom on this thing, especially if you don't do it through Clockwork. If your partition table gets scrambled you're in big trouble.
The Following 2 Users Say Thank You to tickerguy For This Useful Post:
Device(s): OG HTC EVO 4G (JellyBean), Motorola Triumph (ICS), LG Optimus V, Motorola Backflip
Carrier: Not Provided
Thanks: 168
Thanked 134 Times in 38 Posts
Maybe this could be a fix for keymapping
If i go into /system/usr in that rom and replace those folders with the ones from /system/usr on a 2.2 will they fix the keymapping? Thats what we did with optimus S roms with the Optimus V we when we flashed the optimus rom on the the keys was incorrect so we swapped out the folders and it worked. Maybe it will on this.
Last edited by StaticMaal; August 28th, 2011 at 06:55 PM.
If i go into /system/usr in that rom and replace those folders with the ones from /system/usr on a 2.2 will they fix the keymapping? Thats what we did with optimus S roms with the Optimus V we when we flashed the optimus rom on the the keys was incorrect so we swapped out the folders and it worked. Maybe it will on this.
you could always try.... and how would we change the rom from gsm to cdma?
Device(s): OG HTC EVO 4G (JellyBean), Motorola Triumph (ICS), LG Optimus V, Motorola Backflip
Carrier: Not Provided
Thanks: 168
Thanked 134 Times in 38 Posts
Quote:
Originally Posted by ziggy46
you could always try.... and how would we change the rom from gsm to cdma?
Technically speaking it is cdma but its a cdma that uses a sim card. Thats what i think otherwise i think we wouldnt be able to call and text. Other than i dont know what to do. I'm newbie really i dont know that much about android software.
Where'd it come from? Talk to whoever published the link.... if you can figure that out.
The only difference between a RUID-card phone and ours is where the subscription information comes from (card .vs. NVRAM in the radio.) It could take anywhere from a half-hour to a long time to fix it up, depending on how dumb the implementation is.
Incidentally the reason the data won't come up is that the radio has to be in one of two states on a CDMA phone for it to happen: Either RUIM_READY (same as a SIM but on a CDMA phone - up and accessible) OR NV_READY.
If it's not in one of those two states data will NOT start. That's the bottom line; if you have a ROM that is built for a RUIM-capable phone and does not include the ability to run without one, you're dorked and done as the code will never go into the proper state to ask the NV for the subscription information and data will not come up.
If you look under system information your phone number, the MID and PRL are probably also missing on that screen - those come from the NV on our phones.
I doubt there's a way to fix this without source to the entire ROM in question - or at minimum source to rild, which you could recompile and change the callbacks out of it to send a State 9 (NV_Ready) up the stack. That SHOULD work.
(Fighting with this crap is part of what's causing me trouble with CM7 right now; I'm neck-deep in this part of the code at present and I understand it pretty well. Our wonderful Triumph radios keep telling Android that it has a SIM slot, and there's no SIM in the slot. That doesn't work so well either considering there's no slot.)
The Following User Says Thank You to tickerguy For This Useful Post:
Incidentally the reason the data won't come up is that the radio has to be in one of two states on a CDMA phone for it to happen: Either RUIM_READY (same as a SIM but on a CDMA phone - up and accessible) OR NV_READY.
If it's not in one of those two states data will NOT start. That's the bottom line; if you have a ROM that is built for a RUIM-capable phone and does not include the ability to run without one, you're dorked and done as the code will never go into the proper state to ask the NV for the subscription information and data will not come up.
If you look under system information your phone number, the MID and PRL are probably also missing on that screen - those come from the NV on our phones.
I doubt there's a way to fix this without source to the entire ROM in question - or at minimum source to rild, which you could recompile and change the callbacks out of it to send a State 9 (NV_Ready) up the stack. That SHOULD work.
(Fighting with this crap is part of what's causing me trouble with CM7 right now; I'm neck-deep in this part of the code at present and I understand it pretty well. Our wonderful Triumph radios keep telling Android that it has a SIM slot, and there's no SIM in the slot. That doesn't work so well either considering there's no slot.)
Yikes... Any reason the radio is relaying that information? would the radio be built specifically for use without a sim in which case it should never know anything about a sim card to begin with... Or is it a radio used with sims programmed not to look for one?
It's not the radio, it's the load you're using. The radio has NV in it that has your MDN (phone number) and MID (a relative of it, but not the phone number) along with the PRL. All that has to be there and the phone has to know what it is. If you have a RUIM slot then that stuff is in there. But in ours there's no slot, so it's in NV.
If the code is built to use only an RUIM, like a SIM, then it won't come up because it doesn't know to ask the radio for the information. You can make voice calls and send text messages because the radio is working, but Android will refuse to go into data mode until the subscriber information is known to the device - which means the radio has to be in one of those two states or it won't attempt to bring up a data connection.
I assume the reason it allows voice calls is so you can call 911 without being authenticated.
Motorola's radio code in this thing is well-beyond "squirelly"; it is sending up state codes that are blatantly wrong. I had to hack around this in the CM7 software to get data to work on there, and I assume the same thing will apply to this version.
Yes but there is no audio (at all) due to a driver problem of some sort at present. Getting the radio to come up far enough to receive and send a SMS or make/accept a call occurred several days ago - getting the phone to come up into data mode was considerably more difficult.
Getting the code working to that point led me to dig through most of the radio-related code (the related parts are all in the framework, incidentally, which is interesting in and of itself) and at this point I understand the conditions that must exist for Android to attempt starting a data session. Note that by default the debugging statements are off in the log, so a logcat on the radio will imply what the problem is but likely won't TELL YOU which state condition is prohibiting the start - I had to add several debugging statements to discern that and be able to trace it down.
Last edited by tickerguy; August 29th, 2011 at 05:47 AM.
Yes but there is no audio (at all) due to a driver problem of some sort at present. Getting the radio to come up far enough to receive and send a SMS or make/accept a call occurred several days ago - getting the phone to come up into data mode was considerably more difficult.
Getting the code working to that point led me to dig through most of the radio-related code (the related parts are all in the framework, incidentally, which is interesting in and of itself) and at this point I understand the conditions that must exist for Android to attempt starting a data session. Note that by default the debugging statements are off in the log, so a logcat on the radio will imply what the problem is but likely won't TELL YOU which state condition is prohibiting the start - I had to add several debugging statements to discern that and be able to trace it down.
Thank you so much for your work on this! Ya know I flashed this Andro-Id rom and found it to be sooo much better than stock aside from 3g and 1x not working. It was smoother, better battery, less bugs... I'm having gingerbread withdrawals lol. I'd flash back but I realized how often I use data so I'll stick here for know I suppose. But once again thanks a bunch man!
Forget it. The best bet for Gingerbread is the CM7 line of code. If you want you can also take a crack as AOSP but I got started with CM7 so here we are....
This phone does not have the RUIM module and as such it's simply not going to to work.
was this project abandoned? is there no possible way to get this working i mean cm7 is 2.3 and that is working only problem i see here is data... can't be that had to fix can it?
EDIT: does HDMI work with this rom?
Last edited by Mobstergunz; January 7th, 2012 at 03:57 PM.
oh yeah it booted and everything... just no 3g and the process "media" force closes alot
i don't get any force closes but definitively no 3g in my opinion with some tweaking and fixing the capacitive buttons this would be better then cm7 and by the looks of it we would be able to theme this bad boy easily
i don't get any force closes but definitively no 3g in my opinion with some tweaking and fixing the capacitive buttons this would be better then cm7 and by the looks of it we would be able to theme this bad boy easily
it does look sweet! i used the kernel out of cm7-reloaded... and didnt wipe anything before flashing.
[ROM] Andro-ID v.3.3 RC2
Maybe this could be a fix for keymapping
~Faster Internet~
what exactly controls the data?
