Develop Bugs

Simplistic HTC Hero Kernel Question.

Hi All,
Running rooted Hero with Modaco 2.5.1 rom ( thanks Paul )
Was hoping someone could ( simplistically ) answer a few question for me.
As I understand it - one of the things holding back development of Hero ROMS is that HTC haven't released the kernel for the Hero.
1) What exactly IS the kernel in the greater scheme of things?
2) When are HTC likely to release it?
3) When it is released, what new things will it allow developers to do?
4) Anything else relevant to it worth knowing?
TIA

Look at these:
1. The kernel is the Operating System for the phone, it runs everything.
2. That is the magic question...
3. It'll allow more development in terms of mods. we'll be able to change alot more and get more out of the phones.
I'm sure others will have more detailed explanations.

Regarding question 2:
I've gotten response from HTC support the other day that the release is planned but no sure date could be given.
Date: 5th of October
My question:
Hello there, I realize that this might not be the normal kind of request you guys get, but here goes. This is probably not your average request and might require escalation. I was wondering when the source code for the Hero kernel was gonna be available at developer.htc.com?
Click to expand...
Click to collapse
Answer:
Hello
This is quite a normal question we get here at HTC. The source code is something that will becoming soon. We have had contact with those far higher than my self or are planning on adding the source code as soon as possible. I have not been given a time scale but bases on the code for the two other handsets i should expect it in the next couple of weeks.
Hope this helps.
Click to expand...
Click to collapse
So, educated guess would be around the release of the Hero in the US.

Some if I have this right -
The kernel is the basic underlying OS of the phone, and a ROM sits on top of this end gives us the end user experience ( and Sense UI is within the ROM ).
Am I right in thinking the kernel is linux based?
And a big magic question - when the kernel is released, will people be able to modify it and get the bluetooth working properly?
Sorry if it's a bit basic - but interesting to me....

The Kernel is not the OS (As most people understand an OS to be) (OS meaning Operating System)
It's at the core of the OS but is not the OS. You can keep the same build of an OS but update the kernel and vica versa. It is (put simply) what converts the hardware calls from the OS into something the hardware understands.
So (using current issues as explanation) The OS tries to load the GPS and the kernel isn't configured with the right settings the GPS won't load. Similarly if you try and use the trackball and it's not setup in the kernel then it won't do anything.
The OS will still work fine with other things but until the kernel has the right settings put into it it just won't see the parts of the phone it's not set up to.
Here is a technical description of a Kernel.
http://www.linfo.org/kernel.html
I'm sure I've just made it as clear as dishwater but if not I hope it's helped.

J-Zeus said:
Some if I have this right -
The kernel is the basic underlying OS of the phone, and a ROM sits on top of this end gives us the end user experience ( and Sense UI is within the ROM ).
Click to expand...
Click to collapse
Not exactly. To add to what akirainblack has said already...ROM stands for Read Only Memory. In this context it is a bit different as it is the complete package that makes up the Kernel, the OS and anything that is pre-installed to the phone. When you run the RUU (Rom Update Utilitiy) on your PC is completely refreshes the system software in your phone - Kernel, OS and any pre-installed apps - just as if you had bought it from the shop like that.
J-Zeus said:
Am I right in thinking the kernel is linux based?
Click to expand...
Click to collapse
Yes.

Hmmm...
simple question... when the kernel is available... would we be able to get a white taskbar on the Hero?
//Nik

When the kernel source is available, we should be able to rebuild Android completely from the source code repositories and do practically whatever you want.
Regards,
Dave

foxmeister said:
When the kernel source is available, we should be able to rebuild Android completely from the source code repositories and do practically whatever you want.
Regards,
Dave
Click to expand...
Click to collapse
Including getting Bluetooth working?

J-Zeus said:
Including getting Bluetooth working?
Click to expand...
Click to collapse
In theory, yes. In practice, the situation is a little more complicated, but at the very least I'd imagine it would be possible to get BlueX, or something like it, working on rooted Heros fairly quickly.
Regards,
Dave

