Hi all.
Not sure whether this was the right place to post, but coming from a development perspective, I thought it was fitting. If not, mods - please feel free to move.
This thread is here to bring the currently worked on 3.0 kernel for the Desire to the HD2 developers' attention. There is minimal difference in the Desire hardware when compared to the HD2, and therefore would probably not be a difficult port to perform.
The main benefit of porting this kernel over to the HD2 is the improvement in ICS, namely through Hardware Acceleration. Although it hasn't been confirmed yet, the OP over in the Desire thread seems to think Hardware Acceleration is working.
I'm reaching out to all the HD2 developers to collaborate their efforts in an attempt to port this over to HD2 - it will bring us an even more well-rounded ICS build, extending the already expanded boundaries of our beloved HD2's.
The link to the original thread is here.
The link to the github source code is here.
All credits go to Chaosz-X for the current work on the kernel. I am simply acting as a messenger.
I wish you guys luck, and hopefully it won't take long to get some work going on this!
MrP.
It is not as easy as you might think. Altough the hardware is the same the radio is completely different because it is from windows mobile. Wich makes most of the work on the ics kernel useless. No and radio's can not be changed easily because they are closed source.
then how did the desire 2.6.35 kernel get ported ?
I thought hardware acceleration was already working in ICS.
jan-willem3 said:
It is not as easy as you might think. Altough the hardware is the same the radio is completely different because it is from windows mobile. Wich makes most of the work on the ics kernel useless. No and radio's can not be changed easily because they are closed source.
Click to expand...
Click to collapse
Forgive me for my lack of extensive knowledge in the kernel department, but, considering that quite a few of the currently developed kernels for the HD2 are based on the Desire sources, I would've assumed that what was done before in porting the 2.6.35 kernel, could be adapted to work with this kernel.
Once again, not saying that's right, because I'm basing that conclusion off logical thought, not experience.
Visentinel said:
then how did the desire 2.6.35 kernel get ported ?
Click to expand...
Click to collapse
My point above exactly. If it's been done before, surely the steps needed to adapt the 3.0 kernel are not far out of reach. The people I think we should be talking to are marc1706, and tytung. I'll pop them a PM when I have a moment.
KyJelly69 said:
I thought hardware acceleration was already working in ICS.
Click to expand...
Click to collapse
It's not true Hardware Acceleration - its a hack of sorts. It gives a boost in performance no doubt, but most likely no where near true Hardware Acceleration.
Thanks for the input guys.
MrP.
It might be possible to port the 3.0 kernel to the HD2 but the thread you linked is currently providing a 2.6.35.14 kernel. They are planning on releasing a 3.0 kernel.
In order to get a 100% supported hardware acceleration we will need a 3.0 kernel, since ICS was build for the 3.0 kernel. It's pretty much the same with the glitches in sense 2.1 and 3.x ROMs we had prior to using the desire .35 kernel.
marc1706 said:
It might be possible to port the 3.0 kernel to the HD2 but the thread you linked is currently providing a 2.6.35.14 kernel. They are planning on releasing a 3.0 kernel.
In order to get a 100% supported hardware acceleration we will need a 3.0 kernel, since ICS was build for the 3.0 kernel. It's pretty much the same with the glitches in sense 2.1 and 3.x ROMs we had prior to using the desire .35 kernel.
Click to expand...
Click to collapse
Thanks for your input marc1076.
I am aware that it's not 3.0 yet, however, he has backported quite a few things for now, mainly concerning hardware acceleration (as written in the OP).
Would it not be a good step to then try this kernel on our current ICS builds in the hopes of any improvement? Or perhaps alternatively incorporate the backports (possibly more difficult) into our current ICS kernel(s) in an attempt to edge closer to true Hardware Acceleration?
A few thoughts, may be possible, or not - feel free to correct me. Thanks again for the advice.
MrP.
MrPadie said:
Thanks for your input marc1076.
I am aware that it's not 3.0 yet, however, he has backported quite a few things for now, mainly concerning hardware acceleration (as written in the OP).
Would it not be a good step to then try this kernel on our current ICS builds in the hopes of any improvement? Or perhaps alternatively incorporate the backports (possibly more difficult) into our current ICS kernel(s) in an attempt to edge closer to true Hardware Acceleration?
A few thoughts, may be possible, or not - feel free to correct me. Thanks again for the advice.
MrP.
Click to expand...
Click to collapse
Once I see some true ics kernels with specific commits for ics you will see them appear in our kernels.
Sent from my HTC HD2 using XDA App
warrenb213 said:
Once I see some true ics kernels with specific commits for ics you will see them appear in our kernels.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks for your reply warrenb213.
However, I'm kinda lost as to what you are saying - are you saying that our current kernel (namely Tytung's kernel) for ICS is not a proper ICS kernel (which it isn't really, it's adapted from GB kernel from what I can tell), and until we have a kernel dedicated to ICS, there won't be any of the above mentioned additions?
If that's the case, what is your reasoning for saying that if I may ask? And also, where can these 'true' ICS kernels be sourced from? (As far as I know, the only 'true' ICS kernels around are based on 3.0, which in essence, defeats the object of us porting these additions back in the first place).
MrP.
MrPadie said:
Thanks for your reply warrenb213.
However, I'm kinda lost as to what you are saying - are you saying that our current kernel (namely Tytung's kernel) for ICS is not a proper ICS kernel (which it isn't really, it's adapted from GB kernel from what I can tell), and until we have a kernel dedicated to ICS, there won't be any of the above mentioned additions?
If that's the case, what is your reasoning for saying that if I may ask? And also, where can these 'true' ICS kernels be sourced from? (As far as I know, the only 'true' ICS kernels around are based on 3.0, which in essence, defeats the object of us porting these additions back in the first place).
MrP.
Click to expand...
Click to collapse
First of all, tytung's kernel which is based on hastarin's sd kernel is a base of .32 kernel from froyo source of the eVO 4g. It was not supposed to be used in gb but since it works, no worries.
Even though AOSP is opensource, the driver code for the devices is not, which makes porting difficult and moreso when the device actually never had any drivers for that specific os (read Android on HD2).
There is already an initiative (thread to be precise) in the qualcomm developer forums pleading them to opensource the qsd8250 drivers so that devs who are not so rich can backport ics to n1, desire (or HD2 for that matter) since it is clear that HTC certainly won't and google too has given up n1.
What tytung did to make his kernel work with ics is add upon the old base, it works but is dirty and should lead to unexpected issues.
The true ics kernels are based on the 3.0.1-tag of linus's repo.
You can sync into linus's 3.0.1 and compare it to the kernel source code of Galaxy Nexus, see the android changes, port them to the vanilla kernel, copy htcleo board files while rebasing them on 3.0.1 and adding the radio code from current kernels. It is far easy to say this than to actually do this when looking at the staggering size of the linux codebase.
The question is how many of the HD2-specific changes were broken by
a) changes in the upstream Linux codebase in between 2.6.32 and 2.6.40 (aka 3.0)?
b) android-specific changes between Froyo, GB and ICS
EDIT: There seems to be a working (except for USB mass storage) 2.6.35 kernel here. This at least reduces the number of upstream code changes to deal with.
Dr_Grip said:
EDIT: There seems to be a working (except for USB mass storage) 2.6.35 kernel here.
Click to expand...
Click to collapse
USB mass storage works, confirmed it once again. USB Tethering doesn't work. Still working on it.
Dr_Grip said:
The question is how many of the HD2-specific changes were broken by
a) changes in the upstream Linux codebase in between 2.6.32 and 2.6.40 (aka 3.0)?
b) android-specific changes between Froyo, GB and ICS
EDIT: There seems to be a working (except for USB mass storage) 2.6.35 kernel here. This at least reduces the number of upstream code changes to deal with.
Click to expand...
Click to collapse
And a fully working one here
Visentinel said:
then how did the desire 2.6.35 kernel get ported ?
Click to expand...
Click to collapse
Because it was an htc kernel just like the prevous evo 4g kernel so porting it was more easy. If you look at the 2.6.35 cm kernel it is highly unstable and the MSM kernel is also an AOSP kernel like the cm kernel.
jan-willem3 said:
Because it was an htc kernel just like the prevous evo 4g kernel so porting it was more easy. If you look at the 2.6.35 cm kernel it is highly unstable and the MSM kernel is also an AOSP kernel like the cm kernel.
Click to expand...
Click to collapse
That does not make sense, I think. If the Desire devs get a working kernel for the Desire, the changes needed to make it working on the HD2 should be the same no matter if they are starting from a HTC or an AOSP codebase.
That it will be more complicated to get a working 3.0 Desire kernel without HTC's codebase is a challenge the Desire devs will have to face unrelated of the porting effort to the HD2.
uzi2 said:
And a fully working one here
Click to expand...
Click to collapse
Can you confirm that everything works?
My kernel is forked from ACA 2.6.35 non-sense and developed further...
fhasovic said:
Can you confirm that everything works?
My kernel is forked from ACA 2.6.35 non-sense and developed further...
Click to expand...
Click to collapse
There are voice recorder issues in the current version, but these are fixed in the latest release 0103
Swyped from my aHD2oid
SPEAKING FOR THE NOOBS
I LOVE MY PHONE TO ME IT'S SUPER FAST,
BUT WHAT YOU GUYS ARE SAYING IS THAT IF WE HAD A NATIVE ANDROID WITH THE SAME SPECS AS OUR HD2 IT WOULD BE EVEN FASTER AND BETTER?
THIS IS MY FIRST SMART PHONE SO I'M JUST CURIOUS ABOUT THAT.
Sent from my HD2 using xda premium
turn your caps lock off.
Short answer: You can expect the same performance from the HD2 as from the Nexus One and Desire, given it runs the same software.
Slightly longer answer: This is a development thread. What we are talking about is getting the linux kernel (think: core of the system) version used by ICS running on our phone.
Getting this to work -as opposed to trying to get a Froyo/GB kernel working with ICS- would benefit both performance and stability.
There are some issues with that. Most of them are related to the fact that Google and HTC have dropped official support for the Nexus One and Desire. The only issue related to the HD2 not being an native Android phone is the need for a special radio driver.
EDIT: If you tried to be funny: You failed.
uzi2 said:
There are voice recorder issues in the current version, but these are fixed in the latest release 0103
Swyped from my aHD2oid
Click to expand...
Click to collapse
Uzi is correct. Ill be doing a fs thing soon, a Bluetooth thing soon, and more cam related stuff. But overall 99% is fully working.
Sent from my HTC HD2 using XDA App
Related
http://www.google.com/m/url?ei=Utxj...8QFjAE&usg=AFQjCNHby1ckfYOmKipkXxt18wHMy6PdPw
There is the link just released the source code for the desire z,HD,g2 and Droid incredible today. Hope this helps all the devs.
sent from a guy living in a van down by the river
Sweet, so we have new source code for our MT4G kernel. Anything fun you devs can do with this?
There's not much new in this Kernel release for MT4G (Glacier).
HTC updated:
FM Headphone code
Dock Accessory code
Upgraded old DMA engine to the DMA engine from Aurora Project (Google Chrome project)
That's it... If you use this as baseline, you will still have Youtube issues
If you want to find out more about kernels, read my Sense Kernel thread...
I am somewhat disappointed by this HTC release because it means T-Mobile is getting this code also, which means the upcoming OTA update may not be Gingerbread but just a maintenance release to fix a few minor bugs.
Until HTC release their Gingerbread Kernel, we are stuck @ Froyo (Linux Kernel 2.6.32 based).
Maybe after I reach version 1.0.0 for my Sense Kernel, I might start a pure Gingerbread Kernel which is Linux Kernel version 2.6.35+
the only thing they need to update is the fact that the focusing on the camera is all out of wack
im a noob
but the nexus one got gingerbread. maybe that can help out our community?
TopazUser1 said:
im a noob
but the nexus one got gingerbread. maybe that can help out our community?
Click to expand...
Click to collapse
LOL download a cm7 rom and you will have gingerbread
faux123 said:
FM Headphone code
Click to expand...
Click to collapse
Does that mean someone could make an app that could record FM radio? Just a thought.
Now that bytecode has given us CWM, the question becomes what current ROM or branch of cyanogenmod would give us the biggest jump on getting a working image for our phones?
I think CM9 would be a good candidate. It would probably be the most popular choice to get working. I know I'm itching for ICS on our phone. I think it would make it the best phone on the market for now.
I'm no programmer so I can only say my opinion... I think whatever can be done first to get away from LG / AT&T software. If that's CM7, cool, if it's CM9, cool.
I'd think CM7 is the way to go to jump into a custom ROM that you could get working the fastest for this phone. CM7 has been out for a LONG time and it's been well tweaked and it's SOLID!
BUT... CM9 is what's coming (and for more and more phones/tabs, it's what's already here!).
I say even if it takes more effort now (vs. an older and more stable CM7), go right with CM9 and let's get this party started!
Namuna said:
I say even if it takes more effort now (vs. an older and more stable CM7), go right with CM9 and let's get this party started!
Click to expand...
Click to collapse
Why not ICS? Maybe it would be easy to port ICS for Galaxy Nexus to Nitro?
I'd say CM7 since by the time you finish getting CM9 figured out and working with the current kernal, it will have already been released by LG.
I'm going to start working on my own custom rom, at least as long as i can figure out how to get my Ubuntu setup... ugg..
Does anyone know any good guides for making your own AOSP ROMS? Or is it all, learned knowledge and experience?
I sure wish I knew what you guys are talking about. Lol
Sent from my LG-P930 using XDA App
I think CM9 is the way to go.
Question to any who know, if we were to put CM9 or any ICS on the Nitro, will it use hardware acceleration? That is the main feature I have been waiting for.
red_solo_cup said:
I think CM9 is the way to go.
Question to any who know, if we were to put CM9 or any ICS on the Nitro, will it use hardware acceleration? That is the main feature I have been waiting for.
Click to expand...
Click to collapse
Hardware acceleration for the UI? Or 3D / 2D graphics?
I think I read the other day that you can force the UI to use hardware acceleration in the build.prop file. With CWM feel free to tinker.
red_solo_cup said:
I think CM9 is the way to go.
Question to any who know, if we were to put CM9 or any ICS on the Nitro, will it use hardware acceleration? That is the main feature I have been waiting for.
Click to expand...
Click to collapse
unless someone on the CM team gets a nitro, there will be no ICS/CM9 until LG puts out a rom.
We need to just start w/ the basics. Optimize (battery life and performance) what we currently have and go from there.
I find your lack of faith...disturbing
Seriously, I think we can get a pretty damn good rom going if we put some work into it.
AllstarE4 said:
I sure wish I knew what you guys are talking about. Lol
Sent from my LG-P930 using XDA App
Click to expand...
Click to collapse
Allstar, here u go
CyanogenMod: http://www.cyanogenmod.com/
CM7 is based on Gingerbread and is a very optimized and customizable ROM (OS) for the phone, which is generally close to perfect and has a myriad of features that you don't normally find in regular/stock ROMs.
CM9 is the same basic concept as CM7, except it is based on ICS (Ice Cream Sandwich, Android's latest OS).
ICS: http://www.android.com/about/ice-cream-sandwich/
---------- Post added at 08:27 AM ---------- Previous post was at 08:24 AM ----------
In my opinion, our phone is built to support ICS or any iteration of it (clear stated by the 3 softkeys instead of 4 in gingerbread). So I suggest we proceed with either ICS or CM9.
I don't know if it matters, but I think someone should reach out to CM team and inform them of the development. I am sure they will be very interested in developing CM9 for a phone that is clearly intended to be a rival to the Galaxy Nexus.
The main thing to consider is the kernel , ICS runs on 3.xx kernel and gingerbread on 2.6 , porting 2.6 kernel drivers to 3.xx is alot of work. codeaurora kernel is a good start
https://www.codeaurora.org/contribute/projects/qkernel
bytecode64 said:
The main thing to consider is the kernel , ICS runs on 3.xx kernel and gingerbread on 2.6 , porting 2.6 kernel drivers to 3.xx is alot of work. codeaurora kernel is a good start
https://www.codeaurora.org/contribute/projects/qkernel
Click to expand...
Click to collapse
+1
Sent from my LG-P930 using XDA App
I think a simple debloated init.d optimized stock ROM should be the starting point. Starting a long project like CM9 will only slow down the adoption rate of the phone because the progress will be slow. I think most people will want to see a couple of ROM choices before they jump aboard.
Once you use CM9 it will automatically start hardware acceleration for smoothness and my upcoming base ROM that i'm including is going to have hardware acceleration and much more, please stay tune.
mod ammend
moved to general - this isn't a development query
I'm going to bet it will be cm9!
isnt riccardo from G+ already getting close to a ics release for the nitro...
Sent from my LG-P930 using XDA
Pardon the noobish question, but with the release of AOSP Sources for 4.0.4, I'm wondering: How much duplication goes on between ROM devs and AOSP devs?
When ROM devs and Kernel devs are tweaking kernels, are they fixing and optimizing the same things as AOSP devs? Or are they more often working on two different sides of the code, and fixes from one side advance the state of the art for the other?
Another way to put this: Right now, I'm using a custom kernel. Is it likely that a 4.0.4-based custom kernel will actually offer improvements over the current 4.0.3-based version of the same dev's kernel? Or have devs already made most of the tweaks that the AOSP devs did, resulting in a very modest improvement.
I'm just trying to temper my excitement a bit. I know that 4.0.4 would likely be huge coming from stock 4.0.2, but if the ROM devs are already well ahead of the AOSP folks, I won't expect 4.0.4 Gummy to be that different than 4.0.3 Gummy (for instance).
The devs merge the new code and stay current. They keep their tweaks too etc.
RogerPodacter said:
The devs merge the new code and stay current. They keep their tweaks too etc.
Click to expand...
Click to collapse
I understand, but I'm wondering how often the Dev tweaks ARE the new changes in a new AOSP release.
wanderfowl said:
I understand, but I'm wondering how often the Dev tweaks ARE the new changes in a new AOSP release.
Click to expand...
Click to collapse
Thats pretty rare, though may happen once in a while. Mostly the devs work on new features code and additions. I'll try to think of an example and post if it comes to me.
RogerPodacter said:
Thats pretty rare, though may happen once in a while. Mostly the devs work on new features code and additions. I'll try to think of an example and post if it comes to me.
Click to expand...
Click to collapse
The only one I can think of is the swyping of the notifications
Sent from my Galaxy Nexus using xda premium
Hi everybody!
I'd like to know which is the best ICS Rom for our HTC Desire...
At the moment i'm running Cyanogen7.1 and everything is fine, but i'm tired of gingerbread and don't want to wait Cyanogen9 to be stable
So, in your opinion, Which is the best rom for everyday-use?
I know there are camera issues, but this doesn't matter to me
What i'm looking for is good stability, good script for application to ext, and good (fast) browsing experience!
Also have a question:
What kind of Hardware Acceleration are ICS Rom using? Is it native support with latest Adreno driver or other?
The best ICS rom is to use the search function and try yourself.
Gesendet von meinem HTC Desire
muellersmattes said:
The best ICS rom is to use the search function and try yourself.
Gesendet von meinem HTC Desire
Click to expand...
Click to collapse
I supposed that someone would answer this way
but i don't have the time to try all the ICS Roms... So i would be grateful if someone that have tried various roms will give me any suggestion
Oh my look what I've found here using the handy search tool.
Five pages full of replies as to what is the best ICS rom. How convenient. All I have to do is give a little bit of my time to read them all and take it from there. I don't have to create a new thread, wait all day for replies that ends up flaming me.
Cristian.CT46 said:
What kind of Hardware Acceleration are ICS Rom using?
Click to expand...
Click to collapse
Whatever it uses, it is not up to the task. kite edit: uncalled for :/
Edited by moderator. Maybe best if I removed the whole post so someone wouldn't think I'm actually being helpful in these kind of threads.
There is no "best ROM", most ROM's are different and people like different things.. some people prefer "eye candy" and other AOSP highly customizable ROM's.
It's up to personal preferrence.
I think there are only three anyway, and one of them is miui. So, try bcm and sandvold and see which one you prefer. Sorry I cannot help you more, because I never flash beta roms on my phone. I am using it too much...
sudkcoce said:
I think there are only three anyway, and one of them is miui. So, try bcm and sandvold and see which one you prefer. Sorry I cannot help you more, because I never flash beta roms on my phone. I am using it too much...
Click to expand...
Click to collapse
MIUI has now been cut from development.
AOKP dev has paused development for a week or two due to other commitments, so it's a bit behind the other two, but will be back soon.
I personally prefer BCM over Sanvold's/ Nickez's release.
I also prefer BCM over others but there is one big problem for me that in some games like Angry Birds or Temple Run sometimes touch doesn't reacting, just hardware buttons.
Cristian.CT46 said:
Hi everybody!
I'd like to know which is the best ICS Rom for our HTC Desire...
At the moment i'm running Cyanogen7.1 and everything is fine, but i'm tired of gingerbread and don't want to wait Cyanogen9 to be stable
So, in your opinion, Which is the best rom for everyday-use?
I know there are camera issues, but this doesn't matter to me
What i'm looking for is good stability, good script for application to ext, and good (fast) browsing experience!
Also have a question:
What kind of Hardware Acceleration are ICS Rom using? Is it native support with latest Adreno driver or other?
Click to expand...
Click to collapse
you can try ICS by sandvold or BCM both are in beta and close to stability.
Cristian.CT46 said:
Hi everybody!
So, in your opinion, Which is the best rom for everyday-use?
I know there are camera issues, but this doesn't matter to me
What i'm looking for is good stability, good script for application to ext, and good (fast) browsing experience!
Also have a question:
What kind of Hardware Acceleration are ICS Rom using? Is it native support with latest Adreno driver or other?
Click to expand...
Click to collapse
IMHO:
It all depends how fed-up with gingerbread you are. There are currently no ICS roms for Desire that would match Gingerbread based ones in terms of speed and stability. That being said, BCM and Sandvold are at the stage where they can be used on a daily basis as long as you willing to accept that your phone might be unresponsive in critical situations.
AFAIK:
BCM is made from CM9 source soi if you come from CM7.1 this would be the smaller change in functionality (regarding mods). It's up to you whether it's a good thing or not.
Sandvold's rom is made from Evervolve source. (I'm not that familiar with that.)
I started ICS usage with Sandvolds rom a few months ago then I switched to BCM for the reasons mentioned above. These two roms' update rate is pretty muck head-to-head. Currently (AFAIK!) Sandvold's one has video recording and support for barcode scanner with higher instability while BCM only has photo capturing but more stable at that.
Both roms use Drewis kernel for HWA and not native drivers as when the drivers were made available most of the functionality they would provide were already ported by drewis and since he is more comfortable with his own source he keeps improving that.
Keep in mind that the official drivers for the chipset not for Desire in particular so official drivers wouldn't be answer for all HWA related problems. (I heard somewhere that HTC had a wierd way of implementing camera, but that might not be true.)
There's a new thread called COS-Bravo ICS by roalex. Haven't tried it yet but it seems very active recent days.
The project of Sense 3.6/4.0 porting looks very delicious, too.
if you look at the htc hd2 forums, you will see everyone is using tytung kernel for their 4.0 to 4.2 roms as it has fully working 720p video playback, camera and camcorder... why hasn't any htc desire developer ported his work? i would think it would be easier/more flexible than trying to port kernel 3.0 which seems to never be able to work completely because of lack of drivers.
yeahman45 said:
if you look at the htc hd2 forums, you will see everyone is using tytung kernel for their 4.0 to 4.2 roms as it has fully working 720p video playback, camera and camcorder... why hasn't any htc desire developer ported his work? i would think it would be easier/more flexible than trying to port kernel 3.0 which seems to never be able to work completely because of lack of drivers.
Click to expand...
Click to collapse
Maybe because making a working kernel 3 is more important than porting other kernels.
abaaaabbbb63 said:
Maybe because making a working kernel 3 is more important than porting other kernels.
Click to expand...
Click to collapse
i think we will never get a complete kernel 3 tbh as there's a lot of drivers not available..
It looks much easier/feasible to port Tytung work on camera/camcorder as the 2.x kernel of HD2 is very similar to htc desire's 2.x kernel..that would require less effort than trying to port kernel 3 (maybe i am wrong..) Qiss Rom and Tytung have been able to get a fully working camera/camcorder using kernel 2.x; so it is possible
at least i have been able to enjoy ICS with qiss rom and marius.a's rom (not a single issue to the major components : camera/camcorder is perfect, BT, GPS, Fm radio and all apps and games work great) ... i would have liked enjoying Jelly bean on my desire before changing phone next year
yeahman45 said:
i think we will never get a complete kernel 3 tbh as there's a lot of drivers not available..
It looks much easier/feasible to port Tytung work on camera/camcorder as the 2.x kernel of HD2 is very similar to htc desire's 2.x kernel..that would require less effort than trying to port kernel 3 (maybe i am wrong..) Qiss Rom and Tytung have been able to get a fully working camera/camcorder using kernel 2.x; so it is possible
at least i have been able to enjoy ICS with qiss rom and marius.a's rom (not a single issue to the major components : camera/camcorder is perfect, BT, GPS, Fm radio and all apps and games work great) ... i would have liked enjoying Jelly bean on my desire before changing phone next year
Click to expand...
Click to collapse
man you are wrong i have a second device (samsung galaxy5) and it has kernel 3.x working great and it's the only ARMV6 phone whit this kernel and if someone could do it for such a low end phone we can do it so don't worry we'll have our 3.x kernel
tcris45 said:
man you are wrong i have a second device (samsung galaxy5) and it has kernel 3.x working great and it's the only ARMV6 phone whit this kernel and if someone could do it for such a low end phone we can do it so don't worry we'll have our 3.x kernel
Click to expand...
Click to collapse
i mean apart from qiss rom team(unfortunately they did not released their source), no one has been able to get a stable camera/camcorder on kernel 2.x ... what makes you think with kernel 3.x it will be better and easier? and unfortunately there are very very few developers on the htc desire nowadays.. look at the android dev forum, it is quite quiet nowadays
yeahman45 said:
i mean apart from qiss rom team(unfortunately they did not released their source), no one has been able to get a stable camera/camcorder on kernel 2.x ... what makes you think with kernel 3.x it will be better and easier? and unfortunately there are very very few developers on the htc desire nowadays.. look at the android dev forum, it is quite quiet nowadays
Click to expand...
Click to collapse
out there are millions of devices whitout any dev and you complain about your phone whit A LOT of devs? if you want camera to full work stay on sense roms
yeahman45 said:
i mean apart from qiss rom team(unfortunately they did not released their source), no one has been able to get a stable camera/camcorder on kernel 2.x ... what makes you think with kernel 3.x it will be better and easier? and unfortunately there are very very few developers on the htc desire nowadays.. look at the android dev forum, it is quite quiet nowadays
Click to expand...
Click to collapse
Trust me, nikez and team are working on it. The xda thread may seem dead because of a bit of a mishap with a forum mod, but hes is still actively working and reporting his progress on his forum and on twitter.
chromium96 said:
Trust me, nikez and team are working on it. The xda thread may seem dead because of a bit of a mishap with a forum mod, but hes is still actively working and reporting his progress on his forum and on twitter.
Click to expand...
Click to collapse
i know he's developing and i am glad he is still continuing working on k3 ... i am just raising the question why no one ported tytung's work instead of working from "scratch"
tcris45 said:
out there are millions of devices whitout any dev and you complain about your phone whit A LOT of devs? if you want camera to full work stay on sense roms
Click to expand...
Click to collapse
i already have a working camera/camcorder with qiss/marius.a rom and it's ICS!
yeahman45 said:
i know he's developing and i am glad he is still continuing working on k3 ... i am just raising the question why no one ported tytung's work instead of working from "scratch"
Click to expand...
Click to collapse
It wouldn't work, because nikez uses ion now in his rom instead of pmem! With pmem and tytung's camera fix, which tytung already dicussed with nikez in nikez's thread, it would work, but nikez dont want to revert back to pmem
Sent from my HTC Desire using xda app-developers app