yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] extrafuzzyllama:
google only releases it for nexus one

they then release froyo source then hardware makers like htc and motorola use the source along to build their versions with either sense or blur
[EVO 4G Q&A, Help & Troubleshooting] Bielinsk:
Now I can see how so many people are confused.

This isn't a simple phone, it is complex and there are many hands in the cookie jar. Please do some research about your phone, and who makes what, and you will realize it is far more complicated than "Froyo is out, how come my phone doesn't have it."
[EVO 4G Q&A, Help & Troubleshooting] TheBiles:
I'm very happy with the Froyo I already have. I see 4G as a totally useless feature due to its extreme battery drainage.
[EVO 4G Q&A, Help & Troubleshooting] youngdhillon:
Uhh mayb not everyone has the time to research the whole history/background of their phone as you do...like me i switch phones every 2 months that means i'd be doing more research on my phones history then using the damn thing.
[EVO 4G Q&A, Help & Troubleshooting] Bielinsk:
Then thinking you can come into a development forum and post a question that should be common knowledge to anyone tinkering at all in Android is just lazy.

If you switch phones every two months, then what do you care about Froyo, or even learning what your phone can do anyway...

When I make a purchase, I find out what I am buying, if it suits my needs, what limitations it has, what support it has etc. I call that making an "informed" decision.

I don't just walk into the story and buy the pretty one without knowing the above. Or else I would have an iPhone and wouldn't care about what I can do with it.

This was a lazy question posted by someone that hasn't done any reading about their phone or they would see what has to be done to get an Official Froyo build.
[EVO 4G Q&A, Help & Troubleshooting] DraginMagik:
basically,

Froyo (aka: Android 2.2) has been released by it's maker. it's maker is Google. HTC gets licensing to install the OS on it's phones. now, when HTC first started working with Android...android was..well...it was lacking...it was lacking a fair bit. so the HTC devs put some 'Sense' onto android to make it something that the nerds can bring to their corporate executives. (cause if we nerds can't sell the boss on how cool this is...then i don't get to play it.) meanwhile, Google is trying to turn Android into a serious market contender. and its going up against some very mature code. this has a side effect of causing Google to release v1.5, v1.6, v2.1 and v2.2 rather close to each other. this is not a sustainable pace of release...it will piss everyone off. thankfully Froyo supposedly will be able to bridge us over until v3.0. at which point google has said they will proceed with a much slower version relase of Android.

Sense is not needed like it used to be. however, it'll prolly be around for a while. htc has said they will release froyo onto the evo but that is not a priority for them...the evo is yesterdays product so its more important getting the upcoming devices ready for market. perhaps the HTC/Sprint sanctioned Android 2.2 will be released by the end of the 4th quarter (or so they say).

on the good note...CM6 is rather nice. even without having 4G running yet. but really, how often do need to turn on the 4G radio? and they will get it working before long.

i must also agree w/ Bielinsk on this one....

Bielinsk	Originally Posted by youngdhillon

This was a lazy question posted by someone that hasn't done any reading about their phone or they would see what has to be done to get an Official Froyo build.

Today 03:54 PM​
[EVO 4G Q&A, Help & Troubleshooting] kevinb99:
This may be a little off topic, but if I root my EVO what ROM should I use if I want Froyo and Sense?
[EVO 4G Q&A, Help & Troubleshooting] stillryan:
Check out Avalaunchmods Froyo ROM with Sense. He released an RC for it today and hopes to have a couple of little issues fixed tonight. He has a Sense and no-Sense ROM available. He's put a lot of work into them and i'll be checking out the Sense ROM for sure tonight. Probably bounce back and forth between the CM6 that i'm using now and Ava's Sense ROM.
[EVO 4G Q&A, Help & Troubleshooting] firemedic1343:
I respect your desire for Sense, however, I see no Sense in it.
[EVO 4G Q&A, Help & Troubleshooting] youngdhillon:
maybe because all the phones i buy are android os...and you really have way too much time on you're hand to flame someone over such a little thing...all i asked was "isn't froyo suppose to be released by google and not htc" if you don't wana answer it then leave it alone...noone wants to hear your history crap...Noone wants to know how you read every nutrient fact before buying milk or read every little thing that's on the charging adapter...maybe you have time all the time in the world to do that and all the power to you but not everyone is like...we actually have a life and don't learn the history of every little thing we purchase...and fyi forums are made to ask questions and to inform each other...so if you don't like someones question instead of flaming simply don't read it and move on.
[Nexus One Q&A, Help & Troubleshooting] Caree:
I have 2 Nexus One's. The first was rooted and I had the ADB USB driver (v3) installed on my Windows XP Pro SP3 desktop and all worked fine.

