I just brought a TP 2 days ago (previously TytnII), cool phone, fast and lots of ram.......but the response of the stylus on the screen is slow and sometimes you have to press harder to get a response , finger touch is great though....... any one has this problem or do i have a faulty device ........
Install AdvancedConfig and in TF section there are 2 settings: "Pressure threshold" and "Finger pressure". Set it to maximum and apply changes. It is much more better.
I read that Pressure Threshold to 41 Finger Pressure to 18 was an optimal setting.
I've tried those settings but I'm still wondering if the touchscreen can be set more sensitive.
I have some trouble hitting scrollbars, especially along the right edge of the screen. I need to press noticeably harder. It may just be inherent with the construction of the screen, I assume the edges need more pressure just because the edges are harder and the center is softer. From what I understand, resistive touchscreens have two layers that need to make contact, so in the center its easier to make the layers touch, on the edges it would be more rigid since the two layers are fastened along the edges.
Anyway I tried lowering the Threshold and Pressure values way down and my screen wouldn't respond any more, I had to use Mobiler to set them back to 41 and 18 through my PC.
Can anyone explain how the Pressure Threshold and Finger Pressure settings work?
I assumed setting the Pressure Threshold very low would make it more sensitive(why not 5 or 10?) and setting Finger Pressure high would make each press register more strongly. Doesn't seem to be the case though.
41 and 18 are very usable and way better than whatever the stock ROM had, but I'm still trying to see whats the most sensitive setting possible.
Align Screen
Do a screen alignment that should get you back to the correct stylus settings
dsdmarin said:
Do a screen alignment that should get you back to the correct stylus settings
Click to expand...
Click to collapse
Use your finger when you do a screen alignment.
Has anyone found a way or believe it is possible to control how sensitive each button on the touch cover is? I presume the software just sees it as a giant flat surface, and then maps presses in specific areas to button presses. So I guess really you would be saying to the software that touches from this specific area of the cover we are going to accept at a lower pressure.
What I want is to be able to increase the sensitivity of the spacebar area. I feel like when typing from my lapt or any other non solid surface that I really have to hit the spacebar for it to register, where as the rest of the buttons feel spot on.
Thoughts?
tiny17 said:
Has anyone found a way or believe it is possible to control how sensitive each button on the touch cover is? I presume the software just sees it as a giant flat surface, and then maps presses in specific areas to button presses. So I guess really you would be saying to the software that touches from this specific area of the cover we are going to accept at a lower pressure.
What I want is to be able to increase the sensitivity of the spacebar area. I feel like when typing from my lapt or any other non solid surface that I really have to hit the spacebar for it to register, where as the rest of the buttons feel spot on.
Thoughts?
Click to expand...
Click to collapse
It's funny you mention that, because I have more or less the same issue, but with the Shift keys. I always miss the Shift key and hit either below it or I don't hit it hard enough. I want to prevent that from happening because it can get kind of annoying. Great question.
Your assumption is not actually true, by the way - different parts of the cover have different sensors, or no sensor, under them.
I've found hitting the spacebar with my left thumb way more reliable than with my right. Not sure why, and since this isn't my default style, it currently slows down my typing. Also, if I remember to hit further upward on the bar, it works better. It's sensitive all the way down to the top of the trackpad, but it's either more sensitive closer to the other keys, or something about my hand geometry makes me naturally hit it better when I hit further up.
I always found the sensitivity to be a bit low for my taste and I can't get over this particular sensitivity level still. Since it's software that interprets presses, there could be a registry key for that. Microsoft should make it a setting.
Anyway, I'm also starting to experience a bigger problem - certain keys' sensitivity degrading. Now it takes considerably more force for such often used keys as A and S to register compared to the rarely used ones. While it takes an okay amount of pressure for a "devices" button to register a click, I have to stab the A for it to register. And I think it will get worse.
P.S.: I type quite a lot though wouldn't go for the type cover because touch cover is more aesthetically pleasing and good enough as a keyboard if worked correctly, up to it's potential.
Also, I think most people would appreciate autocorrect on the touch cover.
Hello, I am trying to get familiar with this device and those S-pen enabled apps. How does palm rejection really work? It seems that if the pen touches the screen first and then I rest my palm on the screen, there is no marks made by my palm. If I put my palm on it first, depending on the settings, sometimes my palm leaves some marks.
While using the handwriting feature, I often hit the large space bar by mistake. Any way to avoid this while resting the writing hand on the screen?
There's subtle nuances in terms of performance of rejection of stray touches depending on the application that you're in. Some apps handle it better than others.
For example, in Action Memo as you lay hour hand down to start writing with the stylus it may leave a stray mark. Experiment with this by having the first touch of your hand be your knuckle of your pinky. Drag your knuckle across a little before bringing the tip of the pen to the screen. That stray mark stays there when you're done with your writing with the stylus.
Now repeat the same test in S-Note with finger input enabled. Again practice the motion of keeping your knuckle on the screen and dragging, then bringing the pen to the screen. Notice anything different? As long as you haven't lifted your knuckle, S-Note deletes the stray line the moment the pen gets close. Any marks you've made prior to the pen getting close to the screen stay there however.
The point being that the answer isn't as straighforward as you might think. Here we have two examples of two applications made by the same developer (at least you would THINK its the same developer) yet they act completely different. When writing with these devices one has to be deliberate in when and how they bring their hand and pen to the screen. With practice this becomes second nature though. It definitely helps when note taking apps have the ability to ignore finger input.
With regards to your problem with the handwriting recognition pad used for text input . . I'm with you there. The location of that space bar and all the other buttons is mindbogglingly stupid. They should be located above your palm. IMO what we have here is a classic example of the porting of a function that was developed for phones held in your hand (whereby you do not need to rest your hand on the phone) to a tablet without realizing that the usage of the function would be different on the new hardware.
Hi... using styli on tablets is new for me, and some general guidance would be appreciated.... I'm looking for palm rejection solutions for Samsung Tab devices that (unlike touchscreentune) don't require rooting.
We have some of these Notier styli in-house, and certainly they provide a very nice writing experience, except of course that S Note doesn't have palm rejection so the stylus can't be used for note taking.
A Microsoft Surface 3 will arrive later today, and it has a resistive screen, Wacom stylus and palm rejection, so that should work well. But we'd like to use cheaper Tab devices as well.
Our applications are general note taking (instead of legal pads) and also annotating medical images.
Just my opinion here but the perception that palm rejection is not present is not a black and white thing. Rejection of stray input has more to do with touch sensor type of the device, the application used and the way the device is used within the application in question as opposed to a device itself not having palm rejection support.
Take a capacitive sensor based screen for example, where the user holding a capacitive stylus in hand and he/she brings the hand down to rest on the surface to begin writing. For a brief moment some other part or parts of the hand/wrist are going to contact the screen prior to the tip of the capacitive stylus. Without any other means of knowing how to interpret these inputs the software is going to have to consider registering them somehow. As long as these points of contact don't move significantly before movement of the stylus tip begins the application that is active can then make sense of what is going on and begin to reject the touch inputs from everything but the stylus tip. This is how "palm rejection" works. All touch input has to be evaluated and then the application decides what is input and what isnt.
IMO devices with active stylus support are always going to have an advantage when it comes to "palm rejection" in that software applications can be written in such a way as to completely ignore capacitive touch when the pen is in range of the screen. LectureNotes app for example can be set to completely ignore finger touches for writing operations and I'm sure this is not the only application that can do this. That isn't to say that this is a global feature that ALL apps inherently have, but rather it is a feature available to developers based upon how they implement things. Devices limited to capacitive stylus support only will always be at a disadvantage because the device will not perceive a difference between the tip of a stylus and a finger.
Aloha...
Yes, that's right... the application needs to work with the touch screen driver to reject inputs that aren't useful.
With the Samsung Tab Pro 12.2, resting one's palm on the screen completely disables the ability to write with a stylus (using S-Note), so it's pretty much hopeless, at least using S-Note. S-Note is nicely integrated with Evernote...
Will give LectureNotes a try. It mentions being "usable" with Samsung Tab products, so let's see if it can reject palm pressure.
Palm Rejection just means you don't smudge your drawing/writing with your palm whilst resting it on the screen.
Remember how you used to get a black palm from the ink as a kid, and your whole paper was covered in smudges? That.
It is not a 'Disable Touch Input' feature. It does not disable touch, it does not disable the buttons, and it does not restrict input to the Pen only.
If you're rooted, this is an option: https://play.google.com/store/apps/details?id=com.gmd.spencontrol
Hello XDA! I'm one of those old school guys who likes physical keyboard on phone. Specially I like qwerty sliders but the bad thing is that they are dying out. (Watch out small screens, you are next!). Of course there is Priv but I think that it is sliding wrong way. So I decided to make my own qwerty slider:
I bought "The Beast" Xiaomi Mi4C and a bluetooth qwerty keyboard case for iPhone 6 (about 20$). First I cut the edges from the case, drilled hole for a speaker and made the camera hole little bit bigger for flash light. Then I just glued phone and case together. Because I cut the edges from the case there was about 1-3mm meeting between case and phone. I filled the cap with Sugru™. It should last for usage and temperature changes (between -50°C to +180°C).
For the software part I rooted my Mi4C and flashed CM13. Then I installed Keyboard Manager. With that app you can change keyboard based on orientation automatically. For landscape I use Minuum Keyboard with Mini Mode because I wanted the 5th number row. In the settings you can make the Minuum Keyboard only 140px (60+80) high. It takes only 13% of your screen space on Mi4C. If you don't want to use Minuum Keyboard you can use Null Input Method. In portait I use Google Keyboard. (Hint: You can transfer your dictionary from other keyboard to Minuum Keyboard).
When you install the Keyboard Manager you need to make this fix:
ne0fhyk said:
If you are unable to launch the app after installation, please follow these steps:
- Look in your sdcard folder for the directory /Android/data/com.ne0fhykLabs.android.utility.kmLauncher/files/
- There should be an apk file there, Keyboardmanager.x.y.apk, where x,y stands for the version number
- Copy that file to /system/app/, and change the permissions to rw-r--r-- (Read/write for owner, read for group, and read for other)
- Reboot your device, and try running the app again.
Click to expand...
Click to collapse
Total dimensions are 139 x 69.6 x 16 mm and weight is 228 g but I have installed tempered glass screen protector. For comparison Motorola Droid 4: 127 x 67.3 x 12.7 mm and 178.9 g. Here is more pictures:
http://imgur.com/a/Pbvpo
Here are some similar projects:
NUU keyboard and Alcatel One Touch Star
Turning Samsung galaxy note 4 (SM-N910F) into a mobile pc
OnePlus X and iPhone 6 qwerty case (finnish)
Xiaomi Note 2 and Galaxy S4 qwerty case (finnish)
Hit thanks if you liked my mod
PS: I already bought another original back cover so I can change back to "normal" phone if I like (not going to happen :silly
I have found one 5 row bluetooth keyboard case. It is for iPhone 5/5s so it is much smaller. Maybe it is possible to mod it to Mi4C or other phone (Xperia Z5 Compact?):
That's great. I've seen these few Bluetooth sliding keyboards and have been wondering if it was possible to mod them to fit other phones, and obviously it is!
Does the sliding mechanism have any kind of sensor that will tell the phone whether the keyboard is open or not? I use an Xperia Pro and often slide the keyboard open to wake the phone, and also force it into landscape mode. I also sometimes deliberately shut the keyboard in order to gain access to the landscape on-screen keyboard for special symbols, and it would be easier if I could keep it in landscape mode to do that rather than switch to portrait.
With the keyboard closed I guess the speaker is a bit muffled?
pelago said:
That's great. I've seen these few Bluetooth sliding keyboards and have been wondering if it was possible to mod them to fit other phones, and obviously it is!
Does the sliding mechanism have any kind of sensor that will tell the phone whether the keyboard is open or not? I use an Xperia Pro and often slide the keyboard open to wake the phone, and also force it into landscape mode. I also sometimes deliberately shut the keyboard in order to gain access to the landscape on-screen keyboard for special symbols, and it would be easier if I could keep it in landscape mode to do that rather than switch to portrait.
With the keyboard closed I guess the speaker is a bit muffled?
Click to expand...
Click to collapse
The keyboard that I have does not have any sensor that could tell if the keyboard is open or not. However, I believe that it could be pretty easy to implement with NFC. You could just put NFC tag to the keyboard (where?) and the phone would recognize when the keyboard is closed. (I mean that there would be connection in closed position and no-connection in opened position). Mi4C doesn't have NFC so I can't test this. Actually I don't miss that feature at all. I'm pretty happy with double tap. Also you can simply press one button on keyboard and it will wake up the screen.
It is also possible to implement a switcher for keyboard. With Tasker and Secure Settings you can make a toggle which change the keyboard. And if you wanna be really geeky you can control that toggle with gestures using AutomateIt (or maybe Tasker can do this also) and All in one Gestures. So if you use Null Input Method in landscape you can just swipe up to change it to Google Keyboard for example.
For me Minuum Keyboard has every special symbol that I need. Actually only ones that are missing from keyboard are "[" and "]". There are tons of possibilities to tweak with. It is possible to lock phone in landscape with gestures also. You just have to be little bit creative. Of course "native" QWERTY slider is always better but I'm happy with my mod.
The speaker is not that bad in closed position in my Mi4C. As you can se from the teardown pictures the speaker is located only in the left side of the phone when you look from back. Also the keyboard does not cover the speaker directly so there is a air cap between speaker and keyboard. You can test this by placing your thumb directly to the speaker and then test again and leave this time a 5mm cap between finger and speaker.
Flash-A-Holic said:
The keyboard that I have does not have any sensor that could tell if the keyboard is open or not. However, I believe that could be pretty easy to implement with NFC. You could just put NFC tag to the keyboard (where?) and the phone would recognize when the keyboard is closed. (I mean that there would be connection in closed position and no-connection in opened position). Mi4C doesn't have NFC so I can't test this. Actually I don't miss that feature at all. I'm pretty happy with double tap. Also you can simply press one button on keyboard and it will wake up the screen.
It is also possible to implement a switcher for keyboard. With Tasker and Secure Settings you can make a toggle which change the keyboard. And if you wanna be really geeky you can control that toggle with gestures using AutomateIt (or maybe Tasker can do this also) and All in one Gestures. So if you use Null Input Method in landscape you can just swipe up to change it to Google Keyboard for example.
For me Minuum Keyboard has every special symbol that I need. Actually only ones that are missing from keyboard are "[" and "]". There are tons of possibilities to tweak with. It possible to lock phone in landscape with gestures also. You just have to bi little bit creative. Of course "native" QWERTY slider is always better but I'm happy with my mod.
The speaker is not that bad in closed position in my Mi4C. As you can se from the teardown pictures the speaker is located only in the left side of the phone when you look from back. Also the keyboard does not cover the speaker directly so there is a air cap between speaker and keyboard. You can test this by placing your thumb directly to speaker and then test again leaving and 5mm cap between finger and speaker.
Click to expand...
Click to collapse
For my similar project you've already seen, I've used tasker to automate the phone unlock and horizontal rotation when the NUU keyboard slides out and so connects to BT.
On NUU keuboard there isn't nothing that inform the phone that the keyboard is closed, other than the BT disconnection timeout.
So i made a number of conditions to get practical the exit from the qwerty mode.
The phone turned in vertical, if the screen went in standby, if the phone was oriented verctically, and if a physical button was long pushed.
With tasker I had also the automated soft keyboard switch, because the SW keyboard I wanted to use with the vertical keyboard wasn't physical keyboard friendly. So I used two different sw keyboards that switched automatically depending if the phone was landscape or portrait mode.
The landscape keyboard could be the simple null keyboard, if you don't care about the spell checking function.
How's the weight distribution with this combination? With "native" qwerty phones, like Xperia Pro, and Nokia N900, the weight is mostly in the lower half (the keyboard half), with the top half only being the screen itself. This means that the bit you hold and type on is the heavier one.
With your project, is the top (screen/phone) half heavier than the keyboard, and if so, does that mean it feels top heavy if you're holding it by the keyboard only, and feel like it might topple to the ground?
How's the battery life on the keyboard? It would be annoying to have to charge it every day like the phone itself.
Which exact keyboard did you use? Did you take any pics of the making process, to turn it into a sort of tutorial?
EDIT: Have you done this, or seen it done by others, on different model phones?
pelago said:
How's the weight distribution with this combination? With "native" qwerty phones, like Xperia Pro, and Nokia N900, the weight is mostly in the lower half (the keyboard half), with the top half only being the screen itself. This means that the bit you hold and type on is the heavier one.
With your project, is the top (screen/phone) half heavier than the keyboard, and if so, does that mean it feels top heavy if you're holding it by the keyboard only, and feel like it might topple to the ground?
How's the battery life on the keyboard? It would be annoying to have to charge it every day like the phone itself.
Which exact keyboard did you use? Did you take any pics of the making process, to turn it into a sort of tutorial?
EDIT: Have you done this, or seen it done by others, on different model phones?
Click to expand...
Click to collapse
I haven't measured the weight yet but I will do that later today and add it to the first post. The weight is 228g. For me it is pretty light weigh compared to the size. (Xiaomi Mi 4C itself weights 132g). The weight distribution is pretty stable. I mean if I open the keyboard and leave the phone to the table it will stay steady. I can even push the screen part and it will go back where it was. It doesn't feel that it is going to flip when I'm holding it. Of course there is more weight in the screen part but it is pretty stable.
The battery life of the keyboard is very good. I don't even know how long it will last. I have been charging the keyboard once a week. For phone I got 4h SOT in one charge with bluetooth always on. Sorry, I didn't take any pictures during the process. However, here is one picture when I was testing this combination with double-sided tape. Back then there was nasty cap between case and phone. I filled that cap with Sugru™. I don't know if anyone else has done this kind of mod excluding The Solutor. Althought I have found this: Turning Samsung galaxy note 4 (SM-N910F) into a mobile pc
I believe that I bought this one: Mini Bluetooth V3.0 Ultra-thin Wireless Slide-Out Keyboard case cover for iPhone 6 (4.7). I bought it from different seller from ebay and it was cheaper but the name is same (V3.0).
The Solutor said:
For my similar project you've already seen, I've used tasker to automate the phone unlock and horizontal rotation when the NUU keyboard slides out and so connects to BT.
On NUU keuboard there isn't nothing that inform the phone that the keyboard is closed, other than the BT disconnection timeout.
So i made a number of conditions to get practical the exit from the qwerty mode.
The phone turned in vertical, if the screen went in standby, if the phone was oriented verctically, and if a physical button was long pushed.
With tasker I had also the automated soft keyboard switch, because the SW keyboard I wanted to use with the vertical keyboard wasn't physical keyboard friendly. So I used two different sw keyboards that switched automatically depending if the phone was landscape or portrait mode.
The landscape keyboard could be the simple null keyboard, if you don't care about the spell checking function.
Click to expand...
Click to collapse
Actually you were an inspiration for me, thank you . I will check what Tasker can do for me. For now I think that bluetooth timeout method is too slow. I think that double tab is much faster and easier.
Flash-A-Holic said:
Actually you were an inspiration for me, thank you .
Click to expand...
Click to collapse
Thanks
I will check what Tasker can do for me. For now I think that bluetooth timeout method is too slow.
Click to expand...
Click to collapse
Well, I wrote too quickly, and I wanted to be brief just beacause I don't want to hijiak other's threads.
Anyway, the BT timeout didn't require tasker at all. It's just an internal timeout of the NUU keyboard.
What tasker did in that scenario, was the exit contition:
Enter condition ---> the keyboard slides out and connects to BT. Tasker rotates the screen, switches the keyboard, unlocks the phone (if needed) and so on.
On BT timeout (which is managed by the keyboard)--- tasker reverted the above actions.
Additionally I made a number of other conditions to force the exit task.
The phone is hold vertically for a second or so, the screen is turned off (because the power button was pushed, or because the phone turned it off), a physical button was long pushed, and maybe others that I don't remember.
Obviously there only your fantasy is the limit. You can choose a gesture, a tap combination, a shake action...
Whatever tasker and its plugins are able to manage...
Want to make me one? How much do you want?
Supovitz said:
Want to make me one? How much do you want?
Click to expand...
Click to collapse
Maybe it is better that you make it by yourself. I believe that shipping cost etc. would cost too much for you.
Flash-A-Holic said:
First I cut the edges from the case, drilled hole for a speaker and made the camera hole little bit bigger for flash light. Then I just glued phone and case together. Because I cut the edges from the case there was about 1-3mm meeting between case and phone. I filled the cap with Sugru™.
Click to expand...
Click to collapse
I was wondering about the reason for cutting off the edges and then filling the gap with Sugru. I don't have the parts yet, but I assume the problem is that the phone is slightly too large to sit within the keyboard case edges as manufactured?
It would be great if there was a way to simply remove the phone from the keyboard case just by pulling the phone out, as you can do with the iPhone 6 the case is designed for. Would there be any way to modify the case to make that possible?
Also, is the back of the keyboard case less slippery than the original Mi 4C back cover?
pelago said:
I was wondering about the reason for cutting off the edges and then filling the gap with Sugru. I don't have the parts yet, but I assume the problem is that the phone is slightly too large to sit within the keyboard case edges as manufactured?
It would be great if there was a way to simply remove the phone from the keyboard case just by pulling the phone out, as you can do with the iPhone 6 the case is designed for. Would there be any way to modify the case to make that possible?
Also, is the back of the keyboard case less slippery than the original Mi 4C back cover?
Click to expand...
Click to collapse
Yes Mi4C doesn't fit to the iPhone case properly. If you want removable keyboard case then you can buy a cover case for Mi4C. Then just glue the cover case and keyboard case together. You can also pull out the whole sliding mechanism like this (not my modification):
There is pretty good grip in the keyboard case. Much less slippery than Mi4C.
Thanks.
Looking around, I've found someone doing something similar. A few years old, but may be useful for some ideas: https://www.youtube.com/watch?v=1cu6UCobKyY
I've just bought one of those sliding keyboards for iPhone 6. It looks a little different to your one - mine looks like:
Specifically, mine has a sliding power switch on the left, a Bluetooth sync button above that, the space bar is only two normal letters width rather than three, it has an extra "clover" button on the right of the space bar, the labelling is different on some keys to the left, and the keys in general look flatter than yours.
I haven't tried modding it yet, but I'm a bit put off by the power switch, as I would rather not have to switch the keyboard off and on manually. Does your keyboard have a power switch on it too, somewhere else?
I know that beggars can't be choosers, but having tried this keyboard for a while (in conjunction with a Nexus 7 (2013), as I don't actually have a Mi 4C yet), there are some aspects of it which aren't perfect.
For a start, the keys are quite clicky, much more so than my Xperia Pro or Nokia N900, making it noisier to use whenever there is someone else around.
I would like there to be a Ctrl key - I've been trying to use External Keyboard Helper to map keys, and the ideal one looks like the two clover keys, but I can't seem to map those. When I press those keys I get a big animated white border around the entire screen - is that Google Now? I don't know, as I don't use that.
There is also an annoying few seconds delay after pressing a key to wake up the keyboard and the device responding. With my previous phones with intergrated keyboards, they respond straight away. This is presumably just because of Bluetooth and nothing can really be done about that.
The five-row Boxwave keyboard buddy you mention in the second post looks interesting, but I can't seem to find it (or any generic branded clones) on ebay unfortunately.
pelago said:
I would like there to be a Ctrl key - I've been trying to use External Keyboard Helper to map keys, and the ideal one looks like the two clover keys, but I can't seem to map those. When I press those keys I get a big animated white border around the entire screen - is that Google Now? I don't know, as I don't use that.
Click to expand...
Click to collapse
It's been a while since I did that phone, but, assuming you're rooted you should be able to adjust the keylayout to your lickings
https://source.android.com/devices/input/key-layout-files.html
There is also an annoying few seconds delay after pressing a key to wake up the keyboard and the device responding.
Click to expand...
Click to collapse
I assume that depends on the keyboard used. my NUU keyboard did connect when sliding out, not when the first key was pressed.
Taking account there was a small delay since the connection, because tasker had to wakeup and unlock the phone (if locked and/or sleeping) and to force the horizontal orientation (and optionally to swap the SW keyboard with something mechanical friendly like swiftkey or touchpal), I had no perceivable delay on the first key pressed.
P.S. Guys please resize a bit such huge images before posting them.
They break the forum layout using the classic skin (the yellow one)
The Solutor said:
It's been a while since I did that phone, but, assuming you're rooted you should be able to adjust the keylayout to your lickings
https://source.android.com/devices/input/key-layout-files.html
Click to expand...
Click to collapse
That's a good pointer, I'll look into that. It would be good to remap the keys without using External Keyboard Helper.
The Solutor said:
I assume that depends on the keyboard used. my NUU keyboard did connect when sliding out, not when the first key was pressed.
Click to expand...
Click to collapse
Unfortunately the keyboard I was trying doesn't seem to have any kind of sensor that would know when the keyboard was slid out or not.
I followed Flash-A-Holic's great example and built a cover for Huawei P8 Lite.
Here's the process:
http://symbioosi.blogspot.fi/2016/11/how-to-physical-keyboard-for-huawei-p8.html
Scorpizoid said:
I followed Flash-A-Holic's great example and built a cover for Huawei P8 Lite.
Here's the process:
http://symbioosi.blogspot.fi/2016/11/how-to-physical-keyboard-for-huawei-p8.html
Click to expand...
Click to collapse
Did you just apply a back case from another casing to the bluetooth keyboard of a slider case?
Super happy to have found this thread. I'm using my Motorola Droid 4, but it's lost its GPS antenna, and I'm really tempted to jump at this Moto G4 Plus... Just held it in-store at Best Buy, and it feels massive, something I wouldn't type on with just one hand holding it. I just want landscape QWERTY keyboard functionality!
Scorpizoid said:
I followed Flash-A-Holic's great example and built a cover for Huawei P8 Lite.
Here's the process:
http://symbioosi.blogspot.fi/2016/11/how-to-physical-keyboard-for-huawei-p8.html
Click to expand...
Click to collapse
After being disappointed by Blackberry's attempts at a physical keyboard, I'm back to strongly considering this approach. Your blog post is a great inspiration for finally upgrading my Motorola Photon Q LTE to something that can run something more than Android 4.1.2...
What's the most powerful android phone in roughly the right form-factor for this keyboard case? I see you're ripping off the iPhone case part and attaching a proper case for the Huawei, and I'd do similar, but I'd want the whole thing to be vaguely the right shape. Like, attaching this keyboard to a Pixel XL would just be silly, but there aren't that many android phones around the size of the iPhone 6/7.
Hello,
I've recently bought a Lenovo P11 tablet to take notes. When drawing with a pen, however, I have this problem (and I have verified it by enabling touch detector in developer options): when I lay the pen/finger on the screen, there is an area (I would say 2-3 cm) where the cursor doesn't move even if I move the pen. When I exit that area, a line gets drawn between where I started and where I arrived, but this is wrong as I may have drawn curves in the middle of the two.
This leads to two things:
* When I want to draw something rounded (like a "2"), the upper part gets drawn as a line unless I draw it very big.
* When I want to draw something small, only a dot gets drawn because I didn't leave the "area" and therefore didn't trigger the cursor.
Now I am pretty sure this is a software problem, as if it were a problem with the screen this wouldn't happen only at the start of the line.
Also, I'm sure this is not because of the application I'm using (OneNote), as I've tested with the developer options to show the cursor and in any place in the OS, when I start drawing, the cursor is stuck at where I've begun.
Anyone can help?
Thanks.
Nexgan said:
Hello,
I've recently bought a Lenovo P11 tablet to take notes. When drawing with a pen, however, I have this problem (and I have verified it by enabling touch detector in developer options): when I lay the pen/finger on the screen, there is an area (I would say 2-3 cm) where the cursor doesn't move even if I move the pen. When I exit that area, a line gets drawn between where I started and where I arrived, but this is wrong as I may have drawn curves in the middle of the two.
This leads to two things:
* When I want to draw something rounded (like a "2"), the upper part gets drawn as a line unless I draw it very big.
* When I want to draw something small, only a dot gets drawn because I didn't leave the "area" and therefore didn't trigger the cursor.
Now I am pretty sure this is a software problem, as if it were a problem with the screen this wouldn't happen only at the start of the line.
Also, I'm sure this is not because of the application I'm using (OneNote), as I've tested with the developer options to show the cursor and in any place in the OS, when I start drawing, the cursor is stuck at where I've begun.
Anyone can help?
Thanks.
Click to expand...
Click to collapse
was it a solution?