yashsingh1/xdaforums huggingface dataset:
[Thunderbolt General] Ovrclck:
Thread should be locked :)
[Vibrant Q&A, Help & Troubleshooting] s15274n:
Looking for creative ways to get Hulu on my tv.

I am open to ANY suggestion, but to keep it relevant to this section I need to know methods involving either the Vibrant or Android also.

Thanks!
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
Do you prefer free or paid? There's alot of paid options, but there are free options as well.
[Vibrant Q&A, Help & Troubleshooting] s15274n:
Whatever method works... Ha
[Vibrant Q&A, Help & Troubleshooting] xriderx66:
Do you have like a Blu-Ray player? you know the ones with Netflix etc? Or a PS3/Xbox?
[Vibrant Q&A, Help & Troubleshooting] movieaddict:
best option and its very easy!! if u have a pc just download playon its a media server. So if u have a wd media player or a wii, 360 or ps3 then log onto the media server on any of those, it supports many other devices too. U can watch netflix or hulu or many many other channels on there.

theres a android app too

https://market.android.com/details?id=com.playon.playonapp&feature=search_result

pc

http://www.playon.tv/playon

very easy and simple and once u get the android app u can watch netflix or hulu from ur playon on ur phone over 3g or wifi. Works great thats how i do it.
[Vibrant Q&A, Help & Troubleshooting] s15274n:
wow, I had heard playon, but did NOT realize it was on Android.

Can I then use TV out to my tv, from my vibrant? I mean, it gets wifi.. if the signal is good for the server, seems like that would work. Phone has flash.. hulu work on our phones?
[Vibrant Q&A, Help & Troubleshooting] movieaddict:
hulu works on some phones but it works on all phones through playon i think. i know i get hulu and netflix very easily.
[Vibrant Q&A, Help & Troubleshooting] s15274n:
Alright, sounds like my Vibrant + PlayOn is the way to go.

Any other options that I am missing though?
[Vibrant Q&A, Help & Troubleshooting] dsuycott:
3 months ago we canceled comcast services and picked up at&t u_verse Internet (tv not in our area yet) and the Roku HD box. Netflix/Amazon/hulu+ and lots more. Our kids use wii's for netflix. It's a switch not having regular tv but we really don't miss it, I prefer it this way.

Happy Hunting

SimplyGalaxy 3.3
[About XDA developers] StDevious:
Would it be possible to arrange the compact view of the forum index page alphabetically with the same OS devices grouped together ?
[About XDA developers] StDevious:
no interest ?
[About XDA developers] OmegaRED^:
I agree.. it makes sense.

As more and more devices get added it's gona get cluttered.
[Galaxy S II Q&A, Help & Troubleshooting] Arthur Hucksake:
Hi folks,

Just went onto Samsung Apps and I got an update to UNAService.

Any idea what that could be?

There was a longer description underneath, but I didn't quite catch it in time to see what it was. Doh!
[Galaxy S II Q&A, Help & Troubleshooting] Intratech:
It updates the Samsung App app.
[Galaxy S II Q&A, Help & Troubleshooting] msm4069:
unaservice update

For the past few days i have been trying to use my samsung and quik vid app but it always pops up that there is an update. But when i click to allow update it always goes to update incomplete. Just wondering what i would need to do to be able to get these apps working again. Any suggestions?
[HD2 Android Q&A, Help & Troubleshooting and Genera] carazy1:
Nevermind this
[HD2 Android Q&A, Help & Troubleshooting and Genera] Capt.PP:
Label this as Solved.
[Legend Android Development] icebuck:
Hey guys, it took me 3 whole days to find the right way to downgrade. :rolleyes:

Note: This is to be done at your own risk; I am not responsible for any damage or harm caused by this process.

Note: Information in this guide is taken from the works of following Authors:

1.	wag3slav3: (http://xdaforums.com/showthread.php?t=725430)

2.	Paul (http://android.modaco.com/content/ht...rom-froyo-ota/)

3.	TheDeadCpu: (http://xdaforums.com/showthread.php?t=746454)

Please Follow the Instructions Carefully; to ensure success!

Items Required:

1.	HTC Legend

2.	1 MicroSD Card (Gold Card)

3.	1 Micro USB Cable

4.	Full Charge Recommended

5.	Windows OS (I used W7)

Other Stuff:

1.	Android SDK

2.	hack4legend-v5.zip

3.	RUU 1.31 for Legend

Common Errors Faced in the Process:

1.	c---rw---- INSTEAD OF crwxrwxrwx

2.	ADB Server timed out

3.	Various RUU Errors

4. Visionary Not Working/Opening

Troubleshoot:

When you attempt to root you may face ADB timed out errors, it can be very annoying – there are various reasons for this, for me it was HTC Sync that was conflicting with ADB, shutting it down allowed me to boot into the custom recovery (step2 in the root process).

If you run into various other RUU errors (such as: unable to load boot loader, which was fixed by following step 3 correctly.) while trying to downgrade, most likely you didn’t do it correctly. Try doing it again and it should work.

Visionary Not Working/Opening (Solution: Download from phone browser: http://content.modaco.net/dropzone/c...ryplus.r13.apk)

Recommended to Back up Data:

1.	Contacts:

You can save you’re contacts from you’re legend by clicking contacts, menu, import/export and export to SD Card.

2.	SMS:

Get the SMS Backup and Restore App form Market, Install and Save it on to the SD Card.

3.	Backup Complete SD Card:

Copy all the contents of the SD Card and save it onto the PC.

We start now;

Step 1:

Install Android SDK

Extract hack4legend-v5.zip to C Drive

Step 2:

Have adb in your path, or move the files contained in hack4legend-v5.zip into your sdk/tools directory so your pushes will work properly.

FOR ALL OS's Make sure your phone has Applications->Development->USB Debugging turned on.

Do NOT have your phone in Disk Drive Mode, have it in Charge Only.

Open a terminal window in your /tools/ directory. Type this at the prompt.

Code:

crackin.sh

or in Windows

Code:

crackin.bat

Your phone will reboot 5 times.

You WILL see several error messages.

it looks like this c---rw----

c---rw---- 1 1001 2002 90, 0 Jul 19 16:19 /dev/mtd/mtd0

You’re done with this.

Step 3:

- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)

- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'

Step 4:

RUN RUU to downgrade to 2.1 – it should be possible to do so now.

Hence, you will be downgraded to 2.1 and you can use the normal way to root your legend.

All I can say is that the CM7 Mod is so fast on the Legend, no lag whatsoever, it's beyond! (will post a video 4 you guys) :P

End. :)
[Legend Android Development] bonesy:
Forgive me if i seem rude.Hasn't this been covered in many other threads before?
[Legend Android Development] icebuck:
I searched the site but never found this same method, is a combination of 2 or more guides at one place, also touching on some of the common errors faced when downgrading. :)
[Legend Android Development] alfagama:
after this command '/data/local/flash_image misc /data/local/misc1-2.img'

it says "flash_image not found"....
[Legend Android Development] BlaY0:
So? Find it and put it there via adb.
[Legend Android Development] alfagama:
but this is what i try...

i have both files in c:/hack4/ and in c:/android-sdk-windows/tools/

i wright in command " /c/hack4/flash_image misc /c/hack4/misc1-2.img"

and i have the message "flash_image not found"

am i doing something wrong?

i have also tried "/c/android-sdk-windows/tools/flash_image misc /c/android-sdk-windows/tools/misc1-2.img" the same problem...
[Legend Android Development] bonesy:
What hboot do you have? Look at the guide for YOUR hboot ive had different Hboots across 2 devices and needed to use the right guide for the right hboot
[Legend Android Development] alfagama:
i have 1.01
[Legend Android Development] bonesy:
http://xdaforums.com/showpost.php?p=10217134&postcount=1
[Legend Android Development] alfagama:
i have tried this to... the same problem :(
[Legend Android Development] QkSi1ver:
Are you sure you executed these codes from Guide 2 ?

These is supposed to upload the images required on your phone and be exventually be executed on your phone to replace the image

ps: im no expert but i just flashed mine recently and i had to read the guides several times to understand the logic behind each guide to avoid mistakes some had with their phones...
[Legend Android Development] bonesy:
Then you cant be followign the guide right.Have you done temproot?
[Legend Android Development] alfagama:
yes i tried with visionairy13 and 14 both time i had su= #

a noob question...'/data/local/flash_image misc /data/local/misc1-2.img' =" /c/hack4/flash_image misc /c/hack4/misc1-2.img" where i have the 2 files...
[Legend Android Development] bonesy:
Blay0 answered correctly...i didnt
[Legend Android Development] BlaY0:
Nooooooooo dammit! You have just pushed both those files to your phone!!!!!!!!! Go to your phone shell via adb, execute su to gain root privileges and then execute flash_image on your phone not on your PC!!!!! It doesn't really matter where on the phone do you have both as long as they are both in /data dir and don't prepend anything!!!
[Legend Android Development] alfagama:
i am very confused now :(, can yoy help me step by step?

i run on my phone visionairy and then i click on temproot.

then i run on my pc cmd and i give the comand "adb shell" and then i type su and it says #...

after that should i give the next command on the pc again or on my phone, and with what should i replace the /data/local/ ...?
[Legend Android Development] BlaY0:
Pay attention dude!

Open two command prompts. Name them ONE and TWO. You gonna use ONE for copying files from your PC to your phone using adb push. You gonna use TWO for connecting from your PC to your phone using adb shell and execute all commands meant to be executed on your phone there. Now use ONE to copy (adb push) a program called flash_image to your phone's directory /data/local. After you do that use TWO to connect to your phone (adb shell), execute su to gain root privileges (you get # prompt) now in the same commnd prompt (that's TWO) change permissions of program flash_image you have just copied to your phone in ONE. Then also on TWO execute flash_image program with parameters from above.

If you don't understand what I'm saying you better sell that phone and instead use phone booth. In fact sell all your hi-tech stuff including your PC. It would be much safer for you and even for us.

Sent from my HTC Legend
[Legend Android Development] Catnap:
Faaaairly sure you're gonna want to write C: and not c/ dude, regardless of what other stuff you're doing wrong.
[Legend Android Development] alfagama:
my friend i pretty sure that you know much than i do...

but for your information i am 48 and i am the last 20 years involved with computers and mobile phones.... over that 20 years i have learned at least to follow instructions (if they are clear), so once again thanks for your help.

my problem was that after unistalling sync 3.0 and installing sync 2.033 i have not uninstalled the drivers so i had problem.

after fixing that everything went smooth.
[Legend Android Development] BlaY0:
So after 20 years in computers, you actually found out that the problem was on your side and not in the instructions. Too bad. My mom is also been using computers for more than 20 years. She knows what is monitor and that she can move cursor around with the mouse.

BTW what has version of sync to do with your confusion? You are trying to say that "flash_image not found" error had something to do with sync version? Ohh, give me a break...

And as far as clear instructions are concerned... I guess they are pretty clear if 99 ppl find them OK and one (that's you) doesn't.

Don't want to be rude but maybe 20 years was too much and it is time to start something completely different.
[Legend Android Development] alfagama:
my friend i dont want to argue with you, the problem was not the sync 3.0 but the drivers.

about the guide now, have i told you that he was not clear? and when i say thank you i mean it, it is not ironical.

btw thanks again for your gr8 rom...
[Droid Incredible Android Development] bast525:
Would any dev or anyone who knows a bit about compiling be able to do this? I've tried some other kernels, and generally love some of the features and performance they bring, but none of them has been 100% stable for me. Stock kernel is 100% stable, but lacks the 5 point multitouch which I do use for emulators, and GPU+ which makes a noticeable difference in 3D graphics smoothness.

The closest I found was HeyItsLou's #8 (I might have the number wrong) which runs great, has the multitouch, but no GPU+ :( Lou's has some other good features that seem to help smoothness and battery life too.

Maybe Lou or someone could throw GPU+ into that kernel? Or just take the stock kernel and add GPU+ and multitouch? Would anyone else be interested in this?
[Droid Incredible Android Development] phydo:
Um what about the. 32 incredikernel?
[Droid Incredible Android Development] bast525:
That's what I'm running now but it will randomly peg the CPU (system panel shows Android System as maxed out) and slow the phone to a crawl, requiring a reboot. And no, I'm not running SetCPU. That is the ONLY problem I have with that kernel, but I've never had that happen on the stock kernel. I don't want to deal with the random lockups anymore.

Ziggy's kernel doesn't have the lock ups, but doesn't run as smooth either, and I notice a lot of stutters while gaming.
[Droid Incredible Android Development] phydo:
I don't know why that would be. I compiled it for someone a few days ago and he loves how it runs.
[Droid Incredible Android Development] jdog94:
what is 5pt multi touch?????
[Droid Incredible Android Development] wdfowty:
Just that, you are able to use five fingers (or "points") simultaneously.

From my understanding, multitouch is affected by the touch panel you have, and also the way it is flashed. There was a compatible recovery floating around a while ago, but it's no longer maintained.
[Droid Incredible Android Development] phydo:
Yeah not all phones support 5pt
[Droid Incredible Android Development] bast525:
Phydo - I've actually been running your undervolted version of Chad's kernel for the last few days. I'm still having the same issue. In Chad's thread, there were actually a few people having the exact same issue. It was thought that SetCPU was somehow to blame, but again, I don't even have that installed.

From a performance standpoint, Chad's kernel is the one I've had the best results with and keep going back to, but this issue with the CPU getting stuck at 100% load happens regularly, every 24-48 hours.
[Droid Incredible Android Development] aweaver33:
I'd be willing to bet your problem is the ProcessStats.java bug documented in Issue 9733. It is exacerbated by kernels that add extra frequencies. Some ROMs work around the issue by making the time_in_state file unreadable, but SetCPU undoes this workaround every time you open it. 24-48 hours seems about right for the time it was taking for me to run into this problem. I'm now running with an init.d script that redoes the chmod 600 every 5 minutes just in case I open SetCPU and the problem has gone away.
[Droid Incredible Android Development] bast525:
Aweaver33 - would this be something I could easily incorporate into my own ROM? I'm running a mostly stock ROM that I customized by adding an earlier Evo framework and taking out some stuff I didnt want. Would I be able to flash your init.d script? Or since I don't run setcpu, could you explain or point me somewhere I could figure out how to make time_in_state unreadable?

EDIT: nevermind.... aweaver you are awesome for posting that link. I will try to chmod the time_in_state file as outline in that thread and see if I can make it 48 hours without it making the cpu.

Do you know how specifically this is kernel related? I've had this issue with Chad's kernel, and the old KingKlick kernels. I have NOT had the issue on the very old Hydra kernel or any of the stock kernels. I guess its just the number of frequencies they enable? Man if chmod'ing that file is all it took to fix that bug.... you are my friggin hero dude. I've been mostly using Chad's kernel since December and love it but MAN I hated the phone locking up every two days!
[Droid Incredible Android Development] aweaver33:
Yeah, it's mostly just the number of frequencies they enable. Also a potential, but smaller, contributor would be governor settings that result in a more even distribution of frequencies, which would result the overall file size getting larger more quickly. I first noticed this issue when I was doing stability testing that intentially created an even distribution of frequencies and made it less than a day before triggering the bug.
[Droid Incredible Android Development] bast525:
Well, I'm at 36 hours of running now, so far no issues. I did open the time in state file and noted it is still updating, though the permissions were correctly changed.

My only problem now is the leaked GB roms that popped up today... I want to flash one but I REALLY want to see if after six months of dealing with this very annoying bug, if it is finally fixed. I gonna TRY to resist flashing til tomorrow.
[Droid Incredible Android Development] bast525:
Any way to make the change in permissions to the time in state file stick? It undoes the changes on reboot
[Droid Incredible Android Development] aweaver33:
That's where the init.d script comes in. Put the following in a file in /etc/init.d/ and set permissions to 755:

#!/system/bin/sh
while [ 1 ]; do
chmod 400 /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
sleep 300
done
[Droid Incredible Android Development] bast525:
If there is no /etc/init.d folder, and I create and throw that file in there will it work?

EDIT: nevermind... tried it, didn't work. Created the folder, put the file I'm there, rebooted. Let phone sit five mins, looked at permissions for time in state file, they were still at default. Does it need to have an extension? I just named it "fix".
[Droid Incredible Android Development] aweaver33:
Sorry, it looks like the /etc/init.d/ directory is not standard Android. The following is the last line in my /bootcomplete.inc.rc file, which looks like what enables running the scripts in the /etc/init.d directory:

/system/xbin/busybox run-parts /system/etc/init.d

I'm not sure if that line was automatically added when I installed busybox, or if something else put it there.
[Droid Incredible Android Development] bast525:
It's cool, I found an alternate method. There's a very small app in the market simply called "Autostart", to use it you create a script, name it autostart.sh, drop it in a folder you create in /data/, and it runs at boot same as if it were in init.d. I took your script and modified it a bit to make it not repeat every 300 seconds. I don't run SetCPU so I only need it to run once at start up.

I still haven't let the phone run for 48 hours straight to verify this fixed it, but still man thank you for the info, it is greatly appreciated. After reading that Google bug thread you linked, I have very high hopes that this is the fix I've been looking for for six months now.

Thanks again man and I'll report in a day or two as I have no more reasons to reboot for a while.
[Droid Incredible Android Development] bast525:
48 hour mark just passed and still running like a champ :)
[G2 and Desire Z Q&A, Help & Troubleshooting] obas:
I am trying to flash my rom to this rom

http://xdaforums.com/showthread.php?t=1054574&page=10

However, when I go into the bootloader and then into recovery I get a phone with a red triangle and a !. I'm a little confused what to do to get to my sdcard and push the new rom.

Any help is greatly appreciated.
[G2 and Desire Z Q&A, Help & Troubleshooting] ilostchild:
are you rooted? need to be rooted to flash rom,

if you are, when you get that screen

you pres hold vol Up and press power
[G2 and Desire Z Q&A, Help & Troubleshooting] obas:
Nope, I am not rooted.

Would you recommend these steps for rooting a G2

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

HOW TO ROOT and S-OFF

- For rooting questions, please refer to the proper thread (rooting methods).

- Rooting an HTC Vision is a pain in the arse because there are many variants/versions, and not all rooting methods can be used on all of them.

- There are many ways to get root access: "rage" (ADB command line type) "visionary" (an APK installable app by paulobrien from Modaco) and "gfree". Using "Rage" is safer, "visionary" is simpler but many problemshave been reported, so "gfree" is the betterway to go.

- After using any of these, you can go further and turn S-OFF, CID-unlock and SIM-unlock the phone with "gfree", a safe and neat script written by scotty2 et al @ #G2root IRC. Sounds confusing ?? Just follow the instructions on the Wiki.

- TO ROOT, FOLLOW THE STEPS IN THE WIKI

VISION WIKI: ROOTING

- To check if your phone can be rooted you can check this neat thread:

[GUIDE] Root AND Downgrade ANY Desire Z or G2

Thanks to Aegishua

- Before "gfree" was available, transitory ("fake") S-OFF was achieved by flashing an engineering hBoot, but it is not safe and not recommended for newbies.

- As for reference, qpop made a neat a simple guide to get root S-OFF and CID unlock with visionary and gfree. It works a treat with Bell-NAM phones, but visionary sometimes doesn't work for some Asia/Voda versions.

The thread is located here: http://xdaforums.com/showthread.php?t=857390, download the "UberRoot" package from the post footer, and follow qpop's guide.

(thanks scotty2 for your hard work and qpop for the guide !!)

- fattire has another neat and clear guide/tutorial for using gfree version 2, the thread is located here: [Guide] Subsidy Unlock, SuperCID, and Radio S-OFF

- More instructions and several methods to root in the WIKI:

WIKI - Rooting the HTC Vision,

and HTC Vision Permanent Root,

- You will need an ADB shell to run gfree and for other stuff. Please read the FAQ if you don't know what this is. If you don't have an ADB shell already set up and running, download the ADB drivers and the Mini ADB from this post's footer or download the full Android SDK (which includes ADB) and the HTC Sync software (to install the USB drivers on your PC).

- The older rooting guide and the older (and not so safe) "hBoot" way to ("fake") S-OFF have been moved to post 3 for reference purposes only. Plese scroll down to post 3 should you want to read the older guides.
[G2 and Desire Z Q&A, Help & Troubleshooting] ilostchild:
no i recommend using the wiki method, with gree .5

http://xdaforums.com/wiki/index.php?title=HTC_Vision
[G2 and Desire Z Q&A, Help & Troubleshooting] obas:
Ok, first I want to thank you guys for your help. I am using this guide;

http://xdaforums.com/wiki/index.php..._Root_.2F_.22Permaroot.22.29_using_gfree_v0.5

I have two questions. First does "Having the proper USB drivers installed - Windows USB Drivers for the Vision" - does this apply only for the vision or both the vision and the G2

And the second question is for step "2. Copy the files to the phone" I have downloaded all the files to my desktop and I want to unpack them in the folder called "root" from there I go into start->run and type cmd to go into command prompt

C:\root adb push psneuter /data/local/tmp/

C:\root adb push gfree /data/local/tmp/

C:\root adb push busybox /data/local/tmp/ ...etc and so on correct?
[G2 and Desire Z Q&A, Help & Troubleshooting] obas:
I am trying to setup ADB using this guide

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

INSTALLING ADB ON WINDOWS - METHOD B, THE "QUICK" WAY, NO SDK

However, the link for the file appears to be gone for step two. Curious as to where I could find it.
[G2 and Desire Z Q&A, Help & Troubleshooting] ilostchild:
best to install sdk in C:/ then if you can set adb.exe in your windows enviroment