Hi all!
I have an x10 mini pro with MiniCM7 Pro v16 installed on it. My question is about the sensors (accelerometer, orientation).
I have an app that just simply shows the accelerometer x, y, z and the orientation sensor azimuth, pitch, roll on the phone's screen using TextView's. The problem is that after some minutes (3 ~) the sensors start lagging.
On v13 update's changelog there is a row: - fixed G-sensor. But for me it didn't fixed it.
My question is: anyone else noticed this? (or maybe I screw up something?)
Because I haven't seen posts about this issue in the MiniCM7 Pro's thread.
BTW the rom is awesome, I don't want to back to stock rom because of this issue, but it would be nice if it gets fixed sometime.
Thank you for your time.
It is possible that, you skipped any step, so better reflash the ROM.
But if the problem continues, ask the developer.
i m also facing the same problem in minicm7 pro v16...
i play games like hungry sharks and asphalt 5 .... the g-sensor is very unresponsive and slow. ...
but when i switched to sonystlye v10 .. this problem was very much fixed.!
but again i have to use minicm coz i didnt liked the contacts portion
I mentioned it briefly in another post and searched the forum - but found nothing.
I am talking about the Sweep Panorama mode of the Xperia-S camera. Not the '3D' versions, the 'normal' (2D) sweep panorama - the last icon in the first ('Shooting mode') menu. I tend to experience problems with it and am not sure if everyone has observed the same.
In Sweep Panorama mode, whatever direction of sweeping I choose, I tend to get error messages that either:
- I am sweeping too fast, or
- I am sweeping too slow, or
- just 'Picture could not be taken' with no explanation why.
I need to mention that I have plenty of sweeping experience on my previous Xperia X10 and on a Sony Nex camera - so I am sweeping really smoothly and at medium speed. Are the phone position sensors and accelerometers too sensitive? (And the camera software inadequately set to interpret them?).
This is happening in roughly 3 out of 4 attempts (or even 4 out of 5) making the function hardly usable and very annoying.
Ironically, while the X10 had no such function, I was using a 'beta' version (called Panorama Beta) as a standalone app, offered by Sony Ericsson on the Android Market (now Play Shop). Despite being a beta, that app worked flawlessly and never gave me such problems. I have many excellent panoramas from that, and some have even won photographic awards. I particularly like the 'vertorama' mode, i.e. vertical sweeping. With the camera in 'landscape' mode, this captures a square-ish rectangle - with a wider field of view and more scene detail, at highest possible resolution. To capture a square (or 4:3 'portrait') vertorama, you need to stop sweeping early - and the Beta app had a 'Stop' button.
The new version integrated within the Xperia camera has no 'Stop' and expects you to make very long sweeps. I tried to stop by pressing the on-screen or physical shutter button, but that produces the above errors - or a very long and narrow rectangle, half of it greyed and the other half a blurry, low resolution panorama.
Disappointed with the function, I wanted to use the standalone Panorama Beta app, but it doesn't appear in the Market. Is it withdrawn by Sony? (As no longer beta and included with newer firmware)? Or is it only not appearing for the Xperia-S - presuming you already have it?
I tried taking a backed-up .APK from the X10 and 'restoring' (installing) it on the X-S, but it does not install. The install process starts normally, but when the blue 'thermometer' finishes, the message is: 'The app did not install' - with no further explanation. I imagine it discovers the newer version already installed and avoids a conflict with it?
All other 'panorama' apps on the market are much worse, from primitive to utter rubbish. They are either not 'sweep' and ask you to take multiple separate shots, asking you to manually align them to on-screen guide marks, before running a 'stitch' operation (resulting in very poor blends with obvious fault lines). Or they shoot relatively smoothly, but the end image is very lo-res, small in size and out of focus. Among all of them the Photaf app was closest to 'working' but it's only horizontal and stitches are a hit-and-miss (most of the time a miss - too obvious).
Can others, please, share experiences with the Sweep Panorama mode in the Xperia-S camera? Does it work for you or have you got similar problems? Has anyone found solutions?
Any suggestions how to make the Beta standalone app install and work? (The new one isn't standalone, so I am not sure I'll be able to uninstall it, even when I root the phone).
Thanks for any info!
The new Sweep Panorama sucks big time indeed. There's a modified APK of the beta floating around, I've been using it on my Arc S/Neo for ages, works just fine!
Don't have my S yet, so can't try it, but you can give it a go:
http://www.box.com/s/182e205dc19cbba235f7
Ambroos said:
The new Sweep Panorama sucks big time indeed. There's a modified APK of the beta floating around, I've been using it on my Arc S/Neo for ages, works just fine!
Don't have my S yet, so can't try it, but you can give it a go:
http://www.box.com/s/182e205dc19cbba235f7
Click to expand...
Click to collapse
Thanks a lot - this is the same Panorama 'Beta' I loved on my X10, works well on the X-S. I'll now use it as main pano tool and hope Sony will fix their in-camera version with one of the firmware updates.
Not sure if they read (or at least scour with spider-bots) this and similar sites for insight what needs fixing - if I knew a contact point I'd write to them but won't spend time researching their feedback channels...
The S camera rocks otherwise, wish you to get yours soon!
I'll let them know whenever I get the chance
Hi all and sorry for my bad english.
First of all i'd like to thanks for your work.
I had install Alpha 5 ICS in my folio 100 tablet and i think that it's a PERFECT rom but i have a problem and i'd like to know if it happend only to me.
When i put the tablet in standby (press power button) and i turn it on after some minutes the screen blink for minutes and i . Then it return normal.
is there anyone that have this problem?
Is it a problem of the rom or of my hardware?
Thanks a lot
It's related to alpha5,however not everyone experiences it.
Sent from my folio100 using Tapatalk 2
I have the same problem. For me it looks like switching to applications reduces a lot the flickering, and makes it stop a lot sooner.
Same problem, screen flicker when waken from sleep.
Hi everyone,
I have sometimes flicker in wake, but still very reasonable.
This also happens when starting the Folio (very rare), this on the original kernel or amended by the Botto00 (OC+387 Mo).
Can not write about the thread development, I want to thank the developers for this great alpha5.
It works great and is very stable.
-I have only noticed a few crashes during games (screen that completely blocks), as well as the modified kernel OC.
-An issue with the judgment of the Folio. It happens that it freezes at that time, which means that it 's not extinguish. Similarly as with the modified kernel of OC.
-Sometimes the sound does not work correctly on some installations (excluding cracks). The sound is simply inaudible on games.
Overall, that is very good, also modified the kernel botto00 works well. (I don' t use it with overclocking).
Here are the games tested on the Alpha (GT-P7510 build.prop) with kernel OC+387 of botto00 :
Asphalt 6, Canabalt, Dead Space, GTA 3 (download data by automating the time zone), Mass Effect (taken on another device), ShadowGum, Nova 2 and many others.
Does not work :
Modern Combat 3, to CM7 yes.
In the general operation :
-Since the Alpha, more opportunities to uninstall apps by the Drawer of Trebuchet.
-Highly theme manager
Congratulations to all for your work and your information and thank you DerArtem and Nopy occupy the Folio of such a beautiful way.
Daveheart
Can u upload your build.prop?
Nothing more but here : http://www.multiupload.nl/K1GKGD60VX
PS: Nova 3 works pretty well on this rom.
Does Mass Effect work at anyone??
oops, I did not understand your request and I realized, with your second question, that I had forgotten information which "may be" important .
I edit my post......
Crunon said:
Does Mass Effect work at anyone??
Click to expand...
Click to collapse
works for me, you have to launch it for first time and download data using 160DPI, then you can swtich back to 120DPI and it will work nicely
Great =)
I love my Folio more and more,.. =)
If you can tell me, how i can run the Settlers, the Folio is near perfect =)
Your answer was in the build.prop provides ......
I have less problem with a DPI of 160 than 120.
In addition, we use a build of Galaxy Tab has a DPi of 151 .....
For The Settlers HD, that is possible to get rid of the white screen.
You need the version for Tegra and use Chainfire 3D with PowerVR plugins.
Works by 120 or 160 DPI
http://www.imabox.fr/u17/120506141395LqWP24.png
For Chainfire 3D (I use the paid version), you will need to change some settings for the game to run without too many problems.
Thank you for the answer.
On CM7.1 i tried many configurations with CF, everytime white screen,...
Can you tell me your configuration?
Yes to CM7, that was the same problem as on many devices.
Use the PowerVR plugins, uncheck Use default setting and check Reduce texture quality. No choice ......
Unroll textures that crashes the game.
Now i see it right,but the game crashes in the first seconds of the first mission,...
No FC, it closes.
Sorry, I haven 't played much but I'm in act 3.
PS : really, after several tries, not closing the game.
For Nova 3, although the Folio'm running the game, it lacks some effects : (
Hi there,
GyroscopeNoiseFilter (previously: JitteryGyroFixForCardboard) is a module to reduce/eliminate the noise in unstable gyroscope that are found in some phones like the Moto G 2nd gen or Huawei Ascend G7. Basically, the app does the noise smoothing that app devs do, but here this module uses a system hook to apply the noise smoothing preprocessing for all apps, but the main goal here is specifically to remove jitter, not drift (although the filters may help, but there's no sensor fusion, yet).
This is particularly interesting for virtual reality (VR) or head-tracking apps because a noisy gyroscope will produce a feeling of dizzyness and nausea, but this can also be interesting for any app using the gyroscope because the output will be a lot smoother and accurate (particularly when the phone is held still).
The module was originally wrote by Kjos and the repo lives here:
https://github.com/Kjos/XposedJitteryGyroFix
The thread that started the module is on Reddit:
https://www.reddit.com/r/GoogleCardboard/comments/335ins/fix_for_jittery_gyroscopes_such_as_moto_g
Here is the latest version of the module, v1.4 (also attached to this thread):
https://github.com/lrq3000/XposedJitteryGyroFix/releases/download/v1.4/GyroscopeNoiseFilter_v1.4.apk
The module is also available directly from the Xposed repo:
http://repo.xposed.info/module/net.kajos.gyronoisefilter
=== DESCRIPTION ===
The gyroscope is the main sensor for head tracking / virtual reality apps.
However, it's common for phones' gyroscopes to be noisy, which in practice shows as jitter, and this can create a dizzyness feeling and nausea, particularly when standing still (the "camera" still moves around just like if you were at sea).
Android now offers "virtual" sensors, which use a method known as sensor fusion to avoid those noisy outputs by combining several sensors (usually: gyroscope, accelerometer, magnetometer).
However, it's up to each app dev to use these virtual sensors, and to implement further post-processing to smooth the sensor and reduce the noise.
This module adopts another approach: it hooks directly to the hardware gyroscope and it preprocess every outputs with smoothing filters before relaying the data to the apps.
Therefore, the noise is reduced or even eliminated of the gyroscope's output for every apps.
=== OPTIONS ===
This module currently implements a few different strategies to filter and reduce noise, which can be used complementary or alone (each option can be disabled):
1. Filter type: type of the filter that will be applied to reduce noise in the gyroscope output.
2. Filter size: the number of samples to use to compute the filtering. Usually, the bigger the filter is, the less jitter there will be but at the expense of some lag.
3. Filter optional value: value of the constant that configures some types of filters such as lowpass or additive smoothing.
4. Minimum value change threshold: prevents the phone from registering the new sensor's values if the difference to the median is smaller than the given threshold.
5. Stationary minimum value threshold: when stationary, prevents the sensor from moving if the change is below the given threshold (this is similar to min value change but here it only affects the stationary state, when you are not moving).
6. Rounding precision: round all sensor's values to the given decimal.
Options can be changed on-the-fly without having to restart the phone, and are instantly applied to the sensor, so that you can switch between this option screen and a VR app to test for the parameters that reduce the jitter the most for you.
Click to expand...
Click to collapse
I'm looking for feedback before we submit to the Xposed repo, so if you have any idea of a feature or if you spot a bug, feel free.
We are also looking for better filters, currently the best performing two types are the median filter and the one order low-pass filter, so if there's someone with some experience with noise reduction on the gyroscope (not the accelerometer), I'd be very interested to get some advices about that!
/EDIT: update v1.4.
Also, we found a great opensource app called GyroscopeExplorer (kudos to the dev) which implements all kinds of sensor fusion and with a very good documentation, so that's a great source of info to implement advanced filters, but, although they smooth the movement's noise and drifting issues, they do not fix jitter at all, so for the moment we won't implement these advanced filters. We are now focusing on supporting more apps, particularly the ones using the new Cardboard NDK API to access virtual sensors (this bypasses the usual SensorManager).
Sorry, I forgot to attach the APK directly to the thread, like it's usually done around here. That's now done.
Very interesting module.
I wonder if this would give better results when doing Photospheres with the Google Camera app.
Also, does this have any meaningful impact on cpu usage and battery draining ?
thanks!
edgrd said:
Very interesting module.
I wonder if this would give better results when doing Photospheres with the Google Camera app.
Also, does this have any meaningful impact on cpu usage and battery draining ?
thanks!
Click to expand...
Click to collapse
I never made Photospheres with the Google Camera app, but if it uses the Gyroscope and you experience some jitter, then the module should help yes.
About CPU, the module is quite light on resources. The exact usage mostly depends on the filter type and filter size, with the low-pass filter being the lightest on CPU (only a few additions and multiplications, so it's negligible). All the other options such as the "minimum value change" only do a single calculation so their CPU usage is also negligible. However, if you use the mean or median filters and with a big filter size (like 1000), you may notice a very very small CPU usage, but it will still be very low (the time of a summation over an array of the size you specified, so it's not that big).
I have experienced some small (but still perceived) input lag using the default filter (median), switching to the lightest one and decreasing filter size to 8 fixed it
Would be nice if this module was presented more as an improvement / upgrade to the default gyroscope output, other than a simple fix
And after the app matures a little bit, you could make it available on the Play store too, so more people get this benefit
thanks again :good:
Good idea, but I can’t make head or tail of it. Maybe you ought to include simple preset/config… (sophisticated, uniform, simple & powerful, extreme…etc.), so that punters with Cardboards don’t spend a week scratching their heads on figuring out values, stationary thresholds and precisions.
I get nauseous using both DK2 and smartphone HMDs - don’t know if it’s me or noisy gyroscopes.
Thank's for the feedback everyone
@edgrd: yes the median filter smoothes the gyroscope more but it adds a delay proportionally to the filter's size. The low-pass filter does not add any perceptible delay, and the filter size does not matter (it only uses the previous gyroscope's value, so the filter size is always 1. I have yet to find the calculation for a bigger low-pass filter - but it works already very well as it is).
Indeed this is more an improvement now than a fix, that's why we renamed the app now to GyroscopeNoiseFilter
@Lord Childe: thank's for the idea of presets, I thought about that but however I can't think of a way to provide presets, since the values you set entirely depends on your own gyroscope's values. So for the moment, it is advised to just try out different values and you can switch back and forth to a VR app of your choice to instantly see the effect. Maybe we could do some kind of automatic calibration (eg, don't move your smartphone for a few seconds and this will automatically detect the values of the jitter).
Personally, on my Huawei Ascend G7, I use the low-pass filter and the stationary minimum value change set at 0.2. All the others are at default. And yes, this helps greatly to reduce the nausea for me (because when the phone still moves while you are standing still, this produces a feeling similar to being sea-sick).
Does not work on Cyanogenmod 12.1 Moto G 2nd Gen
Hi folks,
Tried to get it working on my Moto G 2nd Gen running Cyanogenmod 12.1. I can set the values but the Google Cardboard app does not seem to be taking the filtered values.
I tried running the Gyroscope Explorer app and if I enable Mean Smoothing, the app (Gyroscope Explorer) shows smooth values. But still has no effect on the cardboard app.
arindammanidas said:
Tried to get it working on my Moto G 2nd Gen running Cyanogenmod 12.1. I can set the values but the Google Cardboard app does not seem to be taking the filtered values.
Click to expand...
Click to collapse
Yes indeed, this is the issue we are currently working on. It seems that there are currently two ways to get the head's position: using SensorManager/SystemSensorManager, or using the Cardboard SDK's own method. The latter seems to completely bypass the SensorManager, which is the usual way of accessing the gyroscope's values. Most cardboard's apps are still using the SensorManager to access the gyroscope, so for these apps, our module works correctly. But for newer cardboard's apps using the Cardboard SDK orientation provider, our module does not work.
This is a pretty tough problem, and I never developped a Cardboard's app. If someone with experience with developping a Cardboard app can give some help with some advices, this would really help us a lot!
We just updated the module, Arindammanidas. Please try the latest version (v1.5) and see if this fixes your issue:
http://repo.xposed.info/module/net.kajos.gyronoisefilter
https://github.com/lrq3000/XposedJitteryGyroFix/releases/tag/v1.5
If it doesn't fix your issue, please tell us what app and what version doesn't work with our module. We are aware that there are still a few apps that may not work, in particular Cmoar Cinema Pro v4.3 (but version Free is OK). We don't yet know why (the source is closed).
/EDIT: we narrowed down the issue, and it seems that only apps using Unity3d along with the Durovis Dive SDK for head tracking are not supported. It seems it's because they use their own native library to manipulate the sensors, so I'm not sure we can do anything about these apps...
I just uninstalled Xposed! I'll flash it back and report! Thanks a lot.
lrq3000 said:
We just updated the module, Arindammanidas. Please try the latest version (v1.5) and see if this fixes your issue:
http://repo.xposed.info/module/net.kajos.gyronoisefilter
https://github.com/lrq3000/XposedJitteryGyroFix/releases/tag/v1.5
If it doesn't fix your issue, please tell us what app and what version doesn't work with our module. We are aware that there are still a few apps that may not work, in particular Cmoar Cinema Pro v4.3 (but version Free is OK). We don't yet know why (the source is closed).
Click to expand...
Click to collapse
Hi, I tried out version 1.5 and it still gives me jitters in the google cardboard app demos. Probably the cardboard app is reading from somewhere else?
Which google cardboard app? Do you mean the treasurehunt? Normally, treasurehunt is supported. Is it another app you are talking about?
lrq3000 said:
Which google cardboard app? Do you mean the treasurehunt? Normally, treasurehunt is supported. Is it another app you are talking about?
Click to expand...
Click to collapse
I was talking about the demos on the cardboard app itself. When you open the Google Cardboard app, you have an option for some demos e.g. Windy Day, Google Earth etc.
These still have jitters.
You're correct, I totally forgot about those demo apps and I didn't try them. We will see what we can do. Thank you for the feedback.
Is there any way to reduce drift when using photosphere or taking panorama photographs in Google camera?
Hello, I have a 'lenovo k3 note "with android 5.0.1, this phone has no physical gyroscope, makes a software simulation using other sensors.
I've been playing some value to your program and seems to improve a bit, but keeps moving image when this stop.
I can change the way you treat the sensor data? Even without one hardware.
Moto G 2014
For those with a Moto G 2nd generation, what are your settings?
Dear developers.
Is it possible to put an inversion of some of the axes in this module?
Some Chinese smartphones (for example ZOPO ZP998, iOcean x8), the gyroscope's axis is inverted, and the manufacturer ignores requests to fix it.
AKSU78 said:
Dear developers.
Is it possible to put an inversion of some of the axes in this module?
Some Chinese smartphones (for example ZOPO ZP998, iOcean x8), the gyroscope's axis is inverted, and the manufacturer ignores requests to fix it.
Click to expand...
Click to collapse
Wow, I was about to post the same because I was impressed someone managed to change gyroscope values. Yes, I have the same problem, my spanish smartphone comes with the X axis inverted, so the sensor fusion makes strange things (gyroscope and magnetometer/accelerometer read oppossite values), although I think this could be another app instead of adding it to your noise filter one (because in my phone there's no jittery, only a changed axis. It could be solved by the developers, but at this time there's no patch).
Thanks a lot!