I was wondering if anyone has figured out a way to get HULU to work. Thanks!
For WebOS there is a work around, search from it. For CM7, just as simple as downloading the app
erick161 said:
For WebOS there is a work around, search from it. For CM7, just as simple as downloading the app
Click to expand...
Click to collapse
Hulu does not work in webOS.
Nburnes said:
Hulu does not work in webOS.
Click to expand...
Click to collapse
they blocked the new method too?
both WebOS and Cm7 works with Hulu....same method (mod flash and change user agent)
Nburnes said:
Hulu does not work in webOS.
Click to expand...
Click to collapse
There was a recent work around after the patch failed, never tried it, never cared enough too.
As for CM7, why flash anything? There's an app. Granted you must be a subscriber..
erick161 said:
There was a recent work around after the patch failed, never tried it, never cared enough too.
As for CM7, why flash anything? There's an app. Granted you must be a subscriber..
Click to expand...
Click to collapse
Ahh never knew there was a fix for the fix.
Edit: Mind linking?
was working till the webOS upgrade to 3.0.4
this workaround was working until the new webos 3.0.4 the new update...the patch says ” could not find area to patch (unknown file version)
claptop dot com/2011/08/make-hulu-work-on-hp-touchpad/comment-page-1
I fixed hulu with a patch for 3.0.4...
It's an alpha, it's quick and dirty, but it works. Find the patch itself here:
forums DOT precentral DOT net/3218146-post139.html
For some reason I can't upload it here (maybe not enough posts or something).
Ok, after much annoyance and a couple webOS doctors, I think I FINALLY have an all-in-one fairly idiotproof patch...
WARNING!!!!!! If you have already done this patching process manually, this patch MAY NOT WORK! You may break your flash player if you run this patch after having performed the manual work and require a visit to the webOS doctor! DO NOT RUN THIS PATCH UNLESS YOUR TOUCHPAD IS COMPLETELY BACK TO STOCK ON IT'S USER AGENT AND FLASH IDENTIFIER STRING.
Please note, this is an ALPHA patch. It will likely throw an error or two but it should work. You should be able to run this patch and it will install the hulu user agent fix AND the flash fix without requiring a reboot. Again, this is an ALPHA patch and I am not responsible if you install it and it magically borks your touchpad. This will do nothing a webOS doctor won't fix, so gauge your willingness to test this patch on whether or not you'd be ok running a doctor if things go wrong.
To install:
Step one: Download the file attached to THIS post and EXTRACT (unzip) it to an easy to find spot (like your desktop).
Step two: "send" this file (tools > send file) using webosquickinstall to /media/internal
OR: put the touchpad into USB mode and drag/drop this EXTRACTED file to your touchpad (that will automatically put it in the /media/internal directory)
Step three: open a linux command line (tools > linux commandline) in webosquickinstall
OR: open a terminal window on the touchpad itself in xterm (you will need to install xecutah, xserver, and xterm from preware to do this).
Step four: type this exactly into the terminal window:
/media/internal/hulu
The device will very likely pop an error or two (again this is an ALPHA patch), but it should finish up without any real trouble in under 30 seconds. There is NO reboot required.
TADA, HULU works once more! Your app catalog is now broken.
If it's still not working (black screen on videos) you need to remove any adblocking patches you have (adblock or max blocker), delete cache/history/cookies in the browser, and reboot the touchpad. Now Hulu will work.
When you want to fix your app catalog so you can download new programs, go back to the linux command line again (in webosquickinstall) and type:
/media/internal/hulu uninstall.
This will break hulu and fix your app catalog. It'll take 30 seconds or less to complete and you're back in business.
The patch will stay on the device, so you can easily flip back and forth from hulu installed and uninstalled.
Perhaps he doesn't want to subscribe??
There are patches and fixes etc etc for other phones, and I'm sure ultimately its all the same.. its just like the WebOS packages.. Im sure you can apply it on the touchpad, but I haven't done it or anything.. this is to allow you to watch it within a browser of course.. app is great if you pay for it..
Ya Im a poor college kid so I was really wondering what was the latest and greatest modded flash zip file. There are a few million online and I didnt want to have to flash 20 before I got one that worked. In the end I was able to find one that works like a charm so thanks guys!
Hulu!
Uninstall what ever version of adobe flash (if any). Search Vgeezyflash 74 in google, it should be the first post on a "toshiba Thrive" forum. Download the modified adobe flash 11 .apk ("apk" is file for you noobs. Install, and reboot for good luck. Then open the android stock browser (i could never get it to work right on any other), change the user agent to IE6 and delete all cookies, etc. This process worked for me on the Touchpad and on my Nook Color.
or...just go to
Code:
http://download.hulu.com/huludesktop.swf
tested...working on webos
Hulu working
Have you hit the upgrade prompt?
it seems to work better if you click ignore...but still works either way
hulu on WebOS
takes a few tries but it will go eventually - I've tried either way as well - sometimes shows crash in the middle of the episode and you have to start over - as well as restarting the instance randomly - hit Menu and select TV - starts to spool and eventually will take you to start again
Related
This is an automated nooter file to streamline the rooting process for the NookColor. This has been tested by myself and others.
Thanks To: pokey9000 for nooter, Mistar Muffin for Market and GTalk Fix, clockworx for the hacked framework.jar used to get androidID, mastapsi for testing and coding, lewellyn for coding, [mbm] for ABI Fix, Suteru for the new custom Boot Animation,Hotaru for the Gingerbread keyboard, rpollard00 for DroidX keyboard with bigger font, bpk for Soft Keys, Ben74 for NookColor Tools which enables Non Market Installs, Freenode's #nookcolor chat for dealing with my crap and checking my code.
Please Note: If I'm using your app within AutoNooter and you'd like it removed please send me a PM stating so and I will do so for future versions.
DO NOT USE THIS IF YOU ARE 1.0.0
There are a few bugs before I can release 3.x.x that need to be worked out.
This is the only officially supported AutoNooter by those working on AN
Changes:
Added: Gingerbread Keyboard.
Deleted: YouTube.apk from /system/app
Update: Busybox has whoami
Update: Installs Soft Keys 3.0.0
What it does:
Installs su and Superuser.apk
Installs Busybox
Installs Softkeys 3.0.0
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Calendar and Calculator.
Installs Android Market, Gmail, Youtube
Enable Multi-touch for Android Apps
Enables Live Wallpapers
Enables Android Market and Gmail.
App Auto Install (Open up NooterFiles from sdcard drop in /data/app)
Still Needs:
Custom Kernel to display something while working.
How to Use:
Before you begin:
* To update to 1.0.1 you must do a complete wipe.
* You must update to 1.0.1 to use AutoNooter 2.12.25 Instructions Here.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: auto-nooter-2-12-25.img.zip
2 Linux: Unzip and use dd if=auto-nooter-2-12-25.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory Reset > Wipes /data
You must do both of these to completely wipe clean your NOOKcolor.
Is it safe to try this after already having done Nooter 0.2?
The manual market install hasn't done the trick for me. Every time I have to restage the thing, if I'm not at home, I have to run out and find a wi-fi point to re-register it (argh).
I've had no ill effects from running this over an already nootered system with Market already fully functioning.
Link broken? Not finding it.
Never mind. Got it. You've got an extra j on the end BTW
I already have the market hack working but I don't have calendar and live wallpapers and some other stuff listed.
So just to be extra clear, this is save to just install over what I have already?
EDIT: WOW, this worked really WELL! I didn't mess up my already done hacks
And a little surprise in in store! It has the NEW market installed!
EDIT: Never mind, tired.
I'll be your guinea pig...will try it now.
Thanks for pointing out the extra j. Took it out.
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Wow. I've got an Android setup wizard. Should I run through it? I haven't seen this before on the NC.
"Learn how to use your LogicPD Zoom2"
Ohs you can try, but it should fail at "sign in" you want to skip it so that you can enable location.
johnopsec said:
While you're at it, you might as well include the ADHOC fix...
http://forum.xda-developers.com/showthread.php?t=872521
Click to expand...
Click to collapse
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
greenmky said:
I dunno. Some people don't tether and probably don't want to hassle switching back and forth. I think that one is kinda optional right now. Probably better off waiting for a good, permanent ad-hoc / infrastructure fix.
Click to expand...
Click to collapse
When installed, it defaults to the "stock" Infrastructure (AP) only wpa_supplicant that shipped with the NC. This simply gives them the option off switching to ADHOC mode if they need it.
I've been watching the progress on adhoc and it's currently unstable. As soon as there's a more stable adhoc solution it will most definitely be put in a future version.
Same server error as before for the Market.
"! Attention"
A server error has occurred. Retry, or cancel and return to the previous screen.
Anything else I should do?
This is the same thing that occurred with the manual Market enable process.
I'm convinced there's still something wrong with this whole process for some of us. I know there's 3-4 people getting the same server error as me for the market.
Should I try the manual editing of the packages.xml file?
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
There's been some suggestion that the androidID may not have been properly create, this may of happened if you messed with the db that holds it.
GabrialDestruir said:
You can always try to do a factory fallback then rerun autonooter or go look in freenode.net's #nookcolor, others have confirmed that Market works with this so there may be another issue someone in there can help you figure out.
Click to expand...
Click to collapse
Yeah, there's a problem with the process still somehow. This is the same results as the manual process.
This is much easier though and faster to redo. Maybe they'll find the bug in the process for those of us that it doesn't work for.
EDIT: Just a note. The Auto-Nooter didn't change my packages.xml file to remove these lines:
<sigs count="n">
<cert index="n" />
</sigs>
Not sure if it was supposed to...but it's in the manual install instructions.
Well if you can come into the irc chat maybe someone there can help you figure out the issue and we can see about adding the fix the next version.
Thanks to auto-nooter I was able to get farther than I did before with nooter .2 version. However, I've got a new problem.
After rebooting the NookColor, it started the Android tutorial. Then, when I tried to set up my Google account, I couldn't click on the "Enter Account" option since I already have a Google account. When I tried the enter account in the future option, Android seemed to immediately crash on me and the NookColor went to the normal B/N interface.
I power cycled the NookColor. However, now it immediately goes into the B/N interface, and I never see Android.
Any ideas?
Robert
Well you were suppose to skip the entering info so that it'd ask you if you want to enable location. I'm not sure if it's possible or not to get SetupWizard running again. I don't know anyone that's tried either.
Awesome! Market finally works. Thanks a lot for this! It didn't even break my previous mods.
here's asus's version of the browser apk.
you get the thumbscrolling and working labs.
you lose being able to back page from a flash site (takes about 4-6 quick backs to go back) and you lose some ua strings. only tablet, desktop and mobile-phone are available, so since you can't pick ipad some html5 sites won't stream right since they haven't added android tablet recognition.
back up your browser and browser.odex files.
would it be possible to come up with our own custom browser when source is released?
why dont you just use the one from your tablet?
G1_enthusiast said:
why dont you just use the one from your tablet?
Click to expand...
Click to collapse
missing labs option so no quick controls for those who may want it and missing thumb scroll bar.
No offense but you might wanna return your tablet then.. Which version do you have and why would you wanna lose those features??? Just saying..
Those are very nice features but not worth keeping a transformer or xoom over the tab 10.1.
I'm wondering though now that I'm rooted if I can just use this to replace the stock browser completely.
Woohooooo. Replaced the stock browser that came with it and installed this one into the system/app folder. Working great... man I missed my thumb controls. Moreso because of the fullscreen mode...I hated how the address bar took up so much real estate.
Nice!!! Congrats!! I'm glad it all worked out..
jaybizza said:
No offense but you might wanna return your tablet then.. Which version do you have and why would you wanna lose those features??? Just saying..
Click to expand...
Click to collapse
never said what features i want or don't want. what this is is an option for those who might want... options maybe.
What is the best way to go about installing this ?
@madsquabbles: If you have enough patience to read and write Dalvik bytecode, you can make your own mods to the Honeycomb browser today. I modded my Galaxy Tab 10.1's browser to use Duck Duck Go instead of Google as default search, and it works fine. (For the patch and helper scripts, see github/Sakurina/mitsuki. I'd link, but not enough posts for that yet.)
@xManMythLegend: Back up the browser, uninstall the browser using the commands from CyanogenMod's wiki (the "Make a barebones system" page linked on the front page), and then installing the apk should work via adb. If you don't uninstall the browser beforehand, you'll run into an inconsistent certificates error message.
The downside is that using a custom browser breaks delta updates such as the 3.1 update; it tries to modify the browser, can't find it, and bails out.
Thanks. Without root wasn't sure ...it'd been awhile
Sakurina said:
@madsquabbles: If you have enough patience to read and write Dalvik bytecode, you can make your own mods to the Honeycomb browser today. I modded my Galaxy Tab 10.1's browser to use Duck Duck Go instead of Google as default search, and it works fine. (For the patch and helper scripts, see github/Sakurina/mitsuki. I'd link, but not enough posts for that yet.)
Click to expand...
Click to collapse
being that i want to make sure i stay rooted i'll only upgrade via custom roms or after root is found.
but thanks for the tip. i'd have quite a bit of learning to do in order to start playing with the code. maybe i'll dig around for the heck of it and see what samsung did to fix the back page button for flash sites.
i've got the xoom apk and gonna try that tonight and see what it offers.
madsquabbles said:
i've got the xoom apk and gonna try that tonight and see what it offers.
Click to expand...
Click to collapse
Please report back. Want to have best browsing option, this one seems to be 3 steps forward one step back.
Sakurina said:
@madsquabbles: If you have enough patience to read and write Dalvik bytecode, you can make your own mods to the Honeycomb browser today. I modded my Galaxy Tab 10.1's browser to use Duck Duck Go instead of Google as default search, and it works fine. (For the patch and helper scripts, see github/Sakurina/mitsuki. I'd link, but not enough posts for that yet.)
@xManMythLegend: Back up the browser, uninstall the browser using the commands from CyanogenMod's wiki (the "Make a barebones system" page linked on the front page), and then installing the apk should work via adb. If you don't uninstall the browser beforehand, you'll run into an inconsistent certificates error message.
The downside is that using a custom browser breaks delta updates such as the 3.1 update; it tries to modify the browser, can't find it, and bails out.
Click to expand...
Click to collapse
Cant install this. Tried adb and terminal both telling me read only.
ADB finds device adb shell doesnt respond to remount
terminal just says read only file when i try to remove.+
Rooted earlier today , updated sdk. Any thoughts ?
i believe you have to type "adb remount" first then you can write to the system.
i use root explorer b/c is easier for and i don't have to use a pc.
here's the link for the xoom browser. i didn't get a chance to try it out yesterday.
http://forum.xda-developers.com/showpost.php?p=14691456&postcount=4
madsquabbles said:
i believe you have to type "adb remount" first then you can write to the system.
i use root explorer b/c is easier for and i don't have to use a pc.
here's the link for the xoom browser. i didn't get a chance to try it out yesterday.
http://forum.xda-developers.com/showpost.php?p=14691456&postcount=4
Click to expand...
Click to collapse
I have not tried adb for quite some time so perhaps there is a problem with commands or the order I am trying. It always finds the device. Adb shell starts fine but fails on remount.
Root explorer also gave me read only but I was trying to replace the apk as I failed to uninstall per cyanogen wiki.
you have to click the r/o r/w button at the top in root expl (if this doesn't work then you're either not rooted, haven't installed su, or haven't given root expl su permissions). then rename your browser.apk to browser.apk.bak (or whatever) and same with the browser.odex. it's probably safer to back them up to you pc too.
then copy over the other browser.apk and fix the permissions.. forgot what it is, but it has to be the same as all the other apks 644 i think. reboot and launch the browser.
madsquabbles said:
you have to click the r/o r/w button at the top in root expl (if this doesn't work then you're either not rooted, haven't installed su, or haven't given root expl su permissions). then rename your browser.apk to browser.apk.bak (or whatever) and same with the browser.odex. it's probably safer to back them up to you pc too.
then copy over the other browser.apk and fix the permissions.. forgot what it is, but it has to be the same as all the other apks 644 i think. reboot and launch the browser.
Click to expand...
Click to collapse
Thank you. Got it working with root explorer.
Had to look up what 644 was.
http://www.droidforums.net/forum/at...-new-cyanogen-jrummy-ultimate-permissions.png
That pic helped.
First, props to TeamWin, joel.bourquard, theintelligent, and maybe a few others I'm not aware of...
Second, these are Windows instructions. If you have another OS, you can open the batch files and type the commands inside (or paste them) one by one.
Third, keep in mind that the current temp root is NOT a full root even WHEN it is in place... so don't expect too much! This method has also been modified (by others) so that it does not "randomly" reset and it sticks until the next restart. As a result of how that works, however, even fewer apps recognize root with this method but some do!
Most of this is just other people's work: stuff from several different posts repackaged in a way that I found very easy to use. So I don't take credit for most of the contents, although I did modify the batch files to take care of a timing issue that was causing a fail on most machines. In the end, you should be able to use the attached prepare.bat file to prepare your phone once and then you can use root.bat after each reboot to restore temp root. Create a shortcut to root.bat on your desktop and you can just plug your phone in, click the icon, and you're (re)rooted in about 8 seconds.
The instructions are simple but I elaborate below to try to hit all the stumbling blocks. Basically you just run prepare.bat the first time you do this and from that point forward, you only need to run root.bat after every restart.
Here are the specific instructions:
THE FIRST TIME ONLY:
(1) Unzip contents of the attached ZIP to a folder you'll remember on your hard drive.
(2) Plug your phone in via USB and set it to "charge only" with "USB debugging" under "Settings", "Applications", "Development" turned on. It's best to do this after a fresh (full, not fast) boot. Your phone should be in this mode each time you connect it to root it. Trust me, if you've been using your phone for a while, reboot it first, then wait a few minutes for it to stabilize, THEN do this routine... saves a lot of headaches.
(3) Go to the folder where you unzipped the files in (1) and run prepare.bat. I prefer to do it in a DOS box but you should be able to just use Explorer and double click on the prepare.bat file.
(4) The first thing these batch files do is a check to make sure your computer can see the phone. If your phone isn't in the list, Ctrl-C and break out of the batch file. You'll have to correct the problem which will most likely be an issue with the HTC drivers. If your phone is not found, try these x64 drivers... or these if you're running a 32 bit OS. To install these, go to Control Panel and click on your Android device and do "Update Drivers" and browse to the location of the drivers you downloaded.
(5) Assuming your phone is on the list, everything should be ready to go. Press enter and the batch file will proceed and it will root your phone.
AFTER DOING THE ABOVE ONCE, AFTER EACH REBOOT:
(1) Attach phone and double click the root.bat file.
(2) Again, verify that your phone is on the list (proves your PC can see the phone). If so, press enter and the phone will be RErooted.
That's it! Works for me. Keep in mind that temp root is NOT a full root! Many apps will not run (won't see root) but that's just the nature of the current temp root. But some apps do work. Barnacle WiFi does for example: although sometimes it take two "start" presses to get it to connect as the first one sometimes produces errors. People say Titanium Backup and some other apps work: I haven't personally tested them. As temp root is really for dev and testing, test what you want and see if it works.
Hope this helps some of us to get a quick and easy temp root. If any issues are found, I'd be glad to modify this initial post and/or modify the batch files if any errors are found.
Mike
I can't get to the site to download the 64-bit drivers for windows. Anybody has an alternate links? Thanks.
Does this really work? How is this thread not blowing up??
vWvSTATICvWv said:
Does this really work? How is this thread not blowing up??
Click to expand...
Click to collapse
Really! Anyone out there? I expected to come back from lunch to find questions I needed to answer or maybe a suggested modification or two. This has been working for me for over 12 hours now. No restarts. No reverting to non-root. Barnacle Wifi Tether is still working. And the best thing is, if I have to restart the phone for some reason, I connect it to my computer, click, and 8 seconds later it is rooted again and I unplug it and go on my way.
Mike
can you run a wireless tethering app after temp root?
edit: see mikeyxda's post above this
I was hoping to be able to help some people with the Barnacle WiFi Tether app because a lot of people complain that they didn't get it to work and I suspect I got it to work with some combination of settings. Only problem is: I don't know how my Barnacle settings differ from those other people are using so I wanted to compare with others. Short on time right now but later I'll try to post my entire list of Barnacle settings. They work for me.
Edit: Oh Hell... I have a few minutes, here are my settings:
SSID: Evo 3D Tether
BSSID: <blank>
Wireless Encryption: not enabled (open)
Channel: mine is 6, probably doesn't matter
Custom Wifi Ad-hoc: none
Skip wpa_supplicant: NOT checked
Auto Associate: NOT checked
Access Control: NOT checked
New Client Actions: Notify Checked, nothing else checked
Local Mode: NOT checked
DHCP: Didn't mess with these
NAT: Didn't mess with that either
WAN: rmnet0 (whatever that means)
LAN: Blank
Mike
it seems like the link for the 32bit drivers is down also....
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
os10 said:
i ran batch files as OP directed, they run successfully, but when i go to start barnacle tether it doesn't have root. same for the "wifi tether for root" app. tried full reboots several times, no help.
Click to expand...
Click to collapse
Try making sure fast boot is turned off and then power the phone down and power it back up. Then use the root.bat to reroot. Might not work the first time.
For those having trouble with the driver links, try this link. It's kind of a convoluted mess with countdowns, etc. but seems like the files are there. I haven't verified them yet though.
Mike
Gave it a shot, doesn't quite seem to be working for me.
johnsmusicbox said:
Gave it a shot, doesn't quite seem to be working for me.
Click to expand...
Click to collapse
What is it that isn't working: the rooting process itself or Barnacle? I was hoping to give enough feedback in this thread to get things working for the people who say "it doesn't work" because I've been watching other threads and most of these methods seem to be very inconsistent, meaning, they don't work for a lot of people. My intention was to find the kinks and get it working for the vast majority. If you can give me details like what you see during the process, whether any error messages display, and so on, we might be able to get a more reliable temp root.
Mike
Titanium backup is definitely not working with this.
So what's going on with this? Anyone got it to work?
OK, let's try this. This is a "cleaned up" version of a different method posted in another thread. Comes with 2 batch files. Run root-init the first time and then root-redo each time you restart after that. Let's see if this works better.
Mike
Ok...My guess is that people are scared and don't know exactly what they're flashing. Would you mind sharing the source of your find, Mike? If this does indeed work, I can't see people not using this method. HmMm
*EDIT* I found the source is from XHAUSX
*EDIT 2* IT WORKS!!
I am by no means an expert, i just dove into this project 4 days ago, and since then, I've had to reformat my SD card about 8 times before I figured out how to get it stable. But now I have it running pretty stable, there are some issues still, but it at least runs linux pretty well. I'm mainly posting this because this would have saved me a lot of digging 4 days ago, and I figured I would help out any n00bs that just got a lapdock and just started playing with webtop.
*Disclaimer* I am not an expert, if you have a problem with any of these steps, please do not post them here, but in their respective threads. I take no credit for developing any of this, im just posting a list of steps from multiple sources. Also, if you break something, its not my fault*
The Guide
By the end of this guide, you will have a more functional linux as your webtop, with the XFCE4 interface. This uses webtop2sd, so if you break anything, you should be able to start over.
You will need a rooted Atrix, a lapdock (or other external device for using webtop on), and a microSD card, I suggest 2GB or bigger. I have a 32GB PNY class 10 card, for example.
1. Lets format/partition the SD card. Sogarth explains here how to do that. I highly suggest NOT doing this on your phone,and use a PC instead.
http://forum.xda-developers.com/showpost.php?p=15109152&postcount=5
2. Here, he explains how to install it after you partition your SD card. The app you need is in the bottom of the first post.
http://forum.xda-developers.com/showpost.php?p=15109140&postcount=4
3. Now plug it in to your lapdock, and it should boot up into the new webtop. You should see 2 icons in the middle, the awn-dock config tool, and the webtop config tool. We just need to focus on the latter one. Open that up, click on Administration on the left,and click on Install by lxterminal. Try clicking on the terminal icon on the dock, if it comes up, you are gold. If it acts funky, like your screen goes black but doesn't open the terminal, open up the webtop config tool again, and the button to install it should be lit up again. You know its installed if you click install,close out the config tool, and reopen it to see Install grayed out.
4. If all goes well, you should be at a terminal. The first thing we want to do, is fix a really annoying and OS breaking bug, regarding the tzdata package. It seems to be corrupted, so we want to make sure it doesn't get in the way of installing other packages. This issue was the bane of my existence for 3 days.
following these steps, we will fix it
http://forum.xda-developers.com/showpost.php?p=18465066&postcount=3
type this into the terminal to bring up the said file so you can edit it
Code:
sudo leafpad /var/lib/dpkg/info/tzdata.postinst
then put exit 0 on the 3rd empty line
I would reboot your phone after doing this, just for good measure
5. When you get back into the webtop, lets run the Webtop Scripts, the files and instructions are here for that. This will fix many broken dependencies. Arvati did a great job with these fixes!
http://forum.xda-developers.com/showthread.php?t=1192488
just put that file in your downloads folder, then run the commands from that first code box, and I just said yes everytime it asked you what you wanted to do. I would reboot your phone again after this.
6. Now lets start installing stuff! Lets start with synaptic, which works a lot better if you install via command line instead of the webtop config tool.
So run this from the terminal:
Code:
sudo aptitude install synaptic
7. Open up synaptic by typing 'sudo synaptic' into the terminal. Lets install XFCE4 now, just search for that there,and install the XFCE4 package, it should install all of the other required packages to run the new interface.
8. Once it is installed,we need to disable the webtop interface,and enable xfce4. I referenced this thread to do that:
http://forum.xda-developers.com/showthread.php?t=1054213
Type this into the terminal to edit the right file
Code:
sudo leafpad /osh/usr/local/bin/start-oshwt-2.sh
put a # in front of
sfalv -i "awm-autostart"
sfalv -i "webtop-wallpaper"
so it looks like
#sfalv -i "awm-autostart"
#sfalv -i "webtop-wallpaper"
then add these 2 lines
sfalv -i "xfce4-session"
sfalv -i "xfce4-panel"
save it then reboot your phone. Hopefully you should be in XFCE4 now!
OPTIONAL:
*To fix an issue with mounting USB storage devices:
I had the same problem, got it to work by adding this to /etc/PolicyKit/PolicyKit.conf
Code:
<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<match user="myaccountnamehere">
<return result="yes"/>
</match>
</match>
</config>
Click to expand...
Click to collapse
http://www.linuxquestions.org/quest...b-storages-debian-squeeze-723251/#post3537149
* To Fix mounting Windows network shares
Chimpdaddy has posted a way to get Samba file shares to work, this requires having a custom kernel though:
http://forum.xda-developers.com/showpost.php?p=22018703&postcount=67
Chimpdaddy said:
Firstly you need to have a kernal, like Faux's, that supports CIFS.
Then install Samba4, via synaptic package manager if you like.
Probably an idea to reboot.
Then create a folder (using terminal) where you want yr share, 'sudo mkdir /media/SHARE' for eg..
then run this;
sudo mount -t cifs -o username=guest //YOURSHAREIP/SHARE /media/SHARE
if you get no errors yr golden
If you want it to mount on startup edit /etc/fstab to include
//YOURSHAREIP/SHARE /media/SHARE cifs username=guest,_netdev 0 0
check this with 'mount -a'
That should do you.
Click to expand...
Click to collapse
OR
You could use an app like ESFileExplorer on your phone to drag and drop files, this is what I have been using,and it works pretty well for both direct windows shares and FTP. The Mobile View is great for having a window open for secondary tasks like this.
EXPERIMENTAL:
This can be buggy,so use at your own risk!
To install chromium browser, follow these steps. This is said to have better performance than the built in firefox, but for me, it crashed a lot, I went back to firefox
http://forum.xda-developers.com/showthread.php?t=1374567
ISSUES STILL PENDING:
*currently no major issues*
LIST OF SUGGESTED APPS:
OpenOffice.org
Qalculator
XChat IRC
This looks good. I just got my lapdock on Thursday and I have been putting togther all of the Docs to get it the way I want, but this is pretty much the results I wanted. I will try your instructions and get back with you.
Thanks.
Which ROM are you running on?
stock ROM.....
Thanks for the guide.
There is one link that appears to be broken though,
On step 5, the thread goes nowhere. That's where I'm stuck right now
my bad,fixed
i actually managed to do all this on my own, but just recently came into a unexpected problem. i'm kind of a linux noob, and it seems like the file manager button on xfce4-panel doesn't lead to the stock file manager i was using before (doesn't lead to anything), does anyone have any suggestions for a good file manager to replace it with?
Thanks for the fix, I've completed all steps and it was working for about an hour. Until I installed chromium.
I have a weird problem where the lapdock doesn't detect webtop and says no hdmi input detected. Not sure if you know anything about that, but just wanted to let you guys know (might be a defect on my lapdock). I'm trying to figure out a fix for that now.
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
teeth_03 said:
I would suggest starting over if that happened,sounds like something broke
as for an XFCE4 file manager, it should install Thunar by default
Click to expand...
Click to collapse
sudo apt-get thunar fixed the problem for me, thanks though
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
toe451 said:
followed your steps and it works great ,i've been messing with this for over a week trying to get this to work ,that ztdata bug fix did the job.. THANK YOU.....
Click to expand...
Click to collapse
dont thank me, thank the guy who figured out how to fix it
webtop2sd app crashes on first run...any ideas?
Here's the answer
http://forum.xda-developers.com/showpost.php?p=19993891&postcount=671
bigworm50 said:
webtop2sd app crashes on first run...any ideas?
Click to expand...
Click to collapse
To the point of installing XFCE4, and synaptic just sits on preparing packages forever... I let it sit for 30+ minutes last night and going on almost 60 minutes currently...is something wrong or does it take that long?
you might want to cancel that, reboot your phone and try again, it should not take that long
can you do one on how to install Chrome instead of Firefox for a noob like myself. Thank you.
there is already a link to the chromium browser thread in the OT
I would caution that its kind of experimental, I installed it and it kept on crashing for me, so when I re-did my webtop after that,I just decided to use firefox
For step 1, can we partition this as ext4 as faux kernels support it?
added info on fixing an issue with mounting USB drives, and a note about chrome
Crobat's Guide to Preware, Alpha/Beta Feeds and Kernels!
Why hello there! I felt that its time for me to give back to this wonderful community, but I can't code for sh*t, so I'm sorry, I can't make a rom or app for you guys. Instead, I present to you this tutorial! This is a simple, easy to follow tutorial on using Preware and other goodies for your TouchPad running WebOS.
This is a work in progress! So expect more soon.
Stuff to add:
-Alpha/Beta feeds for preware
-Kernels and Overclocking
-Pictures
-FAQ
-Links and Credits
So, first and foremost...
What the heck is Preware?!
preware.org said:
Preware is a homebrew package management application for your HP webOS device.
Click to expand...
Click to collapse
To put it simply, Preware allows you to install several useful homebrew packages for your TouchPad, which includes apps, patches, kernels and so on. For those who've done jailbreaking for an iOS device before, think Preware as Cydia, but for WebOS.
How do I get Preware?
All right, it might get a little tricky for some, but follow closely and it will be a breeze.
First, you're going to want to get your TouchPad into Developer Mode. To do this, get to Just Type and key in either of the following: "upupdowndownleftrightleftrightbastart" OR "webos20090606" (without the quotes) and you will see the option to launch Developer Mode. If you're asked for a password, LEAVE IT BLANK! I can't stress this enough. Should you enter a password, the tab will go crazy and you will have to reset it using WebOS Doctor. So don't. Once you're in, turn Developer Mode On.
Next you will want to download WebOS Quick Install. Its a .jar program that can install various items for your TouchPad.
Download it here (Credits to Jason Robitalle from WebOS nation)
Now, I'm assuming that you have Java and the Novacom drivers installed on your computer. You are going to need them to run Quick Install. To get Novacom, just get your device into HP recovery mode and link it up to your computer. It should immediately begin installing.
Next, let your TouchPad boot normally, and then connect it to your PC, but do not let it connect as a USB Drive! Just press close when the prompt pops up on the TouchPad. Now run Quick Install on the computer.
Once you're in Quick Install, click on the globe icon on the left. A window will pop up with various items available for download. On the search bar, type in 'Preware' and click 'Install'.
This is the last step! Now, on your TouchPad, open up the App Menu and look for Preware in the downloads tab. If its there, congratulations! You've successfully installed Preware for your TouchPad. Now you can download and install whatever goodies you want to make it beautiful.
Installing stuff using Preware
Installing things from Preware is a simple affair. After launching the app, you can either use the search feature if you know the name of the app or whatever you're looking for. If not, go to 'Available Packages' and you will be able to browse for whatever you want from a list.
What are Alpha & Beta Feeds?
All the homebrew packages that appear on Preware are there because of feeds. Feeds are, in a way, carrying the information of the packages. Preware is basically the 'centre' where all the packages from the various feeds are displayed. Therefore, without feeds, Preware will show nothing at all. Try and think of eBay. The website represents Preware, whereas the sellers represent the feeds.
So, as the name implies, Alpha and Beta feeds are feeds that contain packages that are still in early development and are for testing. Hence, they are collectively called testing feeds. Alpha packages are highly unstable and could potentially damage your device. Beta packages are more stable, almost ready for use, but with some problems here and there. However, this does not mean that Beta packages are 100% safe to install, so do so at your own risk.
How do I enable/disable Alpha & Beta Feeds?
Due to restrictions I'm not allowed to post instructions here. All the instructions you need can be found here.
Please read their rules carefully before doing anything.
One more thing. Some of the steps require you to access the Linux command line. To do so, simply launch WebOS Quick Install, go to Tools, then Linux Commandline.
To choose which feeds you want to access in Preware, go to Preware>Manage Feeds. From there, you can turn the feeds on/off.
One Last Thing...
I've tried my best to read all the forum rules and searched for other threads to ensure that I'm not posting something that's been done to death. But if I really missed a thread with the exact same topic, then, well, darn! Please get the mods to close this thread.
crobat said:
To do this, get to Just Type and key in the following: "upupdowndownleftrightleftrightbastart"
Click to expand...
Click to collapse
You can use webos20090606 instead, it's considerably shorter.