yashsingh1/xdaforums huggingface dataset:
[Windows Phone 7 Q&A, Help & Troubleshooting] rachnov55:
thanks for all the replies

what I need to know now is, is there anyway to access folders OTHER than the one marked documents on skydrive via my wp7 handset? When I sync my pc with skydrive there's a dedicated space called "Sync Folder"

I can't seem to access it with my handset
[Windows Phone 7 Q&A, Help & Troubleshooting] Aaron McCarthy:
going to have to wait till they release office 365... sharepoint doesnt even work with our phones right now unless you happen to have a dedicated quad core server running sharepoint on that or something. I fiddled with it all for DAYS trying to get it so I could access work documents on my phone from sharepoint but NOPE! Pretty radiculous. Office 365 isnt even going to be available probably for another year! *sigh*
[Windows Phone 7 Q&A, Help & Troubleshooting] StevieBallz:
Originally SkyDrive and LiveMesh were products that had nothing whatsoever in common (except for being Cloud services). Lately Microsoft decided to merge them a little - so now you got a 25 GB SkyDrive AND a 5 GB Sync-SkyDrive. Those two can't talk to each other and if you got a Word Doc on the Sync-Drive you can't open it in office Web. If it's on the REAL Skydrive you can access it.

Unluckily only the pictures hub and OneNote currently integrate with the real SkyDrive and there is no integration with the Sync-Drive.

My guess is that doc/xls/ppt, etc. access from the office hub to SkyDrive is coming with an update.

When Microsoft is gonna clean up the mess of the two different SkyDrives is an entirely different matter - would like to see them merged (even if I afterwards have only 25 GB instead of 25 + 5).
[Windows Phone 7 Q&A, Help & Troubleshooting] andrew-in-woking:
Would you mind sharing your method

Hi mwako

Would you mind sharing your method for mapping a Skydrive folder?

Many thanks

andrew-in-woking
[Windows Phone 7 Q&A, Help & Troubleshooting] arturobandini:
Actually I'm trying to figure out how Skydrive is supposed to work, but I don't understand the idea...

Its limitations ruin the whole concept:

- Impossible to upload folders to Skydrive. This is insane.

- Each transfer is limited to 50MB.

Therefore I find Skydrive useless for business purposes, especially compared to other systems such as Dropbox.

In my daily job I need to transfer folders of office files. And they need to stay organized as such.

If I cannot upload folders to Skydrive, or if I can only upload files without any organization. what's the use?
[Android Themes] DDoZ:
Hi!!

Sorry, for mistake I've posted in the wrong section.

I've already created a new topic in the right section ( I hope, it's in development ).

Could you please delete this topic ?

Thank you and sorry again.
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
I have an unrevoked-forever (s-off) Incredible, running CM 6.0.2 (stable). I have been running an 8gb sd in, but recently I have been reaching the limits.... so I decided to upgrade it to 16gb.

I copied all the files from my 8gb to my PC, via phone USB. Then from my PC to a 16gb card, via card reader. When I unmounted the 8gb, and replaced it with the 16gb, it would not remount. I then started getting low memory warnings....but still could not get it to mount the SD card, old one or new one. So I rebooted and now I'm stuck in a boot loop, with either memory card, for some reason....

I tried a nandroid backup, and it says complete with one line saying "SD-ext.img not found- skipping...." then on reboot, it still goes into a boot loop.

Suggestions on what to try next are VERY welcome. I guess I should have not tried swapping the SD card while the phone was on?? I can of coarse boot into recovery, and I do have ClockworkMod 2.5.0.1.

Worse case scenerio, wipe? and run apply CM from SD card?
[Droid Incredible Q&A, Help & Troubleshooting] SynbiosVyse:
Why do people always get scared about the SD-ext error messages, where it's clearing data, formatting, or restoring backups. SD-ext is for apps2SD. The SD card partition for general storage is called sdcard.

With regards to your problem, I have no idea, Sorry.
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
I have no idea what SD-ext is for...I'm not "scared" of this error, I just want to get out of bootloop....if it's not related or important information, sorry....I assume I messed something related to the SD card....considering how/when this started happening....but of coarse I don't know exactly what I did, that's why I'm asking.

I don't get an "error" screen, I just get a boot loop. I don't even know where to begin to toubleshoot this....so thats what I am asking for...suggestions.
[Droid Incredible Q&A, Help & Troubleshooting] SynbiosVyse:
I thought that you assumed that error was the problem.

