[Q] modifying kernel?! - General Questions and Answers

Hi,
my problem is, that HTC messed up their bluetooth-drivers, so I'm unable to pair a sixaxis-controller with my HTC Flyer on a sense-rom. Pairing worked great with a CM10-based JB. So I downloaded the HTC-kernel sources and the sources from the working-kernel.
But: What do I have to do now? I diff'ed all files in folders with "bluetooth" and there are'nt so many differences. Which files I have to replace?
BTW: Newer HTC-kernels support sixaxis-pairing (tested on ONE X), so is there any chance to port a newer HTC-kernel to my Flyer?
Well, sorry for this noobish questions, but I don't want to get rid of sense, but don't want to miss sixaxis-paring either and it seems, that there is no kernel for that. So it would be great, if I can build one "on my own".

As I heard, the kernel source code of the HTC One X is available, and on the One X sixaxis-bluetooth pairing works great (even with a sense-rom).
So is it possible to take these bluetooth-drivers and use it as a module on the HTC Flyer?
Thanks in advance
me113

Related

Development question

Has anyone tried to use the new Kernel from Rogers Rom , to make roms wich need to be ported work on NEw radio? Thanks
well from looking at it, no one else has been releasing anythign since 2.1 came out but klothius and i, so hmmmmm.......
Sorry i didnt explain myself. For instance, we have now a new HTC kernel. Can this be used to port Cyanogenmod rom ? I would like to see how it worked with the nwe HTC drivers
not sure it would go well, cause if you take a kernel from cyanogen and put in sense, not everythign will work, might not even start, so going the other way from sense to aosp i don't think but who knows, or you could try out new .34 kernel we released in froyorider today

Compiling from source for Sensation (TMOUS)

Hello everyone,
I'm trying to compile my own source ROM for my Sensation 4g (TMOUS) My HBoot is 1.17.000 revolutionary unlocked. My compile from google source gingerbread 2.3.4 (to match version htc is using) went ok however with no lunch or envsetup option for the Sensation my full-user make showed compiling for generic. I have tried fastboot flashing my compiled userdata and system img files to my phone along with my default sense kernel (kernel from TMOUS rom 1.5 made from clockwork recovery) to find that it doesn't get past the white htc screen. I'm interested in compiling and sharing this ROM with the public however finding I'm a little lost on next steps.
In the court of public opinion, what would my next steps be? Is my lack of booting due to the sense kernel and instead should I try using a kernel like trinity cm7/asop kernel? Is my lack of booting even kernel related?
Any advice I would greatly appreciated and once I can get this thing running I will be glad to give credit where due and distribute any modified files. Also, if I run across any additional information that might help anyone I will update this post.
PS - I know ICS is out and it might seem odd to try with gingerbread to start (along with using 2.3.4 instead of 2.3.7) however my rationale is that by trying to stay as close to the gingerbread rom HTC provides version wise I might have the best shot at compatibility.
Thanks everyone.
Various ROM developers have IRC channels. It might be worthwhile trying and asking a developer on there, just don't bug them too much.

Will Desire S to have custom ICS with sense 4.0 ROM?

