yashsingh1/xdaforums huggingface dataset:
[Vibrant Themes and Apps] jrwingate6:
Hey guy's, I just got a Vibrant and that's why I am picking the Vibrant thread to be the lucky recievers of the 2200 wallpapers Iv'e collected. ;)

http://picasaweb.google.com/justin.wingate
[Vibrant Themes and Apps] ram100987:
"500_internal_service_error"

Are all or only some the wallpapers resolution correct for the vibrant/galaxy s
[Vibrant Themes and Apps] acjames:
Would you be so kind to zip/rar them into one file?
[Vibrant Themes and Apps] StefanB86:
Thank you very much, you have a lot of GREAT wallpapers there! :)
[Vibrant Themes and Apps] gthmcty1:
Very nice!!
[Vibrant Themes and Apps] Fat Tires:
Thanks for compiling all these wallpapers.
[Vibrant Themes and Apps] fykick:
I second a request if maybe all these could be zipped into one file so I can keep them all in one folder on my Vibrant gallery. Thanks!
[Vibrant Themes and Apps] jrwingate6:
I will work on the .zip over the weekend.
[Vibrant Themes and Apps] Ste11a:
These wallpapers are awesome. Thanks for sharing.
[Vibrant Themes and Apps] inkdemon:
Thanks. Some nice stuff there!
[Vibrant Themes and Apps] jayzusfk:
Are all of these sized correctly?
[Vibrant Themes and Apps] bromat80:
Thanks for the walls, can't wait to check then all out on my computer.
[Vibrant Themes and Apps] Shrivel:
Most aren't but they are still some nice wallpapers. Thanks.
[Vibrant Accessories] vince2398:
I was thinking about getting these, has anyone purchased and received this for their Vibrant? Was wondering if its any good. Thanks in advance.

http://cgi.ebay.com/3-Clear-Screen-...ewItem&pt=PDA_Accessories&hash=item2eaeab13cb
[Vibrant Accessories] disturkis4u:
Refer to the screen protector thread.... Some like it and some don't because it's somewhat sticky..took me a while to get it on without bubbled and it still has a couple...also leaves a lot of marks and creases
[Vibrant Accessories] timafey:
Yes I just got mine.. they are CRAP! don't even waste the $3 on them... soo flimsy and they feel the same as the stuff that covers new electronics/screens... very thin and flimsy, imposible to install without bubbles b/c its soo flimsy, and using a CC to push the bubbles out of it i scratched and stretched all of them... worthless product
[Vibrant Accessories] disturkis4u:
Mine was terrible at first..then used water to install and it's actually not bad...waiting for the clear freak to see what the hype is about but I'm guessing they're the same as these
[Vibrant Accessories] dublued:
I just got these in today.

These are made out of some sort of vinyl material. It seems like it would be impossible to install this without any bubbles.

Even if you were to get rid of the bubbles, the surface of this is not very good or smooth enough for finger scrolling.

I had ordered a screen protector from dealextreme.com for my old G1 and it was great. It was nice and thin and went on without any problems the first time. It's still on after over a year without any sign of coming off.

I would not recommend anybody to buy this.
[Nexus One Q&A, Help & Troubleshooting] Legaleye3000:
Anyone use a Jawbone Icon? People hear me fine, but the quality of their voice is always pretty crappy. Its hard to understand them. Volume isn't an issue. On the Icon, I'm running latest update with A2DP functionality and 2.2 on N1.

Any input would be appreciated. Thanks.
[Nexus One Q&A, Help & Troubleshooting] newdeepdan:
I have the same issue as well, but as soon I went back to the original Jawbone profile instead of the A2DP, the issue went away.
[Nexus One Q&A, Help & Troubleshooting] Vision77:
Hmmm....I guess I will try disabling A2DP too. :D
[Nexus One Q&A, Help & Troubleshooting] bleedingblue:
I'm using AD2P. It seems to work for me.

-bb
[Nexus One Q&A, Help & Troubleshooting] IronServer:
Did you find a solution for this? Im having this issue too.

I find that that after reseting the Icon the first call is clear, but then call quality gets increasing worse with each call. A2DP sounds good though.
[Nexus One Q&A, Help & Troubleshooting] Zephyron:
are you guys using CM6? I heard a while back that the volume boosting kernel messes with call quality in bluetooth headsets, not sure if this was fixed.
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
Good morning!

With the update from EPE76 to FRF91:

Installing update...
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

