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.

04/Jun - Official HTC 2.1 (3.31.751.1 Chungwa Taiwan) multiple repacks

Please find below the Official HTC 2.1 update for Chungwa Telecom Taiwan (3.31.751.1) in it's various guises repacked to update zip format. An online kitchen is also available for MoDaCo Ad Free or MoDaCo Plus members. A MCR based on this release is in progress.
I note that 42turkeys has already uploaded a rooted repack, but I need to create these for the kitchen anyway...
RECOMMENDED - Rooted with Superuser 2.1 by ChainsDD, insecure boot included, radio image NOT included, Chinese specific functionality (HTC_CIME, Plurk, KKBOX etc.) removed, additional languages, HTC_IME and Busybox added - MD5: e7d08761f201ea3054510b83623eb724
RECOMMENDED - Radio only - for use with the above (note: issues have been reported with Orange UK) - MD5: d2c45b49e76d8826fb50803277b29caf
Rooted with Superuser 2.1 by ChainsDD, insecure boot and radio image included - MD5: 0a6f7cca936c4fc10193532bc99b8cec
Rooted with Superuser 2.1 by ChainsDD, insecure boot and radio image NOT included - MD5: c323bf5689707027cd7f661a94ab7084
Unrooted with insecure boot and radio image included - MD5: 6ef91d52547319b86016e21f6ff99b4e
DOWNLOADS
Enjoy!
P

Nice work Paul, I still beat you to it!

42turkeys said:
Nice work Paul, I still beat you to it!
Click to expand...
Click to collapse
Haha! And i've been waiting for it drop for months, lol!
P

Hi All
Does HTC put Friendstream inside HTC Hero 2.1 rom?
French langage is present inside multi-language? For example in home menu, "Téléphone" instead of "Phone"
Many Thanks
Gibou

ok.... so which one do I use? yours Paul, or roufianos (which certainly sounds interesting), or 42's eclair-update-signed?
and this is likely a really naive question LoL, but I'm guessing these won't overclock?
And if they won't overclock, will it be possible for you amazing people to supply a kernel that CAN overclock any time soon using the actual hero 2.1 official kernel source? or is that going to be unavailable source code for the forseeable future (based on past experience with google/htc)?
One of my current issues with VR6.2.1 is that the camera only works at iso100, making it almost useless for taking pics of kids/dogs/anyone who isn't posing still. I'm hoping that this official rom fixes that. But I'm thinking that maybe using an alternative kernel that can overclock which isn't actually based on the official hero kernel source code but is in fact taken from the Eris (like VR6) might break the camera iso functionality again.
So much boring long crap I'm writing eh? LoL
oh, and most importantly, thanks for being super amazing!
cheers,
Dkelley

No voice search or voice input. Is it possible to add or get this?
Otherwise it's a very good rom, very fast!

dkelley said:
ok.... so which one do I use? yours Paul, or roufianos (which certainly sounds interesting), or 42's eclair-update-signed?
and this is likely a really naive question LoL, but I'm guessing these won't overclock?
And if they won't overclock, will it be possible for you amazing people to supply a kernel that CAN overclock any time soon using the actual hero 2.1 official kernel source? or is that going to be unavailable source code for the forseeable future (based on past experience with google/htc)?
One of my current issues with VR6.2.1 is that the camera only works at iso100, making it almost useless for taking pics of kids/dogs/anyone who isn't posing still. I'm hoping that this official rom fixes that. But I'm thinking that maybe using an alternative kernel that can overclock which isn't actually based on the official hero kernel source code but is in fact taken from the Eris (like VR6) might break the camera iso functionality again.
So much boring long crap I'm writing eh? LoL
oh, and most importantly, thanks for being super amazing!
cheers,
Dkelley
Click to expand...
Click to collapse
Use whichever ROM you want.
SetCPU seems to be overclocking ok, HTC have to release kernel source code as they have modified other open source stuff.

chriscpritchard said:
No voice search or voice input. Is it possible to add or get this?
Otherwise it's a very good rom, very fast!
Click to expand...
Click to collapse
Both of these will be in the 'MCR' version i'm working on.
P

paulobrien said:
Both of these will be in the 'MCR' version i'm working on.
P
Click to expand...
Click to collapse
Cool, thanks, would you also be able to add the news app?

Nice work ! But where's Friendstream ??

42turkeys said:
Use whichever ROM you want.
SetCPU seems to be overclocking ok, HTC have to release kernel source code as they have modified other open source stuff.
Click to expand...
Click to collapse
you should be able to use any 2.6.29 kernel (from other 2.1 roms) or build your own using the leaked kernel sources http://github.com/behnaam/HeRo-2.6.29-GoDmOdE .

