282 replies to this topic

[Frankish]

This kernel breaks camera for me in infusion. Where is genokolar kernel?

[bladebuddy]

Edit wrong link sorry.<br /><br />

Edited by bladebuddy, 11 September 2012 - 04:04 PM.

[kyan31]

What is the difference between omegamoons kernel and genokolars kernel? Which one should I install?

[Potatoes]

Pretty sure Geno's kernel will be the same since Geno supplied the camera fix

omegamoon, on 11 August 2012 - 10:10 PM, said:

[UPDATE 2012/08/13]
* Bluetooth is fixed now
[UPDATE 2012/08/19]
* Fixed camera flash (thanks to genokolar!)
[UPDATE 2012/08/20]
* Fixed camera issue with mt9p017 sensor (thanks to genokolar!)
* Optimized CPU frequencies + added 2 overclock values
[UPDATE 2012/08/24]
* Added zRam feature
* Added smaller steps in overclock frequencies from 1.2 to 1.3GHz

[Potatoes]

kyan31, on 11 September 2012 - 03:29 PM, said:

What is the difference between omegamoons kernel and genokolars kernel? Which one should I install?

I think nothing, apart from omega's has vr and sio schedulers and the overclocking settings go higher (maybe) but can't be sure, can't find the source for the Geno's kernel

[Cyda]

Frankish, on 11 September 2012 - 01:10 PM, said:

This kernel breaks camera for me in infusion. Where is genokolar kernel?

CWM flashable can be found here: http://www.modaco.co...verclock-13ghz/

[timfimjim]

camera works fine for me with infusion b3

[Frankish]

Potatoes, on 11 September 2012 - 03:35 PM, said:

Pretty sure Geno's kernel will be the same since Geno supplied the camera fix

<br /><br />Then why on a clean install does omega kernel break camera yet genos is working fine for me

Edited by Frankish, 11 September 2012 - 07:17 PM.

[Potatoes]

Frankish, on 11 September 2012 - 07:13 PM, said:

<br /><br />Then why on a clean install does omega kernel break camera yet genos is working fine for me

I don't know for sure, the camera on geno's worked for me as does omega's (at least since the 2012/08/19 update). Tbh I'm just speculating since I don't have access to geno's kernel source.

[bladebuddy]

If you read back a good few posts you will see different cameras have been used on the same phone . ZTE also used different parts.

[Potatoes]

Yeah I think that's probably it bladebuddy, I forgot about that. I did notice when I was compiling mine that the new B936 .config has more sensors enabled than omegas, omega's literally only has MT9P017 whereas the official rom has a whole bunch which I assume accounts for all the variations.

B936

CONFIG_HUAWEI_CAMERA=y
CONFIG_HUAWEI_CAMERA_SENSOR_S5K5CA=y
CONFIG_HUAWEI_CAMERA_SENSOR_MT9T113=y
# CONFIG_MT9T013 is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9D113 is not set
CONFIG_HUAWEI_CAMERA_SENSOR_MT9V113=y
# CONFIG_MT9D112 is not set
# CONFIG_HUAWEI_SENSOR_HI701 is not set
# CONFIG_HUAWEI_SENSOR_OV7690 is not set
# CONFIG_HUAWEI_SENSOR_OV7736 is not set
# CONFIG_HUAWEI_SENSOR_HIMAX0356 is not set
# CONFIG_HUAWEI_SENSOR_MT9D113 is not set
# CONFIG_HUAWEI_SENSOR_MT9V114 is not set
CONFIG_HUAWEI_SENSOR_MT9P017=y

Omegamoon

CONFIG_HUAWEI_CAMERA=y
# CONFIG_HUAWEI_CAMERA_SENSOR_S5K5CA is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9T113 is not set
# CONFIG_MT9T013 is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9D113 is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9V113 is not set
# CONFIG_MT9D112 is not set
# CONFIG_HUAWEI_SENSOR_HI701 is not set
# CONFIG_HUAWEI_SENSOR_OV7690 is not set
# CONFIG_HUAWEI_SENSOR_OV7736 is not set
# CONFIG_HUAWEI_SENSOR_HIMAX0356 is not set
# CONFIG_HUAWEI_SENSOR_MT9D113 is not set
# CONFIG_HUAWEI_SENSOR_MT9V114 is not set
CONFIG_HUAWEI_SENSOR_MT9P017=y

