Root [ROM] Quattrimus JB (CM10, AOKP41)

[tdm]

@TDM
im on icy fusion(ICS), i was just wondering if you can make a flashable zip of your newest kernel on cm10. or will it even work on ics?

No, the ICS and JB kernels are not compatible, due to display driver updates.

I (or one of the other devs) could backport changes to the ICS kernel and build a new one.

You're probably interested in the changes that fix the crashes?

 

[tdm]

I just upgraded to Beta 6 this morning and my phone did a soft reset (CM logo) while navigating. WIll there still be a kmsg? If so how do I get to it to upload it for TDM?

If the phone didn't hard reset all the way back to the LG logo, it didn't actually reboot. The logs I would be interested in are the running kernel log (eg. output of "dmesg" command) and logcat (eg. output of "logcat -d" command). But if you haven't already captured them, I am guessing the critical entries are long since gone.

 

[tdm]

I'll check the eri. Did this happen in beta4?

Indeed, eri.xml is not correct in AOKP41b6. It is correct in CM10b6. Investigating...

Note: if you unzip framework-res.apk and look at res/xml/eri.xml, the correct size is 4436 and the correct md5sum is e35611b433d6f37b638ad42893ac8667.

 

[blueracer90]

If the phone didn't hard reset all the way back to the LG logo, it didn't actually reboot. The logs I would be interested in are the running kernel log (eg. output of "dmesg" command) and logcat (eg. output of "logcat -d" command). But if you haven't already captured them, I am guessing the critical entries are long since gone.

So I can pull a log cat after the crash has happened?

 

[tdm]

So I can pull a log cat after the crash has happened?

Yes .. as soon as possible after the crash.

 

[tdm]

Now we're getting somewhere with CM10.1. The CAF version of hardware/qcom/display is being compiled. It seems to require some kernel updates so I'm poking around trying to find those now.

Sigh. Why does qcom always have to update their APIs with each release?

 

[IMUcarmen]

I made some kernel changes to test effects of the performance of /dev/random and entropy availability. Anyone who sees tangible improvements with Seeder, please try this and report your findings.

Changes:
* Use hardware rng istead of software rng for all /dev/random and /dev/urandom operations.
* Short circuit all code paths that add entropy (both kernel and userspace), as they are no longer needed.
* Hard code available entropy to the maximum.
* Apply the ELF patch that uses get_random_int().

To test:

1. Remove all traces of Seeder. I suggest a dirty flash.
2. Test performance.
3. Install the new boot image.
4. Verify the kernel version says -cm-hwrng and entropy_avail is 4096.
4. Test performance.

To install the new boot image, download the appropriate image:
CM10b6
AOKP41b6

Push this to the phone as eg. /data/local/tmp/boot.img, then run this as root:

dd if=/data/local/tmp/boot.img of=/dev/block/mmcblk0p8 bs=4096
Make sure you type that correctly! I suggest copy/paste.

Now reboot the phone and verify the kernel version.

I would like to try this out for you but I'm slightly confused about the last instructions.

"Push this to the phone as eg. /data/local/tmp/boot.img" I'm not sure what you mean by push as eg. I've changed around kernels on GB before and all I ever had to do was move the boot.img to the appropriate folder and thats it. So does this mean to just drop the boot.img in that directory.

then run this as root: dd if=/data/local/tmp/boot.img of=/dev/block/mmcblk0p8 bs=4096 Do I run this in adb on the computer with the phone hooked up? Or is this something don'e on the phone? If you can direct me on these couple things I"ll be glad to test this for you

 

[tdm]

I would like to try this out for you but I'm slightly confused about the last instructions.

"Push this to the phone as eg. /data/local/tmp/boot.img" I'm not sure what you mean by push as eg. I've changed around kernels on GB before and all I ever had to do was move the boot.img to the appropriate folder and thats it. So does this mean to just drop the boot.img in that directory.

then run this as root: dd if=/data/local/tmp/boot.img of=/dev/block/mmcblk0p8 bs=4096 Do I run this in adb on the computer with the phone hooked up? Or is this something don'e on the phone? If you can direct me on these couple things I"ll be glad to test this for you

