• 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

Tito23p said:
Is tdm the only one working on this ROM?
this ROM should be the definitive choice for everyone.
Click to expand...

Easier said than done. We have a decent amount of devs on this phone but some with more experience than others. We have also lost devs to other devices. I'm more than willing to be patient while tdm works his magic. When the time comes when he needs help with an issue, we will all be the first to know. Towards the end I'm sure some others will jump in and help patch up the little things, but to build from source takes hours just to compile to even begin working on it. And that's just the rom, now account for the kernel build. It's a lot of unpaid time put in. We don't need to keep asking for updates, as I have never seen any Dev in here be selfish. When they get to a comfortable point you will see alphas with bugs and testers. In the mean time, download the first jb rom posted not too far back.
 
Phrant1c said:
Easier said than done. We have a decent amount of devs on this phone but some with more experience than others. We have also lost devs to other devices. I'm more than willing to be patient while tdm works his magic. When the time comes when he needs help with an issue, we will all be the first to know. Towards the end I'm sure some others will jump in and help patch up the little things, but to build from source takes hours just to compile to even begin working on it. And that's just the rom, now account for the kernel build. It's a lot of unpaid time put in. We don't need to keep asking for updates, as I have never seen any Dev in here be selfish. When they get to a comfortable point you will see alphas with bugs and testers. In the mean time, download the first jb rom posted not too far back.
Click to expand...

-_- I downloaded it the same day it came out and and already reported the bugs that I noticed :smokingsomb: , was just a question :rolleyes:, because he is the only one I see with news about the ROM ;)
 
Tito23p said:
-_- I downloaded it the same day it came out and and already reported the bugs that I noticed :smokingsomb: , was just a question :rolleyes:, because he is the only one I see with news about the ROM ;)
Click to expand...

I too have been following this thread from the beginning, but I see no need to keep asking for updates, which is just annoying. Pestering the developers for updates has done nothing but harm, in my opinion.

I commend you for your enthusiasm, but be patient. In addition, I am not sure if you are aware, but it is generally considered bad etiquette to request updates in this forum.
 
mvaness said:
I too have been following this thread from the beginning, but I see no need to keep asking for updates, which is just annoying. Pestering the developers for updates has done nothing but harm, in my opinion.

I commend you for your enthusiasm, but be patient. In addition, I am not sure if you are aware, but it is generally considered bad etiquette to request updates in this forum.
Click to expand...
My question again : ''Is tdm the only one working on this ROM?'' ... just curiosity...
where's the word ''update'' in that question? :rolleyes:
 
Why's everyone ganging up on tito23p when he asked one person and that person didn't have any problem answering him as he did ...I don't understand why ppl get mad when someone asks a question, if you don't want to answer you don't have to, but don't be putting ppl down let's be civilized #onelove
 
Bloodawn said:
mines been set at

CONFIG_FRAMEBUFFER_CONSOLE=y
# CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY is not set
# CONFIG_FRAMEBUFFER_CONSOLE_ROTATION is not set

is that how yours is? or did you enable detect primary and rotation too?
Click to expand...

Yeah that's exactly it, thanks.
 
Phrant1c said:
Did that kernel work with the camera drivers for the spectrum?
Click to expand...

Yeah it all works beautifully. Mainly because we have a leaked ics rom to pull from. But with the marquee, I don't think we have that. We only have a p970 rom. That works if and only if the two have the same camera sensors.
 
tdm said:
Yeah it all works beautifully. Mainly because we have a leaked ics rom to pull from. But with the marquee, I don't think we have that. We only have a p970 rom. That works if and only if the two have the same camera sensors.
Click to expand...

We're those the same drivers we couldn't find for cm9? Or was there an official that came out after that?

It looked like there were some missing camera resources in the original cm9. We'll cross that bridge when we come to it. Thanks for all the hard work. It's stuff like this that motivates people to do this in the first place.
 
Phrant1c said:
We're those the same drivers we couldn't find for cm9? Or was there an official that came out after that?

It looked like there were some missing camera resources in the original cm9. We'll cross that bridge when we come to it. Thanks for all the hard work. It's stuff like this that motivates people to do this in the first place.
Click to expand...

I don't remember now, I'll look at it soon though. Syncing my jb tree now. 138mb in diffs just for frameworks/base in 3 weeks. :eek:
 
