yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] crazysane:
Well I asked DCD and he has told me that he had a break in the code of the .net compact framework. He then went on to tell me to redownload the .net 2.0 and 3.5 and reinstall them. I was able to install the .net 2.0 but when it comes to the .net CF3.5 I was unable to make it work. The following picture is a screenshot from my phone during the attempted install. However I am unable to find anything written on it to tell me how to make it work.
[Touch Pro, Fuze General] frnorke:
Does anyone know where to get a copy of the ExtUSB cable that comes with the HTC Fuze? I can find cables that do the same thing, but I'm wondering if anyone could tell me where I can get a copy of the one that comes with the phone (I bought my phone from AT&T)? Thanks for your help.

V/R,

Kurt Nordman
[Touch Pro, Fuze General] Rudegar:
extUSB is a std that htc invented which is pretty much normal miniUSB but plus audio

if you just need to charge and sync any miniUSB in one end normal usb in the other cable you can buy for a 1$ will do

expansys.com prob sell origital htc cables but unless you need audio as to a headset it's a waste of money
[Upgrading, Modifying and Unlocking] dhengu123:
Hello all,

I got he unlock code from att but unfortunately it was wrong, i called up att they gave me a new code, but my phone now gives me a message that i have entered the code more than 5 times, wait till timeout.

I told att about this problem, they said the phone is now permanently locked to att network. unfortunately i am in india and in an area where att netwok does not exist. is there anyway, i can unlock my phone and use a local sim.

please help:confused:
[G1 Android Development] Bavilo:
I got bored so I decided to compile the latest Donut source.

Please make a Nandroid backup before you flash any of this! Just in case.

To add Google apps, check out the Google Stuffer, or similar scripts.

Features:

- Latest Donut source compiled for the HTC-Dream

- Stock (No Google apps whatsoever)

- Otherwise fully working (report bugs if you find any though)

Bugs

