Hy guys! it is possible any porting from samsung galaxy R a tegra 2 device with touchwiz gingerbread and 2.6.36 kernel?
Anyone have the hands on it?
Inviato dal mio LG-P990 usando Tapatalk
Sources?
Sent from my LG-P990 using Tapatalk
Opensource.samsung.com
check mobile phones
select gt-i9103
Galaxy R kernel Sources
Not sure it's what you're looking for but i find GT-I9103_OpenSource.zip on https://opensource.samsung.com/index.jsp
Edit: sorry doesn't see diaramja post
cant we profit from the galaxy R sources? both cellphones have the same cpu ?!
In my mind(i don't know anything of rom kernel etc) i've think that, the galaxy r have a better kernel than optimus 2x, because the 2.6.36 kernel of S.G.R have a better governor enhancement.
It's possible to port it?
Inviato dal mio LG-P990 usando Tapatalk
Best person to ask would probably be armcee, I think I know what the answer will be.
very interested in knowing
Rusty! said:
Best person to ask would probably be armcee, I think I know what the answer will be.
Click to expand...
Click to collapse
Which is... ?????
Cheers
A big, fat no.
Reason for no?
ok but...what a pity..touch wiz is gpu accelerated...it will be fantastic!
-sandro- said:
Reason for no?
Click to expand...
Click to collapse
Just a hunch. It might have the same SoC, but that may be where any similarity ends.
I don't care about touchwiz, just the kernel.
If they released the sources and we already have the LG's, both can be compared to compile a 2.6.36 version for the p990 with all the goodies and EXT4 support.
That would be great but I don't know if that's possible.
(Maybe armcee would say: "Impossibru!" hehehe xD)
Cheers!
The Galaxy R has different wlan chip, different touchscreen driver, different power regulator, etc (basically different everything except the tegra chip itself). Thus, having kernel sources for the Galaxy R doesn't help at all. We already have access to tegra sources for 2.6.36 and 2.6.39 from nvidia ( http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=summary ).
edit: or so I believe (might have some common hardware actually, but still not everything)
tldr: 2x specific drivers and pinout are still missing.
still missing = not released ?
-sandro- said:
still missing = not released ?
Click to expand...
Click to collapse
This is a bit above my level of understanding, so someone with more knowledge in the subject might be able to explain more in detail.
The current 2.6.32 kernel contains most of these drivers source.
However, nvidia _completely_ changed the way drivers for peripherals and cpu control work in the tegra kernel between 2.6.32 and 2.6.36. In the 2.6.32 kernel they had a "simple" middle layer that was closed source (the nvrm_daemon) and the hardware drivers communicated with that. In 2.6.36 this is gone and drivers should be written and work in a "standard" linux way. This means that most drivers have to be rewritten from scratch or at least require severe changes.
This is most likely the reason lg has chosen not to upgrade the kernel.
Fortunately, from a user perspective, it makes little difference whether the phone is running a 2.6.32 kernel or a later one as long as it is stable and all hardware is working. Later kernels obviously contain improvements, but those might not be significant enough for android to justify the effort.
TY ergoen... this is a big deal...
Inviato dal mio LG-P990 usando Tapatalk
What about LG SU880 ?
It has 2.6.36.3 kernel
http://www.lg.com/global/support/opensource/opensource.jsp
Search for SU-880 (It's different from p990 and SU660 but it's a tegra)
Again, RC is the one to ask.
Edit: I did: http://twitter.com/RussUnderhill/status/139137304286593024
Related
Why doesn't the new update from Asus uses the 3.0 kernal? aren't there a lot of enhancements with it?
Sent from my Transformer TF101 using Tapatalk
bobloadmire said:
Why doesn't the new update from Asus uses the 3.0 kernal? aren't there a lot of enhancements with it?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
The 2.6.xx kernels vs the 3.0 kernel........
2.6.39.4 is maybe one ver behind 3.0 i think
Besides all the features can be back ported to the kernel that we are using
Also we still have to wait for kernel source before we can expect anything exciting
Sent from my Transformer TF101 using xda premium
its also kernel not kernal.
There aren't a lot of differences between 2.6.39 and 3.0. In fact, Linus made the Linux kernel jump to version 3 because it has 20 years now, not because it's a major release.
So I don't think it really needed as 2.6.39 works well so far
The main reason due to Asus uses the old 2.6.39 (yes old, we are at 3.3 now, with a looot of changes) is because nVidia doesn't provide updated sources for Tegra's devices
That's all
Inviato dal mio GT-I9100 usando Tapatalk
I remember reading on Wikipedia Android History that ICS is based on Kernel v3.0 as default, seems not the case with this one then?
It's not another complaint about ICS, I don't care if it is Kernel v1.0, I just need something that works
mcbyte_it said:
I remember reading on Wikipedia Android History that ICS is based on Kernel v3.0 as default, seems not the case with this one then?
It's not another complaint about ICS, I don't care if it is Kernel v1.0, I just need something that works
Click to expand...
Click to collapse
Yeah, original ICS from Google is based on newest kernel 3.0, but as i said nVidia just added ICS support to his old 2.6.39 kernel
has nvidia mentione anything about upgrading to 3.0? it seems tegra 3 does use it.
Sent from my Transformer TF101 using Tapatalk
Just noticed spark is using 3.1 kernel. Interesting
Sent from my WX435 using Tapatalk
Hey guys,
Since im a heavy gamer ( Modern Combat 2/3/4,N.O.V.A 3,NFSMW and some other games ) i decided to take my phone back to stock KQM with root. I previously was on CM10 but the gaming behavior of it is just awful. I didnt managed to play a online round of MC3 to the end. It crashed, or lost Wifi connection every single time.
KQM is way better for gaming. Its almost fluid all the time, but i didnt managed to get it complete fluid. Sometimes there are lags for 10 - 15 seconds, and you know what that means for a FPS Gamer, its horror! And you want to throw your phone against the wall when youre in a 14 kill streak and it lags and you get killed one frag away from a nuke. AHHH. (Still better than CM10 where its around 12FPS all the time).
So im kindly asking someone to build a stock KQM Kernel with the ability for Overclock, and if its possible some shedulers. I think im not the only one who needs this and who would use it all the time.
I would do it myself, but i dont have the hardware for it, my CPU (my pc is from 2006) doesnt support x64 and i cant compile anything on it.
Thank you for your time. :good:
P.S: I know this is dev section, but cmon, who reads the I9000 General?? No one.
AW: [REQ] KQM Kernel with OC @ 1,8 Ghz
Why don't you use skyhigh?
You can't modify the kqm kernel itself. You can only use the provided sources by Samsung.
Sent from my GT-I9100 using xda app-developers app
Hey XellaR*! Samsung just released the source for 2.3.3,
the Kernel from the first stock rom.
We don't have the source for the "new" 2.3.6 Kernel, that's why we cannot update...
greets,
EDIT: Do you know why the Q&A thread isn't sticky anymore?
Hi all,
I will try it but i can't give guarantee
Greets
AW: [REQ] KQM Kernel with OC @ 1,8 Ghz
Thank you guys! I didnt knew lamesung didnt released the 2.3.6 Sources. Thats even more hilarious than the fact they didnt provide us with a4.0.
@Heaven
I dont know, ill ask a mod.
@Markey
Thanks for your efford.
Sent from my GT-I9001 using xda premium
AW: [REQ] KQM Kernel with OC @ 1,8 Ghz
I tryd flashing VitalityKernel, Broodkernel and Skyhigh.
None of the works with KQM. Instand shutdown after power on.
Sent from my GT-I9001 using xda premium
64bit OS is not mandatory. 32bit works as well as long as the toolchain supports it. I wouldn't use a VM on 32bit though.
Regarding the KQM kernel.. I would try to find the OC/UV constants on binary level and patch the kernel directly. One possible way would be to compile two minimalistic kernels with both values (stock <> oc) and compare them. If you get the constants apply them to the KQM binary.
On the other hand... the 3.0 kernel is ready. It should kick any 2.3 kernels ass. Probably not worth the hassle at all...
Edit: You could also try to load the kernel directly into decompilers/disassemblers to find the constants. Maybe that's easier...
Very strange. I experienced gaming problems with ICS but not with JB... Very fluent. I am using slimbean!
AW: [REQ] KQM Kernel with OC @ 1,8 Ghz
DualJoe said:
64bit OS is not mandatory. 32bit works as well as long as the toolchain supports it. I wouldn't use a VM on 32bit though.
Regarding the KQM kernel.. I would try to find the OC/UV constants on binary level and patch the kernel directly. One possible way would be to compile two minimalistic kernels with both values (stock <> oc) and compare them. If you get the constants apply them to the KQM binary.
On the other hand... the 3.0 kernel is ready. It should kick any 2.3 kernels ass. Probably not worth the hassle at all...
Edit: You could also try to load the kernel directly into decompilers/disassemblers to find the constants. Maybe that's easier...
Click to expand...
Click to collapse
Thank you! I will try to set up ubuntu and try to compile some kernels. Lets see ehat i can do for the good old gingerbread.
Sent from my GT-I9001 using xda premium
XeLLaR* said:
P.S: I know this is dev section, but cmon, who reads the I9000 General?? No one.
Click to expand...
Click to collapse
Great, so the rules, obviously do not apply to you.
Next time post in the correct sections or your threads & your ability to post in dev sections will be removed. XDA does not exist for you alone.
Thread Closed.
Boeffla Samsung Kernel by AndiP
Ported and compiled by Hbohd and P$T
For i9305
Introduction
Note: The 4.x kernels are only for Samsung based 4.1.x roms!!! Do not install it on CM or AOSP based roms!!!
The 5.x kernels are only for Samsung based 4.3 roms!!! Also do not install it on CM or AOSP based roms!!!
After ausdim's contribution to porting variety of kernels to our phone, I am here to continue his work (he won't maintain it any longer because he simply doesn't own this phone now). Updates will be made as soon as Andi will push them to github.
Here is original thread of i9300 boeffla kernel - CLICK
Here is thread with boeffla ported by ausdim - CLICK
Info
Kernel is compiled using Linaro 4.9.1 with some required changes for our i9305:
No FM radio
No CMA_DMA
No flash and load in Boeffla App
New 'Hbohd preset' and 'PST preset' which are just our everyday use settings.
New 'Hbohd' and 'PST' equalizer preset - just our favorite.
Apart from that, everything is same as in i9300 version.
Please for any questions problems or anything else ask here and not on I9300 thread.
Credits
P$T (for helping hand with compiling and endless patience and time)
Ausdim (basing on his work and he always gives helping hand)
Yank (his endless patience and knowledge to help with any issue)
AndiP (for kernel base and another kind help)
Disclaimer
*** As always - Flash on our own risk! ***
Make sure you flash the correct version depending on your firmware version!
I can and will not take any responsibility for bricked phones or lost data.
It is generally recommended to run a complete Nandroid backup in CWM recovery and safely store your personal data before you flash a new kernel.
Source:
Here it is, github link! - CLICK
5.2 STABLE compiled with linaro 4.8.3 toolchain -->HERE
Newest version 5.3-beta7 compiled with linaro 4.9.1 toolchain (new ramdisk NE4) --> HERE
Camera bug info:
It appears that some people (like me) have problem with camera. In exactly THIS situation: do full wipe, flash sammy rom+boeffla kernel, reboot and launch camera. Effect? Camera closes with "camera failed" popup.
Possible solution:
1. Read this thread and follow steps --> click
2. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, then reboot to recovery and flash my ported kernel
3. Flash Sammy Rom with stock Sammy kernel, run the camera, take a photo, grab file (SlimISP_XX.bin, where XX differs between phones) from /data/cfw/ and backup it where you want. Then if you can always copy it to /data/cfw if your camera doesn't work with my ported kernel. (ATTENTION: Unfortunately this file does not always appear - still don't know why )
Possible explanation, my own research:
I found out that people with ZD and GD will have camera working always. Why? Because these (SlimISP_XX.bin, where XX differs between phones) files are packed within kernel (zImage exactly) and ONLY THESE two are provided by Samsung in their opensource release... Interesting, isn't it? For example, I have GH version, which I may add to zImage manually, however adding more of them breaks the size limit for boot partition, so it's impossible to have all these versions together. However, stock kernel somehow has them, don't know how because zImages aren't extractable.
And just to confirm my theory, I've compiled a kernel with mine version of camera firmware, made full wipe, installed sammy rom+my kernel, rebooted, launched camera and voila - it worked
Thus, we has to live with this bug unless Samsung do something about it or someone else proves me that I'm wrong
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Installed let see how it goes...
Good work
Tank's
Sent from my GT-I9305 using Tapatalk 2
Hbohd said:
I compiled it after adding my own script for zzmoove 0.5 settings, so you all have them in boeffla app. Therefore I need to explain what i changed (it is just for testing purposes, I don't know yet if it is better/worse etc).
I enabled early demand (new feature from 0.5 version):
And also enabled lcdfreq scaling with standard values:
Click to expand...
Click to collapse
Thanks.
Do you have any link or something where we can read about zzmoove governor tunables? I was searching, and searching and nowhere have I found a good explanation of all parameters.
I should probably look into sources you just gave a link for, but I am too tired atm.
Edit:
Oh that wasn't link to sources, but it doesn't matter, there has to be one somewhere in Boeffla thread.
Sent from my GT-I9305 using Tapatalk 2
My 'sources' are only one file - defconfig. The rest is completely same as Andi's sources
And for any explanation of zzmoove configurables - there is some documentation, quite well explained: https://github.com/andip71/boeffla-...48257af1b13/drivers/cpufreq/cpufreq_zzmoove.c
Cheers
Thanks for the port.
Over night I find this one better on battery than the last port. See how it goes with a bit of heavy usage today.
Sent from my GT-I9305 using Tapatalk 2
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
kazoum said:
Hi Hbohd. So, let me see if I get it: this port will no longer be updated, and you are now the good guy that will continue to update Boeffla kernel to our beloved I9305?
Click to expand...
Click to collapse
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Hbohd it will continue the port of the boeffla kernel since i moved to the i9505.
Also i see Andip make some changes to the boeffla sound driver so it will work better.
Thank's
After 1 day with new kernel I can say the battery improve are the best an till now. Great job
Sent from my GT-I9305 using Tapatalk 4 Beta
Nice.. good job man..
Sent from my GT-I9305
Hbohd said:
Yes, you are completely right Ausdim has even mentioned in his thread that he no longer owns our device (i9305) so I decided to ask for his permission to continue his job here !
I am quite in love with usage results of Boeffla kernel, therefore you do not have to worry about frequent updates
Click to expand...
Click to collapse
Well, I'm sad that a developer leaves this phone, but it is awesome to know that Boeffla will continue to be ported to I9305! The best part is the frequent updates Thumbs up!
I'm gonna try your port and will say something later.
beta6
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
dyy said:
I found 2.12beta6 very smooth on my wife's s3 (i9300) - is it possible to have beta6 for our device? (i9305)
Click to expand...
Click to collapse
What if I told you...
Beta7 is better than beta6
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
kazoum said:
What if I told you...
Beta7 is better than beta6
Click to expand...
Click to collapse
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Sincerely, I haven't experienced any random distortions of sound, everything works great. Obviously, if you raise headphone or speaker volume too high, it may be distorted, but it is understandable.
Or did you want to mention the problem with distorted/freezing/stuttering audio on screen-off? That was discussed and it might be caused due to too low screen-off frequency or too high sampling_rate and sampling_rate_sleep_multiplier. If it's the problem, try to change to zzmoove-optimised as it has this values changed a little bit.
About Perseus' screen calibration settings... As for now, introducing such thing would require adding multiple scripts to support variety of configurations for it (in boeffla app), change app to stweaks (which is quite tough task) or wait for new app which will come in some time, made by Andi (and in my opinion, will let us easily configure what we want).
What's more, personally I liked these calibrated colours, however, original colours also seem good to me So nowadays, I do not need it, although I might look at it in my free time and see what can I achieve
dyy said:
Beta7 is with zmoove 0.5 which is unstable at the moment - beta6 with 0.3
Besides beta6 is so great on my wife's phone that I'm afraid of changing anything
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
The fact is, that ausdim released beta4 or 5, I don't remember exactly, and then was my release beta7. And we somehow skipped beta6, you are right! However if I were you, I wouldn't take zzmoove 0.5 as 'unstable'. It introduces a great deal of new configurables that, I suppose will be really beneficiant in the future (when we all will learn what they mean ).
Version 0.5 is ONLY unstable when you are changing governors frequently. Otherwise, it is really efficient and bettery-friendly one (same as 0.3). In addition, it's my beloved governor since its start
Furthermore, new betas always consist of other updates (like Linux kernel upstream to 3.0.82, fixes, optimizations) so it is always worth to use the newest one!
As for now, you may stay with your actual beta version or wait for next update. Andi is testing comparison between zzmoove 0.3 and 0.5 right now, so he haven't pushed any sources, therefore I can't release any new update We are all impatiently waiting for the results i think!
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
inzomnia said:
Anybody experienced a problem when the phone CPU is stuck in the max CPU frequency when the phone is plugged in to the PC using USB connection?
I'm using zzmoove battery profile..
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Have the same problem, no matter the governor i choose.
I try zzmove battery and pegasusq boeffla battery saving
!crazy said:
Thanks for your work.
Do you have any information about problems with distorted sound? It happens randomly here, and someone else reported the same here in this thread.
Have you used Perseus kernel? What do you think about 'Master sequence', that is calibrated colors? I am missing that feature (well, that colors.) a little, so I'm just asking if there is any chance we get it too, or you plan to stay strictly with pure Boeffla source?
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
I had this issue with boeffla but only when i used rxtreme rom, i never have it with ripper rom!
SebastianFM kernel
Info
Kernel 3.4.10 based on HTC Ville C2 kernel.
Features
Compatible with ViperS and Revelation
Smoothness
Performance
Great battery life
Added support for overclocking (maximum CPU frequency 1836 MHz, maximum GPU frequency 320 MHz)
USB OTG without external power connector
Newest ION, ondemand governor, GPU, Android Binder and Android Low Memory Killer drivers from HTC One GE kernel
KSM
Voltage interface
Changelog
1.0.4
Adjusted memory layout to fix camera issues
1.0.3
Fixed crashes while taking photos
Added voltage interface
1.0.2
Fixed issue with random kernel crashes on some devices
Added KSM
Optimized memory layout
Updated ION, ondemand governor, GPU, Android Binder and Android Low Memory Killer drivers from newest HTC One kernel
1.0.1
Enabled swap
Enabled cpufreq stats
Added NTFS support
Download
Newest kernel is always included in Revelation and ViperS updates.
Source code
SebastianFM kernel source code
Compiler: GCC 4.6
Kernel version: 3.4.10
defconfig: SebastianFM
Awesome, Sebastian! Many thanks for all your work on our device
I don't know what we would do without you.
Sent from my HTC Sensation 4G using Tapatalk 2
I dont see s2w in todo list..
Sent from my HTC Sensation using Tapatalk 4 Beta
Seb, This is for your coffee - Confirmation number: 8V5036601K423861T
i'm glad to see you share the 3.4.10 kernel source
what a fantastic work for our sensation
but after i flash vipers there is still reboot
so i think it's kernel related issue
i upload some last_kmsg in ViperS thread
here are these address:
http://forum.xda-developers.com/showpost.php?p=43382584&postcount=2955
http://forum.xda-developers.com/showpost.php?p=43383710&postcount=2965
http://forum.xda-developers.com/showpost.php?p=43385450&postcount=2981
i wish these logs will be helpful with solve reboot issue that someuser suffer from reboot will glad to see new version of these fantastic kernel and JB roms
jazzzzzzz said:
I dont see s2w in todo list..
Sent from my HTC Sensation using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah..... I love this feature!! If this is included in this kernel than it will be ABSOLUTELY PERFECT :good::good::good:
topjohnwu said:
Yeah..... I love this feature!! If this is included in this kernel than it will be ABSOLUTELY PERFECT :good::good::good:
Click to expand...
Click to collapse
jazzzzzzz said:
I dont see s2w in todo list..
Sent from my HTC Sensation using Tapatalk 4 Beta
Click to expand...
Click to collapse
I believe in the Revelation thread Sebastian said he was working on something better.
Sent from my HTC Sensation using xda app-developers app
i feel to your hard work. Thanks SebastianFM.
Should we flash this kernel in revelation to get auto focus back?
Bardzo dziękuję Sebastian!
I beg everyone to actually browse the commits on Sebastian's github. You will plainly see why this was a painstaking process to complete. He starting loading all the commits a few hours ago and completed them in a very timely manner. Each and every commit (31 in total) is well separated and easy to follow.
I know pressure was put on by other "kernel devs", but they had the option of porting this themselves from the start. Only one person (SebastianFM) actually stepped to the plate and made it happen. I would encourage all users of this kernel, and every kernel that will soon be based off of this, to show the utmost gratitude for the efforts put forth here.
GROGG88 said:
Bardzo dziękuję Sebastian!
I beg everyone to actually browse the commits on Sebastian's github. You will plainly see why this was a painstaking process to complete. He starting loading all the commits a few hours ago and completed them in a very timely manner. Each and every commit (31 in total) is well separated and easy to follow.
I know pressure was put on by other "kernel devs", but they had the option of porting this themselves from the start. Only one person (SebastianFM) actually stepped to the plate and made it happen. I would encourage all users of this kernel, and every kernel that will soon be based off of this, to show the utmost gratitude for the efforts put forth here.
Click to expand...
Click to collapse
That goes without saying Sebastian even wrote the camera driver from scratch
android1234567 said:
That goes without saying Sebastian even wrote the camera driver from scratch
Click to expand...
Click to collapse
Wow from scratch
Great job Sebastian!
I was thinking about getting a new phone
But I will keep that for later
Sent from my katana using Tapatalk 2
Thank you fror sharing, and thank you for all of your hard work.
android1234567 said:
That goes without saying Sebastian even wrote the camera driver from scratch
Click to expand...
Click to collapse
And now you can tell me. Do yow think it will be possible to make this awesome kernel working on AOSP?
Wysłane z mojego HTC Sensation za pomocą Tapatalk 4
That`s Pretty amazing to have Real Jelly Bean`s Kernel for our lovely Device " Sensation "....
Such a progress turns our sensation to an updated PHONE with most common and well known features that is included in modern smart phones Nowadays
to have a device with real jelly bean kernel and OTG without power supply connector and that would be great to have sense based MIUI V5 and semi official 4.1 ROM
Though keep going SebastianFM
sorry im newbie, is this only for devs? because i didnt see any link to download this kernel, or maybe this thread is made for people who understand about it?
leo31 said:
sorry im newbie, is this only for devs? because i didnt see any link to download this kernel, or maybe this thread is made for people who understand about it?
Click to expand...
Click to collapse
This thread is for kernel devs who wants to build their kernel based on Sebastian's source.
topjohnwu said:
This thread is for kernel devs who wants to build their kernel based on Sebastian's source.
Click to expand...
Click to collapse
so what can i do here? nothing??? ._. oke i will wait until i understand what can i do with this thread
leo31 said:
so what can i do here? nothing??? ._. oke i will wait until i understand what can i do with this thread
Click to expand...
Click to collapse
If you cant develop than you can do nothing here
Wysłane z mojego HTC Sensation za pomocą Tapatalk 4
Finally after someone pm'd me I looked back into GPU Overclocking.
New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)
Benefits:
Smoother UI
Handle 2d & 3d core GPU intensive applications & games
Currently only 2D core has been overclocked working on 3D core OC
2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz
3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost
2D-core OC only Download: Coming soon...
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work
Download link to source code: http://d-h.st/wbH
3D-CORE OC TESTS Download: Coming soon...
Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)
OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497
thanks for your work
i m just curious
what s the difference with this:
3d: https://github.com/kylon/AndromadusMod-New/commit/bccb6227f629d5dbb6687e0aa851dd86b4fac01a
2d/ increase 3d: https://github.com/kylon/AndromadusMod-New/commit/e623d0449be04081d0418b799fbe3737371dd56c#diff-137 (this is a big commit, sorry)
there is a good performance boost with this, also, now, you can see 8fps on Antutu (openGL 2.0) (6/6.5 before)
tested on cm10.1
What is this.? Kernel patch... Working with our desire S with cm 10.1 instaled and stock kernel that come with Flinny last 24.2 test built?
Sent from my Desire S using Tapatalk 2
kylon said:
thanks for your work
i m just curious
what s the difference with this:
3d: https://github.com/kylon/AndromadusMod-New/commit/bccb6227f629d5dbb6687e0aa851dd86b4fac01a
2d/ increase 3d: https://github.com/kylon/AndromadusMod-New/commit/e623d0449be04081d0418b799fbe3737371dd56c#diff-137 (this is a big commit, sorry)
there is a good performance boost with this, also, now, you can see 8fps on Antutu (openGL 2.0) (6/6.5 before)
tested on cm10.1
Click to expand...
Click to collapse
Hi I'm unable to look at patch no.2 its too big for the laptop to handle but to comment on the first one it takes more than modifying the kernel graphics software layer platform data to overclock the kernel especially if its the 3d core it takes more, the msm7x30/msm8x55 is a very unique soc, im not sure where those values were pulled from but sure doesnt make sense. Afaik no one has yet managed 2d oc nvm 3d oc until now... :s
You can find them in the incredible s dev section
We have the same soc
Sent from my Desire S using Tapatalk 4 Beta
kylon said:
You can find them in the incredible s dev section
We have the same soc
Sent from my Desire S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah basically ive seen it all, all the commits on the devices with this gpu oc only modified the kgsl pdata with random values they want LOL, its false that isnt how it works, the 2d oc i done is 100x easier than 3d oc and look, i modified more than the kgsl pdata just to get the 2d-core running a measly 50mhz boost.
Hi! How can apply this patch?
AFAIK you´re no kernel dev, right? Maybe by reading OP
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Click to expand...
Click to collapse
El Aero said:
Hi! How can apply this patch?
Click to expand...
Click to collapse
Download the .zip and flash in the recovery.
NVardan said:
Download the .zip and flash in the recovery.
Click to expand...
Click to collapse
Lol
NVardan said:
Download the .zip and flash in the recovery.
Click to expand...
Click to collapse
not sure about this))
Отправлено c моего Desire S
El Aero said:
not sure about this))
Отправлено c моего Desire S
Click to expand...
Click to collapse
teadrinker said:
Lol
Click to expand...
Click to collapse
It didn't work for me too lol.
Sent from my Desire S using Tapatalk 4 Beta
NVardan said:
Download the .zip and flash in the recovery.
Click to expand...
Click to collapse
Nah. There is no zip. Link in the op is for source. So a developer like kaylon have to merge it. OP just posted the source he is trying to compile not made any kernel yet. If I'm reading the OP right.
Wow I'm still a noob
niravnn said:
Nah. There is no zip. Link in the op is for source. So a developer like kaylon have to merge it. OP just posted the source he is trying to compile not made any kernel yet. If I'm reading the OP right.
Wow I'm still a noob
Click to expand...
Click to collapse
Thanks for clarifying! I thought, it should have been flashed as a .zip. My noob level is over 9000.
I hope amidabuddha includes this in his awesome kernel
Sent from my Desire S using xda app-developers app
NVardan said:
Thanks for clarifying! I thought, it should have been flashed as a .zip. My noob level is over 9000.
Click to expand...
Click to collapse
Holy Jesus, just open the .zip you've downloaded...really :laugh:
seems it is not working on my kernel
based on what you said in the dhd dev section i should see 245mhz in /sys/kernel/debug/htc_clock/list_clocks or in /sys/kernel/debug/clk/grp_2d_clk/rate
but they say 192
while i can see 245 in sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0/gpuclk
your files are different, especially kgls_pwrctrl(you are using an old kgsl)
maybe the jb kernel needs some more edits
kylon said:
seems it is not working on my kernel
based on what you said in the dhd dev section i should see 245mhz in /sys/kernel/debug/htc_clock/list_clocks or in /sys/kernel/debug/clk/grp_2d_clk/rate
but they say 192
while i can see 245 in sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0/gpuclk
your files are different, especially kgls_pwrctrl(you are using an old kgsl)
maybe the jb kernel needs some more edits
Click to expand...
Click to collapse
Push your code to github n link me to it n ill have a look at it
I cannot push the code to github
I can give you my files, tonight
EDIT:
the 3d oc is still there, even if it is not a real oc, it gives us a performance boost