yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Apps and Games] stefanclark:
I think its going to be very hard to define the requirements exactly for each app as well a the matching specs on each phone. may I propose that the site will mark a project by some general requirements such as bluetooth - unspecified, not required, optional our required. individual versions/downloads could be marked against the same requirements - you may have a bt version and a non bt version.

separately downloads could be marked as working or not working for the different phones. an app developer could either assign phones themselves or users could 'vote'/report an app as working or not working for a certain device.

when searching for relevant apps for a phone it could show apps marked as working and apps which should technically work based on the requirements.

this voting setup would mean developers wouldn't have to spend forever assigning requirements or marking phones which work with an app.
[Windows Mobile Apps and Games] yngvebn:
This is somewhere along the line I was thinking... Didn't think of the voting-feature though. Great idea! :)
[Windows Mobile Apps and Games] xfox:
i vote for the XDA-Market

better than every other market
[Windows Mobile Apps and Games] julienrl:
modaco users already have a good idea with the apptodate application, incorporating this in a cab market would be amazing.
[Touch HD General] miannaeemd:
Very Sad, I dropeed my lovely Blackstone on ground and It was restarting again & again from Bootloading screen. I sent to HTC for repair and they were unable to repair, they lost the front speaker cover, the phone was not closed properly, now my phone total dead, no respons no charging ?

This much costlier phone and dead only after one drop ? it is very bad I lost all my money.

Is there anybody who can suggest where shall I send my phone for repair ? I am in UAE.

Sorry for my bad english
[Touch HD General] miannaeemd:
Got a call from HTC from an anonymous Number, They promised to resolve the problem.
[XPERIA X1 Q&A, Help & Troubleshooting] troii1818:
when i install this FINGERKEYBOARD it will work on my xperia?? and how can i disable the default screen keyboard.. http://xdaforums.com/showthread.php?t=487677
[XPERIA X1 Q&A, Help & Troubleshooting] harveydent:
Yes, it works on the Xperia. You can set it as the default keyboard with the SIP Changer app or SK Tools
[myTouch 3G, Magic Android Development] iaio72:
hello guys

I wanted to know if i can change spl on my magic, putting one

engineering, I have a perfect SPL 1.33.0007, and I dont have root ...

it's possible?

I've tried many methods to get root, but without success and hoped

that if I change spl, I could manage to unlock my magic

thanks
[myTouch 3G, Magic Android Development] paindoo:
Try this method:

