Related
Is it just me, or this phone has the same button layout as the Dream?
Any chance we will see the Touch HD with android on it?
The dream, the Diamond and the Touch Pro all have the same 4 buttons.
And no, i don't believe for one single, solitary second that HTC will sell a device with Windows mobile and offer you a choice to install android on it.
If they did offer you the choice to change, i'd expect MS would get seriously pissed with HTC!!
They will not offer a choice for sure, but they can sell a different SKU with Andoid (based on the same hardware). MS would have nothing to say, and at the end of the day I don't really think that HTC cares a about how happy MS is.
But that is just speculation.
Well, at least these latest WM devices lost the dedicated Strat, PIE, Messaging and OK buttons, which were included probably in the reference WM phone design.
Now the phones look a lot more OS agnostic, and MS has to live with that, since their os is crap and manufacturers need to fight the iPhone.
oh thank god i'm not the only one that kept thinking that... I was starting to think that I was seeing android stuff everywhere! But this does leave me to believe that they (HTC) are leaving us open in the future with OS choice on our phones. And by that I do mean same hardware, but different systems on separate SKU's.
I´m sure in a short time, from this fantastic forum some devs will start to develope Android to be ported on several HTC models.
Lt´s see how good it is
personally I think the diamond and TPro should have ditched the dpad and gone with wide (tall) screens as well, would add another quarter inch or so to the screen, which would be more welcome than the dpad.
The 4 buttons are enough for most people (but 6 would be better, I miss my dedicated win and OK buttons).
I hate the current trend of removing buttons in favor of a full touch like device. Can dcall me old school, but the idea of completely removing the dpad is insane to me. However, I do like the touch HD and I look forward to seeing it run android. I think it's just a matter of time.
I'm concerned that I won't be able to play any of my games. Some dude is working on an app that converts the g-sensor moves into button presses and he has it working but still...
why are apps like multi touch pong not really multi touch? when u have 2 fingers on the screen at the same time the 2 points interfere with each other making it impossible to play games like pong or air hockey etc
from what I understand, true multitouch is still disabled for US devices. What's used in most of these apps is a hacky multitouch we've been seeing since the G1.
kozm0naut said:
from what I understand, true multitouch is still disabled for US devices. What's used in most of these apps is a hacky multitouch we've been seeing since the G1.
Click to expand...
Click to collapse
this isn't true there is true multi touch from android 2.0 and up! but google decided to disable it in their native apps.
oh so what we have multi touch but not the real one like the iphone has. gay
i understand that theres multi touch. we can pinch to zoom and what not but download the simply draw app which is "multi touch" and try to draw 2 different objects at once. just wont work. i mean true multi touch
it's been made clear that android handsets (including n1) support true multitouch on the hardware level. however, the apps I've used on 2.1 so far with "multitouch" suffer from the mixed-axes issues mentioned here and elsewhere on the forums.
I just tested the multitouch capabilities of the Atrix. It only registered two fingers? wow I have expected that it will recognize at least 4.....I don't play games on my phone so I don't worry too much but still it leaves a bitter taste...
You can't really use more than 2 fingers on a 4" screen anyway unless you have tiny hands.
Why would you ever need 4 point multitouch on the atrix to begin with... I mean of all the things to complain about this is the lame...
dumasymptote said:
Why would you ever need 4 point multitouch on the atrix to begin with... I mean of all the things to complain about this is the lame...
Click to expand...
Click to collapse
First of all. I wasn't complaining. I just wanted to test how accurate the multitouch is because I am a former N1 user and the multitouch sucked. It was more by curiosity that I tried 3 fingers. I had also a Nexus S and a MT4G and they could register several fingers. I thought that all newer touch sensors were multi finger enabled...
BTW I like my Atrix very much and the screen responsiveness is better than on my HTC devices that I had.
from the build.prop file, it says 2 max touches.
I tried to change the value to 4 but it still would only register 2.
wierd my Nexus S allowed 5
and htc desire HD allowed 4
i think newer screens would allow more, not that it matters
just curious
Is by brand is not HTC so don't expect the same I guess it does suck tho , oh well
I looked at the fixit site and they say it is the same sensor as in the Nexus S: Atmel mXT224. But this beast should have unlimited touch according to the manufacturer. Interesting maybe it is disabled software wise.
As a former N1 user, this touch issue is not important. What is important is it registers two independent touches and never confuses them.
Why is this important? Virtual game joystick and buttons. You will never use more than two touches for that.
Yes there are a few games or apps that can do more than two touches and it is disappointing to not have that enabled. But we will almost never notice this.
snlu178 said:
As a former N1 user, this touch issue is not important. What is important is it registers two independent touches and never confuses them.
Click to expand...
Click to collapse
This has already been proven for the Atrix (that it treats multitouch correctly); read about it a few days ago on this very forum.
http://forum.xda-developers.com/showpost.php?p=11540136&postcount=56
The Atrix has the same ATMEL multitouch sensor as the Nexus S, EVO, etc. So we know it can register at least 5 screen inputs at once. The apps you are using to test the multitouch input simply does not support the device (yet), and will need to be updated in order to for this phone to register multiple inputs beyond 2. This is simply a case of outdated software on new hardware.
novaIS350 said:
The Atrix has the same ATMEL multitouch sensor as the Nexus S, EVO, etc. So we know it can register at least 5 screen inputs at once. The apps you are using to test the multitouch input simply does not support the device (yet), and will need to be updated in order to for this phone to register multiple inputs beyond 2. This is simply a case of outdated software on new hardware.
Click to expand...
Click to collapse
The EVO would not register more than two touch points while operating on the stock kernel - and it was shown after rooting and unlocking the bootloader that there were two different touch panels - one that could do three points and one that could do 5.
So hopefully the OE kernel enables the use of the max number of touch points supported by the screen and it is just a matter of outdated software.
so far I have downloaded multitouch test, touch test, multitouch visualizer 2, and multitouch tester all from the android market and the results are always dual imput, not multi...
Am I doning something wrong is the fact that it will not register a third or more imputs... I thought we had up to 5 digit touch
Can anyone confirm or deny?
Thanks
more than 2 fingers, Apple will give u a hard time
majik8ball said:
so far I have downloaded multitouch test, touch test, multitouch visualizer 2, and multitouch tester all from the android market and the results are always dual imput, not multi...
Am I doning something wrong is the fact that it will not register a third or more imputs... I thought we had up to 5 digit touch
Can anyone confirm or deny?
Thanks
Click to expand...
Click to collapse
Use the app phonetester. That is the most accurate.
dumasymptote said:
Why would you ever need 4 point multitouch on the atrix to begin with... I mean of all the things to complain about this is the lame...
Click to expand...
Click to collapse
This is a terrible problem. I had to stop playing metroid zero mission on my old phone, because you couldn't press the r trigger, the up button, and the b button simultaneously, and you needed to (those 3 buttons when pressed shoot misslles up) in order to kill the boss.
has anyone tried some emulators, like snes or psx or gameboid? i wonder if it reconizes more than two touch imputs..??
ronan_zj said:
more than 2 fingers, Apple will give u a hard time
Click to expand...
Click to collapse
DING DING DING finally someone remembers...
http://www.tgdaily.com/business-and...-back-at-motorola-with-multitouch-patent-suit
Apple, Google and device makers have been embroiled in patent lawsuits since the first Android devices were being made. It still continues. If folks recall, there was huge controversy when I think the original Droid (or was it even earlier, the G1 maybe?) came out and didn't have multitouch in the US, but the international version did. This is why and it continues to be an issue.
What are you talking about... The ATT captivate with the froyo ROM does 5 fingers...
Galaxy s has 5 touch
all i want to know when moto atrix is getting ics.i also have sgs captivate and it is running on ics port and woking very well.so i also want to have ics on this phone also.pls do it quickly
sx4 said:
all i want to know when moto atrix is getting ics.i also have sgs captivate and it is running on ics port and woking very well.so i also want to have ics on this phone also.pls do it quickly
Click to expand...
Click to collapse
Seriously, SEARCH!! there's already too many threads about this. And writing another thread isn't gunna help it get here faster. We need another tegra device to get it first. You'd know this if you SEARCHED!!!!
Sent from my MB860 using XDA App
sx4 said:
all i want to know when moto atrix is getting ics.i also have sgs captivate and it is running on ics port and woking very well.so i also want to have ics on this phone also.pls do it quickly
Click to expand...
Click to collapse
This sense of entitlement is why devs are leaving XDA.
There is currently no ICS port. The group working on CM7 will be doing a version for CM9 but as with any version of CM, no etas. Next time use search. If you want ICS badly, you already have it on your captivate.
sx4 said:
all i want to know when moto atrix is getting ics.i also have sgs captivate and it is running on ics port and woking very well.so i also want to have ics on this phone also.pls do it quickly
Click to expand...
Click to collapse
If you want it so bad, port it hisself instead of giving orders in a somewhat polite way.
Sent from my MB860 using XDA App
sx4 said:
all i want to know when moto atrix is getting ics.i also have sgs captivate and it is running on ics port and woking very well.so i also want to have ics on this phone also.pls do it quickly
Click to expand...
Click to collapse
Pls do it quickly? Every dev in here is probably cursing your phone and hoping it breaks right before ics leaks. Might want to take your a la carts attitude to the windows phone forums.
Sent from my Galaxy Nexus using xda premium
[opinion]you will never see an official port for ICS from the Atrix, Atrix 2, or any device using the webtop.[/opinion]
In addition, the Atrix 4G has the FP scanner. These two features are going to kill any official support from Motorola. Why?
They are LAZY! The webtop was cobbled together in the first place. This is why the 'the optimus 2x is getting ICS' argument doesn't work in the case of the Atrix. Sure this will leave a bad taste in consumers' mouths, for maybe two seconds until they come out with something new and shiny. Seems people are willing to shell out hundreds of dollars for hardware that isn't even an upgrade, so why bother putting effort into updating software when it isn't profitable?
Its also worth noting that there are some parts of the world where GB isn't even an official release yet! Once they roll out GB in all regions, they will bury support for this phone six feet under, despite the customer objections.
Besides, our clandestine group of developers for the Atrix have pushed out better software than the official Moto devs ever could. You'll see a CM9 port before you even hear an utterance from Motorola to support the Atrix.
SirFork said:
you will never see an official port for ICS from the Atrix, Atrix 2, or any device using the webtop.
Click to expand...
Click to collapse
Source please!
CaelanT said:
Source please!
Click to expand...
Click to collapse
Aside from Motorola's track record, I have none. Hence, the several paragraphs explaining my reasoning. The lack of correspondence from Motorola (all I have gotten from them are canned almost political-sounding statements) and the present state of affairs for Atrix support in addition to the points I made previously are why I am extremely skeptical of ICS ever coming to the Atrix officially.
Of course I hope that I will eat my own words some day, like an ice cream sandwich
Edited my previous post to reflect as an opinion article not as fact.
SirFork said:
Aside from Motorola's track record, I have none. Hence, the several paragraphs explaining my reasoning. The lack of correspondence from Motorola (all I have gotten from them are canned almost political-sounding statements) and the present state of affairs for Atrix support in addition to the points I made previously are why I am extremely skeptical of ICS ever coming to the Atrix officially.
Of course I hope that I will eat my own words some day, like an ice cream sandwich
Edited my previous post to reflect as an opinion article not as fact.
Click to expand...
Click to collapse
Including the fact that since July, Motorola has released or is about to release the Droid 3, Bionic, RAZR, Droid 4, RAZRMAX, Photon 4G, Triumph, and Atrix 2. Throw on the Cliq 2, Atrix, and Droid X2 from earlier in the year.
im running ics on my atrix right now CM9, enginerring build, lots of things broken, def not for public and will not be made available for public for a while. so DO NOT ASK FOR IT. btw all credit to turl and atrix-dev-team. my point is, never say never because its already a fact.
samcripp said:
im running ics on my atrix right now CM9, enginerring build, lots of things broken, def not for public and will not be made available for public for a while. so DO NOT ASK FOR IT. btw all credit to turl and atrix-dev-team. my point is, never say never because its already a fact.
Click to expand...
Click to collapse
Great news! I'm sure none of us will be stupid enough to ask for ETA's!
I'm assuming no HW Acceleration and the good stuff. Have you heard about Nvidia's plans to release ICS drivers and binaries for their Tegra 2 and Tegra 3 line early next year?
coolnow said:
Great news! I'm sure none of us will be stupid enough to ask for ETA's!
I'm assuming no HW Acceleration and the good stuff. Have you heard about Nvidia's plans to release ICS drivers and binaries for their Tegra 2 and Tegra 3 line early next year?
Click to expand...
Click to collapse
actually is really smooth, the issues are on other things, im not gonna go into detail, but is def very nice and smooth
There you go! Now all ICS on Atrix speculation can be laid to rest!
samcripp said:
actually is really smooth, the issues are on other things, im not gonna go into detail, but is def very nice and smooth
Click to expand...
Click to collapse
So you saying hw accel or no hw accel?
sent from a galaxy far far away.
maybe idk, just got it today, sure feels hw accelerated, any ways, no more questions
samcripp said:
maybe idk, just got it today, sure feels hw accelerated, any ways, no more questions
Click to expand...
Click to collapse
Thank you for the input mate. I'd get ready to go into hiding if i was you I can just rest easy now
As always, thank you and the Atrix Dev Team, and all the other devs who work on this phone, thank you, thank you, thank you so very much!
;19986019 said:
So you saying hw accel or no hw accel?
sent from a galaxy far far away.
Click to expand...
Click to collapse
How about some Android graphics true facts?
• Android has always used some hardware accelerated drawing. Since before 1.0 all window compositing to the display has been done with hardware.
• This means that many of the animations you see have always been hardware accelerated: menus being shown, sliding the notification shade, transitions between activities, pop-ups and dialogs showing and hiding, etc.
• Android did historically use software to render the contents of each window. For example in a UI like there are four windows: the status bar, the wallpaper, the launcher on top of the wallpaper, and the menu. If one of the windows updates its contents, such as highlighting a menu item, then (prior to 3.0) software is used to draw the new contents of that window; however none of the other windows are redrawn at all, and the re-composition of the windows is done in hardware. Likewise, any movement of the windows such as the menu going up and down is all hardware rendering.
• Looking at drawing inside of a window, you don’t necessarily need to do this in hardware to achieve full 60fps rendering. This depends very much on the number of pixels in your display and the speed of your CPU. For example, Nexus S has no trouble doing 60fps rendering of all the normal stuff you see in the Android UI like scrolling lists on its 800x480 screen. The original Droid however struggled with a similar screen resolution.
• "Full" hardware accelerated drawing within a window was added in Android 3.0. The implementation in Android 4.0 is not any more full than in 3.0. Starting with 3.0, if you set the flag in your app saying that hardware accelerated drawing is allowed, then all drawing to the application’s windows will be done with the GPU. The main change in this regard in Android 4.0 is that now apps that are explicitly targeting 4.0 or higher will have acceleration enabled by default rather than having to put " in their manifest. (And the reason this isn’t just turned on for all existing applications is that some types of drawing operations can’t be supported well in hardware and it also impacts the behavior when an application asks to have a part of its UI updated. Forcing hardware accelerated drawing upon existing apps will break a significant number of them, from subtly to significantly.)
• Hardware accelerated drawing is not all full of win. For example on the PVR drivers of devices like the Nexus S and Galaxy Nexus, simply starting to use OpenGL in a process eats about 8MB of RAM. Given that our process overhead is about 2MB, this is pretty huge. That RAM takes away from other things, such as the number of background processes that can be kept running, potentially slowing down things like app switching.
• Because of the overhead of OpenGL, one may very well not want to use it for drawing. For example some of the work we are doing to make Android 4.0 run well on the Nexus S has involved turning off hardware accelerated drawing in parts of the UI so we don’t lose 8MB of RAM in the system process, another 8MB in the phone process, another 8MB in the system UI process, etc. Trust me, you won’t notice -- there is just no benefit on that device in using OpenGL to draw something like the status bar, even with fancy animations going on in there.
• Hardware accelerated drawing is not a magical silver bullet to butter-smooth UI. There are many different efforts that have been going on towards this, such as improved scheduling of foreground vs. background threads in 1.6, rewriting the input system in 2.3, strict mode, concurrent garbage collection, loaders, etc. If you want to achieve 60fps, you have 20 milliseconds to handle each frame. This is not a lot of time. Just touching the flash storage system in the thread that is running the UI can in some cases introduce a delay that puts you out of that timing window, especially if you are writing to storage.
• A recent example of the kinds of interesting things that impact UI smoothness: we noticed that ICS on Nexus S was actually less smooth when scrolling through lists than it was on Gingerbread. It turned out that the reason for this was due to subtle changes in timing, so that sometimes in ICS as the app was retrieving touch events and drawing the screen, it would go to get the next event slightly before it was ready, causing it to visibly miss a frame while tracking the finger even though it was drawing the screen at a solid 60fps.
• When people have historically compared web browser scrolling between Android and iOS, most of the differences they are seeing are not due to hardware accelerated drawing. Originally Android went a different route for its web page rendering and made different compromises: the web page is turned in to a display list, which is continually rendered to the screen, instead of using tiles. This has the benefit that scrolling and zooming never have artifacts of tiles that haven’t yet been drawn. Its downside is that as the graphics on the web page get more complicated to draw the frame rate goes down. As of Android 3.0, the browser now uses tiles, so it can maintain a consistent frame rate as you scroll or zoom, with the negative of having artifacts when newly needed tiles can’t be rendered quickly enough. The tiles themselves are rendered in software, which I believe is the case for iOS as well. (And this tile-based approach could be used prior to 3.0 without hardware accelerated drawing; as mentioned previously, the Nexus S CPU can easily draw the tiles to the window at 60fps.)
• Hardware accleration does not magically make drawing performance problems disappear. There is still a limit to how much the GPU can do. A recent interesting example of this is tablets built with Tegra 2 -- that GPU can touch every pixel of a 1280x800 screen about 2.5 times at 60fps. Now consider the Android 3.0 tablet home screen where you are switching to the all apps list: you need to draw the background (1x all pixels), then the layer of shortcuts and widgets (let’s be nice and say this is .5x all pixels), then the black background of all apps (1x all pixels), and the icons and labels of all apps (.5x all pixels). We’ve already blown our per-pixel budget, and we haven’t even composited the separate windows to the final display yet. To get 60fps animation, Android 3.0 and later use a number of tricks. A big one is that it tries to put all windows into overlays instead of having to copy them to the framebuffer with the GPU. In the case here even with that we are still over-budget, but we have another trick: because the wallpaper on Android is in a separate window, we can make this window larger than the screen to hold the entire bitmap. Now, as you scroll, the movement of the background doesn’t require any drawing, just moving its window... and because this window is in an overlay, it doesn’t even need to be composited to the screen with the GPU.
• As device screen resolution goes up, achieving a 60fps UI is closely related to GPU speed and especially the GPU’s memory bus bandwidth. In fact, if you want to get an idea of the performance of a piece of hardware, always pay close attention to the memory bus bandwidth. There are plenty of times where the CPU (especially with those wonderful NEON instructions) can go a lot faster than the memory bus.
On a side note, the Tegra 2 does not have NEON instructions and only uses single-channel memory, which limits how well GPU acceleration helps with smoothness.
thanks.
sent from a galaxy far far away.
samcripp said:
maybe idk, just got it today, sure feels hw accelerated, any ways, no more questions
Click to expand...
Click to collapse
Sure would love to see a screenshot or 10. Have seen absolutely zero anywhere else about this happening.
Not saying "prove it" or anything, mind you! Just curious (as is everyone else here).
It's great to know that ATrix CM9 is in the oven. I personally have no doubt that ATRIX will get ICS officially.
so here is the change log for 7.1
Pixel product-specific
Pixel Launcher - swipe up for all apps, new Search Box, date/weather header on home
Google Assistant
Unlimited original quality photo/video backup to Google Photos
Smart Storage - when storage is full, automatically removes old backed up photos/videos
Phone/Chat support (new support tab in settings), screen-share functionality
Quick switch adapter for wired setup from Android or iPhone
Pixel Camera:
Electronic Image Stabilization (“video stabilization”) 2.0
Pro Features
White Balance Presets
Exposure Compensation
AE/AF Locking
Viewfinder grid modes
HW-accelerated (on Qualcomm Hexagon coprocessor) HDR+ image processing
Smartburst
Sensor Hub processor with tightly integrated sensors (accel, gyro, mag) + connectivity (Wi-Fi, Cell, GPS)
Cosmetic
Solid navbar icons with home affordance for Assistant
SysUI accent color theming
Wallpaper picker with new wallpapers and sounds
New setup look and feel
Dynamic calendar date icon
Android Nougat 7.1
Night Light
Touch/display performance improvements
Moves (Fingerprint swipe down gesture - opt-in)
Seamless A/B system updates
Daydream VR mode
Developer features:
App shortcuts / shortcut manager APIs
Circular app icons support
Keyboard image insertion
Fingerprint sensor gesture to open/close notification shade
Manual storage manager Intent for apps
Improved VR thread scheduling
Enhanced wallpaper metadata
Multi-endpoint call support
Support for various MNO requirements
PCDMA voice privacy property
Source type support for Visual Voicemail
Carrier config options for managing video telephony
Manual storage manager - identifies apps and files and apps using storage
will our pixel c get the pixel specific update?
Be nice to get 7.1 it is not like Google refreshed the tablets yesterday but I am not sure how some of the 7.1 benefits will work on a tablet
The vast majority of that is hardware dependent. It's 7.1 that I want to see, and not the 'dev preview' coming to Nexus phones by end of the year. I had preordered the Pixel phones, but have now cancelled as there's little in them that really says progress and development. Also, the fairly poor support for the Pixel C (eg the indispensable physical kb that still gives false inputs) didn't fill me with confidence.
In short, this better get the 7.1 update as soon as it drops on the Pixel phones or I and others will begin to extricate ourselves from Google products.
The main thing I want is the unlimited original quality photo uploads. The rest of it I can live without. I'm happy with the standard Google launcher rather than the Pixel one.
kboya said:
The vast majority of that is hardware dependent. It's 7.1 that I want to see, and not the 'dev preview' coming to Nexus phones by end of the year. I had preordered the Pixel phones, but have now cancelled as there's little in them that really says progress and development. Also, the fairly poor support for the Pixel C (eg the indispensable physical kb that still gives false inputs) didn't fill me with confidence.
In short, this better get the 7.1 update as soon as it drops on the Pixel phones or I and others will begin to extricate ourselves from Google products.
Click to expand...
Click to collapse
umm... the 7.1 update is going into a dev preview at the end of this month, not by the end of the year, and will not even be on the Pixel and Pixel XL until december... It's initially launching as a dev preview on the 5X, 6P, and Pixel C. Check the blog post: http://android-developers.blogspot.ca/2016/10/android-71-developer-preview.html
"Initially, we’ll offer the Developer Preview for Nexus 5X, Nexus 6P, and Pixel C devices, extending to other supported devices by the end of the preview. At the final release of the Android 7.1.x platform, due in early December, we’ll roll out updates to the full lineup of supported devices — Nexus 6, 5X, 6P, 9, Player, Pixel C, and supported Android One devices — as well as Pixel and Pixel XL devices."
I haven't had any problems with false inputs on the Pixel C Keyboard. Have you tried getting in touch with them to deal with it under warranty?
NJ72 said:
The main thing I want is the unlimited original quality photo uploads. The rest of it I can live without. I'm happy with the standard Google launcher rather than the Pixel one.
Click to expand...
Click to collapse
I highly doubt that would be coming to the Pixel C for a plethora of reasons, but do you actually use the camera on the Pixel C? It's pretty atrocious as far as I've found.
Ummm... It's a shame they posted that 4 days after I posted my point, which was based upon the news available at the time. We shall see.
I'm pleased you haven't experienced the well documented kb false inputs. I've had 2kb and 3 pixel c. It remains an issue. YMMV.
sniperfox47 said:
I highly doubt that would be coming to the Pixel C for a plethora of reasons, but do you actually use the camera on the Pixel C? It's pretty atrocious as far as I've found.
Click to expand...
Click to collapse
I don't use the Pixel C camera, no, mainly because I feel like an idiot holding a tablet up to take a picture - especially when my S7 takes great pics.
What I am hoping is that it will be applicable to all photos uploaded through the device - but I'm ready to be corrected on that as I haven't read too much in to it.
kboya said:
Ummm... It's a shame they posted that 4 days after I posted my point, which was based upon the news available at the time. We shall see.
I'm pleased you haven't experienced the well documented kb false inputs. I've had 2kb and 3 pixel c. It remains an issue. YMMV.
Click to expand...
Click to collapse
Fair. Sorry, it seems I was either blind or asleep when I posted that and didn't look at the time of your post. My apologies.
I sincerely hope that the "Google" features like assistant come to the Pixel C too, but tbh I'm not holding my breath for it.
sniperfox47 said:
Fair. Sorry, it seems I was either blind or asleep when I posted that and didn't look at the time of your post. My apologies.
I sincerely hope that the "Google" features like assistant come to the Pixel C too, but tbh I'm not holding my breath for it.
Click to expand...
Click to collapse
No worries. My reply appears more curt than I meant... apologies backatcha!
To keep the topic on track, it's a strange mix of information as the Pixel/XL camera 4.2(?) apk teardown (on xda) is specified for 7.1, and devs adapted it for 7.0 (if memory serves). I suppose we'll all find out when those phones drop into hands anytime now. Elgoog have a history of conflicting lines of communication.
kboya said:
No worries. My reply appears more curt than I meant... apologies backatcha!
To keep the topic on track, it's a strange mix of information as the Pixel/XL camera 4.2(?) apk teardown (on xda) is specified for 7.1, and devs adapted it for 7.0 (if memory serves). I suppose we'll all find out when those phones drop into hands anytime now. Elgoog have a history of conflicting lines of communication.
Click to expand...
Click to collapse
And according to pictures by telexco customers who got their phones early, the clock app's new shortcuts appear on the Pixel show up, and they're input using the new 7.1 shortcuts API... So whaaaaaaaaaaat? Maybe the Pixel ships with 7.1 after all?
It's live, already > http://www.androidauthority.com/android-7-1-developer-preview-download-723427/