Given that this is a Linux kernel, aren't HTC required by the GPL to make the source available to all Hero owners?

This is covering the same ground, but is another way to look at things regarding the kernel and the OS. The kernel abstracts the specifics of the hardware from the Android system. For example, when the Android system requests that the bluetooth hardware be enabled, the kernel can translate that request so that it works with the particular hardware of the phone - as the bluetooth hardware of the Magic may be different from the bluetooth hardware of the Hero. So the kernel, is an interface that translates and Android call to the specific hardware level controls necessary. The kernel sits between the hardware and the Android system.
It also means that releasing the kernel will not allow us to make changes to the Hero Android user interfaces. If we want to change colours, icons and so on in the Hero ROM, we would need the source code for their "tweaked" Android and maybe to some degree their TouchFlo software. I doubt they would give that away. It would allows us however, to tweak the kernel, or transplant the driver code for specific hardware pieces in the Hero, to a newer version kernel.

I understand that the release of the hero kernel, could help me with my cause (getting 1.5/1.6 'clean' android on my hero without any htc apps/front ends).
Somebody suggested contacting HTC and asking for it to be released.
I have a few questions regarding that:
1) Has this happened before? That HTC released an android kernel?
2) Did this happen after the request?
3) Who should we contact to get it? (which HTC division)
4) Is there a possibility that they don't want to release it, because it would allow people to copy parts of the proprietary interface?

E2K said:
1) Has this happened before? That HTC released an android kernel?
Click to expand...
Click to collapse
Take a look at http://developer.htc.com/
The Dream and Magic sources are available.
E2K said:
4) Is there a possibility that they don't want to release it, because it would allow people to copy parts of the proprietary interface?
Click to expand...
Click to collapse
The HTC Sense UI won't be included in the kernel source.
They dont have to release the source of them.
New question
Is it possible to create a new donut kernel (2.6.29) with the changes they made to the 1.5 kernel (2.6.27)?
Looks like they send you the hole kernel, not just some patches and new drivers...

mopodo said:
Take a look at http://developer.htc.com/
The Dream and Magic sources are available.
Click to expand...
Click to collapse
So this means that we could compile or 'cook' a working vanilla android 1.5 for the HTC hero, with everything working fully?

HTC HAS to release the kernel source as required under the GPL license that the kernel was released under. It is indeed a linux kernel and it contains the necessary parts to work the hardware along with extra drivers and modules (stupid monolithic kernels).
Here's what I don't get (and hopefully somebody will clarify this for me). Why hasn't anybody tried building android with the current kernel available? Android has the ability to be built around a pre-compiled kernel (it does this if you do a straight make right after repo sync with the pre-compiled dream kernel). You'd only need to re-build the wlan.ko module for the new kernel and the gps module would be compiled against the specified kernel, so it should work.
If I had Hero, I'd test it (if you want to trade your Hero for my G1, hit me up ), but there's no reason it shouldn't work.
Up to now, I've only seen ports, and those are hard to make work because of the pre-compiled files, so that leads to loads of file-swapping and finger-crossing, but an AOSP make should still work. Anybody wanna try it (or post me a hero kernel and I'll compile you a stock donut build to test).

