Please help us test it out and report bugs/issues. Thanks
Just search "adosbox" in Google, I am not allowed to post external URL here.
Any kinds of help are welcome
Hi, i downloaded this last night for one reason and one reason only (for now anyway) - to play championship manager and i managed to get it start a new game it took over an hour to do it and then simple things like changing pages takes over a min so it esentially unplayable.
Other that great work and i wish i could be of more help but im afraid ive never done any software programming in my life
Wow, this is perfect so far. I just tried cyberdogs on it and it ran amazing. The program is really easy to get running. Is there a way to mount hard keyboards to the controls?
Just tried it. works like a charm.
Yep, works awesome.
Sent from my GT-I9000 using XDA Premium App
I am really enjoying adosbox right now on my Transformer, but lack of 3.1 mouse support has saddened me to the point where I compiled from source myself. I have it working sort of (on the java end), but because the build screen size doesn't match with the actual screen size, I am having issues with the mouse not following perfectly. I would like to get mouse support working better for 3.1 devices (and probably better emulation going for pre 3.1 devices), but I need to edit some of the C files for that. Unfortunately I have not done much native code on Android, so I am running into problems compiling. The ndk-build script seems to fail on me with an error of "missing separator" in the SDL-1.2 make file. Sadly I have never used make so I don't know how to correct it.
Today I saw the build_instructions.txt in jni/application/dosbox/. Are you building through this instead of the ndk (do I need to get gcc ARM cross compiling installed on my linux box)? In either case where does the dosbox-0.74-cfg-pelyaSDL.tar.gz come from?
Any help you could give me in getting the native part to build would be appreciated. Then I can focus on getting some usability stuff working and throw patches your way.
P.S. The feedback page is broken.
Hi. That's great news.
I love dosbox an I appreciate your work.
If you don't mind I will post some issues here.
I've installed adosbox 0.2.5 on my Desire Z.
I've tried to run some apps and games.
Dos Navigaror: Usable.
1. Mouse trackpad emulation works quite well, however it only moves in x,y axis separately. No intermediate directions (I suppose the hardware does not allow it). Any possibilities to solve this?
2. Touch screen mouse movement works quite well - however with delay.
2a. Well, sometimes there is no mouse. I swing on the screen with no effect.
3. It does not respond to screen tap as a left mouse click. Well it works sometimes. I have no control on that.
3a It does not respond to double tap (double click) at all.
4. No possibility to bind/emulate arrow keys. I can't find such function in dosbox menus. ---edit --- I could bind some keys but... see the edit part down there.
5. On PC I've been using config to autostart Dos Navigator with dosbox start. How to do it on Android? I couldn't find .conf file on my device.
System shock: starts but unplayable.
1. I've got a slide show. I've increased the CPU cycle to 1000 even to 2500 with no satisfactory effect.
2. On screen mouse movement works but the cursor jumps into different position when tapping.
3. With no option for binding keys this game is 100% unplayable.
Hocus Pocus: works but no arrow keys.
1. It starts nicely.
2. It reacts on "FN" key - the hero is shooting.
3. However no hardware arrow keys makes the game unplayable. Moving with trackpad sucks so much that the game is unplayable.
Oxyd Magnum: Playable but not exciting.
1. It react on taping the screen.
2. On screen mouse works well but with some ugly delay. This takes out most of the fun.
So the main issues I see are the cpu speed, mouse delay and the hw keys binding.
You are making a great job.
However making dos games being fun on the phone needs good controls workaround. Without that - no fun.
Thank you.
Don't forget we appreciate your work.
-------------edit-----------
Keys binding:
The .dosbox\mapper-0.74.map file (the file for binding keys) can not be found from the phone level. It must be done from a PC level. It's not a big issue but what to hide the file for?
After rebinding left FN, left shift and tab keys Hocus Pocus is quite playable.
It would be nice if you provide us the list of numbers for HW keys on some devices.
I can't bind "menu" as right arrow. And I can't bind search, sym, and the two shortcut keys. They are left useles.
And binding some keys as arrows disables trackpad!
Sound:
No mater what number I set for cycles I can't make the sound to play smoothly.
Any suggestions?
Someone knowns the makefile system for adosbox "libapplication.so"?
Ive been trying for a long time to recompile adosbox for mips, and i still unable to compile that file, not even for arm.
Hello,
I am using aDOSBox to run QBASIC (yes I know there are "better" and "faster" interpreters/compliers, but some have bad issues, see one comment about writting files on X-11 BASIC, others have a max file size) with an external keyboard (so I can see the screen while typing - can you make the virtual keyboard transparent?).
I have found that some keys do not work nor processed correctly in this version (freshly gotten from Google Play), namely the "." when shifted (I get ":" every time, all other punction keys appear to be fine). At first I though this was a KCM problem (had problems with mismapped keys on a Droid X), but while I was briefly able to rooted my tablet (someone please read/question my post/question about the Azpen A701 rooting) I was able to view the generic.kcm and other kcm files (lost root right after this) and those files define the shift period combination correctly. Also I get a ">" when I hit that combination in the 920 Text Editor.
Function keys seem to send to Android key processes (opening/launching other apps) instead of work in the program. Insert, Delete, Home, and End do not seem to be working at all.
Related
This might not be for everyone but I thought I'd share. Before this I couldnt stand playing my games on Nesoid since the virtual D-pad wasnt that accurate and I would always end up pressing the wrong direction since it is very small and without something to feel you dont know what you are pressing. The same goes true for the virtual A and B buttons since they were so small I would constantly jump when I wanted to fire and vice versa...
So here goes:
- Under user settings make sure screen upside down is checked and set the orientation to only landscape (These settings will make sure you can use the trackball for your trackball D-pad on the proper left side we have always been used to PLUS it makes the screen size bigger)
- Set trackball sensitivity to 2 since the trackball is REALLY sensitive when at 3 or more
- Under key settings set the B button as volume down and A button as volume up
Presto! now you've got a physical d-pad on the correct side (left) and physical buttons on the right...
Hope this helps
Using the trackball to move would make it so u had to constantly scroll the TB to move :/ ... That would get rather annoying lol
I like it! Cool idea.
the virtual buttons on gameboid works well for me but this sounds like a good idea (for the a/b buttons) but idk about the track ball.....
edit: nevermind you can use vol up/down for bumpers on snesoid, let me try this out
what would be amazing is some sort of support for a bluetooth gamepad
That would be sweet, i noticed in snesoid if i turn off keypress vibration it makes it a lot lot lot easier to through combos in street fighter
malicious85 said:
what would be amazing is some sort of support for a bluetooth gamepad
Click to expand...
Click to collapse
I saw an article where some hacked a Playstation 3 controller (bluetooth) to work with the Nokia N900. Both phones run linux, so I'm thinking it's at least hypothetically possible.
altarity said:
I saw an article where some hacked a Playstation 3 controller (bluetooth) to work with the Nokia N900. Both phones run linux, so I'm thinking it's at least hypothetically possible.
Click to expand...
Click to collapse
this would be amazing, unfortunately i do not possess the skills to do this, anyone know someone that does?
lolittle said:
Using the trackball to move would make it so u had to constantly scroll the TB to move :/ ... That would get rather annoying lol
Click to expand...
Click to collapse
tried this set up, and i have found that using the trackball is significantly less annoying than the on screen dpad
someone really needs to figure out how to get a PS3 controller paired up tho
Ok I can't help but put my 2cents in, in the market there is a program called wiimote and it controls as well as can accept input from the wii remote. Getting code like that to work with an emulator would truly make the android OS a competitor in the gaming market.
I have one of these: http://cgi.ebay.com/MSI-Bluetooth-G...oysticks_Game_Controllers?hash=item19ba54b4e7
And I have successfully paired a BT keyboard to my Nexus a while back.. I'll give it a try and get back to you guys.
C
Hi guys -
Shocked that no one else has mentioned this issue on XDA yet, actually...
One of the reasons I bought the keyboard dock for the Transformer was for the possibility of using VNC / RDP clients to control remote machines. This works brilliantly with the built-in client (Splashtop) -- with 2 mildly important exceptions: trackpad scrolling and right-click.
Right-clicking obviously backs out of the session completely (as this is hard-mapped to Android "back")... which is only less frustrating than 2-finger scrolling actually crashing the client and ending the session. If you even touch the trackpad with two fingers, you're finished. (Note: I've tried using USB mice and other clients as well with the same result.)
I'm really surprised at the oversight on ASUS' part here. The transformer and dock would be the perfect solution for this task if it were not for these issues.
So... as I'm not a programmer or dev (like some of the brilliant minds that grace this forum) I'm wondering -- is this something that could be fixed?
Trevor_g said:
Hi guys -
Shocked that no one else has mentioned this issue on XDA yet, actually...
One of the reasons I bought the keyboard dock for the Transformer was for the possibility of using VNC / RDP clients to control remote machines. This works brilliantly with the built-in client (Splashtop) -- with 2 mildly important exceptions: trackpad scrolling and right-click.
Right-clicking obviously backs out of the session completely (as this is hard-mapped to Android "back")... which is only less frustrating than 2-finger scrolling actually crashing the client and ending the session. If you even touch the trackpad with two fingers, you're finished. (Note: I've tried using USB mice and other clients as well with the same result.)
I'm really surprised at the oversight on ASUS' part here. The transformer and dock would be the perfect solution for this task if it were not for these issues.
So... as I'm not a programmer or dev (like some of the brilliant minds that grace this forum) I'm wondering -- is this something that could be fixed?
Click to expand...
Click to collapse
I believe it is probably possible to remap the right click button by editing the kernel and recompiling it (just like how people got rid of the tap click), thus letting you make it right click instead of "back". Some dev who looked at Transformer's kernel can probably give a definite answer.
i believe long press left click=right click
Sent from my Transformer TF101 using Tapatalk
Hmmm... that sounds positive. A hack to switch back and forth from "back" to "right-click" mapping (depending on the active app) would be helpful here.
However, the lack of right-click support isn't nearly as bad as the trackpad scrolling bug. The lack of this basic functionality makes remote clients really horrible to use.
Add one more feature to the list here: click and drag. This doesn't work also, meaning that the only way to scroll anything in VNC is to actually point and click. Yeeesh!
Trevor_g said:
Hmmm... that sounds positive. A hack to switch back and forth from "back" to "right-click" mapping (depending on the active app) would be helpful here.
However, the lack of right-click support isn't nearly as bad as the trackpad scrolling bug. The lack of this basic functionality makes remote clients really horrible to use.
Add one more feature to the list here: click and drag. This doesn't work also, meaning that the only way to scroll anything in VNC is to actually point and click. Yeeesh!
Click to expand...
Click to collapse
Uh, what VNC app are you using? Two-Finger scrolling works on any of the ones I use (Splashtop, RDP) and drag is just click, click and hold and then move your mouse.
frosty5689 said:
Uh, what VNC app are you using? Two-Finger scrolling works on any of the ones I use (Splashtop, RDP) and drag is just click, click and hold and then move your mouse.
Click to expand...
Click to collapse
I'm not speaking of the touchscreen functionality; these issues affect the trackpad on the keyboard dock making it almost unusable for this purpose.
I'm using Splashtop (bundled software -- but regardless, these issues are present on any VNC software I've tried). Two-finger scrolling does NOT work on the trackpad (if you try, your session will actually crash). Neither does click and drag, and right-click backs you out of the session completely. :s
Click and drag works in the HD version of Splashtop
Remote RDP Enterprise/free? supports drag and right click
Thanks for the input!
gwai_jai: Splashtop HD does seem to support click and drag - good find (discovered that recently). Now, if only we could find a way to map right-click and scroll (especially) to the trackpad on the keyboard dock...
dude2k5: When you say that this program supports right-click, is it just some kind of "virtual" / on-screen solution, or does the right mouse button on the trackpad actually work correctly?
Trevor_g said:
dude2k5: When you say that this program supports right-click, is it just some kind of "virtual" / on-screen solution, or does the right mouse button on the trackpad actually work correctly?
Click to expand...
Click to collapse
Supports physical right-click with the right button on the TF trackpad.
That is my primary RDP app now because it's the only one that properly supports right-mouse.
Two finger scrolling on the trackpad doesn't work for me though.
Trevor_g said:
Thanks for the input!
gwai_jai: Splashtop HD does seem to support click and drag - good find (discovered that recently). Now, if only we could find a way to map right-click and scroll (especially) to the trackpad on the keyboard dock...
dude2k5: When you say that this program supports right-click, is it just some kind of "virtual" / on-screen solution, or does the right mouse button on the trackpad actually work correctly?
Click to expand...
Click to collapse
oh man iam waiting for scroll on the trackpad so desperately (two finger scroll on the touchpad of the dock)...then the transformer is perfect!!!
now iam using splashtop HD and i have to use page up/down for scrolling in windows.
opened a request on the splashtop forum support-remote.splashtop.com/entries/20210293-better-support-for-touchpad-dock-asus-transformer
I'm currently 'hacking' android-vnc-viewer (OpenSource) to support the TF touchpad. I have right-mouse-button and mouse tracking working although the former is a bit of a hack and the latter is laggy. I'll look into two-finger scrolling...
It's not perfect, contains debugging, and I need to do a fair amount of cleaning
up before I can commit patches to the opensource code project, but if people want to beta test I can stick a build up someplace.
YES!
Fantastic that someone is working on this! I'm sure I'm not the only person who would be willing to serve as a beta tester...
The first RDP app to support right-click, 2-finger scroll and mouse tracking would make it BIG I'm sure.
2-finger scrolling is huge... I agree with the previous poster. The Transformer handles this so well in Android, and dragging scroll bars and / or being forced to use 'page down' to navigate really does ruin the experience.
Keep us updated, mamoulian666...
rilot said:
Supports physical right-click with the right button on the TF trackpad.
That is my primary RDP app now because it's the only one that properly supports right-mouse.
Two finger scrolling on the trackpad doesn't work for me though.
Click to expand...
Click to collapse
This sounds promising as well - I'll look into it. Thanks for the heads up!
OK here's a link to my current build:
http://dl.dropbox.com/u/13927052/androidVNC-branch_antlersoft_eeePadBuild_001.apk
As far as I know it's only VNC though, no RDP!
Because it's not signed it will probably ask you to uninstall the Market version first, it also won't use the settings so use the export function in the settings screen before uninstalling.
It should show some toasts on startup indicating that it has detected the Tranformer's touchpad, you should switch to 'mouse input mode' to get the pointer following and right-mouse-button. There might be some other toasts in there for my debugging purposes, if any are particularly annoying I can comment them out quite easily.
No two-finger yet, but any other suggestions/problems let me know.
Has anyone tried the build I put up?
If so can I have some feedback please - does it work OK for you?
It wouldn't install over the market version, but removing that manually first and then installing your worked.
As for right click, it works for thouchpad
It doesnt work for usb mouse, right button on it does nothing (don't remember it if it backed out of the app before).
I like the improments you made to the android-vnc app. Could you please post a version of the app without the toasts? Every so often one of them gets stuck on the screen and won't go away for ~5 min.
I like the right click option but the mouse tracking is very jumpy. I find that when the vnc pointer lags behind the trackpad the two won't line up again and will stay a fixed distance apart. Also is there a way to make the movement on the trackpad not act like a click and drag?
Xtralogic is the way to go. It supports right click (dock and Bluetooth). It also support the scroll wheel on Bluetooth. Give it a try on the Transformer, you'll be surprised how well it works (and how integrated it is).
Cheers.
Hiya Everyone,
I've just rooted my Nook Simple Touch and have it all working from a USB keyboard which is great!
I really need the Nook as my unit has no mains electricity and I use solar panels instead which can be difficult at times as they are mounted in the window and are facing the wrong way really but it is what it is. I know everyone is alarmed at the amount of power it uses when in USB mode but it's nothing compared to the 5 watts my DAB radio pulls! To be honest it's even at lot less than the 1.5watts of the LED light!
Anyway it's basically great but I want to get it working as well as I can for my application.
I'm using a new text editor from F-Droid called Text Warrior:
https://f-droid.org/repository/brow...com.myopicmobile.textwarrior.android&fdpage=4
It's the best text editor I've found for the Nook so far and it's also a GNU application with source code!
If you havn't already checked out the F-Droid stuff I really recommend it as a lot of the apps there work on the Nook and it can be hard to find stuff for the earlier versions of Android.
Anyway that's my setup. What I'm wondering is if it's possible to assign keys on my USB keyboard to do different things and how I would go about doing that? For instance it might be cool if I could use the Esc key as a back button or the extended win keys menu key as an android menu button and things like page up and page down etc. How could I go about setting the keys up for different functions? Anyone have any idea?
Freya
FreyaBlack said:
Hiya Everyone,
I've just rooted my Nook Simple Touch and have it all working from a USB keyboard which is great!
I really need the Nook as my unit has no mains electricity and I use solar panels instead which can be difficult at times as they are mounted in the window and are facing the wrong way really but it is what it is. I know everyone is alarmed at the amount of power it uses when in USB mode but it's nothing compared to the 5 watts my DAB radio pulls! To be honest it's even at lot less than the 1.5watts of the LED light!
Anyway it's basically great but I want to get it working as well as I can for my application.
I'm using a new text editor from F-Droid called Text Warrior:
https://f-droid.org/repository/brow...com.myopicmobile.textwarrior.android&fdpage=4
It's the best text editor I've found for the Nook so far and it's also a GNU application with source code!
If you havn't already checked out the F-Droid stuff I really recommend it as a lot of the apps there work on the Nook and it can be hard to find stuff for the earlier versions of Android.
Anyway that's my setup. What I'm wondering is if it's possible to assign keys on my USB keyboard to do different things and how I would go about doing that? For instance it might be cool if I could use the Esc key as a back button or the extended win keys menu key as an android menu button and things like page up and page down etc. How could I go about setting the keys up for different functions? Anyone have any idea?
Freya
Click to expand...
Click to collapse
You can easily change what your keyboard keys do in the file /system/usr/keylayout/qwerty.kl. I personally use a very good modified one by Renate with a few of my own modifications.
Thanks so much Nookie! That looks great! I will try and install it today.
I'm also running the Nookie terminal emulator BTW which I think must be something to do with you?
Right off to give it a go!
Freya
FreyaBlack said:
Thanks so much Nookie! That looks great! I will try and install it today.
I'm also running the Nookie terminal emulator BTW which I think must be something to do with you?
Right off to give it a go!
Freya
Click to expand...
Click to collapse
It might. I did make a few modifications to the original Terminal Emulator and probably put it up for download somewhere here on the forums. What's the package name (/data/app)?
How'd the .kl installation go for you?
I discovered Noogie and after a lot of messing about I managed to get the qwerty.kl installed and working quite well.
Sadly it seems it's not going to be easy to reprogram for a UK keyboard though as you can only reprogram entire keys and not their shifted states.
In the UK the @ and " symbols are swapped with one another but on the upside the # key now does a # so that's nice.
I'm going to get used to the USA keyboard layout and be driven nuts when I switch back to a UK keyboard again!
I'm sure the terminal emulator must be your version as it has nookie in the filename.
Freya
FreyaBlack said:
I discovered Noogie and after a lot of messing about I managed to get the qwerty.kl installed and working quite well.
Sadly it seems it's not going to be easy to reprogram for a UK keyboard though as you can only reprogram entire keys and not their shifted states.
In the UK the @ and " symbols are swapped with one another but on the upside the # key now does a # so that's nice.
I'm going to get used to the USA keyboard layout and be driven nuts when I switch back to a UK keyboard again!
Freya
Click to expand...
Click to collapse
Hmmm. I see your point, and it's a good one, indeed. Tell you what - I'll work on it this week and tell you if I come up with anything by Sunday night. Sound good?
FreyaBlack said:
In the UK the @ and " symbols are swapped with one another...
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=59922517&postcount=406
Thanks Renate,
I ended up sitting in a hotel room with a hex editor but I got it to work and have since spent quite some time on Solar with the Nook.
Thanks again for your help with that!
Now I'm back to civilisation for a while and I'm wondering if it is possible to get the cursor keys to work properly too.
They don't seem to move up and down and side to side in the text in the way I would expect!
Is it possible to fix that as well or is that just an android feature!
Freya
FreyaBlack said:
Thanks Renate,
I ended up sitting in a hotel room with a hex editor but I got it to work and have since spent quite some time on Solar with the Nook.
Thanks again for your help with that!
Now I'm back to civilisation for a while and I'm wondering if it is possible to get the cursor keys to work properly too.
They don't seem to move up and down and side to side in the text in the way I would expect!
Is it possible to fix that as well or is that just an android feature!
Freya
Click to expand...
Click to collapse
Does this happen when your Nook is in portrait mode, landscape mode, or both?
If they work correctly in portrait but don't work right in landscape, there is a fix that I applied several months ago that resolves the issue.
ИΘΘK¡€ said:
Does this happen when your Nook is in portrait mode, landscape mode, or both?
If they work correctly in portrait but don't work right in landscape, there is a fix that I applied several months ago that resolves the issue.
Click to expand...
Click to collapse
OUCH! Yes you are totally right.
I'm using an ipad stand from a pound shop to hold the Nook in place and it fits quite nicely in Landscape.
Also I just find it's a bit more like a normal laptop setup when in Landscape mode too.
I didn't click what was happening. Doh!
So how do I go about fixing that?
I guess I have to swap the cusor keys around?
Freya
@FreyaBlack,
Kind of, yeah. Follow the instructions at this post by Renate to apply a patch to /system/framework/services.jar that will prevent your arrow keys from rotating when in landscape mode.
Good to go!
I'm back to civilisation for a while but sadly I havn't been able to get this to work. I don't quite understand what you are supposed to do and I usually use ssh or similar rather than adb.
What does this mean?
Then you edit in the replacement in smali/com/android/server/KeyInputQueue.smali
Click to expand...
Click to collapse
I assume I need to change services.jar in some way.
Do I use the attached file?
Freya
@FreyaBlack,
After you acquire services.jar on your PC, the next step is to decompile it using this command:
Code:
apktool d services.jar
Then, go into the root folder of where you decompiled that file, and navigate to the .\smali\com\android\server\ directory. In that folder, locate the file KeyInputQueue.smali. Open that file with a good text editor (like Notepad++ on Windows), delete the entire contents and copy/paste in the entire contents of the partf.txt file attached to Renate's post I linked two posts above. Save that file.
Now, all you have to do is recompile the edited services.jar file using this command:
Code:
apktool b [the directory where you extracted the file originally] services.jar
Only thing left after that is to replace the existing services.jar on your Nook (located in /system/framework) with the one you just created, reboot your Nook, and you're good to go.
You can also use my mergesmali utility to merge correctly formatted patches.
nook121patch.zip has patches for various things that can be selectively supplied.
They are both found in the signature under "mergesmali".
Hiya Renate,
So you mean I can find a patch for the file or something and use mergesmali to apply it?
I assume Nookie is saying I need the Android SDK or the java sdk to make the changes but by doing this patch thing I can sort this without having to do that?
I have my hex editor to hand but a whole SDK is more than my 3G connection can handle right now!
Freya
Hi All,
I am wondering if anybody here had any success with getting their Yoga Book to work nicely with the GIMP photo editor at all? I can use it to draw, but as a mouse with no pressure. I went through a few tutorials online on how to get the GIMP to work with Bamboo/Wacom tablets, but it doesn't seem to work with the Yoga Book, as the drivers aren't being seen by GIMP or DirectInput for whatever reason.
I am more of a casual artist, and so I don't feel like I want to fork out money for say Photoshop, when the GIMP can for the most part do what I'd like. Plus, I am mostly an open source guy, using Linux as my main daily driver on my home PC, that I am fairly used to the GIMP already.
Thanks!
kveroneau said:
Hi All,
I am wondering if anybody here had any success with getting their Yoga Book to work nicely with the GIMP photo editor at all? I can use it to draw, but as a mouse with no pressure. I went through a few tutorials online on how to get the GIMP to work with Bamboo/Wacom tablets, but it doesn't seem to work with the Yoga Book, as the drivers aren't being seen by GIMP or DirectInput for whatever reason.
I am more of a casual artist, and so I don't feel like I want to fork out money for say Photoshop, when the GIMP can for the most part do what I'd like. Plus, I am mostly an open source guy, using Linux as my main daily driver on my home PC, that I am fairly used to the GIMP already.
Thanks!
Click to expand...
Click to collapse
Hey,
I indeed had the same issues with GIMP (also with Krita and MyPaint - I am open source guy as well ) a while ago. The trick is to install specific drives from Wacom. Here is the link (or at least I hope it is, I tried this few months ago ): http://us.wacom.com/en/feeldriver/ EDIT: Please note that this driver might change the way stylus behaves and might not work correctly.
Just little bit of advice/side note; I tried all thinkable painting/photoshop software on my yoga - both open source and piad one (trial versions) - and thou I use open source software daily in my work (GIMP and Inkscape) it is not the same on yoga. Small screen and Atom processor is not very optimal - it works, no doubt about it, but it just isn't same as on the desktop. I hate to admit it, but after a while I ended with older version of Sketchbook Pro - it runs very well and has nice easy UI and reasonably powerful tools, which is perfect for light sketching.
Thanks. So, I tried installing the driver, and it did install successfully. However, GIMP is still unable to work with pressure sensitivity. On the bright side, the Halo keyboard, and touchscreen are unaffected and still work as expected. The only issue from installing the driver is that now when I use the pen on the create, I still a full white windows cursor on the screen which is very very annoying.... I very much preferred the unobtrusive translucent circle. I went into the settings to attempt to return said circle, but it resulted in total failure as the annoying white Windows cursor remained. This now renders any drawing or writing activity now annoying as the windows cursor is an eye sore and just gets in the way and blocks whatever is behind it.
I am writing this on the Yoga book, and I'm just noticing something with the keyboard. I am a very fast typer, and I am feeling the hepatic feedback from each key press, but the click sound is only heard after I stop typing quickly. Not sure if this is related to the driver or if it was like this prior.
I am now considering removing said driver, however, I am unsure if it completely replaced the Lenovo one, and if I remove it, will it just turn this machine into a brick, and needing a full factory reset to get everything back to normal.
For anyone else reading about this driver, I highly recommend to avoid installing it until these specific quirks can be figured out, and if uninstalling it after will result in a non-functional wacom touch screen and create pad. I am really hoping that the keyboard part of the create pad is part of a completely separate driver, and the pen button/light is just a toggle between two completely separate hardware modes. I'll see if I can use a restore point perhaps to return back the previous functionality. I am hoping that Lenovo themselves issues an update for this rather great piece of technology so that we don't need to download wacom or third party non-Lenvovo tested drivers. This device is fairly unique and it's hard to see a generic driver keeping all the customization from Lenovo working 100%.
UPDATE: Okay, so I was unable to remove the driver using the standard add/remove program thing in Windows, which seemed to have restored the original functionality. My cursor is back to a nice small circle when I hover or use the create pad with the pen, which is much more favorable. I can live without pressure sensitivity in GIMP, as long as the sketching apps have pressure and show me a non-obtrusive circle, I can easily export said sketches into PNG format and import that into the GIMP to further edit using more advanced tools.
kveroneau said:
Thanks. So, I tried installing the driver, and it did install successfully. However, GIMP is still unable to work with pressure sensitivity. On the bright side, the Halo keyboard, and touchscreen are unaffected and still work as expected. The only issue from installing the driver is that now when I use the pen on the create, I still a full white windows cursor on the screen which is very very annoying.... I very much preferred the unobtrusive translucent circle. I went into the settings to attempt to return said circle, but it resulted in total failure as the annoying white Windows cursor remained. This now renders any drawing or writing activity now annoying as the windows cursor is an eye sore and just gets in the way and blocks whatever is behind it.
I am writing this on the Yoga book, and I'm just noticing something with the keyboard. I am a very fast typer, and I am feeling the hepatic feedback from each key press, but the click sound is only heard after I stop typing quickly. Not sure if this is related to the driver or if it was like this prior.
I am now considering removing said driver, however, I am unsure if it completely replaced the Lenovo one, and if I remove it, will it just turn this machine into a brick, and needing a full factory reset to get everything back to normal.
For anyone else reading about this driver, I highly recommend to avoid installing it until these specific quirks can be figured out, and if uninstalling it after will result in a non-functional wacom touch screen and create pad. I am really hoping that the keyboard part of the create pad is part of a completely separate driver, and the pen button/light is just a toggle between two completely separate hardware modes. I'll see if I can use a restore point perhaps to return back the previous functionality. I am hoping that Lenovo themselves issues an update for this rather great piece of technology so that we don't need to download wacom or third party non-Lenvovo tested drivers. This device is fairly unique and it's hard to see a generic driver keeping all the customization from Lenovo working 100%.
UPDATE: Okay, so I was unable to remove the driver using the standard add/remove program thing in Windows, which seemed to have restored the original functionality. My cursor is back to a nice small circle when I hover or use the create pad with the pen, which is much more favorable. I can live without pressure sensitivity in GIMP, as long as the sketching apps have pressure and show me a non-obtrusive circle, I can easily export said sketches into PNG format and import that into the GIMP to further edit using more advanced tools.
Click to expand...
Click to collapse
Hey, sorry to hear that you had issues, I did not noticed any when I tried the driver and pressure in GIMP/Krita/MyPaint was working - if I remember correctly, there was new wacom icon under Control Panel, did you tried adjust this? Also in GIMP you need to enable, and correctly set, "Dynamic" setting under brush tool for pressure sensitivity to work.
Anyway, I edited my previous post with warning about drivers so that anyone would know immediately. Again sorry for the issues, but from my point of view it worked.
Talsi said:
Hey, sorry to hear that you had issues, I did not noticed any when I tried the driver and pressure in GIMP/Krita/MyPaint was working - if I remember correctly, there was new wacom icon under Control Panel, did you tried adjust this? Also in GIMP you need to enable, and correctly set, "Dynamic" setting under brush tool for pressure sensitivity to work.
Anyway, I edited my previous post with warning about drivers so that anyone would know immediately. Again sorry for the issues, but from my point of view it worked.
Click to expand...
Click to collapse
I did notice the new settings under control panel, but there was nothing there but pen button related options, of which the Lenovo pen has no buttons. I tried a few options in GIMP, and the Wacom tablet did display itself as an Input device. I figure I could have gotten it working, but having a full Windows cursor when using the create pad was just a bit distracting in my eyes. This cursor persisted in programs which it is normally absent such as the Windows built-in Sketchpad which is one of the easiest and quickest programs to launch for quick jotting of notes and sketches. I tried changing a few options in both Settings and Control panel, but the Windows cursor remained.
Thank for your help anyways, I'm sure this driver will be useful to other people.
I have an Android box, well, I have about 5 but this one is the fastest and the rest are in storage, and all seems to be working pretty well except...I can't find any way to type the letter "Q." Not upper case, nor lower case. Not using the on-screen keyboard, nor my external mini keyboard. I can't use it in web browsers or search bars on system settings menus or file browsers or anywhere else I can think to try it.
All the other letters an numbers seem to work fine. The modifer keys seem to work as well, as far as I can tell (the mini keyboard has some shortcut keys I have no guide for so I can't be POSITIVE they are fine but there haven't been issues). The box is a media center, but I haven't really set that part up. I'm currently living in a motel and its the closest thing I have to a computer, so I've been using it for general purposes like browsing, YouTube, and unfortunately WRITING which my current job requires. Thankfully, I found a file with an uppercase and lowercase "Q" in the filename so I can cut and paste but that's really cumbersome.
The box has a root-switch in the settings that I haven't messed with. It also has an on-screen keyboard that won't go away when I use the external keyboard - but I can live with that. It doesn't seem to recognize the external keyboard as an actual keyboard and it might be because it uses an RF receiver instead of bluetooth.
I came here because my dad said it might be a problem with the motherboard and if that's the case I'm going to be cutting and pasting until I can find housing. But on the off chance that there's any way around it, you guys would be the ones to figure it out. I've been untangling the idea in my brain for how to maybe set up a macro for about the last half hour. I have external keyboard helper pro purchased also if that's of any help. Dunno. If you have questions for specifics I will help as best I can. Sorry if this is an odd or out of place Q. haha ... Q
Thanks guys
Its all I can afford to work with right now so I gotta do what I can