Grab the appropriate boot image and place it somewhere on your phone. I just used /data/local/tmp/boot.img as an example.

I always use adb so it would look like this for me:

adb shell dd if=/data/local/tmp/boot.img of=/dev/block/mmcblk0p8 bs=4096

Running that command on the phone directly in a terminal is possible if you don't have access to a computer and adb. Just don't type the "adb shell" part. But be very careful when typing...

 

[tdm]

Looks like I've got CM10.1 building. Not sure if it will boot .. I won't be able to try until tomorrow.

There were two key changes in the kernel that will need to be sorted out: they refactored the ION stuff and, of course, the qcom display stuff. Hopefully that's all the necessary changes to get things working.

 

[nathanhaywood]

they refactored the ION stuff and, of course, the qcom display stuff

Oh yeah... that doesn't sound like much

 

[tdm]

And nathanhaywood gets honors for the first reported reboot on beta6 (not a kernel crash, user space called reboot). Either he's got a bad phone, he's a thorough tester, or he's just the most vocal user.

Anyway, I'll be adding some code to try to figure out what's going on in user space.

 

[nathanhaywood]

And nathanhaywood gets honors for the first reported reboot on beta6 (not a kernel crash, user space called reboot). Either he's got a bad phone, he's a thorough tester, or he's just the most vocal user.

Anyway, I'll be adding some code to try to figure out what's going on in user space.

Or it's a bad App. OverDrive Media console has been soft-rebooting on me on and off since B1... at least that's consistently my foreground app when my reboots occur.

Anyone else had this issue (on CM10B6 or anywhere else)? Anyone else even use ODM?

 

[MrB206]

I had the same issue with app-based reboots. I had to dial back my cpu and it resolved the issue. Sucked and was a waste, but it worked.

 

[tdm]

And here's the failure in the qcom display code:


W/Adreno200-GSL( 235): <gsl_ldd_control:225>: ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument
E/qdhwcomposer( 235): ioctl MSMFB_BUFFER_SYNC failed, err=Invalid argument
D/qdoverlay( 235): Set pipe=RGB0 dpy=0;
W/Adreno200-GSL( 235): <gsl_ldd_control:225>: ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument
E/qdhwcomposer( 235): ioctl MSMFB_BUFFER_SYNC failed, err=Invalid argument
E/qdoverlay( 235): Failed to call ioctl MSMFB_OVERLAY_PLAY err=Invalid argument
E/qdoverlay( 235): MdpData failed to play
E/qdoverlay( 235): == Dump MdpData start ==
E/qdoverlay( 235): == Dump OvFD fd=34 path=/dev/graphics/fb0 start/end ==
E/qdoverlay( 235): mOvData msmfb_overlay_data id=2
E/qdoverlay( 235): data msmfb_data offset=0 memid=31 id=0 flags=0x0 priv=0
E/qdoverlay( 235): == Dump MdpData end ==
E/qdhwcomposer( 235): draw: queueBuffer failed for external
E/qdhwcomposer( 235): hwc_set_primary: FBUpdate::draw fail!
E/qdgralloc( 235): fb_post: MSMFB_DISPLAY_COMMIT ioctl failed, err: Invalid argument
E/qdhwcomposer( 235): hwc_set_primary: ctx->mFbDev->post fail!
W/Adreno200-GSL( 235): <gsl_ldd_control:225>: ioctl code 0x40140931 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument
E/qdhwcomposer( 235): ioctl MSMFB_BUFFER_SYNC failed, err=Invalid argument
E/qdoverlay( 235): Failed to call ioctl MSMFB_OVERLAY_PLAY err=Invalid argument
E/qdoverlay( 235): MdpData failed to play
E/qdoverlay( 235): == Dump MdpData start ==
E/qdoverlay( 235): == Dump OvFD fd=34 path=/dev/graphics/fb0 start/end ==
E/qdoverlay( 235): mOvData msmfb_overlay_data id=2
E/qdoverlay( 235): data msmfb_data offset=0 memid=31 id=0 flags=0x0 priv=0
E/qdoverlay( 235): == Dump MdpData end ==

 