Works great for me Hero GSM China Mobile.
Thanks for Sharing !

paulobrien said:
Please find below the Official HTC 2.1 update ..
Enjoy!
P
Click to expand...
Click to collapse
i have a question, will i receive if the official have any other update pack??

Hi ! Thank you for this release ! Flashing right now. I'll use it until the WWE or European version come out.
I still find that the new "shiny" look of the Sense UI is not as good as the previous one

Is there any body using oc kernel? If yes which kernel you using with this rom?
-------------------------------------
Sent via the XDA Tapatalk App

i flashed this and booted it up, and there's a little box in the middle that says "Loading........it make take several minutes to complete, please wait"
its been there for 10 minutes now
should i reboot, or take the battery out ? or just wait ?

berger34 said:
i flashed this and booted it up, and there's a little box in the middle that says "Loading........it make take several minutes to complete, please wait"
its been there for 10 minutes now
should i reboot, or take the battery out ? or just wait ?
Click to expand...
Click to collapse
Wait. It takes ages...

ok thank you

the screen times out after inactivity, and i can't get into settings to turn it off; does that affect the loading at all ?

how can i get mms working on this?
EDIT: fixed didnt set any APN's =_____=

30/Jun r1 (JFB) - MoDaCo Custom ROM for Samsung Galaxy S with Online Kitchen

I'm pleased to present my MoDaCo Custom ROM for the Samsung Galaxy S! READ THIS WHOLE POST BEFORE YOU START! No, really, it contains everything you need to know. wink.gif
This ROM is the 'starting point' for my Galaxy S custom ROMs.
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 ALREADY BE RUNNING THE JFB ROM FROM HERE. Do NOT use this ROM with any other base, unpredictable things will happen, the most likely being you'll have to reflash your device via Odin.
Features Included
* Based on the JFB release
* Rooted with Superuser 2.1 by ChainsDD
* Built with the MCR build process which reduces the size and boosts the speed of the ROM
* busybox with Droid Explorer support
* Updated Google Maps
* MCR version displayed in 'About' screen
* Optional Google Voice Search
* Optional Google Voice Dialer
* Optional Fancy Widget
* Optional Beebplayer
* Optional baked in Wavesecure via the online kitchen (installed to system partition for maximum security)
Changelog
Please see 2 posts below this one for the changes in each release.
Installation
To install this ROM:
* Ensure you have the JFB ROM installed (linked above)
* Download the zip file of your choice from the links below (or the online kitchen) and copy to your SD card named 'update.zip'
* Restart your device in recovery mode by running 'adb reboot recovery' (download adb if you do not have it already, use adb-windows, adb-mac or adb-linux as appropriate)
* 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 currently only available in the online kitchen - prebakes to follow.
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.
And finally...
If you would like to show your appreciation for the ROM, please consider supporting MoDaCo by signing up for a MoDaCo Ad Free or MoDaCo Plus account, both of which also give you early access to Beta ROM releases and access to the the online kitchens.
Enjoy!
http://android.modaco.com/content/s...rom-for-samsung-galaxy-s-with-online-kitchen/

Does this ROM fix the ram issue so that all 512MB of ram is utilized?
Congrats on being the first custom rom here.

Congratulations! I don't have a phone yet but I am very pleased to see a custom rom already!

woohoo custom ROMs already. Guess I'll be getting myself the phone after all.

umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?

Perrosky said:
umm.. but in another thread people where saying that it wasn't gonna be possible because samsung encrypt their drivers etc. so this mean they did release they drivers? and there is gonna be alot of custom rooms for galaxy gravity?
Click to expand...
Click to collapse
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.

Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?

Javalu said:
Hold on, hold on. So even though Samsung released the Galaxy S' driver source code to the public, it's going to be "near impossible" to port Sense and FroYo to the phone? I may be ignorant but I'll just ask with ignorance, how do you figure?
Click to expand...
Click to collapse
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean

psychoace said:
No I said it would be near impossible to get roms from other sources like Sense roms or Froyo on because of the driver issue. I never said you would never see custom roms. The only roms you are going to see are one's based off of Samsungs release.
Click to expand...
Click to collapse
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.

Papa_I said:
Quick question, does that mean any custom rom that is release will be based off the official rom they release which has Touchwiz backed in? If so, does that rule out a plain vanilla android rom for this device? Thanks for your help and appreciate the knowledge.
Click to expand...
Click to collapse
No it doesn't rule out plain vanilla android rom. Yes they will all be based on Samsung but rom makers can take out all the touchwiz garbage and throw in another launcher like adw or Launcherpro.

That's what I wanted to hear. Thanks for the help. Now if I only could decide if I should keep the Nexus One or purchase this phone..... Decisions, Decisions.