Does your phone still reboot loop when the sdcard is removed completely? You can try backing up the contents of the card onto your computer..then format it with FAT32 in windows. Try it with a completely empty card, but formatted as FAT32 of course.

If you're still having problems then if I were in your shoes I would resort to a factory reset, clear everything, and then start fresh (especially considering your nandroid backup did not work)
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
The boot loop happens with, either card, and also with no SDcard in. I only get to the Cyanogen animation and it keeps looping......I will try formatting the cards on the PC and then pasting the SD card "copy/backup" from my initial try....

---if worse case----

I have never installed other roms, I have had relative success with CM....so I really don't know how to "wipe" and start fresh.

Are these steps close:

1. boot to recovery> ClockworkMod

2. select wipe data/factory reset

3. select wipe cache partition

4. select advanced> select wipe Dalvik cache?

5. install zip from SD card > select CM- 6.0.2

6. done?
[Droid Incredible Q&A, Help & Troubleshooting] SynbiosVyse:
Yes, those steps sound correct to me. That is your best shot.

The Incredible in general has reboot problems, for some reason it is very sensitive. I'm not really sure if you changing the SD card truly caused the problem or not, but it's worth reflashing the latest CM. I recommend 6.1 RC2

6.0.2 is quite old and it has a lot of problems, including force close mail client by default, a faulty radio interface layer that may cause reboots, and many, many other fixes have been implemented in 6.1 RC2 and the latest nightlies. Don't be discouraged that it is a release candidate..in reality it is much more stable than the 6.0.2 "stable".
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
Well I downloaded a fresh 6.0.2 and 6.1 RC2 from Cyanogen....I followed the steps above to "wipe" and installed the 6.0.2....result= bootloop still

repeated steps to "wipe" again......selected to install 6.1 rc2......result= bootloop still

SO now I'm really at a loss. I figured with a wipe it would work....maybe my steps are wrong.....ANY suggestions now are welcome.
[Droid Incredible Q&A, Help & Troubleshooting] linuxmotion:
Do you know how to use advanced from the android ask. It can be used to figure out where your problems are.

Might be that the Dex cache is being created, but that only happened to me when flashing my own custom roms, not when changing SD cards.
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
No I do not know how to use the "advanced from android ask." But I am willing to learn if needed.....Is this the SDK tool? I believe I toyed with this when I first used the Unrevoked method to root....but thats been months and I don't mess with roms much. I started playing around with SDK a few minutes ago to familiarize myself....but idk.....

Is there a simple way to get some kind of log file? Can I load another recovery, like Amon_RA style type, which has some different options....but I don't know if it will help......Thanks for all suggestions thus far.
[Droid Incredible Q&A, Help & Troubleshooting] SynbiosVyse:
See I'm not exactly sure that the SD card was what caused the malfunction in the first place.

If you have an AMOLED incredible your 3G radio or battery may be beginning to fail...as I said before the Inc is very sensitive and tends to reboot a lot for stupid reasons.

You can certainly get a log if you use LogCat from ADB, but if you cant figure out exactly whats happening, then most likely you need a replacement.