When I tried to update to R21 via recovery-RA-nexus-v1.7.0.1:

Writing BOOT...
E:No space left on device
E:Error writing BOOT:
Failure at line 380:
write_raw_image PACKAGE:boot.img BOOT:

Installation aborted.

If we take boot.img from 2.2 and do «fastboot flash boot boot.img»:

sending 'boot' (2336 KB)... OKAY [ 0.391s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.281s

Via recovery downgrade to ERD79 and download OTA FRF91. Error.

The kernel can't be written because there's not enough boot partition space.

I found a similar problem (xdaforums.com/showpost.php?p=6779420), but the this solution did not help.

Command "fastboot flash zimage zImage" return error.

It is hoped that the problem can be corrected? Reducing the size of boot up such as it was in 2.1? Or maybe you can increase the size of the partition boot?

The fact that Russia is not valid warranty google and I can not fix your phone officially.

Thanks and sorry for my English.
[Nexus One Q&A, Help & Troubleshooting] willverduzco:
Try this:

In Fastboot USB, flash to Clockwork Recovery (fastboot flash recovery recovery.img). Once you're done with that, enter the recovery and go to the Partition menu and format the boot partition first (and the rest of them, except for SDCard). After that, flash any one of the FRF91 builds available here, such as CM6 RC1 or MCR.
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
Thank you!

I did it, but the result has not changed. If I write boot from FRF91:

>fastboot flash boot boot.img
sending 'boot' (2336 KB)... OKAY [ 0.406s]
writing 'boot'... FAILED (remote: image update error)
finished. total time: 1.328s

I think have to resize the boot partition, and not just format it.

But superboot.himem.img from EPE76 (2162 KB) installed correctly.
[Nexus One Q&A, Help & Troubleshooting] Firerat:
from G1 thread http://xdaforums.com/showthread.php?p=7061471#post7061471

unrelated, but I maybe able to help here

some observasions have been made with older G1 SPL's and newer 'larger' kernels, where they fail to boot, current theory is that for whatever reason the ramdisk actually overwrites the tail end of the kernel in memory. This is unproven, but is academic as the newer SPLs do not have the same issue and are superior in other respects.

In any case I don't belive that the issue you are having is the same, as you are getting a clear message that the boot.img write has failed.

This error could be due to failed nand, where the blocks in boot partition have failed and you have a reduced sized boot partition.

do you get errors with the following ?

fastboot erase boot

does

fastboot flash boot <boot.img>

then work as expected?

also , are you using the same SPL as others, who don't have the same issue?
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
Thank you for trying to help!

>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.063s

Naturally so!
[Nexus One Q&A, Help & Troubleshooting] Firerat:
ok, so next option is to write the boot.img to recovery,

fastboot flash recovery <boot.img>

if that works then you will have to get to recovery with

fastboot boot <recovery.img>

not ideal, but if you can do a normal boot via a 'boot to recovery' you have no option

edit:

thinking about I have another option, but its a little bit more complicated

write a custom zImage to /boot

this kernel has its own mtd map, with a new partition where system normally starts ( or maybe cache or data ), and get it to load the ramdisk from that address

This assumes that the problem area is towards the end of boot partition

BUT, tbh , it seems like you have an actual hardware problem, it might be better to return it under warranty, less fun but better solution.
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
Thanks for help and hint!

That's what has helped:

>fastboot boot boot.img
downloading 'boot.img'... OKAY [ 0.391s]
booting... OKAY [ 0.063s]
finished. total time: 0.469s

But temporarily. Ie until the first reboot.

But to fully solve the problem I need a magic "recovery.img"? Or something I did not understand?

I tried but failed to write of the default zImage to /boot

Russia is not covered by Google warranty and I can not fix my phone officially.

In addition, the phone works fine with Android 2.1, but I want 2.2

edit:

After "fastboot flash recovery boot.img" I understand what "normal boot via a 'boot to recovery'"

This is what I need! Thank you!
[Nexus One Q&A, Help & Troubleshooting] Firerat:
well, if we assume that your boot partition is 'broken', then we can use the recovery partition

i.e., instead of writing boot.img to boot, we write it to recovery

fastboot flash recovery <boot.img>

so instead of going into recovery you go into the ROM

if you do this, then you can only get to recovery with

fastboot boot <recovery.img>

but it is more useful to be able to boot the ROM any time than recovery.

the 'trick' with zImage would be a lot more complicated, but would allow you to keep recovery.img on the phone

Actually, I still need to work out if we can load the ramdisk from a separate source to the boot.img, for now useing recovery for boot.img is your best bet
[Nexus One Q&A, Help & Troubleshooting] J.L.C.:
I had similar problems and have concluded that it is due to bad mtd blocks in the boot partition.

I found the address of the bad blocks with the recovery.log from amon ra recovery. After trying to flash some custom kernels.

I currently have a ticket in with htc to send the phone in for repair. Hopefully they will get it fixed up.

________________________

N1 w/ XDA App
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
This is what I need! Thank you!
[Nexus One Q&A, Help & Troubleshooting] Firerat:
I may have a more convenient solution to this ( if you can not get warranty cover )

basically it is using an idea I have been playing with on g1s

here is the implementation

http://xdaforums.com/showthread.php?p=7061471#post7061471

and here is the background ( lbcoder's thread on the subject )

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

basically the idea is that we can 'grow' the boot partition, and shift system up

this should give you enough 'good' blocks to write a boot.img via a modified recovery, we then patch said boot.img to recognise the 'shift' in the partition layout

there are drawbacks

you will be unable to fastboot flash boot ( but you can't anyway )

you will be unable to fastboot flash system ( but you probably use recovery for that anyway )

one of your partitions will have to shrink by the amount you grow boot ( but its going to be small, so no great loss )

the advantage

you get to boot 'normally' and keep recovery ;)

if you could give me the output of

fastboot oem listpartition

I can workout a custom MTD partition layout for you ( I don't have an N1 )

you would need to 'patch' your recovery.img, and any boot.img you flash

but I can make that quite simple ( see the first link )

can't say for sure that it will work, but I'm confident it can
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
Excuse:

>fastboot oem listpartition
... INFO[ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.063s

I'll be very grateful!
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
Strange bug:

After "boot to recovery" (in recovery boot.img) not working WiFi.

After "fastboot boot boot.img" WiFi working.

Radio version 4.06.00.12_7. But that is another problem...
[Nexus One Q&A, Help & Troubleshooting] Firerat:
:(

looks like your SPL doesn't support it :(

e.g. , my G1 looks like this

android@Firerat:~$ fastboot oem listpartition
...
INFO[radio] start block=0, size=287 (36736 KB)
INFO[hboot] start block=288, size=6 (768 KB)
INFO[misc] start block=294, size=2 (256 KB)
INFO[mfg] start block=296, size=2 (256 KB)
INFO[sp1] start block=298, size=6 (768 KB)
INFO[misc2] start block=304, size=3 (384 KB)
INFO[mfg2] start block=307, size=3 (384 KB)
INFO[recovery] start block=310, size=40 (5120 KB)
INFO[boot] start block=350, size=20 (2560 KB)
INFO[system] start block=370, size=720 (92160 KB)
INFO[cache] start block=1090, size=240 (30720 KB)
INFO[userdata] start block=1330, size=718 (91904 KB)
INFO[cpld] start block=0, size=0 (0 KB)
INFO[microp] start block=0, size=0 (0 KB)
OKAY [ 0.053s]
finished. total time: 0.053s
[Nexus One Q&A, Help & Troubleshooting] Firerat:
that is strange,

I can't think of a reason why it wouldn't work
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
This information can help?

$cat /proc/mtd
dev: size erasesize name
mtd0: 000e0000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 09100000 00020000 "system"
mtd4: 05f00000 00020000 "cache"
mtd5: 0c440000 00020000 "userdata"
[Nexus One Q&A, Help & Troubleshooting] Firerat:
sorry,

the bit I really need is where to 'start' partitions

they are just the size and erase size in hex

but, soon we can get them
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
what i can help you?
[Nexus One Q&A, Help & Troubleshooting] lbcoder:
During or right after a boot, you need to get the output of the "dmesg" command.

There should be a part of it that looks similar to this:

<5>[ 7.130676] Creating 6 MTD partitions on "msm_nand":
<5>[ 7.130920] 0x0000024c0000-0x000002500000 : "misc"
<5>[ 7.133300] 0x0000026c0000-0x000002bc0000 : "recovery"
<5>[ 7.149017] 0x000002bc0000-0x000002e40000 : "boot"
<5>[ 7.159057] 0x000002e40000-0x000008840000 : "system"
<5>[ 7.321685] 0x000008840000-0x000008a40000 : "cache"
<5>[ 7.328094] 0x000008a40000-0x000010000000 : "userdata"

That will provide the information that Firerat is after.
[Nexus One Q&A, Help & Troubleshooting] iNDEX3:
I updated hboot to version 0.35.0017 (from rom for Korean Nexus One) and that has solved the problem completely!

http://xdaforums.com/showthread.php?t=722281
[Nexus One Q&A, Help & Troubleshooting] ollegut:
How did you update? Just flashed the passimg.zip?
[Nexus One Q&A, Help & Troubleshooting] RrOoSsSsOo:
With Clockwork Recovery try:

Wipe Data/Factory reset

In Mount & Storage -> Wipe Boot

In Mount & Storage -> Wipe System

Flash the ROM
[Desire Q&A, Help & Troubleshooting] mysteryfr:
Hello.

I got my Desire in HK but did not think of having an Asian ROM on it.

Can I just flash a European ROM on it or will I run into problems?

I found a page with stock ROMS in the forum (xdaforums.com/showthread.php?t=695667) - which one should I use?
[Desire Q&A, Help & Troubleshooting] suleymanc:
I would also like to change to an European ROM on my Desire from Asia. Is it possible to use one of the offical ROMS?
[Desire Q&A, Help & Troubleshooting] suleymanc:
I just successfully flashed a WWE ROM and haven't run into any problems as of now.

I used one of the official ones available on xda. However I used a goldcard even though my device was unbranded.
[Desire Q&A, Help & Troubleshooting] mysteryfr:
Which ROM did you use? I am not so much into this, so what is a goldcard?

Did you have to set the phone up once again or did the settings survive? How about the installed apps?
[Desire Q&A, Help & Troubleshooting] suleymanc:
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe

This is the ROM I used. You can find it in the post you shared above. The second WWE ROM.

Preparing a Goldcard is a relatively easy process and you can find tutorials and in the android development section of the forum.

My settings didn't survive. As far as I know there is no complete backup solution for unrooted phones.
[Desire Q&A, Help & Troubleshooting] mysteryfr:
I guess I then will just wait for the next release - no point in spending hours to flash the same firmware version with no other benefits.
[Hero CDMA Android Development] piranah:
testing this out. looks good.
[Hero CDMA Android Development] vlatinlove:
Great ROM

Great ROM only thing I noticed is that the Market goes slower than the other 2.2 but I dont mind it I like the color theming you used nice work and thanks.
[Hero CDMA Android Development] rynet91:
Still have GPS issues?
[Hero CDMA Android Development] jaybob413:
I am not having any issues, but GPS has worked pretty well for me on all of the FroYo ROMs. YMMV. ;)
[Hero CDMA Android Development] alioto1:
what is that gapps?
[Hero CDMA Android Development] piranah:
google apps.

been using the rom. love it. fast, looks good and is so much better than 2.1. only gotten one force close as well.
[Hero CDMA Android Development] feefeeboomboom:
please keep this updated

this is nice.

i really hope you keep it up to date. well worth it if you ask me.
[Hero CDMA Android Development] danaff37:
Where did ya get the kernel from? this 7/22 build actually boots for me, where as darch's 7/22 won't.
[Hero CDMA Android Development] jaybob413:
This was compiled using the source from Darchstar's repo at: git://github.com/darchstar/GoDmOdE-FrOYo-KeRnEl.git
[Hero CDMA Android Development] danaff37:
that's weird that his won't boot but yours will
[Hero CDMA Android Development] platinumrug:
I'm liking another 2.2 rom, but I'm not at all digging the theme lol. Good stuff tho
[Hero CDMA Android Development] strauss0829:
2.2 froyo

this rom is quite fast and slick but camera doesnt come on whats up wit that
[Hero CDMA Android Development] danaff37:
camera preview doesn't work in stock app in any froyo build at the moment. try camera magic in the market
[Hero CDMA Android Development] jaybob413:
You could try taking the boot.img from this one and flashing it after flashing his ROM; may help narrow it down to whether it is a kernel or init issue that your phone is having a hard time with, or something else in the build.

Do you know what the default OC settings are in his rom? Any issues with OC for your phone on previous builds?
[Hero CDMA Android Development] shabbypenguin:
nice rom will have to check it out, how did you get the sense clock on an aosp rom? i have been searching for the clock and weather in one like sense's
[Hero CDMA Android Development] sdotcarlisle:
Fancy widget in the market
[Hero CDMA Android Development] shabbypenguin:
thanks much :D
[Hero CDMA Android Development] tbaybucs:
nice n fast, but the recovery mod lost my nandroids i think. i flashed a dif rom but still have the same recovery mod, anyway to remove this , thanks
[Hero CDMA Android Development] ptowsvc:
hi,me again,i have 1 more question:confused:.cm6 7/29 vanilla rom on sprint hero not receiving text message,any ideas???mahalo again and love this rom:) any help would be greatly appreciated.
[Hero CDMA Android Development] swears11:
Is anyone using Wave Secure successfully on here?

I get an "unable to connect" error.

Also, what's up with the market? Is their a fix for this?

Besides this, the ROM is really smooth.
[Hero CDMA Android Development] cdub02:
I've been using the Vanilla ROM for about a week now and I'm really happy. Flashed from stock 1.5 --> Fresh 2.3.3 --> Blue --> Vanilla. This is by far the best one I've tried. Found Launcher Pro Plus (not in the Market, must download directly from his website) and got a couple of the sense like widgets that are almost better than original sense. Only minor issues:

-browser force closes when I add a bookmark and change the default text

-can't get facebook sync to work even with the patch...puts my phone into irreversible airplane mode...used syncmypix as a work around.

Can anyone point me to a better contacts app that will let me define multiple groups? If it can be done in the default contacts app, I can't find it.
[Hero CDMA Android Development] aquarinard:
boot process

how long does this rom take to boot up. im stuck on this htc white bootup screen. its been over 10 min now
[Hero CDMA Android Development] ptowsvc:
first launch does take some time,if no luck,wipe and reflash
[Hero CDMA Android Development] jaybob413:
Try the updates posted today. [01AUG]
[Hero CDMA Android Development] danaff37:
I noticed in the changelog something about fixing widgets on homescreen with apps2sd... did they fix disappearing widgets (from the homescreen and selection screen?) when it is stored on sd? downloading now to try
[Hero CDMA Android Development] FussyQBert:
Yea you mean darch's facebook fix kills the signal and data. I'm having this problem too. Ill try syncmypix
[Hero CDMA Android Development] Zardos66:
I love this to death, but my battery life goas into the toilet when I'm using it.
[Hero CDMA Android Development] ptowsvc:
i have downloaded and flashed with wipe every version of this rom,v1 thru aug 1 and even darchdroid v2.7 and i cant recieve text messages with any of them on my sprint hero.i nandroid backup back to my fresh 2.3.3 and it works fine.any ideas???i love this rom but need my text messaging[kids to keep up with].any help would be greatly appreciated:confused::eek:
[Hero CDMA Android Development] sean914:
is it possible to use htc_ime keyboard on this rom?
[Hero CDMA Android Development] jaybob413:
I am not currently using the FroYo apps2sd feature, so can't say from experience. Looking at the source, it looks like the change was made to fix getting icons for apps that are on SD. Let us know if this fixes the issue for you.
[Hero CDMA Android Development] pwachleman:
Building to greatness

Still no luck with MMS on the latest build, hope they can get that figured out. Hard to figure too, I have apps that list in the market on my phone but my wifes phone with the exact same build doesnt. Take for instance the weather channel app, I show it in the market on my phone, on my wifes its strangely absent.

FYI--I went ahead and reloaded this with a complete wipe and now things work, so if you dont have working MMS or you have issues with your market you might try that...
[Hero CDMA Android Development] Big-O-Devil:
Noob Q. Those this rom work on the sprint hero...
[Hero CDMA Android Development] danaff37:
Nope, still have to have widgets on phone storage, not sd. I've noticed the issue with the app icons, but restarting the launcher always fixed it for me (it only happened on boot for me). No real problem, just thought they somehow fixed it.
[Hero CDMA Android Development] pfer10:
MMS being sent out works on the Aug 1 build. Thanks!
[Hero CDMA Android Development] BAttitude7689:
Does facebook sync work with the updated rom "01 - Aug"??
[Hero CDMA Android Development] omair2005:
I used syncmypix and yes it worked:)
[Hero CDMA Android Development] ItsDon:
It is built specifically for the CDMA Hero, works great.
[Hero CDMA Android Development] Big-O-Devil:
Thank you.. will try it out...
[Hero CDMA Android Development] riotkid976:
Also having the same problem. using the black theme if it makes any difference at all.

having the problem if i wipe or not prior to flashing.
[Hero CDMA Android Development] ooyonnie:
this should work for VM

xdaforums.com/attachment.php?attachmentid=362919&d=1279525560