psychoace said:
Download the source code..... ok now open it and go to GalaxyS_Kernel.tar.gz. Now in there just enter the first folder then go to modules. Go to Dpram. Open up any of those files in notepad. You should see written non-compiled code right? That is fine now go back to the module folders and go to S3cbc. Now open up s3cbc_module.o. Does that look like non-compiled code? No it doesn't. It's either already compiled or encrypted. That's what I mean
Click to expand...
Click to collapse
How lame. Have other handsets had similar problems?

what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.

Javalu said:
How lame. Have other handsets had similar problems?
Click to expand...
Click to collapse
Yes the Behold 2, the original Galaxy, and the Moment all made by Samsung have only had Samsung roms on them.
lgkahn said:
what are talking about .o files and unix compiled modules same on all versions of unix. o stands for object module.
Click to expand...
Click to collapse
So they can easily be decompiled? If it's source code why is it already compiled?

dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?

raspdeep said:
dont go too deep into specific things that we may not even need (we are not coders here) but the source code for basic hardware that we need to get things going are already there.. things like camera, wlan, etc. btw, do u know what s3cbc is for?
Click to expand...
Click to collapse
What about s3clcd? Here is a little copy and paste of some of the garble that was in the compiled file
screen width=%d height=%d va=0x%x pa=0x%x
I would go out on a limb and say those are video drivers. The one's that have been encrypted on all other samsung phones.
Also in s3cbc there is some code at the bottom
PVRSRV_PIXEL_FORMAT_YUY2 PVRSRV_ERROR_FIFO_SPACE char ui32ByteStride psDevInfo PVRSRV_PIXEL_FORMAT_PAL1 PVRSRV_PIXEL_FORMAT_PAL2 pfnOpenBCDevic
If you don't know the Galaxy's gpu is PowerVR SGX540 and YUY2 is a colol format for video screens
http://www.fourcc.org/yuv.php#YUY2 and Pal is of course a European video standard.

they are not encrypted, they are object codes in machine language for arm.. and why we need that again for custom roms?

Wanted to test modaco ROM but they are not free.. Any kind souls upload and share ?

well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here

Ferdimage said:
well feedback on the R1 rom its clean and smooth, worked even better when i did the stall tweak posted here
http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
the phone seriously got 2 times faster, opening apps playing game very quick .. happy as here
Click to expand...
Click to collapse
How much free ram have you got? Considering flashing and rooting, but not sure if it's worth it right now. Meh 10£ isn't that much think I'm gonna give it a try.
EDIT: Just flashed, but now I don't have root access(says access denied when I try to access the /data/data folder). Thought this included the rooted PDA file or do I have to flash that again with odin?
EDIT2: Scratch that I forgot to press the allow-button on my phone after sending the Super-user request..

[DEV][DEV-ONLY] Honeycomb Progress

[This is not the place to say "this is awesome" or "thanks!"]
[DEVS ONLY]
I want to start this thread to keep up the progress on the port.
the bad news is that the SDK is incomplete for now, so (like other devices)
we will have to write our own code for the OS, the nook community
has done a wonderful job writing their own libraries and stuffs, so we will have to do the same.
Instead of pursuing different goals, let's focus on one thing at a time.
since GSM and CDMA versions are already out, it seems we suffer the same bugs, so for now let's unite strength and knowledge to overcome these.
I propose that the first goal to fix is the SurfaceFlinger, so we could at least see the apps, the buttons and the notifications.
it is currently throwing this:
04-06 22:01:35.495: ERROR/Surface(2960): dequeueBuffer failed (Out of memory)
this could lead us that it might coudln't start because of some malloc malfunction or something.
also that pvrsrvinit bugs me a lot.
update:
8/APR/2011
since DiP7 could fix SurfaceFlinger and other things using a different build from the GSM kernel, we have to dig deeper
======================================
CURRENT GOAL
Rebuild Kernel
======================================​
Current approaches:
*none
Post any finding, guessing or anything, and please, please don't be afraid to ask anything you have a doubt, as a Dev you should not know everything, so we can help us each other
------------------------------------------
Google Easter egg:
while searching some info about the android.mk file , I put it on the chrome bar to search for that term, but instead I went to
http://android.mk
an easter egg web page from google lol

******TOOLS*********
How to send text and Keystrokes via ADB
http://bradchow.blogspot.com/2011/02/send-intent-and-key-event-by-adb.html
use DroidExplorer to easily access your device from your computer and makes changes from it
http://de.codeplex.com/
The Android Boot Process
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
---Kernel Tools----
CPU Datasheet
http://forum.xda-developers.com/showthread.php?t=745877
Samsung GIT
http://android.git.kernel.org/?p=kernel/samsung.git;a=summary
PowerVR SDK
http://www.imgtec.com/powervr/insider/powervr-sdk.asp
Source code of samsung firmwares(keep and eye on this)
http://opensource.samsung.com/
Asus pad honeycomb Kernel Source
http://forum.xda-developers.com/showthread.php?t=1026528