I came across this site. http://www.engadget.com/2012/02/02/htc-sensation-puts-on-a-white-ice-coat-to-match-its-ice-cream-sa/
and it seems like the sensation will have an OTA update to ICS with sense 4.0. So, does that means that we will have a custom ROM base on that ROM? That will be awesome. Discuss.
UPDATE: ok, now I have a few questions for the developer. Since there are already so many ROMs on ICS with sense 3.6, but why there are non for our desire s ? Take a look at this ROM http://forum.xda-developers.com/showthread.php?t=1419278... there are more at sensation forum. Is it because of the drivers or hardware related? I'm not quite familiar with all these developing stuffs, so maybe the experts out there would enlighten to me? Thanks.
Firstly I am no developer but I think I can say some things about what you said. Yes it is hardware related like all linux based OS android has a kernel and the kernel is mostly written for a device specific hardware. And sensation and saga in that respect is no match so no part of it could be used in ours. And also there might be a need of lot kernel tweaks and for that rom to work. The derivative of sensation , sensation xl in retrospect is whole lot similar to our device so if a leaked rom is released for that one then I am sure devs will be able to do the things you wished. On top of kernel device specific hardware driver and all that the sense version as always by htc is a very special one as i understand cause its a whole lot different than any other rom. Looking through posts you might have seen sense kernels and aosp ones are different. So in the end to port that rom it will need a kernel drivers and all plus the effort to crack the sense overlay that htc slaps on anything too...
It might be not possible my heart strongly wishes for an ICS official rom as that would ease up a lot of things.
The HTC Desire S has a different screen, so the one leaked sense 3.6 (4.0) could only be ported to devices sporting the same screen. Be patient, HTC anounced that the Desire S will get ICS with Sense l8er in 2012. I'm sure the XDAdevs will be faster though....

