yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] ahmgsk:
i m downloading it -> have abt 1/2 hr free to rest.

if i can sort it out i will upload it back with my work.

p
[Desire Android Development] :
Good Luck mate;)
[Desire Android Development] JDouce:
aswome :D hope you can good luck good to have another long time dev working on it
[Desire Android Development] AdamG:
No that is my image they are using because of the *ERE27*, I basically replaced the .prop file with the one from 2.1
[Desire Android Development] sruon:
Yeah it is, gonna look around for more fix.
[Desire Android Development] MaTiCeK-:
ahmgsk eagerly awaiting your findings. :)

And also to all the guys trying to figure it out... You guys are great, I really hope something big comes out of this!
[Desire Android Development] ahmgsk:
its a very dirty port

nothing is working and all unwanted process are running.

i am off to study again next break when i work on it again i will report wat worked
[Desire Android Development] cTrox:
Paul from modaco is also working on a froyo port...

What does he mean with waiting for the source?
[Desire Android Development] Pyr0x64:
sounds like we'll be waiting a while for a port from Paul then :(
[Desire Android Development] :
At least we will get a non sense update;)
[Desire Android Development] gr0gmint:
I got everything working except:

*Microphone

*Bluetooth (forgot about that one)

*HDSPA

*Keeps reverting to EDGE/GPRS. 3G rarely works.

*Camera seems to work, but it won't "shoot" and freezes up.

I don't know if this was said earlier, but to resolve the graphics glitches, just replace the files in /system/lib/egl with the HTC ones
[Desire Android Development] sruon:
That's interesting, which files did you use for radio and bluetooth?
[Desire Android Development] gr0gmint:
Stock radio. Bluetooth didn't work, my mistake.

I've done these changes:

*Stock HTC kernel with modified ramdisk

*All files from froyo, except:

- /system/lib/modules/bcm4329.ko