jubeh said:
HTC HAS to release the kernel source as required under the GPL license that the kernel was released under. It is indeed a linux kernel and it contains the necessary parts to work the hardware along with extra drivers and modules (stupid monolithic kernels).
Here's what I don't get (and hopefully somebody will clarify this for me). Why hasn't anybody tried building android with the current kernel available? Android has the ability to be built around a pre-compiled kernel (it does this if you do a straight make right after repo sync with the pre-compiled dream kernel). You'd only need to re-build the wlan.ko module for the new kernel and the gps module would be compiled against the specified kernel, so it should work.
If I had Hero, I'd test it (if you want to trade your Hero for my G1, hit me up ), but there's no reason it shouldn't work.
Up to now, I've only seen ports, and those are hard to make work because of the pre-compiled files, so that leads to loads of file-swapping and finger-crossing, but an AOSP make should still work. Anybody wanna try it (or post me a hero kernel and I'll compile you a stock donut build to test).
Click to expand...
Click to collapse
Hi, thank you for this information. You make it sound like it's possible
I tried searching for the Hero Kernel, but I could only find this:
http://developer.htc.com/
The hero is not listed (maybe it shares a lot with the magic kernel?).
edit: this post dating from september 10 stated that HTC would "release the kernel source soon".
This was more than a month ago though..
edit2: calling HTC Netherlands right now..
edit3: after explainig the need for the kernel, I've been on hold for 10 minutes now..
edit4: more than 18 minutes now
edit5: after 26 minutes I hang up

Well I have a Hero running Modaco 2.2. I could post this kernel (where?) Or it surely could be extracted from one of the ROMs available on this very site

SquiffSquiff said:
Well I have a Hero running Modaco 2.2. I could post this kernel (where?) Or it surely could be extracted from one of the ROMs available on this very site
Click to expand...
Click to collapse
I could be wrong, but I believe there is a difference between the 'kernel', and the 'kernel source'. The second one is needed when you want to compile the kernel.

Speaking as one who has compiled kernels in the past there are three components required here:
The kernel source- this is typically available from http://kernel.org/ If HTC have made any changes to the source of the kernel itself then these should be apparent in their distribution of the kernel source
The relevant configuration file '.config' which should accompany their distribution of the kernel source and permit you to compile any other kernel as a drop in replacement.
Source code and makefiles for any custom kernel modules ('drivers' in windows terminology) In Linux these have to be compiled together with the kernel.
To use a cookery analogy:
The kernel source is the raw ingredients. It can be set up for anything from a supercomputer to a DVD player depending on how you use it. The kernel config is the method which will allow you to bake the type of cake you intend. The modules sources are any of HTC’s own custom ingredients required for everything to work. THe kernel is the finished cake which you eat.

[DEV] 23/10 1.2 - MCK - Playing with custom kernels (for the brave!)

As you may know, HTC have just released the kernel source code, and i've been having a play.
Nothing massively exciting yet, but if you want your kernel to feature...
- Additional filesystems (EXT4, NFS, CramFS, SquashFS 4.0)
- Freshly compiled tun.ko module
- CompCache 0.5.4 support
- Required iptables functionality for DroidWall
...then you can install this package over the top of the latest MCR.
This is pretty much untested at the moment, so Nandroid backup first (of course), and i'm taking requests for future improvements. This is seperate from the main MCR thread for now simply because of it's untested nature!
I'd like to add...
- Port to 2.6.29 kernel
...but as I say this is just an early first-stab at a custom kernel. I thought i'd put it out there as I know many people like to run EXT4 on their A2SD partitions.
Download: MoDaCo
Enjoy!
P

Changelog
1.2
Added DroidWall support
1.1
Internal (non public) Test Release
1.0
Initial Release

Added source download.
P

We could look into Bluetooth OBEX file transfers now...

oblika said:
We could look into Bluetooth OBEX file transfers now...
Click to expand...
Click to collapse
http://code.google.com/p/androidobex/source/checkout

Version 1.2 up, added DroidWall support.
P

MCK 1.2 is now rolled into MCR 2.8. This thread will remain as the test bed / source code post.
P

good going Paul.

Good work Paul ,I apriciate your hard work. You are our HERO.

gangstaunitg said:
Good work Paul ,I apriciate your hard work. You are our HERO.
Click to expand...
Click to collapse
Bump - i second that!

MasterOfDesasters said:
Bump - i second that!
Click to expand...
Click to collapse
I have to third that.

