Jump to content

[KERNEL][Omegamoon][B926+][ICS]Overclock to max 1.3GHz (Updated 2012/08/24)


Guest omegamoon

Recommended Posts

Guest omegamoon

I've uploaded the new kernel here. Please give it a try. I started to clean up the kernel code, and as soon as this is done I will put more sources into my githup repository. I made quite a mess to get this fixed to be honest, most of it completely unnecessary :wacko: All credits go to genokolar for this camera flash fix. Just great that he was willing to share that on such a short notice!

Link to comment
Share on other sites

Guest samjam

Nice one! Works for me.

Infusion kernel, gene's and this kernel all crash the zxing scanner about half the time and Amazon scanner all the time. Other camera apps are fine although the infusion panorama view finder is often stuck on a solid colour till I start the photo.

Possibly it is not a kernel fault but with infusion.

Link to comment
Share on other sites

The camera is still broke for me with this update, stock gives a can't connect error and camera zoom just freezes when you start it and then does nothing until it closes. Using geno kernel the camera works fine. Anyone else get this? I'm using Infusion 934.

Logs attached.

post-923750-0-21647300-1345391694_thumb.

logcat.txt

Edited by Cyda
Link to comment
Share on other sites

Guest tillaz

Nice one! Works for me.

Infusion kernel, gene's and this kernel all crash the zxing scanner about half the time and Amazon scanner all the time. Other camera apps are fine although the infusion panorama view finder is often stuck on a solid colour till I start the photo.

Possibly it is not a kernel fault but with infusion.

could you get me a logcat of the crash, when using infusion

Link to comment
Share on other sites

Guest wso277

The camera is still broke for me with this update, stock gives a can't connect error and camera zoom just freezes when you start it and then does nothing until it closes. Using geno kernel the camera works fine. Anyone else get this? I'm using Infusion 934.

Logs attached.

post-923750-0-21647300-1345391694_thumb.

I got an error like that with geno kernel. Try this:

unistall camera zoom

reboot

try camera and see if it works.

Link to comment
Share on other sites

Guest omegamoon

The camera is still broke for me with this update, stock gives a can't connect error and camera zoom just freezes when you start it and then does nothing until it closes. Using geno kernel the camera works fine. Anyone else get this? I'm using Infusion 934.

Logs attached.

post-923750-0-21647300-1345391694_thumb.

Strange... could it be that Huawei produced the G300 with different camera sensors after all then?

Please reboot and make a dump of the device startup using "dmesg". This can be done as follows:


adb shell

cd /sdcard

dmesg > dmesg_startup.log

Now copy the "dmesg_startup.log" from the sdcard and post it here. After that, setup a "live log" from the kernel as follows:

adb shell

su

cat /proc/kmsg

Now start the camera app and make it crash. Then post the last part of the log here as well

This probably can be done more easily maybe, but this is how I debug these kind of issues :)

Link to comment
Share on other sites

Strange... could it be that Huawei produced the G300 with different camera sensors after all then?

Please reboot and make a dump of the device startup using "dmesg". This can be done as follows:

Now start the camera app and make it crash. Then post the last part of the log here as well

This probably can be done more easily maybe, but this is how I debug these kind of issues :)

Tried both stock cam app and camera zoom and both seem to fall down with the following error...


08-19 18:44:27.519 E/CameraService(128): CameraService::connect X (pid 2617) rejected (invalid cameraId 0).

Logs below as requested.

camz.txt

stock.txt

dmesg_startup.log.txt

Link to comment
Share on other sites

Guest omegamoon

Just what I thought...


s5k4e1.c: s5k4e1_sensor_probe: SENSOR PROBE FAILS!

msm_sync_init: failed to initialize s5k4e1

Could you go back to stock kernel and post the "dmesg_startup.log" from there? I'm curious to know what sensor is used in your device!

Link to comment
Share on other sites

Just what I thought...


s5k4e1.c: s5k4e1_sensor_probe: SENSOR PROBE FAILS!

msm_sync_init: failed to initialize s5k4e1

Could you go back to stock kernel and post the "dmesg_startup.log" from there? I'm curious to know what sensor is used in your device!

dmseg_startup.log from stock kernel (3.0.8-perf-00240-g6df6f4c).

dmesg_startup.log.txt

Edited by Cyda
Link to comment
Share on other sites

Guest omegamoon

dmseg_startup.log from stock kernel (3.0.8-perf-00240-g6df6f4c).

Thanks for all the logs. It confirms that the G300 is build with different camera sensors. I figured it was build with the "s5k4e1" camera sensor only, like mine has. But your G300 has the "mt9p017" camera sensor. No wonder genokolar's kernel is working for you because the U8818 model he uses has the same "mt9p017" camera sensor. I have to re-insert support for the "mt9p017". I guess I was a little too thorough with cleaning up the kernel ;) Edited by omegamoon
Link to comment
Share on other sites

Guest samjam

could you get me a logcat of the crash, when using infusion

Hi tillaz

A simplification of Omega's logcat method (thanks for that) which gets the file local to my PC:

http://pastebin.com/tvcZaL6h

