Develop Bugs

flawless 2.1 on g1! bot still not on hero?

have a look at this, launcher 2 working perfectly
no softreboot efter 3d gallery to lancher2
and multitouch in 3d gallery :O
how come this work on g1, but not on hero?
http://www.youtube.com/watch?v=DxPLCq_pdCA

Because the G1's drivers are fully opensource and unfortunatly the hero's are copyrighted to HTC. This means we cant have em XD

xinos said:
Because the G1's drivers are fully opensource and unfortunatly the hero's are copyrighted to HTC. This means we cant have em XD
Click to expand...
Click to collapse
I don't think the launcher2 work on AOSP Roms

Also the G1 has a fully functional 2.6.29 kernel, while the Hero is stuck with 2.6.27...

gu1dry said:
Also the G1 has a fully functional 2.6.29 kernel, while the Hero is stuck with 2.6.27...
Click to expand...
Click to collapse
should be fixed soon... sanpei has done great things for the 2.6.29 kernel. We've got it running pretty damn well on radio 6.35 for the 32A hold on guys when he releases sources we'll all be set to do whatever we want

Phil_McRevis said:
should be fixed soon... sanpei has done great things for the 2.6.29 kernel. We've got it running pretty damn well on radio 6.35 for the 32A hold on guys when he releases sources we'll all be set to do whatever we want
Click to expand...
Click to collapse
32A? We're talking Hero, not Magic here!
Regards,
Dave

[DEV] Idea for using 3.0 Desire kernel - Attention Kernel Devs

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

Cm 9?

Will there be a cm 9 for the Inc? Because there is a lot of supported phones but not the Inc
I just need to flash something
Sent from my ADR6300 using xda premium

Try kushdeck's ROM, I'm running it and it works great.
Sent from my ADR6300 using xda premium

Kushdecks rom is pretty great. I ran the latest build for several days with no problem.

You guys both didn't answer the question, lmfao Are we getting dropped?

Technically there are no truly supported device for CM9 as they haven't even made any nightly releases. With that said, according to the official statement, QSD8250 devices (Nexus One, Inc, Evo4g) should be supported. That is planned but not definite.
http://www.cyanogenmod.com/blog/cm9-progress-update
Above is the official statement from CM. If you want CM9 support, CUViper is the CM maintainer for the Inc. Coming from a Galaxy Nexus user using AOSP, AOKP is a great ROM based on stock. CM9 is not really even ready on the GNex so I'd say they're still working on it. It's not as simple as a transition from froyo to gingerbread.

Evervolv ICS rom preview is better than omx and INC-Deck imo. I have a post on rootzwiki with everything you need, link to the rom, gapps and the exchange.apk fix

apophis9283 said:
Evervolv ICS rom preview is better than omx and INC-Deck imo. I have a post on rootzwiki with everything you need, link to the rom, gapps and the exchange.apk fix
Click to expand...
Click to collapse
Haha, maybe I should just follow you around apophis and keep giving a +1 to Evervolv ICS p5
But seriously, best ICS rom out there right now IMHO

Hey a good rom is a good rom. Im not bashing other devs but the rom is the most complete at the moment. Since he only post updates on twitter i post everything everywhere i can so more people can have this awesome rom

I used to be a hard core cyanogenmod user and I recently switched over to MIUI which will be coming out with v4 soon
I am much happier with MIUI.. give it a try..

jss24,
Is MIUI v4 based upon ICS? Is there some place that gives info about what can be expected out it. I would like see what they are cooking up.

yes there is a CM9 in the works. most of the ICS builds that are out now for the phone are repo'ed from CM source.

I don't know if CM9 will get inc support but the kushdeck alpha 5 has the camera working now; so feel free to FLASH AWAY!! eh, eh, see what he did there?

There is already a CM9 release out for the INC, but I'm assuming it's very buggy and it is missing some important apps.
Here's the link:
http://rootzwiki.com/topic/10750-romunofficialcm9-with-working-hardware-acceleration/
Be sure to check further down the page for another download that's required in order to boot it up.

Not really a release more along the lines of a port. I dont believe it will have any more support

nope R2 pulled repo from cm so its not a port. they are work on it. we still have one maintainer left. CUViper. i have faith in him.

First line in r2s post says , so i ported cm9 to the inc earlier to see if hardware acceleration worked

Why would he say that if it wasnt a port?

Likely to be a port only, but that's where most of our great ROMs come from. These are called AOSP for a reason...
On another note, CCM7 (V10) is a great ROM to hold you off until ICS hits us in February, oops did I drop dates?
Oh well, I was going to post pictures of my setup, but I guess I am too new.

What is ccm7 v10? Where can it be found

Condemned cm7, ill pass

Wimax on ICS

Quick question for those who understand more about the kernel than I do.
Why doesn't WiMax work on any of the new ICS builds. I thought the benefit of TeamWin writing the wimax implementation from scratch was we have the source and can tack it into anything. If the ASOP kernel has been released, what is keeping us from plugging in the WiMax bits and complining?
I understand that many of the driver sources are held by HTC and won't work until they release their ICS code. I just thought WiMax would be the first thing that would be implemented.
Thanks

It takes time, and since the code hasn't been released, they have to get it from scratch and test it out until it's nearly perfect. Just be patient.

I'm in no rush, this is just out of sheer coding curiosity.
I thought ICS code was released by Google and the WiMax code was written by the TeamWin guys? If both of these are available what else does it take to get it working?
My only guess would be that google releases a vanilla kernel. We need and Evo ICS kernel, and the source for that kernel has not been released? If that is true, what kernel are current ICS builds using? Anyway, I'd be interested to hear how this all works.
Thanks

amw2320 said:
I'm in no rush, this is just out of sheer coding curiosity.
I thought ICS code was released by Google and the WiMax code was written by the TeamWin guys? If both of these are available what else does it take to get it working?
My only guess would be that google releases a vanilla kernel. We need and Evo ICS kernel, and the source for that kernel has not been released? If that is true, what kernel are current ICS builds using? Anyway, I'd be interested to hear how this all works.
Thanks
Click to expand...
Click to collapse
I think ics builds are using tiamat 4.0.1 kernel

Interesting. I guess that would mean it is supported in the kernel, but the networking connections have yet to be written into the OS then. Thanks for the info.

[Q] why has no developer ported tytung's kernel to htc desire?

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