I now have a second Nexus One. I rooted it, and after turning on "USB debugging" and wanting to use it with ADB, the driver USB installed again. But now I get constant "Found New Hardware Wizard" install loops, for both phones with "USB debugging" turned on.

Every time I plug either phone in, or reboot, Windows wants to reinstall the ADB driver. Right after it completes a driver install it wants to do it again.

Solutions I've tried; I have rebooted after install, uninstalled the drivers from Device Manager, deleted the drivers manually from the registry, removed any possibly associated hidden drivers that were marked error in Device Manager, and combinations of the above in various order.

I know that USB driver install loops on Windows can happen to any type of device, not just the Nexus, but in my case it's only on the ADB driver for Nexus One.

Can anyone suggest what I can do other than what I listed to stop the ADB driver endless install loop, or what is causing it?

Thank you.
[Nexus One Q&A, Help & Troubleshooting] johng75:
ever find a resolution for this? im having the exact same issue.

my phone was purchased used, already rooted and bootloader unlocked...

if i hit cancel on one of the multiple install attempts it seems to stop until i unplug then plug back inthe phone...

i can see the phone through ADB thou....

ive not tried to run any commands not knowing the actual state of the install, dont want a brick...
[Nexus One Q&A, Help & Troubleshooting] Caree:
No, I haven't found a solution to this yet. And you are the only person here that has replied.

I did contact Google and HTC and asked for their help. But since the phone is rooted I got the expected replies from both, that rooting violates warranty so they refused to help. I was expecting that, but have heard that the occasional tech support person at Google will still offer support within reason. But not in my case.

If and when I figure this out, I'll post it here to help you out.
[Nexus One Q&A, Help & Troubleshooting] Caree:
Hi JohnG75,

Just wanted to let you know my constant ADB driver reinstalls have stopped. But unfortunately I have nothing constructive to point out as a solution. I spent hours online researching for a possible solution, and found nothing worthwhile yet. I've posted in several places and got no helpful replies other than trying System Restore and going back to a point before this happened. Of course that's hardly a guaranteed fix, plus you loose any other updates and installs you have made since then.

In my case, I left "USB debugging" turned off on my phone since I wrote you last, and the only thing that has changed system wise for me, is I have installed 2 unrelated device drivers since, and MS has pushed out a security update. So today when I turned "USB debugging" back on in the phone, it did a single device install, and it didn't repeat. So hopefully this resolves it for me.

If I were to take a guess as to what appears to have solved it in my case, I would say it was the new unrelated device driver installs. Perhaps it cleared whatever was wrong in the device driver system. So maybe if you were to install some new device driver you need, or uninstall an existing one, reboot and then reinstall that same device driver, perhaps it will clear whatever is messed up in your device drivers.

Sorry I can't be of more help, and my suggestion is only a guess based on my only recent system changes.

There is very little documented solutions to this problem out there, only lots of people that have complained about the same type of problem, with every sort of device you can think of. And the solutions documented are always specific to those exact devices.
[Nexus One Q&A, Help & Troubleshooting] myboo_1988:
Omg i just root my n1 now

