I'm sure you guys have seen the video of Google Maps rocking out on the new Motorola Tegra 2 Tablet, so I was pretty excited to download the update today. But it appears that we are unable to do the 2 finger "swipe" (which changes pov down) and the "twist" (which rotates the view).
Maybe I just suck with the movements, but I was trying for five minutes and couldn't accomplish either. So what do you think? Hardware can't support it (a la the Nexus One), or software?
There is no doubt that multitouch is currently very broken on the G Tablet. Single touch is very sensitive, but as soon as you try to detect even 2 fingers simultaneously, the driver seems to have some major issues, glitching back and forth unless you lean all out on the screen. It's like it's normalizing the magnitude of the two signals improperly. And there seems to be no "true multitouch" capability with this sensor, because I've been unable to get it to sense three simultaneous touches at all. I've tried two of the Multitouch testing apps in Market, with the same results.
So definitely there's the need for updated touchscreen drivers to fix pinch and zoom, etc. , but I'm not clear whether or not the touch sensors are hardware-crippled like the Nexus One, or whether the improved drivers can fix this better than I suspect.
Edit: See my post here: http://forum.xda-developers.com/showthread.php?t=863741&page=8 I've managed to fix my terrible multitouch/pinch-to-zoom. It looks like it was a calibration issue, and now that I got the TSCalibration executable working properly, pinch-to-zoom works much better. However, the limitation on multitouch to two simultaneous touches seems to be baked into the drivers or the hardware and can't be fixed by calibration. So no "true multitouch" yet with the G Tablet.
Thanks for the excellent reply. Crossing my fingers it's just a driver issue that can be addressed. I've seen the devs here work wonders, so hopefully we can get this touch screen under control.
Sent from my T-Mobile G2 using XDA App
Well just for you all know, I have a streak, an evo, my gf has incredible my brother has a droid. ALL OF THEM, excluding the evo, has just 2 finger recognition in the multitouch test's from market.
The evo has 5. Also, maps 5 works perfectly on my streak with just 2 finger recognition.
Cheers
New maps works fine on my nexus one. Haven't tried on my G tab yet.
The two finger down works on my gTab but I can't make the 2 finger rotate do anything, I can't make it do anything on my droid 1 either, nor do I see any 3D buildings, guess I just don't know where to look.
landykos said:
New maps works fine on my nexus one. Haven't tried on my G tab yet.
Click to expand...
Click to collapse
Do you mind sharing which ROM are you running on your N1? I can't get the two finger swipe to work on mine or on the gtab.
EDIT: scratch that - I have it working now on N1.
prscott1 said:
Do you mind sharing which ROM are you running on your N1? I can't get the two finger swipe to work on mine or on the gtab.
EDIT: scratch that - I have it working now on N1.
Click to expand...
Click to collapse
I'm on CyanogenMod 6.1.1. I get the tilt to work have you been able to get the rotate to work??
i know on the gtab if your two fingers are too close together, multitouch will crap out. try putting some distance between the two fingers or try one finger each hand.
landykos said:
I'm on CyanogenMod 6.1.1. I get the tilt to work have you been able to get the rotate to work??
Click to expand...
Click to collapse
I'm on miuimod and get tilt but no rotate.
the 3d stuff is just plain missing for our tabs... the new features screen didn't mention the same items as my evo did when i updated... something's different for this version... not cool. perhaps having to do with MDPI gapps?
myndwire said:
the 3d stuff is just plain missing for our tabs... the new features screen didn't mention the same items as my evo did when i updated... something's different for this version... not cool. perhaps having to do with MDPI gapps?
Click to expand...
Click to collapse
I noticed that too. My G2 had a list of about 4 things. The gtab had 2?
Sent from my T-Mobile G2 using XDA App
Nospin said:
I noticed that too. My G2 had a list of about 4 things. The gtab had 2?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
exactly what i had happen -- there's definitely stuff missing. the only options i recall seeing on the tab were the offline stuff and 1 other trivial feature... no 3d or multi-touch... not cool :-\ you'd think they'd just delay the update; this makes me think it's not going to happen, and that the moto tablet is HDPI
the fact that the tutorial/tips doesnt show us the 3d tilt/2 finger drag makes me think the software is limiting what were allowed, not the hardware. If it said we COULD do it, but we physically couldnt trigger it, then id be worried.
lame. the only thing we got thats new is the offline caching. rotating maps doesn't work, 3D doesn't work, vector based zooming doesn't work.
i even tried sideloading it from my droid onto the tab but still got the same result. its definitely the software disabling it. i wonder if this is what google is planning on doing going forward with tablets that aren't using 3G. what a slap in the face.
that's even more screwed up... if you pulled the apk from your phone that it works on, then it's almost definitely the tab's os doing it... perhaps its unhappy with whatever model / make device our tabs 'tell google' we're using? not sure... there's also the possibility that whatever prevents the new features from working isn't part of the actual apk, rather another file from maps (it's got files in a couple of places if i recall, including a framework directory, etc). those files could be to blame..
either way, i'm terribly disappointed right now... to top it off my evo just randomly stopped charging unless i jiggle the crap out of the power connector. i've even tried 3 different microusb cables, and there's not 1 sign of physical damage to the interface on the phone... this is bs... sorry, really needed to vent a bit...
If you go to about it ids the platform as android-VEGAn v something or other but my EVO shows HTC-Supersonic Pc36100. Somehow we need to spoof it.
Definitely seems like google maps is reading something on our tablet and deeming it not worthy of all the features. Makes me optimistic that a bit of hackery might get this thing working. Just need to get somebody who knows their way around the code to maybe modify the apk.
Sent from my T-Mobile G2 using XDA App
rcgabriel said:
There is no doubt that multitouch is currently very broken on the G Tablet. Single touch is very sensitive, but as soon as you try to detect even 2 fingers simultaneously, the driver seems to have some major issues, glitching back and forth unless you lean all out on the screen. It's like it's normalizing the magnitude of the two signals improperly. And there seems to be no "true multitouch" capability with this sensor, because I've been unable to get it to sense three simultaneous touches at all. I've tried two of the Multitouch testing apps in Market, with the same results.
So definitely there's the need for updated touchscreen drivers to fix pinch and zoom, etc. , but I'm not clear whether or not the touch sensors are hardware-crippled like the Nexus One, or whether the improved drivers can fix this better than I suspect.
Edit: See my post here: http://forum.xda-developers.com/showthread.php?t=863741&page=8 I've managed to fix my terrible multitouch/pinch-to-zoom. It looks like it was a calibration issue, and now that I got the TSCalibration executable working properly, pinch-to-zoom works much better. However, the limitation on multitouch to two simultaneous touches seems to be baked into the drivers or the hardware and can't be fixed by calibration. So no "true multitouch" yet with the G Tablet.
Click to expand...
Click to collapse
There's a hack out there which I plan to add to the next TnT Lite / VEGAn builds. Allows those of you without a microSD card to calibrate your device, just by adding a file to the root of /sdcard. I'm thinking of maybe a supplement for TnT Lite, but I also want to see what VS is planning to do in the next few days.
Can someone post the apk? I can't find it on the market have the previous version running, and did the market fix a few times!
Thanks
Related
youtube (.com) watch?v=1P9vMAvvkGY
This issue can be replicated by putting both finger on the screen, and lift one finger off the screen while keeping the other finger absolutely still. If the finger still remains on the screen moves, the phantom touch point will go away.
The kinds of problems the above issue is causing:
1. Most action/platform Emulator games on EVO is nearly impossible to play.
2. When typing too fast on the EVO keyboard, very rarely the keys will stick.
3. Driving games that require 2 finger to play will sometime jam when both finger are touching the screen. (holding break and gas at the same time when cornering)
While i haven't done much low level programing (Java guy myself), this seem to me like a driver issue, in which either the driver is not sending untouch interrupt to the OS. Or the OS is somehow not recognizing an untouch event when there are more then 1 contact point on the screen.
If it is either of the above cause, I think it should be a relatively easy fix if we can get hold of the source code for the driver/OS. However there is another possibility, in which HTC is using a cheap touch screen hardware in which the hardware itself is not design for multitouch, but rather the driver/os itself is doing extra calculation to approximate multitouch (Similar issue to Nexus One?), then this might be an unfix-able issue. I really hope this is not the root cause, but then again I am fairly new to using HTC hardware, and don't know their track history when it come to the quality of their hardware.
Does anyone have the source code to the driver or the OS snippet that interpret the hardware interrupts? I am interested in taking a shot at it and see if I can leverage my programing skill to fix the problem.
i dont have that problem at all
Hardware 3 epson screen
Are you sure? I posted the same problem on AndroidForums.com evo forum and multiple people reported able to reproduce the same issue.
It is not exactly easy to reproduce the issue when you are deliberately trying, might take a couple try, if will, can you please try again? I currently have the version 002 of the EVO. If the problem is indeed fixed on the version 003 of the EVO, I could just go to the nearest sprint store and trade the phone.
i have 002 and i dont have that problem either..i tried with the multitouch and with gba emulator..mines is fine
gordon1hd1 said:
Are you sure? I posted the same problem on AndroidForums.com evo forum and multiple people reported able to reproduce the same issue.
It is not exactly easy to reproduce the issue when you are deliberately trying, might take a couple try, if will, can you please try again? I currently have the version 002 of the EVO. If the problem is indeed fixed on the version 003 of the EVO, I could just go to the nearest sprint store and trade the phone.
Click to expand...
Click to collapse
I see the issue on an 003 device with a Novatec screen.
EDIT: But then how often will you really notice this? I mean unless you have freakishly steady robot hands, your hands will move a tiny bit and it will clear. If you move so much as one pixel, it clears.
EDIT 2: I can also replicate this on my Droid & Nexus. Thats just how it works in Android it seems. It's not exactly a big deal IMO
Eh, confirmed but i dont think its much of an issue, as soon as you move the other finger a single pixel(which is ridiculously easy) it will go away. I was able to hold it for about 5 seconds before it went away.
gordon1hd1 said:
youtube (.com) watch?v=1P9vMAvvkGY
Does anyone have the source code to the driver or the OS snippet that interpret the hardware interrupts? I am interested in taking a shot at it and see if I can leverage my programing skill to fix the problem.
Click to expand...
Click to collapse
two hardwrae revisions of the phone rev 2 and rev 3. i think both of them use the same touch panel.
booting into the bootloader will show - mine is rev 2 - atmel224_16ab
the source code is in toast's kernel!
http://forum.xda-developers.com/showthread.php?t=686240
Geniusdog254 said:
I see the issue on an 003 device with a Novatec screen.
EDIT: But then how often will you really notice this? I mean unless you have freakishly steady robot hands, your hands will move a tiny bit and it will clear. If you move so much as one pixel, it clears.
EDIT 2: I can also replicate this on my Droid & Nexus. Thats just how it works in Android it seems. It's not exactly a big deal IMO
Click to expand...
Click to collapse
It is interesting that you can replicate the issue on the Droid, I had the Droid before this Evo, and never seem this issue when I was play zelda on Sneoid, but this issue became very apparent when I play zelda on the Evo. I am not sure if it is because of the bigger screen or maybe just different batch of the Droid, but never the less, this issue made playing Zelda, S.Mario, and Kirby on the Evo very difficult for me. I still hope to take a stab at fixing the code if all possible.
PS: I also used to have the iPhone 3GS with Snes emulator on it, and never ran into this issue either, maybe this is Android specific?
I think the bigger issue is not being to have more than 3 inputs. The touch sensor in our phones is evidently capable of a large number, with Android itself capable of 3. Only two inputs make games like Super Mario Mart impossible to really play.
Not really helpful, but I know exactly what you're talking about. I have noticed it quite a bit playing first person shooters where you constantly have two fingers on the screen. Good luck looking for a fix.
Ill post a video tomm on mine I have no problems playing NOVA or anything including super mario kart on the emulators maybe im just lucky?
You can hold left, b, and l/r at the same time in snesoid?
Android sees three? I can only get stuff to show two.
|Jason8| said:
Android sees three? I can only get stuff to show two.
Click to expand...
Click to collapse
you can cheat and use 2 touch button and a physical button like the volume control. I had it up to 4 button on my Droid playing megaman soccer. But somehow on my Evo it is having trouble with 2 touch button
gordon1hd1 said:
you can cheat and use 2 touch button and a physical button like the volume control. I had it up to 4 button on my Droid playing megaman soccer. But somehow on my Evo it is having trouble with 2 touch button
Click to expand...
Click to collapse
Sure, that way, but as far as on-screen stuff, I can only see two touch points at a time.
I tested out a demo Droid at a Verizon store this morning, and was not able to reproduce the issue. Beside Geniusdog254 can anyone else verify this issue for their Droid or Nexus One?
gordon1hd1 said:
I tested out a demo Droid at a Verizon store this morning, and was not able to reproduce the issue. Beside Geniusdog254 can anyone else verify this issue for their Droid or Nexus One?
Click to expand...
Click to collapse
you'll prob get a higher volume and more accurate set of replies posting that question a droid or nexus one forum/board as opposed to the EVO 4G Development board ...
did the links i gave to the kernel source help at all in your research on the evo "multi touch issue" in this threads topic?
joeykrim said:
you'll prob get a higher volume and more accurate set of replies posting that question a droid or nexus one forum/board as opposed to the EVO 4G Development board ...
did the links i gave to the kernel source help at all in your research on the evo "multi touch issue" in this threads topic?
Click to expand...
Click to collapse
I downloaded, but haven't had a chance to loaded up in Eclipse yet, been too busy at work
Using "Multitouch Vis Test", I can get the Evo to do it. Using Multitouch Visualizer 2, There is not a phantom touch. That makes me think it is a software issue rather than a Evo issue. How does MV2 know to respond to the lifted finger unless the Evo is reporting properly? The original MV seems to fall asleep when I slowly lift a finger.
I got the MLB At Bat 2011 app working for non supported devices since so many devices aren't supported that clearly can run it.
YOU MUST HAVE A MLB.TV SUBSCRIPTION TO GET THE GAMES!!
You also need to buy the At Bat 2011 app.
I have a nook color, but should work for any device.
I changed the build.prop to contain the fallowing:
ro.product.model=SCH-I800
ro.product.brand=verizon
ro.product.name=SCH-I800
ro.product.device=SCH-I800
ro.product.board=SCH-I800
ro.build.fingerprint=verizon/SCH-I800/SCH-I800/SCH-I800:2.2/FROYO/EC02:user/release-keys
rebooted and worked. Should be able to chose any supported device and it will work. This is from the verizon galaxy tab.
I'm very much looking forward to trying this today.
Is there some sort of shortcut that could be made so we don't have to manually edit things every time?
EDIT: it's working! Though the supposed "HD" is far from it, and this is streaming over wi-fi.
I will be checking this out with today's free game of the day!
Now, I just need an easy way to switch the build.prop to watch the games.
the build.fingerprint isn't needed to be changed, works without it. Got it working on my nook color, pretty nice. Need to OC it and have a good fast connetion. Still not near HD though.
Good to know about the fingerprint.
Streaming is working great on my Captivate. Connected on wifi, close to HD after about 30 seconds, but if the connection gets bogged down, the picture loses quality fast.
Nice to have it working, clunky as it is...
I find I need a knead perfect 3G or strong wifi to get decent streaming on my droid2 and nook.
Sent from my SCH-I800 using Tapatalk
Will changing these settings have any unintended consequences for other apps or the operation of the phone in general? I have a Galaxy S but don't want to stuff anything up just for MLB At Bat.
nm, build.prop is a system file duh?
Congrats on getting this working, jkabaseball.
Are people getting the streaming working on CM7 Stable? I see that Nightly 37 was suggested before Stable came out. I'm on Stable now, and seeing the option, but only getting the white screen. I'm willing to try switching to 37, but it seems like there'd be no reason to do so, given that it's an older version. (Unless something was taken out before the stable release preventing this from working.)
Doesn't work on my nook with cm7. I even copied the signature.....yes I have sub also.
Cm7 installed on the Emmy
Sigh I had high hopes
I have been successful on cm7 stable on my HTC dhd. On a side note, anyone find a workaround to play blackout games?
SpiffyRob said:
Congrats on getting this working, jkabaseball.
Are people getting the streaming working on CM7 Stable? I see that Nightly 37 was suggested before Stable came out. I'm on Stable now, and seeing the option, but only getting the white screen. I'm willing to try switching to 37, but it seems like there'd be no reason to do so, given that it's an older version. (Unless something was taken out before the stable release preventing this from working.)
Click to expand...
Click to collapse
Sent from my SCH-I800 using Tapatalk
Just wanted to follow up, and say a HUGE thanks for the info. I modified the build.prop file like you said, and now I can watch the Cardinals anywhere on my Samsung Mesmerize. Just a note it works great even though I am running Voodoo. The only thing that is different is my swype keyboard won't work anymore, says that it was not meant to be used for my device, oh well, I love Cardinals baseball more than swype so who cares!! Thanks again for the info!!
mrfurion said:
Will changing these settings have any unintended consequences for other apps or the operation of the phone in general? I have a Galaxy S but don't want to stuff anything up just for MLB At Bat.
Click to expand...
Click to collapse
Other apps that require a specific build.prop might not work. I have a Captivate and the preinstalled Swype does not work while I an using the modified build.prop.
I duplicated my build.prop, renamed the duplicate build.prop.mlb and made the changes. Then when I want to watch baseball, I rename the real build.prop to build.prop.real and rename build.prop.mlb to build.prop and then reboot the phone. I switch it back when I'm done.
plasticdarlow said:
I have been successful on cm7 stable on my HTC dhd. On a side note, anyone find a workaround to play blackout games?
Sent from my SCH-I800 using Tapatalk
Click to expand...
Click to collapse
Enabling Mock Locations and an application that lets you spoof your location would probably work. Haven't tried it though.
lactardjosh said:
Enabling Mock Locations and an application that lets you spoof your location would probably work. Haven't tried it though.
Click to expand...
Click to collapse
Tried that. It works for the NHL app, but NOT for MLB at bat
chinly43 said:
I'm very much looking forward to trying this today.
Is there some sort of shortcut that could be made so we don't have to manually edit things every time?
EDIT: it's working! Though the supposed "HD" is far from it, and this is streaming over wi-fi.
Click to expand...
Click to collapse
I have the sgs4G not working for me and yes I have subscription. Any help? Does this work on tmo. Using the Verizon settings?
Doesn't work on the Xoom either.
jkabaseball: youre awesome!!! Works like a dream on my Cappy!! Not quite in HD, but still so awesome. Now to figure out, like above posts mention, how to navigate around the locale so I can see my Giants games!!! I tried the app for changing locale, but i believe its a bit more involved than just fooling App Market. Thanks a ton jkabaseball
kamasi36 said:
I have the sgs4G not working for me and yes I have subscription. Any help? Does this work on tmo. Using the Verizon settings?
Click to expand...
Click to collapse
This might be too basic to ask, but - do you also have the paid app, rather than the free one? And is the sgs4g flash-capable? Those are also prereqs, in addition to the subscription.
The build.prop changes I posted is for the galaxy tab on Verizon. You should be able to use another device like droid2 build.prop and Skype should work as well. On my nook I thought the galaxy tab would be best.
Working on spoofing location. It mint be a little harder. MLB is pretty good at determining your location even through a VPN. I'm not sure if they are using gps location, which would be easy to spoof, or the network location where the stream is going to. I haven't got it to work on my pc yet, but will keep on working on android.
Just wondering what people's experiences are so far with the physicalilty of the device. I really like the way it feels and fits in my hand, with the keyboard open and in landscape mode. Also love the feel of the keyboard, tho i might change a couple things in the key layout.
The one thing i'm seeing is my keys are already getting quite scuffed, perhaps from being pressed with my thumbnails? A few of the printed letters are wearing down and i'm afraid i won't be able to see them after not too much longer! Is anyone else seeing this?
Other than that, the overall build quality is ok, maybe a tad cheap-ish(?), but i like it. In some ways it could be my favorite qwerty phone yet.
Physically the phone is solid. Mentally.. not so much.
Agreed on the mental instability bit.
The things my Photon would do, but not limited to:
1. Notifications go into the ether (don't pop up in notification bar)
2. Apps that go fullscreen will sometimes cause the nav/status bar to black out
3. Vibrate completely at random
4. Take 5 minutes to unlock
5. Regularly see my SD card as "corrupted"
6. Autopunctuation fails at random
And that's all I can remember off the top of my head. It seems to have some real crazy quirks. Hoping CM10 makes it better.
Xodium said:
5. Regularly see my SD card as "corrupted"
Click to expand...
Click to collapse
...YES...and now is my 32GB SD definitely dead
For me is this problem only with 32GB cards.16GB works fine.
I forgot to mention, the touchscreen seems a bit wonky to me.... Not very responsive, gotta press a few times sometimes to open an app, and it sorta freaks out sometimes and doesn't swipe from side to side and opens stuff i didn't mean to open. I had a Moto Cliq 2 and had similar touchscreen issues.
I think CM10 would be great on this device, we oughta get cracking on that build. I don't know for sure, but I'd be surprised if we ever got official support from the CM team.
yogi2010 said:
I think CM10 would be great on this device, we oughta get cracking on that build.
Click to expand...
Click to collapse
Done.
Now to get it functional...
I still think we should focus on CM9, then worry about getting 10. But that's just me...
arrrghhh said:
Done.
Now to get it functional...
I still think we should focus on CM9, then worry about getting 10. But that's just me...
Click to expand...
Click to collapse
Sounds good to me, we do have ICS source, right? How come the source download is only a few MB tho? Did they just release the drivers, and you gotta add them in to the rest of the code?
yogi2010 said:
Sounds good to me, we do have ICS source, right? How come the source download is only a few MB tho? Did they just release the drivers, and you gotta add them in to the rest of the code?
Click to expand...
Click to collapse
Moto released the kernel source, they are under no obligation to release userland source.
I have gotten CM9 booting, but not much else. Interloper didn't have the device and was working on CM10... it never booted. I'm hoping he'll make some progress with the device in his hands.
arrrghhh said:
Moto released the kernel source, they are under no obligation to release userland source.
I have gotten CM9 booting, but not much else. Interloper didn't have the device and was working on CM10... it never booted. I'm hoping he'll make some progress with the device in his hands.
Click to expand...
Click to collapse
For fun i have built an HTC kernel or two, and the source downloads were always almost 100 MB tho, so i was confused when i looked at our source, haha. I'm not real experienced tho.
From what i hear, getting it to boot is a huge part of it, so that's great. Hopefully we'll get further along soon!
yogi2010 said:
For fun i have built an HTC kernel or two, and the source downloads were always almost 100 MB tho, so i was confused when i looked at our source, haha. I'm not real experienced tho.
From what i hear, getting it to boot is a huge part of it, so that's great. Hopefully we'll get further along soon!
Click to expand...
Click to collapse
The actual kernel source is something like 2gb uncompressed on my machine...
arrrghhh said:
The actual kernel source is something like 2gb uncompressed on my machine...
Click to expand...
Click to collapse
Ah yes, i see it now lol. Had gone to the wrong link before.
CornholioGSM said:
...YES...and now is my 32GB SD definitely dead
For me is this problem only with 32GB cards.16GB works fine.
Click to expand...
Click to collapse
64GB cards do this as well.
I have a fix: Go to a Mac (haven't tested this on PC) and have Disk Utility repair the SD card. Twice for good measure. Usually clears it right up. It's annoying when it happens and I'm nowhere near my computer, though.
arrrghhh said:
Moto released the kernel source, they are under no obligation to release userland source.
I have gotten CM9 booting, but not much else. Interloper didn't have the device and was working on CM10... it never booted. I'm hoping he'll make some progress with the device in his hands.
Click to expand...
Click to collapse
They have a 3 month obligation before they violate the GPL for every kernel/software update.
The phone has some issues but so did my evo shift to a certain extent which is why I was re-flashing ROMS all the time. Go to any phone forum and there are always bugs
- I only have the weird touchscreen problems, that someone mentioned above, only when the phone is charging. A little weird. if I overtax the phone i can cause some hangups. I blame Android more than the touchscreen or processor.
- I'm in and out of cell service alot because of the location of my job. I've been blaming that for the fact that notifications come at weird times and out of order. When I'm in service all the time, notifications seem pretty solid.
- The physical keyboard seems to double-type occasionally, but overall I'm ok with its performance. Keyboard slide out mechanism is good, where on my evo shift I thought was a bit too..."loose"?
- I have the wifi drop problem that someone mentioned in another thread. I blame software on that as well. Maybe the next patch will get it right. These companies are just trying to push phones out the door these days. Remember when video games couldn't be updated over internet and how solid they were out the box? Nowadays, everything needs OTA patches at some point. Shame, but I digress.
- camera could be WAY better (auto-focus, poor lighting scenarios). This may be my biggest complaint, because this should be solid out the box given how far phone cameras have come. How long have phones had cameras now? I had a phone camera in 04.
I could give a long list of good physical and software points. Overall I'm really happy. JB would make me happier, but ICS on the Q is pretty darn good.
I have a few scrapes/scratches on my spacebar from sliding the phone open and closed so often, but that's it.
Also, that little oval/dot thing on the left side of the keyboard face of the phone to the left of the number 1, what is that?
Sent from my GT-N8013 using Tapatalk 2
dpwhitty11 said:
Also, that little oval/dot thing on the left side of the keyboard face of the phone to the left of the number 1, what is that?
Click to expand...
Click to collapse
Caps lock indicator.
cmags said:
Caps lock indicator.
Click to expand...
Click to collapse
Is it supposed to light up or something?
Sent from my XT897 using Tapatalk 2
yes bro..it supposed to light on when we activate caps lock key..
Sent from my XT897 using xda premium
cloud_9 said:
yes bro..it supposed to light on when we activate caps lock key..
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Oh. Mine doesn't. Oh well.
Sent from my GT-N8013 using Tapatalk 2
Ever since I updated, my keyboard backlight is no longer "automatic". Have to set it always on because it stops turning on when set on automatic.
Physically, phone is solid.
I hope this is the right place to post this. I have owned and really loved my N7000 for several months now. As an ex-Palm user, the SPen stylus was a huge draw. I began to note, however, that over time the accuracy and the location of the floating pointer of my SPen began to drift. I searched and found many people complaining about this and saw multiple posts of "fixes" to try. I even found a paid app in the marketplace that claims to deal with this. I recalled that on my various Palm devices I occasionally had to re-run the touchscreen calibration routine and began to look for one of these thinking it should be built-in. But I could not find one that actually seemed to help.
After more digging I discovered a technique that seemed to work. Simply changing the SPen's dominant hand setting back and forth from my setting of Left to Right and back to Left again made a big difference. But doing so was inconvenient and really had to be done with some regularity to keep things really perfect. After more searching, I discovered how changing the SPen device's dominant hand (not the actual preference setting but seemingly communicating directly with the device) could be triggered by a script. However, this requires ROOT and some way to launch the script. I tired this and found it worked well.
So I decided to wrap this technique up in a little app - my first real Android app. It also requires ROOT and uses much the same technique as the script. You simply tap the app's icon and the quick change is performed - there is no UI. The app determines your current dominant hand setting from the preference file and then tells the device to switch to the opposite hand and back again. Nothing too big here but it seems to work for me (as well as some others who posted this "fix" idea).
I would think it good for this to be scheduled to run regularly (maybe once every .5 - 1 hour) so one never has to be bothered. But for now I haven't figured out how to do this and my guess is there are free apps available that can run this on a schedule. I was able to find such a program to run the script in this manner.
But I have not tested this on any but my own N7000. Will it work for others? Will it work on US carrier's versions of the Note? Will it work on the Note II or the new tablet that has an SPen? I am not sure and am hoping others out there will try this and let me know their findings and suggestions.
Thanks
EDIT: Please note that I have moved the APK file to the Google Play Store. Here is the link.
Wow! Thanks for this tool. :thumbup:
Sent from my GT-N7000 using xda premium
good start
whitedavidp said:
I would think it good for this to be scheduled to run regularly (maybe once every .5 - 1 hour) so one never has to be bothered. But for now I haven't figured out how to do this and my guess is there are free apps available that can run this on a schedule. I was able to find such a program to run the script in this manner.
Thanks
Click to expand...
Click to collapse
For those that have it, Tasker should allow one to schedule this activity as needed. For those that don't, I recommend looking into it.
you should be able to get it to run as a service,
http://developer.android.com/reference/android/app/Service.html
Nice bro.. But I think this goes in the themes and apps section.. Guess you gotta ask a moderator to move your thread there
Tapatalking on my n7000
undrwater said:
For those that have it, Tasker should allow one to schedule this activity as needed. For those that don't, I recommend looking into it.
Click to expand...
Click to collapse
Also, I can no report that I have this running on a schedule using the Scheduling function of the excellent SManager app from the marketplace. I have been using that to run the onandroid script automatically to perform nightly backups. It can run executable programs as well as scripts. To run the .apk you use the android activity manager program (/system/bin/am) using the following command line:
/system/bin/am start -n com.whitedavidp.reset.spen/.MainActivity
Cool!
fards said:
you should be able to get it to run as a service,
http://developer.android.com/reference/android/app/Service.html
Click to expand...
Click to collapse
Thanks, I will look into that. I am so new to this I kept things as simple as possible. A service would seem the right way to handle built-in scheduling. But I would also want to retain the tapping of the app icon so it can be run on command in case the user has set the interval too large and wants to reset things right now.
thats a nice one
required
thanks
Feedback on GB or Jelly Bean?
I should have mentioned in my original post that I have tested this only on Stock Touchwiz ICS 4.0.4 using Hydracore 4.3 kernel. It would be helpful to know if this works and does its job well on other platforms. Lacking adequate hardware, I can think of no way to ascertain this except asking others to try and give me feedback. Other suggestions are appreciated. Thanks
Thank you for this app! I'm using an SGH-T889 Note II and the app worked perfectly. It could just be my imagination, but it really seems like my stylus is way more accurate, so I'm assuming it worked! If anything the app installed and ran fine (it stated successful so I'm assuming it did), and I'm using a US version of Note II on Tmobile with a custom rom (Jedi X5). Just thought I'd let ya know in case you still needed to know if it worked on a different phone. Thanks again!
Sent from my 1992 Motorola StarTAC
jeep447 said:
Thank you for this app! I'm using an SGH-T889 Note II and the app worked perfectly. It could just be my imagination, but it really seems like my stylus is way more accurate, so I'm assuming it worked! If anything the app installed and ran fine (it stated successful so I'm assuming it did), and I'm using a US version of Note II on Tmobile with a custom rom (Jedi X5). Just thought I'd let ya know in case you still needed to know if it worked on a different phone. Thanks again!
Sent from my 1992 Motorola StarTAC
Click to expand...
Click to collapse
Thanks for your info. I DO want to know if the app works on other Note I and II phones. It would be great to know if it works on the new tablets that SPens as well.
whitedavidp said:
Thanks for your info. I DO want to know if the app works on other Note I and II phones. It would be great to know if it works on the new tablets that SPens as well.
Click to expand...
Click to collapse
Ok that's cool I'm glad I could help (even though it's miniscule lol). I can also say now that it's not just my imagination, because it actually does work. This morning I had some time to kill before a meeting so I was doodling it up. After a while I noticed the S Pen accuracy was really starting to slip, so I ran your app again and the difference was amazing! I'm really surprised that Samsung didn't intergrate an app like this, because you'd figure they'd recognize the precision drops over time by now. Anyway I'm definitely glad I found this man and once again I really appreciate your hard work!
Sent from my 1992 Motorola StarTAC
jeep447 said:
Ok that's cool I'm glad I could help (even though it's miniscule lol). I can also say now that it's not just my imagination, because it actually does work. This morning I had some time to kill before a meeting so I was doodling it up. After a while I noticed the S Pen accuracy was really starting to slip, so I ran your app again and the difference was amazing! I'm really surprised that Samsung didn't intergrate an app like this, because you'd figure they'd recognize the precision drops over time by now. Anyway I'm definitely glad I found this man and once again I really appreciate your hard work!
Sent from my 1992 Motorola StarTAC
Click to expand...
Click to collapse
Thanks again for the feedback. I guess I will post this thing on the Play store so others may find it more easily. Maybe I will follow-up with a "Pro" version that permits periodic, scheduled running of the app and allows for the notifications to be turned off. Cheers!
whitedavidp said:
Thanks again for the feedback. I guess I will post this thing on the Play store so others may find it more easily. Maybe I will follow-up with a "Pro" version that permits periodic, scheduled running of the app and allows for the notifications to be turned off. Cheers!
Click to expand...
Click to collapse
That sounds great man I'll definitely keep an eye out for it! Thanks again!
Sent from my 1992 Motorola StarTAC
hi
this app is a great idea! please update it with schechule... but i still have problems with landscape mode... there it's always off...
a fix for this would be soooo nice!
thx for youre work!
App runs on paranoid Android.
Not sure about tw roms but on cm/pa and aokp roms pointer icon is always slightly towards top left of screen. If phone is rotated, rather than point to the 'new' top left it is still pointing at the volume up button.
To fix landscape we need someone to work out how to convince the input that the screen is 1280 x 800 instead of 800 x 1280, this (I think) means the spen input would need to recalibrate every time your screen rotates eating batteries for breakfast.
Right handed use landscape where bottom of phone moves right (anticlockwise) you can still see it its just off. If you swing bottom of phone left pointer hides behind spen
Sent from my GT-N7000
phasA said:
hi
this app is a great idea! please update it with schechule... but i still have problems with landscape mode... there it's always off...
a fix for this would be soooo nice!
thx for youre work!
Click to expand...
Click to collapse
Thanks for the info and response. Can you please describe: (a) does my app help when in portrait mode? and (b) can you describe how the pointer is off when you are in landscape (which direction and by how much)? and (c) when you return to portrait mode does the pointer seem right?
I have a more complete version offering scheduling and other convenience features coming and will put both on the marketplace once I figure out how to do that.
PS - I think I read somewhere that toggling auto-rotate on/off may help "fix" the S-Pen and I wonder if this will work for you?
Cheers!
sam.crowther said:
App runs on paranoid Android.
Not sure about tw roms but on cm/pa and aokp roms pointer icon is always slightly towards top left of screen. If phone is rotated, rather than point to the 'new' top left it is still pointing at the volume up button.
To fix landscape we need someone to work out how to convince the input that the screen is 1280 x 800 instead of 800 x 1280, this (I think) means the spen input would need to recalibrate every time your screen rotates eating batteries for breakfast.
Right handed use landscape where bottom of phone moves right (anticlockwise) you can still see it its just off. If you swing bottom of phone left pointer hides behind spen
Sent from my GT-N7000
Click to expand...
Click to collapse
Thanks for your info. Good to know that the app doesn't crash on Paranoid. My phone is TW ICS 4.0.4 with Hydracore 4.3 kernel. On my phone I do not see the issue with landscape mode that you and phasA describe. I can say that I really wasn't liking the way auto-rotate was working on my phone (sometimes just too sensitive). So I have installed this app which basically makes me confirm that I want to rotate. Perhaps this has something to do with my I am not seeing this issue?
I still didnt get the use of this app, sorry i am not at all rude but how can changing dominant hands reset the pointer settings. I mean what does it has to do with resetting the pen settings???
Sent from my GT-N7000 using xda app-developers app
I saw the phone's announcement, and in my opinion they should never let Charlie Chang present a phones again.
It was one of the most awkward announcements I watched. He looked like he is going to explode, and every feature he presented it looked like he is praying to god that it will work.
but that's one thing.
during the presentation he tried to activate google assistant through the Edge Sense, and it didn't work, then he tried again and it failed again, then he made the most awkward "ooopss" he could make, while trying again couple of times until he continued presenting the google assistant without mentioning or talking about the incident (which is understandable but still troubling).
the weirdest thing is that I can't find any review or post that talks about it, I thought the press will destroy Htc for this screw up.
for me it's really troubling, this gimmick can be nice, but it's the first time we see something like this on any phone and I have doubts about its quality.
what do you think?
Meh, to say that I've never had stuff like that happen on any phone I've owned would be a huge understatement.
Had a unit in hand to test it one week ahead of the official announcement. On my test unit the Edge Sense worked really good, after getting accustomed after the first 30 Minutes and configuring it to my pressure sensitivity in settings.
Sent from my htc_pmeuhl using XDA Labs
Jeah some other people already tried Edge Sense and said something similar like @5m4r7ph0n36uru said. Its working okay or good - better then many expected. But for me its just a nice to have. Lets see how much they can improve this feature with future Software updates. Maybe its just a feature that ends up being a public prototype which would also be okay. If this feature is any good they will probably improve the hardware behind it in a future device.
I mean its the same with the fingerprint scanners, the first and even second version in the iPhone was quite bad in my opinion. The one in the 6s is good, but the ones before where too slow and the failure rate was too high (for me).
liorderei said:
I saw the phone's announcement, and in my opinion they should never let Charlie Chang present a phones again.
It was one of the most awkward announcements I watched. He looked like he is going to explode, and every feature he presented it looked like he is praying to god that it will work.
but that's one thing.
during the presentation he tried to activate google assistant through the Edge Sense, and it didn't work, then he tried again and it failed again, then he made the most awkward "ooopss" he could make, while trying again couple of times until he continued presenting the google assistant without mentioning or talking about the incident (which is understandable but still troubling).
the weirdest thing is that I can't find any review or post that talks about it, I thought the press will destroy Htc for this screw up.
for me it's really troubling, this gimmick can be nice, but it's the first time we see something like this on any phone and I have doubts about its quality.
what do you think?
Click to expand...
Click to collapse
I wouldn't read too much into it - could be nerves, could be the phone wasn't set up properly for him, old software, etc.
Microsoft launched a version of windows (I think it might have been Win98) and during the launch they encountered the Blue Screen Of Death... it didn't seem to have much impact on their future!
I'm not too worried. If it doesn't work well I will just disable it. The phone is still nice.
Entrail said:
Jeah some other people already tried Edge Sense and said something similar like @5m4r7ph0n36uru said. Its working okay or good - better then many expected. But for me its just a nice to have. Lets see how much they can improve this feature with future Software updates. Maybe its just a feature that ends up being a public prototype which would also be okay. If this feature is any good they will probably improve the hardware behind it in a future device.
I mean its the same with the fingerprint scanners, the first and even second version in the iPhone was quite bad in my opinion. The one in the 6s is good, but the ones before where too slow and the failure rate was too high (for me).
Click to expand...
Click to collapse
They will update it. As HTC told in the same briefing, they are already planing to implement Double-Tab as a possibility to take further actions with Edge Sense, though they couldn't tell the date at this time but only that it is on the list. So I guess they are definitely planing to implement more gestures by such a step making short press, long press and double press available. With two different force settings, this would give us six gestures in total to configure for separate actions.
Something further is App based actions that'll be implemented to change the action resulting from a short press depending on the App you're using.
Sent from my htc_pmeuhl using XDA Labs
I saw reviews. it works pretty well.
5m4r7ph0n36uru said:
They will update it. As HTC told in the same briefing, they are already planing to implement Double-Tab as a possibility to take further actions with Edge Sense, though they couldn't tell the date at this time but only that it is on the list. So I guess they are definitely planing to implement more gestures by such a step making short press, long press and double press available. With two different force settings, this would give us six gestures in total to configure for separate actions.
Something further is App based actions that'll be implemented to change the action resulting from a short press depending on the App you're using.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
I hope so and i am sure they will but all I'm saying is that the hardware will be limited like i said with the fingerprint or another example the pressure sensitivity from the surface pen. In the first iterations it only had 256 different steps now they have around 2000. (not sure about the exact numbers here )
My hope is not too big about this squeeze feature in the first iteration but i am curious and will give it a try.
liorderei said:
I saw the phone's announcement, and in my opinion they should never let Charlie Chang present a phones again.
It was one of the most awkward announcements I watched. He looked like he is going to explode, and every feature he presented it looked like he is praying to god that it will work.
but that's one thing.
during the presentation he tried to activate google assistant through the Edge Sense, and it didn't work, then he tried again and it failed again, then he made the most awkward "ooopss" he could make, while trying again couple of times until he continued presenting the google assistant without mentioning or talking about the incident (which is understandable but still troubling).
the weirdest thing is that I can't find any review or post that talks about it, I thought the press will destroy Htc for this screw up.
for me it's really troubling, this gimmick can be nice, but it's the first time we see something like this on any phone and I have doubts about its quality.
what do you think?
Click to expand...
Click to collapse
+1
I thought the same Totally agreed with you... But I'm still buying the phone.. I hope after 1-2 updates it will work better.
I am lucky I wasn't in his shoes. Very awkward indeed. His hands were shaking.
I don't think it will damage sales. And in a live event anything can happen.
I don't think it even had to do with edge sense TBH... I think it had to do with the assistant apps themselves and probably the internet connection within the venue.
Mine works well do far. I just need to remember about it. I've left it starting the camera and it's good.
Honestly, I was hoping the edge sense would have worked just as the early videos showed of a couple walking the street and navigating the app drawer with the edge. Maybe version 2. But that was sick!
Sent from my 2PS64 using Tapatalk
mbaseball3 said:
Honestly, I was hoping the edge sense would have worked just as the early videos showed of a couple walking the street and navigating the app drawer with the edge. Maybe version 2. But that was sick!
Click to expand...
Click to collapse
Can't say I've every been walking the street and needed to navigate the app draw. I have shortcuts for everything already. Actually only time I navigate the app draw is when I'm adding a shortcut lol. But I see what you saying. Maybe if they added volume up down or scrolling, but don't think that's how it works.
well... it would probably have worked better if she took them off..