Im having some issues with the view from my phone being really shaky. I already rooted it so is there anything that can be done to fix this issue? Or what is the cause of this?
The accelerometer values are too precise, some apps have a smoothing algorithm built in but not all of them otherwise it is a matter of tweaking a kernel value but I don't know how and I don't thin kanyone has looked into it yet
Related
I am not entirely sure, but it seems to me that I have lost some precision with the S-Pen after I updated to ICS. When I am writing I have a feeling that the drawn line is slightly off the "pencil point" then before, maybe only for a fraction of a millimeter which is affecting the text, it seems much worse now.
When I am writing something it seems a bit more "unnatural" then before.
The only calibration I have found so far is the left-right handed set-up and it is set-up correctly for me.
Anyone else notice this?
I too have noticed this, Although I cant compare it to GB because i flashed ICS within minutes of getting the Note.
I have googled for the calibration methods but none of them work, They all relate to turning on / off the auto rotation and tapping the pen in 4 corners.
Could really do with a proper screen calibration tool
My drawing is pretty pathetic at the best of times, but with this inaccuracy im getting bullied on Draw Something
There is app on Google Play Store with which you can off set Spen position on the screen. It's called Touchscreen tune. It's not free to make changes permanent but you can try it to see if it works for you.
So nothing for unrooted devices?
Has the JB update fixed this issue for those who have updated their firmware?
No, it hasn't fixed the issue however there is a program in google play that fixes it (albeit you have to pay for the full version). It is called touchscreentune (galaxy note) - you can change the offset of the tip and also change things like the sensitivity if the screen. I can confirm that it works on most XXLSZ ROMS with Philz (haven't checked it on pure samsung JB).
Hey all,
I've been poking around the web and XDA for a while, and I'm wondering now if anyone else has had some weird audio stammering/stuttering on their Ones? Initially, I thought it might be something wrong with my headphones (have had a bad history of wearing out the jacks, but after using four or five sets, I don't think that's the issue. It's also not an issue with streaming/buffering the content in Play Music-- it happens with local content as well as streamed, although I haven't seen it much in other apps, such as YouTube.
If anyone has any thoughts, I'd love to hear them-- this has been a very frustrating issue on an otherwise excellent phone. I'm running tbalden's kernel, and otherwise am stock/rooted (and no, I don't see anything about the issue in the kernel thread, aside from some people playing around with PureXAudio). Thanks much!
Rirere said:
Hey all,
I've been poking around the web and XDA for a while, and I'm wondering now if anyone else has had some weird audio stammering/stuttering on their Ones? Initially, I thought it might be something wrong with my headphones (have had a bad history of wearing out the jacks, but after using four or five sets, I don't think that's the issue. It's also not an issue with streaming/buffering the content in Play Music-- it happens with local content as well as streamed, although I haven't seen it much in other apps, such as YouTube.
If anyone has any thoughts, I'd love to hear them-- this has been a very frustrating issue on an otherwise excellent phone. I'm running tbalden's kernel, and otherwise am stock/rooted (and no, I don't see anything about the issue in the kernel thread, aside from some people playing around with PureXAudio). Thanks much!
Click to expand...
Click to collapse
I'd go back to the stock kernel anyway. The current kernel source has had several issues that HTC needs to fix (including missing portions) so it's really not advisable to use one. There's not much benefit to a custom kernel right now anyway.
Vincent Law said:
I'd go back to the stock kernel anyway. The current kernel source has had several issues that HTC needs to fix (including missing portions) so it's really not advisable to use one. There's not much benefit to a custom kernel right now anyway.
Click to expand...
Click to collapse
Nominally an option, the main issue is that I've become quite dependent on sweep2wake and logo2menu, but if it does become a bigger issue it's certainly a tradeoff I'll consider.
Rirere said:
Nominally an option, the main issue is that I've become quite dependent on sweep2wake and logo2menu, but if it does become a bigger issue it's certainly a tradeoff I'll consider.
Click to expand...
Click to collapse
I'd look into other solutions for those. sweep2wake actually eats quite a bit of power (it leaves the entire touch panel powered), and logo2menu can be replicated with other programs.
For example, what I do for powering the device on/off is using my flip cover combined with a Tasker profile that acts like the iPad smart cover, using the proximity sensor. Open = on, Close = off. Even works when turning the device over or putting it in the pocket.
Also, you can use apps like GMD GestureControl to enable menus with a simple gesture, combined with a basic rom modification to remove the soft menu button.
Vincent Law said:
I'd look into other solutions for those. sweep2wake actually eats quite a bit of power (it leaves the entire touch panel powered), and logo2menu can be replicated with other programs.
For example, what I do for powering the device on/off is using my flip cover combined with a Tasker profile that acts like the iPad smart cover, using the proximity sensor. Open = on, Close = off. Even works when turning the device over or putting it in the pocket.
Also, you can use apps like GMD GestureControl to enable menus with a simple gesture, combined with a basic rom modification to remove the soft menu button.
Click to expand...
Click to collapse
I've yet to have trouble with sweep2wake, actually-- it, along with PGM Nexus are compromises I'm willing to make for extra utility. I've actually never had very good luck with Tasker and a proximity sensor (I actually tried it again this morning with ill results), although the pocket trick does work reasonably well for me.
Personally, I can't stand GMD GestureControl on a phone, although it's a lifesaver on a tablet. In any event, I did try a restore to stock and I'm still having the issue (although it may be slightly less pronounced-- who knows!). Hopefully there may be a fix incoming from one side or the other.
Hello, I recently bought the "Google Cardboard" and I noticed that all apps I tried were shaking a lot (Even if I just leave the phone on the table). It seems to be an Gyroscope issue.
Noticed the same in Google Camera (360ยบ Picture Mode). It doesn't happen in Google Street View as it seems to apply some kind of filtering. Is there any fix for this?
I've been told that the Samsung Phones doesn't suffer from that kind of shaking
Is there any way to calibrate the Gyroscope? Or at least to apply some kind of shaking filter globally to all apps?
Can somebody please confirm if they have the same issue (And if this issue has been fixed on Android L)? [I'm on Android KitKat]
Greetings.
Remove
I have the same problem.
Interface of Google cardboard is very shaky.
Google camera's lens blur doesn't work for me; it says device moved too quickly whereas i didn't even move it a cm. (Kitkat)
Everyone should have this problem I think so.
I think the gyroscope is not calibrated correctly
Remove
ErixGamer said:
Nvm its all fixed. remove please.
Thank you,
Click to expand...
Click to collapse
Fixed? Where? In Android Lolipop?
I have Moto G 2014 European version so I still haven't received the Update.
Or is there some other fix? I'm very interested in this.
Okay that message was because a thought this was solved. Anyways it works on lollipop very well. Its very steady but if i try to hold steady it shakes a little. On KitKat my gyroscope reacted very sensitive (slightest movement even registers) So my suggestion is maybe use lollipop? or try this app: A thread about how to recalibrate the gyroscope sensor
Anways hope it works wish you much lucky
Greetz ErixGamer
I am using lollipop on my moto g 2014, and videos are still shaky!
RK_DROID said:
Interface of Google cardboard is very shaky.
Google camera's lens blur doesn't work for me; it says device moved too quickly whereas i didn't even move it a cm. (Kitkat)
Click to expand...
Click to collapse
I'm having the same problem. Mine was working, but I flashed a new ROM and it stopped. I deleted that ROM and went back to stock, but the problem is still there.
When I start moving left, the phone thinks I'm moving right and vice-versa. It hardly detects any movement, even if I do a full 360 rotation.
I am also unable to view VR photos in Google Cardboard correctly. This is really frustrating and I have no idea how to fix it.
Have you had any luck?
I found the same, infuriating problem in all the ROMs I tried.
I read in another thread (possibly another forum, I can't remember now) a post from a Moto dev who acknowledged the issue and stated they would fix it in the next update. I installed the latest 6.0 soak test and the first thing I checked was the gyro, which appears to have been fixed.
Google cardboard runs as smooth as butter, with no shaking or anything.
In CM13 devs have fixed the sensors also added some new ones.
gyroscope is working correctly on CM13 too
My Gyro has gone "bad". It fails the diagnostics test. If I do a factory reset it works for awhile and then stops working again. Which would seem to me that I have a software issue rather than hardware. Factory resets are a huge pain of course. I thought I would root it and put CM13 on it, but (thanks ATT) that seems about impossible. I am getting ready to buy a new phone but I really don't want to because this one has been pretty damn good. But not being able to watch videos or take photos in landscape is just too much of a drag. Can anyone assist me in digging in to the root of the issue?
I am fairly technical (system engineer) but not very familiar with AndroidOS. Can I see if my gyro driver is corrupt?
Thanks.
So this may sound crazy, but I've noticed recently that my Urbane runs great if I'm not wearing it, but the second I put it on on my arm it runs terribly. The screen will freeze and I'm lucky if I can get it out of ambient mode most of the time. Has anyone else experienced this? Any ideas on how to fix it?
My running theory is that it's something to do with the heart rate sensor, but I've disabled LG health and uninstalled Google Fit, and I'm not sure if there's any other apps that use it. I also seem to recall there being a setting to lock when taken off, but it's not enabled and I can't seem to find it anyway.
I'm on stock AW2.0. Bootloader is unlocked though from previous tinkering. I can try to get video of it later today if anyone is interested.
Hi,
that's a weird inssue. I had a similar one with my Urbane being responding slowly or not at all but I did not test how and if it works when I put it off. have you tried to install a boot.img from this thread? as your bootloader is alread unlocked it's just a matter of minutes to install a new boot.img.
After I installed the 4-core version my watch is much more responsive and runs really fast. Battery usage increased just a little (and really just a little) on my wach. From appr. 1.54%/hour to 1.75%/hour.