Edited by Potatoes, 11 September 2012 - 08:00 PM.

[omegamoon]

LucabossY, on 29 August 2012 - 10:17 AM, said:

is possible overclock the GPU? thanks

Read this thread over at XDA. Bottom line is that GPU overclocking is impossible but "global overclocking that affects 1GHz CPU clock will affect GPU too"

[omegamoon]

timfimjim, on 31 August 2012 - 08:24 AM, said:

Hi Omegamoon, just getting round to adding some zRAM to my g300 and got a question:

1. On your website you give instructions to add 100kb - isn't that 100mb?

2. I got stuck with the last line - turning the swap on. Screen shot attached. Screenshot_2012-08-31-09-15-03.png

3. For people who add zRAM but don't know if it's working, type 'busybox free' into terminal emulator and it'llshow you the status of the swap on the last line

You're right, the proposed size is too high. I'm looking into this "short write" problem. Don't know why it occurs, it sometimes does. After that I have to reboot to give it another try.

[Dazzozo]

Potatoes, on 11 September 2012 - 08:00 PM, said:

Yeah I think that's probably it bladebuddy, I forgot about that. I did notice when I was compiling mine that the new B936 .config has more sensors enabled than omegas, omega's literally only has MT9P017 whereas the official rom has a whole bunch which I assume accounts for all the variations.

B936

CONFIG_HUAWEI_CAMERA=y
CONFIG_HUAWEI_CAMERA_SENSOR_S5K5CA=y
CONFIG_HUAWEI_CAMERA_SENSOR_MT9T113=y
# CONFIG_MT9T013 is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9D113 is not set
CONFIG_HUAWEI_CAMERA_SENSOR_MT9V113=y
# CONFIG_MT9D112 is not set
# CONFIG_HUAWEI_SENSOR_HI701 is not set
# CONFIG_HUAWEI_SENSOR_OV7690 is not set
# CONFIG_HUAWEI_SENSOR_OV7736 is not set
# CONFIG_HUAWEI_SENSOR_HIMAX0356 is not set
# CONFIG_HUAWEI_SENSOR_MT9D113 is not set
# CONFIG_HUAWEI_SENSOR_MT9V114 is not set
CONFIG_HUAWEI_SENSOR_MT9P017=y

Omegamoon

CONFIG_HUAWEI_CAMERA=y
# CONFIG_HUAWEI_CAMERA_SENSOR_S5K5CA is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9T113 is not set
# CONFIG_MT9T013 is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9D113 is not set
# CONFIG_HUAWEI_CAMERA_SENSOR_MT9V113 is not set
# CONFIG_MT9D112 is not set
# CONFIG_HUAWEI_SENSOR_HI701 is not set
# CONFIG_HUAWEI_SENSOR_OV7690 is not set
# CONFIG_HUAWEI_SENSOR_OV7736 is not set
# CONFIG_HUAWEI_SENSOR_HIMAX0356 is not set
# CONFIG_HUAWEI_SENSOR_MT9D113 is not set
# CONFIG_HUAWEI_SENSOR_MT9V114 is not set
CONFIG_HUAWEI_SENSOR_MT9P017=y

I just made some changes based on these findings to my own kernel configuration, but mine wasn't that too few cameras were enabled, mine was too many.

Huawei provides a standard msm7x27a configuration which they must use for more devices, as the one used on the U8815 is a little different.

[omegamoon]

cazad, on 07 September 2012 - 08:57 PM, said:

Omegamoon kernel - OC 1228Mhz  (performance, sio), Infusion B03 ICS ROM, Chainfire3d - PowerVR plugin, charging
PNY SDHC card, class 10,16GB

a score of 3849 is very high, nice ...

Just gave it a try, using stock B936 ICS. I scored 3810 (see screenshot below). This is at 1.31GHz. Bare in mind though that the score is just a rough indication of system performance, and it's influenced by a lot of things. I did another test just after this one, and the score was 3785.

Attached Files

•  Screenshot_2012-09-11.png   36.49K   15 downloads

