Related
Welcome to the Eternity Project Kernel for HTC Vision Thread!
The Eternity Project Kernel for HTC Vision (T-Mobile G2 & HTC Desire Z) is developed for gaining the maximum possible speed mantaining the maximum safety on our devices.
Features:
- Updated kernel (2.6.32.17 -> 2.6.35)
Kernel GIT Repository: http://gitorious.org/eternity-prj/eternityvision_2-6-35
Still some errors to correct.... and need help :|
Stay TuneD!
Thanks! Will test.
good stuff. porting the board files/dependancies, etc. is quite a bit of work, so my hats off to you!
will check it out.
thx for your efforts.
wow another?
I'm not 100% sure that I've ported all correctly (excluding some compiler errors that prevents the building ... and that I'm correcting)... so, well, pershoot, knowing your work I'd be proud if you take a look at the code
Anyway, I've corrected some other things, now I'm dealing with some errors on mddi.c ... I hope it'll be ready to test in some hours
Returning at work!
P.S.: It's ----SO---- dirty! I've uploaded it while testing and error checking!
kholk said:
I'm not 100% sure that I've ported all correctly (excluding some compiler errors that prevents the building ... and that I'm correcting)... so, well, pershoot, knowing your work I'd be proud if you take a look at the code
Anyway, I've corrected some other things, now I'm dealing with some errors on mddi.c ... I hope it'll be ready to test in some hours
Returning at work!
P.S.: It's ----SO---- dirty! I've uploaded it while testing and error checking!
Click to expand...
Click to collapse
yup for sure. i've gotten as far as the new QSD SPI bits, and put it down to work on other things... haven't gone back to it yet.
The new QSD SPI bits in the files uploaded are broken (prevents compilation), but locally I've already corrected them.
I've uploaded the files because I've done almost all the work, it needs only another percent of finalization...and I'm not committing every change in the same moment 'cause it would be painful
EDIT: Other things checked and fixed. Changes committed.
EDIT2: I'm stuck at the end. Anyone can help? Thanks!
Has there been any headway on this? I for one think this has a lot of potential.
Sent from my G2
thanks for your work. Is this kernel designed for AOSP or Stock or both? I'd love to have it compatible with Stock Rooted Rom
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
kholk said:
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
Click to expand...
Click to collapse
Ooo, you do what you have to do buddy and take your time! Have a great time with your loved ones and Happy new year to all!
Can I test this kernel on gingerbread/cm7 builds
Sent from my HTC Vision using XDA App
kholk said:
It's designed to work on stock Android, but I haven't had time to continue the work on it.
Unfortunately now I'm not at home and the only thing that keeps me connected is my G2...and anyway I'm on vacation with my girlfriend so you can understand the situation
However.
I'll watch at this when I'll get back home...
Resuming on 10/01
Click to expand...
Click to collapse
That is completely understandable, make sure you enjoy yourself. We can wait a little while in the backseat, but an updated kernel would be awesome . Just know that your efforts are appreciated. Thanks, and have fun!
thatruth132 said:
Can I test this kernel on gingerbread/cm7 builds
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Nandroid, and go for it . At it's current state I would expect a few things to be broken. Actually, gingerbread was designed to work with a .35 kernel so results might be favorable. The absolute worst thing that could happen is a bootloop, and you can fix that by flashing the stock kernel with adb. Let us know how it works.
Sounds cool..... stay safe
Sent from my HTC Nightmare G3
Bump for justice!
Do I need to build this to test on MIUI?
And can I OC to 1GHz with it? Or will I need to build one?
Or get someone else to build it
Please stay ON TOPIC to kernel DEV and missing code. Don't report every bug the Android build your using is having or it will be deleted as OFF TOPIC
As you all might be knowing that hd2 is pretty much a android native device now. Its just like any another snapdragon device. The current kernel code we are using in HD2 is pretty obsolete and missing a lot of things. It more like something working at its minimal efficiency. While i was porting over all the HD2 board files getting it on par with the other snapdragon devices I found out a lot of code was missing and some was obsolete. Eg. The gsensor code from microp was pretty minimal, a lot of things were missing in microp code. I suspect that it isnt the only code, a lot of bluetooth related stuff was missing and much more. I am not really gonna work on backporting the stuff to .32 kernel so i would like the kernel devs here to backport the stuff to the .32 kernel so a lot of bugs can be fixed and stuff can be made more stable until the .37 kernel is ready. All the commits can be found here
https://github.com/charansingh/cm-kernel/tree/master
There might be some bravo or passion instances in there cuz i am comparing the code with these two devices and taking what is necessary and sometimes i have to leave my work due to some other work and forget which file i was working on so would appreciate the more bugs.
Also Mods can we get this a sticky so we can track the progress here
Yap.. i'm not a really pro developer but i suspected those bugs before.. finally a real developer suspected that.. eager to see who's going to help fixing them
charnsingh_online said:
Also Mods can we get this a sticky so we can track the progress here
Click to expand...
Click to collapse
Ok sticky for the moment to see if it helps.
@charnsingh_online
I am really happy that you put so much power in this project big respect for that.
The reason for the missing code is because most of the drivers are reversed engineerd from winmo by cotulla. Wich make it possible to make working android parts but they don't work optimal by that. Also we miss some skilled active coders. After cotulla almost everything is created by markinus he did a incredible part big credit to him but looks like he isn't that active anymore..
Current development are mostly little things a guy who sees a little part from that and a little part from that like : you, tytung, darkstone, gauner,letama, the guy from the bluetooth fix.
We probaly don't have so much real kernel programmers because they buy a native linux / android phone.
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
memin1857 said:
The last two major things left with HD2 Android are buggy speakerphone and missing assisted-gps function.
Speakerphone mode is not usable because mic gain does not change when speakerphone is enabled. Info here:
http://forum.xda-developers.com/showpost.php?p=12698204&postcount=22
GPS works but without assistance so most locks take 1 minute instead of like 15 seconds. Info here: (please read all 25 pages)
http://forum.xda-developers.com/showthread.php?t=1008252
Click to expand...
Click to collapse
actually i think the gpu drivers are kinda unstable when comparing to the performance of other phones that carry the similar gpu...
@charnsingh_online
Good start.
After reading the github commits, I still don't understand what kernel devs can do so far.
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
hi charansingh,
i am willing to help, but i think it would be helpfull to define packets to take over.
By looking in the kernelsources it looks good to me, but i know from own expiriences with porting that i have to look deep...
best regards
trilu
charnsingh_online said:
Just see the microp stuff I added to the file. Also I have updated the board files. See wats the difference between the files. A lot of updated code
Click to expand...
Click to collapse
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Ok I'll do it tomorrow n also maintain the list in the op
I may be wrong, but this thread is not supposed to become a bug fix request thread. It is aimed at developpers, so that they collaborate on a merging of HD2 specific stuff onto a cyanogen 2.6.37 kernel...
This would most likely result in the resolution of a lot of our issues, but in the mean time, [DEV] in the thread title means it is for devs only......
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
I looked pushed code and it's ok, at least for first few commits. But it needs some deep cleaning an optimization, also there is some bravo naming convention used in leo specific files. You should put this tree on gitorious so we can do more work on it, but anyway i will clone tree and do some cleaning and porting new stuff.
This could be of interest, and not too much off-topic.
This kernel: http://forum.xda-developers.com/showthread.php?t=966786
is being abandoned and it had some patches for performance that I think are valuable. It had linpack scores that can be achieved only with heavy overclocks on other kernels... The problem is, the source is being distributed by a .zip, no commits, nothing... the only way to get those would be to issue a diff with... something and guess where they are. Staying on topic, I've already adapted cm-kernel for another device so I think I'll be able to help when I get enough free time to spare.
D4rk50ul said:
Keep this thread clean please.. there are only a select few devs who actually work on kernels around here. Let them use this as a way of communication to generate a complete kernel, then we can test it for bugs.
Very excited about the prospects of this, if you guys get a working kernel with all the new commits shoot it over and I'll test it out on one of my HD2's.
Click to expand...
Click to collapse
Yes you are right. Unfortunately many threads like this one get's filled with off topic chatter, complaints etc. I will try to keep my eye on this thread so the dev's can communicate. If your not contributing to the DEV work on the HD2 kernel's, please don't post your wishes and thanks post as this will quickly clog up the thread. I'd hate to lose progress due to this. That's why many DEV's end up not using XDA and reverting to IRC only. Thanks
noellenchris
Hi,
Few days back there are some conversation about libsurfaceflinger.so for color banding issue http://forum.xda-developers.com/showthread.php?t=1012278 . Since Rom is changing continuesly with libs can we port the change for color issue.
HD2 GB-2.33-SENSE-2.1 LOCKSCREEN SENSE-3
tytung said:
It's better to start/clone from pure CM 2.6.37 kernel, then add new commits when adding any new functions.
Would you please add a new commit when adding a new function?
Otherwise, it's very easy to lost the way in the source code.
A commit "Update some board files" doesn't tell the whole story. I want to know why to change.
Comparing the source code manually and guessing its function is not convenient for any kernel devs.
For me, I won't add any code in my 2.6.32 kernel until I know the meaning of the changes of the source code.
Thanks.
Click to expand...
Click to collapse
tytung, has any1 of you done so? please let us know..
g30rg10u said:
tytung, has any1 of you done so? please let us know..
Click to expand...
Click to collapse
No, I didn't work on 2.6.37 kernel so far.
I didn't see that charnsingh_online added a TODO list in the OP.
Fried my laptop charger. New one on way. Hd2 arrived
@Kernel devs,
Please, congregate your forces and build 3.x kernel for our precious Arc. I bet this will be one of the most (if not The Most) appreciated works. I bet this will be one of the most useful ones too. I bet almost every Arc/S user will agree with me.
Sent from nowhere
Absolutely!
What are the features you are waiting for in 3.0?
soo what does the new kernel provide?! I've seen few comments about users wanting the new kernel, and was wondering what improvement will it do to our Xperia?!
Mods please move this thread to general or Q&A. This thread is for android development, not wish lists.
Yes we'd all love a new kernel, why not bump to 3.5, well the answer to that is closed source drivers. While we should be able to theoretically add most of the maintenance patches to get to the latest 2.6.32.xx, porting to different major versions are just unlikely to be possible for our phone. You can't link against something with a different API, it just won't work.
The first request should be made to Sony to release sources for these drivers. Good luck with that.
So instead of focusing on version numbers, instead ask "Is feature X possible with our current kernel" and the kernel devs will try to accommodate and patch it in.
First of all, this isn't for Wishes and Requests, this is where you share you dev work with everyone, if you have a request then go to general or Q&A.
Second, EVERY DEVELOPER ALREADY KNOWS ABOUT THIS. Everyone IS WORKING on Kernel 3.0, ICS was laggy and JB isn't perfect is because the the lack of support in the kernel. So they don't need a "request"
Third, it is not impossible but very very hard. There is a reason why kernel 3.0 was never ported, because even the best devs like FXP and DoomLord CAN'T. Unless Sony releases their hardware sources or some developers open up his own Arc and get it out, no kernel 3.0 can be ported!
Custom msm7x30 3.0 kernels are still really in infancy stages with no major changes. If anything it's just a facelift but still the same purpose-wise.
Well, for those saing that devs can't do something I would argue - there's a 3.0 kernel being developed for HTC Desire (which also has closed source drivers) and guys working on it are pretty close. Same goes for HTC DHD and HD2 if i'm not mistaken. So why not for our device?
Sent from nowhere
tajimura said:
@Kernel devs,
Please, congregate your forces and build 3.x kernel for our precious Arc. I bet this will be one of the most (if not The Most) appreciated works. I bet this will be one of the most useful ones too. I bet almost every Arc/S user will agree with me.
Sent from nowhere
Click to expand...
Click to collapse
+ over 9000!
---------- Post added at 09:49 AM ---------- Previous post was at 09:40 AM ----------
It would be just awesome, beacuse idiots from Sony will pobably never update our kernels. Even HTC Wildfire S (which is little, smarttoy) has 2.6.35.x. It's not big difference, but... It is!
pmdisawesome said:
First of all, this isn't for Wishes and Requests, this is where you share you dev work with everyone, if you have a request then go to general or Q&A.
Second, EVERY DEVELOPER ALREADY KNOWS ABOUT THIS. Everyone IS WORKING on Kernel 3.0, ICS was laggy and JB isn't perfect is because the the lack of support in the kernel. So they don't need a "request"
Third, it is not impossible but very very hard. There is a reason why kernel 3.0 was never ported, because even the best devs like FXP and DoomLord CAN'T. Unless Sony releases their hardware sources or some developers open up his own Arc and get it out, no kernel 3.0 can be ported!
Click to expand...
Click to collapse
Work had already begun (with a lot of help from Jimbo77). It is stopped now (holidays) but for sure it's not abandoned.
tajimura said:
Well, for those saing that devs can't do something I would argue - there's a 3.0 kernel being developed for HTC Desire (which also has closed source drivers) and guys working on it are pretty close. Same goes for HTC DHD and HD2 if i'm not mistaken. So why not for our device?
Sent from nowhere
Click to expand...
Click to collapse
Because there is no Sony msm8255t 3.x kernel released that we can use as a base. There are major changes between 2.6.3x and 3.x kernel so
-all hardware related files (read: cpu, vibra etc) must be updated
-all drivers (read: screen, keys, sound etc) must be updated or rewritten
so it takes a lot of time and learning.
It's done when it's done
Click to expand...
Click to collapse
gen_scheisskopf said:
Work had already begun (with a lot of help from Jimbo77). It is stopped now (holidays) but for sure it's not abandoned.
Because there is no Sony msm8255t 3.x kernel released that we can use as a base. There are major changes between 2.6.3x and 3.x kernel so
-all hardware related files (read: cpu, vibra etc) must be updated
-all drivers (read: screen, keys, sound etc) must be updated or rewritten
so it takes a lot of time and learning.
Click to expand...
Click to collapse
first and bigest major new funcion is ntfs suport(for me there are, also sove with batery iporvents , also ksm is form 3.0.16 or 3.0.8(with used in cm roms))
n1kolaa said:
first and bigest major new funcion is ntfs suport(for me there are, also sove with batery iporvents , also ksm is form 3.0.16 or 3.0.8(with used in cm roms))
Click to expand...
Click to collapse
I had internal functions in mind (like ssize_t(*show) ), not user level.
Why would anyone think that this thread belongs in Development section, is beyond me.
Moreover, why would anyone think that in such community, known for the breakthroughs that its developers are achieving at a daily basis, such a request thread is needed.
I would like to believe that anyone who has been here long enough knows that if something is possible, it is done.
So, all in all, please think twice before clicking the "Start A New Thread" button.
Thanks for your cooperation.
Thread closed.
You might already know about the existence of the beautiful SailfishOS, what if it was possible to port it to our XPERIAS? It would look great on XS! Waiting for suggestions.
Wtf, QT based? MeeGo based? Last time I heard these words was when I was on symbian .
Personally I don't like the UI, and the android app compatibility
Sent from my LT26i using xda app-developers app
Ahh c'mon dont be that agressive! It's just and experiment, Sailfish is open source and can be ported, it only depends on the devs, will they do it or not.
MY BAD!!!
I messed up the pages and posted my thread into wrong section!!! Please remove it, I wanted to post it in the Q&A.
Sorry Sorry Sorry....
Oooohhh yeah, I really love Meego and Sailfish would be one very nice addition to ever growing Xperia S ROM collection
Would love Dual-Boot it on my Xperia S
Hope some friendly dev port it to our Xperia S.
Would love to have this wonderful OS. This is what Nokia essentially could've had instead of that other OS. It looks very well designed and very thoughtfully done.
https://www.youtube.com/watch?v=zxv7iXwIgno
If we can't get it ported, I'd at least love the launcher xD
Sent from my LT26i using xda premium
Would love to have this wonderful OS.
please can we have this
bclub said:
please can we have this
Click to expand...
Click to collapse
i dont think we ever get this bcoz we have only left 1 or two active developers for our xperia s.where other devices have plenty of roms, we just have one rom to play....Thanks to mickybart who is still making Xperia s alive....
In fact Sailfish OS is not 100% open source. All the UI is closed source.
Android compatibility is not supported on "custom" ROM too and it is not possible to buy a licence per device for now.
And last financial situation was not so great :/ (I hope that Jolla will survive and will be able to deliver a new phone in the future)
So that make interest more limited to work on it hardly.
I have already attempt to run SailfishOS and all sources to compile it are available under my github (https://github.com/mickybart/). The main issue is about hwcomposer implementation that is not working for our device. After long hours of troubleshooting I was not able to run the graphical stack. I forced clock initialization on the kernel too to avoid issues and it was better (no more kernel panic) but not enough to fix the problem. In fact the issue seems to be on the GPU driver because hwc initialization is done as it is done by SurfaceFlinger but it fails.
I have an experimental solution that permit me to run interface with SurfaceFlinger. So it is supposed to be possible to adapt lipstick (wayland compositor used by mer-hybris/SailfishOS) to use SurfaceFlinger but I chose to work on plasma mobile for now.
mickybart said:
In fact Sailfish OS is not 100% open source. All the UI is closed source.
Android compatibility is not supported on "custom" ROM too and it is not possible to buy a licence per device for now.
And last financial situation was not so great :/ (I hope that Jolla will survive and will be able to deliver a new phone in the future)
So that make interest more limited to work on it hardly.
I have already attempt to run SailfishOS and all sources to compile it are available under my github (https://github.com/mickybart/). The main issue is about hwcomposer implementation that is not working for our device. After long hours of troubleshooting I was not able to run the graphical stack. I forced clock initialization on the kernel too to avoid issues and it was better (no more kernel panic) but not enough to fix the problem. In fact the issue seems to be on the GPU driver because hwc initialization is done as it is done by SurfaceFlinger but it fails.
I have an experimental solution that permit me to run interface with SurfaceFlinger. So it is supposed to be possible to adapt lipstick (wayland compositor used by mer-hybris/SailfishOS) to use SurfaceFlinger but I chose to work on plasma mobile for now.
Click to expand...
Click to collapse
Hello sir...I am a great fan of yours and it worths...I follow your git everyday..I saw you are working on a project named hybris 5.1.1...can you tell me something about it???asking for my curiosity...sorry for my bad English
Sent from my C1904 using XDA-Developers mobile app
mihirtherocks said:
Hello sir...I am a great fan of yours and it worths...I follow your git everyday..I saw you are working on a project named hybris 5.1.1...can you tell me something about it???asking for my curiosity...sorry for my bad English
Sent from my C1904 using XDA-Developers mobile app
Click to expand...
Click to collapse
In fact the project is gnulinux_support (that include hybris with gnulinux-support-5.1 branch). For now I'm testing and writing the documentation to officially release this new project.
I will create an official xda project really soon (this week or next one if everything is good ! Take me longer time than expected !). The state of the project is very good but it will be reserved for developers to start.
You will know more soon
mickybart said:
In fact the project is gnulinux_support (that include hybris with gnulinux-support-5.1 branch). For now I'm testing and writing the documentation to officially release this new project.
I will create an official xda project really soon (this week or next one if everything is good ! Take me longer time than expected !). The state of the project is very good but it will be reserved for developers to start.
You will know more soon
Click to expand...
Click to collapse
Thank u sir for your reply
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Sarmiento_Luise said:
Hello! This is my first post and i want to know if anyone is making an AOSP rom for this device? It appears that this device is really laggy and stutters here and there. The Geodev rom is based on AOSP i think but don't know how the rom is doing right now and i can't comment on it because this is only my first post. MAY I KNOW WHO HERE IS TRYING TO GET AOSP FOR OUR DEVICE BECAUSE THAT IS THE ONLY WAY OF MAKING THIS SMOOTH. Thanks everyone! Cheers!
Click to expand...
Click to collapse
As of now, Geodev is the only one in development. If you're trying to get your post count up, go to the XDA General section and post in the new members forum or the off topic lounge.
postcount++
imho that geodev thing sounds shady at best.
If you would decide to port a custom rom to a new device, would you really start by porting KitKat if the device
currently only runs jellybean? Wouldn't it be easier to use the stock kernel for now to get cm10 running
and then wait paitiently until htc releases the kernel src to make it a full unofficial cm10 build.
Instead this sounds more like taking the existing source of a hopefully hardware compatible build
and bending it until it brea.. ehm works.
I may be biased, but if you plan to make any kind of release you usually don't go and announce it to the world.
This only encourages the rather impatient endusers to come up with many variations of the same old:
"i need my rls now!", "I am entitled to a release because I found this thread","GIMME RLS!!!11oneeleven"
posts that will just annoy the crap out of every dev I've ever met. Also there is absolutely no point in asking for
beta testers before you even have a working build ready.
Combine that with the recent e-begging post and draw your own conclusions.
DroidTwe4kz said:
[...] I can't continue developing until someone gift me new computer (or motherboard only). [...]
Click to expand...
Click to collapse
In any case, for the time being it might be a good idea to check if there are some services you could deactivate
in order to get a little bit more speed out of your phone. I personally have no problems with lags, but maybe
it's because I don't expect the phone to run every app ever made at the same time since it has only 512MB RAM.