Hmm, it looks like CM10 no longer boots. I suspect it was the recent 4.1.2 update. Based on diffs from the p930, looks like some recent change stopped automagically including init.$hardware.rc. Need to dig in tomorrow.
 
Guys, just popping-in real quick to let you know I deleted just a few off-topic posts up above.

Posting your appreciation and showing enthusiasm is indeed welcome--but at the same time, this is a development thread and an effort should be made to keep things on-topic.

Apologies for the couple of posts that I did delete above...selective editing didn't make sense, but I simply wanted to remove the off-topic stuff from here (not every deleted post is "bad", sometimes they just get caught-up in the conversation that needs to go away--thanks for understanding).

Thanks to all and please let me know if you have any questions.
 
Got a couple surprises this morning. I compiled a kernel to test the framebuffer console (which I really need for getting the p970 ics kernel running) and ... it booted into my jb build from yesterday. wtf?!? lol. But, unfortunately, the fbcon didn't work. So I'm going to see if I can get jb working with the current kernel (plus any tweaks required) for now.
 
Does anyone know what mmcblk0p8 is for?

I was developing on my Spectrum yesterday and forgot I had plugged in my in-service Marquee to charge. I wrote the Spectrum boot partition to mmcblk0p8 on the Marquee and then realized my mistake when it said "out of space". Doh!

mmcblk0p8 is not in the fstab. The phone boots and runs fine. And on my dev phone, it seems to be an ext4 filesystem that is empty.

So any clues what it might be for?
 
tdm said:
Does anyone know what mmcblk0p8 is for?

I was developing on my Spectrum yesterday and forgot I had plugged in my in-service Marquee to charge. I wrote the Spectrum boot partition to mmcblk0p8 on the Marquee and then realized my mistake when it said "out of space". Doh!

mmcblk0p8 is not in the fstab. The phone boots and runs fine. And on my dev phone, it seems to be an ext4 filesystem that is empty.

So any clues what it might be for?
Click to expand...

Not sure what its for, but i found this. not sure if it helps


You will need to boot into my recovery and open adb shell.
This will cause loss of all data contained on /data which will lose your /data/media.

From adb shell:

mount (This is to check data isn't mounted. If mounted use "umount data")

mke2fs -j -b 4096 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
e2fsck -fy /dev/block/mmcblk0p8

After this is done your file system on /data will be fixed. You can install the ROM of your choice. Good luck!



EDIT: it looks like that block is empty/misc. used for mounting ext4?
http://androidforums.com/5021332-post28.html

also, found this with block descriptions
major minor #blocks name description

179 1 2048 mmcblk0p1 (First stage bootloader - dbl.mbn)
179 2 2048 mmcblk0p2 (Second stage bootloader - osbl.mbn)
179 3 7168 mmcblk0p3 (fota)
179 4 1 mmcblk0p4 (EBR)
179 5 16384 mmcblk0p5 (/persist)
179 6 237568 mmcblk0p6 (/cache)
179 7 4096 mmcblk0p7 (blank, Unknown)
179 8 24576 mmcblk0p8 (Misc.)
179 9 8192 mmcblk0p9 (boot.img)
179 10 4096 mmcblk0p10 (modem fs1)
179 11 4096 mmcblk0p11 (modem fs2)
179 12 368640 mmcblk0p12 (/system)
179 13 925696 mmcblk0p13 (/data)
179 14 8192 mmcblk0p14 (recovery.img)
179 15 2023424 mmcblk0p15 (/sdcard)
179 16 28672 mmcblk0p16 (amss.mbn, FAT16)
179 17 4096 mmcblk0p17 (appsbl)
179 18 8192 mmcblk0p18 (adsp, same as mmcblk0p20)
179 19 28672 mmcblk0p19 (amssbak, FAT16)
179 20 8192 mmcblk0p20 (adspbak, same as mmcblk0p18)
179 21 16384 mmcblk0p21 (/mpt)
 
  • Like
Reactions: tdm
Okay back in business with cm10, more or less. It boots and runs anyway.

rild is crashing, I think I might have lost my change to fix that.

Other than that, I think I'm back to the functionality of test1.

Now, on to look at audio routing...
 
You must log in or register to reply here.
Back
Top Bottom