Related
Do not use the lagfix anymore voodoo will be incorporated into our new kernels very soon. Thanks
Kept the attachments so you can remove if needed!
I keep getting permission errors when I try this. I found another way to update busybox but the script doesn't work
With the current limited root I have, I could not write to /system/bin. I just woke up and I didn't feel like figuring that out, so I copied stuff to the sdcard, then I used cat to write the file to /system/bin as shown above (steps below). I would suggest before starting, download Quadrant Standard from the Market, run the full benchmark and see where your device is on the list. Mine was below the Galaxy S before starting.
This is what I did (on Mac) to get busybox in place:
Code:
./adb shell
su
mkdir /sdcard/lag_fix/
exit
exit
./adb push ~/Downloads/busybox /sdcard/lag_fix/
./adb shell
su
cat /sdcard/lag_fix/busybox > /system/bin/busybox
cd /system/bin/
chmod 755 busybox
ls -l (check the permissions)
exit
exit
Now busybox is in it's right place with the right permissions.
Now, I have to manually execute the steps in the lagfixme.bat file, because I'm not on a PC and I don't feel like re-writing the script, because I just woke up.
Before pushing the files, I edited lines 35 and 36 in the createlagfix.txt file to fit my sdcard folder path. I like to keep my SD card organized, so I put all the files from the zip into the /sdcard/lag_fix folder I created above. Here is what my line 35 and 36 look like before I push createlagfix.txt to the SD card:
busybox cp /sdcard/lag_fix/playlogos1 /system/bin/playlogos1
busybox cp /sdcard/lag_fix/userinit.sh /system/bin/userinit.sh
Now, I know the folder paths below looks ugly, but that's because I just pushed the files directly from my Downloads folder. Hopefully you guys can see what I did here. If not, let me know and I'll edit the post to read better. These are basically the lines in the batch file written out manually for Mac users:
Code:
./adb kill-server
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/createlagfix.txt /sdcard/lag_fix/createlagfix.sh
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/playlogos1 /sdcard/playlogos1
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/userinit.sh /sdcard/userinit.sh
./adb shell su -c "/system/bin/sh /sdcard/lag_fix/createlagfix.sh"
Once the process is complete, run Quadrant Standard again and you'll see your device as the fastest one in the list.
Many thanks to Dirrk!!
Worked just fine for me.
Thanks for this and your root instructions!
Guys, is the phone actually laggy, or are you just assuming it's laggy because of complaints with the other models? I mean, you've only had them a day or two, right? Took me longer to notice lag than that on my i9000.
I'm tempted to grab a Fascinate, but all the issues I've had with the i9000 and it's a tough call.
I've seen it lag sometimes under high load, but I thought that was normal.
I've tested it with GroceryIQ, to compare against the last 30 seconds or so of this video ( http://www.youtube.com/watch?v=10ox35vMS78 ) and the Fascinate is nowhere near as bad at lagging. That video was 8/21/2010, so they may have updated their application by now, not sure.
Edit - Anyway, it works just fine. Nice work Dirrk! 2,191 !
Yep, worked like a charm! My Quadrant score jumped to 2125 after the fix. Phone is much snappier too. Thanks Dirrk!
i've been trying this but i keep getting permission denied.
can someone take me step by step on how to do this?
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
spotmark said:
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
Click to expand...
Click to collapse
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
m2cool2go said:
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
Click to expand...
Click to collapse
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
C:\sdk\tools>adb shell
$ su
su
# cat /sdcard/busybox > /system/xbin/busybox
cat /sdcard/busybox > /system/xbin/busybox
cannot create /system/xbin/busybox: read-only file system
Any ideas why I'm getting this error? It looks like I'm screwing up something very simple...
namebrandon said:
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
Click to expand...
Click to collapse
Really? I removed Backup Assistant and I'm not bricked. Am I missing something?
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
undo lagfix
Hello. I want to undo this for now, due to running out of space for apps. I assumed running unlagfixme would do the trick, but it hasn't given me back the 1 gb it used. Am I doing it wrong, or is it stuck like this now? Thanks for your help!
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Nevermind, figured it out
xirnibor said:
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Click to expand...
Click to collapse
You screwed up if your only getting 871 thats stock. Open up a shell on your phone and type mount and place the results in here
Whitepaint said:
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
Click to expand...
Click to collapse
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
namebrandon said:
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
Click to expand...
Click to collapse
I am waiting on rom manager so I can make a back up before I continue removing stuff
OK. I told someone I would go through this and come up with a quick HOWTO to get the Droid-X multitouch keyboard installed on the NC.
I really like this keyboard. It has predictive text and it also allows me to touch type when in landscape mode.
This HOWTO assumes that you have downloaded View attachment DroidX_Keyboard.apk <- [that is a link to the APK people!] to the same directory that your adb binary (adb on linux, adb.exe on Winblowz) is located in...
DO NOT CONTINUE UNLESS:
(1) You have at a minimum enabled non-market apps on your NC!!!
(2) You are willing to suffer through a single reboot to get the new keyboard loaded.
(3) In the unlikely event that something goes wrong, you're unable to go through the "revert to original keyboard" procedure listed in this post.
Note: If your computer is infected with the Bill Gates virus (you're running Winblowz), you will run adb.exe in the current directory instead of ./adb as I have in the HOWTO. My personal system is Ubuntu 10.04 LTS with android-sdk_r07-linux_x86.tgz installed.
OK... Here we go...
(1) Verify that View attachment DroidX_Keyboard.apk is in your adb binary directory:
$ ls -al DroidX_Keyboard.apk
-rw-r--r-- 1 tvo tvo 3256280 2010-12-08 22:07 DroidX_Keyboard.apk
(2) Verify that the MD5SUM for DroidX_Keyboard.apk is as follows:
$ md5sum DroidX_Keyboard.apk
c2ae341417585a2847765d9598575b20 DroidX_Keyboard.apk
If the MD5SUM doesn't match, DO NOT CONTINUE! (If you don't know what MD5SUM is, Google it. )
(3) Connect your NC to the USB port of your computer.
(4) Verify that you're in the correct directory and that ADB can see your NC. IE; Your ADB binary is in the same directory and things are OK with communications between the computer and the NC:
./adb devices
List of devices attached
xxxxxxxxxxxxxxxx device
Note: the x's will be the actual SN of your NC.
(5) If and ONLY if all of the above has worked as expected, continue with the following:
(6) Make a local (on your computer) backup of your original NC keyboard...
./adb pull /system/app/LatinIME.apk
You should see something like the following:
1408 KB/s (198321 bytes in 0.137s)
(7) Make another local copy of the original NC keyboard:
cp LatinIME.apk LatinIME.apk.nook.original.keyboard
(8) Run the following ADB commands:
./adb shell
# mount -o remount rw /system
# cd /system/app
# mv LatinIME.apk LatinIME.apk.bak
# exit
What we just did was mount the /system partion as RW and move the original keyboard to a backup file. Notice that we have three backups now. Two on your computer and one on your NC.
(9) Install the View attachment DroidX_Keyboard.apk with the following command:
./adb install DroidX_Keyboard.apk
You should see something like the following:
1782 KB/s (3256280 bytes in 1.783s)
pkg: /data/local/tmp/DroidX_Keyboard.apk
Success
(10) Reboot your NC:
./adb reboot
(11) WHILE the NC is rebooting, disconnect the USB cord.
When the NC boots up, you will now have the DroidX multitouch keyboard instead of the stock NC keyboard.
I know... I know... I could have written a script to do all of this for you. But, if you can't follow 11 very simple steps, um... Oh, nevermind.
How to REVERT TO ORIGINAL KEYBOARD...
If something doesn't work right or if you just want to go back to your stock keyboard, run the following commands from within your adb binary directory (the directory with adb or adb.exe in it):
./adb shell
# mount -o remount rw /system
# cd /system/app
# cat LatinIME.apk.bak > LatinIME.apk
# chmod 755 LatinIME.apk
# reboot
While the NC is rebooting, remove the USB cable.
When the NC reboots, your keyboard will be restored to the stock NC keyboard.
Simple, huh?
I've gone through this multiple times now trying to find any issues. It works flawlessly for me to switch back and forth between the two keyboards.
John - Your friendly neighborhood e-thug.
Worked for me without a hitch.
Has anyone figured out how to make the letters on the keys bigger? It's not a big deal but if possible it would be a 'good thing.'
I should add: Thanks for the instructions!
Any idea how to get the font/letters on the keys to display larger?
-CC
DyDx said:
Worked for me without a hitch.
Has anyone figured out how to make the letters on the keys bigger? It's not a big deal but if possible it would be a 'good thing.'
I should add: Thanks for the instructions!
Click to expand...
Click to collapse
Glad it worked out for you. I'm looking into making the keys bigger. Will post an update if I get it figured out.
Strapping on Flame Suit.
It didn't work for me. :-(.
Just kidding. It was simple enough. It's funny, I've been playing with Android for a while but never got into using adb. Partly because I never could get the SDK installed correctly, it was always a pain to use. I don't know which instructions worked, I tried a few, but this install of the SDK is working great and I can run adb anywhere. I've learned more about Android on the NC then my last 2 Android phones. I'm McLuvin it
If I could only get Swiftkey to work. This keyboard will do me fine till Switkey works.
Thanks.
You really made that complicated sarcasm boy.
Its really easy in Root Explorer. Thanks for the apk though.
Just curious, does this have swipe functionality?
Also, I haven't installed this yet, but as some of you are asking about getting the letters bigger, are these smaller than stock NC key letters?
Yes, the letters are quite small. The buttons themselves are larger, however.
Has anyone tried the Gingerbread keyboard?
EDIT, I guess it won't work on 2.1 roms.
Anyone know a keyboard that works but doesn't have the small letter problem the DROID X keyboard has?
donballz said:
You really made that complicated sarcasm boy.
Its really easy in Root Explorer. Thanks for the apk though.
Click to expand...
Click to collapse
If you think that typing a bunch of things on the NOOK keyboard compared to copy/paste to your computer is compliacted, sure.
Glad I could help you out. As for Boy... OK. Based on your moniker, I was in combat killing enemies YOUR AGE before you left your mommy's teet. That's OK though. You can call me boy if you must.
Figured out how to increase the font size on the keyboard.
I used apktool and decoded DroidX_Keyboard.apk posted by johnopsec. I took a peek at the xml in the LatinIME.apk and found that the NC keyboard has this setting android:keyTextSize="24.0sp" in /res/layout/input.xml.
It was as simple as copying that into DroidX_Keyboard's /res/layout/input.xml and rebuilding it. Obviously if you wanted a larger or smaller font-size it would be fairly easy to adjust. Anyway, I'm not much of a hacker but I figured I would share.
I also went ahead and removed the voice search buttons as they serve no purpose with our lack of a microphone.
I attached a screenshot as well as my apk, which installs(at least for me) just fine using johnopsec's method.
I take no responsibility if your NC explodes or bricks or turns into a unicorn.
rpollard00 said:
Figured out how to increase the font size on the keyboard.
Click to expand...
Click to collapse
Great work. Looks great on my NC. Thanks for your work!
Works great, thanks. One minor issue I'm having (using rpollard00's apk) is that in landscape, if I bring up the numeric keyboard, the "&" key shows as "&". Is this just me, or can you guys see it too?
ddenson said:
Works great, thanks. One minor issue I'm having (using rpollard00's apk) is that in landscape, if I bring up the numeric keyboard, the "&" key shows as "&". Is this just me, or can you guys see it too?
Click to expand...
Click to collapse
I see the same thing here. And it is very bold text. I'd actually like to see all of the letters this bold on the keyboards. Hey rpollard00, any chance of an updated APK?
Glad someone found a fix for the font size.
Now the next thing I'd like to see is someone getting the new SwiftKey 'HD' to work. It has a 31 day trial on the Market for anyone who wants to give it a shot. I'm eager to see it work because they just changed it to work better with higher res screens like the Galaxy Tab.
However, it's a keyboard that has it's own setup utility and requires you to turn it on in "Settings," which of course is hidden on the NC. So, I was unable to get it to work using the method applied to the DroidX keyboard.
johnopsec said:
I see the same thing here. And it is very bold text. I'd actually like to see all of the letters this bold on the keyboards. Hey rpollard00, any chance of an updated APK?
Click to expand...
Click to collapse
I fixed the & issue. I played around a bit to see if I could make all of the keys bold but I couldn't get anything working. I also restored the "<" symbol(anyone notice?), which I accidentally deleted when I fixed the &'s in portrait mode. Oops!
I'll see if I can figure anything out with bolding the text after work, but no promises.
rpollard00 said:
I fixed the & issue. I played around a bit to see if I could make all of the keys bold but I couldn't get anything working. I also restored the "<" symbol(anyone notice?), which I accidentally deleted when I fixed the &'s in portrait mode. Oops!
I'll see if I can figure anything out with bolding the text after work, but no promises.
Click to expand...
Click to collapse
Works great. Thanks!
Feel free to mock me, but I'm having problems. Here's the error I get:
$ adb install DroidX_Keyboard.apk
2385 KB/s (3256280 bytes in 1.333s)
pkg: /data/local/tmp/DroidX_Keyboard.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
I'd already installed SoftKeys_2.00.apk before attempting this, which may be the source of the issue. Any idea how to get my Nook to a state where I can successfully install the Droid X keyboard?
EDIT: Got it! You need to revert to the stock keyboard before you can install a new custom one.
I used root explorer, because I don't have ADB installed at work.
I made a copy of the stock keyboard file, and pasted it to my SD card. I then renamed the stock keyboard to LatinIm.apk.bak.
I then installed the new multitouch keyboard as a regular APK, it installed, and I rebooted. Voila, everything worked well.
(I figured I'd throw this in here in case anyone was wondering how to do it with root explorer...I know adb can sometimes be a little intimidating)
Is there a way to revert to NC original keyboard if i got the droid-x's with the Auto-nooter batch installation? I dont think it made any backup copies... Now im stuck with Droid-x i dont want at all...
UPDATED 12/23
---------------------------
1) Added automatic fixing of devicemanager.apk sql databases to prevent OTA root (thanks for the SQL tweak suggestions, Indirect)
2) Added otaban.sh script for those who are already rooted and just want to tweak the sql databases (you will need to put your device back in USB debug mode)
3) Added getroot.sh to just dump the nook back in to rooted/adb mode
INSTRUCTIONS
(Please follow these to the letter; over 500 people have downloaded this script and very few have reported issues)
On the NOOK
Disconnect from USB
Factory restore & initial setup
Browse to this:
http://goo.gl/vTNpJ
Click on notifications center, wait for the file to finish downloading.
Press on downloaded go_launcher_ex_v2.66.apk file
Select Complete action using package installer
It should say "install blocked"
Press settings
Tick unknown sources (press ok)
Pick Development
Tick USB debugging (press ok)
Tick the other USB debugging further down
Untick Automount
Back/Back
Connect the Nook to the MAC. On the nook you should see "USB debugging connected" in notifications center
On the MAC
Download the nooktablet-mac-root-0.6.zip file from http://goo.gl/qyYDB
Open Terminal, and change in to the directory where the zip file was downloaded. Unzip and cd in to the directory created. EG:
Code:
[B]cd ~/Downloads
unzip nooktablet-mac-root-0.6.zip
cd nooktablet-mac-root-0.6[/B]
Start the rooting script:
Code:
[B]./go.sh[/B]
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly. Also don't connect via a USB Hub.
When the script is finished, it should say "Done. Unplug from USB now"
The Nook will reboot.
You are now rooted and the following is auto-installed for you
1) Go Launcher Ex (Rooted App Launch/Desktop)
2) Market Place (The Android "App Store")
3) Button Savior (adds tiny button on right of screen for nagivation home/back etc)
4) Home Catcher (makes 2 clicks of the Nook N bring up the new Launcher)
5) Nook Color App Menu (allows you to install sideloaded apps to the Nook home screen/Library)
6) Dolphin HD Browser (Replacement web browser)
In addition, some tweaks have been made to prevent OTA updates from working, preserving your root state.
trying this now..
thanks a lot! i spent 2 hours last night trying to get the other method working and it gave me the headache of the gods.
edit: that mediafire link is crawling for me (dl is at like .2kb/s) can anyone mirror it for others who may have similar issues?
Worked beautifully! Where can I send a donation to?
beatlesfan01 said:
Worked beautifully! Where can I send a donation to?
Click to expand...
Click to collapse
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
i can confirm this works guys
yes.. someone please start a thread and aggregate donations for some roms on this bad boy.
t-r-i-c-k said:
Tempting and appreciated as that is, there is no neeed. Good luck,
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
You are a good man. Thanks again for all of your help and great work. You're an invaluable asset to this community.
Sent from my BNTV250 using Tapatalk
Thanks for the tutorial. It works extremely well!
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
jdubr said:
This worked great, thanks!
I had one minor glitch. I was doing this on an old MBP running Leopard and for whatever reason it wouldn't create the ~/.android directory when I ran the script.
I created the directory manually and re-ran the script and it worked perfectly! Thanks again!
Click to expand...
Click to collapse
Ah, I just looked at the script, I realized now I missed out the mkdir -p ~/.android in it, hence your issue. I will likely fix that and update the script/zip file when I get a minute.
I'm currently considering whether to make the script install busybox at the moment. I don't really need it myself, but I see other people might.
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
t-r-i-c-k said:
Part of the problem is that if I develop the script any further I ought to test it before releasing it... but I really don't want to keep re-rooting my nook. I want to actually use the damn thing!!
Click to expand...
Click to collapse
I totally get that. I had just gotten done side-loading tons of stuff and getting my launcher screens setup the way I wanted and then I saw your script and thought about it for a day before breaking down and wiping my NT and starting over.
It was worth it! Thanks again!
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Minor problems encountered
I followed the directions and it mostly worked. First, had the problem with the missing:
[ ! -d ~/.android ] && mkdir ~/.android
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail?
Click to expand...
Click to collapse
Sent from my BNTV250 using Tapatalk
lanceot said:
I'm confused... rooting on PC using other method didn't work for me and now I'm stumped on Mac as well.
This part stumped me:
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Can someone explain the steps in greater detail? I tried runing the adb fiel via terminal, it goes through the script but does nothing on installing files to the device.
Thanks.
Click to expand...
Click to collapse
Literally type
unzip nooktkablet-mac-root-0.4.zip
cd nooktablet-mac-root-0.4
mkdir -p ~/.android
./go.sh
Sent from my BNTV250 using Tapatalk
kisstek said:
Then I wasn't sure about the step where it says to click on the golauncher icon in the notifier. I clicked on the LauncherPro.apk entry and choose the package installer. That seemed to work but I'm not sure that's what you meant.
Then found out I should have unplugged the USB cable before rebooting otherwise the launcher chooser is covered by some wrning message. (I can't remember the exact wording now.)
Installed Button Savior. Not sure what that does. I can't figure out where it's suppose to be on the screen.
And worst of all, LauncherPro keeps crashing on me, dumping me back into native Nook mode. That requires a reboot.
But despite all that, I'm happy and will now probably keep my NT.
Big thanks!!
Mike
Click to expand...
Click to collapse
Launcher: that's what I meant.
Unplug: if you dont before you reboot it probably wants to media sync
Button savior: installs a tiny button on the right of the screen. Gets you back/home
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Sent from my BNTV250 using Tapatalk
Thanks. I found the little tiny button savior icon while trying out an ssh client. It shows up well on a black background.
And that does make it real easy to get back and forth between Android and Nook. Thanks again for making this easy and the button savior recommendation.
I may have to break down and try the Amazon store now.
t-r-i-c-k said:
Connect the Nook to the MAC. On the nook you should see "USB debugging enabled" in notifications center
On the MAC
Download the nooktablet-mac-root-0.4.zip file
unzip it
cd in to nooktablet-mac-root-0.4 directory
mkdir -p ~/.android
./go.sh
Sometimes adb doesn't wake up immediately. Just try go.sh again if it says it can't find your Nook and you are sure it's in debug mode and plugged in properly.
On the NOOK
Click on Notification center again, and press on the Golancher Icon again. Install the Goauncher
Reboot
After reboot, slide to unlock and it should ask "complete action using..". Pick LauncherPRO
Open Marketplace which should be on the launcher screen
Sign in with your google credentials, attach the device to your account
Install button savior from the Marketplace.
Browse to amazon.com/app-email
Click notifications and watch for Amazon appstore apk download
Click and install.
You should now be live with Android Market & Amazon Market.
Click to expand...
Click to collapse
Hey! Noob here. Thanks so much for this! Just have a few questions...is this a permanent fix? I currently have the amazon appstore, but not android, so is this going to be set up the same way (i.e. have to click search and then go launcher to find the apps)?
When I connect to my mac, the usb debugging prompt will come up right away (like the screen for file xfer normally does)?
After unzipping, are those instructions to enter into the mac's terminal command prompt? Sorry, that's where u lost me! Is "cd" short for something? Thanks again for your help. Just want to make sure I do this right the first time. I think swype is the first thing I will install. Hating this keyboard!!!
First, I want to openly thank t-r-i-c-k for this. Even with little to no knowledge of this kind of stuff, after futzing with terminal for a while I got it to work in two tries. Finally, freedom from another lock-in service/device. But I am having a little glitch that I don't understand.
It's intermittent, but now and then I'm getting a crash on the launcher. It happens when trying to adjust settings/preferences. No big deal as it comes right back, and maybe its the app itself. Anyone else facing this?
t-r-i-c-k said:
LAUNCHER: certain things crash for me. Cant change dock shortcuts for example
I'm sure this will all get smoother in time. Pretty good already though.
Click to expand...
Click to collapse
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
jdubr said:
I installed the ADW Launcher because LauncherPro wouldn't let me change the dock shortcuts. ADW is letting me modify just about everything--dock shortcuts, icons, etc., without issue.
I get an occasional crash but not as many as before.
Click to expand...
Click to collapse
ADW seemed slow to me. I just switched to Launcher Ex anf thsts is working nicely. No crashes yes.
Sent from my BNTV250 using Tapatalk
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
Hiya people..
So I was on the first Beta by Team DRH ICS but decided to go back to Beastys.
I went to CWM, wiped everything, installed the beastys.zip and rebooted the G-Tab.
But now when I turn the G-Tab on the screen is just black after the "Notion Ink" bootanimation..
I've tried NVFlashing 4349 Rev4 with the CWM Touch 5504 B14.
Tried with Calkulin+ClemsysFroyo and Beastys+ClemsysFroyo, also tried with and without the SOD Fix for Froyo ROMs.
If I just let the G-Tab boot after the NVFlash it works, it boots up to the TnT ROM.
I've also tried unplugging the battery for 15 sec or so, and pressing the internal reset button.. Still no luck =/
Anyone at all got any clue on how to fix this? =/
ZoZo- said:
Anyone at all got any clue on how to fix this? =/
Click to expand...
Click to collapse
Do these two things:
1. Boot into CWM, run this ADB command and post the output.
Code:
C:\SOME\PATH> [B]adb shell fdisk -l /dev/block/mmcblk3[/B]
2. After installing the ROM of choice in CWM, and before rebooting into the ROM for the very first time:
- power off the gTab
- connect the USB cable to PC.
- run this ADB command on the PC (and keep it running until you encounter the black screen):
Code:
C:\SOME\PATH> [B]adb logcat -v time > logcat.txt[/B]
- now power on the gTab.
This sequence will ensure that all the logs are collected, and right from the start. Kill the log collection after some time and post that output here too.
Ehum... Could the adb shell fdisk -l command have done anything?
Because after another NVFlash 4349 > NVFlash CWM Touch > Flash Beastys... It magically works!
I couldn't initiate any logcat, only get "waiting for device"
ZoZo- said:
Ehum... Could the adb shell fdisk -l command have done anything?
Click to expand...
Click to collapse
If you ran the fdisk while in CWM, then no--the fdisk was just a diagnostic command.
I couldn't initiate any logcat, only get "waiting for device"
Click to expand...
Click to collapse
That is how it should be. ADB will wait until the device is booted up and the ADB server on the device runs.
Different tablet, same problem
This is same topic, but a different tablet.
A friend on mine purchased Xtex MyTablet 7" (ICS); after about a week, the tablet boots into a "blank" screen, after running two bootanimations.
I ran "adb logcat" and can see the system processes running, but screen stays blank, making the tablet unusable.
I ran "adb logcat -v time > logcat.txt" and here is the file:
https://dl.dropbox.com/u/18476770/Android/logcat.txt
This tablet being fairly new, I could not find any support forums for it; I opened a ticket with the supplier, but they are very slow responding.
I turn to XDA, knowing the knowledgeable and helpful people here will shine some light my way.
Thank you in advance
./B
kozmo2k4 said:
This is same topic, but a different tablet.
A friend on mine purchased Xtex MyTablet 7" (ICS); after about a week, the tablet boots into a "blank" screen, after running two bootanimations.
Click to expand...
Click to collapse
Since I don't have that tablet, it's difficult to do comparisons to determine deviant behavior. So, what follows are just guesses:
1. There is this error message in that log which might be relevant (or it might not--I've no idea):
Code:
06-12 21:12:30.659 E/SurfaceFlinger( 85): couldn't find an EGLConfig matching the screen format
06-12 21:12:30.729 E/DisplayDispatcher( 85): Open Display Device Failed!
06-12 21:12:56.849 E/DisplayManagerService( 149): Open Display Device Failed!
2. I noticed that some 3rd party live wallpapers were being loaded. Did the problem start after the live wallpapers were installed? Maybe that's causing problems.
Given that you are able to see 2 (?!!!) boot animations before the display goes blank, I would have to guess that its no. 2 (heh!) that's causing problems. Uninstall all the live screensaver packages using ADB. Use this as a guide.
As a last resort, you could try going into CWM (if it's installed) and do a "wipe data/factory reset", then re-install the ROM. You will lose all data with this.
Thank you for the fast reply, rajeevvp.
I'm sorry I said it wrong earlier, there is only one boot animation, the "old school" letters: ANDROID, with a light beam running across them. There are two "boot logos" that flash on the screen prior to that. My PC, right now logged in on Win7x64, recognizes the tablet connected (USB device connected jingle) at the Android bootani.
I'm going to try to adb uninstall some of the apps and we'll see what happens.
Thanks for the insight.
./B
[EDIT]: Unfortunately, no CWM installed. I can't even figure out any kind of recovery on this. Only physical buttons are: Power, Menu and Escape. I tried all combinations, but it just boots up.
---------- Post added at 05:23 PM ---------- Previous post was at 04:50 PM ----------
Follow up:
ADB has root access, I can browse all directories (i.e. /data/data)
adb uninstall, all I get is "Failure"
In adb shell, after remount rw, command: rm -f /data/app/.apk
says "No such file or directory"
I know I typed the package name (com.cellfish.livewallpaper.marvel_avengers-1.apk) correctly. Hmmm
./B
kozmo2k4 said:
Follow up:
ADB has root access, I can browse all directories (i.e. /data/data)
adb uninstall, all I get is "Failure"
Click to expand...
Click to collapse
What is the exact command you used? As the document says, if you are using ADB, you should do:
Code:
C:\SOME\PATH> [B]adb uninstall [I]packagename[/I][/B]
Unfortunately, no CWM installed. I can't even figure out any kind of recovery on this.
Click to expand...
Click to collapse
If you can figure out how to get into stock recovery (it would be very unusual to not have one--its needed for ROM upgrades for instance), then you could try this:
Clear Cache and Data from Stock Recovery
Thank you for the reply.
Here is what I've tried:
Code:
adb uninstall com.cellfish.livewallpaper.marvel_avengers-1.apk
then the app full name I found in Play Store
Code:
adb uninstall The Avengers Live Wallpaper
Al I get is "Failure"
Next I tried
Code:
adb shell
[email protected] # mount -o rw,remount /data
[email protected] # rm -f /data/app/com.cellfish.livewallpaper.marvel_avengers-1.apk
The I get:
rm failed for -f, No such file or directory
I was not able to figure out how to get to recovery of any sorts; like I mentioned, only 3 physical buttons, Power, Menu and Esc. Tablet has microSD slot, Mini HDMI, 3.5mm headphone, Mini-B USB and full USB ports. That's all. I'm getting close to opening the case to see if there is a reset button, but waiting for my colleague's pernission (she'll most likely just send it back).
Update:
I was able to remove the live wallpaper in adb (just omitted the -f after rm), but no cookie....black screen after boot.
Is there a way to wipe-factory reset with adb? Just delete the contents of /data/app directory? .... Only one way to find out...
---------- Post added at 06:22 PM ---------- Previous post was at 05:59 PM ----------
Update II:
Code:
adb shell wipe data
did the trick, tablet booted up just fine (except for the Chinese language...lol).
Thank you again for all your help!
Linux ROCKS
./B
Follow up post
Just a follow up:
A couple of days later, my colleague had brought the tablet back with black screen again.
After a little "interrogation", I found out that she actually hit the brightness button on the Power Widget a couple of times and that had dimmed the background light to ZERO.
Having more information than before, I've came across two possible solutions:
1. Use LED flashlight and shine it on the screen at a certain angle and try to make out the icons on the (LCD) screen and re-adjust the brightness...
2. Use Droid Explorer with the "Screen Cast" java applet to mirror the screen on a PC and try to adjust the brightness that way.
3. Try to reset the brightness sqlite database (way out of my league; I'm a "hardware guy", not a programmer...)
Well, number 2 was the winner!
So, for future reference, if anyone get "black screen only" and have ADB set up on your PC, use the Droid Explorer (http://de.codeplex.com/) with Screen Cast plugin to access you Android device.
I hope this will help someone....
kozmo2k4 said:
Code:
adb uninstall com.cellfish.livewallpaper.marvel_avengers-1.apk
Click to expand...
Click to collapse
You have to use the package name and not the apk name to adb uninstall. Look inside the /data/system/packages.list file to determine this.
Update II:
Code:
adb shell wipe data
did the trick, tablet booted up just fine (except for the Chinese language...lol).
Click to expand...
Click to collapse
A bit drastic, but, that works . But, I wouldn't have recommended wiping the /data partition like that while inside the ROM. This is why a recovery mode exists.
I wouldn't be surprised if after a wipe like that and a subsequent filesystem check, the /data/lost+found directory contained more than a few files/dirs.
---------- Post added at 11:16 PM ---------- Previous post was at 11:13 PM ----------
kozmo2k4 said:
Just a follow up:
A couple of days later, my colleague had brought the tablet back with black screen again.
After a little "interrogation", I found out that she actually hit the brightness button on the Power Widget a couple of times and that had dimmed the background light to ZERO.
Having more information than before, I've came across two possible solutions:
1. Use LED flashlight and shine it on the screen at a certain angle and try to make out the icons on the (LCD) screen and re-adjust the brightness...
2. Use Droid Explorer with the "Screen Cast" java applet to mirror the screen on a PC and try to adjust the brightness that way.
3. Try to reset the brightness sqlite database (way out of my league; I'm a "hardware guy", not a programmer...)
Well, number 2 was the winner!
So, for future reference, if anyone get "black screen only" and have ADB set up on your PC, use the Droid Explorer (http://de.codeplex.com/) with Screen Cast plugin to access you Android device.
I hope this will help someone....
Click to expand...
Click to collapse
+1 kozmo2k4. We need more smart users like you on the board.
Thank you for the kind words, rejeevvp. I love to "tinker" with things and do not give up that easily.
I know the "adb shell wipe data" was an overkill, like chasing a fly with a .50cal, but at that point in time it was the most feasible.
I've tried all possible button combinations to get into recovery, but everything led to regular boot.
After the successful booting into the ROM, I did notice an option under settings>development to boot Recovery. Which I did, and was presented with a basic "blue" Android System Recovery .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I did another Wipe Data and wipe Cache and rebooted.
Everything seemed to be working fine afterwards, and my colleague texted me that the tablet is running faster and smoother than when she first got it, so everything is all good.
[Edit] Funny thing I just noticed, in the picture it says to use (Q7, volume up/volume down, Home, Enter), however, there were no "hard" buttons labeled that, only: Power, Menu and Escape!
Here is the front:
Sent from my NookColor CM9 using Tapatalk 2
kozmo2k4 said:
After the successful booting into the ROM, I did notice an option under settings>development to boot Recovery. Which I did, and was presented with a basic "blue" Android System Recovery .I did another Wipe Data and wipe Cache and rebooted.
Click to expand...
Click to collapse
+1 again. That is the right thing to do.
[Edit] Funny thing I just noticed, in the picture it says to use (Q7, volume up/volume down, Home, Enter), however, there were no "hard" buttons labeled that, only: Power, Menu and Escape!
Click to expand...
Click to collapse
Tried the soft buttons? ...but, yeah, that's Android for you--basically not a lot of QA going on anywhere. Even the top guns like Asus seem to be asleep at the switch.
BTW, I think I've found where the screen brightness level is stored--at least for Gingerbread. Care to run a few test commands with that tablet?
Reset Brightness
rajeevvp said:
+1 again. That is the right thing to do.
Tried the soft buttons? ...but, yeah, that's Android for you--basically not a lot of QA going on anywhere. Even the top guns like Asus seem to be asleep at the switch.
BTW, I think I've found where the screen brightness level is stored--at least for Gingerbread. Care to run a few test commands with that tablet?
Click to expand...
Click to collapse
Soft buttons work while in ICS; when tablet was off, only "hard buttons" were available.
I would be more than happy to run few tests, but I returned that table on Sunday (have the feeling that wasn't the last time I saw it, though).
During my "research", I came across these possible locations of brightness setting on ICS:
/sys/class/backlight/rk28_bl/brightness
or
/sys/class/leds/lcd_backlight/als
(however, I don't see "rk28_bl" or "lcd_backlight" on my gTablet ICS 4.0.4, or my SPH-D710 2.3.6 under /sys/class; I have "/sys/class/pwm-backlight/" tree on both devices:
There was also a script to reset brightness to 100% in sqlite database
Code:
#sqlite3 /data/data/com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
#reboot
But I did not get to try any of that, since I got lucky with Android Commander and ScreenCast.
kozmo2k4 said:
During my "research", I came across these possible locations of brightness setting on ICS:
/sys/class/backlight/rk28_bl/brightness
or
/sys/class/leds/lcd_backlight/als
(however, I don't see "rk28_bl" or "lcd_backlight" on my gTablet ICS 4.0.4, or my SPH-D710 2.3.6 under /sys/class;
Click to expand...
Click to collapse
Everything under /sys/ depends on the kernel. Some files and directories are standard, some, like the above, are not.
I have "/sys/class/pwm-backlight/" tree on both devices:
Click to expand...
Click to collapse
Interesting...don't have that on the pershoot kernel. Try fiddling with the values in "brightness" as root.
There was also a script to reset brightness to 100% in sqlite database
Code:
#sqlite3 /data/data.com.android.providers.settings/databases/settings.db
sqlite> update system set value=255 where name='screen_brightness';
sqlite> .exit
#reboot
Click to expand...
Click to collapse
+1 again. The path is different (/data/data/...) but that's what I meant. There is also the 'screen_brightness_mode' setting. 1 => Auto brightness, 0 => manual brightness, I think. You may need to change both.
rajeevvp said:
Everything under /sys/ depends on the kernel. Some files and directories are standard, some, like the above, are not.
Interesting...don't have that on the pershoot kernel. Try fiddling with the values in "brightness" as root.
+1 again. The path is different (/data/data/...) but that's what I meant. There is also the 'screen_brightness_mode' setting. 1 => Auto brightness, 0 => manual brightness, I think. You may need to change both.
Click to expand...
Click to collapse
That was a TYPO on my part (fixed on original post for future reference).
My gTablet is on ICS (actually I just flashed AOKP, running pretty good so far) with TeamDRH kernel. My phone is on stock EL29-repack (Calkulin's v3.0) kernel.
Hope all this info will come in handy for someone in the future!
I am glad you were able to solve this issue for your friend because I did exactly the same thing as she did and now I have black screen.
I could not follow all the discussion so, is it possible to dumb it down so I can repeat what you did to fix that XTEX tablet?
Thank you
fazluke said:
I am glad you were able to solve this issue for your friend because I did exactly the same thing as she did and now I have black screen.
I could not follow all the discussion so, is it possible to dumb it down so I can repeat what you did to fix that XTEX tablet?
Thank you
Click to expand...
Click to collapse
Do you have ADB.set up on your PC?
If so, go ahead download and install Droid Explorer (there is a link few posts back).
Once installed, run it, ensuring you "powered on" tablet is recognised. Along the top row of icons, there is one called Screen Cast (hovering over the icons will show the name). Select it, let the Java applet install, then click Screen Cast and that should open a new window, mirroring the tablets screen. Then you can navigate on the tablet to settings.... and get it set.
I think there may be a video on YouTube showing this.
Hope this will help.
[Edit] Here is a link to Youtube:
http://www.youtube.com/watch?v=eEeHaszOMi0&feature=youtube_gdata_player
Sent from NOOK Color CM7.2 using Tapatalk 2
Thanks for the quick response, will download and follow your directions, then report back tonight.
fazluke said:
Thanks for the quick response, will download and follow your directions, then report back tonight.
Click to expand...
Click to collapse
Worked exactly as described with minor issue. Screen cast does not work on locked device. I see the locked screen but can't unlock it and the Youtube link confirmed that too.
I tried to turn it off and on, to see if I can get hold of it before it goes into locked mode and after few tries I got it to work.
Another issue was that my mouse will not control it. SO looking at the computer screen and moving my finger on the tablet surface, I managed to get to setting/display and adjust brightness.
Thank you again for your help.