• 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

It looks like the GPS lib (gps.omap3.so) is related to the RIL somehow because there are a bunch of AT-commands embedded in the lib.

I initially took gps.omap3.so from FOP, which is obviously not matched to our RIL. The reason I did this is that my Sprint version of gps.omap3.so crashes system_server with a SIGSEGV. I think I need to use the Sprint gps.omap3.so and fix the crash, and then GPS should work. Easier said than done, though...

Ha, I pulled the gmp.omap3.so from an older rom and think I ran into this too with a reboot cycle from which I couldn't escape.

Sounds like a monumental task to me without source for that sprint gps library. Wish I could help, but now sounds really, really out of my league. :(
 
Isn't that a bit hasty lol?

Obviously ICS alone will be awesome to have on this phone. However, this device isn't getting any younger so getting the latest android will really rejuvenate it. More devs will probably be interested in the marquee if it's on the latest and greatest software. Also, (and I'm no dev), but I've read that ICS to jellybean is a much easier task than gingerbread to ICS. If so, it makes sense not to waste a lot of time on ICS when you can use that time on JB instead.

Regardless, I'm just happy that you devs are putting so much work into this phone. It's seriously a completely different device coming from stock!

Great job all around!
 
  • Like
Reactions: tdm
Obviously ICS alone will be awesome to have on this phone. However, this device isn't getting any younger so getting the latest android will really rejuvenate it. More devs will probably be interested in the marquee if it's on the latest and greatest software. Also, (and I'm no dev), but I've read that ICS to jellybean is a much easier task than gingerbread to ICS. If so, it makes sense not to waste a lot of time on ICS when you can use that time on JB instead.

Regardless, I'm just happy that you devs are putting so much work into this phone. It's seriously a completely different device coming from stock!

Great job all around!

I was about to get a eco v, than tdm and blood got ics working now I wanna keep this phone. Stock ics is better than any other manufacturer skin.
 
Likely on the heels of ics. As soon as I get an ics beta, I'll start on jb.

You are an animal tdm. I was with the other guys in thinking this phone wasn't going to make it much past stock, but you and blood have made this a really fun phone to have!
 
  • Like
Reactions: tdm
Lmao. My girl uses my ov I hate how small the screen is lol. Then she used my marquee with ics and wouldn't give it up

lol had to buy my wife a optimus s cause she wanted mine, however the lcd broke so i just bought her a used one from ebay 35 bucks, deal and a half do to the fact that TDM released a aokp build of ics for that phone. kinda made me jealous lol
 
Currently playing around with the image formats for the camera.

It looks like the front and back cameras actually have different image formats. Switching the preview conversion function for the back camera from y422_to_yuv420() to yuyv422_to_yuv420() made it look better. Still not correct, but better.

The IMX072 driver source claims that the sensor supports exactly one format, V4L2_PIX_FMT_SRGGB10, which is known as Bayer10 RGGB. I don't have an IMX072 datasheet (is it available?)

I'm trying to wrap my head around these formats and write code to convert SRGGB10 to YUV420 for the back camera.

Handy references for color conversions:

SRGGB10: V4L2_PIX_FMT_SRGGB10 ('RG10'), V4L2_PIX_FMT_SGRBG10 ('BA10'), V4L2_PIX_FMT_SGBRG10 ('GB10'), V4L2_PIX_FMT_SBGGR10 ('BG10'),
YUV420: V4L2_PIX_FMT_YVU420 ('YV12'), V4L2_PIX_FMT_YUV420 ('YU12')
Conversions: YUV to RGB Conversion
 
Oh, and a couple more things:

After fixing up the latona camera code to only use supported methods, the save picture code is running out of memory during JPEG encoding. There must be either a way to have hardware encode it or an OEM camera library function that is optimized for this.

There doesn't seem to be any support for auto focus, but the OEM libraries have some function names that looks interesting.
 
I
Obviously ICS alone will be awesome to have on this phone. However, this device isn't getting any younger so getting the latest android will really rejuvenate it. More devs will probably be interested in the marquee if it's on the latest and greatest software. Also, (and I'm no dev), but I've read that ICS to jellybean is a much easier task than gingerbread to ICS. If so, it makes sense not to waste a lot of time on ICS when you can use that time on JB instead.

Regardless, I'm just happy that you devs are putting so much work into this phone. It's seriously a completely different device coming from stock!

Great job all around!

Well it looks good on paper lol but one must take into account the further we move away from Android 2.3 the higher the number of incompatible apps in the market. As it stands Android 4.0 only accounts for about 15% of Android devices, that's nearly 10% less then 2.2. I believe Google realized this and that's why it only went up 4.x opposed to hopping to 5.0 and it may just be my imagination but it seems like the only apps updated are corporate, home brewed (from our community) or editors choice and besides I hear porting from ics to jb is a breeze so plz 1 step @ a time lol.
 
  • Like
Reactions: tdm
Well I got the vibrator working, and oh boy did I ever lol.

I flashed a new build on the way home while stuck in traffic and the vibrator started at boot and wouldn't stop. I had to turn the phone off and now I'm reverting to alpha1b.

Hopefully that's an easy fix...
 
Found this commit from 2 days ago from FOP. Commit comment is "camera: add NEON conversion library from gingerbread". Again, not sure if this helps or not. Guessing tdm has already seen this.
 
  • Like
Reactions: tdm
Found this commit from 2 days ago from FOP. Commit comment is "camera: add NEON conversion library from gingerbread". Again, not sure if this helps or not. Guessing tdm has already seen this.

Thanks I'll take a look but the latona camera code does have a neon lib already.. Check the code drop.
 
I

Well it looks good on paper lol but one must take into account the further we move away from Android 2.3 the higher the number of incompatible apps in the market. As it stands Android 4.0 only accounts for about 15% of Android devices, that's nearly 10% less then 2.2. I believe Google realized this and that's why it only went up 4.x opposed to hopping to 5.0 and it may just be my imagination but it seems like the only apps updated are corporate, home brewed (from our community) or editors choice and besides I hear porting from ics to jb is a breeze so plz 1 step @ a time lol.

This is the color conversion function I was looking for all day...

https://github.com/gabwerkz/ics_device_optimus_black/commit/e69174dda5636206d0be49717e68831d4dca5307
 
I hadn't seen gabwerkz code repo, thanks for pointing that out. "Social coding" is difficult for me to do, my first instinct is to hack it up myself.

Judging by his commits, he may have the camera and camcorder fully working. Or at least mostly. So I'm thinking we should have camera, camcorder, and vibrator this week. Yay! :D
 
Hmm, after flashing the LS855 zip plus the vm855 fix, I see "Sprint" on the lock screen and the notification drop down. I guess that must be controlled by eri.xml. which is in framework.jar.

So we have:

framework.jar at 3.9mb for one line of different text.
Mms.apk at 2.9mb for about 10 lines of different text.
build.prop at 5kb for a few lines of different text.

So we're looking at 6.8mb of unique data per phone, times 3 phones (for now). That is two more than a basic ROM would have, because a basic ROM has one set of unique data, of course.

So for a unified ROM, we can expect the size to increase by about 13.6mb or about 13%. That's a whole lot more than I was expecting.

And it will be somewhat worse on the thunderc family because they all have slightly different proprietary files for the RIL.

But wait, I remember that edify has built in support for bsdiff formatted binary patches, which I think is very similar to rdiff. So I'll need to look into that, especially for the sniper family.
 
bsdiff between LS855's framework.jar and VM855's framework.jar is 143 bytes.
bsdiff between LS855's Mms.apk and VM855's Mms.apk is 53 kb.

I'll take it! :D
 
Tdm, just thought I would mention mms works sending and receiving on my AS855 Ignite with the sprint Mms.apk from the LS855 build
 
  • Like
Reactions: tdm
Agreed, and on a semi related note my phone has spent time at the 600mhz and 800mhz frequencies. I'd upload a pic if I knew how or where lol.

Doesn't CTMod have a screenshot option built in? Then you could use Tapatalk to upload it after configuring androidforums account to it... then voila you can insert images into your post easily! :D
 
Hmm, after flashing the LS855 zip plus the vm855 fix, I see "Sprint" on the lock screen and the notification drop down. I guess that must be controlled by eri.xml. which is in framework.jar.

So we have:

framework.jar at 3.9mb for one line of different text.
Mms.apk at 2.9mb for about 10 lines of different text.
build.prop at 5kb for a few lines of different text.

So we're looking at 6.8mb of unique data per phone, times 3 phones (for now). That is two more than a basic ROM would have, because a basic ROM has one set of unique data, of course.

So for a unified ROM, we can expect the size to increase by about 13.6mb or about 13%. That's a whole lot more than I was expecting.

And it will be somewhat worse on the thunderc family because they all have slightly different proprietary files for the RIL.

But wait, I remember that edify has built in support for bsdiff formatted binary patches, which I think is very similar to rdiff. So I'll need to look into that, especially for the sniper family.

the lockscreen carrier text should come from the build.prop, did you leave any lines in it that say sprint?

also framework.jar doesn't have eri.xml, framework-res.apk does. jar's just have smali code.
 
  • Like
Reactions: tdm
Back
Top Bottom