[KERNEL] [Y300/G510] Stock Huawei

[Guest]

I recommend to use the gcc-4.9.1 build version since the 3D performance seems better. At least in benchmarks   --> http://www.modaco.com/topic/372447-kernel-y300g510-stock-huawei/page-22#entry2215387

 

...not to forget that the UI seems smoother as well...

 

 

More likes (green upper arrow) on the 1st page please if you are satisfied with this kernel -- > http://www.modaco.com/topic/372447-kernel-y300g510-stock-huawei/#entry2210677 (that's some kind of feedback for me too, even if you don't write anything)

Edited June 16, 2014 by Guest

[Guest Picvajzmen]

Man, you dont need no feedback, your the king, i cant beleve how good this kernel of yours is!

[Guest jor1196]

http://www1.zippyshare.com/v/77559056/file.html

 

has all the latest updates (https://github.com/m...i/README.kernel) 

including new (in Place ROW scheduler - update kernel's drivers FM-Radio (DONE))???????

[Guest jor1196]

Now with the experimental kernel I have lag on Asphalt 8

[Guest]

GPU OCed Edition *325 Mhz*

 

 

DOWNLOAD: http://www69.zippyshare.com/v/15791347/file.html ---[ update ] ---> http://www.modaco.com/topic/372447-kernel-y300g510-stock-huawei/#entry2215535

 

 

This kernel should run just like the previous experimental versions. Hopefully those issues reported by jor1196 are gone again. Additionally to the increased GPU clock, I also lowered the transition latency multiplier of OnDemand.

 

NOTE: Future versions will NOT include overclocking. I need to keep track on how every change affects the device. Overclocking is an disturbing factor which makes it harder to debug and stress-test upcoming changes.

 

Have fun

Edited June 17, 2014 by Guest

[Guest]

Don't get me wrong. In my opinion overclocking doesn't really help much at al due of our weak CPU.

[Guest squal]

GPU OCed Edition *325 Mhz*

DOWNLOAD: http://www69.zippyshare.com/v/15791347/file.html

This kernel should run just like the previous experimental versions. Hopefully those issues reported by jor1196 are gone again. Additionally to the increased GPU clock, I also lowered the transition latency multiplier of OnDemand.

NOTE: Future versions will NOT include overclocking. I need to keep track on how every change affects the device. Overclocking is an disturbing factor which makes it harder to debug and stress-test upcoming changes.

Have fun

i got reboot twice..even i do nothing on my phone.,.

so that i revert to gcc 4.9.1

Edited June 17, 2014 by squal

[Guest]

Did you download the version before my EDIT maybe?

[Guest squal]

i download only the gpu oced edition ....

[Guest]

I edited the GPU OC post and changed the download link. So my question still is: did you download the version BEFORE the edit @ 04.13 AM?

[Guest squal]

nope..bcoz the only i download is the latest gcc 4.9.1(fm radio updated)..before the gpu oced edition(325mhz)....

sorry for bothering you...

Edited June 17, 2014 by squal

[Guest spanitzer]

Hey moddingg

Es ist wunderbar was du hier für Arbeit leistest, aber geht beim Thema OC noch ein bisschen? Du willst zwar nicht mehr übertakten aber unser Handy kann das gebrauchen. Kannst du bitte die Android 4.2 Grafiktreiber in den Kernel integrieren? Ich denke mal das Huawei die von 4.0 oder 4.1 verwendet hat.

[Guest luca020400]

Can you translate to english ??

Thanks

[Guest spanitzer]

Can you translate to english ??

Thanks

i can only translate with Google. [emoji20]

[Guest spanitzer]

Hey moddingg

It's wonderful what you are doing here for work, but goes with the OC topic a bit? Although you do not want more but overclock our phone can use it. Can you please the Android 4.2 video drivers into the kernel integrate? I guess that Huawei has used of 4.0 or 4.1.

[Guest fonz93]

With your last versions (12-06 and up, i don't know if previous too), i can't change minfree values with an init.d script, not even with performance control, i can do it only with root explorer

Edited June 17, 2014 by fonz93

[Guest]

There are 2 tuneables. "min_free_kbytes" and "extra_free_kbytes". The kernel uses the sum of both for it's calculations.

[Guest fonz93]

I want to modify this minfree: /sys/module/lowmemorykiller/parameters/minfree

[Guest]

I didn't touch anything related to this value. There is no change I could have done which would explain to me why it shouldn't work, when I did work before, too.

[Guest fonz93]

I didn't touch anything related to this value. There is no change I could have done which would explain to me why it shouldn't work, when I did work before, too.

 

I don't know, i tried both CeXtel and H3ROS kernel and with those kernel i can change minfree values with a simple script, with your kernel i can, but only manually with a root explorer, i also tried to add the script in the synopsis.sh modifying the ramdisk and still doesn't work

Edited June 17, 2014 by fonz93

[Guest]

Do you want to increase or decrease this value?

Try to delete the line with "min_free_kbytes" in it on the file: init.synopsis.RC

[Guest fonz93]

Do you want to increase or decrease this value?

Try to delete the line with "min_free_kbytes" in it on the file: init.synopsis.RC

 

Increase

 

I'll try it when i am at home

[Guest]

GPU *325 Mhz* (-update-)

 

DOWNLOAD: http://www27.zippyshare.com/v/81444706/file.html

 

DOWNLOAD (without GPU OC): http://www70.zippyshare.com/v/12370281/file.html

 

Just some small performance related adjustments and some minor reverts, nothing special.

 

Except that I made an really really experimental version where I increased the kernels internal timer rate from it's default of 100 to 1000 (changed to 200 Hz). This works good on desktops. But I can't guarantee how and embedded mobile SoC behaves with that change. I also upgraded my compiler to the most recent version available.

 

In both versions the GPU is running @ 325 Mhz.

 

Kernel (200 Hz Timer Rate - very experimental -): http://www38.zippyshare.com/v/48105308/file.html

 

 

EDIT: Just to clear up some possible confusions in advance: the kernels timer rate does NOT affect any hardware clocks. It neither overclocks GPU/CPU nor any other buses. It only affects how fast the kernel core's clock is running which a lot of kernel modules relay on. Of course this can have an impact on how the hardware performs, since drivers are using timers as well.

 

EDIT2: *updated* the 100 Hz version and implemented an optimized memcopy/memmove routine.

Edited June 20, 2014 by Guest

[Guest]

Personally I'm testing the 1000Hz version currently of course .

 

But from my 1st impression it seems the increased timer rate does hurt more than actually improve anything.

 

EDIT: UI is smooth with the 1000Hz version, but benchmark doesn't seem to like the timer rate increasing.

 

EDIT2: trying with 200 Hz timer rate ... that's on which older samsung devices were running at (look at the previous post for a download link in case you wanna test it on your own).

Edited June 18, 2014 by Guest

[Guest]

I think it doesn't make much difference whether I call this kernel "stock" or "synopsis" as less as some might care if I call the uploaded build "stable / nightly / experimental" or whatever.

 

After the progress made so far it might be an idea to re-label this kernel's topic and officially name it "Synopsis Kernel"