Edited by omegamoon, 12 September 2012 - 09:19 AM.

[omegamoon]

Colossae3.23, on 10 September 2012 - 09:44 AM, said:

@omegamoon,
great work, thanks for this. It works great on the newest Infusion build. Like greased lightning now

For me its stable to the highest setting (in the Infusion processor settings) which is 1.325. I imagine No Frills may provide higher values?
Anyway, its probably not the best to keep it at full wack is it? I mean for wear and tear? Just wondering what people's thoughts are on that.
And on the lower side, I find 122 doesn't wake up very nice. Anyone else experience this as well?

All the best,
Bill

Could you try running a AnTuTu benchmark at 1.325? If I do that it reboots at the 3d performance test. I use 122 as min freq and I don't see any problems waking up the device

[omegamoon]

Potatoes, on 10 September 2012 - 10:58 AM, said:

Nice, you're lucky to be able to hit 1.325. It can be compiled to go faster. Omega has put in the values all the way up to 1.5 but they're commented out

// Users report that CPU is stable in between 1.2 and 1.3GHz
{ 1, 1270000,	ACPU_PLL_4,  6,  0, 158750,   3,  7, 200000 },
{ 1, 1280000,	ACPU_PLL_4,  6,  0, 160000,   3,  7, 200000 }, // PLL4 max of 66.7MHz
{ 1, 1290000,	ACPU_PLL_4,  6,  0, 161250,   3,  7, 200000 },
{ 1, 1300000,	ACPU_PLL_4,  6,  0, 162500,   3,  7, 200000 },
// Up to 1.3GHz is stable but... Let's go bananas!!
{ 1, 1310720,	ACPU_PLL_4,  6,  0, 163840,   3,  7, 200000 },
{ 1, 1324800,	ACPU_PLL_4,  6,  0, 165600,   3,  7, 200000 },
/*
{ 1, 1344000,	ACPU_PLL_4,  6,  0, 168000,   3,  7, 200000 },
{ 1, 1382400,	ACPU_PLL_4,  6,  0, 172800,   3,  7, 200000 },
{ 1, 1420800,	ACPU_PLL_4,  6,  0, 177600,   3,  7, 200000 },
{ 1, 1459200,	ACPU_PLL_4,  6,  0, 182400,   3,  7, 200000 },
{ 1, 1497600,	ACPU_PLL_4,  6,  0, 187200,   3,  7, 200000 },
{ 1, 1536000,	ACPU_PLL_4,  6,  0, 192000,   3,  7, 200000 },
*/

I commented the higher frequencies out since the device becomes unstable or doesn't even boot. I could add smaller steps to see what the ultimate stable value is. I'll try that later

[Potatoes]

Those sdcard card scores are nice is that using the VR scheduler? On the subject of that, whenever you next update github can you chuck in the cpu and io schedulers. I've managed to add them myself but for the life of me can't get VR compiling, always bombs out with

  CC	  block/vr-iosched.o
block/vr-iosched.c:417: error: unknown field 'elevator_queue_empty_fn' specified in initializer
block/vr-iosched.c:417: warning: initialization from incompatible pointer type
error, forbidden warning: vr-iosched.c:417
make[1]: *** [block/vr-iosched.o] Error 1
make: *** [block] Error 2

But no rush

[omegamoon]

luismiyu, on 10 September 2012 - 01:21 PM, said:

I have wifi toggle freeze too. I thought it was a B936 related issue and reading some posts here I'm not the only one suffering. Switching to geno.kolar kernel that has never failed... for the time being

During the AnTuTu tests I did yesterday I witnessed the same wifi toggle freeze a few times. Too bad that every time this happened I didn't have the device connected to my pc, so I still don't have a debug log

[omegamoon]

Colossae3.23, on 11 September 2012 - 11:44 AM, said:

cheers, I'm going to try the llama app for that. Staying steady for 24 hours @ 1.3ghz, smartassv2 and vr scheduler. Going back up to 480mhz as minimum. Seems like anything less is slow to wake up.

Slow to wake up? I really don't know what you mean... ah, wait, I just set the minimum to 480Mhz myself, just to see if I see any difference while waking up the device