my n1 cannot barely call...each time call the connection will end it after few second...or else it will be fine after 1 -2 hour...can make call and etc...after that the phone start back to normal the signal is full bar but just end it automatically..now what warranty also cannot claim ?? crying =(
[Nexus One Q&A, Help & Troubleshooting] polo79:
........favorite post ever
[Nexus One Q&A, Help & Troubleshooting] Daneshm90:
You're holding it wrong. :rolleyes:
[Nexus One Q&A, Help & Troubleshooting] rj3005:
This post does not belong in the development sub-forum.... and it might help if you actually would write something that makes sense and add some useful info (versions of kernel/Android/radio)
[Nexus One Q&A, Help & Troubleshooting] THATTON:
I gotta add this as my sig. ROFLMFAO!!
[Nexus One Q&A, Help & Troubleshooting] kogir:
Calm down. You can't break your hardware by rooting, and HTC has been good about fixing hardware defects even on rooted phones. Since your phone is rooted, I'd recommend starting troubleshooting by downloading RomManager from the android market and installing the factory FRF91 build. You want it rooted and with google apps. Then do a full reset of your phone (look that up) and see if that helps.
[Nexus One Q&A, Help & Troubleshooting] prettyboy85712:
OP is cross posting. Reported.
[Nexus One Q&A, Help & Troubleshooting] stylez:
Please read the rules only post once on that note thread closed.
[HD2 General] Pappagallo:
Posting this so maybe other people can profit from my experiences.

The last couple of days I've been strugling to get my HD2 synchronized again with Outlook on PC after flashing a new ROM. Never had problems getting Active Sync running after flashing.

Just so you know......I'm not a noob, I've flashed new ROMs many times, and YES, I also do a Task 29 before flashing.

Anyway, after flashing the latest Energy ROM, I tried to connect to the PC again, but WMDC (Windows Mobile Device Center) just showed a big red cross with a nice comment that said: ERROR. I could see the HD2 in My Computer, could access both the Device and the Storage Card, but I was not able to set up a Partnership to be able to Sync my Contacts and Calendar.

I started troubleshooting, looking in the Windows Eventlog, Googling for Active Sync / WMDC errors, and tried all things below to get it to work again:

- disable Fast Data Sync in ActiveSync on the HD2

- deleted the Windows Mobile Network Adapter and the HTC Leo devices from Device Manager, and let them install again

- uninstalled and re-installed WMDC

- Soft Reset of the HD2

- Hard Reset of the HD2

- Did a System Restore in Vista to a point BEFORE flashing the ROM

- Flashed to other versions of the Energy ROM (including the one that was on the HD2 when it Synched without problem)

Nothing worked, so I was really getting desperate because I need my Contacts and Appointments :mad:

I then dug up my old HTC Wizard which connected without a problem :(

So, it had to be something in my HD2, it couldn't be the ROM because the same ROM worked before.

I didn't sleep very well last night, constantly thinking about this problem :confused:

Then this morning it suddenly hit me........

I've been using XDA-UC on the Energy ROM, but I realised that since the last time I flashed a new ROM, I had included an XML file to setup my GMail Sync via Exchange (created by Makisu).

I deleted the XML file from XDA-UC, did a Hard Reset, connected to my PC and YES !!!!!!!!

I have now established my Partnership and synched my Contacts and Calendar succesfully.

I also manually added My Exchange settings for GMail and that's working too.

Maybe it's time to start using Change Management for my HD2 so I won't have problems like this in the future :D

Anyway, hope this may be of help for other people that have Activesync issues.
[General Questions and Answers] jpenny2525:
I have a G1 that has rooted & upgraded with Cyanogen's Froyo 6 ROM and has Android 2.2. Here's my problem and it's a simple (maybe) one and have not been able to figure out the what and why. Btw, I did not do the upgrade had a friend do it (I'm not as handy with the tech stuff as I would like to be). The end call buttom used to put the phone in sleep mode, but for whatever reason that is no longer the case. I have searched high and low and can not figure why this is no longer the case. Anyone has a hint/clue on what I need to do to get this back?
[Droid Incredible General] Honestly77:
http://www.engadget.com/2010/07/26/library-of-congress-adds-dmca-exception-for-jailbreaking-or-root/

Check it out. Yup. We just won a big one dudes. No longer can they keep us down. Root. Forever.

More detailed link here:

http://www.eff.org/press/archives/2010/07/26
[Droid Incredible General] jdkoreclipse:
thats a win!
[Droid Incredible General] rfarrah:
Interesting. Nice to know we're getting positive attention.
[Droid Incredible General] aaronjb:
RTFA. Thread headline is a mess.
[Droid Incredible General] snackcharmer:
not exactly as cut and dry as...jailbreaking is legal..but definitely heading in a more positive direction. YAY!
[Droid Incredible General] jdmba:
Ugh

People ... this is not as big a story as you think. It simply means Verizon can't sue you under the copyright code if you root.

That said, you entered a contract with Verizon when you got the phone and signed up for service. The copyright code has NOTHING to do with that contract.

That contract says that if you root, your warranty is void and they can do other fun things. So, if you root, "I believe" (i want to say that ... as I am not rendering legal advice) that you won't get prosecuted under the copyright code, but you are CERTAINLY in breach of contract, and have voided your warranty. Since Verizon was unlikely to look to the copyright code to go after those who root, when they can just hold you in breach of contract, etc., this is a non-news story as far as the every day person is concerned.

It is BIG news for unrEVOked; but not for "you".

... so move on from this news story.
[Droid Incredible General] TNS201:
I never knew rooting was considered illegal. Its not like it allows you to use paid apps for free, cuz technically you could do it with a non root phone.

BTW, the law might not hold us back, but the things the makers of the phones do to the phones will at least hold us down for several months.

Umm, I don't think verizon would hunt you down for rooting your phone for breach of contract. If you are stupid enough to brick your phone rooting or doing something and messing it up and go to verizon and tell them what you did instead of saying "my phone fell in the lake" or some random stole my phone then I don't think you deserve a new phone lol.

What you don't tell, wont hurt you.
[myTouch 3G, Magic General] c0dehunter:
Hey, when i press on call button, call log pops-up. I want dialpad to show first because now i have to manually select it on top. How could i do that?

Thanks
[Hero, G2 Touch Themes and Apps] embrion:
Hi,

to make long story short, I'd like to have HTC/Sense on Vanilla 2.1 ROM.

Vannilla Eclair 5.0 to be precise.

Something like this: http://androidforums.com/roms-droid/118201-htc-status-bar-theme-motaboy.html would be perfect.

Anything like that already made? Or could I just pull files from another 2.1 ROM with Sense?
[Hero, G2 Touch Themes and Apps] ZED_pt:
all depends on what ROM you are using...

You have a lot of themes for the CM´s several versions in Android Themes section.Just make sure they are MDPI´s
[Hero, G2 Touch Themes and Apps] shinyfong:
what do you mean?
[Hero, G2 Touch Themes and Apps] embrion:
Yeah I checked them but nothing I need. I think I'll check some tutorials and swap a few PNGs by myself. I'm using Vanilla Eclair, it's based on CM 5.0.8, so 5.0.8 themes should be compatible with it?
[Hero, G2 Touch Themes and Apps] shinyfong:
i cant link my contacts to fb? i go to contacts page and press mene but dont have the link function? unlike the sense people
[Hero, G2 Touch Themes and Apps] embrion:
move somwhere else with your offtopic
[XPERIA X10 Themes and Apps] GPdhillon:
I have installed the NOLOCK application to rid to the arc swipe to pick the calls but seeing my phone wake-up every min (screen turn ON) if disabled the lock using NOLOCK,

is anybody else seeing the issue? or there any other disabled the lock with using NOLock application?

Thanks in advance
[Vibrant Android Development] Koush:
It's easy, it's free. And here's how you do it!

You will need to create two simple JavaScript files:

A file that describes your ROMs that you send to me.

A file that you host that lists your ROMs, so you can update your ROM Manager section.

First, your developer/ROM description file:

{
// This is what name you want your ROMs to show up under.
developer: "CyanogenMod",
// Your id. This should have no spaces or other funny characters.
// This would ideally be your Github id, so when you send me your manifest
// I can verify who you are. But it can be anything really.
id: "cyanogen",
// The display summary. Two lines max.
summary: "Mods and bacon for Dream, Sapphire, Droid, and Nexus One",
// The location of the developer's manifest.
manifest: "http://gh-pages.clockworkmod.com/ROMManagerManifest/cyanogenmod.js",
// The list of devices that this developer's ROMs support.
// If you don't support a device, just don't list it!
roms:
{
vibrant: true,
sholes: true
}
}

Send me that file! koush@clockworkmod.com

Link to developer sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/developer.js

And now, create your ROM list file:

{
// The version of the manifest, so ROM Manager knows how to load it
version: 1,
// The homepage for your ROM, if you have one.
homepage: "http://www.cyanogenmod.com/",
// The donate link for yuor ROM, if you have one.
donate: "https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3283920",

// Your list of ROMs
roms:
[
{
// Display name of the rom
name: "CyanogenMod 5.0.5",
// Display summary of the rom
summary: "Stable",
// Device that this rom runs on
device: "sholes",
// This is the download URL of your ROM.
// These URLs should have unique filenames per version!
// Ie, don't use a zip with the same name
// as that of a previous version with a new version.
// Otherwise ROM Manager will continue using the
// old cached zip on the SD card.
// This must be a direct download,
// and not a Mediafire type link.
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.5.zip"
},

// Antother, older ROM!
{
name: "CyanogenMod 5.0.4",
summary: "Stable",
device: "vibrant",
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.4.zip"
}

]
}

Link to manifest sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/simplemanifest.js

And you're done!

If you're a pro dev, you can even create a ROM customizer. But I won't get into that here :)

