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

Root ICS/CM9-JB/CM10 Development Thread

lMonsterl said:
I haven't scrapped it but I haven't been working on it much. Too into ics (not only for this phone) but I will have a stable build, I just can't tell u when. I graduate college next week so it should free up some time. It's based on cm7 so if one works both work, not that many will be interested in gb anymore. I'd honestly rather go forward, look towards jb or miui 4
Click to expand...

Congrats on graduation :beer: lewa has a nice UI to it.
I've been using job on my kindle fire and it sure is smoother than ics(almost didn't think it was possible) smooth as butter.
 
tcaudill01 said:
Having some signal issues. Only getting 1x up and down. Using the same prl a I had with CT mod and I was getting 3G there. Any ideas or anyone else seeing this?
Click to expand...

Same here only thing is that i get roaming and jumps from 1x, 3g and roaming. Also what i noticed its that if you have boost running ct mod and you flash this rom my phone was picked as being a sprint phone but flashed a stock boost rom and then the rom picked it up as boost but in the notification bar it will not show boost it shows roaming indicator off.
 
FYI @tdm - For the AS855 I found the following items in:

cm_device_lge_AS855 / cm.mk
Code: 
PRODUCT_RELEASE_NAME := Marquee
stock is
PRODUCT_RELEASE_NAME := Ignite

PRODUCT_BRAND := Sprint
stock is
PRODUCT_BRAND := lge
cm_device_lge_AS855 / BoardConfig.mk
Code: 
TARGET_OTA_ASSERT_DEVICE := sniper,marquee,AS855
stock is
TARGET_OTA_ASSERT_DEVICE := sniper,ignite,AS855
I'm going to start a thread in the Ignite forum and see if we can get people to post their build.prop, mms_config.xml and eri.xml. That should give us a good look at how the other small carriers are setup. Might have to right up a how-to first.:)
 
Craptorman said:
FYI @tdm - For the AS855 I found the following items in:

cm_device_lge_AS855 / cm.mk
Code: 
PRODUCT_RELEASE_NAME := Marquee
stock is
PRODUCT_RELEASE_NAME := Ignite

PRODUCT_BRAND := Sprint
stock is
PRODUCT_BRAND := lge
cm_device_lge_AS855 / BoardConfig.mk
Code: 
TARGET_OTA_ASSERT_DEVICE := sniper,marquee,AS855
stock is
TARGET_OTA_ASSERT_DEVICE := sniper,ignite,AS855
I'm going to start a thread in the Ignite forum and see if we can get people to post their build.prop, mms_config.xml and eri.xml. That should give us a good look at how the other small carriers are setup. Might have to right up a how-to first.:)
Click to expand...

I'll change PRODUCT_RELEASE_NAME and PRODUCT_BRAND right now. But I'm pretty sure that switching marquee for ignite in the TARGET_OTA_ASSERT_DEVICE is a bad idea. Aren't the Ignite users using the same recovery as the rest of us -- the one from PlayfulGod, that indentifies as marquee?
 
tdm said:
I'll change PRODUCT_RELEASE_NAME and PRODUCT_BRAND right now. But I'm pretty sure that switching marquee for ignite in the TARGET_OTA_ASSERT_DEVICE is a bad idea. Aren't the Ignite users using the same recovery as the rest of us -- the one from PlayfulGod, that indentifies as marquee?
Click to expand...

pretty sure he is
 
I believe they are different. Playful made the one for the ignite first. I believe this did not work on the marquee as he had to modify something to get it to work on the marquee. Trying to find that initial thread.... Playful would probably remember.

I know the userdata partition size is different.
Ignite - BOARD_USERDATAIMAGE_PARTITION_SIZE := 2147483648Marquee - BOARD_USERDATAIMAGE_PARTITION_SIZE := 3109945344

Found the intial thread
 
Craptorman said:
I believe they are different. Playful made the one for the ignite first. I believe this did not work on the marquee as he had to modify something to get it to work on the marquee. Trying to find that initial thread.... Playful would probably remember.