http://xdaforums.com/showthread.php?t=589771
[myTouch 3G, Magic Android Development] iaio72:
thak's, but i can't try, because my magic its no rooted..:(

and ive 32B this is for 32A

thanks
[myTouch 3G, Magic Android Development] vmaxada:
You should probably try this method. If than doesn't work for you, you should use a goldcard to change your SPL. Also check this thread for the goldcard method.
[myTouch 3G, Magic Android Development] iaio72:
the first its a method only for 32A mine its 32B :(

the second how to create a goldcard, i already tried and when I do the update with the sappimg.nbh eventually gives me the "main version is older "

the third method (remote not allow) ive tried...without success.....
[Hero CDMA Android Development] maejrep:
So, since HTC is now almost 3 months past due releasing the kernel sources, I've been trying to adapt the GSM kernel to compile and work with our devices, by disassembling the stock kernel and going through line-by-line of the source to see what needs changing.

I started by copying all the '*hero*' files to be '*heroc*', and renamed all the symbols to be heroc as well. Then pulled /proc/config.gz to use as a base config. Also had to fix up the Kconfig's and Makefile's, as needed, to be able to support HEROC-specific stuff. That more or less gets it to a point where you can compile the kernel successfully, although it's still just a GSM kernel with the name and mtype of heroc.

Then I imported the stock kernel (extracted from boot.img, then decompressed) into IDA as a ROM, setup the CONST segment of string data, imported the symbols from /proc/kallsyms using an ida .idc script, and analyzed the remaining areas of the ROM. At that point, I had a virtually fully analyzed binary ROM in ida, complete with symbols. Then went through and renamed the important symbols from the board-heroc* segments as needed to match what is in the source. I also set up some of the more complicated structures/arrays to make them easier to identify.

I found several differences between the stock heroc ROM, and the make-shift hero-turned-heroc source code, and fixed most of what I came across, or just left notes for things to investigate later. What I have now is a hybrid GSM/CDMA kernel that will likely not boot on either device :P But I figure since I've put as much time into as I have, and I'm sure there are people more familiar with IDA and ARM than I am, I'm putting my IDA file out there for people to start from. If you're not familiar with ARM assembly, this is absolutely useless to you, so you probably shouldn't bother.

I've spent 2 sleepless nights on it already, and still can't get anything to boot. I also tried to get htc_fb_console working so that I could at least see where and why it was dying, but that hasn't worked out well either.

So, by all means, have fun: http://madcoder.binti.ehpg.net/~madcoder/stock_kernel_heroc.i64

It was created using IDA 5.2, 64-bit, but I don't know how well other versions are with compatibility. Oh yeah, it's 35MB

And if you make some breakthroughs, please post about it here. When I get some time, I'll make a patch set to go from the released GSM kernel, to what I have now, and put that up here too.
[Hero CDMA Android Development] 5tr4t4:
Thank you, sad but true

I just wanted to say thank you for this work and express how sad it makes me to see the necessity of reverse-engineering in an OPEN SOURCE kernel. I never thought I would see the day.

I would be very curious to hear from you about the specific differences your disassembling unearthed. Can you say with certainty that the Linux kernel code has indeed been changed to work on the CDMA Hero? I mean it's not simply a matter of some missing driver code or other userspace stuff? If so, this would be pretty damning for HTC.

Thanks again, it's amazing to watch the XDA developers' progress in spite of the barriers put in front of their work.
[Hero CDMA Android Development] maejrep:
The majority of differences I found were in things like heroc_fixup() where it doesn't check for engineerid/skuid/etc; different camera driver (s5k3e2fx, vs cy8c); fewer checks for multiple pieces of hardware (which is weird considering the stock phone's kernel supports 4 devices) based on system_rev; wrong vreg_get() strings; etc.

The source that HTC released *does* appear to have all the support we need. With modifications to Kconfig and Makefile, and ignoring the missing board files, you *can* compile the kernel directly, using the stock /proc/config.gz, which means all the necessary drivers are already in the GSM source. It's quite obvious that they had a working kernel tree that supported the GSM phone, plus our 4 CDMA phones, and they simply yanked out the CDMA board files and Kconfig changes, before releasing the source code.

What worries me is that I can't get a console, so it's incredibly difficult to find out where it's dying at. If I could get even a serial console to work, it would make this task so much easier. I think my next step is going to be to load up my hacked kernel into ida, and see how different the two are -- that might be easier than translating asm into C and comparing that way. If I can just compare the assembly for the two, it'd probably be easier.
[Hero CDMA Android Development] markachee:
Not to derail this too much, but which 4 phones do you mean? does it name them in some way?
[Hero CDMA Android Development] maejrep:
MACH_HEROC (sprint hero)

MACH_DESIREC (vzw droid eris)

MACH_HEROCT (not entirely sure, maybe bell south hero?)

MACH_NEONC (neon is supposed to be the touch dual, which afaik has never been planned as an android phone, so I'm not sure what's up with this name either)

You can see those in the /proc/config.gz on the phone (ungzip or zcat it first ;)), and just search for "CONFIG_MACH_".

Also in the htc_wifi.c source, you can see references to espresso, and many others.
[Hero CDMA Android Development] Mr. Biggz:
Would it be possible to port the moment kernel over and use that since its the same processor type and then fill in the things we need?
[Hero CDMA Android Development] travo1:
I was talking to zefie not too long ago and he was saying the hero kernel is so much more stable than the moments kernel... just my 2 cents.
[Hero CDMA Android Development] flipzmode:
Keep up the amazing work mad man. :)
[Hero CDMA Android Development] abcdfv:
Yeah, my fiance went through 2 moments, and they were so buggy she switched to the Hero. No problems since.
[Hero CDMA Android Development] Is_907:
+1 for keeping up the good work!

