I remember AOKP used to have the option to decrease the display rotation delay on android 4.0 on my galaxy nexus. Does anyone know how to manually decrease the delay for our nexus 7s? It takes way too long for the rotation to occur and makes the device seem slow.
Not yet.
Sent from my Nexus 7 using XDA Premium HD app
malikadnanm said:
I remember AOKP used to have the option to decrease the display rotation delay on android 4.0 on my galaxy nexus. Does anyone know how to manually decrease the delay for our nexus 7s? It takes way too long for the rotation to occur and makes the device seem slow.
Click to expand...
Click to collapse
this is why i turned off homescreen rotation.
the worst is when you pick it up from the table and turn on the screen and it's sideways and takes ages to switch back to normal and let you unlock it. i've been looking for a way to disable rotation for the lock screen but haven't found anything.
Wow, this really isn't something that has been figured out yet?
I just got the tablet, I keep forgetting how young this thing is still, I just assumed what the maturity of development would be.
Sent from my Nexus 7 using xda premium
nvertigo said:
this is why i turned off homescreen rotation.
the worst is when you pick it up from the table and turn on the screen and it's sideways and takes ages to switch back to normal and let you unlock it. i've been looking for a way to disable rotation for the lock screen but haven't found anything.
Click to expand...
Click to collapse
There are rotation apps in the play store that can lock the rotation of the lockscreen... but it still wasn't good enough for my needs. The lockscreen is a problem and annoying because the slide to unlock moves.
The app solutions are OK but there is still a delay. The app basically senses the lockscreen and rotates it to a specific orientation. So if you wake it up in landscape, it will rotate to portrait if set. The problem is the delay that is annoying.
Disabling the stock lockscreen or using another 3rd party lockscreen such as WidgetLocker is the only real solution (outside of locking rotation system wide).
You may also have success using a launcher to force a orientation before locking.... but this would prove irrelevant if locking from another app.
Other then the lockscreen being annoying, the rotation sensor isn't very touchy IMO. For me, I don't see it rotating unwantedly very often.
For AOKP, 4.2.1 is still very new and development are adding features every day. Because of the new multiuser features, the file system and other features have changed enough to warrant building from scratch. I'm sure if you asked your favorite dev to implement rotation delay, they could. Hell, maybe even a stock lockscreen that doesn't rotate.
Sent from my Nexus 7 using XDA Premium HD app
Maybe I'm missing something here. Delay in rotation? How much time are you talking about because takes about a second or less and is quite acceptable.
From my Nexus 7
Funny enough i mentioned the same thing in the PA thread and didn't seer this thread lol. I can't believe people feel the slow speed is acceptable when my iPhone 4(yeah i know. I hate it but its all I've got at the moment) rotates faster
Sent from my Nexus 7 using xda premium
Anthonok said:
Funny enough i mentioned the same thing in the PA thread and didn't seer this thread lol. I can't believe people feel the slow speed is acceptable when my iPhone 4(yeah i know. I hate it but its all I've got at the moment) rotates faster
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I totally agree with the comments in this thread. The rotation lag is unacceptable from a flagship device such as the N7. We got 4 cores ffs. Android doesn't seem to focus on these details and that's what makes them look "cheaper" than the competition. I mean, what do you think people will think if you're showing off your device, turn it horizontally, and wait... wait... wait... there ya go! Horrible!
It is a setting. Trust me, you don't want a faster rotation speed. The delay is put in place to let the accelometer know that you are requesting a rotation. Else it would rotate unexpectedly.
God I hated my iPads with their too fast rotations. Laying on the couch or with it in my lap (or most cases) the damn thing would just spinning away. Even just laying it down on the table, most times it would rotate first. I actually ended up locking the rotation because of this.
I thought this thread was to make the delay LONGER because it was too fast.
Android rotates plenty fast as it is. It is a simple timer not lag lol. It's like 2 seconds. Devs don't increase this for a reason. Don't mess with perfection.
Sent from my Nexus 7 using XDA Premium HD app
player911 said:
It is a setting. Trust me, you don't want a faster rotation speed. The delay is put in place to let the accelometer know that you are requesting a rotation. Else it would rotate unexpectedly.
God I hated my iPads with their too fast rotations. Laying on the couch or with it in my lap (or most cases) the damn thing would just spinning away. Even just laying it down on the table, most times it would rotate first. I actually ended up locking the rotation because of this.
I thought this thread was to make the delay LONGER because it was too fast.
Android rotates plenty fast as it is. It is a simple timer not lag lol. Devs don't increase this for a reason.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Personal preference. Some people don't like the slower speed. When I had my iPad I never had a problem of it rotating too quickly. When aokp had the option it was fantastic. Plus you wouldnt have to change it if you didn't want to. Even if aokp gets it back it doesn't effect me cause there's no way in leaving PA so hopefully they would use it.
Sent from my Nexus 7 using xda premium
player911 said:
It is a setting. Trust me, you don't want a faster rotation speed. The delay is put in place to let the accelometer know that you are requesting a rotation. Else it would rotate unexpectedly.
God I hated my iPads with their too fast rotations. Laying on the couch or with it in my lap (or most cases) the damn thing would just spinning away. Even just laying it down on the table, most times it would rotate first. I actually ended up locking the rotation because of this.
I thought this thread was to make the delay LONGER because it was too fast.
Android rotates plenty fast as it is. It is a simple timer not lag lol. It's like 2 seconds. Devs don't increase this for a reason. Don't mess with perfection.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Uhhh.....what? A lot of other Android devices, including other tablets rotate faster. Why would anyone want it slower?
Sent from my EVO using Tapatalk 2
His preference then. I use my nexus primarily but have an ipad and I wish my nexus rotated even a fraction as smoothly and quickly as it does.
If you want proof how fast it can rotate look in the camera app. There is no delay set for rotation on that.
Sent from my Nexus 7 using xda premium
player911 said:
It is a setting. Trust me, you don't want a faster rotation speed. The delay is put in place to let the accelometer know that you are requesting a rotation. Else it would rotate unexpectedly.
God I hated my iPads with their too fast rotations. Laying on the couch or with it in my lap (or most cases) the damn thing would just spinning away. Even just laying it down on the table, most times it would rotate first. I actually ended up locking the rotation because of this.
I thought this thread was to make the delay LONGER because it was too fast.
Android rotates plenty fast as it is. It is a simple timer not lag lol. It's like 2 seconds. Devs don't increase this for a reason. Don't mess with perfection.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I never said it was lag. I actually prefer the iPads instantaneous rotation so it'd be nice if there was a way to reduce the delay to 0 seconds. The delay gives the appearance that there is lag, but I know it's purposely there.
Sent from my Nexus 7 using xda app-developers app
the source is with us..always. (attempt to document android orientation detection)
squshy 7 said:
Wow, this really isn't something that has been figured out yet?
Click to expand...
Click to collapse
not my device but when investigating this same issue.. dug deep and figured it out. So0Oo..
The code in question resides in frameworks/base/core/java/android/view/WindowOrientationListener.java..
last change explains the current (Jelly Bean/Android 4.1+) algorithm very well:
Code:
commit 5aa73ae58f049379a97bc86add541f27170c02a4
Author: Jeff Brown <[email protected]>
Date: [B]Fri Jan 13 15:29:21 2012 -0800[/B]
Improve heuristics for orientation detection.
1. Except as otherwise indicated, orientation change happens once
the predicted rotation has been stable for [B][U]40ms[/U][/B]. Noise is
suppressed by a low-pass filter with a 200ms time constant which
seems to be about as small as is practical given the quality
of the sensor data.
2. If the magnitude exceeds a threshold (excessive noise or freefall),
resets the predicted orientation.
Doesn't happen very often even when shaking the device.
This heuristic mainly protects the detector from spurious tilt due
to inaccurate determination of the gravity vector.
3. If the device was previously in a flat posture (on a table for at
least 1000ms), then it must move out of that posture for at least
[B][U]500ms[/U][/B] before the next orientation change will happen.
This heuristic suppresses most spurious rotations that happen while
picking up the device.
4. If the device is tilted away from the user by 20 degrees within
a span of 300ms, the device is said to be swinging and at least
300ms must elapse after the device stops swinging before the
next orientation change will happen.
This heuristic suppresses some but not all spurious rotations that
happen while putting down a device. Unfortunately, this heuristic
sometimes triggers a false positive when turning the device very
rapidly due to accelerometer noise. The 300ms pause is a compromise
so that occasional mispredicted swings don't significantly delay
the rotation.
===========================================
The code in effect for Ice Cream Sandwich/Android 4.0 was somewhat simpler:
Code:
commit c0347aa19f354a8e1ff4fcd5372b134c0c7c16ad
Author: Jeff Brown <[email protected]>
Date: Fri Sep 23 17:26:09 2011 -0700
Prevent unintended rotations.
Bug: 4981385
Changed the orientation listener to notify the policy whenever
its proposed orientation changes, and changes the window manager
to notify the orientation listener when the actual orientation
changes. This allows us to better handle the case where the
policy has rejected a given proposal at one time (because the
current application forced orientation) but might choose
to accept the same proposal at another time.
It's important that the proposal always be up to date. A proposal
becomes irrelevant as soon as the phone posture changes such
that we can no longer determine the orientation with confidence
(such as when a device is placed flat on a table).
Simplified the orientation filtering. Now we just wait [B][U]200ms[/U][/B]
for the device to be still before issuing a proposal. The idea
is that if the device is moving around a lot, we assume that
the device is being picked up or put down or otherwise in
the process of being moved. We don't want to change the rotation
until that's all settled down. However, we do want to tolerate
a certain amount of environmental noise.
(The previous confidence algorithm was also designed along
these lines but it was less direct about waiting for things
to settle. Instead it simply made orientation changes take
longer than usual while unsettled, but the extra delay was often
too much or too little. This one should be easier to tune.)
[...]
Code:
// The number of milliseconds for which the device posture must be stable
// before we perform an orientation change. If the device appears to be rotating
// (being picked up, put down) then we keep waiting until it settles.
private static final int SETTLE_TIME_MS = 200;
Then the talked-about "orientation delay" option was added in AOKP:
Code:
commit 94d7c35becdbdb129541fd3aa60e6e9d5f9dca7a
Author: Roman Birg <[email protected]>
Date: Sat Jan 7 12:44:16 2012 -0600
use a custom setting for SETTLE_TIME_MS
which added this to frameworks/base/core/java/android/provider/Settings.java:
Code:
public static final String ACCELEROMETER_ROTATION_SETTLE_TIME = "accelerometer_rotation_settle_time";
That setting was then introduced into the AOKP's ROMControl app:
Code:
commit 6b208ed81ce18a76c87e448b78972c0dda37a23d
Author: Roman Birg <[email protected]>
Date: Sat Jan 7 14:36:53 2012 -0600
Update many things!
- fix white spacing in strings/arrays
- add rotation rotation options
- add advanced toggle settings
[...]
Code:
mAnimationRotationDelay = (ListPreference) findPreference(PREF_ROTATION_ANIMATION);
mAnimationRotationDelay.setOnPreferenceChangeListener(this);
mAnimationRotationDelay.setValue(Settings.System.getInt(getActivity()
.getContentResolver(), Settings.System.ACCELEROMETER_ROTATION_SETTLE_TIME,
200) + "");
HTML:
<!-- animation rotation -->
<string-array name="rotation_animation_delay_entries">
<item>10 ms</item>
<item>25 ms</item>
<item>50 ms</item>
<item>75 ms</item>
<item>100 ms</item>
<item>150 ms</item>
<item>200 ms</item>
<item>250 ms</item>
<item>300 ms</item>
</string-array>
However, that option didn't live long and obviously a delay customization has to be reimplented for JB.. going to try out a delay of 0ms to figure out if it is even worth it..if it really is only 40ms on JB now then YTF does it still take so0O darn lo00O0ngzz^^^
maybe going to mess with that 200ms lowpass heh
eMPee584 said:
not my device but when investigating this same issue.. dug deep and figured it out. So0Oo..
Click to expand...
Click to collapse
Anyway I can try this out?
Sent from my Nexus 7 using xda premium
reading comprehension: mediocre.. at most^^
bcvictory said:
Anyway I can try this out?
Click to expand...
Click to collapse
a) yes, become an android developer and compile your own rom OR WAIT for actual developers to do the work .
b) please don't FULL QUOTE huge posts without reason (edit your post please!), it just makes threads that much harder to read .
eMPee584 said:
a) yes, become an android developer and compile your own rom OR WAIT for actual developers to do the work .
b) please don't FULL QUOTE huge posts without reason (edit your post please!), it just makes threads that much harder to read .
Click to expand...
Click to collapse
Mate don't jump down my throat haha. I haven't got the pc hardware needed to make a rom. Otherwise I would
Sent from my Nexus 7 using xda premium
bcvictory said:
Mate don't jump down my throat haha.
Click to expand...
Click to collapse
well then PLEASE be more considerate of your behaviour starting NOW aight. :good:
TO MUCH SPAM on the XDA development section..
It's making actual information exchange about development so much harder = slower development
eMPee584 said:
well then PLEASE be more considerate of your behaviour starting NOW aight. :good:
TO MUCH SPAM on the XDA development section..
It's making actual information exchange about development so much harder = slower development
Click to expand...
Click to collapse
First, this isn't in the dev section. Second, I've been here longer than you and I hate spam too.
Sent from my Nexus 7 using xda premium
Related
Hey guys! We are about to release an application for tablets and phones that will allow you to put the device into standby just by closing the case.
A closed beta is available to select XDA members, and we would like to test more on people's XOOMs.
You can find the app thread HERE.
i'll beta test it.
What kind of Case must you use for the Xoom, the portfolio one Moto puts out?
Count me in for this one.
Sent from my Xoom using Tapatalk
I'm in as well. Sounds fantastic
Sent from my Xoom using XDA App
sure I'll test it
Count me in. I have a xoom and a galaxy tab.
Sent from my SCH-I500 using Tapatalk
count me too.
I noticed a little bug. As I move back and forth at my desk. The program tries to close my screen. Is there a way to uninstall this?
Sent from my Xoom using XDA App
Guys, developer already wrote that they took 10 (!) testers and others just missed the train, so we shall wait for an open beta test if there will be any (doubt it will)
I got in on the test. I have noticed one problem. If someone stands over you or there is a shadow killswitch will start to engage. It maybe a setting just need to play w/ it more.
Hey everyone, and thanks to all the beta testers! Just an FIY, the app is now out, you can find its thread in the Paid Software Announcement and Discussion forum:
http://forum.xda-developers.com/showthread.php?t=988126
It has now been tested thorougly on my own Xoom and is working fine! To avoid accidental activations, read the Help and Tips section carefully and set a higher activation delay time.
I have it at 8 seconds and rarely have any issues...
Great, works fine on all my devices
Eer, this expired a month ago!
Hi ... I just purchased this and figured I would be able to spoof a cover by simply covering the sensor (at the opposite location to the camera) with my finger briefly but this doesn't seem to do the trick, but if I cover the front with a pad then it does go off. Is there another sensor I am not seeing?
I also expected it to auto wake when uncovered? If I enable unlock on screen then the volume keys at least seem to wake it up which is a bonus I guess
Sent from my MZ604 using XDA Premium App
The light sensor is quite hard to spot. Its 2.5 cm to the left of the front facing camera.
The autounlock feature is supposed to work like that. Please, read the help file!
Great ... that makes it easier to test ... but I can't get it to wake. It seems the volume key is not even waking it now either.
Sent from my MZ604 using XDA Premium App
This functionality is broken by tegra drivers on honeycomb - but works on all other devices...
OK... so are you working to get around this? Or will 3.1 fix it? Or is the function just broken forever? Without it the app is nowhere near as useful :-(
sent from my mz604
you live and learn ... at any rate you live
Weve been busy prepping for the release of RCB and i havent had time to tinker with killswitch for a few weeks!
I have thought about it though, and there is a workaround. Trouble is, it would mean the tablet wouldnt really sleep.
However... there is a hack i have been using myself, but it would mean root and some nasty errors on many devices.
Atm you can already do something similar yourself using a key remapper. Search the forums for a compatible one.
I promise though i will add some root functions to killswitch.
I have to say, my experience so far with getting my NC up and running with CM7 has been very positive so far. I'm running it from the SD and OC @ 1.1ghz. Just a great experience all around. I'm still considering a Xoom somewhere down the road but no rush now.
I wasn't going to buy it as I had a Kindle but I have to say, this really has so much more potential, I just couldn't say no.
Anyways, just wanted to pass along my positive experience and look forward to learning a bunch more from all the smart people around here.
I'm gonna add a question here as I don't want to make another thread.
One thing I'm slightly frustrated with, and really it's very minor, I have some difficulty with swiping through menus and accidentally selecting whatever happens to be at the location I start my swipe.
For example: When I'm scrolling through a web page, I'll press somewhere close to the bottom and drag up to scroll down the page. For some reason, this typically will launch a link if that happens to be around where my finger touches the screen initially. Or if I'm in 'Settings' and scrolling through the screen to go further down, this usually opens a misc option or checks/unchecks a box, etc. I don't know what else to do but is there a setting or something that will stall the OS from reacting so quickly?
If I click and hold, then drag, it seems to work ok. But this is something that's not really natural to me. I'll say now that I've used an iPhone and iPad and never had this type of quirky/touchy response. Is it just me?
Yea BN missed the boat. They could if given it full aosp android and probbley spent less software development money and charged more money.
Sent from my SGH-I897 using Tapatalk
Do you use your stock BN home? It is laggy but I overclocked with Dal's 1.1 oc kernel for bn 1.2 and now things are snappy! I also use Phiremod 6.2 from sd which is a rocket!
Sent from my SAMSUNG-SGH-I897 using XDA App
Kadin said:
I'm gonna add a question here as I don't want to make another thread.
One thing I'm slightly frustrated with, and really it's very minor, I have some difficulty with swiping through menus and accidentally selecting whatever happens to be at the location I start my swipe.
For example: When I'm scrolling through a web page, I'll press somewhere close to the bottom and drag up to scroll down the page. For some reason, this typically will launch a link if that happens to be around where my finger touches the screen initially. Or if I'm in 'Settings' and scrolling through the screen to go further down, this usually opens a misc option or checks/unchecks a box, etc. I don't know what else to do but is there a setting or something that will stall the OS from reacting so quickly?
If I click and hold, then drag, it seems to work ok. But this is something that's not really natural to me. I'll say now that I've used an iPhone and iPad and never had this type of quirky/touchy response. Is it just me?
Click to expand...
Click to collapse
I had this same problem until I installed a screen protector and it solved all of my touch screen issues!
Jimbo67 said:
I had this same problem until I installed a screen protector and it solved all of my touch screen issues!
Click to expand...
Click to collapse
Interesting... I never thought about that. If I may ask, where did you get it and how much was it? Does it take away much from the image quality?
Garoto1973 said:
Do you use your stock BN home? It is laggy but I overclocked with Dal's 1.1 oc kernel for bn 1.2 and now things are snappy! I also use Phiremod 6.2 from sd which is a rocket!
Click to expand...
Click to collapse
I use the stock 1.2 without any type of modifications. I haven't found the need to do much to it as it runs pretty smooth. Although I maybe only run that mode 10% of the time, if that...
Kadin said:
Interesting... I never thought about that. If I may ask, where did you get it and how much was it? Does it take away much from the image quality?
Click to expand...
Click to collapse
I picked up an anti-glare screen protector on Amazon.com, but I can't remember which one it was. I bought it mainly to just protect the screen from scratches, but it really cuts the glare and doesn't show fingerprints as easily as the bare screen.
It doesn't degrade image quality at all, although I bumped up the screen's brightness just a hair to compensate.
----------------------------------------------------------
Sent from my Palm Pilot III
tjsooley said:
Yea BN missed the boat. They could if given it full aosp android and probbley spent less software development money and charged more money.
Sent from my SGH-I897 using Tapatalk
Click to expand...
Click to collapse
IDK, the stock interface is accessible for the computer-illiterate and the hardware configuration is equally accessible for all levels of power-users. I pretty much forgive all shortcomings in the stock OS because B&N made no effort to lock me into using it, aside from withholding the magazine and kids book functionality in their Android Market app.
Since updating to 4.2, my screen brightness keeps going up and down from moment to moment, things generally run a bit slower, the lock screen is buggy and Quickoffice can no longer save changes to files. Not exactly a forward step.
Same here buddy, lockscreen takes a long time to respond
Sent from my MB526 using xda premium
I hate it when folks feel the need to start their own topic when there are 100 similar ones that would do.
Sent from my Nexus 7 using xda app-developers app
Are you sure you turned off automatic brightness?
Google released a bad update, I don't know why people yell at others for being upset. We didn't see threads like this at all for 4.11 or 4.12. Its obvious that Google obviously needs to work on this as people don't post threads like this for no reason.
Sent from my Nexus 7 using xda premium
blackhand1001 said:
Google released a bad update, I don't know why people yell at others for being upset. We didn't see threads like this at all for 4.11 or 4.12. Its obvious that Google obviously needs to work on this as people don't post threads like this for no reason.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If it was really a bad update, why doesn't it affect everyone? I have a stock locked tablet, and simply flashed Google's factory image.. No issue whatsoever!
Sent from my Nexus 7 using Tapatalk 2
I have almost only good experiences with the 4.2, generally feel more stable and haven't noticed any sluggish behaviour. Only problem Im having is with bluetooth, it won't remember profile selections for my paired devices. So everytime I connect to my phone for internet access I need to go and tick internet access under profiles
Sent from my Galaxy Nexus
The majority of people come here for solid technical advice, and some of this discussion hardly inspires confidence. We also need confidence in Google as we have invested in their product and it is perfectly legitimate to raise concerns about the 4.2 update that they pushed to our devices
If you use Bluetooth, for example to tether, then you will have been thrown by the changes to the interface. It was not obvious how to connect, and is actually quite inconsistent in that clicking the device name disconnects which is different to what's needed to connect.
One of the advantages the Nexus has over the Mini is the 16:10 screen great for widescreen movies. It's no surprise then that loss of USB mount (a feature available when many of us decided to buy the Nexus) has hit us hard. Yes there is a paid App which might allow movie streaming but I use the USB to extend storage for the huge game files we must download and so this is a major loss.
PromaneX said:
has a legitimate complaint - the update is terrible and people have every right to be upset about it.
Click to expand...
Click to collapse
l suppose google Should be the first stop, I'm sure they will be happy with the feedback.
Sent from my GT-N7105 using xda premium
I cant believe its not butter :/
On a serious note. I am yet to face any problems with 4.2. I like it alot. Battery life is great, keyboard is great and quick settings i love.
Just like 4.1.2 but with extras
Sent from my Nexus 7 using Tapatalk 2
stevensdrs said:
Since updating to 4.2, my screen brightness keeps going up and down from moment to moment, things generally run a bit slower, the lock screen is buggy and Quickoffice can no longer save changes to files. Not exactly a forward step.
Click to expand...
Click to collapse
Screen brightness is an isolated issue I suspect not caused directly by Android, as most people don't see it.
Everything runs just as fast as 4.1.
Quick Office has a coding problem, not Android.
Stop.
I have only seen 1 real bug in 4.2 and that's the missing December bug.
GldRush98 said:
Screen brightness is an isolated issue I suspect not caused directly by Android, as most people don't see it.
Everything runs just as fast as 4.1.
Quick Office has a coding problem, not Android.
Stop.
I have only seen 1 real bug in 4.2 and that's the missing December bug.
Click to expand...
Click to collapse
It is most certainly NOT as fast for me, just because it is ok on your device please don't assume everyone else's is the same!
I actually love 4.2. A little lag here and there, but I owned a Huawei Ascend with like a 500 mHz processor, a Samsung Sidekick 4G with a 1 gHz processor, and a Kindle fire. Seriously Google isn't perfect (but they are damn close) they released an update you don't like, does that mean you should cry and hit the new thread button? No, it means you should just flash 4.1.2 and save server space. Especially when there are 100 other topics exactly as useless as yours. We don't need more of them.
blackhand1001 said:
Google released a bad update, I don't know why people yell at others for being upset. We didn't see threads like this at all for 4.11 or 4.12. Its obvious that Google obviously needs to work on this as people don't post threads like this for no reason.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Clearly you and other folk unhappy with 4.2 should IMMEDIATELY upgrade to Windows Mojave. It will solve all your concerns. Pinky swear!!!
stevensdrs said:
Since updating to 4.2, my screen brightness keeps going up and down from moment to moment
Click to expand...
Click to collapse
Disable Nvidia PRISM. http://forum.xda-developers.com/showthread.php?t=1815414
android1234567 said:
Disable Nvidia PRISM. http://forum.xda-developers.com/showthread.php?t=1815414
Click to expand...
Click to collapse
Has nothing to do with Prism, the heuristics on the backlight seems to allow it to ramp up and down faster than it did before. In fact before the N7 seemed to be very stubborn to change levels, now it's a little too fast perhaps.
No matter what version or ROM I'm using I don't use automatic brightness. I use the lowest setting and adjust when I need to.
Sent from my Nexus 7 using xda premium
Hating it and loving it ? - wow these are strong words for an OS. Just like W8 people just can't work out whether its the cool thing to be for it or against it yet even though there's no need to take sides or feel possessive about it - we're all here just users equally dependant upon the working of Google aren't we?
One sure thing though - bugs will iron out but things like the way Bluetooth works now and the loss of USB mount are major hits for those of use dependant on those features for the last 4 months.
USB mounting was never part of 4.1... why are people suggesting it was? You needed root and stickmount or a custom ROM.
Stickmount will update eventually. Stop blaming Google for breaking something they never supported in the first place.
Sent from my Galaxy Nexus using Tapatalk 2
When using the pinch to zoom feature in the browser, gmail, maps etc I noticed there is a delay in that your fingers have to travel a certain distance before the phone/OS start reacting to the command and begin zooming, Once it begins to zoom its very responsive, it's just the initial delay when you first begin to initialize the zoom.
After the Jelly Bean update on my last phone the Galaxy Nexus I've become so accustom to a instantly responsive experience that this is driving me nuts. The phone is great in every other way, that's my only gripe but I haven't noticed anyone else complain which really surprises me. I'm really interested in trying this on the Optimus G to see if it's hardware related or the new version of Jelly Bean.
i believe its been like that for awhile. I guess its just the way android works. it doesnt want you to accidentally pinch to zoom when you might be trying to do something else
Yes, that's true. But the zooming out is not affected, only the zooming in. Should be a software issue. It doesn't bother me.
Sent from my Nexus 4 using xda app-developers app
düdldihüü said:
Yes, that's true. But the zooming out is not affected, only the zooming in. Should be a software issue. It doesn't bother me.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yep you're correct zooming out is not affected which lead me to realize something. If you space your finger apart and zoom you wont get the delay. So it's definitely something where the phone is not recognizing multi-touch input until your fingers are spaced out.
Yep. This isn't an issue with just gmail, try and zoom within gallery. It's almost too stiff.
Sent from my Nexus 4
seems not to be hardware related (puh...) check out this guy pinching and zooming on optimus g:
http://www.youtube.com/watch?v=05rSXn96QrU&feature=related#t=7m44s
its definatly not hardware related...see above post... as for the argument that androids been lik this for some time is horse apples... and there is only the zooming feature that involves multitouch in the UI ..so saying it is to avoid mistaken inputs is also wrong... its definatly a software BUG which is to be fixed...
It is a software problem. Basically the screen is set to recognise touches as taps even after a certain amount of movement and not as swipes to allow for some movement of the finger and not be overly sensitive. The SGS2 had this 'problem' as well, but a guy (I think his name is vitalij, not 100% sure though) found where this value was stored and it could be tweaked perfectly afterwards. So I wouldn't worry a lot about this, probably it'll be solved similarly in the foreseeable future.
btw guys check out firefox it doesnt have the problem!
its much better
i made a video here
http://www.youtube.com/watch?v=EU-N3mEOwU0
I tried a N4 today and it was present in the gallery but not maps.
ste1164 said:
I tried a N4 today and it was present in the gallery but not maps.
Click to expand...
Click to collapse
Very true, just tested, so far iv found it in all browsers except Firefox and in the gallery
This is probably just google designing around a patent. Function patents need to describe extremely specific methods. This lets you design around them. Some vendors (ahem, Samsung) tend to use the "best" way instead of properly designing around, but the reason that Apple hasn't attacked Google directly is because Google designs around pretty well.
I hope all of you guys are reporting this to google here:
http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=40445
Make a comment...the more comments, the higher on their priority it should become. Right now it only has a paltry 26 comments, so they won't think of it as a problem.
I'm suprised so few people are bothered by this issue. I for one am getting extremely annoyed everytime I try to zoom in the browser or gallery app. I settled with using just double tap for a while, since in my opinion pinching is not usable. I only just started using firefox. What a difference! Why the hell don't googles own app zoom properly like that??
I think it's a real shame googles own apps don't work properly on their own Nexus flagship phone for crying out load... this issue deserves more attention from google!
edit: I could not find a ticket about this specific issue (only about generic screen sensitivity) so I created one. If you think this issue is as annoying as I do, please star it/leave a comment so it will get noticed by google.
https://code.google.com/p/android/issues/detail?id=54093&thanks=54093&ts=1365444331
Is there a fix for this problem in any custom roms?
I don't find it that bad in gallery but I must admit that pinch to zoom on Chrome is a real nightmare for my eyes. Just try Firefox or aosp browser. The difference is heaven and earth. The best way to see the difference is to magnitude the view as much as you can and then swipe. Scrolling on Chrome will be just physically painful. Firefox or aosp browser feels incomparably smoother.
I also came from Galaxy Nexus and I agree totally with OP about its swiping experience. After JB update pinching to zoom was being registered instantly and swiping felt almost perfect. Perhaps it has something to do with the lower touch sensitivity (due to new drivers that came with 4.2.2).
Sent from my Nexus 4 using xda premium
In the MIUI Rom there's not the pinch to zoom issue. Hope someone can use it to solve the problem once and for all
If you want an instant pinch to zoom just put your fingers a little bit far from each other when you start pinching.
This is why zooming in works well for you guys
I was reading that the Galaxy uses its Infrared technology for its Air View application, does anyone know if we would be able to utilize Air View on the HTC One or if there is an similar application?
derrick8 said:
I was reading that the Galaxy uses its Infrared technology for its Air View application, does anyone know if we would be able to utilize Air View on the HTC One or if there is an similar application?
Click to expand...
Click to collapse
What does it do?
It has another sensor up front for that purpose I believe
Sent from my HTCONE using xda app-developers app
raptoro07 said:
What does it do?
Click to expand...
Click to collapse
It uses sort of a hands free function: you can use your hand as a wave gesture to swipe pages horizontal/vertically, it has a feature that if you look away from a video it will automatically pause, etc.
Sounds like a useless gimmick. My Evo 3D had an overly sensitive screen, didn't always have to touch the screen, just be close, and it detected touch. It was pretty annoying.
Sent from my HTCONE using xda app-developers app
gk1984 said:
Sounds like a useless gimmick. My Evo 3D had an overly sensitive screen, didn't always have to touch the screen, just be close, and it detected touch. It was pretty annoying.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Really, I didnt get the Evo 3D so never had the option of that software, man these commercials really make certain apps look brillant
derrick8 said:
Really, I didnt get the Evo 3D so never had the option of that software, man these commercials really make certain apps look brillant
Click to expand...
Click to collapse
Lol it was more of a flaw... It was never intended to be like that but it would randomly register touches from your finger before you touched the screen.
derrick8 said:
It uses sort of a hands free function: you can use your hand as a wave gesture to swipe pages horizontal/vertically, it has a feature that if you look away from a video it will automatically pause, etc.
Click to expand...
Click to collapse
If it did you wouldn't want it. The accuracy required to make these gestures reliable is way beyond the technology the S4 has in it, which is why reviewers say it's a gimmick. It either triggers when you don't want it, or doesn't when you do. You'd need something like a Kinect strapped to the top of your phone to really pull that off. The battery drain alone would be devastating.
Add in it likely won't function on any ported ROM or new versions of android. It will be very similar to the 3D where the drivers and other needed stuff won't be available to make it work. One reason I avoided Samsung.
Sent from The ONE using xda premium
the S4 has a specific sensor just to the right of the earpiece speaker for the air gestures. its not as accurate as they make it seem just like the eye tracking isnt very good either. like previously stated its a gimmick. your average consumer is WOWED by stupid crap like that. i felt like an idiot swiping my hand in front of the phone and when using eye scrolling you have to physically tilt your head up and down. all the phone is doing is tracking the movement of your head and using your eyes as a focal point to base amount of movement off of. not to mention you cant be more than a foot or two from the sensor. if you wear glasses like me its really a pain. i guess the reflection in the lenses of the glasses makes it react funny. ive only played with the s4 for a couple days when ive been at my store but all in all im not impressed. im wondering if it will gradually learn your personal body movements and become more accurate. it seems like they took an S3 made the viewing area slightly bigger, new camera, and stupid gesture sensor. if it worked as well as Tony Starks stuff it might be worth playing with lol. even then though its not practical its just something that looks neat when you can get it to work. you can also use Svoice from the lock screen so say you name your phone then hold home key say name so svoice will launch then you say name again to start a command. the ability to launch from lock screen makes me wonder if it will have security issues like the S3 did. i also feel like me having to address the device twice in a row is dumb. i should say "S4 call ...." or "S4 launch ...." not say "s4" wait for svoice "S4 call...." or "S4" wait a few secs "S4 launch...." again i felt like an idiot standing there making swipes and repeatedly saying "S4..." thats just what i named the one at our store. i like google now bc i launch it then say "google" it beeps i say "search target.com for..." and it goes. i wish it worked better as a launcher for apps or taking appointments, sending emails, texts, ect.. i will say svoice has that going for it.
in the end im still holding out for black 64gb HTC One. im getting ready to make a sacrifice to cellphone gods if i dont hear something official soon.
xanmanz31 said:
i wish it worked better as a launcher for apps or taking appointments, sending emails, texts, ect.. i will say svoice has that going for it.
Click to expand...
Click to collapse
Google Now can do all of those things.
Seems like more of a headache than it's worth trying to get it on the HTC One.