Wellcome to MISSION HWA
Why am I affected by?
Because you what CM9 and MIUI running on your phone.
But fast, smooth and with all functions or am I wrong?
About:
Wildfire S, Aria, Legend.. and more (you tell me) We all got the ports working on
your device. But without HWA it is unuseable. We are brothers and sisters, because our phones are similar.
CPU 600 MHz ARM 11
GPU Adreno 200
Why a mission?
You all are her because ONE PROBLEM needs to be solved.
Most things are fixed like WIFI/GPS/Network and so on.
Everyone love Android ICS but only a few run it because
its laggy, slow and not made for the daily use because of this bug.
And because I wanted a cool name^^
Most of the devices are running the CM7 Drowningchild Kernel.
We need to fix HWA. It enable a lot of apps for ICS and 3D but also the speed and smoothness.!
Working together is much successful than working alone.
Working harmonously together is much more enjoyable
And NOW START WORKING!
WE JUST NEED ONE WORKING KERNEL!! So we can port it and porting
a kernel isn't that hard.
GO TO THE THREAD
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
matt5eo said:
WE JUST NEED ONE WORKING KERNEL!! So we can port it and porting
a kernel isn't that hard.
Click to expand...
Click to collapse
Yes, it really is.
matt5eo said:
WE JUST NEED ONE WORKING KERNEL!! So we can port it and porting
a kernel isn't that hard.
Click to expand...
Click to collapse
Drowning can do that !
Only kernel? What about egl... etc?
Here's the precise status:
There's a group of devices based on the msm-7x27 arch that all use the same adreno 200 driver. Their libegls will work for us, once we get a kernel updated to use the right gpu drivers. The problem is, the gpu drivers are all built around a later fork of the msm kernel tree, which is after the clock code was RADICALLY overhauled. This means our board files (arch/arm/mach-msm/board-liberty*) are not compatible with the new kernel trees, and the clock stuff+kgl stuff backporting to a kernel that works for us means integrating the clock changes.
I've been in communication with drowningchild on this, btw. He is not going to contradict what I say here.
'Just' porting the kernel over here means integrating a few THOUSAND lines of code from a different kernel, some of which are conflicting changes with what is in our kernel right now. The alternative (porting our board files to the new kernel) means porting THOUSANDS of lines of code to a kernel that is also partially incompatible, so it means re-writing a good chunk of it.
If you don't believe that I'm credible, here's the article discussing my port of the HTC Hero CDMA to kernel 2.6.35:
http://www.xda-developers.com/android/2-6-35-kernel-successfully-ported-to-hero-cdma/
Let me know if I can help with anything...
(My kernel "skill" isn't very good though )
s0be said:
Here's the precise status:
There's a group of devices based on the msm-7x27 arch that all use the same adreno 200 driver. Their libegls will work for us, once we get a kernel updated to use the right gpu drivers. The problem is, the gpu drivers are all built around a later fork of the msm kernel tree, which is after the clock code was RADICALLY overhauled. This means our board files (arch/arm/mach-msm/board-liberty*) are not compatible with the new kernel trees, and the clock stuff+kgl stuff backporting to a kernel that works for us means integrating the clock changes.
I've been in communication with drowningchild on this, btw. He is not going to contradict what I say here.
'Just' porting the kernel over here means integrating a few THOUSAND lines of code from a different kernel, some of which are conflicting changes with what is in our kernel right now. The alternative (porting our board files to the new kernel) means porting THOUSANDS of lines of code to a kernel that is also partially incompatible, so it means re-writing a good chunk of it.
If you don't believe that I'm credible, here's the article discussing my port of the HTC Hero CDMA to kernel 2.6.35:
http://www.xda-developers.com/android/2-6-35-kernel-successfully-ported-to-hero-cdma/
Click to expand...
Click to collapse
Will it easier if porting a same processor device's kernel to our devices?
if i am not wrong , the sony X8 did have a same processor and it has HWA on ICS Port.
zhuoyang said:
Will it easier if porting a same processor device's kernel to our devices?
if i am not wrong , the sony X8 did have a same processor and it has HWA on ICS Port.
Click to expand...
Click to collapse
It will be easiest from another HTC device, as they'll have a more similar code base. I believe the Wildfire S is the prime candidate. I'm on a Don Quixote-esque approach of grabbing the 3.0.8 msm kernel from code-aurora and am trying to just dump board files in and fix up the fallout. Currently merging the AMSS and SMD stuffs (still a long way from boot testing, in other words).
if a newer htc base is what we need what about the htc pico/explorer, based on 2.6.38?
i find the kernel version very odd for an android device, and the cpu (msm7225A) is labeled a scorpion?
drowningchild said:
if a newer htc base is what we need what about the htc pico/explorer, based on 2.6.38?
i find the kernel version very odd for an android device, and the cpu (msm7225A) is labeled a scorpion?
Click to expand...
Click to collapse
Perhaps? Have a link to a recent tree for it? Ideally it'd be a 2.6.35 tree (not having to battle linux core changes is a huge plus), but 2.6.38 might not be bad. I believe 2.6.38 was the kernel standard for Honeycomb(could be completely off base), so it's likely that the chip was used in a tablet first, so a 2.6.38 kernel base was the standard (again complete smoke).
s0be said:
Perhaps? Have a link to a recent tree for it? Ideally it'd be a 2.6.35 tree (not having to battle linux core changes is a huge plus), but 2.6.38 might not be bad. I believe 2.6.38 was the kernel standard for Honeycomb(could be completely off base), so it's likely that the chip was used in a tablet first, so a 2.6.38 kernel base was the standard (again complete smoke).
Click to expand...
Click to collapse
all the kernels ive seen(tegra mostly) where .36
this is a GB 'mid range' device, odd that they label a new cortex a5 7225 :\
---------- Post added at 02:38 AM ---------- Previous post was at 02:18 AM ----------
bump with link to repo
https://github.com/drowningchild/msm-2.6.38
---------- Post added at 03:15 AM ---------- Previous post was at 02:38 AM ----------
repo uploaded, damn upload is slow
one thing i noticed was NO bcm4329(but 4330) drivers
the newest htc device with 7227 is the chacha(sources merged into my repo)
i guess they replaced the arm11 cpus with newer cortex a5 :\
We got hwa working on cm9 and on my miui v4 port. Now the latest iusses are wifi/gps and yes.. ..the camera. I think we need the driver from kernel 3.0.
About wrong facts.. sorry. I am a rom dev. Not really a kernel dev.
Gesendet von meinem GT-S5830 mit Tapatalk
matt5eo said:
We got hwa working on cm9 and on my miui v4 port. Now the latest iusses are wifi/gps and yes.. ..the camera. I think we need the driver from kernel 3.0.
About wrong facts.. sorry. I am a rom dev. Not really a kernel dev.
Gesendet von meinem GT-S5830 mit Tapatalk
Click to expand...
Click to collapse
:O
(Someone help me pick my jaw up off the floor, please.)
Sent from my HTC Intruder
matt5eo said:
We got hwa working on cm9 and on my miui v4 port. Now the latest iusses are wifi/gps and yes.. ..the camera. I think we need the driver from kernel 3.0.
About wrong facts.. sorry. I am a rom dev. Not really a kernel dev.
Gesendet von meinem GT-S5830 mit Tapatalk
Click to expand...
Click to collapse
Do you have a link to your working kernel tree and egl libraries? I pulled the libs from your MIUI port, and used DC's kernel tree, and am still hitting the same non functioning HWA. I also built a kernel for aria based on Alquez' kernel, with identical results. How have you verified HWA works?
if you see:
Code:
D/libEGL ( 97): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 97): loaded /system/lib/egl/libEGL_adreno200.so
D/libEGL ( 97): loaded /system/lib/egl/libGLESv1_CM_adreno200.so
D/libEGL ( 97): loaded /system/lib/egl/libGLESv2_adreno200.so
W/libEGL ( 97): 0: eglInitialize(0x1) failed (EGL_SUCCESS)
In your logcat, hwa isn't quite working.
BREAKING NEWS: http://www.xda-developers.com/android/qualcomm-releases-adreno-2xx-gpu-binaries-for-ics/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+xda-developers%2FShsH+%28xda-developers%29&utm_content=FaceBook
zhuoyang said:
BREAKING NEWS: http://www.xda-developers.com/andro...rs/ShsH+(xda-developers)&utm_content=FaceBook
Click to expand...
Click to collapse
Wow, that is huge.
Sent from my HTC Intruder
Those binaries are for arm v7 and the aria is arm v6 but maybe some of our devs can get some thing out of it. Fingers crossed
sent from wherever I am
derefas said:
HW working ! With latest driver for adreno from qualcomm
Yupiii!!11
Click to expand...
Click to collapse
eh, maybe working??
Related
All,
Since we are working as a DEV team now I wanted to share a PM I had with another DEV on the board about our Kernel. I hope this can assist some others that have more experience with the Kernel like b_randon
g60madman said:
subpsyke,
I would love to upgrade our kernel for the Motorola Triumph. How did you go about figuring which Code Aurora vanilla kernel to start with? I took over development for CM7 from Whyzor and would be interested in your methodology.
Thanks in advance,
g60
Click to expand...
Click to collapse
subpsyke said:
1. I unpacked the original Huawei source to one directory, and downloaded the CodeAurora kernel to another.
2. I used the release tags as a reference: https://www.codeaurora.org/xwiki/bin/QAEP/froyo_almond
https://www.codeaurora.org/xwiki/bin/QAEP/froyo
https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=tags
3. I reverted the codeaurora repository to tag releases (e.g.: git reset --hard M76XXTSNCJNLYA6010) and compared the result via "diff urN" and meld. I knew I was getting closer when you get a smaller diff in the patch size, and used meld to see if the differences were likely to be Huawei's additions vs. CodeAurora's changes. It was only after going forward and backwards between tags was I sure of the proper baseline.
I performed the same discovery process with the Samsung kernel for my GT-I5500, which used M76XXTSNCJNLYA6040 as a baseline.
Click to expand...
Click to collapse
g60madman said:
Sweet thanks! I will check it out and see what I can do
Click to expand...
Click to collapse
subpsyke said:
No problem
I forgot to mention the last steps:
4. Once you establish the baseline, create a new branch: git checkout -b newbranch
5. Overlay the changes from the vendor to a new commit*:
cp ~/blah/vendorkernel/ . ; git add . ; git commit -m "Initial import of vendor changes".
6. Once you've commited the vendor changes, you can use "git merge origin/froyo_almond" to move from the baseline to a newer revision. The froyo_almond branch is most suitable, as it's locked at 2.6.32, and the development focus seems to be on the msm7k chipset series. You could try updating to the android-msm-2.6.32 kernel, but it has more significant changes that will require adaptations of the board file, and may not be worthwhile, as development focus seems to be on newer chipsets.
7. Inevitably you'll get merge conflicts, as more than likely some vendor commits may interfere with upstream changes. For this, you'll need to use your own discretion in fixing up the code. I use the "git mergetool", with meld configured as my default editor, and manually checked all the conflicts.
Good luck!
*You may also want to fix up permissions etc., if your vendor source comes from a zip tarball. But it's purely cosmetic.
Click to expand...
Click to collapse
g60madman said:
So is almond the best flavor to start with. I have been using MSM/QSD for a while and in when TickerGuy originally created our device files for cm7 he listed in the readme
CAF information:
Branch: froyo_pumpkin
Tag: M7630AABBQMLZA2030
Didn't know if I should start with pumpkin or use almond. Let me know what you think?
Thanks again for the info!
Click to expand...
Click to collapse
subpsyke said:
Hmm... if your phone really has a msm7630 chipset, then yes, you should probably go for the froyo_pumpkin branch. The froyo_almond branch is only for the msm7627 and qsd8650 chipsets.
Click to expand...
Click to collapse
g60madman said:
Well thats the stupid thing, since the beginning we have used always used msm7x30 for our board config, But our stock ROM from Virgin Mobile the config was msm7k in the build.prop. However if you hit the Motorola Dev our pone clearly states Qualcomm MSM8655. I am leaning towards using the almond branch would that be correct?
Click to expand...
Click to collapse
subpsyke said:
According to wikipedia, it's MSM8655.
Look at the table here: https://www.codeaurora.org/xwiki/bin/QAEP/
The froyo_almond supports qsd8650, and froyo_pumpkin supports qsd8650a_st1x. I honestly have no idea what the difference is, but it's within the realm of possibility that your phone's chipset is that odd revision on the pumpkin branch.
If your kernel is using a pumpkin baseline, then you should continue along the same branch.
Click to expand...
Click to collapse
g60madman said:
I will download pumpkin and compare the kernel. I am not sure why TickerGuy started with pumpkin. That maybe what our build is based off of but I am not 100%.
Click to expand...
Click to collapse
subpsyke said:
Ok. When you clone the codeaurora git repository, you'll have all the branches included anyway.
Click to expand...
Click to collapse
....sympathy post...
Sent from my SPH-D700 using xda premium
(The froyo_almond supports qsd8650, and froyo_pumpkin supports qsd8650a_st1x.) Is this the difference between the Photon 4G which has a WiMax radio in it, and the Triumph which does not include a 4G radio? <--- nvm when they came out I had heard they were the same phone except 4G, apparently the Photon is a Tegra 2 device.
Okay so after looking into code Aurora more, as soon as I get my Ubuntu back up I am going to work on a vanilla froyo 2.6.32.9 kernel by using the froyo_pumpkin branch on the tag Karl gave us. Once I do that and have a commit that adds in Motorola changes, I am going to use the gingerbread_rel branch to try to get a 2.6.35 kernel booting on the phone, then use the ics_chocolate_rb7 branch to hopefully get the 3.x kernel.booting. those branches all seem to have the best support for msm7630 chipsets which I believe is the closest to the msm8655 chip only that it is clocked at 800mhz instead of 1ghz. If anyone else can lend any advice or help it would be swell!!
Sent from my Triumph using Tapatalk
b_randon14 said:
Okay so after looking into code Aurora more, as soon as I get my Ubuntu back up I am going to work on a vanilla froyo 2.6.32.9 kernel by using the froyo_pumpkin branch on the tag Karl gave us. Once I do that and have a commit that adds in Motorola changes, I am going to use the gingerbread_rel branch to try to get a 2.6.35 kernel booting on the phone, then use the ics_chocolate_rb7 branch to hopefully get the 3.x kernel.booting. those branches all seem to have the best support for msm7630 chipsets which I believe is the closest to the msm8655 chip only that it is clocked at 800mhz instead of 1ghz. If anyone else can lend any advice or help it would be swell!!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Swell, I love that word. Here is an email I got from TickerGuy on the Kernel a fe months back
g60madman said:
TickerGuy,
I know you have moved on from the MT. Currently I have taken over development for CM7 from Whyzor and had a question for you.
When you designed the original device files you listed in the readme:
Branch: froyo_pumpkin
Tag: M7630AABBQMLZA2030
Is that really our branch from MSM/QSD? I know the phone has the MSM8655 chip. So I'm just trying to figure out why we use msm7x30 for the board configuration and not say msm7k or qsd8k?
Thanks in advance for any help you can offer
Click to expand...
Click to collapse
TickerGuy said:
I think the reason had to do with some of the peripheral chips -- it was a lot of fun getting this phone to work as it has a number of very odd things about it, especially in the GPS area.
Click to expand...
Click to collapse
So I think it's safe to say the route you are taking the right route. Also when building the Kernel do not forget to merge in the Wyzor fixes for the Video as I am using the new Andreno drivers. Just an FYI.
Yeah I will on the cm7 kernel. As of right now I'm gonna try to get a stock froyo kernel booting off code Aurora sources then go ffrom there.
Sent from my Triumph using Tapatalk
I've got my Linux mint 13 up and running so I'm going to try to get my build environment setup to build kernels either tonight or tomorrow and start pulling in source.
By the way, Linux mint 13 is pretty nice distro so far. I like it alot better than Ubuntu!
Sent from my Triumph using Tapatalk
b_randon14 said:
I've got my Linux mint 13 up and running so I'm going to try to get my build environment setup to build kernels either tonight or tomorrow and start pulling in source.
By the way, Linux mint 13 is pretty nice distro so far. I like it alot better than Ubuntu!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Also you don't need to download the pumpkin branch simple download the kernel
git clone git://codeaurora.org/kernel/msm.git
git reset --hard M7630AABBQMLZA2030
The M7630AABBQMLZA2030 is the pumpkin branch and that should take us back to the vanilla kernel
Here is the pastebin link for the warning I was getting from the linker during the build of the code Aurora kernel.
http://pastebin.com/GLMBSz26
You can look at the kernel source on my github. Its the froyo pumpkin kernel repo.
The warnings cone from the gcc linker saying that it's trying to link a non executible section in built-in.o
I'm not sure where to start looking for the issue at. If anyone can lend any insight I would be grateful!
Sent from my Triumph using Tapatalk
I switched to the gcc 4.3.1 toolchain included with the cm7 source and it booted up. Worked just as good as the stock kernel. I'm gonna have to see why the newer toolchains are not compiling it right. I use linaro 4.6 on bKernel froyo which is based off motos source. So I don't see why it wont build this code right. But at least I got one to boot! !!
Sent from my Triumph using Tapatalk
b_randon14 said:
I switched to the gcc 4.3.1 toolchain included with the cm7 source and it booted up. Worked just as good as the stock kernel. I'm gonna have to see why the newer toolchains are not compiling it right. I use linaro 4.6 on bKernel froyo which is based off motos source. So I don't see why it wont build this code right. But at least I got one to boot! !!
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
Good work brother!
Thanks. Now lets try to move on up to 2.6.35. My idea is to make a different patch between 2.6.32.9 and 2.6.35.7 and maybe that will simplify updating it. I'm not sure which gingerbread branch I'm gonna use for the 2.6.35 kernel!
Sent from my Triumph using Tapatalk
I would think the gingerbread branch, and use the M7630AABBQMLZA404025I.xml version. That is where I snagged the keyboard updates.
g60madman said:
I would think the gingerbread branch, and use the M7630AABBQMLZA404025I.xml version.
Click to expand...
Click to collapse
you can use source kernal .35 for device fih-fbo..we are the same drive only need to change touch driver..
Yeah I would use the fih kernels but we has issues with them rebooting on us.
Sent from my Triumph using Tapatalk
b_randon14 said:
Yeah I would use the fih kernels but we has issues with them rebooting on us.
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
yes you need get a logcat and new baseband for this kernal...I have a file to solve the rendom reboot..but I can't help to get you for the baseband...
The kernel shouldn't have nothing to do with the baseband. Which file is it?
Sent from my Triumph using Tapatalk
b_randon14 said:
The kernel shouldn't have nothing to do with the baseband. Which file is it?
Sent from my Triumph using Tapatalk
Click to expand...
Click to collapse
yes I know,I mean in rom library need these file,I will give you file when I go back home
Anyone got any ideas to fix the issues with newer toolchains when building from the code Aurora source?
Sent from my Triumph using Tapatalk 2
Have you tried downloading one of the gingerbread repo's from code Aurora? I am not sure if they have a different version of the tool chain or not?
PROJECT: Backport essential OMAP drivers from OMAPZOOM 3.0.y Kernel into our 2.6.35 Source
Firstly, I would like to thank dhiru1602 for his CM9/CM10 builds in which he fixed up a lot of bugs single-handedly.
Also, thanks to rocker529 who helped me in this Project.
Me, and rocker529 have been working on this project for the last few weeks, and we have made some progress.
Since backporting Kernel 3.0 wasn't possible on our GT-i9003, I contacted dhiru1602 regarding what could be done in order to have a fully working CM9/CM10 port. Since, the OMAPZOOM Kernels would refuse to boot and no news about the LG Optimus Black Kernel Sources I decided to work on this.
According to my study/research and after a talk with dhiru.
The following would be needed to fix up all Video decoding/recording , camera, lag, HW Composer issues with our present CM9/CM10 builds.
We need-
Implementation of ION Memory Allocator.
What is ION?
ION is a generalized memory manager that Google introduced in the Android 4.0 ICS (Ice Cream Sandwich) release to address the issue of fragmented memory management interfaces across different Android devices. There are at least three, probably more, PMEM-like interfaces. On Android devices using NVIDIA Tegra, there is "NVMAP"; on Android devices using TI OMAP, there is "CMEM"; and on Android devices using Qualcomm MSM, there is "PMEM" . All three SoC vendors are in the process of switching to ION.
You can read more documentation here: http://lwn.net/Articles/480055/
Our progress:
We managed to backport all the ION drivers including our OMAP Specific ION Allocator driver. Fixed up all the errors. It will compile, even managed to get it to boot. However, the required sysfs enteries seem to be missing at /dev/ion . All that I get is some enteries in /debug/ion .
This could possibly be due to improper changes made to our board-latona. We need to initialize ion properly when our board initializes(omap_ion_init() and omap_register_ion() ) which I have failed to do due to no possibility of getting logs on splash screen when the Kernel is loaded.This port also required to new memblock drivers from Linux 3.0 which I have backported.
You can take a look at the changes at my github, please point out if I have missed out anything
Implementation of DSSCOMP-
A: DSSCOMP is needed to make our OMAP HW Composer to work. I have merged all the possible necessary drivers needed for dsscomp. Firstly, dsscomp needs implementation of OMAP ION. Despite of this, we have managed to fix up all the compile errors encountered in our Kernel Source. The driver will compile, but will not boot since ION is not working. Also, it does not go past the boot screen so there are no chances of getting a log.
Again, you can look at my github to see what I have done.
Besides this, we had to backport a LOT of stuff from the OMAPZOOM 3.0 Kernel ! You can take a look at the changes I have made in detail at my github repo..
If I have missed out something, or if I am doing something wrong please help. If we can manage to fix this we could possibly have a stable CM9/CM10 in future.
Please keep this thread [DEV-ONLY] and avoid posting noob questions.
Thanks.
Current progress: Backporting all dependencies for ion and memblock to work.Not sure it would boot though.
Compile from my sources
If you wish to help us I have made a small guide on how to compile your Kernel from my Sources-
Please do not ask me stupid questions like how to copy modules, toolchain error, etc. Proceed only if you have basic knowledge about Linux Kernel Compiling.
Toolchain I use and reccomend: arm-eabi-4.4.3 from CyanogenMod repo. You can find it here.
I would recommend making a github account since it is free and will make it easy for us to track changes, again don't ask me on how to use git, there is plenty of information over the Internet. Take time and search,read etc.
Clone my github repo
Download these boot.img tools.
I will be using directory /home/aditya/i9003 for my reference, you may use any.
Assuming our Kernel is in i9003/Kernel.
Unpack your boot.img tools into tools folder at i9003/tools.
Follow the README in the tools, and unpack CM9/CM10 boot.img.
In the tools/unpack folder make sure you have boot.img-ramdisk.gz (Thats the ramdisk, do not unpack it)
Download this and extract it in i9003/tools folder such that you get i9003/tools/out (This folder will have files needed for CWM zip and compiled modules will go here)
Change your toolchain path in Makefile, add your name to i9003/Kernel/scripts/mkcompile.h if you wish.
Thats done. Your build environment is set up.
Now just,
Code:
cd i9003/Kernel
./build.sh
Sit back and relax, the resulting Kernel will be automatically packed into a flashable zip in i9003/BETA_KERNEL#.zip.
Simply copy to sdcard and flash.
Hoping more people can contribute to development for i9003.
rocker529 said:
Current progress: Backporting all dependencies for ion and memblock to work.Not sure it would boot though.
Click to expand...
Click to collapse
The functions needed for omap_reserve() need to be backported, can you commit your changes? They are not booting as per the ones in the omapzoom 3.0 Kernel.
good luck u guys. have u missed to write "wifi fix" on the topic or,
fix up all Video decoding/recording , camera, lag, HW Composer
Click to expand...
Click to collapse
does it not depend on kernel?
all the best bro with your project and thx you to try it for our phone !:laugh:
i think it is an good idea to make our phone stable before porting kernel 3.x
Good luck in developing, looking forward to this project. :thumbup:
Happy sl user
Sent from my GT-I9003 using xda app-developers app
you should add battery solution cuz battery drain is huge compared by ginger kernel ... the old kernels like amits and vurrut so much better compared to cm kernels
thanks 4 ur effort and waiting 4 ur custom cm10 rom if allah want
Sent from my GT-I9003 using xda app-developers app
Dude like seriously,
I have so much of expectation from u guyzz (Y)
Good Luck !!
Sent from my Galaxy SL using XDA Premium App !!
dorukc said:
good luck u guys. have u missed to write "wifi fix" on the topic or, does it not depend on kernel?
Click to expand...
Click to collapse
From what I know, the wifi module is not compiled from the kernel source and the TI SDK is used to compile it. But ION and DSSCOMP will not help with wifi. For that we will need to seperately debug the wifi drivers (ti_wlan) .
Sent from my GT-I9003 using xda premium
Stuck up at the moment. The backported omap_reserve() functions aren't booting, getting stuck at splash screen. I'll wait, since hillbeast is busy now.. once he is free I will ask him for uart logs.. thinking of posting my kernel(cm10) for testing here , what say people?
Sent from my GT-I9003 using xda premium
^^ Go ahead and post it, but not on this thread. Leave this for development only.
I hope the kernel could be released soon AS possible
Sent from my GT-I9003 using xda app-developers app
Current progress and To-Dos:
The current progress is we are already having the board reserve memory for ion on startup. But since the reserve functions for vram, dsp, ipu and omapfb are not working, we need to backport all the functions and its dependancies from the omapzoom 3.0.y kernel.
To-Dos:
1.Have another brief look at omap_ion_init and omap_ion_register functions.
2.Try to backport the four functions from omapzoom 3.0.y kernel.
3.Have a check at memblock and mm drivers of our current kernel to check for dependancies.
4.If it doesn't boot, get UART logs from hillbeast for debug.
rocker529 said:
Current progress and To-Dos:
The current progress is we are already having the board reserve memory for ion on startup. But since the reserve functions for vram, dsp, ipu and omapfb are not working, we need to backport all the functions and its dependancies from the omapzoom 3.0.y kernel.
To-Dos:
1.Have another brief look at omap_ion_init and omap_ion_register functions.
2.Try to backport the four functions from omapzoom 3.0.y kernel.
3.Have a check at memblock and mm drivers of our current kernel to check for dependancies.
4.If it doesn't boot, get UART logs from hillbeast for debug.
Click to expand...
Click to collapse
Do you want me to edit the Kernel 3.x discussion thread to a backporting project (this) ?
Or simply create another independent one.
I think this topic is very well for questions and information and monitor progress
if there are no spam we get to the good times to follow.
Create a topic and put the other links on the first post when compared with the release obliged for calm languages lamp.
This is the topic of CM10 should have done as the section between dev and overall it is not clear
^^ Wait till Adi_Pat or rocker529 decide to post their test kernel here or maybe give it a unique name and make another thread. Then it would be time to have a q&a or discussion thread. Hopefully this thread wont attract much crowd till there's stuff to download.
Adi_Pat said:
Stuck up at the moment. The backported omap_reserve() functions aren't booting, getting stuck at splash screen. I'll wait, since hillbeast is busy now.. once he is free I will ask him for uart logs.. thinking of posting my kernel(cm10) for testing here , what say people?
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
it will be another kernel or the kernel with omap drivers frim linux 3.0 into your 2.6?
Skander1998 said:
Do you want me to edit the Kernel 3.x discussion thread to a backporting project (this) ?
Or simply create another independent one.
Click to expand...
Click to collapse
No need editing it, as the 3.0.y kernel work is mainly done by hillbeast, and our's is just a backport of parts of the 3.0 kernel to the current 2.6.35.7 kernel, which is separate and non related.
Mamica said:
it will be another kernel or the kernel with omap drivers frim linux 3.0 into your 2.6?
Click to expand...
Click to collapse
Just the old 2.6.35.7 kernel, with DSSCOMP, ION and other dependancies backported from omapzoom 3.0 kernel.
ooikaisheng529 said:
No need editing it, as the 3.0.y kernel work is mainly done by hillbeast, and our's is just a backport of parts of the 3.0 kernel to the current 2.6.35.7 kernel, which is separate and non related.
Just the old 2.6.35.7 kernel, with DSSCOMP, ION and other dependancies backported from omapzoom 3.0 kernel.
Click to expand...
Click to collapse
with this kernel the rom might works much better than with an old kernel?
Kernel created for ViperS JB.
Currently based on my Overclocked kernel v.1.5.2 for HTC Sensation, with fully implemented ION and updated drivers:
-battery,
-audio,
-headset,
-USB,
-WiFi,
-frame buffer,
-video decoding and encoding,
-genlock.
Features:
Compatible with HTC JB.
Overclocked CPU, added optimized CPU frequency tables with CPU frequencies up to 1836 MHz (1512 MHz by default) and L2 cache frequencies up to 1566 MHz.
Increased CPU voltage limits (700 mV - 1400 mV).
Added CPU Voltage Table interface that allows voltage adjustment.
Fixed CPUFreq.
Overclocked GPU, increased maximum GPU frequency in 3D mode from 267 MHz to 320 MHz (300 MHz by default), increased bus bandwidth.
Camera flash: low battery limit decreased to 10%.
Added USB OTG.
Enabled USB Host.
Added support for different types of USB peripherals: USB Hub, USB mass storage devices (e. g. USB HDD, USB Stick, MP3 player), USB HID devices (e. g. USB mouse, USB keyboard, Wireless mouse or keyboard with USB receiver).
Issues:
Camera doesn't work.
Source code:
GitHub
Donations:
Tomasz Paś x2
guidogsbn
Karl Potts
monosoul
Matteo Olive
Jelmertjuhh
Raven2k
Jaglicic
Thank you very much!
thanks for your grat work .bluetooth not work perfectly.whene change visibly time .
Great work mate!
How are you going about getting the camera working? Nikez is working on creating a v4l2 driver from our existing s5k3h1gx driver and Bruce is trying to port the msm8960 camera binary. If you need any help, your best bet would be to ask them
Kind Regards
Dave
Re: [KERNEL] PyramidION v.0.1.2
Hmm go na try this soon.
Thanks.
Sent from my HTC Sensation using xda app-developers app
Re: [KERNEL] PyramidION v.0.1.2
Thanks for your hard work, you gave our phones new life!
Sent from my HTC Sensation Z710e using Tapatalk 2
topgeardave said:
Great work mate!
How are you going about getting the camera working? Nikez is working on creating a v4l2 driver from our existing s5k3h1gx driver and Bruce is trying to port the msm8960 camera binary. If you need any help, your best bet would be to ask them
Kind Regards
Dave
Click to expand...
Click to collapse
Kernel camera drivers and whole interface is a little complex. Also I think I'll have to port HTC Ville C2 JB kernel first.
SebastianFM said:
Kernel camera drivers and whole interface is a little complex. Also I think I'll have to port HTC Ville C2 JB kernel first.
Click to expand...
Click to collapse
Thanks so much for posting your source man i am interested to get involved in this project once source is up ill dig up my sensation and build up a copy to see what i can do about camera
SebastianFM said:
Kernel camera drivers and whole interface is a little complex. Also I think I'll have to port HTC Ville C2 JB kernel first.
Click to expand...
Click to collapse
I've had a look at the source of the Ville C2 kernel and that would take up a considerable amount of time to port. I've tried to get it to initialise with a dodgy defconfig from the sensation but it didn't seem to work. You may want to look at the current k3.4.x thread and see how the guys there are doing. The last thing I remember was that Banb from team darksense got stuck on porting the camera so you may want to ask him for his sources.
And best of luck with it pal! If anyone can get it ported, it would be you
Kind Regards
Dave
topgeardave said:
I've had a look at the source of the Ville C2 kernel and that would take up a considerable amount of time to port. I've tried to get it to initialise with a dodgy defconfig from the sensation but it didn't seem to work. You may want to look at the current k3.4.x thread and see how the guys there are doing. The last thing I remember was that Banb from team darksense got stuck on porting the camera so you may want to ask him for his sources.
And best of luck with it pal! If anyone can get it ported, it would be you
Kind Regards
Dave
Click to expand...
Click to collapse
For testing purposes I already ported HTC Ville C2 ICS kernel into Sensation few months ago.
Re: [KERNEL] PyramidION v.0.1.2
This is great but will it blend?
Sent from my HTC Sensation 4G using Tapatalk 2
Re: [KERNEL] PyramidION v.0.1.2
Is this kernel updated one or the same ?
And does it supports swap and s2w
Sent from my HTC Sensation Z710e using Tapatalk 2
Lost data off my PC hdd but am re installing Ubuntu now so ganna dig through the sources and get my hands on the VilleC2 Kernel and see what i can do about camera initialization see if i cant at least get camera to start thanks again Sabastian your skills brings a new lease of life to our phones
SebastianFM said:
For testing purposes I already ported HTC Ville C2 ICS kernel into Sensation few months ago.
Click to expand...
Click to collapse
Nice! Hypothetically speaking; porting the JB kernel should be a doddle for you
Regards
Dave
topgeardave said:
Nice! Hypothetically speaking; porting the JB kernel should be a doddle for you
Regards
Dave
Click to expand...
Click to collapse
lol not a doodle mate. The new intergrated ION makes it harder ION was not in ICS kernels so ICS kernels are much easyer to port
leeboycott said:
lol not a doodle mate. The new intergrated ION makes it harder ION was not in ICS kernels so ICS kernels are much easyer to port
Click to expand...
Click to collapse
I know mate, I was being sarcastic lol. The ICS kernel contained pmem memory allocation whereas now it has ION. Since we also don't have a base kernel to work from, most of it is pretty much from scratch. That's why I stated earlier that it would take some time to port it.
Regards
Dave
Re: [KERNEL] PyramidION v.0.1.2
This might be a dumb question but how do I download this?
"I wanna be the apex of predators in my backyard"
Joe Rogan
AW: [KERNEL] PyramidION v.0.1.2
1. I think he wouldnt make the kernel itself to download (zImage)
2. If you want source you must wait for link
leeboycott said:
lol not a doodle mate. The new intergrated ION makes it harder ION was not in ICS kernels so ICS kernels are much easyer to port
Click to expand...
Click to collapse
Ville C2 ICS kernel uses ION.
BanB said:
1. I think he wouldnt make the kernel itself to download (zImage)
2. If you want source you must wait for link
Click to expand...
Click to collapse
New zImage will be delivered with ViperS update.
Source code is already available.
Re: [KERNEL] PyramidION v.0.1.2
SebastianFM said:
New zImage will be delivered with ViperS update.
Source code is already available.
Click to expand...
Click to collapse
When do you expect that to be?
Sent from my HTC Sensation 4G using xda app-developers app
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