yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] foxmeister:
Where's this "next day" come from?

Froyo announced on the 19th and today is the 22nd.

It may well be hoax. Time will tell of course, if over the next few days Nexus One owners start reporting getting at OTA to Froyo.

Regards,

Dave
[Desire Android Development] DocRambone:
http://twitter.com/Integrateds/status/14486956801

http://twitter.com/ehkrass/status/14480874165

Lets hope some dev takes on the challenge, what happened to the "developer checking in thread" ? They checked out again?
[Desire Android Development] abc27:
It looks like this is a genuine OTA update, many people have reported receiving a FroYo OTA update from Google.

Only a matter of time now before it's ported to the Desire!
[Desire Android Development] Nekromantik:
lets hope people get on to the port right away!!
[Desire Android Development] darrenjdoc:
Excellent news !!
[Desire Android Development] Azurael:
Do N1 ROMs work on the Desire? I know that some N1 owners were flashing Desire ROMs to get Flash support, although I've no idea whether those were modified?

To be honest, I think at this stage, I'd lose Sense for official Apps2SD and the Dalvik enhancements.
[Desire Android Development] DocRambone:
Devs, start cooking :

http://android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
[Desire Android Development] neowlchaz:
The thread over at Nexus One discussion have the link to the update now. I've downloaded it, just in case google take it down. Can any of our guys get to work with porting this by any chance??
[Desire Android Development] StuMcBill:
Yeah me too, I would also be interested in any battery life improvements it may bring, I think sense may be a bit of a battery hog!
[Desire Android Development] MaTiCeK-:
I happily give up Sense, it's only slowing down my workflow. Love the look of 2.2. vanilla.
[Desire Android Development] erfarne:
cant i just flash with original update just to desire? isnt it exactly the same phone? :).. rename the updatefile or something..
[Desire Android Development] DocRambone:
No, u cant, Nexus and desire dont even have the same hardware
[Desire Android Development] erfarne:
its a shame i dint buy a nexus.. the desire is better looking tho.. i really need this update.. could almost kill for it :).. how long you think itll take when a dev start working on it?
[Desire Android Development] Azurael:
That's clearly not true if N1 owners were using Desire ROMs - obviously there are minor cosmetic differences, like the hard vs. soft keys and optical vs. physical trackball but those must have been worked around.

However, I suspect this is a jump that only works properly in one direction, due to the dodgy rooting process on the Desire where you have the ability to flash the 'wrong' ROM a lot more easily onto the N!.
[Desire Android Development] :
Do you feel its useable now then? Are we getting close?

jd;)
[Desire Android Development] Bengaal:
Bravo....TEAMWORK!!!!,

That's the spirit

You're doing great job :)
[Desire Android Development] gr0gmint:
It's usable to the limit that you can't make phone calls, because of the microphone not working :( But the system generally seemed very usable, except those few bugs that are left. Flash worked fine too.

Here's the download link:

hxxp://www.mediafire.com/download.php?czdczyfje1z

;)
[Desire Android Development] MaTiCeK-:
what about usb and sd card?
[Desire Android Development] 1wayjonny:
Dont post this crap in the development section of XDA, this is no development!
[Desire Android Development] :
Wow thats superb, we can smell the sugary goodness now mate;)

So the mic is the real stumbling block really now;)

JD;)
[Desire Android Development] sruon:
A wild troll has appeared!
[Desire Android Development] gr0gmint:
Both works. If SD does not seem to work, you have a weird parition table.

You can fix this by renaming files in /dev/block/vold.

I had to rename my 179:1 to 179:3 . But this was unnecessary after i formatted the SD
[Desire Android Development] myth1001:
I assume he only read the title and not the content of this thread where a few people has been trying hard to port froyo to Desire. :rolleyes:
[Desire Android Development] :
He is still a pr**k;)

ahhahahaha;)
[Desire Android Development] phunkycow:
Re: Froyo for nexus released, any DEV's here?

If this isn't development, I really wonder what is. Please leave :)

On topic now, thanks to the guys working on this! Really great job! Wish I could help in any way, but I'm totally clueless...
[Desire Android Development] :
He is still a pr**k;)

ahhahahaha;)

I have been noticing a rise in self rightrous people in this forum of late, time for the mods to kick these prats out and let them understand that its the mods that do the moderating and not the sheep;)

lol

JD;)
[Desire Android Development] kingchris:
http://xdaforums.com/search.php?searchid=37746628