I know the userdata partition size is different.
Ignite - BOARD_USERDATAIMAGE_PARTITION_SIZE := 2147483648Marquee - BOARD_USERDATAIMAGE_PARTITION_SIZE := 3109945344
Click to expand...

Okay thanks, I'll get the partition size changed as well.

The OTA assert needs to match ro.product.model in the recovery. If you were able to install this ROM without removing the asserts, then it matched. So whatever you're running is not identifying the device as "ignite". Though adding "ignite" to the list certainly couldn't hurt.

Can you extract your recovery and paste the ro.product.* section?

Thx!
 
Just realized if the userdata changed, then system probably also changed. I'll need both of these for sure. And for cempleteness, boot and recovery sizes as well.
 
Here's the info I gave Playfulgod. I do have to remove the assets to install your CM9 builds, I'll try and get recovery exctraced.

Also, here's what I have for each one.

Ignite
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 429916160
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2147483648

Marquee
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 429916160
BOARD_USERDATAIMAGE_PARTITION_SIZE := 3109945344
 
  • Like
Reactions: tdm
Craptorman said:
Here's the info I gave Playfulgod. I do have to remove the assets to install your CM9 builds, I'll try and get recovery exctraced.

Also, here's what I have for each one.

Ignite
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 429916160
BOARD_USERDATAIMAGE_PARTITION_SIZE := 2147483648

Marquee
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 429916160
BOARD_USERDATAIMAGE_PARTITION_SIZE := 3109945344
Click to expand...

Hmmm.... where did that extra space go in the ignite? Does it have a bigger boot, recovery, and/or radio partition? A new partition? It's not just wasted, is it?

BTW, doing a test compile from the repos at thebigq, looks like it might succeed. That means my device and vendor files are pretty much in order, as well as the basic manifest and vendor/cm tweaks. Next up is to fork frameworks/base for the RIL stuff.
 
tdm said:
Hmmm.... where did that extra space go in the ignite? Does it have a bigger boot, recovery, and/or radio partition? A new partition? It's not just wasted, is it?
Click to expand...

Dude. They left that space unpartitioned. You have nearly 1gb of wasted flash. :/
 
tdm said:
Can you extract your recovery and paste the ro.product.* section?Thx!
Click to expand...

Extracted my recovery.img and here's what I have:
Code: 
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_ignite
ro.product.device=ignite
ro.product.board=ignite
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
 
  • Like
Reactions: tdm
Compiled successfully. But I won't be able to update the RIL code in frameworks/base until tomorrow.
 
tdm said:
Compiled successfully. But I won't be able to update the RIL code in frameworks/base until tomorrow.
Click to expand...

tdm, I'm planning to flash your latest update tomorrow for a friends phone. Were you expecting to have vibration fixed for hopefully tomorrow new build?
 
@tdm - I created a thread under the Ignite section asking Ignite users for their info so hopefully we could see how these other small carriers are setup.

I was thinking about all the small carriers out there and having all the different operator.alpha and operator.numeric values. I had an idea to throw by you and see what you thought.

Maybe they could add a line/lines to the /sdcard/.install.prop like "ro.cdma.home.operator.alpha=xx", where xx is the carrier name, ro.cdma.home.operator.numeric=xx", where xx is the mnc&mcc, etc..

Or, just edit build.prop after install.

Just a thought.:D
 
  • Like
Reactions: tdm
Anyone notice the in-call volume is extremely loud? It's so loud the speaker distorts and people 3 to 5 feet away can hear the person on the other end with the volume at absolute minimum.
 
Is it just me or is tapatalk totally screwed recently? Blank posts all over and won't quote the correct post when replying, for starters.

If you see weird posts from me, it's likely that. Sorry.
 
tdm said:
Is it just me or is tapatalk totally screwed recently? Blank posts all over and won't quote the correct post when replying, for starters.

If you see weird posts from me, it's likely that. Sorry.
Click to expand...

its not just u, ive had to edit more than a few weird posts.
 
You must log in or register to reply here.
Back
Top Bottom