Jump to content

[KERNEL] [Y300/G510] Stock Huawei


Guest

Recommended Posts

I recommend to use the gcc-4.9.1 build version since the 3D performance seems better. At least in benchmarks tongue.png  --> 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 wub.png (that's some kind of feedback for me too, even if you don't write anything)

Edited by Guest
Link to comment
Share on other sites

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 smile.png

Edited by Guest
Link to comment
Share on other sites

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 smile.png

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

so that i revert to gcc 4.9.1

Edited by squal
Link to comment
Share on other sites

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 by squal
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 by fonz93
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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 by fonz93
Link to comment
Share on other sites

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

Link to comment
Share on other sites

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 by Guest
Link to comment
Share on other sites

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

 

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

 

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 by Guest
Link to comment
Share on other sites

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" wub.png

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.