omg he spend the last 2 hours in posting this in several forums....
[Desire Android Development] PaulW21781:
Your search link won't work for other users, but yeah, I've seen the same...

Blah blah blah dont post here, post there, wtf you doing, blah blah, im 12, blah blah, MUMMY!!!

...

But as for the ORIGINAL reason to this thread, keep up the good work :D I'm just downloading the Froyo repo from the other page which was linked up, going to have a look through it myself see whats what with the thing :)
[Desire Android Development] :
TROLL ALERT!!!!

lollol,

Not a dev topic, give me a break:)

hahaha;)

I think the word TWAT comes to mind;) lollollol

JD;)
[Desire Android Development] NoMercyWWE:
Good evening guys - using the file posted above my device hangs at htc screen - i have bootloader 0.80 - should i use custom kernel from modaco?
[Desire Android Development] PaulW21781:
Out of interest (I could always split it...) but the boot.img file contained within the Froyo ROM... What was that one originally from?? Or is it the N1 boot.img?? And also, was this based on the FRF50 rooted Froyo ROM?? Or is it that just with the radio & hboot split out?? (Sorry if it's already been mentioned, I'm lazy today...)
[Desire Android Development] :
I think we should post a warning not to use this rom untill its out of the dev stage.....

JD;)
[Desire Android Development] DocRambone:
U kidding?
[Desire Android Development] gr0gmint:
This boot.img is a custom one based on the HTC stock kernel (2.6.29), and a modified init script from Paul's rooted Froyo update. What i mean by modified is, it's merged with some lines from the stock init scripts.

Btw don't use the splitting and repacking perl scripts, that are popularly used. They are broken.. I've attached my own
[Desire Android Development] NoMercyWWE:
Jupiterdroid just sent you a pm! thx
[Desire Android Development] Simon2:
Great work guys! Hope we can all run froyo soon!

Maybe a rom for the right/missing files:

[Rom] nexus experience

http://xdaforums.com/showthread.php?p=6566400
[Desire Android Development] kingchris:
right wont boot on HBOOT 0.80

seems, 0.80 uses another kernel??

i changed the kernel and used the given ramdisk.
[Desire Android Development] AdamG:
booted for me fine on 0.80
[Desire Android Development] NoMercyWWE:
adam what did you do to make it work?
[Desire Android Development] sruon:
Quick test...

Very stable, 3G seem to work fine here, but indeed no HSDPA

SD card works fine, it asked me to format it though, GPS works...

Camera works but only on the first launch, I took a picture, went back to menu then camera, quit working
[Desire Android Development] :
I advise strongly no - one other than the guys developing this to boot this, sit tight;)

JD;)
[Desire Android Development] Tuborgmann:
If you by HSDPA mean the statusbar showing "H", its completely normal, it only says "3G" on stock Google Rom's, even when running hsdpa.
[Desire Android Development] PaulW21781:
I'll have a go at building a 2.6.33 kernel for it... see if that helps! Soon as I've got the Desire sources, and figured out what needs patching on the vanilla kernel!
[Desire Android Development] sruon:
Ha! Didn't know, indeed I have HSDPA showing under Phone Status in the parameters menu.

Other than that, android market takes some time to download (though N1 owners have reported market being really slow lately), the desktop has a laggish feeling... but if I didn't know it was a N1 port I'd swear it's the stock Desire ROM. (well... bar the obvious bugs like microphone.)
[Desire Android Development] Tuborgmann:
Yes, compared to Launcherpro the desktop seems really slow, not really laggy just slow.
[Desire Android Development] nikosrs4:
keep it up guys, much appreciated!
[Desire Android Development] AdamG:
what did you change to get the radio working?
[Desire Android Development] Bengaal:
That was the main reason I dont use Android. ;)

But i will of course if froyo works correctly. :)

I believe in you devs.
[Desire Android Development] kingchris:
48 mflop in linpack!

rly good.

i think its not so hard to fix the mic
[Desire Android Development] sruon:
My battery is up to 40°C, never even got past 35 in 2.1
[Desire Android Development] gr0gmint:
I think including the firmware, adding libhtc_ril.so and adding "rild.libpath=/system/lib/libhtc_ril.so" to build.prop did the trick
[Desire Android Development] kingchris:
rild.libpath=/system/lib/libhtc_ril.so

is includest in the original nexus froyo build prop.

think this was not the problem
[Desire Android Development] gr0gmint:
What kernel did you use for your rom?