:beer: (Does that emote work on this forum? I hope so...)
[Hero CDMA Android Development] toastcfh:
bumping this so it doesnt get buried 3 pages again:D
[Hero CDMA Android Development] gu1dry:
I thought you said you were going to bed :p
[Hero CDMA Android Development] toastcfh:
i was till i had to refresh again:D
[Hero CDMA Android Development] maejrep:
Yeah, I basically put this on hold, due to work priorities (happens a lot unfortunately :/)

But with the news that HTC may be releasing the source soon, this is probably not worth continuing anyway :rolleyes:
[Hero CDMA Android Development] tkirton:
Honestly, I would continue it. Nobody's sure that HTC will release the source code (HTC said they would release the source for the "Gero"...we're hoping that was a mistype).

I have a feeling they won't release it anytime soon and you'll probably solve the entire issue with the cameras and more before that source is released.
[Hero CDMA Android Development] toastcfh:
bump.... its on the second page:D
[Hero CDMA Android Development] bcnice20:
Yea def keep the good work up HTC said over the weekends tht came and went so now all we got is you my good man
[Hero CDMA Android Development] toastcfh:
man we gotta get this thread stickied!!!!
[Hero CDMA Android Development] toastcfh:
agreed... lol

anyhow i think this will work out before the htc hope does. bumped to the top:D
[Hero CDMA Android Development] maejrep:
So, with some inspiration from NetRipper, I started trying to find a way that I could see how far it gets in the kernel booting before it stops, since I still don't have a console. Unfortunately, his suggests were LED-related (particularly gpio-enabled), and we don't have any of those. Did find one reaction that is very hard to miss, and luckily very easy to trigger: reboot via gpio :p

So now I'm stepping through the code, trying to find at what point in execution it stops rebooting and just hangs. So far I'm in init level 4 (of 6). I'm really hoping this leads me to something that will at least tell me "well THERE'S your problem!", and I can reverse the stock kernel asm to figure out what is different.
[Hero CDMA Android Development] david_ag:
Don't get discouraged man, and THANK YOU so much for your hard work!
[Hero CDMA Android Development] wtphoto:
I know several people have already said this but, thank you for the work you are doing. If you can pull this off before HTC releases we could show them that despite the bariers that they put up devs like you will prevail for the community.

Thank you again
[Hero CDMA Android Development] mrinehart93:
Or (hoepfully not) HTC decides that we can handle updates on our own, and refuses to push out anything new to us :( But screw HTC, keep reversing this kernel!!! :)
[Hero CDMA Android Development] wtphoto:
so if they decide that then no big deal if we have the kernel source since it seems that our devs to a better job anyways.
[Hero CDMA Android Development] obelisk79:
lets not ignore the hard work htc's devs do writing and adapting code to get our hardware working on the linux kernel. It is by no means a simple task, that includes the quality control that is necessary to ensure it isn't buggy and cause crashes and problems. That is a lot of time, money and hardwork HTC invests. While devs here can devote time to picking through and optimizing the excellent code-base the many developers who have contributed to the linux kernel and htc has invested to making it functional on this phone.

Yes, I find it extremely frustrating that we do not have kernel source code available yet, however HTC has created an excellent product that I personally enjoy on a regular basis.
[Hero CDMA Android Development] david_ag:
+1 Great post in the middle of the storm, I totally agree
[Hero CDMA Android Development] Nanan00:
You show all the classical signs of Stockholm Syndrome.

HTC built a phone with the intent of using the Android OS, a platform designed with the explicit intent that it remain open and free via GPLv2, then refuses to share even the slightest hint of how they jury rigged the GSM code to run on CDMA. If HTC didn't alter the kernel then we would be able to use the GSM rom with its camera driver, etc. rename some files from *Hero to *Heroc and should be well, but this is not the case.
[Hero CDMA Android Development] chuckhriczko:
I have to say you have a good point but so does Obelisk. If it werent for HTC we would have to build the kernel to work with the phone from scratch. Instead we have to reverse engineer it. This sucks big time but at least we don't have to build it from scratch.
[Hero CDMA Android Development] Nanan00:
Ah nope, CDMA functionality was a big part of why 1.6 got made in the first place and it came out prior to HTC making the CMDA Hero. If anything HTC is 100% responsible for this whole mess, instead of porting the Rosie crap to 1.6 they just jury rigged CDMA to work with existing software. The 1.5 running on our phone is the Windows ME of the Android world, it mostly works but a good number of apps and whatnot FC, and when we ask for support we just get laughed at.
[Hero CDMA Android Development] black7:
:eek::D HAHA

