I would like find the freshest available 3.0 kernel for the Desire Z. Where is it hosted? My intention is to make a kernel more stable than others available, as all are undervolted, and unfortunately with those settings I am experiencing random reboots. I've found some sources, tuned voltages to the original ones (as in htc's 2.6.35 kernel), and the reboots disappeared.
Thanks in advance,
The Andromadus 3.x kernel and cn.fyodor's are the most recent, I might say fyodor's might be slightly ahead being as he is the Andromadus kernel guy and his kernel stuff which goes into his ROM probably gets merged into Andromadus later (or maybe he does entirely different things for each, I'm not sure, you'd have to ask him).
By the way if you manage to get either of the above up and running, I'd appreciate some help as I've been trying to compile the Andromadus kernel but have so far not been able to produce a zImage, although compilation seems fairly smooth .
And are these kernel for sense? I always read on forums that there are kernels for sense roms, but actually I dont know the difference.
Last time I compiled from github / ajhavery / htc7x30-3.0.git, and it compiled well for me.
Then two linked to you by htcdreamon are for aosp/cm/aokp etc, you are right that you can not interchange aosp kernels and sense kernels, by and large they are not compatible
Sent from my Nexus 7 using xda premium
Related
Hi guys,
it's my 1st thread started at xda, so if it's in wrong place or anything, let me know and i'm sorry.
As I'm not a developer myself I just follow up stuff here to see all u guys good work... but when I saw this news and noticed that it's not here... I'm sure some of you can make good use of this info.
HTC release the source code for Hero (and some others) on their developer centre, it seems like a straight download which should help the devs get nicer drivers (Froyo ???) and smoother running ROMs.
news via: http://www.androidcentral.com/htc-developer-site-updated-kernel-sources-evo-4g-and-htc-hero
HTC dev site: http://developer.htc.com/
Optimized HTC Sense UI coming?
Go go devs.
Nothing new though. At least not for Hero benefits anyhow.
We've had hacked together kernel sources for 2.6.29 for a while now, so this isn't as big a deal as the original kernel source release. Hopefully the devs here can still make use of it.
Hi
nothing really new ?
IIRC, "Github for the untouched original kernel source: hxxp://github.com/toastcfh/CdMa-HeRoC-2.6.29" is another device kernel src reverse for the Hero from a forgotten patch file in the archive ?
so this "really" original kernel source may be newer with last correction from htc ?
thx help me understand
Az'
from what I understand (After a bit of toying with toast's kernel sources myself) this is what's done:
(correct me if wrong):
They took a supplied 2.6.29 kernel source as the base. Don't know if it's from Nexus, Desire or Legend, but some anroid-2.6.29 base kernel that was already available.
Already having a 2.6.29 base with most HTC-ish hardware available, the hard part was merging in all the cpu centric files (board files, for the MSM720x platform) from the already released 2.6.27-htc sources.
So starting with a htc-ish 2.6.29 base, and slowly and trial-and-error moving stuff over from the 2.6.27-htc sources (which is harder than it looks. 2.6.27 -> 2.6.29 had quite some changes in the linux world) until it boots and until all hardware worked.
He did this for the CDMA hero. From there it wasn't too long (or did it work directly?) until it worked for the gsm hero. Someone just had to notice his work I believe .
_So_, that means that our 'godmode-2.6.29' sources aren't really 'hacked together' that much. The support files are still from HTC, only they are the same as the 2.6.27 (android 1.5) drivers. _Maybe_ HTC updated or optimized some things and thus the official-2.6.29 might contain newer or better working support for the hardware.
The way to check this is out is to compare the **** in the source files (which people are probably doing already) to see the differences HTC did to toast's version.
The other method is to 'try' and feel what's different. This _never_ works in the XDA community because there is a _huge_ placebo effect in what all the users are feeling. The same as compcache, swap, bfs or not, etc... opinions and preferences are all over the place.
Only if benchmarks or other hard numbers make one version better than the other, it remains something of preferences for the users and creators of the roms.
(Is there already a simple recompile somewhere with overclocking enabled of the HTC 2.6.29 sources? Because then the testing can begin ).
so no current roms are built from the official kernel (the 2.6.29 kernel from HTC)?
As far as I can understand the GoDmOdE kernel sources are based on a leak of 2.6.29 kernel sources for multiple HTC devices, including a CDMA hero kernel source. And the sources for all our 2.6.29 GSM hero kernels are based on this.
The official 2.6.29 are very new, but I am sure that now that they are released we will see kernels based on these sources as well.
There are quite a few ROMs available, but one thing is not entirely clear to me. Why aren't there any clean AOSP ROMs for the Wildfire? I can understand it would be difficult to develop newer Android versions like Gingerbread that were never officially released for the Wildfire, but wouldn't it be relativly easy to compile a working ROM from the 2.2/2.2.1 source code? Or am I completely missing the point here?
It seems to me all the materials are available to pull this off without too much effort, right? The Kernel source is available from HTC and the Froyo source from our friends at Google.
From what I understand there are also some vendor specific issues that need to be solved, but the Cyanogen developers apparently have this solved already.
That pretty much covers everything right?
So my question would be, is it possible to easily build a clean version of Froyo for the Wildfire by doing the following:
1. Grab the kernel source from HTC and compile it (or just fuse a pre-compiled one seeing as there are quite a few available).
2. Compile the Android 2.2/2.2.1 source
3. Apply vendor specific fixes (assuming they don't have to be incorperated in the code directly).
4. Flash kernel + ROM, thereafter Gapps
5. win?
Basically something like Openfire without bugs. Which reminds me, wouldn't the video recording/SIM card issues be fixed with the official HTC kernel? In which case, I see little reason to try and compile the stuff by myself.
Ah well, I really really hope someone can enlighten me on this subject.
TL;DR: I want to create a basic a clean AOSP Froyo 2.2/2.2.1 ROM which should be easy right because we already have the required materials (proper HTC kernel -- or third party one, 2.2/2.2.1 source, cyanogen vendor fixes), so compile = good to go?
there are
- Wildmix http://forum.xda-developers.com/showthread.php?t=1155032
- CM6 http://forum.xda-developers.com/showthread.php?t=822132
- Utmost http://forum.xda-developers.com/showthread.php?t=862561
- Openfire - http://forum.xda-developers.com/showthread.php?t=783024
more here (scroll down) http://forum.xda-developers.com/showthread.php?t=1029318
There is always CM7
Remember you use these at your own risk
Thank you for your reply, but it doesn't really address my questions. I am aware of the custrom ROMs available, none of them really meet my demands.
Cyanogenmod is an excellent ROM, but CM6 has some issues and CM7 is based of Gingerbread.
Utmost and Wildmix are both based on Openfire. The problem with Openfire is that it has a lot of internal stuff I don't really like. Seeing as Utmost and Wildmix are based on it those don't really float my boat either.
My eventual goal would be to create a clean AOSP like this one:
http://forum.xda-developers.com/showthread.php?t=1162656
Unfortunately it's based on Gingerbread and not fully functional (yet!).
That is why I asked the questions that I asked. I'd rather do it myself from scratch, but in order to do any work I could really use an answer to my questions
Thanks anyways.
Trademark225 said:
Thank you for your reply, but it doesn't really address my questions. I am aware of the custrom ROMs available, none of them really meet my demands.
Cyanogenmod is an excellent ROM, but CM6 has some issues and CM7 is based of Gingerbread.
Utmost and Wildmix are both based on Openfire. The problem with Openfire is that it has a lot of internal stuff I don't really like. Seeing as Utmost and Wildmix are based on it those don't really float my boat either.
My eventual goal would be to create a clean AOSP like this one:
http://forum.xda-developers.com/showthread.php?t=1162656
Unfortunately it's based on Gingerbread and not fully functional (yet!).
That is why I asked the questions that I asked. I'd rather do it myself from scratch, but in order to do any work I could really use an answer to my questions
Thanks anyways.
Click to expand...
Click to collapse
Have news for you
We are currently working on a ROM with the aosp ROM you linked as base ...
Stay tuned
Sent from my HD2 using XDA Premium App
He meant a AOSP Froyo, no Gingerbread ;D
nejc121 said:
He meant a AOSP Froyo, no Gingerbread ;D
Click to expand...
Click to collapse
Got that after posting that
But gingerbread is much better than froyo and compatible to nearly all apps you can have
Sent from my HD2 using XDA Premium App
Anyway what's wrong with gingerbread??
I figured since 2.2.1 is the last available official version released it would be easier to get all hardware functioning properly. But if those new ginger AOSP projects fix the video recording bugs and get everything else fixed, ill gladly switch to it. Maybe ill use xdbg's (spelling?) ginger aosp as a base as soon ss the bugs are fixed.
Sent from my HTC Wildfire using XDA App
skeevy420 may ported this rom, because it seems very stable and would be fantastic for all users of the Motorola Bravo
you are very good for ported rom
Link http://forum.xda-developers.com/showthread.php?t=1161110...:D
mataflakitas said:
skeevy420 may ported this rom, because it seems very stable and would be fantastic for all users of the Motorola Bravo
you are very good for ported rom
Link http://forum.xda-developers.com/showthread.php?t=1161110...:D
Click to expand...
Click to collapse
I tried once a few weeks ago, but gave up after 15 minutes of zip editing and a bad flash....didn't bother any further cause Quarx started droppin CM9\7 releases the second I had installed CM7.
I may try again (with actual effort this time), but I've been looking at porting the DroidX Miui v4 and am more interested in doing that to be honest.
I also attempted patchrom with Quarx's latest CM9, but didn't get anywhere. Doubt I will either since I don't know smali code, or anything more than basic bash scripts.
Not at all related, but thinking about it, I will post a zip containing the DroidX cpu governors this evening, they work great with CM9. My bad battery (CM9 05\12) has been with using the stock conservative setting. Using stock settings with DroidX BOOSTEDassV2 governor gave the best battery I've had (all roms) with CM9 05\09 and 05\06.
Hello all,
First of all, sorry for posting in the wrong forum, but I cannot post in the development one, so forgive me.
I have a question for all of you:
I have installed on my HTC Desire the Nikez Lente Evervol JB ROM, which is great.
I really like it, even if there are few bugs and random FC.
I've used CM7.2 for a long time before to switch to JB.
I don't miss CM (sorry for that), but I really miss Tiamat Kernel I installed within it, which helped me overclock and underclock my processor, changing also the voltage.
With Nikez Lente JB original kernel this is not possible, I tried to install Tiamat Kernel for ICS but the phone cannot boot anymore, I'm stuck to initial black screen.
So I went back to the original Nikez Kernel.
Unfortunately this kernel seems do not allow "extreme" overclock as Tiamat does, and do not allow the user to change the voltage table.
I would really like to have these features back on my JB installation, is it possible?
Is there a kernel which can work with Nikez JB ROM and can give me back the features I'd like to have?
Moreover: can you explain why the Tiamat ICS kernel (for Bravo GSM) does not work with both Nikez Lente ROMs (ICS & JB)? Am I making something wrong?
My phone is a PVT-1 Amoled, S-OFFed qith Revolutionary, the HBOOT is the Alpharev Stock one, The recovery is CWM 5.0.2.0, I have a 32Gb SD card with 1 Gb ext3 sd-ext partition.
What else can I say?
Thank you very much in advance.
Regards,
Giovanni
Yes it is possible.
But probably you have to wait.
Evervolv team (nikez included) are working on jb and probably when all features will be working they add some mod in kernel that will let you OC CPU.
Sent from my HTC Desire using xda app-developers app
Did you check/compare the kernel configs? One of the CM wiki pages about building the kernel describes howto access the config - or check the git repos, evervolv has the file somewhere in arch/asm, it is called bravodefconfig IIRC
Maybe a device or filesystem driver is missing
jhl80 said:
Did you check/compare the kernel configs? One of the CM wiki pages about building the kernel describes howto access the config - or check the git repos, evervolv has the file somewhere in arch/asm, it is called bravodefconfig IIRC
Maybe a device or filesystem driver is missing
Click to expand...
Click to collapse
Almost, it's located in arch/arm/configs/evervolv_bravodefconfig
I have seen to many kernel threads and none of them seems to say that the kernels are safe to use with the JB leaks.
I really don't see why they shouldn't, but I really wanted to be sure.
have anyone used a Franco, faux or similiar present kernel with the new JB leaks from Insert Coin or ARHD?
Do we have to repack them to be fine?
I know that kernel version should not be a problem, but we only have source code for the ICS kernel based in 2.6.X and the new kernel is 3.0.X
So I wanna know real experiences if possible
Thanks,
Santroph.
Hi, i have tried repacking a few of them as im keeping a list up together for the maximus thread but none of the linux 2 kernels have worked yet, will try trips kernel when i get round to it this week but it says no support for sense so probably a no go. I havent seen anything new yet but will keep my post updated as and when (link in my sig) they should work for other jb sense 4+ roms too :good: