Related
The DX specific changes with the Froyo update that I've noticed:
• Better text zoom bubble for cursor placement and text selection. Faster. Nicely shifted up, so not as covered by finger.
• Swype looks nicer, also seems quicker/smoother.
• Clock in notif bar now shows AM/PM (seems a waste of space).
Anything else that's not general to Froyo?
e.g.
A couple of more that I noticed....
- Lock screen is different.
- Some minor changes to gmail(even before the new 2.2 version of gmail). You can now click to the next message without going back to the inbox first.
In addition to what you guys mentioned... the gallery has changed, they added a file explorer program, and the phone seems to run quite a bit faster (I'm using LauncherPro Plus, not the stock launcher). They said they were going to improve the weather and calendar widgets, but I didn't notice any change.
New camera app that was in the leaked build?
Don't notice any difference in Files program, using LauncherPro but not plus. Phone seems to respond faster. Quadrant up from 1290's to 1400+ however stopping services seems slower?
How are you guys getting 1400+ in Quadrant? My highest run was 1375. So far FroYo has been good except I'm not sure if I like the removal of the .com button in the browser keyboard.
m2thedeep said:
How are you guys getting 1400+ in Quadrant? My highest run was 1375. So far FroYo has been good except I'm not sure if I like the removal of the .com button in the browser keyboard.
Click to expand...
Click to collapse
Reran Quadrant now 1445,seems to getting faster, previous run was 1403.
Quadrant up to 1513 then , when pressing menu button settings was unresponsive so rebooted , now working ,will monitor , quadrant now high 1390's FWIW
Now back up to high 1400's , phone is stable and everything's appears to be working. Youtube is great.
Holding down "Home" button gives you a Recent App window. Somewhat same as before but I think it looks nicer.
Long hold on Magnify glass button gives you a speak-to-search tutorial. Was this available on 2.1?
Voice Actions is only available in 2.2
toddman said:
Long hold on Magnify glass button gives you a speak-to-search tutorial. Was this available on 2.1?
Click to expand...
Click to collapse
They changed the way the period and comma work. Before you could double tap that button to switch between period and comma, now its period by default and you have to long press for other punctuation. Overall I find it a little annoying and makes it take longer for me to text because I have to wait for a comma.
Also they changed something with the autocorrect/predictive text but I'm not exactly sure how. All I know is,sometimes after I'm done typing a text, I hit done, go to hit send (muscle memory, without looking at the screen) and somehow accidentally end up changing a word in the text message based off of a predictive text list that is still active underneath the text window. I'm not sure why it stays afterwards.
Has anyone else had any trouble playing media like pandora and mp3's? It will play for awhile and then it says media type not recognized and I have to reboot. Once I reboot my mp3 plays just fine then does it again.
Sent from my DROIDX using XDA App
skraapz27 said:
Has anyone else had any trouble playing media like pandora and mp3's? It will play for awhile and then it says media type not recognized and I have to reboot. Once I reboot my mp3 plays just fine then does it again.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Pandora works fine for me, although lately I've gotten a lot of error messages in the beginning when I First open it, but they don't seem to affect playback. I haven't really tried many MP3s, but I have noticed videos, specifically videos that I actually took with the camera, are giving me that exact same behavior. It says it's unsupported, and then if I reboot it works for a little while, then stops working again.
Have any of you gone from the 2.2 leak to 2.2 OTA? The OTA will have a newer kernel and baseband and I am curious to know if a performance increase is noticeable going from the Leak to OTA.
I have this problem. Had to reset the phone to get it to stop. Very annoying issue.
skraapz27 said:
Has anyone else had any trouble playing media like pandora and mp3's? It will play for awhile and then it says media type not recognized and I have to reboot. Once I reboot my mp3 plays just fine then does it again.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Sent from my DROIDX using XDA App
There is now a HDMI option in the media player. I haven't tested it but I don't remember seeing it in Eclair.
TheFuzz said:
I have this problem. Had to reset the phone to get it to stop. Very annoying issue.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
I'm glad its not just me its.really frustrating.
Sent from my DROIDX using XDA App
Problem #1: lack of hotkeys. Control T, Control F, etc do not work.
Problem #2: "Shift + c" is mapped to "backspace", and "Shift + b" is bound to enter. The only way to type a capital C or B in Chrome is to hit the key twice in rapid succession, which first causes a backspace/enter, then types the letter.
If you all could so kindly go into Chrome, go to settings, click Under The Hood, click Send Feedback, and write off a quick description of the problem to Google, let's try to get them to fix it. Google's support is typically pretty lackluster, and it generally takes many people acknowledging and reporting a problem to get it fixed!
I'm still god damn floored by how awesome Chrome is. JSNES (NES emulator written in JavaScript) runs at 25 FPS in Super Mario Bros. That benchmark alone gets me a little hard, as my old notebook doesn't even handle it that well. But with the above two problems, it's kinda annoying to use it, especially the lack of control T to open new tab as that's just become instinctual over the past 8 years.
Sent from my Transformer TF101 using Tapatalk
Huh...I can't reproduce the issue on mine (Shift-B and Shift-C work fine). No CTRL+T or CTRL+F, but the cut/copy/paste shortcut keys work fine.
Gary13579 said:
I'm still god damn floored by how awesome Chrome is. JSNES (NES emulator written in JavaScript) runs at 25 FPS in Super Mario Bros. That benchmark alone gets me a little hard, as my old notebook doesn't even handle it that well. But with the above two problems, it's kinda annoying to use it, especially the lack of control T to open new tab as that's just become instinctual over the past 8 years.
Click to expand...
Click to collapse
I'm not familiar with JSNES, what's it do in the old browser? I ask because on a completely stock, just-wiped US TF101 running ICS, I get a slightly (but outside margin of error) *worse* Javascript score in the Chrome beta, than I do with the stock browser. I also find the scrolling lag on Chrome beta to be awful -- the stock browser is orders of magnitude better.
I want to like Chome, and I'm sure I will eventually when the bugs are worked out, but so far it isn't usable for my purposes.
Perhaps related to the scrolling thing, I also noticed if I check chrome://gpu-internals/ that I get "WebGL: Unavailable. Hardware acceleration disabled." and "Problems detected. WebGL has been disabled, either via about:flags or command line."
Edit: No, not related. Just googled and now know WebGL's for 3D graphics.
laslow said:
Huh...I can't reproduce the issue on mine (Shift-B and Shift-C work fine). No CTRL+T or CTRL+F, but the cut/copy/paste shortcut keys work fine.
Click to expand...
Click to collapse
Where did you try it? It only occurs in text boxes within the actual page. In the URL bar and other places, Shift C/B work fine, but if you try to respond to this post in Chrome and use shift C, it should backspace. It also makes capital C and B impossible to enter in password fields -- really annoying.
knoxploration said:
I'm not familiar with JSNES, what's it do in the old browser? I ask because on a completely stock, just-wiped US TF101 running ICS, I get a slightly (but outside margin of error) *worse* Javascript score in the Chrome beta, than I do with the stock browser. I also find the scrolling lag on Chrome beta to be awful -- the stock browser is orders of magnitude better.
I want to like Chome, and I'm sure I will eventually when the bugs are worked out, but so far it isn't usable for my purposes.
Perhaps related to the scrolling thing, I also noticed if I check chrome://gpu-internals/ that I get "WebGL: Unavailable. Hardware acceleration disabled." and "Problems detected. WebGL has been disabled, either via about:flags or command line."
Edit: No, not related. Just googled and now know WebGL's for 3D graphics.
Click to expand...
Click to collapse
It ran fine in the HC browser, just slow. To be fair I checked it in ICS browser and it gets the same FPS as Chrome, glad to know stock ICS browser is just as capable, but it doesn't handle the actual page anywhere near as well as Chrome does, for ex it cannot hook the keys to get keyboard input like Chrome does. I suspect Chrome's compatibility far surpasses that of the stock browser, perhaps costing it a bit of performance in benchmarks?
Haven't really had any scrolling issues whatsoever.
Sent from my Transformer TF101 using Tapatalk
Gary13579 said:
It ran fine in the HC browser, just slow. To be fair I checked it in ICS browser and it gets the same FPS as Chrome, glad to know stock ICS browser is just as capable, but it doesn't handle the actual page anywhere near as well as Chrome does, for ex it cannot hook the keys to get keyboard input like Chrome does. I suspect Chrome's compatibility far surpasses that of the stock browser, perhaps costing it a bit of performance in benchmarks?
Click to expand...
Click to collapse
Well, to be equally fair in return, it was only a very slight difference in benchmark, and it was just one benchmark -- Sunspider -- I didn't try any others.
Gary13579 said:
Haven't really had any scrolling issues whatsoever.
Click to expand...
Click to collapse
Interesting. Pretty-much any long web page (say, Engadget or similar), if I load the page, let it finish loading, then swipe my finger across the screen to scroll, I'm instantly into a white page until I stop scrolling, or at the very least I get significant stuttering. With the stock browser, the same trick gives me a perfect preview of the fast scroll, so I can stop it in the right place with a tap of my finger.
Even when scrolling slowly, Chrome is noticeably stuttery for me, nowhere near as smooth as the stock browser's scrolling.
Gary13579 said:
Problem #1: lack of hotkeys. Control T, Control F, etc do not work.
Problem #2: "Shift + c" is mapped to "backspace", and "Shift + b" is bound to enter. The only way to type a capital C or B in Chrome is to hit the key twice in rapid succession, which first causes a backspace/enter, then types the letter.
If you all could so kindly go into Chrome, go to settings, click Under The Hood, click Send Feedback, and write off a quick description of the problem to Google, let's try to get them to fix it. Google's support is typically pretty lackluster, and it generally takes many people acknowledging and reporting a problem to get it fixed!
I'm still god damn floored by how awesome Chrome is. JSNES (NES emulator written in JavaScript) runs at 25 FPS in Super Mario Bros. That benchmark alone gets me a little hard, as my old notebook doesn't even handle it that well. But with the above two problems, it's kinda annoying to use it, especially the lack of control T to open new tab as that's just become instinctual over the past 8 years.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Yep. I concur... The shift c, b is a pain in the ass. Also having the lagging problems.
Anyway, i'm back to stock browser.
control c and control v work fine for me, make sure you have asus keyboard set
wilx said:
control c and control v work fine for me, make sure you have asus keyboard set
Click to expand...
Click to collapse
I never said they didn't. Try reading, this time.
Sent from my Transformer TF101 using Tapatalk
Gary13579 said:
Where did you try it? It only occurs in text boxes within the actual page. In the URL bar and other places, Shift C/B work fine, but if you try to respond to this post in Chrome and use shift C, it should backspace. It also makes capital C and B impossible to enter in password fields -- really annoying.
Click to expand...
Click to collapse
Well, I'm using the hardware keyboard to type this reply -- BBBBCCCCCBCBCBC -- and I used it to login here and a number of other places. I'd say that no, I really can't reproduce it, whether the Asus, Android, or Swype virtual keyboard is enabled along with the hardware keyboard.
laslow said:
Well, I'm using the hardware keyboard to type this reply -- BBBBCCCCCBCBCBC -- and I used it to login here and a number of other places. I'd say that no, I really can't reproduce it, whether the Asus, Android, or Swype virtual keyboard is enabled along with the hardware keyboard.
Click to expand...
Click to collapse
Interesting. Lates t version of chrome from the market? What region ICS version? What version dock? You are doing this in CHROME, right? It's affecting a lot of us, interesting that it works for some. The same problem even occurs on the TF Prime. You spamming the keys doesn't really show that it's working though, as if you hold shift and hit "c" twice, it will backspace once then type out C, but when you press down shift, hit c, then let go of shift, it only does a backspace.
Sent from my Transformer TF101 using Tapatalk
US region ICS, dock version EP101-0213. Yes, this is the latest Chrome Beta from the market. Yes, I'm actually using the hardware keyboard, and yes I'm actually typing this through Chrome. The keyboard spam was for effect - if you read my post you would have noticed I also said that I had used the above to login in to different places (the problem doesn't happen text inputs, text areas, or password inputs). Yes, other people are having the issue, but I'm not.
If you're interested, I did a clean install of the official .21 HC firmware (with a wipe), then did the OTA update and wiped it again before rooting it.
Hadn't actually tried it myself, so here's a fourth (fifth? forget how many replies we've had...) opinion:
* Ctrl-T, Ctrl-F, Ctrl-N: Do not work
* C and B type just fine for me on the first try, by holding down shift and typing the letter on the physical keyboard, in Chrome. That's how I just did it, in this post. No backspace, no enter for either combination.
I have a B60 dock with EP101-0213, a just-wiped, unrooted, stock ICS US build, and although I'm using the physical keyboard to type the whole of this post, I'm set to the stock ICS soft keyboard, not Asus' modified one.
I, too, did a double-wipe, once before updating and once after ICS was installed.
I can only reproduce this when I have the ASUS keyboard selected. Using the normal Android one it's not reproducable.
So, that's a workaround if anything.
Radiofodder said:
I can only reproduce this when I have the ASUS keyboard selected. Using the normal Android one it's not reproducable.
So, that's a workaround if anything.
Click to expand...
Click to collapse
Just tested that myself: yes, Shift-C and Shift-B don't work when the Asus soft keyboard is selected.
This is an Asus problem, not a Google problem.
Radiofodder said:
I can only reproduce this when I have the ASUS keyboard selected. Using the normal Android one it's not reproducable.
So, that's a workaround if anything.
Click to expand...
Click to collapse
Interesting, this does fix it for me now, even though I had tried it previously. It makes me wonder, what "compatibility" does ASUS speak of when you get the warning message using stock ICS keyboard with the dock? Thinking back to when I was using thumb keyboard on HC, I never noticed any issues not having the ASUS keyboard enabled.
Sent from my Transformer TF101 using Tapatalk
Beats me, I've yet to find any slight incompatibility between the physical keyboard and the stock ICS keyboard. I wonder if they're not suggesting an incompatibility with the stock one, but rather practicing CYA with respect to all the other third-party keyboards on the market?
Does the ASUS keyboard need to be used only if you want access to all of the hotkeys on the dock (Transformer Prime)? Or is there any other reason not to switch over to the standard keyboard to avoid the SHIFT-C bug?
There is something specifically related to Chrome here. The standard browser has no problem with SHIFT-C or B using the dock w/ASUS keyboard selected. Chrome is the only application I have found that has this problem.
shuddles said:
Does the ASUS keyboard need to be used only if you want access to all of the hotkeys on the dock (Transformer Prime)? Or is there any other reason not to switch over to the standard keyboard to avoid the SHIFT-C bug?
Click to expand...
Click to collapse
Can't speak to the Prime, but with the TF101, the hotkeys work just fine regardless of which soft keyboard you're using, the Asus one or the stock one. Just tested, I don't use the Asus one, I'm on the stock ICS keyboard but I just tested and absolutely every hotkey works correctly regardless.
The only problem I've encountered is that special characters specific for your language will not work properly. Or in my case, åäö. You can still do capital Bs and Cs - just click B and C again after typing it and it should pop. Fiddly as hell, but I'm sure if enough users report it something will be done.
Bloody' ell, the Asus keyboard isn't exactly a thing of dreams.
Radiofodder said:
The only problem I've encountered is that special characters specific for your language will not work properly. Or in my case, åäö. You can still do capital Bs and Cs - just click B and C again after typing it and it should pop. Fiddly as hell, but I'm sure if enough users report it something will be done.
Bloody' ell, the Asus keyboard isn't exactly a thing of dreams.
Click to expand...
Click to collapse
Interesting, so for native English speakers, there's basically no reason to use the Asus soft keyboard then. Unless for some strange reason you like it, that is.
So I was so tired of not being able to long-press the upper row of the keyboard to input numbers, so I remember reading somewhere that Google had updated the keyboard with this feature for tablets, to my surprise, Play Store didn't notice any update, so I tried installing it from the play store website like I do pretty much always, and I got the update pushed to my phone.
I attach the link to the playstore here, even if it says INSTALLED, click on it and you will get the option to install it on the devices linked to your account.
https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin
My keyboard gets the numbers on the top row now. Thanks!
Shame I paid for SwiftKey 1 week prior to get that feature.
Bah
Sent from my Nexus 7
oldtimer42 said:
Shame I paid for SwiftKey 1 week prior to get that feature.
Bah
Sent from my Nexus 7
Click to expand...
Click to collapse
Don't regret it: SwiftKey is far better than the "standard" Android Keyboard!
henklbr said:
Don't regret it: SwiftKey is far better than the "standard" Android Keyboard!
Click to expand...
Click to collapse
Indeed. One of the best features for me is reducing "hold" time for secondary characters.
Sent from my Nexus 4 using Tapatalk 2
henklbr said:
Don't regret it: SwiftKey is far better than the "standard" Android Keyboard!
Click to expand...
Click to collapse
Different strokes for different folks. I prefer SwiftKey's functionality, but there's something about "stock" that's always appealing for me.
Thanks for letting us know. I'm a bit confused why keep this update hidden and not notify the users like a normal app would do, That's weird !
Sent from my Nexus 7 using Tapatalk 4
Huh, the Google Keyboard update installed automatically for me just fine, right when it came out.
undercover said:
Indeed. One of the best features for me is reducing "hold" time for secondary characters.
Click to expand...
Click to collapse
Google Keyboard can also do this.
Hmmmm. Didn't do anything for me. Couldn't push it from a PC, the option was grayed out for my N7. Went into apps, installed updates, forced closed, went to the play store and updated ... nada. Using Swype, so no biggie, but still...
PJ Clifford said:
Hmmmm. Didn't do anything for me. Couldn't push it from a PC, the option was grayed out for my N7. Went into apps, installed updates, forced closed, went to the play store and updated ... nada. Using Swype, so no biggie, but still...
Click to expand...
Click to collapse
Try opening the play store page on the tablet, and clicking install from the webpage open in the tablet.
jak3z said:
Try opening the play store page on the tablet, and clicking install from the webpage open in the tablet.
Click to expand...
Click to collapse
Did that and it didn't work. Ah well, as I said no big matter as I am using Swype anyway.
Guys, I've installed the last version from play store.
I have a problem that it seems to exist only on my (actually my wife's) N7II. I don't have it on other "regular" android phones...
When I press a key, I don't get that blue pop-up with the key pressed, if u know what I mean...
Does anyone get the key pressed on the blue pop-up ?!?
I searched on settings, but I haven't found nothing related to this...
Is this a bug or does it work like this on tablets (or at least on N7) ? Can also be a 4.3 bug??
Best keyboard setup with google keyboard is advanced setting, custom input styles, english (us) (pc). Gives you a pc keyboard layout. Numbers on top and symbols like your familiar qwerty pc board. Keys get small on portrait but thats what swyping is for.
onesolo said:
Guys, I've installed the last version from play store.
I have a problem that it seems to exist only on my (actually my wife's) N7II. I don't have it on other "regular" android phones...
When I press a key, I don't get that blue pop-up with the key pressed, if u know what I mean...
Does anyone get the key pressed on the blue pop-up ?!?
I searched on settings, but I haven't found nothing related to this...
Is this a bug or does it work like this on tablets (or at least on N7) ? Can also be a 4.3 bug??
Click to expand...
Click to collapse
No one?!?
onesolo said:
No one?!?
Click to expand...
Click to collapse
What do you mean, "blue pop-up"? Letters don't "pop up" on the stock Android keyboard unless you hold down the key to select, say, a number or symbol.
hyperspacey said:
What do you mean, "blue pop-up"? Letters don't "pop up" on the stock Android keyboard unless you hold down the key to select, say, a number or symbol.
Click to expand...
Click to collapse
But on my Samsung S3, Desire HD, Huwaei X5 (and so on...) it shows the contrary ...when I touch (or hold down, it's indifferent) a key on those devices I get that blue popup
Oh, and now I went to the keyboard settings and there is an option for that: "Popup on Keypress"
If I disable it, it wont show that popup as natural.
On N7 I can't remember quite if it's there and if it's enabled or not... only at night when I came back home...
Maybe this is a phone feature, maybe it's a nexus bug, a 4.3 bug... who knows...
onesolo said:
But on my Samsung S3, Desire HD, Huwaei X5 (and so on...) it shows the contrary ...when I touch (or hold down, it's indifferent) a key on those devices I get that blue popup
Oh, and now I went to the keyboard settings and there is an option for that: "Popup on Keypress"
If I disable it, it wont show that popup as natural.
On N7 I can't remember quite if it's there and if it's enabled or not... only at night when I came back home...
Maybe this is a phone feature, maybe it's a nexus bug, a 4.3 bug... who knows...
Click to expand...
Click to collapse
None of those other phones ship with the stock Android keyboard- the S3 in particular uses Samsung's keyboard app, the Desire HD uses HTC's, the X5 Huawei's own app, etc. This is the stock keyboard app that is on Nexus devices: https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin&hl=en
Edit- I've had a check, on tablets it doesn't do the pop-up because the keyboard is big enough for you to see the letters. Swiftkey does, I think. Try Swiftkey!
hyperspacey said:
Edit- I've had a check, on tablets it doesn't do the pop-up because the keyboard is big enough for you to see the letters. Swiftkey does, I think. Try Swiftkey!
Click to expand...
Click to collapse
But I think this is stupid... altought the kayboard is big enough I would love to see the letters popup... sometimes I just can't see it...
Anyone else having this problem? https://code.google.com/p/android/issues/detail?id=62366
Me and my brother both use Google Play Books to read e-books. I use the Owner account whereas my brother is using a Secondary account I created for him.
Every time my brother opens an e-book, the touchscreen functions fine as along as the Immersive mode is not enabled. However as soon as it enables (i.e. Navigation bar and Notification bar disappear) the touchscreen locks out and stops responding. No matter how much I touch the screen, it remains locked. The only workaround is to use the Volume button to turn pages or hold the Power button to bring the Navigation bar back and close the Play Books app.
Device specifics:
- Asus Google Nexus 7 Wifi (nakasi)
- Android 4.4 Kitkat
- Build: KRT16O
- Using default Launcher (that was shipped with 4.4 OTA)
Video: https://docs.google.com/file/d/0B_NwBQSIC6akT25mXzRWYzh0eG8
Please note that the user with the Blue Wallpaper is the Owner, and the user with the Red Wallpaper is the Secondary User.
In this video I first show how the screen does not respond(in Immersive Mode) in the Secondary User, then I show how the pages can still be turned using the Volume button and lastly how Immersive mode works fine when in the Primary User.
This problem also occours with MX Player.
Click to expand...
Click to collapse
Yes!!! I'm totally having this same exact issue. I tried removing the secondary account and remaking it. Did not work. Now, I did notice that there was a brief tutorial on the new features of KitKat on the primary account when I opened Books. I didn't see that on the secondary axcount. That's before and after the wipe of the secondary account.
So I got a response from Google. They suggested a factory reset. Unfortunately, I'm using my work tablet, and that's not an option for me. If you end up trying that, let me know if it solves your issue.
I have the same issue and wipes secondary account not work for me too : (
i hopefull google fix this
+1 here as well. I thought it was just my tablet being stupid but after reading this I decided to check using the main profile. Bloody annoying to tell you the truth. I'm the main user of the tablet anyway but can't be bothered resetting everything and changing the users over.
After seeing all the 'benefits' of upgrading to kitkat, I'll have to say, if I knew about this I wouldn't have upgraded.
My case isn't as bad though, I can still swipe to get the toolbar etc back. It's just while in immersive mode, I can't do anything.
Maybe I should just my ass into gear change the users over.
Wes Janson said:
So I got a response from Google. They suggested a factory reset. Unfortunately, I'm using my work tablet, and that's not an option for me. If you end up trying that, let me know if it solves your issue.
Click to expand...
Click to collapse
I can't believe Google actually told you to do a reset? I mean Google must have tested Immersive Mode before actually releasing it. And secondly, this problem is pretty widespread, occurs on ALL Nexus tablets including the 2013 N7 and the N10.
Wes Janson said:
Yes!!! I'm totally having this same exact issue. I tried removing the secondary account and remaking it. Did not work. Now, I did notice that there was a brief tutorial on the new features of KitKat on the primary account when I opened Books. I didn't see that on the secondary axcount. That's before and after the wipe of the secondary account.
Click to expand...
Click to collapse
biondi53 said:
I have the same issue and wipes secondary account not work for me too : (
i hopefull google fix this
Click to expand...
Click to collapse
ckai said:
+1 here as well. I thought it was just my tablet being stupid but after reading this I decided to check using the main profile. Bloody annoying to tell you the truth. I'm the main user of the tablet anyway but can't be bothered resetting everything and changing the users over.
After seeing all the 'benefits' of upgrading to kitkat, I'll have to say, if I knew about this I wouldn't have upgraded.
My case isn't as bad though, I can still swipe to get the toolbar etc back. It's just while in immersive mode, I can't do anything.
Maybe I should just my ass into gear change the users over.
Click to expand...
Click to collapse
Google has fixed(somewhat) this problem with an update to Google Play Books Version 3.1.17+
This solution basically disables Immersive Mode on Secondary Users and uses the older LOW_PROFILE/LIGHTS_OUT mode in which the Navigation Buttons are reduced to small, circular blobs of light.
I wouldn't exactly call this a 'fix' though, because all they have done is entirely disable the buggy feature. Nonetheless, at least this makes the app usable.
Same bug here. 4.4.2 (KOT49H). Fresh system (factory image restore) without any user's staff. Immersive Mode absolutely for second account.
Anyone have trouble with Pure Nexus Rom? Home button does nothing. ( Solved this problem. Wipe memory and reinstall rom and gapps.)
Another questions is does anyone have any problems hooking up a large 2TB external hard drive? The Rom crashes. It used to work with CM 12.1. (This is still a problem after solving the above mentioned home button problem.)
Thanks dhacker29, you are awesome.
For all the guys who have played contra. To hard restart Netflix you go to the home page after you have cleared the app memory so netflix is asking for your login info or to start trial. On this page you hit (up, up, down, down, left, right, left, right, up, up, up) with your nexus player controller. This takes you to the netfilx settings page. Click the sign out button on the bottom and you hard set netflix.
rezein said:
Anyone have trouble with Pure Nexus Rom? Home button does nothing. ( Solved this problem. Wipe memory and reinstall rom and gapps.)
Another questions is does anyone have any problems hooking up a large 2TB external hard drive? The Rom crashes. It used to work with CM 12.1. (This is still a problem after solving the above mentioned home button problem.)
Thanks dhacker29, you are awesome.
For all the guys who have played contra. To hard restart Netflix you go to the home page after you have cleared the app memory so netflix is asking for your login info or to start trial. On this page you hit (up, up, down, down, left, right, left, right, up, up, up) with your nexus player controller. This takes you to the netfilx settings page. Click the sign out button on the bottom and you hard set netflix.
Click to expand...
Click to collapse
That's one of the coolest fixes Ive ever heard! Sadly it didn't work for me. Wondering if its the way i flashed the rom? Just a basic factory reset in twrp /wipe dalvik after. Everything seems fine except netflix.
Anybodys voice search not working?
ctrlaltdeln said:
Anybodys voice search not working?
Click to expand...
Click to collapse
Mine also doesn't work.
CharFalco said:
Mine also doesn't work.
Click to expand...
Click to collapse
There is a new update to gapps in the pure nexus op. Gonna try and flash that and see if the update to Google search helps.
Not having the voice search really stinks. A lot of times the virtual keyboard will pop up but not respond
For people having issues with Netflix, it is a gapps issue apparently.
Rumors are "purenexus-gapps-mm-mr1-x86-leanback-20151208-signed.zip" has no issues with Netflix, but I can't find it anywhere. I can confirm that the gapps I flashed with pure nexus 6.0.1 rom (purenexus-gapps-mm-x86-leanback-20151215-signed.zip) has the Netflix issue (will allow you to log in, but keeps saying "We are having difficulty playing this title right now".)