It's not THAT bad ;)
[Hero CDMA Android Development] david_ag:
Man, you take it so far....

The 1.5 is bad, but not THAT bad. We will eventually get the source code. The GSM Hero didn't see it's source code until after SOME time after the phone was released. I understand everyone's frustration, but we will get it in some time. I am sure the community pressure will make them give it up sooner rather than later. In the meantime, I am enjoying my Hero and will be more than happy to do so and see the improvements we can get out of it with the release of the kernel. Patience is a great virtue.
[Hero CDMA Android Development] miamicanes:
Well, just to mention a few things that have positively driven me *nuts* about 1.5... things we could fix ourselves if we could at least get at the CDMA-specific part of the HeroC's kernel:

* According to my status bar, I've had 12 new, unheard voicemails since November. In reality, I have no new messages. Ironically, I think THIS problem began right around the time the first service release was applied...

* The only way I even DISCOVER new voicemail is the arrival of a text message whose general body content hints that it's supposed to be notifying the phone of the arrival of a new message.

* No android.gestures.* means I'm stuck with the horrid soft keyboard in the meantime, because all but one of the graffiti-1 input apps require 1.6 or better. The one that doesn't require it has so much lag, it's practically unusable.

* Did I mention yet that I really, REALLY hate the fact that accidentally rolling the trackball while trying to take a picture one-handed throws it out of camera mode and into photo album mode?

* Even when the voicemail indicator worked, the option to flash the trackball led didn't.

* HTC's lockscreen is a half step short of useless, but if you use the Android lockscreen or a thirdparty lockscreen, you can't disable HTC's... pick your poison: random unlocking in your pocket, or the annoyance of having to do two different unlock gestures.

(takes breath)

And those are just the things I can think of off the top of my head. With the possible exception of the gestures library, these are almost all things that would have been fixed *long* ago if the source to the kernel were available. And let's not forget about the GPU acceleration that's doing nothing besides sit on the die and wait for something to make use of it.

Give a man a bugfix, and he'll be happy for a day or two (until he discovers the new ones). Give him the sourcecode, and he'll be empowered to fix them himself (or at least content to rationalize & tolerate their continued existence, because he could fix them himself if he thought they were annoying enough).
[Hero CDMA Android Development] david_ag:
Its a matter of opinion and YMWV.

I do understand your frustration and completely respect your opinion.

I have never had one issue with my voice mail, I actually like the soft keyboard and lastly, I have no issues with random pocket unlocking. So, I can understand that some people are way more pissed off than others but I personally don't have THAT much issues.
[Hero CDMA Android Development] maejrep:
12 hours at work, followed by maybe 6 hours of staring at assembly, can also make some people a little more frustrated than others. :eek:

I agree 100% with obelisk -- I'm not trying to say what they've already done isn't absolutely invaluable. The work that HTC and Google did to support the early devices actually enabled users of others phones (winmo) to run Android as well. So at least their drivers are reusable, and hardware within various phones remains pooled from a somewhat consistent selection, making it easy to reuse those drivers. And those things wouldn't have been possible (well... they would have been painfully [more] difficult) without the source code that HTC had already made available.

So yes, HTC has done a great job in supporting the hardware, and I'm sure they've invested a good deal of money doing it. But let's be honest... They knew what they were doing when they got into the Android game, and they knew that their work (at least on the kernel) would have to be made public. It's not like they got tricked into it. And now they continue to slap the open source community in the face by delaying like this. The eventual release of code helps, yes, but it doesn't change the fact that they're ignoring their obligations, and misinforming their customers.