You can unroot, turn S-ON, and put a stock RUU and see if you still get reboots (I'm willing to be that you will). But if you still get reboots completely stock, since you're stock you can go to verizon now and get a warranty replacement.
[Droid Incredible Q&A, Help & Troubleshooting] smtom:
Quick review

- you unmounted the 8 Gb SD card, and removed it from the device while the device was still on, replaced it w/ the 16 Gb SD also while device still on?

- in the last working CM 6 ROM... were you using the SD card to cache memory or any other SD card usage tied to an AOSP ROM?

- what apps had you moved to SD card?

Absent all that, try and d/l a non AOSP ROM, for instance Virtuous, place it on your SD card in Recovery, and see if you can flash it.

Why? Solving for whether the device boots and will load a ROM at all - AOSP ROM's utilize the SD card more than Sense ROMs.
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
Correct.

I did use a rooted app to move things to the memory card, but I didn't see any benefits so I moved it back, at least I selected too, whether the program moved them back or not.....hmm...

you know I'm not sure I moved apps back. I know again I didn't see the benefit of apps/cache on the SD card, so I moved it back to phone....

------

Status as of 12/06/10 11:18am est.......Things I have done since last posts.

1. I have wiped numerous times via ClockworkMod. And tried CM 6.1rc2. Still got loop.

2. I installed Amon_RA recovery, wiped everything, formatted SD card through Amon, partioned SD card through Amon.....installed Cyan CM6.1 listed above, and phone sat loading at the initial screen "htc Incredible." Let it sit for 10+min....still nothing....

3. Tried to repeat step above...same results, now just initial screen, NO bootloop.

4. Installed ClockworkMod 2.5.0.5. Wiped. Install Virtuous 3.1.0. Recieved an error during install....."E:\" unable to read data...followed by a string of numbers and other info.....

5. Wiped.

6. Installed Hboot 92. (upgraded from 77)

7. Tried MIUI v0.12.3. Rom installed "successful." Rebooted and stuck on initial screen. been 5+ min as of now....

So NOW I am not getting a Bootloop....just a frozen screen. I can still get into recovery, so hopefully I still have options. Your insights or suggestions are the only thing keeping me trying ATM....I'm running out of options of my own.....
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
Well I still haven't got past initial boot screen with MIUI, even though it said installed correct during flash.....

SO I tried to wipe, and install Virtuous 3.1.0 again. got the same error...wrote it down this time:

E: Can't chown/mod /data/app (operation not permitted)

E: Failure at line 8: set_perm_recursive 1000 1000 0771 0644 DATA:app

Installation aborted.

I'm still at a loss, and taken any pointers or ideas. I may play around with other roms, but idk.
[Droid Incredible Q&A, Help & Troubleshooting] heiney5:
1. I tried Skyraid_333 and had the same results. Locked on initial white screen.

2. Wiped and tried a "stock" rom available from Virtuous.....http://www.virtuousrom.com/p/other-releases.html

It loaded and then it actually booted to the red eye droid (different from my original post which was the CyanMod boot anim)....yay....then it froze (eye stopped moving)....tried booting w/o SD card...same thing....

3. Wiped and decided to try Virtuous again. This time it loaded and installed "completely."

It booted again to the red eye animation....seemed to freeze, but I left it, and it finally started after 5+ min....I finally got a phone back.....

I do not know entirely what I did, in the process of loading all these roms. I do remember when I installed the "stock" rom, listed above, it had an install step which said installing "BOOT." (or something like that) I do not remember this listed step on the other rom installs...although they may do it and not list it....idk....

I have a feeling that the stock rom did something, but I don't know why a "wipe" does not reset everything, and why any rom wouldn't work....So I'm stuck back with HTC sense, due to the time I have been without a phone, I will live with it....I forgot how much I dislike this sense.......

Thanks to everyone who chimed in.
[Droid Incredible Q&A, Help & Troubleshooting] bearaids:
Congrats on you fixing your phone. I am still very new to this myself, but one of the first things I would have done would be install a stock rom again. It sounds like you lost or had some corrupt files which were fixed by going back to stock. If it were me I wouldn't be scared to wipe with a custom rom or nandroid backup, but thats just me.
[Droid Incredible Q&A, Help & Troubleshooting] Dobrah:
i'm stuck with a similar problem: phone (dinc rooted, recovery CM 2.5.1.2, hboot .92) currently frozen on htc splash screen -

How it happened:

I was running MIUI 0.6 1.1.28.1, tried to re-format the SDcard to wipe it and start from scratch again. Did not nandroid beforehand (wiping SD) but pulled the 0.6 1.1.28.1 zip to my desktop. Tried formatting but phone wouldn't format it properly - wiped all info from SD, but no longer readable by phone or computer.

Used Mac disc utility to re-format and erase card to FAT32, still un-readable. Phone now only boots to splash screen, recovery works.

Brother has an un-rooted dinc so I grabbed his SD and mounted the card to the Mac via recovery, wrote onto it the MIUI rom I was previously using and did a full wipe (data, cache, davlik) and installed rom - rom installed correctly but still couldn't get past htc splash screen

Gave bro back his SD and tried mine again - got it to mount to the phone by partitioning through recovery, re-installed MIUI rom to my SD card and tried rebooting a number of times, still can't get past the splash screen (15+ mins)

Currently downloading virtuous "stock" rom as posted above and will try to wipe/ flash. It's a huge zip compared to the MIUI zip - maybe that's a good thing?

Here's to hoping.
[Droid Incredible Q&A, Help & Troubleshooting] Dobrah:
Have tried flashing multiple versions of MIUI rom, packaged by n_i_x and warttack - no luck on either.

I just flashed the virtuous "stock" rom and got to the droid eye splash YES!! Mine may also be stuck in that screen though on the droid eye.
[Droid Incredible Q&A, Help & Troubleshooting] Dobrah:
IT'S WORKING!!!!!!!!!!!!!!!

Can't even begin to say how relieved I am - I'm never getting rid of that magical virtuous zip.

So glad someone had gone though this before me.
[Droid Incredible Q&A, Help & Troubleshooting] smtom:
AOSP interacts w/ SD

Handy information to know -

AOSP ROMs interact w/ the SD card quite a bit, whereas Sense ROMs not so much.

So, if a new SD and boot w/ AOSP, expect it to be wonky, particularly during boot.

hth
[Droid Incredible Q&A, Help & Troubleshooting] xmilkmanx:
i dunno what caused it but mine has been doing this for about a month. Got my refurbished phone in today so HOPEFULLY that one will work better, but i dont really expect it, as this stupid boot loop issue seems to be a VERY common problem with inc's. I probably wont ever buy an HTC after this one, should have learned my lesson after the touch pro

anyway, even on stock rom, unrooted, with nothing extra, mine does this for no apparent reason
[Android Software Development] DDoZ:
Hi there ^^!!

I was wondering if any of you developers is already or would like to work on a game Nokia Bounce like for Android.

I'm not a developer, so I could only use... play with it :p

I already know about BallVenture, but it's not exactly the same :(

What do you think about it ??
[Android Software Development] PatricB:
Yes, I'd go with that!

I woke my old Nokia 6600 up to accomodate my new simyo sim, and first thing I did with it was play Bounce!

Been searching for a long time now, but there isn't such a thing. I prefer the old version, nog the 3D they made for nGage later on.

Unfortunately I'm no programmer either, wanted to learn Java, but never got to it (apart from buying some books)

Anyone?

Greetz, Patric
[Android Software Development] Ihaveatattoo:
Have you tried the .jar file in J2ME runner from netmite or jbed?
[Android Software Development] DDoZ:
It could work for someone, but, since my phone is only touch, no keyboard, as lot's of android phones, how can I play with it ?
[Android Software Development] Ihaveatattoo:
No D-pad? or ball?
[Android Software Development] DDoZ:
Nope, I'm a "proud" owner of an xPeria X8, & probably in the future of an HD2, but I'm not sure about that.
[Android Software Development] Ihaveatattoo:
No problemo, fire up Bounce with netmite's runner and push the menu key and choose D-pad. Now you have an onscreen D-pad!
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
Hello & yes, yet ANOTHER person with this issue. This is what I've done:

It all started by going out to unlockr's page & following their rooting how-to. When I did this it put it in the never ending dell screen flashing lights loop. I've researched quite a few hrs on this. This is what I tried:

1) Doing factory restore (holding volume buttons & pwr buttons down) & choosing restore.