modaco said:
As you may know, HTC have just released the kernel source code, and i've been having a play.
Nothing massively exciting yet, but if you want your kernel to feature...
- Additional filesystems (EXT4, NFS, CramFS, SquashFS 4.0)
- Freshly compiled tun.ko module
- CompCache 0.5.4 support
- Required iptables functionality for DroidWall
...then you can install this package over the top of the latest MCR.
This is pretty much untested at the moment, so Nandroid backup first (of course), and i'm taking requests for future improvements. This is seperate from the main MCR thread for now simply because of it's untested nature!
I'd like to add...
- Port to 2.6.29 kernel
...but as I say this is just an early first-stab at a custom kernel. I thought i'd put it out there as I know many people like to run EXT4 on their A2SD partitions.
Download: MoDaCo
Enjoy!
P
Click to expand...
Click to collapse
I'd love to help test this however I'm new to Android so when you say MCR I assume you mean the latest Modaco Rom? So I should install MCR then install this? Sorry and thanks, looking forward to giving it a go
will this have CDMA support by any chance for the CDMA hero?

jman069 said:
I'd love to help test this however I'm new to Android so when you say MCR I assume you mean the latest Modaco Rom? So I should install MCR then install this? Sorry and thanks, looking forward to giving it a go
will this have CDMA support by any chance for the CDMA hero?
Click to expand...
Click to collapse
The MCK kernel was added to the custom ROM in version 2.8, so if you want it all you have to do is install the MOdaco ROM 2.8

Well may be it is possible to make clean Android OS available for HTC Hero since kernel sources are released? With no Sense UI etc.

NoXXX said:
Well may be it is possible to make clean Android OS available for HTC Hero since kernel sources are released? With no Sense UI etc.
Click to expand...
Click to collapse
There seem to be more and more people expecting that

all our hopes r on the devs. only they can provide us something. good job guys. keep it up.

*sorry. double post*

No sense UI..................Slightly off topic
frandavid100 said:
There seem to be more and more people expecting that
Click to expand...
Click to collapse
I dont understand all the people not wanting sense UI
if you dont want it, go into settings--------manage applications-----find touch flo and clear defaults....
The next time you press the home button, just press launcher and make it your default home screen.
There you have it...
Sorry Paul for going slightly off topic

Some people do not want it because they find it heavy.
By using the clear defaults method you only visually disabling it, but in the background the sense ui processes are still running.

ZenorGR said:
Some people do not want it because they find it heavy.
By using the clear defaults method you only visually disabling it, but in the background the sense ui processes are still running.
Click to expand...
Click to collapse
Ever heard about Paul's Rosie remover? I think what people want is to get features of e.g. Cyanogens work in a ROM, and the ability to modify. In fact if you remove Rosie, add some vanilla android apps and change the Hero drawables in the framwork.apk you'll get a "vanilla" looking and working kind of ROM.

[ROM][2/10/11] NO SENSE: HTC Vision G2/Z MoDaCo Custom ROM with Online Kitchen (r2)