- /system/lib/egl/*

- /system/etc/firmware/*

*Modified build.prop

Anyone interested if i post some of these files?
[Desire Android Development] sruon:
Yeah, I am. :3

Do you still have system process ****ing up?
[Desire Android Development] gr0gmint:
Hold on, i'll make a ROM
[Desire Android Development] soulpilot:
amazin jus amazin ..froyo looks around the corner !!
[Desire Android Development] gr0gmint:
No, hows that?
[Desire Android Development] sruon:
on Adam's ROM the system process freezes every 3 seconds, giving you the wait or kill process message
[Desire Android Development] gr0gmint:
No that does not happen. I suspect it might be because i used and modified the init files from the Froyo update
[Nexus One General] Azuske:
Please post a link to a dump of FRF86 (Froyo)?
[Nexus One General] knightnz:
There aren't any. When there are, this forum will explode and you'll know all about it.
[Nexus One General] jamesyb0i:
http://tinyurl.com/froyodump2-2
[Wildfire General] Zd0s:
a new android device has just come out called the HTC Wildfire http://www.htc.com/uk/product/wildfire/overview.html

the design sort of looks like a desire with a few nexus one buttons.

well theres no forum for it yet so.... an administrator could make one so people that get one can use xda to tweak it.

Thanks
[Wildfire General] cmstackar:
Its not even released yet, so I'm betting xda can wait a while. To me it seems like a hero in a different case
[Wildfire General] onlyankush_s:
Yup but it is releasing soon.

hTC Wildfire Official Release Date is June 14th 2010 at T-Mobile, UK.

And it will cost about $200:)

I m also eagerly waiting for this device.
[Wildfire General] Slave1:
Had a play with a prototype last week. It had a trackball but the shipped version will have an optical track pad like the Desire.

I quite like the unibody constuction on the Legend but this means you could plug in an extended battery as you're not constained by the size of the case.
[Wildfire General] Ultima94:
Phone looks pretty nice was thinkin about gettin it or the mytouch slide
[HD2 General] kclive:
I am having an issue...I have installed my Garmin XT Mobile on numerous phones in the past and it worked just fine for me. I installed it on my HD2 and the install went just fine, however, it won't connect up. When I have Garmin running and go into the System/Remote Gps folder it is showing Garmin is on COM4: COM4 What com should this be set at to get it to connect? If I click on the Disable icon at the bottom right corner of the screen it will let me choose COM1: Bluetooth, COM2: Bluetooth, COM4: COM4, or COM9: 7500 COM port. No matter what port I choose it won't connect up. Am I missing something here?

Any help would be GREATLY appreciated.

Thank you. .
[HD2 General] kclive:
**UPDATE**

After upgrading to Version 5 everything works just as it should
[Nexus One Q&A, Help & Troubleshooting] dany74q:
Hi there,

I am building a .zip file that will install RTL support for some applications , and got stuck at the update-script part.

I have two files named CalendarFix.apk , and GalleryFix.apk , I would like to install them directly from the recovery.

Tried to put them both in system/app and data/app with :

copy_dir PACKAGE:system SYSTEM:

set_perm_recursive 0 0 0755 0644 SYSTEM:app

copy_dir PACKAGE:data DATA:

set_perm 1000 1000 0771 DATA:app

But no luck , they wont install .

Is there a command that I need to use to install them ?

I thought to use run_program , though I did`nt see it in any rom update-script code.

I need to -

Extract CalendarFix.apk and GalleryFix.apk , delete the old once (Calendar.apk,Gallery.apk) and install the new once .

Any help would be appreciated,

Danny.
[Nexus One Q&A, Help & Troubleshooting] behelit:
http://www.robmcghee.com/android/creating-an-android-update-zip-package/
[Nexus One Q&A, Help & Troubleshooting] dany74q:
Fantastic , I managed to work that out.

Thanks.
[Upgrading, Modifying and Unlocking] archers3001:
Hi guys just asking if theres going to be a updated HTC IMEI Update Tool that would cover the new hand set's like hd2 nexus one and so on.

As I played with the old one with my hd2 but just would not see the phone at all.

Please note my phone fully unlocked out the box and used all day long just wonted to play :D
[Upgrading, Modifying and Unlocking] thefuryx:
im looking for simmilar program/app for HTC wildfire ;)
[myTouch 3G, Magic Android Development] ramersonw:
Great news Sanpei. Now maybe our android 2.1 will work better on new radio.
[myTouch 3G, Magic Android Development] Krzysiec:
Thats more than great news ;) What can we say more ? Thank U for that ;) But there are not many devs who wants to play with kernels for Magic ;P You were the only one ;) Hope one day U`ll bring us good .29 to live :) Cheers !
[myTouch 3G, Magic Android Development] Case_:
And it only took you about six months to share this info with others. How great...

Nevertheless, thanks.
[myTouch 3G, Magic Android Development] xaueious:
Case_ at least he is sharing it now

sanpei I'm working off HeroC source:

http://github.com/toastcfh/CdMa-HeRoC-2.6.29/

The correct changes were made in board-sapphire files already. Might be other stuff.

All devs need is to add the EBI1 config!

there are additional mods sanpei has not mentioned. maybe that's why his kernels have been a little finicky. but this is probably it: http://github.com/cyanogen/cm-kernel/commit/fef60feb4caa22d82a35636b1679243e67512ce5#L7L160

CPU freq tablets already fully support our CPU there. Overclock should work as well.

As for eflan, I'll have to play with it

toastcfh sent me a compile last night with board files added, but I think there was still some stuff missing, but...

EBI1 was why my device didn't boot! Going to compile that and see what happens now!

As for him not sharing it, at least he is sharing it now.

Thanks sanpei my fellow countryman :)

I feel dumb for compiling the source when the board files wheren't even there. I don't know if this is all I needed to do but this is a big step in the right direction. I have no knowledge of how stuff like this works. I am not a dev still.

sanpei I wish I had better understanding of all this code. But I don't. In any case thanks for sharing this with us now.
[myTouch 3G, Magic Android Development] toastcfh:
the only two reasons i didnt make the patch public is one because of the EVO (superconic) source in it, second in hopes that it wouldnt be the last mess up by HTC. the source has ony been up for 3 or 4 weeks. so the 6 months idk. i released the source as i got it to compile. i had other projects also like making source for the CDMA heroc. which oddly enough the patch says heroc on it :/ but lacks source for our device. as soon as i finished the heroc project of creating board files compatible with the heroc, i moved on to commitig the board files for the other devices. starting with the GSM hero (which was unfinished) and then the Sapphire (also unfinished). all know devices have been commited and someone at least informed of the files being there. im a busy person and have a life of my own. the patch did me no good while i was creating board files for the CDMA hero. once i finished that i turned my attention to releasing the rest of the devices. but yeah i doubt HTC will make this mistake again for sure now that its publicly announced.

so yeah i only was trying to protect a interest that everyone can gain from. ;)
[myTouch 3G, Magic Android Development] xaueious:
interesting none the less...

first try didn't go (defined ebi1 in .h file, compiled and flashed)

i'm giving it another last chance, this time defining ebi1 in the kconfig.

i might be missing more stuff than this.

edit: I'm blind. didnt' edit acpuclock properly. lol. doing another compile.
[myTouch 3G, Magic Android Development] toastcfh:
for the color issues look into ur panel settings. its most likely the reason the color is messed up. maybe wrong settings ;)
[myTouch 3G, Magic Android Development] xaueious:
Holy **** it's booting

Colors look okay actually. My touchscreen is broked though!

Cursorsense too lol

BUTTONS ALL OKAY
[myTouch 3G, Magic Android Development] capychimp:
sounds interesting :) lets see what you get fixed :)
[myTouch 3G, Magic Android Development] klothius:
I'm hoping you can get it to work properly, good luck mate, crossed fingers !
[myTouch 3G, Magic Android Development] xaueious:
All you need to start with to get 2.1 roms working

Not all of sanpei's changes are needed to fix what is on toastcfh's github.

My .config is still messed I bet.

In Cursorsense pretty much everything is broken.

http://www.youtube.com/watch?v=lasToRLQQCA&feature=player_embedded

I HAVE A BOOTSCREEN ON AHERO

For devs, if you are working off toastcfh's github source, this is what you need to get it working:

a)

acpuclockarm11.c sanpei mentioned

b) touchscreen fix by using the aosp synaptics driver here (rename this file)

http://github.com/toastcfh/CdMa-HeRoC-2.6.29/tree/master/drivers/input/touchscreen/

synaptics_i2c_rmi.c-AOSP-fix -> synaptics_i2c_rmi.c

c)

make changes to 'Kconfig' here, and enabled the config option during make

http://github.com/cyanogen/cm-kernel/commit/fef60feb4caa22d82a35636b1679243e67512ce5

The board files that are up work perfectly.

d) work off my config or similar:

http://pastebin.com/cKkBNtKJ

e) download aHero for GSM Hero here:

http://xdaforums.com/showthread.php?t=638584

e) PROFIT

note that all apps are force-closing on aHero right now. but launcher works. boot screen works. radio works.

I will play with this later. For now I need a working phone.
[myTouch 3G, Magic Android Development] xaueious:
Did a wipe. Most apps work. Random stuff is broken but that's okay.

But I talked to zinx in irc. He said CM-Kernel actually already supports new radio Magics.
[myTouch 3G, Magic Android Development] toastcfh:
commited the changes above to alow the sapphire to boot

github.com/toastcfh
[myTouch 3G, Magic Android Development] xaueious:
It boots but the drivers are broked. I messed up my source and don't want to touch it for a while.

Sanpei?
[myTouch 3G, Magic Android Development] sanpei:
do you know when the desirec_2.6.29 had been released? or, do you think that I was a time traveler?

I found this leaked patch 1~2 weeks ago. I was working on my career jobs these days (I even didn't have time to visit here), and I thought that others would find it and share with each other, so I didn't post it immediately.

yesterday, when I visited here, I found that it was not mentioned by any other people. so I decided to write something.

and hope that it won't surprise you, the .29 and .32 kernel builds made by me are not based on htc-kernels, and I never use any files from HTC. I just made aosp kernel working with our devices.

to put it simply: for 32A device, I don't need any pieces of codes from HTC, I just need the information about radio versions and interfaces between hardware and software, and I already know/understand some of them.

to be honest, I never change my mind. I won't open "my" sources before I would have considered that they could be open.

but this patch, it is leaked from HTC's sources and I don't make any efforts on it. so I think that if I shared this information, all of you will get what you want, and it is not conflict with my "moral standards" what I had mentioned in previous arguments.

maybe you and others think that I am a selfish man or bad person. I don't care. take what you want, and leave me alone.

but if you and others could reconsider what I am, and think about if I could be a friend of you, I will be very happy.
[myTouch 3G, Magic Android Development] xaueious:
Oh but we (I) did make a thread. It should be on the 3rd page or so by now. This ROM is flooded by rom ports and has zero dev activity. There's just hopelessly few devs on Sapphire forums. That's why all you see see are ports and no AOSP stuff.

But since you have a .3X kernel anyways I don't see you really needing this. Toastcfh did remind me to replace the synaptic touchscreen driver to get it working properly for the Sapphire.

Or we could use your source. Because I have no idea what I need to do to fix wifi and camera on my port. I have CM5 working with sound, rotation, sleep, Youtube, 3D on a 32A Magic. It's not my phone though so I wont try much more on it now.

I first booted into Cursorsense, then aHero and finally Cyanogenmod 5. CM5 as a ***** because squash fs didn't compile, so it broke my xbin completely. I worked around it by extracting xbin through my virtual machine since my PC runs windows before I realized I can just install busybox from the recovery onto the phone. I pushed the lib*camera*.so files from aHero and after data wipe I had ZERO force closes, bluetooth + audio + video + rotation. Not bad for a noob, but I have no idea how to fix. This isn't my career path :P

toastcfh helped me a lot

Question

Doesn't it make more sense to get Cyanogen's kernel source working? All it needs is AMSS 6355 support, and the code difference doesn't seem to be that great. It already has up to AMSS6350 the last time I checked. It's actually not that bad to add new phones, but their kernel source is kind of different than HTC's now that it's now harder to just add new phones. zinx expressed interest, and I'm sure bcrook is interested as well.

We can use a plain HTC source and adapt it, but CM already should have a lot of 32a bits in it including native EBi1 support, compatible makefiles and a kernel version ready to boot any 2.1 rom.

The major differences between the AMSS versions 6350 and 6355 seem to be in the multimedia msm drivers. That's probably less than 10 files to edit in total.

The existing CM5 config should build new radio 32As no problem.

But is there a point anymore? Sanpei your kernel seems pretty darn stable right now. If I figure out how to throw it in Koush Anykernel we can probably have working ports for every ROM out there. The only thing is since you have source code sometimes the local version doesn't work well with some ROMs. So yes we still want your source because it works well.
[myTouch 3G, Magic Android Development] sanpei:
no, it is not that "my" kernel works well, it is the original aosp kernel works well, except some minor bugs (which are already fixed in my kernel build). and I think that .32 is more suitable than .33, since .33 is marked as experimental by Google.

some "custom" mods of .33 use older drivers which are taken from kernel sources of an older version. I can't sure if these drivers could work properly with new radio, though you could boot your device and most features will works.

and sorry, I don't want to talk about other's works. but I must repeat again: all "custom" kernels are just original kernels from Google/Qualcomm/HTC's repo, and with little public patches made by some real programmers.

so don't care about their brands. you should find out what they are using: drivers, hacks, and patches of features.

if you use a lib (in userspace or android layer) because it is necessary for a radio version (because the lib and the radio have some conventions directly), then you should choose the kernel driver which could work with this lib. KERNEL itself is NOT the KEY problem in this case.

in fact, the most programming jobs I had done are in android layer; and if I have spare time, what I would work on are in android layer too. (except OC or other things which do most things in the kernel).

for devs who don't have enough experiences in kernel jobs or programming, and if they want a most stable kernel which would works with new radio, I recommend them start from htc-kernel. it's always more reliable, because we (I, you and others) can't know every changes of hardware configurations between each radio versions, and HTC knows these things exactly.

but why I would still be working on .32 kernel?

because I think that I could fix every bugs (if we would encounter) by myself :o, and I want to learn and remember the new changes Google made in kernel. thus, I wouldn't need to learn these things again when newer versions of android (they might need these changes in kernel) will be coming.

a kernel and some libs for new radio, and they could work with both AOSP and HTC ROMs, it's my current goal. and you could see giant's work on AOSP ROM, I think that we are more close to this goal now.

"my" sources..., I will think about it (and I often considered if it's the time). but I am rather obstinate :)

and for problems of using htc-kernel, I can't remember all the details of my tweaks and tests. maybe I will take a look for you. but I won't make any promise, since I really don't have enough time at current. :(
[myTouch 3G, Magic Android Development] GuestK00288:
Here is a slightly separate but related thought.

It seems to me (and I am the first to admit I am not knowledgeable in this stuff so I could be wrong) that one of the following statements are true regarding the devs working on the G1 and other phones:

(1) Either they are not very knowledgeable when it comes to kernel programming and development (and so they are not capable of getting a kernel working on the 32a like Sanpei did), or

(2) The other devs are not interested about the 32a user community enough to spend their time providing us with support (and so they do not focus their time getting a kernel working on the 32a).

My guess is that it is a combination of the two possibilities above. Devs are not as knowledgeable as we think when it comes to kernel development and the required changes HTC and qualcomm do to get a kernel working on different phones especially the 32a, and even if they could do some reverse engineering and some hacking that they don't want to spend the time and energy supporting the 32a user community which is probably a lot smaller than the 32b community. (I don't fault anyone for not wanting to support a community - it takes time and there is probably very little financial reward.)

I believe the lack of a working new radio kernel for 32a supports Sanpei's view that other devs should not be branding the kernel with their names after they have done some minor tweaks. I believe that anyone capable of doing major work on a kernel worth re-branding the kernel to their own name would have already been able to get it working on the 32a properly.

But what do I know.

Lastly, I don't mean to disrespect any dev with these views. All of the devs have contributed - big or small - to the user experience and all devs have done a lot more than I will or could ever do to support Android. However, I do think we should be honest about what we can and can't do and what we take credit for.
[myTouch 3G, Magic Android Development] GuestK00288:
It is also interesting....

(1) How xaueious has good things to say about "Sanpei's" kernel

(2) How Sanpei refuses to call it his kernel, or to take credit for the 6.35 .32 kernel, and how Sanpei actually plays down or belittles what he had to do to get the .32 kernel working on the new radio (something which no one else has done), and

(3) How guys like Alan who know very little about kernel development choose to criticise the .32 new radio kernel ported by Sanpei, going so far to call it "garbage"

All of these things point to people's approach and character.
[myTouch 3G, Magic Android Development] FirstNoobToBrickHisPhone:
I really wished you guys would get along and share your works, this conflict is really tearing our community apart.

The Rogers RUU can't come out fast enough...
[myTouch 3G, Magic Android Development] xaueious:
If anyone wants to work with the toastcfh source you guys can pm me so i can add more info...
[myTouch 3G, Magic Android Development] carz12:
Ok, Ive done it, cm5 with 2.6.29 on new radio, need to fix wifi and camera, very cool.
[myTouch 3G, Magic Android Development] helderp:
I guess this means that we are about to experience CM5 with the new radio. After upgrading to the new radio I feel that it's the way to go, and we should invest more time in this radio instead of downgrading. Hopefully, with the 2.6.29 sources available, maybe it will be possible to adapt the 2.6.33 kernel to work with the new radio. Nice work to everybody involved.
[myTouch 3G, Magic Android Development] xaueious:
I am pretty stumped right now with the source because I don't know how to work with it. I will continue to deduce though because it makes me feel like a dev lol!

I copied the Cyanogenmod driver folder for compiling wlan.ko, and it didn't quite work.

modprobe manually does not seem to want to work.

I've a feeling that the wlan.ko driver generated is not the culprit. Maybe something in the msm board files for sapphire missing some references for new radio since those were kind of generated afterwards by toastcfh, and were not originally in the source. I don't think toastcfh just did the reverse diff to generate the diff files. If you can maybe you should try what sanpei said about the desire kernel and do a reverse diff so we can check the board files, specifically the mmc/sdio stuff that is tied to the wifi code.

About the camera issue, there was a reference to this that seemed similar to the error messages coming through, fixed by Google that might not be in our CDMA Hero kernel source for Cyanogenmod:

http://code.google.com/p/cyanogenmo...ty Version Model Owner Summary Stars Modified

The camera driver is mt9t013

But with all that done, we will get as far as a working .29 kernel that works with Eclair. As far as real enhancements, I think CM-Kernel is much more suited for building things even without support for AMSS 6355 radio right now because it's just so much more far along.

toastcfh has moved on to trying to merge his branch of the CDMA Hero sources with CM-Kernel, and for good reason.
[myTouch 3G, Magic Android Development] carz12:
I have everything but wifi and camera working, 3d gallery works, market, gps, no force closes yet at all on anything but camera, had to do birthday dinner... now back to work on this.

Edit: I'm using the source from htc and reverted the patch, thank you for your insight Sanpei, i was close but had no idea about the acpuclock edit.