- Home key and Phone key not working (I'll try to get them to work)

Instructions

Unzip "Android-1.6_r1.zip"
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot

Only the system.img and boot.img is needed for the flashing procedure, but I included the other images just in case someone wants to take a look at them.

Screenshots

Download

http://www.mediafire.com/?ntdmo0ulxdr

Enjoy~
[G1 Android Development] hiroots:
Is this a root rom?
[G1 Android Development] coolmarkoo:
Great job now we proved to Google that we don't need them
[G1 Android Development] Bavilo:
This does not affect the recovery.img. So if you have Cyanogen's 1.4 recovery.img you will still have root.

Although you won't have apps like SuperUser, since it's Stock.
[G1 Android Development] chevycowboyusa:
Good Job!

I want to try this, but I dont ADB (yet) can this be flashed thru recovery??

I used Tmobile contacts backup, so I can see if it will restore my contacts.

Chevy
[G1 Android Development] Bavilo:
Yes you can use the recovery console.

Move the files to the root of your sdcard first though.

mount sdcard [enter]
mount system [enter]
flash_image system /sdcard/system.img [enter]
flash_image boot /sdcard/boot.img [enter]
reboot
[G1 Android Development] saprano614:
any way you could make this a update.zip. so we can just use cyan recovery to flash the zip?
[G1 Android Development] Bavilo:
Only things that I noticed to be not working are the home key and phone key.

I'll investigate further.
[G1 Android Development] mykenyc:
is this experimental
[G1 Android Development] roadrunnerx7:
i feel i shouldnt be looking at this. its so naked :(
[G1 Android Development] Bavilo:
Yes this is experimental since it's compiled from a non-finalized source.

I know this ROM is naked. But since Google is taking action against the distribution of their closed-source apps, everyone has to release Stock ROMs now.
[G1 Android Development] roadrunnerx7:
i know i know its just so different from what were used to seeing.. but this is the new standard now(unless google changes! :D..) so might as well get used to it =/
[G1 Android Development] DavidChill:
this looks very interesting. i will probably wait to use this until i see that it works with a few of the scripts that are being developed.
[G1 Android Development] Bavilo:
I'm sure someone will create a script that's compatible with Donut. Since we have all of the proprietary files necessary.

Script makers, do your magic please ;D
[G1 Android Development] chevycowboyusa:
Weird

I keep getting an invalid argument when trying to mount the system in recovery terminal.

i typed

#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system

and

#mount -o remount,rw /dev/block/mtdblock3 /system

and

#mount -o remount,rw /dev/block/mmcblk0p2 /system

I seem to b having a brain fart.

Can i flash thru terminal emulator? edit: [I figured this one out.... NOPE!]

Chevy
[G1 Android Development] JimmyJayCEO:
It was VERY hard on my eyes to see an actual "bare bones" ROM already. Use to all the bells and whistles. I guess this is what we will have to work with right now till something is figured out. I really like this idea. Has ANYONE tested this yet with any google apps script. I really dont wanna try this until I know that we can get everything. I'll keep my eye on this though. Thanks for coming up with something so quickly
[G1 Android Development] Bavilo:
To mount anything in the recovery console you just need to type "mount system" for instance...or mount sdcard.
[G1 Android Development] robpet2:
wow.. this is the start of more freedom... Rebenga!!!!
[G1 Android Development] chevycowboyusa:
Weird things

Wow.... Something must have been messed up....

I wiped and reflashed cm 4.1.11.1... then I went to recovery terminal (after booting)

was able to [mount system] [mount sdcard] flashed system and boot imgs.

Rebooted and went thru g1 screen, then black, and then another g1 screen, then automatically went back to recovery.... {Weird!!!}

any advice?
[G1 Android Development] Bavilo:
Yea that is weird. I only tried flashing the images with fastboot, and erasing the userdata.

I'm working on fixing the home and phone key atm.
[G1 Android Development] chevycowboyusa:
User data

Can you erase user data from recovery?

One more question, can I copy the [new] system.img and boot.img to a nandroid backup, and retore it?

ok, one more... do you have the MD5sum for these two files? (I'm going to edit the Nandroid.md5 file)

Thanks!
[G1 Android Development] Bavilo:
Not really sure if you can erase the userdata from within the recovery console. I'll need to test this in a bit. I'm recompiling the source right now, hopefully the home and phone keys are fixed now. I'll then re-upload the files and provide the md5sums.
[G1 Android Development] chevycowboyusa:
Thanks..

Good work. I am recharging my phone now...

I"ll let you know if the nandroid backup works... [with the new files]

I'm going to wipe, and backup, then i"ll mod the md5 file and restore.
[G1 Android Development] Bavilo:
I gotta head to bed. Work at 6am *sigh*. But I'll upload an update tomorrow!
[G1 Android Development] danguyf:
Are you sure? Back in the day I installed it from the Market. It was only with the advent of the JesusFreke mod that SuperUser began to be packaged in the ROM. Did Google start offering it stock??
[G1 Android Development] jubeh:
Hey, I tried building 1.6 from source (i haven't synced in a while, so I don't have 1.6r1 yet) and I tried using the binaries ADP1's proprietary files and building for dream, the device would boot, but I'd get no signal, or wifi, etc. Where'd you get your files, or what procedure did you use other than just running make?
[G1 Android Development] jubeh:
ooohh, cool beans, I see you included the ramdisk and kernel in the zip.

Another way to clear your userdata and cache when flashing through fastboot is to

fastboot reboot -w

after flashing boot and system.

Great job guy.
[G1 Android Development] jubeh:
This is newer than Cyanogen's releases. Cyanogen's builds were DRC59 (update 4.1.4 to 4.19.2) and the now infamous 4.1.10.x were DRC 63. The SDK emulator image was DRC 63C, and this is DRC 79. The image I had made and couldn't make work was also DRC 63, so maybe r1 will boot better building it "the cupcake way".

This is fun, only reason I was holding on to rogers was because there's no better CRC1 build, but now with DRC, I'll see if I can make HTC's CRC apps work.
[G1 Android Development] fries_:
Same question here. I compiled donut myself. But it would not boot up completely. I could adb logcat and adb shell, just to see that some binaries would die getting a SIGBUS.

The device would endlessly try to start the Android software stack.

How did you get around this?
[G1 Android Development] jubeh:
when I got that error, it turned out I was missing a libcamera.so which is not included in the HTC provided binaries, so I had to pull it from my phone and then make the build with the file included in the proprietaries, this will allow you to boot, but again, I had no signal and trying to start wifi would reset the device (or just fail, I don't remember since I flashed rogers crc1 right away)
[G1 Android Development] Bavilo:
I'm currently at work so I can't upload any changes, but I did resolve the problem I was having wioth the home and dial key.

To jubeh and fries:

I used the proprietary files from CMs 4.1.11.1, and I customized the build scripts a little.

Also when I said that SuperUser is not included, I meant that it will work but I won't include it to keep this rom stock and more managable. Besides theres enough experienced rom makers who are more than welcome to take this build and change it around :).

I'd appreciate it if you guys could test a few thing on your actual G1. Like camera, music, dial, calling, etc.

Thanks
[G1 Android Development] Loccy:
Any chance of including an init.sapphire.rc in future releases, so it'll work on a 32b Magic with no additional faffing?
[G1 Android Development] Bavilo:
I'm completely unexperienced when it comes to sapphire...if anyone can take a look on getting this to boot on the magic, that'd be great. But I'll look into it aswell.
[G1 Android Development] jubeh:
One thing I noticed on this build, you're missing Contacts Provider, so you can't save your contacts, or use the contacts apk for anything. I didn't have a chance to test what that meant when trying to use phone because I pushed the apk to the phone and then after I was done playing with it I installed back my rogers build, but yeah, you need to build Contacts Provider.
[G1 Android Development] Bavilo:
Ahh I probably missed it. I'll build it later on when I have access to my computer. Thanks!
[G1 Android Development] Bavilo:
I'm going to rebuild the entire source with the new proprietary files. So hang in there.
[G1 Android Development] :
Bleh, a plain donut. I prefer mine with a bunch of chocolate and sprinkles. :(

Thanks for posting this, gonna try it out after work.
[G1 Android Development] xile6:
Not sure if you know this but htc just released there adp1 1.6

So wouldn't that be better to use and mod? I haven't tryed it yet as I'm not @ a pc but will later and see if it has google apps. Also how do u unlock root on an adp?

I know it should be there right?
[G1 Android Development] Bavilo:
I was planning on taking their proprietary files and using it on this build, since I assume that this build is still newer.

EDIT: Currently building.....

EDIT EDIT: Building should be done....BUT I locked myself out of my place...So once I get back in, in a few hours. I´ll upload...UGH
[G1 Android Development] Bavilo:
Sorry been very busy.

New update tomorrow with CM's Kernel + BFS and maybe more.
[G1 Android Development] uberingram:
Now we're making progress. Kudos.
[G1 Android Development] Bavilo:
I decided to drop this project. It's not worth the time. There's newer builds out there, plus cyanogen has his repository almost done.
[Touch Pro2, Tilt 2 Windows Mobile General] coykiam:
hi all...How can I turn off the phone from beeping everytime I get a missed call?

I've already unchecked everything in the"Sounds & Notifications", And also in the Event's "missed call" in the notifications tab. Did I miss something else? I have Advanced Config Installed if that can help.

Thanks in advance all...
[G1 Android Development] burninglava001:
i tried seaching the forums but wasn't able to find anything...

i need to transfer all my apps from Internal memory to SD card....i saw APPS2SD app but it says that it doesn't work with cyanogen 4.1....

is there any way i can move all the apps from the phone to SD card while staying on cyanogen 4.1....
[G1 Android Development] Gilliland12:
Apps2SD is automatic with Cyanogen Mods.
[G1 Android Development] miketaylor00:
a) wrong forum

b) do a little research

c) read the first post on the CM thread
[G1 Q&A, Help & Troubleshooting] kidrobot978:
lookin for the "you got mail" notification sound anyone can help me find it thx
[G1 Q&A, Help & Troubleshooting] stefan.buddle:
Noone uses AOL, lol "you got mail"
[G1 Q&A, Help & Troubleshooting] Fingerlickin:
Just imagine the millions and millions of AOL CDs that are in landfills right now and all you need is one but can't find it. LOL
[G1 Q&A, Help & Troubleshooting] david1171:
well you can just pretend to say "i have mail" when you see the pm.
[G1 Q&A, Help & Troubleshooting] Fingerlickin:
HAHAHAHA I just did that out loud mocking you david, the guy in a cubicle next to me says "WTF was that, are you OCD?" BWAHAHAHA
[G1 Q&A, Help & Troubleshooting] david1171:
man, i wished i could've heard that. now every time i get a pm i think i am going to say "i have mail"
[G1 Android Development] IronFly:
good post!
[G1 Android Development] dwang:
Agreed, very good post..
[G1 Android Development] vixsandlee:
Maybe someone can clear something up for me (its been bugging me a little)

If i compile from source i need to add files that are pulled from my phone.

Does this mean that ALL roms are technically illegal, even if they dont include the google closed source programs.

Or are we ok to include these files as they are needed for the phone to work, so considered closed source but part of asop?

I have not seen this addressed and i am curious what the state of play is with these files.
[G1 Android Development] harry_m:
Agreed ........ !
[G1 Android Development] Metal_Hurlant:
Thank you for taking the time to clear things up. Hopefully this will help folks gain some perspective and move toward productive directions.

Good question. It certainly means the ROM is not purely open-source, at the least.

My sense is that those files are the property of HTC and we don't have a license to redistribute them.

Now I don't really expect HTC to serve anyone with a C&D anytime soon, for various reasons, but until a ROM cook gets a written license to redistribute those files from HTC, or until a fully open-source rewrite of those files is done, it's a gray area at the very least.
[G1 Android Development] jashsu:
Speaking very technically: yes, because you do not have the express right to redistribute the binary drivers for things like the wifi module or the radio. In reality, these pieces of code are so tightly tied to the hardware that it is unlikely you will get a c&d for redistributing them. However, in the hardcore open source community, even these drivers will be left out, requiring the user to fetch them for him/herself. That would be the 100% license-compliant way.

I'm pleased to say though, there are already many people working on semi and full license compliance methods and "ROMs". Just take a look at the first two pages of this subforum.
[G1 Android Development] TunsterX2:
Read the post again. It's illegal to even copy the Google APKs files out of an original installation and import it into a custom ROM. The major issue was that all ROM creators were importing the Google Apps which are "closed-source" into their own legal open-source code.

I guess now, it'll be down to the individual to decide whether they want the Google Apps in their phone. That's why scripts have been created to give the user a choice on whether to do the illegal act of placing the Google Apps onto their phone.

Google are unlikely going to chase you the individual down rather than the ROM creator (like in Cyanogen's case with the C&D letter).

Hope this helps.
[G1 Android Development] roadrunnerx7:
ok. so then all this is not because of the google propriatary crap, but because he released the market early, so google just USED this BS reason to stop that? in other words, had he not released it early, nothing would have happened?

if thats the case, i dont blame cyanogen, but i blame ALL those GREEDY users that MUST have EVERYTHING before everyone else because they feel they need to be the best. you greedy punks almost ruined it for everyone. from what i see cyanogen usually tries his best to do what the people want, had the people not wanted the market so early(its not even that great, just new colors "ooohhh wooow ive never seen colors before i must have that! and now!".. ridiculous.) then this wouldnt happen.

now from i see the latest and "greatest" usually comes in the experimental releases. i think, cyanogen should shut down the experimental releases, or only release them to certain people.. or make it a lot LESS public..that way he can keep testing the stuff till its good and then release it as stable when he sees fit. i mean come on, 4.0.4 is already awesome!! i love it! been using since forever. why couldnt everyone else just be happy with 4.0.4?

and like the post said, dont be stupid and release some leaked program. cause it doesnt just shut you down its gonna shut everyone down. unfortunately i see that soon some noob working on hero roms is gonna release something, and then HTC will be here next.

oh and add this in there:

and i just saw a rom that got some of the motoblur stuff mixed with hero and for the g1. how long do you think till motorola and HTC are here complaining about software on the g1 that isnt supposed to be?
[G1 Android Development] peshkata:
Why don't Google offer these closed-source apps like they do for Google Maps? They could only benefit from more users having the 'Google Experience', even though their phones don't have them pre-installed.
[G1 Android Development] jashsu:
If a user downloads a "ROM" without Google apps on it, downloads an official update.zip from google.com, and then copies the Google apps from the official update into the cooked "ROM", that completely mitigates the problem of unauthorized distribution and only leaves the much less sticky issue of unauthorized usage. Unauthorized usage is typically a lot less offensive to the interested companies and definitely a lot less enforceable. There are likely some EULAs somewhere governing the usage of the Google apps (GMail, Market, etc) and except for Market I would be surprised if they explicitly required the app to run on authorized distributions only. But again like I said, it would be difficult to detect, let alone enforce.
[G1 Android Development] jashsu:
That's a very good question, and one I sure would like the Android team at Google to answer. The only app I see being a problem would be Market, since it requires a secured app-private to function properly (which would not be guaranteed on a non-GE phone).
[G1 Android Development] rbrahmson:
Your post nicely presents the legal aspects and rights of Google but IMHO misses the larger point. The open source community was believing in the ideals of open source and looking the other way at the control Google has over this platform. The pieces that Google controls are not easily (if ever practically) replaceable.

Google actions show that they are not that much different than Apple in trying to control the platform and the user experience. Don't be surprised to see Google behave more and more like Apple as the platform gets stronger and Google's need of an open community weakens.

The only bright spot is one that Google may have missed - that is their existing fight with Apple and AT&T regarding GoogleVoice. Their actions against Cyanogen gives Apple and AT&T ammunition in their arguments with the FCC, which is the last thing Google wants.

This is the only lever this community has over Google. Bring up the FCC and Google Voice case, and Google may back off.

For those who pray for Cyanogen to be hired by Google -- that is the last thing you want. We do not need Google having more control over him, but less.

For those who think that creating bypasses with clean roms and user-initiated backups will solve these problem -- these are short-term technical workarounds which Google could close too.
[G1 Android Development] vixsandlee:
so with it being technically illegal its pointless (IMHO) being open source.

Its fine with taking from the community, but google seem unwilling to give anything back.

Roll on when full open source roms appear, It would be like a linux distro coming with everything but keyboard and mouse drivers.
[G1 Android Development] ytj87:
This is all legally correct. But it misses the point of the uproar.

We did not expect Android to devolve into a squabble over closed source bits when the whole premise is open source. Goog has disappointed, plain and simple. Your sticky is an apologist's point of view since it doesn't address that fundamental issue.

edit: btw, if Goog was upset about the new Market app specifically, they could have blocked its access to the market using a client-check.
[G1 Android Development] jashsu:
That depends on what your objective is. Open source has many benefits, and many of those are retained even if your distribution contains some closed-source elements. Another important aspect to remember is that while x86 PCs have had three decades to mature, smartphones have not had that same luxury. Given enough time, even hw drivers will become open sourced. So "pointless" is a bit hyperbolic.

The spirit of open source is the spirit of giving. In that vein, Google has invested considerable time building parts of the AOSP from scratch. To say that they are "unwilling to give anything back" is just a plain falsehood.

Good luck finding an open source 3G radio driver.
[G1 Android Development] rpcameron:
If anyone has read any of the dialog between Steve (cyanogen) and some other Google employees about this issue (most notably JBQ), you would realize that the Google employees are trying to work with Steve.

There is dialog about making the AOSP able to be built and fully functional and distributable without infringing on anyone's rights. This includes investigating other avenues for users to acquire and legally install the Google applications.

The current belief is that Google's legal team sent the C&D letter to Steve, and that it was not done so at the request of the Android developers. They most likely would have liked to work with him quietly and amicably.

Also, please remember that the Market application is not a part of AOSP. The Market application is Google's proprietary code; it is not part of the Android base. Not all Android devices have Google's Market—that is why there are other markets and means of installing software.

I have no doubt that this "controversy" will ultimately be for the best. I believe that Steve, JBQ and the rest of Google/Android will find a middle ground that will work best for everyone. (JBQ has an excellent history of working with other developers and finding good solutions for all—I remember back when he was working at Be and how helpful he was to all of those writing applications for BeOS.)
[G1 Android Development] jashsu:
So what you're saying is you expected everything included in a Google Experience phone to be open source? I think the problem here is you (and the people you lump into "we") don't understand that Android isn't just built for users, it's also built for handset manufacturers. Quote from the OHA website:

In light of that, I don't feel its necessary to dignify the rest of your post with a response.