Edit: Could also have been some permission issues arising from bad init scripts
[Desire Android Development] gr0gmint:
The biggest part of this challenge was actually faulty boot.img-packing scripts. The popular ones unpack-bootimg.pl and repack-bootimg.pl are broken. Sorry for mentioning twice, but just thought i should mention. I didn't change much, i didn't fix any kernel code or anything with this rom...

So the next question is, are the problems in the rom now in kernelspace or userspace... :confused:
[Desire Android Development] :
Well we know for sure that the bluetooth is kernel space, maybe richard trip can have a look at what you guys have done and delve into the kernel.

JD
[Desire Android Development] AdamG:
I'm going to attempt to build a newer kernel for the desire tonight, I have put the kernel sources here for anybody who needs them.
[Desire Android Development] PaulW21781:
Adam, what version are you looking at? .33 or .34?

*edit*

Just seen your .34 repo on the same location :D
[Desire Android Development] :
Phenominal effort mate, fingers crossed
[Desire Android Development] AdamG:
Going to try for .34, I will let you know how it goes before the night is out I hope.
[Desire Android Development] adam235:
Adam, where can i get the source of the kernel on which your froyo port is running atm. i would like to compare the diffrences in arch/arm/mach-msm with the .34 kernel sources.
[Desire Android Development] AdamG:
I was using an older kernel on my froyo port, I just took one from a 2.1 release.
[Desire Android Development] JDouce:
some admin should lock this and create a new topic "Desire Porting Effort" and have all the upto dat links or adamg could start 1

unlesss you know whats going on in this thread ud have no idea from the title
[Desire Android Development] Kali-:
why do not start with the same kernel of the froyo nexus one?
[Desire Android Development] PaulW21781:
Froyo is 2.6.33 from what I've seen on my friends N1, and as making a new updated kernel (regardless of .33 or .34) requires a complete work through the source, its easier to just grab the latest vanilla sources & work on patching those for the Desire.

You can't just use the source for the N1 kernel & tweak it, even though the hardware is "similar", there are still significant changes which require more than just a quick change in the configurations.

I build kernels myself for my server (Gentoo-based), and when there is a major kernel update, I have to go into it, configure it all over again, patch what I need patching for bits which aren't in the kernel by default, blah blah blah...

AdamG has got his work cut out, I'm having a look at it aswell, but to be fair I dont think I'm anywhere near as skilled with Android hacking compared to this chap.

Hats off to him, thats all I say!
[Desire Android Development] Kali-:
from Froyo N1 /proc/config.gz

#

# Automatically generated make config: don't edit

# Linux kernel version: 2.6.32.9

# Thu May 6 16:48:18 2010

#

http://android.git.kernel.org/?p=kernel/msm.git;a=shortlog;h=refs/heads/android-msm-2.6.32

sure .33 or .34 are also good, but starting from a working kernel is better imho

edit:

another good start point is cyanogenmod kernel http://github.com/cyanogen/cm-kernel (2.6.33.4)
[Desire Android Development] StrongOneX:
where is dat "stable froyo before night"? im waiting..
[Desire Android Development] sruon:
you can't be serious, are you?

Thanks whoever renamed thread btw
[Desire Android Development] JDouce:
which rom are u working with as a base ...

kernel it the main issue

are using pauls pre rooted etc nexus rom
[Desire Android Development] JonesWTF:
You're waiting? So am I, but I understand the complexity of what everyone has to do to get it running. If you're going to be like that, maybe you'd like to offer some help to speed things up? If not, shut it!

I personally would love to help out, but I don't really know the first thing about where I'd need to start. Theming is about all I can offer.
[Desire Android Development] FloatingFatMan:
Do it yourself then, Mr Impatient.
[Desire Android Development] stingerpl:
Ask mommy.
[Desire Android Development] StrongOneX:
any progress?

sorry for last post guys..
[Desire Android Development] fstluxe:
If I'm right the only big thing that has to be done = modifying our kernel to .32/.33 right ? if thats alright froyo would run .... so this job is for the kernel developers.:rolleyes:
[Desire Android Development] gr0gmint:
Why are the problems kernel related again?