Follow this link for more information: http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html
[Vibrant Android Development] TGA_Gunnman:
Excellent thanks Koush!!
[Vibrant Android Development] defconoi:
very nice, I love koush lol
[Vibrant Android Development] blackerwater:
Nice :)
[Vibrant Android Development] WilliamStern:
Damn Kouch, you seem to be making all this pretty easy for everyone. I'm new to all this rooting stuff, and I've gotta say you've got me really excited about all this. I paid for your Clockwork app to show my support for your hard work, and time you've put into this. Can't wait to see what ROMs hit the Vibrant within the next few weeks!

Thanks!
[Captivate Android Development] Koush:
It's easy, it's free. And here's how you do it!

You will need to create two simple JavaScript files:

A file that describes your ROMs that you send to me.

A file that you host that lists your ROMs, so you can update your ROM Manager section.

First, your developer/ROM description file:

{
// This is what name you want your ROMs to show up under.
developer: "CyanogenMod",
// Your id. This should have no spaces or other funny characters.
// This would ideally be your Github id, so when you send me your manifest
// I can verify who you are. But it can be anything really.
id: "cyanogen",
// The display summary. Two lines max.
summary: "Mods and bacon for Dream, Sapphire, Droid, and Nexus One",
// The location of the developer's manifest.
manifest: "http://gh-pages.clockworkmod.com/ROMManagerManifest/cyanogenmod.js",
// The list of devices that this developer's ROMs support.
// If you don't support a device, just don't list it!
roms:
{
captivate: true,
sholes: true
}
}

