Related
Here are the nbh files compiled upto the last change in the Dzo's GIT on the 03-05-10.
15-04-10 Updated - Uploaded new nbh's due to not working with Sense 2.1 build. Thanks kallt_kaffe & toasty_.
22-04-10 Updated - Latest Change from Dzo's git - Fix GPS enable/disable race condition on Kaiser.
26-04-10 Updated - Latest Change from Dzo's git - Add delays to vfe commands
29-04-10 Updated - Latest Change from Dzo's git - Add a delay to the adsp code and change the dsp irq handler.
03-05-10 Updated - Latest Change from Dzo's git - Add adsp delay and irq trigger change for cdma devices only.
PS: You may have to wipe system to get this to work so if your currently happy wait until you update your andriod system.
Here's the ones for the AT&T Tilt.
Updated 03-05-10 - See Post 1
What's the difference between the files in the first post compared to the second post?
Dukenukemx said:
What's the difference between the files in the first post compared to the second post?
Click to expand...
Click to collapse
ATT Tilt Keyboard layout.
tried this with eclair, and it gets stuck on at
Code:
A N D R O I D
xPreSiDenT said:
tried this with eclair, and it gets stuck on at
Code:
A N D R O I D
Click to expand...
Click to collapse
What build of eclair did you use as it sounds like the kernel is booting as it get's to where ANDRIOD is displayed.
I'm been using polymod 2.1g + the upgrade posted in the thread, it's been working ok for me. My knowledge of Andriod and linux is still quite limited, so I'm not sure what else to recommend.
happened to me too... just reinstalled the system with androidinstall.tgz (without wiping data) and all went well
I'm also using 2.1g, but I dont know about the update. Ive installed all the updates (polymod_2.1g-BT_Update.zip and the full market update) posted after 2.1g.. are there any more? I dont know how to update the kernel as is posted on the first page:
UPDATE 19 Mar 2010:
Latest .NBHs and Kernel for Kaiser & Polaris posted to http://ponack.net/poly/BT_Update/ , thanks again to Mr PaveL for building them.
If you're using HaRET, the same zImage now works for Donut AND Eclair. For Eclair you will need to add hw3d.version=1 to the command line in your default.txt . If the previous BT zImage wasn't working for you, this one should. (New Vogue .nbh and the same kernel can be found @ dzo's site.)
Click to expand...
Click to collapse
as far as I know the zImages are for haret users only... am I wrong?
xPreSiDenT said:
I'm also using 2.1g, but I dont know about the update. Ive installed all the updates (polymod_2.1g-BT_Update.zip and the full market update) posted after 2.1g.. are there any more? I dont know how to update the kernel as is posted on the first page:
as far as I know the zImages are for haret users only... am I wrong?
Click to expand...
Click to collapse
ZImages are for Haret you are correct.
PolyMod Update
http://forum.xda-developers.com/showpost.php?p=6105602&postcount=3011
What's the difference between the different Panel types? How do I know which one to use?
OshiHidra said:
What's the difference between the different Panel types? How do I know which one to use?
Click to expand...
Click to collapse
board-htckaiser.panel_type
Panel type used to power the panel off and on (see also vertical line issue)
[edit] Values
* 0 - Don't power off the panel
* 1 - Sony
* 2 - Topoly
* 3 - Topoly
Shamefully copied from here.
I just tried all three and settled on the one I think worked the best.
fultotop said:
ZImages are for Haret you are correct.
PolyMod Update
http://forum.xda-developers.com/showpost.php?p=6105602&postcount=3011
Click to expand...
Click to collapse
thanks alot! Am gonna try it right away. I seriously hope it solves my wifi issue :S
fultotop said:
Here are the nbh files compiled upto the last change in the Dzo's GIT 4 Days ago Fix kaiser usb (same as polaris). These are the first time I've done this, but I've tested them on my Kaiser.
Click to expand...
Click to collapse
Just a heads up. I also make my own NBH's and I noticed today another thing in tinboot.S that aren't up-to-date with the NBH's that DZO compiles.
Use a hexeditor and you will see that the mtdparts parameters are different. I've updated my NBH build (another thread here) and the noticable difference is that the partition sizes are different so that the system partition is larger than before. The data is still the same though.
I'm currently testing the Sense 2.1 build and it requires a larger system, that's why I noticed the difference.
Ok got the same problem with the nbh from DZO and yours. Problem is DZO uses other sizes and adresses for mtd-partitions, so if you are using Data and/or System on Nand, data can' be found.
Code:
DZO's NBH from 8th April:
mtdparts=msm_nand:[email protected](nand)ro,[email protected](root),[email protected](system),[email protected](userdata)
Yours:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
maybe it works if you first flash nbh and then reinstall system and data
EDIT: OK, was allready said - I've been to slow
kallt_kaffe said:
Just a heads up. I also make my own NBH's and I noticed today another thing in tinboot.S that aren't up-to-date with the NBH's that DZO compiles.
Use a hexeditor and you will see that the mtdparts parameters are different. I've updated my NBH build (another thread here) and the noticable difference is that the partition sizes are different so that the system partition is larger than before. The data is still the same though.
I'm currently testing the Sense 2.1 build and it requires a larger system, that's why I noticed the difference.
Click to expand...
Click to collapse
Thanks that would explain why it wouldn't boot without reinstalling the system partition for some people.
toasty_ said:
Ok got the same problem with the nbh from DZO and yours. Problem is DZO uses other sizes and adresses for mtd-partitions, so if you are using Data and/or System on Nand, data can' be found.
Code:
DZO's NBH from 8th April:
mtdparts=msm_nand:[email protected](nand)ro,[email protected](root),[email protected](system),[email protected](userdata)
Yours:
mtdparts=msm_nand:[email protected](boot),[email protected](root),[email protected](system),[email protected](userdata)
maybe it works if you first flash nbh and then reinstall system and data
EDIT: OK, was allready said - I've been to slow
Click to expand...
Click to collapse
Thanks you saved me some time, I've updated them see first post.
FYI, all the links in the first two posts are dead.
EDIT: nevermind, evidently I'm having a serious problem with my browser right now. Links are fine.
You say these work with the Sense 2.1 build but that requires HVGA while according to the file names these are QVGA. Are these actually HVGA (480) but just have the wrong names?
Nevermind, tested it out myself and they really are 320 builds. Well, nothing a little hex editing couldn't fix...
OshiHidra said:
What's the difference between the different Panel types? How do I know which one to use?
Click to expand...
Click to collapse
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
byron0318 said:
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
Click to expand...
Click to collapse
Yes. Yes it does.
byron0318 said:
320 works best with TyTn II. now you have to choose panel 1, 2 or 3. i suggest you try 2 or 3 because panel 1 have some pixel errors.
Click to expand...
Click to collapse
On your TyTn II perhaps panel 2 or 3 work best, however all 3 panel types are used on most models of kaiser, depending on supply at the time of manufacture, so there is no really easy way to tell which panel type you have, apart from disassembling your kaiser and checking the part numbers on the lcd panel itself.
I have 2 almost identical kaisers (KAIS130) both are identical in every way, apart from the lcd panel, one has type 1, the other type 2.
Pixel errors, colour problems, lines and streaks on the display, are all symptoms of choosing the wrong panel type for your device, and the only thing you can do is use a different nbh, or change panel type in default.txt until you find the correct one.
The last couple of hours I've been frantically trying to cook together a working ROM.
So far, this is what i've done:
*Replacing 2.6.33 kernel with Paul's "Custom Kernel" which is 2.6.29.
*Replacing&editing init scripts
Especially with the init scripts, my question is, are these the main parts of concern regarding a port?
In other words, am i on the right track, or is this much harder than i think? :S
Btw i don't think i'll get done with this before a ROM gets released, its just for interests sake
I thought the main problem was Froyo needing a 2.6.33 kernel and having to port Desire specific code into a 2.6.33 kernel so replacing it with 2.6.29 wouldn't work
Se the other froyo thread, I posted some quick instructions on how to boot a semi-working rom. There's no service and graphics are glitchy, also no wifi but that is just a matter of copying the right module, I didn't bother doing that.
There should be no dependency on a specific kernel version, but 2.6.33 is faster. I have also been trying to port cyanogen's 2.6.33 kernel but it's not as easy as it seems, there are many caveats and it did not boot yet.
deovferreira said:
Se the other froyo thread, I posted some quick instructions on how to boot a semi-working rom. There's no service and graphics are glitchy, also no wifi but that is just a matter of copying the right module, I didn't bother doing that.
There should be no dependency on a specific kernel version, but 2.6.33 is faster. I have also been trying to port cyanogen's 2.6.33 kernel but it's not as easy as it seems, there are many caveats and it did not boot yet.
Click to expand...
Click to collapse
Could the fact that MoDaCo's boot.img from rootedupdate.zip works, be related to it having an extra stage attached besides kernel and ramdisk?
I tried unpacking & repacking the boot.img you mention. And it doesn't boot
deovferreira said:
Se the other froyo thread, I posted some quick instructions on how to boot a semi-working rom. There's no service and graphics are glitchy, also no wifi but that is just a matter of copying the right module, I didn't bother doing that.
There should be no dependency on a specific kernel version, but 2.6.33 is faster. I have also been trying to port cyanogen's 2.6.33 kernel but it's not as easy as it seems, there are many caveats and it did not boot yet.
Click to expand...
Click to collapse
Could you post a link to this kernel?
I have managed to make it boot other kernels, by writing my own boot.img packing scripts.
edit: uploaded wrong file -_-
froyo kernel is 2.6.32
i'm almost sure this is the source code http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
cyanogen have also used 2.6.34
Kali- said:
froyo kernel is 2.6.32
i'm almost sure this is the source code http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32-nexusonec
cyanogen have also used 2.6.34
Click to expand...
Click to collapse
Thanks for the link.
So, as the Desire source code is available, it's mainly a matter of porting kernel code? What about RIL and "acoustic" libraries htc ? hmm.... When i booted Froyo with r1.1 MCR custom kernel, 3G/EDGE and calling worked fine. There was graphic glitches though. Framebuffer port?
gr0gmint said:
Thanks for the link.
Click to expand...
Click to collapse
i made a mistake,
http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32
this is "probably" the right kernel (with few patch to bcm 4329 wifi) i have just compared to the nexus config.gz (2.6.32.9, CFQ Scheduler ...)
sorry but there is no froyo tag in the git
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 =_____=
Dear all,
I ask around in the past days if anyone was doing it, but no luck, I even try to look myself if it was easy to do starting from CM kernel, but then, looking better on sourceforge.net the androidhtc project... in the git repo I've seen the htc-vogue-2.6.32 branch!!! Obviously started by dzo.
To get it I've done:
mkdir androidhtc
cd androidhtc
git clone git://androidhtc.git.sourceforge.net/gitroot/androidhtc/kernel
cd kernel
git checkout -b htc-vogue-2.6.32 origin/htc-vogue-2.6.32
Click to expand...
Click to collapse
Than to configure and compile it (I have a crossdev environment)
cp arch/arm/configs/vogue_defconfig .config
make ARCH=arm menuconfig
# need to be adjusted the config...
make ARCH=arm -j3 CROSS_COMPILE=arm-none-linux-gnueabi-
Click to expand...
Click to collapse
Or you can take the nbh in DZO site and edit with NBH editor.
Everything is working right now:
wifi http://forum.xda-developers.com/showpost.php?p=7869029&postcount=5586
GPS, 3g, touch screen, camera, 3d... bluetooth.
In two days I didn't have any trouble.
Can't wait for the new compcache
Original thread on HTC Vogue by DZO
This is GOOD NEWS!!! I bet theres a shed load of work to be done yet though but it'll be good to get things up to date!
WOW.. nice keep your good work Dude..
I'm just newbie, only can hope and waiting
this confused me when i saw it. according to the internet the google foryo release already is .32
blindguyinanorgy said:
this confused me when i saw it. according to the internet the google foryo release already is .32
Click to expand...
Click to collapse
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
This thread is kind of confusing. dzo said in the Fresh Froyo thread that he was pretty busy at the moment and what he meant with that is very likely that he is spending his available time on getting 2.6.32 ready for our devices.
It's very obvious if you keep an eye on the repo: http://androidhtc.git.sourceforge.n....git;a=shortlog;h=refs/heads/htc-vogue-2.6.32
The very best thing to do right know is propably to not disturb dzo more than necessary. I'm sure he'll let us know when it's has evolved to a somewhat useable state.
loserskater said:
Our kernel is .25 I think. This is what's in the nbh regardless of whether we're running Donut, Eclair, or Froyo. Froyo is just the "top layer" if you will. The kernel is what makes the hardware work with Froyo.
*I'm not 100% on this:* dzo started with .25 and has just been hacking away at it to get it where we could get each piece of hardware working on our devices. Because he's been working so hard and altered so much, it's difficult to port all of his changes to a new kernel. That's why we haven't upgraded. If we could do what dzo has done for the past 2 years on the latest kernel I'm sure there would be much improvement on our devices, but there's a LOT that needs to be done.
Click to expand...
Click to collapse
You are correct that we are using an older kernal. .25 is from before cupcake, wow.
I guess what I saw on the web was that new devices with froyo are also going to already come with .32
I wonder if there is much difference for any phone
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
new kernal
voyteckst said:
There's already nbh for vogue with kernel 2.6.32 posted yesterday. Do You think we can use it? Of course after customizing it to Kaiser with NBHEditor.
Click to expand...
Click to collapse
Used kernel 2.6.32 after using nbheditor, boots fine running fine so far. Shows kernel version 2.6.32.9 in android settings using Fresh Froyo. Taking it to work tomorrow to test it more.
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
handle223 said:
So far from some testing gps work, 3g work, wifi got error, video works
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
From my tests:
- had to reinstall whole system because of force close errors after changing nbh...
- 3g works, camera works, bt probably works (it enables, so probably it works ;-) )
- cannot even enable wifi
- probably location don't work (I wait about 15 minutes without results)
- didn't check gps
for me on pola200 camera doesnt work... bt activates, but wlan as with all devices - not working. feeling pretty smooth with this kernel...
Wifi fix - new 26/08/2010 kernel
dzo said:
I've fixed wifi on the 2.6.32 kernel. Attached is the new module, put it in /system/lib/modules. You'll also need the very latest kernel. I made some very big changes to the sd driver so this could break other things..
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
tiagoclc said:
http://forum.xda-developers.com/attachment.php?attachmentid=389254&d=1282909102
Try this...
Click to expand...
Click to collapse
Thanks, now wifi can be enabled ;-)
hello all
maybe a stupid Question how can I put the wlan.ko in the lib module
kisses
Rose Red
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
vArrow said:
Hi Rosered,
you must put it into androidinstall.tar(tgz) and reinstall it,(keep the data, don't wipe it).
That what I have done.
Click to expand...
Click to collapse
No, You don't have to reinstall. You can mount /system partition rw and replace old one wlan.ko in /system/lib/modules/
Use this android update
thx all for your help
kisses
Rose
haret
Did someone try haret already? I've problems with zimage 2.6.32 ...it hangs on startup...can someone drop here the haret.exe, initrd and default.txt ?
Hugs
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
i'd really like to help you, but i'm not able... this morning i studied some tutorial such as http://pdk.android.com http://android.git.kernel.org http://d.android.com, but i'm new with linux and i can't understand anything... however i was asking myself the same questions...
Quick catch-up:
Dexter_nlb said:
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
Click to expand...
Click to collapse
Check, Possible: http://forum.xda-developers.com/showthread.php?t=767431
Dexter_nlb said:
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
Click to expand...
Click to collapse
Well, IDK if this easy, but manageable. Both odin (easier) and update.zip (more stable) options available.
Dexter_nlb said:
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
You could contact people at #project-voodoo to get more detailed information.
Best of luck.
Dexter_nlb said:
I got myself a Galaxy S to play with now, and so far the good part is the nice screen...
ive done some porting to motorola milestone which i will start looking into on this phone...
As i understand Kernel can be customized and we can pretty easily install mods using update.zip ?
is updating ramdisk "easy"? if you can handle linux quite well? anyone with instructions on building the initrd image?
secondly building an image? should it be tar'd using odin? or using update.zip?
problems on milestone has been "usb" steeling battery as the native support on htc is different so handling it required a scripting workaround..
with senseui the biggest problem will be porting Bluetooth as it is very different from standard google practice...
anyways i hope to be able to contribute with a SenseUI and MotoBlur port to SGS soon, when i get time to research handling on this model.
Click to expand...
Click to collapse
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
thanks , very usefull.. so the .md5 extension on odin files are related to?
anyways i have made zImage for other platforms so changing the ramfs should be straight forward...
Finally a person who knows their stuff is attempting at a sense ui port.
Hope you succeed
I really hope you succeed - I have time but no knowledge - if you need help pm me
DesireHD rom? YES PLEASE!!!
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
Same here.
MAMBO04 said:
I'll happily donate if you create a Bounty Thread here, if you do get down and serious about it.
Click to expand...
Click to collapse
thanks, im primarily persuing this as a personal challenge, but of course if ppl likes my work its great.
one note is, as written earlier, more experienced guys will be required to finish the bluetooth adaption, its alot more complex than the remaining parts.
and im told even on older htc phones it was hard to port drivers for bt.
my 2.1 sense mod on milestone was ok, except milestone only had 256MB, which resulted in many reloads of senseui.. here i think we can stabilize, even with a modified kernel to add swap if needed (if the 512MB utilization becomes a problem)
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
xan said:
You could contact people at #project-voodoo to get more detailed information.
Click to expand...
Click to collapse
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
jjwa said:
I would be very interested in a Desire HD rom for the SGS .
If it is completely functional for all the functions I use (I use no Bluetooth for example), I would be willing to donate too.
+1.
It's on the Freenode IRC servers. There's a bunch of talented developers working on improvements for the SGS there, so be sure to drop by.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=8254744#post8254744
A thread for bounty to devs porting for SGS succeed
-Fraction
Aery said:
Samsung is using a zImage. Compressed Kernel + Initramfs.
Since for 2.2 is no Sourcecode available till now, it's very hard to modify anything.
2.1 Source is available at opensource.samsung.com.
You can pack the zImage with tar under linux and flash with odin or you can flash the Image directly using redbend_ua (OTA Update) through an update.zip.
Click to expand...
Click to collapse
Wasn't the JPM source leaked for a little while about a week back? Is that the source code to which you're referring?
Edit: Sorry forgot to check the post date, so at the time you posted that, the source code had not been leaked