[Q] Which rom is the best for my rooted phone?

Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
kostistheo said:
Hi, I have recently rooted my Desire S, with revolutionary, clockwork etc, and I currently ported this rom HTC_DESIRE_S_2.3.5-2.10.401.4.zip
Everything is working just fine, but theoretically, when I decide to port a new rom, how would I know which will work, and which won't?
Actually, I'm waiting until ICS is released for desire s, so I can find it and install it...
Are there any methods to identify which rom would be compatible?
Thank you!
Click to expand...
Click to collapse
hey mate
your're actually talking about two different things: porting a ROM and flashing a ROM.
Porting means, you take a ROM from another device and modify it so it works on your device too.
flashing means, you take a ROM which is already optimized for your device
and install it, so you wipe the stock firmware and get a custom rom.
which of the two things is what you want to do? i think its just the flashing.
so you can take any ROM from the "development section", and if you follow the guides that you can find everywhere here im sure you will be succesfull and happy with it.
bytheway
there is no "best" ROM for your device. it all depends on what you need and want. there are alot sense 3.5 Roms, Endymion 3.4 is the one i would recommend. you can also try AOSP ROMs (android open source project, means no sense), cyanogenmod7 could be a good first choice. and you can also try ics right now, since there are at least 3 (?) ICS AOSP ROMs right now:
CM9, Virtuous Quattro RC3, IceColdSandwich
have fun!
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
kostistheo said:
Yes I meant "flashing" a rom
Thanks for all the information. That's the general idea I have as well, however I had this question because after I flashed another rom (official rom through htc sync - that could have been the problem) over my first flashed one , the phone was "bricked"....
Click to expand...
Click to collapse
i would never recommend to flash an official ROM over a custom ROM. But anyways, i think if you would have done a full wipe before flashing the official rom you wouldnt have got a "you call it brick"
a real "BRICK" is a useless phone, where there is no way to use it again.if there is still a way, its no brick.. but who cares about definitions
I recommend you to flash the ROMs only through recovery mode. AND ALWAYS DO A FULL WIPE BEFORE FLASHING A NEW ROM. very important
and dont forget to backup as always
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Start flashing different roms and trying them for a day or two. First
Sens 3.0 and then sense 3.5 roms to see the difference. Only then you will know which rom is best for you.
+1 for Endymion 3.4,
+1 for Endymion
Swyped from my Desire S using XDA Premium
+1 Endymion
Sent from my HTC Desire S using xda premium
edymion, will try it
+1266592.23 for Endymion
kostistheo said:
Yes you are absolutely right. I'll have that in mind the next time I'll decide to flash a new one
Yeah the device wasn't completely useless, it hanged at boot...but I guess that was due to not following the right procedure as you previously described..
Thanks eyahl
Click to expand...
Click to collapse
Each ROM type suits different personal tastes, so there isn't an 'best' ROM for everyone. Trial and Error which ones suit you!
General opinions:
Stock
Pro: Straight from HTC, *newest kernel/drivers*, least likely to have compatibility issues.
Cons: HTC is slow to release updates, and sense interface is usually resource hungry.
Sense-like
Pro: usually keep the Sense interface, but custom kernals offer speed / various other improvements.Runnymead versions are kernals ported across from HTC Sensation (which offer some of the goodies like Beats Audio etc. that were not originally developed for Saga.
Cons: Sense interface is resource hungry...
CyanogenMod based
Pro: offer lots of customisations
Cons: not the most user friendly
AOSP
Pro: Roms from the android source, usually less resource hungry, so lighter and faster.
Cons: Obviously, no sense.
ICS Alpha/Beta
Not strictly a new category, but builds from the new Android 4.0 (ICS).
Currently some things (like camera) isn't fully working yet.
Note: new Desire S may suffer from camera/video lag bug with non-stock / non-sense ROMs, this is due to HTC putting in new hardware / driver into the new DS phones and the other kernels not reflecting this change yet.
Personally, I use SenseMOD Lite V1.2 build 2 as it is one of the few AOSP like builds that don't have the camera bug. Oxygen would have been best choice for me but unfortunately camera bug makes it unusable.
Hey guys. I don't want to drive over your feet, but I think the OP is already very satisfied with all those replies. specially the post above is really trying to help, but you spend much time to type what has already been written on the first page.
I appreciate your intend to help, bit I think the OP isn't gonna read this anymore..
Btw: endy!...
Sent by my fingers to your head

[Q] Understanding Kernel 2/3 and Android 4.X

Hello friends,
since i've bought my Desire S, i'm playing with CustomRoms and like to try new one's. So i'm not totaly unknown in this section. I know that we need the new Kernel 3 for get ICS working in our device. But yesterday got my wife her new phone, a Sony Xperia Ray (which is realy great, btw!). I've updated via SEUS (Sony Ericsson Update Service) to official Android 4.0 and saw, that this phone still use the 2.x Kernel, instead of 3.x! I'm just wondering about that and i'm a bit confused. Can anyone explain?
The second one is about compiling / creating a own kernel. I've saw in Desire Section, that they try to create a costum 3.x Kernel. And for Samsung S1, they are finished to create them and got many ICS Roms working. So, is it so much hard to create / compile a 3.x Kernel for our Device? Is it possiple to compile a Kernel from Kernel Source Code: http://www.kernel.org/ ??
Best greetings.
Bulkatos
Bulkatos said:
Hello friends,
since i've bought my Desire S, i'm playing with CustomRoms and like to try new one's. So i'm not totaly unknown in this section. I know that we need the new Kernel 3 for get ICS working in our device. But yesterday got my wife her new phone, a Sony Xperia Ray (which is realy great, btw!). I've updated via SEUS (Sony Ericsson Update Service) to official Android 4.0 and saw, that this phone still use the 2.x Kernel, instead of 3.x! I'm just wondering about that and i'm a bit confused. Can anyone explain?
The second one is about compiling / creating a own kernel. I've saw in Desire Section, that they try to create a costum 3.x Kernel. And for Samsung S1, they are finished to create them and got many ICS Roms working. So, is it so much hard to create / compile a 3.x Kernel for our Device? Is it possiple to compile a Kernel from Kernel Source Code: http://www.kernel.org/ ??
Best greetings.
Bulkatos
Click to expand...
Click to collapse
I'm not sure as to why the current devices with factory ICS or updates to it have kernel 2.6 (because I had the chance of playing with a one x and it had kernel 2.6) but the samsung galaxy s devs could make the kernel work because the exynos processor ( or as it was called back then hummingbird) is open source, unlike the snapdragon in our desire s. Also the original desire also had a snapdragon processor, which unless htc released the source, makes it almost impossible to make a custom3.0 kernel. We have kernel 3.0 on the DS because it was leaked and apparently it cannot be modified to work with vanilla ROM's(it only works with sense). So, I hope I cleared your misunderstandings as best as I could

Categories

Resources