Just a short screenrecord showing my Nexus 7 running with Launcher3 on my own 4.4 AOSP Build. Demonstrates that it doesn't seem to have the Keyboard issue GEL has, but it does do landscape the same. (I don't know if there's a way to properly record orientation changes, so it only show's the left half of the screen there).
Related
Anyone who's had an Android tablet knows that a lot of poorly coded apps get flummoxed by the default 90 degree rotated, landscape orientation of the device.
Thus my question, is the sensor in the Nexus 7 rotated as well? Or is the default orientation set to portrait, the same as a phone?
Google "sensors-overview sensors-coords android" to find the relevant developer page. The specific orientation details are near the bottom: Sensor Coordinate System
"One Screen Turn Deserves Another" is an excellent article that explains the problem quite well.
If anyone who has a preview device could check to see what orientation the N7 uses, that'd be great. I'm hoping for portrait.
zinfinion said:
Anyone who's had an Android tablet knows that a lot of poorly coded apps get flummoxed by the default 90 degree rotated, landscape orientation of the device.
Thus my question, is the sensor in the Nexus 7 rotated as well? Or is the default orientation set to portrait, the same as a phone?
Google "sensors-overview sensors-coords android" to find the relevant developer page. The specific orientation details are near the bottom: Sensor Coordinate System
"One Screen Turn Deserves Another" is an excellent article that explains the problem quite well.
If anyone who has a preview device could check to see what orientation the N7 uses, that'd be great. I'm hoping for portrait.
Click to expand...
Click to collapse
I'd assume it would be rotated since they're very intent on educating users on using a 7" tablet in portrait like a book.
Yea I'm gonna say that it's probably not in landscape since the whole UI is portrait based. Seems a bit counter productive to have to rotate the device every time you launch an app.
Sent from my Samsung Galaxy S III using xda-developers app
DarkRyoushii said:
Yea I'm gonna say that it's probably not in landscape since the whole UI is portrait based. Seems a bit counter productive to have to rotate the device every time you launch an app.
Click to expand...
Click to collapse
I'm fairly confident the sensors will be in portrait orientation by default, but confirmation would be nice.
The reason I ask is because my current Galaxy Tab 2 7.0 has the 90 degree offset sensor issue. 99% of the time it's fine. It boots up in portrait, apps launch in portrait (unless landscape only apps, which launch in landscape with no issues). Certain apps that are poorly coded and expect all devices to be portrait by default tend to do all sorts of odd things though. I've only run across a couple in the Play store, and one of those has been fixed.
The real problem lies with custom roms, as all of the ones I have tried default to the landscape sensor orientation (boot orientation when laid flat is landscape), rather than compensate for it (the stock Samsung rom is portrait by default when laid flat). This has led to all sorts of aggravating (and unintentionally hilarious) issues with the custom roms.
So hopefully Google thought this through and the N7 sensor orientation is portrait by default and basically acts like a large phone minus the phone bits.
Will there be a new build for the Nook color?
PIE Status Update: 22-23 January, speed bump, scalability
We wrapped up the elementary work, now we will look into the technical issues that are still left. If you were afraid of buggy betas, it has gotten to a point where its pretty decent for daily use.
We rewrote the original AOSP control pretty much from scratch now. Even if it was once based on the Google control, you wont be able to recognize much when you see the code (which comes out soon). It is blazing fast now and responsive due to hardware acceleration and optimized drawing. The old betas were a bit laggy due to test code, we cleaned up completely. It should not be heavy on your battery either. Flicking or navigating it blind is simple. Until now we can do:
- Per app color, it has its own theme aswell but when switched off it picks up colors you define per app (see video)
- Recents key transforms into /// kill-all-button inside the recents view
- Rubberbanding for fast navigation
- Displays status informations like clock, date, notifications on touch
- We wrote our own custom panels for notifications and toggles that can be flicked into view - these are still basic though
- It can be on either of all the four sides, you can even set up multi trigger areas
- It is resolution independent and scalable - it will not look distorted on tablets and phablets anymore
- You can control the animations, even switch them off
- It supports per-app-expand, meaning that it can jump into PIE mode for apps you chose
First updates starting to roll out soon. 1-2-3 hours.
I'm currently running Team EOS' most recent build on my N4, and I'm really enjoying it. I've got the navigation bar hidden on boot with LMT installed with pie. This setup is just about perfect, but one issue I'm having is that, in landscape orientation, Swiftkey doesn't extend to the end of the screen. There is a gap where the navigation bar would normally be. The stock keyboard doesn't behave the same way, covering the full screen. Anyone know a way to make this a little more visually appealing?
Been updated to 4.4.1 for a couple of days now, changed to ART and WhatsApp compatibility has been fixed!
Other updates include:
The camera app on the Nexus 5 has become faster with the latest update.
The low volume output from Nexus 5 speaker in certain apps has been fixed.
The heptic feedback on Nexus 5 has also been tweaked.
There are some bug fixes related to ART. This allows Whatsapp to work with the ART runtime.
The default email client in Nexus 5 not syncing with an exchange server bug is also fixed now.
Immersive mode breaking while adjusting the volume level bug is fixed.
The new Photo app is now the default Gallery app.
There is slight improvement in benchmark performance of the Nexus 5.
The transparent status bar sometimes turning opaque issue on the Nexus 5 has fixed.
The navigation bar is now transparent on the Nexus 4 lockscreen.
The Settings icon in Quick tiles has been changed.
The Miracast setting has been renamed to Cast Settings.
Option for 4G/LTE under Mobile Data now shows “recommended.”
LED pulses more frequently for notifications.
Cell/Wi-Fi/Battery icons in the notification bar are now aligned properly.
For a list of whats working on ARTand what's not visit
http://www.androidruntime.com/list
Changelog from IBTimes. Apologies if this has already been posted.
libart.so
Is it possible to use 4.4.1 libart.so at 4.4 rom?
I used AICP and CM14.1, and had installed moto camera on both. The interface works glitchy, as in I had to touch a bit away from the buttons to actually trigger them, or some things just don't respond to touch, etc.
On AICP, the moto camera UI wouldn't work at all. Touching anywhere on the screen, even on a UI element would take a picture as if I touched any empty spot on the screen. I couldn't toggle front cam or toggle other options.
On CM14.1, I can toggle some options, but for many things I have to touch a bit away from the buttons. And I can't turn off shutter sound either.
I'm on CM as I type this.
I was on AICP till 2 days ago .
jayantbh said:
I used AICP and CM14.1, and had installed moto camera on both. The interface works glitchy, as in I had to touch a bit away from the buttons to actually trigger them, or some things just don't respond to touch, etc.
On AICP, the moto camera UI wouldn't work at all. Touching anywhere on the screen, even on a UI element would take a picture as if I touched any empty spot on the screen. I couldn't toggle front cam or toggle other options.
On CM14.1, I can toggle some options, but for many things I have to touch a bit away from the buttons. And I can't turn off shutter sound either.
I'm on CM as I type this.
I was on AICP till 2 days ago .
Click to expand...
Click to collapse
you have to fix the DPI value of the screen.
pijes said:
you have to fix the DPI value of the screen.
Click to expand...
Click to collapse
Didn't expect this would be a problem. But makes sense.
I've reduced the display size to small.
I would however really want it to stay that way. Anything I can do to the app to fix this?
It nothing works, I'm okay with not using moto camera.
jayantbh said:
Didn't expect this would be a problem. But makes sense.
I've reduced the display size to small.
I would however really want it to stay that way. Anything I can do to the app to fix this?
It nothing works, I'm okay with not using moto camera.
Click to expand...
Click to collapse
xposed in MM has a module called App Settings where we could set per-app dpi values. unfortunately, xposed is not yet available in Nougat.