adb shell dmesg > /tmp/dmesg_startup.log
http://pastebin.com/UcMM59ma (beware this one for pipeline buffering, so I shut the phone down and let it quit itself)
adb shell su -c 'cat /proc/kmsg' > /tmp/kmsg_crash.log
Omega, you will be interested in the startup.log as it uses your kernel but has a kernel backtrace in it:

<4>[1, swapper] [	0.856054] ------------[ cut here ]------------

<4>[1, swapper] [	0.856103] WARNING: at drivers/gpio/gpiolib.c:1261 gpio_free+0x114/0x14c()

<4>[1, swapper] [	0.856129] Modules linked in:

<4>[1, swapper] [	0.856199] [<c004c594>] (unwind_backtrace+0x0/0x140) from [<c00cb7c8>] (warn_slowpath_common+0x54/0x6c)

<4>[1, swapper] [	0.856251] [<c00cb7c8>] (warn_slowpath_common+0x54/0x6c) from [<c00cb7f8>] (warn_slowpath_null+0x18/0x1c)

<4>[1, swapper] [	0.856303] [<c00cb7f8>] (warn_slowpath_null+0x18/0x1c) from [<c02639bc>] (gpio_free+0x114/0x14c)

<4>[1, swapper] [	0.856358] [<c02639bc>] (gpio_free+0x114/0x14c) from [<c03c73c0>] (s5k4e1_probe_init_done+0x30/0x50)

<4>[1, swapper] [	0.856408] [<c03c73c0>] (s5k4e1_probe_init_done+0x30/0x50) from [<c03c84f4>] (s5k4e1_sensor_probe+0xe4/0x1b0)

<4>[1, swapper] [	0.856458] [<c03c84f4>] (s5k4e1_sensor_probe+0xe4/0x1b0) from [<c03c376c>] (msm_camera_drv_start+0x1a0/0x698)

<4>[1, swapper] [	0.856509] [<c03c376c>] (msm_camera_drv_start+0x1a0/0x698) from [<c02bd6b8>] (platform_drv_probe+0x18/0x1c)

<4>[1, swapper] [	0.856561] [<c02bd6b8>] (platform_drv_probe+0x18/0x1c) from [<c02bc26c>] (driver_probe_device+0x18c/0x2e4)

<4>[1, swapper] [	0.856609] [<c02bc26c>] (driver_probe_device+0x18c/0x2e4) from [<c02bc424>] (__driver_attach+0x60/0x84)

<4>[1, swapper] [	0.856658] [<c02bc424>] (__driver_attach+0x60/0x84) from [<c02bb84c>] (bus_for_each_dev+0x48/0x84)

<4>[1, swapper] [	0.856704] [<c02bb84c>] (bus_for_each_dev+0x48/0x84) from [<c02bb0cc>] (bus_add_driver+0xd8/0x28c)

<4>[1, swapper] [	0.856751] [<c02bb0cc>] (bus_add_driver+0xd8/0x28c) from [<c02bcb08>] (driver_register+0xac/0x134)

<4>[1, swapper] [	0.856801] [<c02bcb08>] (driver_register+0xac/0x134) from [<c00403f4>] (do_one_initcall+0xa0/0x1b0)

<4>[1, swapper] [	0.856851] [<c00403f4>] (do_one_initcall+0xa0/0x1b0) from [<c00083f8>] (kernel_init+0x90/0x150)

<4>[1, swapper] [	0.856898] [<c00083f8>] (kernel_init+0x90/0x150) from [<c0047544>] (kernel_thread_exit+0x0/0x8)

<4>[1, swapper] [	0.856959] ---[ end trace 00c709be83459f99 ]---

Edited by samjam
Link to comment
Share on other sites

Guest samjam

Also, my phone isn't sleeping (screen always on) with this omega kernel

I take that back - it is now... I'll will see if it occurs again or if there is a pattern

Edited by samjam
Link to comment
Share on other sites

Guest omegamoon

I uploaded a new kernel here (MD5 3c5eb7d4626355b87a2ea325fc59adfa).

* This should fix the camera problems for all of you having the mt9p017 camera sensor.

* I added two more overclock frequencies up until 1.325GHz. I did some tests, and it seems that this is the maximum before the CPU becomes unstable and/or crashes or reboots

Link to comment
Share on other sites

Guest samjam

Looks good here. Camera panorama pre-preview works properly but ZXing barcode scanner and Amazon app barcode scanner both fc as said earlier. I think its nit your kernel fault but would like to know if they work for you

Edited by samjam
Link to comment
Share on other sites

Looks good hear. Camera panorama pre-preview works properly but ZXing barcode scanner and Amazon app barcode scanner both fc as said earlier. I think its nit your kernel fault but would like to know if they work for you

This barcode scanner? Its working fine here with omegamoon kernel.

Edited by Cyda
Link to comment
Share on other sites

Guest bladebuddy

As promised a few beers on me,

Confirmation OD2727395N9600032

Would of donated earlier hadn't PayPal frozen my account, not accepted my online security question as correct, charged me £8 in credit to talk to them in America and get told I was right and they don't no why my account was frozen, quoting " it sometimes happens"

F--k you very much PayPal and to the person who has my wallet.

At least I can overclock my phone.

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.