Send me that file! koush@clockworkmod.com

Link to developer sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/developer.js

And now, create your ROM list file:

{
// The version of the manifest, so ROM Manager knows how to load it
version: 1,
// The homepage for your ROM, if you have one.
homepage: "http://www.cyanogenmod.com/",
// The donate link for yuor ROM, if you have one.
donate: "https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3283920",

// Your list of ROMs
roms:
[
{
// Display name of the rom
name: "CyanogenMod 5.0.5",
// Display summary of the rom
summary: "Stable",
// Device that this rom runs on
device: "sholes",
// This is the download URL of your ROM.
// These URLs should have unique filenames per version!
// Ie, don't use a zip with the same name
// as that of a previous version with a new version.
// Otherwise ROM Manager will continue using the
// old cached zip on the SD card.
// This must be a direct download,
// and not a Mediafire type link.
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.5.zip"
},

// Antother, older ROM!
{
name: "CyanogenMod 5.0.4",
summary: "Stable",
device: "captivate",
url: "http://www.droidaftermarket.com/koush/motorola/sholes/cyanogen_sholes-ota-eng.koush_5.0.4.zip"
}

]
}

Link to manifest sample: http://gh-pages.clockworkmod.com/ROMManagerManifest/samples/simplemanifest.js

And you're done!

If you're a pro dev, you can even create a ROM customizer. But I won't get into that here :)

Follow this link for more information: http://www.koushikdutta.com/2010/03/rom-manager-and-third-party-roms.html
[Captivate Android Development] derekedw:
Why don't our devs utilize this? Not complaining, but was trying to investigate and come up with an answer why they won't post their ROMS (and updates) to ROM Manager. It's such an awesome tool for ROM deployment and updates.

With the growth we've had in ROM development, I will gladly make my next donation (albeit not very much) to the next few ROM Devs that start posting their ROMs to ROM manager.

Granted I hope to get off this POS captivate and away from Samsung phones altogether in the next few months. You devs are the only saving grace for the phone. Would love to see you post your work and ROMs in ROM Manager!!
[Captivate Android Development] nbs11:
With andromeda we were going to utilize this feature, but we were not able to because of our versioning scheme.
[Captivate Android Development] mcord11758:
I think the lag fixes and custom recoveries make it a non viable option