The current kernel supports the hardware just well ? :confused:
[Desire Android Development] StrongOneX:
Please make a new thread just as Pay's and paul does it, like posting rom at the first post and changelog and so on, its boring to browse all pages to find the rom .. really!
[Desire Android Development] JonesWTF:
Surely this will happen when there is an almost fully working rom? Is there really any point just now? I don't think we're able to make calls yet are we? When I get home (currently in the hospital with my mate) I think I'll lend a hand with this. I've been doing some reading about the kernel and I think I'll give it a go.
[Desire Android Development] StrongOneX:
i know its just half finished, but still.. just put some big red letters over the post DEVELOPER ROM - NOT FINISHED
[Desire Android Development] Mad Majk:
Hehehe! This thread is preatty funny I must say. People are requesting devs to make ports, open new threads, stickys almost, because they can't wait a few weeks. How old are You guys? Seven?
[Desire Android Development] kevinye:
I'm afraid there won't be a perfect ported version until the source code comes out.
[Desire Android Development] StrongOneX:
i just want microphone to work then im happy
[Desire Android Development] JDouce:
i know there will be no perfect port till the source is out but there a 3/4 ppl working on it... and just depends how awsome those guys are :P
[Desire Android Development] Kollegah:
Hi

10 zeichen
[Desire Android Development] deovferreira:
My guess is they aren't, the current kernel is fine. Of course we should try to port the desire to more recent kernels to make it future proof.

The new kernels have improvements on the CFQ scheduler and better memory management. However, appart from bluetooth, I don't see any problems being solved by kernel changes.
[Desire Android Development] StuMcBill:
Out of curiosity, what does updating the Kernel enable us to do?

If we get it to the same level as the Nexus One, does that mean we can install Nexus One roms??

I am guessing no, but I just want to understand the process?

Cheers

Stu
[Desire Android Development] JonesWTF:
What do you think we should work on, if not the kernel?
[Desire Android Development] Kali-:
1) Froyo is developed with 2.6.32.9 kernel and use some function not available on 2.6.29 (most of the froyo rom work but never will be 100% compatible with this kernel)

2) Froyo ROM source is not available, fix library or userspace tool is not possible, kernel source is available :D
[Desire Android Development] deovferreira:
Did you read that somewhere or do you know for a fact that it is true? There is few relation between software and the kernel in this case, there might be changes in the OOM killer and memory management but that is probably it.
[Desire Android Development] deovferreira:
Userspace mostly, but when the source becomes available I guess it will be easier to deal with most of the problems.
[Desire Android Development] Kali-:
so, not only userspace

for what is available there are 3 solution:

1) backport from 2.6.32.9 -> htc 2.6.29

2) port htc stuff to 2.6.32.9

3) wait full froyo source

just for info, i'm pretty sure the released htc source did not match the stock binary :/
[Desire Android Development] deovferreira:
Maybe not, some user mailed them and they said they were removing the proprietary bits (which are not allowed by the license, btw). However, we have no way of knowing this.

Also, some users have compiled kernels that work fine from their source.

I will try to boot my 2.6.33-cyanogenmod port again later today.
[Desire Android Development] gr0gmint:
On a sidenote:

Right now im trying to patch the kernel, so that it can boot from SD card with if you press some key during boot. Figured it'd be a good idea, with all this Desire flashing paranoia
[Desire Android Development] mardox:
i am strongly considering trading my desire for a nexus one because all i really want is stock android, dont really like sense ui (before you ask why i got the desire, i got it because it was available on cantract in my country and the N1 isn't available at all) but i do not see the need for this if froyo is fully ported to the desire.

so my qeustion is, is it possible to fully port a 100% working stock froyo rom onto the desire in a reasonable time frame?
[Desire Android Development] Dactylion:
y it is. it will happen in 2 monts or earlier
[Desire Android Development] sruon:
once froyo sources are available, it will be much faster.
[Desire Android Development] Kookitza:
When it's gonna b?
[Desire Android Development] sruon:
according to Google, few weeks.

http://twitter.com/googleio/status/14385195791

According to unofficial news, HTC received them this weekend so we can hope for them very soon.
[Desire Android Development] Kookitza:
10x 4 the info m8! ;)
[Desire Android Development] Kali-:
why not?

we have the binary the source and the configuration, this is not to difficult to verify
[Desire Android Development] deovferreira:
How will you compare things? By comparing the binaries? Imagine they use in-house compilers, the generated code will be different :)
[Desire Android Development] Kali-:
just try to run both, compare the config ...
[Desire Android Development] deovferreira:
Guys, I just got 2.6.33-cyanogenmod to boot. Well, kind of. It boots, then I can't actually interact with the touch screen, working on it, I think I know the reason.

There is really not much I can show you, but here goes nothing:

# cat system/build.prop | grep -i desire
ro.product.model=HTC Desire
ro.product.name=Htc_Desire
# uname -r
2.6.33.4-cyanogenmod
# uname -a
Linux localhost 2.6.33.4-cyanogenmod #4 PREEMPT Sat May 22 14:39:19 WEST 2010 armv7l GNU/Linux

Also, as I have said before, the fact that we can't write to /system is not a kernel limitation, it's way deeper in the SPL, empiric results after a remount:

defer@oni:~$ ~/Apps/android-sdk-linux_86/tools/adb shell
# touch /system/bin/test

touch: /system/bin/test: Out of memory
[Desire Android Development] Kali-:
yes, not kernel related, i hope paul can get a better spl

this is not a big problem but is very annoying
[Desire Android Development] JDouce:
yea as for the system r/w issue... is any1 working on this .... its be cracked befor for other htc devices and the desire source is available now
[Desire Android Development] Ramedge:
Apparently the Evo 4G has been rooted already - Not sure if they've got full R/W in /System but it sounds like they might of.

Surely full root would be the answer to many problems with this port?
[Desire Android Development] deovferreira:
Not really, r/w in system is required for pretty much nothing. It's just a convenience thing, we can still have r/w from the recovery.

If anything, a big thing would be flashing the recovery image to mtd1
[Desire Android Development] JonesWTF:
I actually made an attempt at editing mtd1 earlier today to try and push a custom recovery, but it's currently beyond my understanding at the moment. I'll have to do a bit more studying into the subject first, I think.

This was the page a was using to explain what to do;

http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images

I don't know if you may already know this stuff, but maybe it will help?
[Desire Android Development] deovferreira:
Well, i know the process, I used it to boot the 2.6.33 kernel.

The mtd1 is a tricky case, I strongly believe we won't be able to do it without SPL changes.
[Desire Android Development] JonesWTF:
Is there any way to extract the SPL so we can reverse engineer it, or do we have to wait for an engineering SPL to be released/leaked?
[Desire Android Development] ahmgsk:
can anyone provide me last worked with max things working froyo port

with list of not working things

i hope i can remove abt 4 hrs for this today but at later part of the day

post it here or pm me

thx

or else i shall start with it from beginning
[Desire Android Development] myth1001:
This is probably the latest progress that I know
[Desire Android Development] sruon:
3G and HSDPA worked fine for me as I pointed it out in an earlier post. Might be related to different carriers.
[Desire Android Development] ahmgsk:
thx will check it -> i will hav quick look

and work on it
[Desire Android Development] stingerpl:
Behnam - the guy responsible for porting HTC Hero to 2.1 is buying a Desire. He just tweeted that he is going to do some dev for it so you guys are going to get some help pretty soon! :)

http://twitter.com/benocharm
[Desire Android Development] DocRambone:
Good news, nice to see more skilled devs working with Desire.

And good work from the devs in this thread to :)
[Desire Android Development] ahmgsk:
Starting work on desire Port Of froyo now!!

hope i solve camera and audio issues
[Desire Android Development] vuoshino:
thanks. you're the best!
[Desire Android Development] sruon:
I have to say, thanks AdamG, Kali, gr0gmint, deovferreira, ahmgsk and everyone else for the work and the valuable inputs.

(post count+1)
[Desire Android Development] Kollegah:
my desire doesnt boot
[Desire Android Development] JDouce:
cant wait for the port ahmgsk ... and thanks to every1 above for the awsomeness of u guys
[Desire Android Development] kingchris:
Double post. ..
[Desire Android Development] kingchris:
@kollegah

A few pages ago i posted an other Boot.img try this
[Desire Android Development] setenza01:
Is there a link to download a froyo test rom for desire ?

-------------------------------------

Sent via the XDA Tapatalk App
[Desire Android Development] shawe_ewahs:
Here are de reply:

http://xdaforums.com/showpost.php?p=6601263&postcount=284
[Desire Android Development] ahmgsk:
before i start work on i had to fix recovery wipe and other small issues -> all almost fixed

now froyo
[Desire Android Development] JDouce:
how do we get ur fixed recovery :D
[Desire Android Development] shawe_ewahs:
Can you share the recovery with others?
[Desire Android Development] PsYDoX:
WHOOOOT

Have you cracked the Recovery oO.... Nice One!
[Desire Android Development] JDouce:
i assume its a recovery you gota push in the same way as befor
[Desire Android Development] ahmgsk:
its not flashing to device

u need system now too i have not worked on system permissions.

i m going to share it let me finish everything