ellokomen said:
======================================
CURRENT GOAL
Find why SurfaceFlinger is not working
======================================​
Click to expand...
Click to collapse
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)

updated approaches and new tools have been added

spacemoose1 said:
Mmmk.. Let me tell you a story.
A long time ago in a galaxy far away... No, that will take too long. In a nutshell, one third of the answer is here, another third is here and the rest is here. I'm not trying to be intentionally vague, I just haven't figured out how these three fit together yet.
Of course, there could also be some bit of code that I missed... some telling line in a debug log that I overlooked or some driver or library that I could have decompiled to sift through its juicy secrets. There could easily be a fix that would take seconds to add and make the whole thing fall in line...
Or we might have to work it from the ground up.
Either way it will happen. It's just a matter of whether it will happen next week, or next month.
(Watch it be a misplaced semi-colon, or a bad symlink... that's how these things go.)
Click to expand...
Click to collapse
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
However I do not think you are wrong that there is a problem somewhere in the kernel. The kernel that has been released for the galaxy tab is a mess of horrid code, I have had to re-write parts of kernel drivers just to get them to work under linux, I would not be surprised if similar patches are needed for honeycomb
Click to expand...
Click to collapse
you mean that you made a port of a Linux Distro into the tab?

ellokomen said:
you mean that you made a port of a Linux Distro into the tab?
Click to expand...
Click to collapse
yes click here for the thread on the port of ubuntu

Current kernel source
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
here it is, bear in mind that this is for CDMA devices

Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??

daml said:
Unfortunatey, we have 4 other honeycomb threads.
Not trying to be rude but spacemoose updates us in the cdma forums AND we have russian rom updates in the gsm forums.
I really dislike the idea of this thread, there is enough clutter amongst the other threads. Do we really need one more place to browse..
The first posts in the roms thread are kept updated by devs.. Is this not enough??
Click to expand...
Click to collapse
yeah but we need a place for the other devs to share their milestones, here is a place for technical discussion amongst us, to share the knowledge etc...
the other threads are flooded from non devs messages, so it´s kind of difficult to read 14 pages of information when the 80% is people complaining not making it boot

lilstevie said:
The kernel source that you have linked to is 2.6.35.7 for the Nexus S gingerbread and is not fully maintained by samsung but rather by google.
Click to expand...
Click to collapse
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.

noobporter said:
Do you guys have another link to the current spacemoose kernel source? The download link seems to be corrupted and won't untar. I want to get in on the fun
Click to expand...
Click to collapse
D'oh! Nobody told me, LOL... I'll get another copy up.

spacemoose1 said:
D'oh! Nobody told me, LOL... I'll get another copy up.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!

Flokey said:
http://forum.xda-developers.com/showthread.php?t=1026528
hey spacemoose! the first portion of honeycomb source... The kernel source of the Asus EEE Pad Transformer... maybe it helps you with a few kernel issues, even if it's for another device... It's honeycomb!
Click to expand...
Click to collapse
Digging through it now.

spacemoose1 said:
Yes, and it contains some support for our device (s5pc110), and some more that can be added (pvr) and the architecture necessary to fully support HC without patching the build itself. If we work only towards patching the system build to communicate with the hardware, we won't be able to run AOSP hc versions when the source drops without going through the same painstaking process of hacking the system to function (while creating numerous faults causing FCs in the process). If we build a new kernel, we can get the hardware to communicate in the way future android versions want it to and we can then do what we want with ease.
Click to expand...
Click to collapse
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb

lilstevie said:
Not enough really, PVR kernel module sources have been released from samsung for our device, and is available in update1 zip.
The kernel panics and we have no framebuffer from the nexus s, believe me that is the kernel I want to be running for my project, it is cleaner nicer and things are implemented overall better. unless you know of a solution for kernel debuging over usb
Click to expand...
Click to collapse
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.

Goal and tools updated*

spacemoose1 said:
Kernel debugging over USB = adb shell cat /proc/kmsg
You can make any kernel work for any device as long as you add the **** it needs. Just takes time. Working on it now.
Click to expand...
Click to collapse
You don't know what a kernel panic is do you?

lilstevie said:
You don't know what a kernel panic is do you?
Click to expand...
Click to collapse
I thought that linux throws a dump log when it makes a kernel panic specifying the memory address and the cause of crash

[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?