2) Borrowed a buddies SD card & tried a restore (did nothing)

3) Followed a couple of guys instructions on doing a restore one of them being here: http://xdaforums.com/showthread.php?t=776883

After following the directions I did see it look like it was updating back to the 1.6 OS, but after it rebooted it was still stuck in the Dell flashing loop cycle.

SO I did probably the dumbest thing I could do & took it back to Best Buy who is shipping it off... most likely to get my warranty canceled, but I didn't know what else to do. I had purchased their protection plan, so I'm not sure how it's gonna go. They would have replaced it in the store, but I had already returned my 1st one as it wouldn't boot right out of the box (not my fault).

So I figure if they don't flash it at Dell & get it back to working, I'll have to keep working on it myself to correct the issue....

So I guess my question is, any advise on why mine is being so difficult or is this just the way it is & it takes several attempts to flash these things sometimes? Or has Dell implemented a security feature in the new releases & that's what is causing my headache?

Those of you who feel the need to rain down the "Dumb thing to do returning it" please save those comments as I've already stated "I know".... I just need some positive input on getting this thing back on "it's feet" IF Dell doesn't fix it for me.

I will keep you posted on the Best Buy/Dell Drama that I'm sure will start up... I will say that if it's not fixed, I can't say that I'll continue with paying Best Buy $10 a month for a protection plan, as they supposedly will replace the phone if it was damaged in any way. If anyone has info or a story on that part of it I'd like to hear it as well.