I'm pleased to present my MoDaCo Custom ROM for the HTC Vision (this is the version based on the T-Mobile G2 ROM, without HTC Sense)! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know.
Remember that if you use this ROM, you do so entirely at your own risk!!
About MoDaCo Custom ROMs
MoDaCo Custom ROMs are based on official ROMs - either shipping or leaked. A MCR release is designed to feel as far as possible like a stock ROM, with optimisations, tweaks and complimentary additions that enhance the user experience. The aim of a MCR is to be ultra reliable for use on an everyday device.
Requirements
In order to use this ROM on your device, you must have a custom recovery image installed (Clockwork Mod).
THIS ROM SHOULD RUN ON BOTH THE G2 AND THE DESIRE Z!
Features (these are the features for the currently posted prebake, please check the changelog for any pending changes that are in the kitchen)
Based on the 1.22.531.8 T-Mobile G2 ROM
Pre-rooted with su and Superuser Permissions by ChainsDD
Insecure boot image (ro.secure=0)
Optimised with the MCR build process, which means that the ROM will fit on a G2 without needing to remove any content!
All components updated to the latest versions
ROM is de-odexed
Please note that this is a r1 release, many more changes will be added now via the kitchen and periodically updated prebakes (as per normal MCR builds!)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card
Restart your device in recovery mode
PERFORM A NANDROID BACKUP FROM THE MENU
Select the option to apply an update zip, and select the zip file you copied to your memory card
Upgrading
No wipe is explicitly required in order to use this ROM, however if you do encounter issues of any kind, it is recommended that you wipe your device and reproduce the issue before raising it here.
Downloads
This ROM is now available in the online kitchen! In addition to the kitchen, a prebaked download is available.
DOWNLOAD
Thanks
It's impossible to mention everyone who contributes to the Android community by name, but to everyone out there who does great work and shares it with us all - you have my gratitude and respect.
Future Updates - READ THIS!
By providing this ROM I am not implying in any way that future updates will follow. Due to limits on my time and the fact that I have a large number of devices for short periods of time, it isn't possible for me to continue providing ROM updates indefinitely. Please do not donate / sign up on the assumption that future releases will be available (I don't want you to be disappointed!).
And finally...
Details on how to donate should you wish to do so are in download topic at MoDaCo.
Enjoy!
P

Changelog
r2 10/Feb
Reoptimised - smaller, faster!
Updated all outdated components
r1 16/Nov
Initial Release

This is the first release of the ROM - I will start dropping in the usual MCR features quickly going forward (via the kitchen first as usual, periodically building prebakes).
P

Why doesn't the stock sense image fit without optimization? They are the same phone
Sent from my T-Mobile G2 using XDA App

Flippy125 said:
Why doesn't the stock sense image fit without optimization? They are the same phone
Click to expand...
Click to collapse
Same phone but different partitioning, I believe ? I'm sure someone who knows a lot more than me will be able to comment better though.

Stock G2 does fit on Z, but the other way round doesn't.
What he said - different partitioning!
P

wheres the download link? I am getting a 403 on your page??

how does this compare to CM6? i'm a fan of Modaco and Cyanogenmod and i would like different opinions on both

No OC Kernel with this ROM?
** Update: I just flashed the BaconBits 0.3 and all is good baby!

whats the user space, you know whats free for apps and what not

is anyone gonna make a stock rom with a black status bar or explain how to do it

shibby80 said:
is anyone gonna make a stock rom with a black status bar or explain how to do it
Click to expand...
Click to collapse
look into metamorph

CM6 has an option for a black status bar

Ciborg54 said:
CM6 has an option for a black status bar
Click to expand...
Click to collapse
ive tried a few roms now and the wifi seems buggy thats why i was looking for a stock one i need my wifi calling lol

shibby80 said:
is anyone gonna make a stock rom with a black status bar or explain how to do it
Click to expand...
Click to collapse
Sent from my T-Mobile G2 using XDA App
In cm6 go to the cyanogen settings/theme settings/ stock black

kpoeticg said:
Sent from my T-Mobile G2 using XDA App
In cm6 go to the cyanogen settings/theme settings/ stock black
Click to expand...
Click to collapse
wanted to stay with a stock rom

paulobrien said:
This is the first release of the ROM - I will start dropping in the usual MCR features quickly going forward (via the kitchen first as usual, periodically building prebakes).
P
Click to expand...
Click to collapse
I'm sorry, but I am just surprised no one has mentioned or requested screenshots.
Can we get at least one? I mean some of us may not know what a Non-Sense UI looks like.
Also, will this ROM help extend battery life? I am assuming it will with less eye-candy correct?
Thank you.

apueb008 said:
I'm sorry, but I am just surprised no one has mentioned or requested screenshots.
Can we get at least one? I mean some of us may not know what a Non-Sense UI looks like.
Also, will this ROM help extend battery life? I am assuming it will with less eye-candy correct?
Thank you.
Click to expand...
Click to collapse
Its a stock ROM base nothing special nothing out of the ordinary. I am using it right now, it runs smoother than stock.