As for the whole CDMA-in-1.5 issue: I think you're confused... They don't have to show us what they did to get CDMA working in 1.5, and they won't have to show us what they are doing to interface the AMSS with the Android platform in 2.1 either. The kernel source wouldn't have enabled us to run 1.5 without their drivers, and we'll still be reliant on them with a 1.6 or 2.0+ system. The work dzo did on getting Android to run on vogue was mostly reverse engineering as well (at least the CDMA part of vogue). At some point, we're still going to be reliant on HTC's proprietary binaries that they *are not* obligated to release source for (under the Apache license). What the kernel source would enable us to do is to fix things that they left out, and tweak, and make a hodge-podge of 2.1 using a 1.5 RIL -- BUT at least the camera would work, because we'd be able to add the support we need directly into the kernel, without waiting for HTC to do it.

That's my rant for the night :o
[Hero CDMA Android Development] obelisk79:
I'm not stating that what HTC is doing by withholding the kernel source isn't completely wrong and frustrating. But you guys are grabbing your pitchforks and torches trying to rustle up an unruly mob as if HTC is the evilest corporation ever. I think there's just a general overreaction to the whole situation.

Yes the GPL demands they release the source upon request and they have yet to comply. I don't work for HTC so I have no idea what kind of legal and corporate red-tape they need to wade through to get the source out. Obviously there is some kind of process they use as every android device they have produced has taken a minimum of 3 months to see a source code release.

What amuses me to no end are the truly ignorant people who make statements to the effect of "**** HTC for not releasing the source, I'm going to get the Nexus One, that'll show them!"

Anyone who's remotely intelligent should be able to realize that the Nexus One was designed and is manufactured by none other than HTC themselves(with some input from the big G also). What a shocker. Of course that is merely an example that sticks out in my mind.

Implying that I am suffering from stockholm syndrome is incorrect. I merely acknowledge that HTC has put a lot of work into making a quality product. Additionally, you may want to put away your tinfoil hat and stop thinking up conspiracy theories and try to do something productive for this community rather than harass one of the developers here who actually tries to improve your experience with your phone.
[Hero CDMA Android Development] Nanan00:
Don't mind me obelisk79, I am just venting. I am frustrated that HTC is/has invalidated the reason I got a Hero in the first place instead of getting an iPhone. I am a hacker/tweaker at heart, a glance at my cars, motorcycle, and computers would tell you that with out a doubt. I got the Hero with the express intent of making my own ROM, with the crap HTC is pulling it is seriously hampering my desire to have this phone.
[Hero CDMA Android Development] obelisk79:
Nothing wrong with venting. I'm just offering the voice of reason for the masses who know no better when they see people's ranting. I am also a hardcore tweaker and gadget-head. Trust me I'm chomping at the bit to get my hands on some source code.
[Hero CDMA Android Development] maejrep:
So, back on topic, I did get the kernel to boot past the ram console, and was able to boot back to recovery while keeping that console intact. Then I got the /proc/last_kmsg from that previous boot: http://xda.privatepaste.com/4712b75b2a

So, this tells me 3 things:

1) I hit a kernel panic while enabling the usb_function_serial (fserial)

2) It can't register any of the smem channels because the size is wrong (I've traced that back to heavy modifications of fifo buffer types and half-channel sizes in smd.c)

3) msm_nand can't register any of the mtd partitions, which confirms previous reports that HTC modified the nand config in heroc.
[Hero CDMA Android Development] maejrep:
Turns out this is helpful for now :p So I'm actually leaving this until I get further.

I put in some basic smem_alloc calls, but as of now, it's not using the larger fifo buffers correctly yet. This does allow the smd channels to be registered though.

Fixed this, so it now infds all 6 mtd partitions.

http://xda.privatepaste.com/bc505aeb6b

I think I can get it to boot, but we're not going to have GPS or data until I can fix smd... :o
[Hero CDMA Android Development] mrinehart93:
Forgive my lack of knowledge on this subject, but from what you just posted, the kernel is working, minus GPS and Data? Well... NICE WORK!!!
[Hero CDMA Android Development] maejrep:
It's mostly working.. but it's not a "working kernel" still. What's holding it up now is smd, and all the modifications they made to work with msm75xx (seems like they couldn't get the standard smd code to work with 7500, so they kept the weird layouts from wince devices and instead hacked up smd.c for those weird data channels)

I might be able to use one of the older smd drivers from vogue or raph/diam, but i doubt it, because those actually had hard-coded fifo buffer offsets, where these are actually stored in the heap toc.