Thanks in advance!
[Streak 5 Q&A, Help & Troubleshooting] rodjordan:
Look for the upgrading downgrading guide in xda. Nornally starting from 4399 build is a good start to get you back up and running.

http://android.modaco.com/content/dell-streak-streak-modaco-com/317549/how-to-go-back-from-21-to-00-builds/&source=android-home&ved=0CBoQFjAB&usg=AFQjCNH7W3lUKYibzBQg4qVNxKs955Q0LQ
[Streak 5 Q&A, Help & Troubleshooting] topshelf95:
DON'T USE THE UPGRADING/DOWNGRADING GUIDE!! IT WILL BRICK YOUR WHITE STREAK!!

The white Dell Streak is known to have something different going on with it. There is a special tool (QDLTool) that is needed to upgrade it/unbrick it. It takes you directly to stock 2.2 and you can do what you want from there. See this thread here for more information and a fix.

http://android.modaco.com/content/d...24010/warning-white-dell-streak-is-different/
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
Thanks for the knowledge! Didn't know there was a difference, although I suspected something was amiss when I was doing what I was instructed to do but not getting results....

Any more info is appreciated so keep it coming!!!
[Streak 5 Q&A, Help & Troubleshooting] decoyeb:
erm not that im saying this BUT you got protection(inshureance)accidently drop it in a sink full of water or some such like acident pay your excess and get a new one.

but i dint say that.There norm pritty good at replaceing your phone after such an acident
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
We'll see what happens when I get the phone back... the post from TopShelf95 may just have saved it from a fate similar to that! HA!
[Streak 5 Q&A, Help & Troubleshooting] bigfoots1:
other solution

Solution # 2

Take the phone back to where you bought it and get the black one.

As some of you may know my white one met similar fate and after hours of getting no where i just took it back and got the black one.

after 20 minutes of getting it home i had froyo 2.2 running on it.

besides..do you really want a white phone? lol

i didn't. they were supposed to give me a black one to begin with..

I told the returns lady i wanted a black one and they gave me a white one. when they booted up the phone it didnt boot and they did not say one word. they just went and got me a black one.

Frankly this was the only reason i bought one from bestbuy..

it certainly wasnt because of their pricing ;)

Good luck.
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
Bigfoot, if you'll reread my original post you'll see that I've already returned one & tried to return the white one, but they would only allow one instore return. I don't care if it's white or black (I'm not racist HA!) it's gonna be in a Otterbox Defender anyway. I just want a phone/tablet that works at this point.

We'll see how the above mentioned "fix" works if I have to install it when I get my phone back.
[Streak 5 Q&A, Help & Troubleshooting] Hebinator:
I have the white streak too and I can tell you that the QDLTool works like a dream. Just follow the instructions to the letter and you will have 2.2 on it in no time. The Streak is virtually impossible to perma-brick. Since QDLTool works on a lower level than fastboot, it will work even when all else fails.
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
Awesome again good to know!
[Streak 5 Q&A, Help & Troubleshooting] borijess:
Does the qdltool work for the black streak?

Sent from the Dell streak
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
FINALLY (update)

So after 42 days I FINALLY got my phone back from Best Buy... WORST customer experience... I would tell the whole experience, but I'll just make it short... they couldn't find it at one point, they shipped it back 42 days later, my 16 gig sd card is missing from it & when I got it back, they'd not reflashed the phone. So they did nothing but basically steal my sd card & gave it back to me....

ANYWAY.... After I went back to BB to find out what they were gonna do about my phone not working (which I'll have to call mgr tomorrow) I got home & followed the instructions given in this thread to flash my white dell streak & IT WORKED!!!! No issue 1st time around... Perfect, almost as easy as jailbreaking an iPhone... THANK YOU VERY MUCH FOR THE HELP!!! You guys are awesome...

Now... I have a friend who is also asking will this process work for the Black Dell Streaks... so will it?
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
also

this puts your system into an unlocked status which enables you to download the official Dell 2.2 ver. One downside to it is it shuts off your wi-fi hotspot...

Good thing about the Dell ver. it fixes the buttons sensitivity for one thing that seems to be an issue on the QDAtools ver... I'm sure later builds that is fixed though (would think it would be)
[Streak 5 Q&A, Help & Troubleshooting] logun1970:
WRONG

I was wrong (looked in the wrong spot) wi fi hotspot is there... my bad