~~Tito~~ said:
Its a stock ROM base nothing special nothing out of the ordinary. I am using it right now, it runs smoother than stock.
Click to expand...
Click to collapse
Ok, so what does NO SENSE mean?

So, is that a no on the screenshots?

[App] 2BOrange - Install any kernel (Voodoo, SpeedMode, Infusion...) without computer

____________________________________
2BOrange
____________________________________​
Hi everybody,
I have made a free application to install any kernel on your SGS very easily.
The idea is that there is a website where kernel are uploaded with a script and an application to:
- search
- download
- install it on your phone.
The application and the website are not limited to install kernell but I think it is a good way to try it.It can execute any script in the android shell.
So I have made some script for some kernel, there are so much that I have not the time to make one for each of them.
To make a script is very easy, I have attached an example of one I have uploaded on the website. If you need to attach a file, put it in a zip and upload both (the script and the zip) through the upload form on the website,
The address of the website is:
http://www.2borange.com/
A general thread on XDA (not dedicated to kernel on SGS) about the application:
http://forum.xda-developers.com/showthread.php?p=14875954#post14875954
You need to create an account to upload but it is not mandatory to just search, download and install a kernel.
Please keep me informed if everything work or not. I have only test it on my phone.
For the author of the kernels: I am sorry to have not yet informed you of the sharing of your great work, I will do it for sure when I will have done enough test to offer you an interesting way to share your work.
For the user: if you have time, don't hesitate to upload some scripts, it is free and easy to do...
Thank you for everything,
Michael
LIST OF KERNEL AVAILABLE AS OF JUNE, 27:
- Galaxian
- Infusion Kernel Faster Fusion Reaction
- Semaphore Kernel JVH - JVP
- SpeedMod Gingerbread
- TalonDEV
- TEGRAK lagfix- Voodoo kernel installer
- Voodoo kernel JVP
Don't hesitate to upload some new firmware. A model of script is provided below as attachment

niceee something to look foreward to

Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
This allows you to actually find a kernel, download it and flash it as well. The Kernel Flasher is just for kernels already on your sd card.

O-T said:
Neldar's SGS Kernel Flasher
is not locked to any web-site.
Sent from my GT-I9000
Click to expand...
Click to collapse
Thank you for your message.
I did not know about this application. I have read the description and I can tell you the purpose of mine is totally different.
I have understood that Nedar application is to install a Kernel that you have already downloaded and copy on your SDCARD.
The purpose of my application is to download automatically a script and a zip file, and execute the script.
So there are 2 main differences between these two applications:
- my application get files you need directly from the cloud (Internet), so it is like a deposit of files
- my application is not limited to kernel installation, it is just a usefull example to show people how it works, but it can do more, really lot more tasks.
However, because the application of Nedar is dedicated to one particular task, it has option I have not yet implemented in mine. By example, I have not yet construct a script to backup the kernel in an update.zip file, which could be very usefull.
So they are really very different. I hope I will be able to construct more script, but may be the biggest difference with any dedicated application is that anyone can participate to my project without any knowledge in Java programation.
You just have to know a little bit about shell to be able to share your work with others.
THAT IS THE REAL PURPOSE OF THIS APPLICATION : SHARING!

Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!

Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
Thank you for your interest.
The thing I need now is not money, donation,etc... but report of test and ideas of improvment.
By the way, I only have a samsung phone, and I am wondering if there are possibilities to install kernel in other phone only by using the shell, have you an idea ?
Second question: have you an idea how to proceed to install an entire ROM through the shell ? I suppose the phone has to be rebooted before installation begin and lauche in a recovery mode, but how to make it automatic like in ROM Manager?
Thank you for your help!

omzworld said:
Amazing concept!
Thumbs up for the foresight for such a nice project. If enough effort is put I can see in next couple of months, the whole, ROM, Kernel, Modem flashing automated.
Right from finding the correct software till installing them and may be some debugging and fault finding as well!
Will definitely donate in case the project takes off the way it should!
Great work Snoopy!
Click to expand...
Click to collapse
What is the way it should take for you?
I need ideas

lttldvl said:
Loving the concept of this!
As omzworld was saying, if this grew into a script that could automatically install your ROM/kernel/modem etc. that would be awesome, especially for people who are new to flashing.
Now, here's another suggestion that may or may not have been thought about already..
Is there any way to make the app look at your phone and use that as a basis for roms, kernels etc. ? If that was possible, anyone and everyone would be using your app to flash because they would know that bricking their phones would be almost impossible.
Click to expand...
Click to collapse
I have already included a kind of filter based on brand, model of phone and firmware version plus sdk version, do you think it could be more precise?

Fixed script on server, should work on every phone now

Hey snoopy33, why do you have not yet updated this page?

[Q]creating my own rom?

Hi guys- I have seen a website or page on how to build your own rom.
how difficult is it on 1 to 10?- 10 being very difficult.
what tools do I need?
many thanks

Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app

building your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??

creating your own rom
Chromium_ said:
Well it depends how you create the rom and what type of ROM you are creating.
If you plan to simply take an already made rom.zip, make a few little modifications, and zip it back up...it obviously isn't very hard, and likewise its not very satisfying.
If you want to compile a rom from source, then its a bit harder than the process above. To be more specific let's first talk about android versions that are officially supported by the desire: froyo, and gingerbread. Compiling roms based on those honestly isn't that hard. You just need some basic Linux/terminal knowledge. The device and kernel source is actually meant to work by default so you don't need to make any further adjustments. It as simple as opening terminal, downloading the source, and running a build command. Give it an hour (more or less depending on how food your PC is) and you should have a freshly made ROM that you built from source. Yay...some satisfaction.
The hardest thing in my opinion (I've tried all three of these) is compiling a rom based on an android version that isn't officially supported by the desire. (Ice cream sandwich or jellybean). With roms based on these android versions you will have to scour to internet for a working device, vendor and kernel tree. (Hint, hint: WoH and evervolv/nikez). Even once you get the right device tree it probably won't work. You will have to make further adjustments, and even then I'm sure you will be bombarded with build errors. But eventually once you get it to compile successfully....most satisfying thing ever
So yea thats my answer. Keep in mind that I've tried (and eventually succeeded) with all three of the above, and that I've got quite limited programming knowledge. (2 high school comp sci courses, where I learned some java.)
Sent using xda-developers app
Click to expand...
Click to collapse
htc_desire_luke said:
Thanks for that-
Sound very complicated
I am a webdesigner but have no knowledge of developing.
Wanted to try and build a really good rom to make the desire a really good phone for photography.
I have on my phone your rom and RSK supersense 3.5 rom running - coz I like the camera
and I would like to make a rom to turn it into a photography rom for my phone.
any advice??
Click to expand...
Click to collapse
any software needed ??

htc_desire_luke said:
any software needed ??
Click to expand...
Click to collapse
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670

There is an entire section dedicated to this subject, found in

creating your own rom
paolo-red1 said:
here is a summary of what you need and main steps, from hd2 forum.. next time do a search before post.
Obviously you have to use a desire device tree.
http://forum.xda-developers.com/showthread.php?t=2488670
Click to expand...
Click to collapse
sound very difficult-
my laptop is running linux and i think 64bits- I am running opensuse 12.1 KDE
but thats all i know
will have to do some more reading on this, I dont think I will be able to just pick it up and go.....

You are kiddin' me
Enviado desde mi HTC Desire

creating your own rom
Jack4L_ said:
You are kiddin' me
Enviado desde mi HTC Desire
Click to expand...
Click to collapse
what do you mean Im kiddin you?