@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.
Related
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
Hello boys and girls,
Thanks to Scooter1556 Michga and MaRekRM I am now able to do some porting (well, actually it is more of a copy/paste venture) on the GINGERBREAD roms of other HTC phones, like the HTC Wildfire and HTC Hero. The files I posted in this thread are only for the gingerbread builds and don't work for the other versions of Android. Since this is porting on your own, I can't possibly know what does and doesn't work for you. But just to give an example I never have gotten the wifi working.
These files are just taken from Scoot's latest android build:
http://dl.dropbox.com/u/8992815/xda/porting/Copy/paste.zip
Be sure to remove all the files in the original build first, EXCEPT the files in the permission folder. You just need to add the files which are present in the paste folder, but not present in the system folder you are porting.
And as always I am not responsible if you break/brick your phone (I do advise using the haret method when you're purely experimenting with different roms)
**And if you find a nice rom combination for our kaiser, then don't feel ashamed to post the combi**
Also if you find a better way of which files to port, then please post your improvement. And if your find other devices from which we can port the roms, also post them
Have fun!!
**I advise using 7zip, http://www.7-zip.org/, when unpacking and repacking the system folder!**
Hi,
It's great that someone interested yet in the Android on Kaiser project.
I'm installed scoot's latest ROM some days ago. It's mostly stable enough (not perfect but really, really not as bad), fast and smooth for me with 500Mhz OC setup, and have a nice position in benchmarks also.
But I have some problems (like the total lack of power saving), and I have a little time to check it out if I can do something to fix or optimize something. So I'm glad that the CM7 project is living yet on the forum.
Well, so as I see the kernel itself is the bigger problem in porting, because of the oldish Kaiser specific drivers. Are these drivers in my current install is compiled from source (and if yes are these have a downloadable source), or collectible from other devices, or we have to stick to 2.6.32 kernels and use these binaries what we have now? I'll thank some of your helpful experiences shared in this topic.
What else... it's a bit late here, let me see if we can progress in the topic, it would be great if the porting would be open for everyone who want to participate.
Steve
I am sorry if I gave you the wrong idea, but I am really quite a noob on android development, my knowledge is really limited. I am just able to read the given tutorials and I am able to google my problems, but it is not like I actually know something.
The original source for the package which I posted in this thread is, I should have mentioned befor, given in this link:
http://forum.xda-developers.com/showthread.php?t=996431
I just followed the instructions in this thread and also got help from MaRekRM in this thread:
http://forum.xda-developers.com/showthread.php?t=1382722
But that's all I know, I hope that a actual developer notices your question, but although I really want to be helpfull, I can't. Due to my limited knowledge.
**I just posted this thread to make it easier to port for other, who didn't feel like searching for the aforementioned thread**
Thank you hom.hom. Yes, these posts help me a lot. I see the basic strategie behind the porting. I made some research today around the possibilites.
The problem is that the Kaiser have MSM7200 CPU, and devices based on this version only shipped with windows mobile. Android only installed on MSM7200A, which is nearly the same CPU. I think the only difference is the increased speed. At least, as I see in the specifications. So now I'm collecting anything Android related stuff from devices based on MSM7200A.
I also managed to get the CM version of the HTC Hero and HTC Wildfire to boot, so it is not only the msm7200 processor. I think you might even be able to also port the msm72xx proc.'s to the htc kaiser. Also the Sony Ericsson Xperia X10 pro has roughly the same specs so you might even give that one a roll.
And if you find a nice rom out there in the other forums, you can just post them here.
And glad to be a help!
Re
Hi
Thanks.
That long time ago when we discussed about it i successfuly made a sense rom for kaiser.. i think it could be too on SD and on mobile (sry, i forgot name of this first option in install menu) it was slow, but not too much.. With little more tweaks and upgrades it will be usable.. and it was stable..
It was too for 320x240 so ther wasnt any problem with resolution
Unfortunately, somehow i lost it.. (maybe i deleted it, i dont know) and i tried it again many times but nothing.. worse is i dont know which model exactly was (i mean wildfire,hero,....)
i did it with same steps as you wrote..
Now Im iSheep.. So i dont working on it yet..
I think now cannot be ported ICS because we havent any ICS kernel for iphone.. Latest is GB
Hey and i forgot for something..
I made ports from:
MyTouch 3G
Hero
Tattoo
Wildfire
So good luck and i believe here will be more ports..
---------- Post added at 12:07 AM ---------- Previous post was at 12:03 AM ----------
hom.hom said:
I also managed to get the CM version of the HTC Hero and HTC Wildfire to boot, so it is not only the msm7200 processor. I think you might even be able to also port the msm72xx proc.'s to the htc kaiser. Also the Sony Ericsson Xperia X10 pro has roughly the same specs so you might even give that one a roll.
And if you find a nice rom out there in the other forums, you can just post them here.
And glad to be a help!
Click to expand...
Click to collapse
I think you can make a hero-based rom.. In "Kaiser and. dev. forum" are some roms based on hero.. but there is a little problem with resolution.. default is 320x480.. but somehow if i remember, can be ported to QVGA (320x240).. So try it
Hello everyone...I'm planning on trying to develop a gingerbread kernel for AOSP because we don't really have support anymore and everyone has moved onto developing for ICS (not that this is a bad thing). I figure in my spare time I might as well try to learn and develop for our phone. Let me start by saying I was never really into phones/smartphones/rooting, or software development, but I've always been fascinated by Linux in general. I've played around using a number of Linux distros, but I've never really done anything intensive with them (modified their kernels, etc.) but I am vaguely familiar with terminal usage.
Anyways that was just my introduction. I've been running an ICS kernel on my AOSP GB system (specs/stuff in my signature) and while most advised against it, I find it to run pretty well. I'm not sure why it seems to run so well on my phone, but it's basically solved most of my problems (or at least it appears to have done that), but I know the kernel isn't "optimized" for my phone. Some major things people have said are that the ramdisking operations/system is totally different when comparing ICS and GB. This kernel that I'm using is running pretty well, even knowing this fact. What I was wondering is if I could basically get the ICS kernel, then "merge it" with a GB kernel's parameters that pertain to the ramdisk/other major options of GB. That would probably make it better. Also, people stated that multitouch issues for the DINC2 occured on Aeroevan's 0.8 kernel, but not on the 0.7 kernel. This was the changelog stated by aeroevan:
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.
Click to expand...
Click to collapse
So maybe this "small touchscreen driver update" is the thing that caused it, but I'm assuming many other kernels applied this update too? Maybe there is a way to roll back to whatever was in 0.7 in this sense to get rid of the multitouch bug that plagues some people.
I have a pretty powerful laptop, so development shouldn't be too bad. I plan on running Ubuntu 11.10 (or whatever people find suitable these days) in a Virtual Machine and I plan on compiling stuff from there. I am not claiming I know everything or that these things are correct....I am simply just throwing out some brainstorming to get some ideas out there. I know GB is "old", but I (and some others as well) enjoy it's stability and that it generally functions perfectly. Maybe this thread will get a look from popular devs, or maybe it'll get a look from people who just know this stuff. Thanks for reading, and sorry for the length of the post.
Looking forward to your progress on this.
Sent from my ADR6350 using xda premium
It would be nice to have another kernal for AOSP other than aero.
Your help in developing AOSP kernels would be fantastic.
Thanks given. Because I am hard of hearing I cannot use any of the kernels (even Evan's) and have to stick to Sense
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.
MIUIv5 will Jelly Bean, based on GeekyDroid's CyanogenMod 10.
Kitkat will be Source Compiling, and may not be fully functional.
let me Know, So I am working on a more beneficial project.
quakze said:
MIUIv5 will Jelly Bean, based on GeekyDroid's CyanogenMod 10.
Kitkat will be Source Compiling, and may not be fully functional.
let me Know, So I am working on a more beneficial project.
Click to expand...
Click to collapse
Can you see anything related to lollipop on github If you have synchronized resources ???
Sent from my XT1033 using XDA Free mobile app
sachoosaini said:
Can you see anything related to lollipop on github If you have synchronized resources ???
Sent from my XT1033 using XDA Free mobile app
Click to expand...
Click to collapse
Due to lack of responses for my present project, I have decided not do.
I also ask the moderator to close this thread
upon you
quakze said:
Due to lack of responses for my present project, I have decided not do.
I also ask the moderator to close this thread
Click to expand...
Click to collapse
well ohk
sachoosaini said:
well ohk
Click to expand...
Click to collapse
I Thought of doing Kitkat, tried with prebuild Kernel but compiler says its deprecated and discontinued.
So trying to compile Kernel with the Kitkat ROM.
To make it happen, Need some support from you guys !
Well i am not developer
quakze said:
I Thought of doing Kitkat, tried with prebuild Kernel but compiler says its deprecated and discontinued.
So trying to compile Kernel with the Kitkat ROM.
To make it happen, Need some support from you guys !
Click to expand...
Click to collapse
you see i don't own a linux ever. i use windows and my laotop is mostly always filled my own stuff. i need a decent RAM for building a machine for ROM And kernel development. so in that case i never able to succeed. IT require a certain amount of knowldge about programming which i don't know. so here everything stops. Well i tried to ask as much as developers in the past to make us a 3.0 kernel. but the issue is that our processor is way too slow and moreover it is single clock. The biggest thing that hampers the development is the non availability of GPU. After 2.3.7 google has introduced hardware acceleration. That was the last that was enough to kill our willy. Now as the code changes and and API changed with the more powerful phones. So at the end of the tunnel i also came to know that arm 6 processor does not support ART. So whati thought that someone will try to port the kitkat for our willy. But most of the devices that are getting the updates of kitkat are having GPU. I closed down my threats because of this. No one want to work on a device in which the power is way too less. so the main issue is not with kernel i saw HTC Explorer got KITKAT on 2.6 version of kernel though it is buggy but still they got it. Now hell it again has GPU. SO GPU is must for anything to happen after 2.3.7.. SASA's last attempt to built 4.2.2 is the last ray of hope for us. Because there the main developer of the arm 6 supported us for a while but then he vanishes. Well now just imagine for a wonder that somebody will post a KITKAT built. :good: