Hello everyone. I have a problem with pitch and roll on my 3T. If the phone lies flat on the table the pitch/roll value is not 0 (about 7° difference). A factory reset did not help. Some apps can correct this for themselves, but not system-wide. Is there a system-wide way to calibrate pitch/roll or reset it ?
My Android Version: [OP3T] [ROM + KERNEL] Unofficial CyanogenMod 13.0 with custom kernel [Dec. 11, 2016] By Sultanxda
Edit: I now have the current official LineageOS installed: https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/rom-lineageos-15-1-oneplus-3-3t-t3739169
Edit: Perhaps it is a ROM problem because a friend has the same "7 ° pitch" problem with his 3T. Here is a screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Has everyone else a perfect 0° calibrated phone ?
Really ?
Yesterday I noticed the same thing.
So
orientation is calculated by android using magnetometer and acceleration which works fine as long as you are within earths magnetic field and earth's gravitational acceleration is 9.81 m/s², aka everywhere on earth.
if you look at your acceleration sensor's y axis you will see that it is off by ~ -1 m/s², aka you would have to add 1 to it to be correct. To check what your value is, lay your op3t onto a flat surface, so there should be an acceleration of 0.0. to check that, place it in portrait mode, at a 90° angle. you should get 9.8 m/s² +_ your offset.
fixing that would require an addition into this method here, line 692: https://android.googlesource.com/pl...ava/android/hardware/SystemSensorManager.java .
this requires either recompiling OOS from source with that patch and replacing the framework.jar (and odex) files, or using a custom rom, or using the xposed framework, which sadly is not available for android 7.0. If you are using a custom rom, call their maintainer to add a patch in there, or diy. if not, sorry.
Thanks for explaining. You are right there seems to be an Y offset of about -1. But the question is why? And I'm not the only one. Two friends with an 1+3T have nearly the same offset. Strange.
This affects VR mode. Everything is the same 6 degs tilted and makes for a pretty nauseating experience.
https://forums.oneplus.net/threads/...rometer-magnetometer-gyroscope-sensor.405894/
You can recalibrate
The 808 method seem to be working fine for the 3/3T according the OnePlus forum, but only if one has OxygenOS installed.
Because I have LineageOS installed this is sadly no option for me.
Is there any way for LOS ?
Or can the app which does the trick on OxygenOS be extracted and used on LOS ?
Will anything change now that advanced VR is supported by LineageOS ?
Sent from my ONEPLUS A3000 using Tapatalk
I think there won't be an easy solution with LOS so fast, if ever ... too bad :crying:
Can confirm, with OOS I was able to do the calibration :victory:
Too bad that it can't be done with LOS
Related
Decided to have a go at my first bit of dev (if you can call it that ), by converting a game designed around SDK2 and bringing it to the Streak7's Honeycomb screen, It is similar to Cartoon Wars for the iPhone but nowhere near as good.....But it passes the time and can be quite addictive on the hardest setting!
I decided to do this as my youngest lad loves this type of game (as I do too ) I could not find a version other than the ones designed around a small screen device, although the original runs on the Streak7 it displays a small game, also it was an excuse to learn something new
The original game would scale up when the LCD density was set to 160, but this version scales up & lets you keep DJ_Steve's recommended 106 density setting for his HD7-B3 OS, I have not tried it on any other device other than the Streak7 or any other OS other than HD7-B3, so feedback would be appreciated on other Device/OS combo's.....Although I don't expect it to work on anything else other than Streak7-HD combo
The overall process was time consuming to say the least, mostly in the latter stages of fine tuning the .png sizes for paticular images, too big and the game wouldn't load, too small and it left empty bits of screen everywhere.
The programs I used to help me achieve my goals where:
APKTOOL - by Brut.all - For the decompile/recompile of original .apk (must have tool )
.XML Editor - For the obvious
IMAGE CONVERTER PLUS - A brilliant program for batch image conversions that can be profiled to your specific needs
AUTO-SIGN by Dave Da Illest 1 - Which enables you to sign your recompiled .apk (does what it says on the box )
Anyway, have a try for yourself and let me know your results
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or
CLICK HERE
Force closes on 2.2.2
Sent from my Streak 7 rocking the Streakdroid7 ROM
Gravityrat said:
Force closes on 2.2.2
Click to expand...
Click to collapse
....As I expected TBH, I rekon the original would work just fine though, but posting that would of been outright piracy IMHO, this is more of a screen mod of the original that is based around the 106 LCD Density setting of HD7, I could of created a few drawable-XXXX folders for the different res, but then this just takes the file size to rediculous levels.
Many thanks for taking the time trying and replying anyway, much appreciated, button pressed!
Hey Folks - I could use some help here I am stumped.
I am working on a project to launch one of my model rockets and stream the launch video live via USTREAM (using an LG Revolution modified to be onboard). The issue is USTREAM sets the camera to landscape mode so the phone needs to be held in the landscape position for the video feed to be oriented properly for viewing. The problem is I need the phone to be oriented in the PORTRAIT position due to size limitations of the rocket itself.
USTREAM does not offer the ability to rotate the video stream.... so I was wondering if anyone (dev?) can write a middleware app that will force the camera output to be rotated 90 degrees before the application layer receives the stream? Is that even possible?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FYI: I have tried rotating the camera physically but the connector ribbon is too short and doesn't afford the flexibility for such a move. Creating an "extension" cable is also not in cards since the plugs are nano-sized surface mount.
Thanks in advance...
I have no idea how to do that but please let us know about the launch. Awesome project!
This really does not belong in Development so I have gone ahead and moved it. The project does sounds interesting and I wish you good luck.
Android1 Project Thread ...
Launched the rocket and As-droid-naut this past weekend (minus the LG) - here is the thread I started in the General area if you want to see what I'm up to:
http://forum.xda-developers.com/showthread.php?t=1892422
Dashcam
Did you find a solution?
I have tested a lot of dashcam-apps (f.i. 640x480) and the phone in mounted in portrait, the video is only in portrait (480x640). On the pc i have to transform it 90 degrees.
Camera gets its positioning from the accelerometer. Need to somehow fool the camera into thinking it is vertical all the time.
Thanks for the quick response.
That is not the problem. (It is easy, to rotate the video later (and maybe crop) on the pc.
My phone camera has 8 MP CMOS (Landscape 3264x2448 or Portrait 2448x3264)
I need only the upper 720x480 (or better of the 2448x3264) and not 480x720.
The lower part of the video is waste. (only the dashboard, what is not very interesting)
(If I rotate my phone 90°, i see only the dashboard and a little bit of heaven, but no street.)
A higher mounting of the phone holder is not possible.
The best solution is a dashcam-app with a possibility of selecting a video area. Why is it so difficult to program?
NookCalc is a basic, four function calculator designed from the ground up for the Nook Simple Touch. It is optimized for the e-ink display. I wrote this app. The top right page button acts as a dedicated clear button, in addition to the on screen clear button and clear option in the menu.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That looks nice, but 840 kB is way too big an .apk file for what this does.
It should be somewhere in the neighborhood of 10-20 kB.
You have included android.support.v4 and android.support.v7 when they are not used in the least.
You can delete those from your project.
Nice! It's good to see apps written for the nook.
The calculator looks nice and the e-ink optimization is great,
however, since I don't have anything to calculate just now I just did a bit of stress testing to find that:
a) there seems to be an int overflow on really large nubers, it either crashes or warps to negative.
b) I'm not sure what pressing '=' repeatedly is supposed to do (if anything at all) as it gives weird and inconsistent results.
c) it crashes on division by zero (I HAD to try that )
d) Also, to have a useful division function you really need to use floating point numbers.
It's a nice project, but needs some working on before being a useful calculator
Thanks for the feedback guys, I appreciate it. Renate NST I removed the android.support.v7 and it significantly reduced the size of the apk from 837KB to 60.4KB, a 776.6KB difference. I didn't see android.support.v4 in my project. I didn't add any support libraries myself, Android Studio seems to put the support library in new projects and there doesn't seem to be a way to make a new project without the support library.
sega dude said:
Thanks for the feedback guys, I appreciate it. Renate NST I removed the android.support.v7 and it significantly reduced the size of the apk from 837KB to 60.4KB, a 776.6KB difference. I didn't see android.support.v4 in my project. I didn't add any support libraries myself, Android Studio seems to put the support library in new projects and there doesn't seem to be a way to make a new project without the support library.
Click to expand...
Click to collapse
how do i close this program ?
Many thanks
I just rooted my nook touch and will try this app
Let me explain my problem... I love to use on-screen soft key instead of capacitive keys on my Galaxy S6... But when I try to use Camera app the UI of the app (buttons) is under lapped to the Soft key (back, home, multitasking buttons)... So is there any way the UI of camera app can be fixed while using soft key on Galaxy S6...? Smart Manager app has same problem...
Please see attached screenshot...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help will be much appreciated..!
Sent from my SM-G920F using Tapatalk
Did you try clearing the camera app cache and data see if that helps? its not suppose to be like that in your screenshot.
As I mentioned in the the 'multidpi system app mod thread' where you also posted this question this is a result of the dirty multi-dpi fix... The apk has it's dimension values set to absolute pixels instead of dp... As a result it doesn't take into account the actual displayable view, but just stretches across the entire screen.
So this isn't going to work with the multidpi versions, an earlier mod where dp values where changed also didn't work so I have no idea how to fix this for now... Only solution if you wish to use softkey is to use standard dpi of 640 and the unmodded stock apks.
*EDIT*
By the way, as you posted this in the modded apk thread I assumed you are sing these... But as I haven't done anything to the smart manager I am starting to doubt that. If that isn't the case you can forget my remark (Still no clue though, apart from the fact that Samsung seems to suck at making these apps scale properly)
I've ran into a problem on 5.1.1 (just updated) with navbar. The themes won't work! When trying to apply a theme it says that I have to remove "keyboard cover". Is the a service we can disable to make themes work again with navbar? Any ideas? There were no issues with 5.0.2
Okay, so here's what I've tried to fix this problem, and I'm still drawing blanks. Here's the problem - the phone acts as if there is no rear camera whatsoever, nor led light on the back for a flashlight. Selfie (front-facing) camera works as intended.
1) Clear Cache on app.
2) Multiple different camera apps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- no change
3) full factory reset - no change
4) Aftermarket ROM - LineageOS - no change
5) installed brand new camera purchased new from witrigs - no change
6) Z-Device test
Weird that it shows front facing (secondary) camera isn't working, but front-facing works fine. If I try to save a z-device log, the app crashes every time. And this is a fresh install.
There was no inciting incident or anything done to the phone, no fall or water damage or anything along those lines. I'm running out of ideas here, what else can I do/try to get this thing working?
Crossposted to Reddit
I would recommend performing the Unbrick guide.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
ZVNexus said:
I would recommend performing the Unbrick guide.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
So I've just spent the past couple of hours trying to make that work. No luck on SO many steps. I imagine it's because the phone is not bricked? Is there another tool that would potentially accomplish the same thing?
marvin_rock said:
So I've just spent the past couple of hours trying to make that work. No luck on SO many steps. I imagine it's because the phone is not bricked? Is there another tool that would potentially accomplish the same thing?
Click to expand...
Click to collapse
This unbrick guide can be used even if the phone is not bricked.
What steps gave you problems?