[mediumrarestea]

Is there a fix for the CPU clock speed to stop changing? Mine keeps resetting or changing randomly.

 

[IMUcarmen]

Is there a fix for the CPU clock speed to stop changing? Mine keeps resetting or changing randomly.

it clocks down when you plug it in for some reason. This phone has done this since gingerbread on brokenout with the blitzkrieg kernel. I've experienced this on every rom. Once unplugged it goes back to whatever clock speed you have it set at.

 

[nayr14]

Hello,

I've installed the AOPK rom as per the instructions (from stock ICS) and it's terrific!

The issue I'm having now is that when I call someone (or they call me) they say my voice sounds very echoed and I'm hard to hear. It's happened with anyone I've talked to now. I think this must be related to the rom. Any ideas?

Edit: I've confirmed this by leaving a voicemail and it sounds bad. If I start up skype and use the echo service, my voice sounds fine.

Thanks

 

[death2all110]

it clocks down when you plug it in for some reason. This phone has done this since gingerbread on brokenout with the blitzkrieg kernel. I've experienced this on every rom. Once unplugged it goes back to whatever clock speed you have it set at.

It clocks itself down so it doesn't get too hot while charging.

 

[Dcaugust]

nayr,

There was a lib fix posted in an earlier post that solved this problem on earlier versions...it might have been left out in beta6, or it somehow didn't replace when you flashed. I had the same problem, so I grabbed the lib file and replaced the faulty one using es file explorer and everyone said they could hear me clear again.

 

[tdm]

nayr,

There was a lib fix posted in an earlier post that solved this problem on earlier versions...it might have been left out in beta6, or it somehow didn't replace when you flashed. I had the same problem, so I grabbed the lib file and replaced the faulty one using es file explorer and everyone said they could hear me clear again.

What exact Rom are you running that has the bad file?

 

[nayr14]

What exact Rom are you running that has the bad file?

I'm running AOKP41B6.

I replaced the libaudcal.so from the link earler (stock ICS) and there is no echo. The quality seems low though. Better than an echo I guess. Hopefully some more progress can be made with this!

 

[IMUcarmen]

I'm running AOKP41B6.

I replaced the libaudcal.so from the link earler (stock ICS) and there is no echo. The quality seems low though. Better than an echo I guess. Hopefully some more progress can be made with this!

just switch to cm10 b6. Seems a few bugs have popped up in aokp since b5 but cm10 is running better than ever.

 

[Dcaugust]

tdm,
I'm on AOKP41 B6...I had been on cm for all of the earlier versions but I wanted to try out AOKP. I like the extra customization...especially center clock.ha. Thanks again for all of the hard work on these ROMS!

 

[sosaudio1]

T D M,

ONE OF THE HARDEST WORKING DEVS IN THE BUSINESS...I think its time to raise a collective toast to you. Thanks!

TO TDM.....

 

[IMUcarmen]

tdm,
I'm on AOKP41 B6...I had been on cm for all of the earlier versions but I wanted to try out AOKP. I like the extra customization...especially center clock.ha. Thanks again for all of the hard work on these ROMS!

I ran aokp41 from the start but was always experiencing performance issues with it so switched over to CM10 and it runs much smoother for me. At first I missed the extra features of AOKP but over time not as much. I get bored though and switch back and forth but since beta 5 of aokp I get the roaming signal by my signal bars and when I plug my bose desktop speakers into my phone the phone goes into silent mode, and even when I toggle it out of silent mode after a couple minutes it turns itself back on.

I've posted this twice already and my post have been completely ignored by everyone. I'm confused as to how I can be the only one this is happening to. I have neither of these issues with CM10 beta 5 and 6.

So could someone on AOKP beta 6 plug a set of speakers into their phone and see if it goes into silent mode please.

And could someone please give me some input on why my phone keeps showing as roaming (though it's actually not, data works fine) and how I might fix it since it seems I'm the only one this is happening to.