I have loved everything about this tablet and is a worthy successor of my nexus 7, but since the Pixel C is technically not a "nexus" line, will Google still let us unlock the bootloader and root? I'm really hoping so because this thing has so much potential. I wanted to love the nexus 9, but the price was absolutely absurd with nothing really new to bring the table except lollipop.
Thoughts?
Sent from my XT1254 using XDA Free mobile app
Yes! Pixel C has to be up to date tablet so google has to provide ability to flash firmware images when they arrive. And Fastboot provides and easy way of flashing firmware onto a device as it requires almost no setup on linux (a fastboot binary is needed). Nexus player is an android device but still has its images online.
It could just be the first Non-Nexus device to have images hosted.
I think the only difference between the pixle and nexus is that the nexus is always built by another oem where as pixle is made house. I expect this to be like a nexus in every possible way
My prediction is this:
1. Yes the bootloader will be unlockable
2. Yes there will be factory images available
3. It is possible that the stock ROM will be a proprietary version of Android M 6.0, (hopefully not) being closed sourced.
4. The Pixel C will only be available to US residents, and difficult to obtain from outside the U.S.
I'm only speculating on this based off of previous Pixel releases, not trying to be negative. I really hope Google loosen up on this device because there really is no other tablet that I've been interested in since the Nexus 7. I really wish Google would give us some more information, at the very least about availability by country.
Edit: Well, looks like I was wrong. Good wrong though, I'm quite happy they're treating this device like a Nexus. On a whim I bought a N9 for $200 off on Black Friday. I have no regrets though, as the N9 fits my needs to a tee and I'm quite happy with it.
I'd love to be able to dual boot this with Debian.
"PK: Yes, the Pixel C will be supported on AOSP just like other Nexus devices. The bootloader can be unlocked to enable booting an alternate OS. Pixel C does not support Chromebook style recovery via USB. The firmware is open source. It is Coreboot. DisplayPort support over Type C is being worked on but we don't have a release date yet."
And the answer is...
Yes!
https://www.reddit.com/r/IAmA/comments/3w3x7p/hi_im_andrew_here_at_google_and_im_with_the_team/
Envoyé de mon LG-H815 en utilisant Tapatalk
as mentioned in another thread the pixel c uses the new unlock command, fastboot flashing unlock, introduced with the 6p.
I hope the aosp sources will be avaliable soon.
They are here!
https://developers.google.com/android/nexus/images#ryu
https://developers.google.com/android/nexus/drivers#dragon
Related
I'll lead off by saying that I've really enjoyed by having a developer phone like the Gnex. A while back I purchased a Droid 4 to see how much I missed the physical keyboard. It's been striking to notice the functionality and performance difference between bootstrapped and true unlocked phones. No disrespecting the Droid 4 fans; I just found that the Gnex works better for me.
Like many in these forums, I'm very excited to see what Google has to share on Monday, especially in terms of the Nexus 4. That said, what really is the difference between a Nexus phone and any other phone that has an unlock able bootloader? Specifically, I'm looking at the Samsung Galaxy SIII and wondering what I would get with a Nexus phone.
Thanks in advance for your assistance!
Sent from my Galaxy Nexus using Tapatalk 2
dea0002 said:
That said, what really is the difference between a Nexus phone and any other phone that has an unlockable bootloader?
Click to expand...
Click to collapse
Nexus phone = Google device (aosp support included).
This should be clear to you if you own/owned a nexus.
bk201doesntexist said:
Nexus phone = Google device (aosp support included).
This should be clear to you if you own/owned a nexus.
Click to expand...
Click to collapse
That makes sense, and I suppose I wasn't clear with my question. From the perspective of using custom kernels, ROMs, etc., what are the differences between an unlockable phone and a Nexus device? I understand that the Nexus devices come out of the box with a pure AOSP experience, which I acknowledge is very nice. However, if I am planning to use a custom ROM and/or kernel either way, what is the benefit of the Nexus device?
Given the fact that I value and prefer open/unlockable phones, I'm curious about whether it would be worthwhile to hold out for Nexus devices (e.g. Nexus 4) or go with top-notch non-Nexus-but-unlockable devices (e.g. GS III).
Thanks,
Danny
all of the binaries are easily available to the public because of AOSP. this leads to quicker development as far as custom roms are concerned.
also, the bootloader on nexus phones is the easiest one to unlock
As stated above:
Nexus - pure Android UI. Simple adb command to unlock bootloader. Factory images available as soon as Google posts them up online. Source available for quicker/easier development for those so inclined.
Others - OEM UIs. Various tricks or methods required to unlock bootloader. Must wait on carrier/manufacturer to push OTA updates/images. Development of custom ROM hindered by lack of availability of source in some cases.
Also - if you're talking 'unlockable' phones. Just so there's no confusion, a bootloader unlock is a completely different beast from a sim/carrier unlock.
Now that Google has officially brought the Play Store to Chrome OS, do you think that Google might bring Chrome OS to the Pixel C through an update?
Personally, I think they should, given the fact that the Pixel C was originally intended to be a Chrome OS device.
EDIT: Forgot to mention that I would want them to make it so you could dual boot between Android and Chrome OS. Obviously if they replace the OS completely I would not be too happy about it.
I am thinking why would I want Chrome OS, I hope not.
I also doubt it would happen with the Pixel C, maybe something in the future but not the Pixel C.
I think at this point, it is highly unlikely Google will do anything to drastically change the layout of the Pixel C. However, they do need to better optimize Android for tablet usage and overall make it more feasible as a desktop-like OS. Sure, there's multiwindow support supposedly coming with Android N, but they really need to make it generally easy to use if Google hopes to attract more people to devices like the Pixel C.
While I love my Pixel C, I also would have no real use for it without my desktop as well. Android as an operating system is great for devices more geared towards entertainment media consumption, but they have a long ways to go if they hope to be any form of effective productivity machines. While they have since officially denied rumors of merging Chrome OS and Android, I do hope they create some form of format for the Pixel C that is similar to Chrome OS, as well as iron out some of the ever-present bugs as well.
Now if only Google would make a Pixel Phone.....
ChromeOS is getting more Android goodness with better integration than the ARCWelder. So that argues that larger tablets should come with ChromeOS for better multitasking and run Android apks where ChromeOS may be lacking.
However given so few Pixel C sold, it doesn't make sense for Google to productise a ChromeOS ROM for the Pixel C, but rather for its successor.
My Chromebook (based on Intel) I put into developer mode, install Ubuntu via Crouton, then installed Virtualbox and run a Windows VM, hence I got ChromeOS, Ubuntu and Win7 all in one $400 large screen full backlit keyboard with trackpad and a $30 128GB SD card. I tend to stay in ChromeOS unless I got an unsupported media to play then use Ubuntu, and for the odd Windows app I boot that.
Compare to Pixel C.... expensive, no expandable storage and one OS (Android).
These devices are the same weight, just different robustness and from factor.
I got my Pixel as a replacement for my desktop and I would love to have ChromeOS on it, instead of Android, or the ability to switch between the two on the fly depending on whether or not it's docked to a keyboard or not.
I doubt it'll come as an automatic update. It's not 'right' to force people who bought an Android device to switch them to a completely different OS.
May be as an optional update with a lot of warnings but the Google will have then to support 2 different firmware lines for the same device.
I know I'd like that but I have very little hope.
Agreed, it would most likely come in the form of a custom ROM.
Sent from my Pixel C using Tapatalk
The hardware seems good for a small Chromebook, but I read a rumor/insight that ChromeOS touchscreen wasnt ready so last minute they loaded Android, as shown in the bootloader and drivers.
Does anyone think they'll offer ChromeOS for the Pixel C?
Or it is all it can be and it is the split-screen champion of Android N and hence why the 25% "developer's" discount?
The discount came around because there's so little development and fairly limited interest. Since it has a Chrome OS bootloader, dev'ing for it is harder, from what I hear/understand. I doubt it'll get Chrome OS, though I'm hoping for Remix OS. I wish they would replace the bootloader with an Android one, but I doubt that's possible remotely.
YevOmega said:
The discount came around because there's so little development and fairly limited interest. Since it has a Chrome OS bootloader, dev'ing for it is harder, from what I hear/understand. I doubt it'll get Chrome OS, though I'm hoping for Remix OS. I wish they would replace the bootloader with an Android one, but I doubt that's possible remotely.
Click to expand...
Click to collapse
I just yesterday manually flashed the latest Android, and I did the fastboot flash bootloader bootloader-dragon-google_smaug.7132.295.0.img
I'm sure bootloader could be modified.
The relatively quiet Pixel C shows me there is little interest relatively for this tablet.
It's a real shame as this tablet has a lot of potential. I guess I bought into that potential though I do consider XDA as the benchmark and if this section isn't booming....then
Doesn't help with the early woes and the normal price of the unit. I've been fortunate to have a problem free unit, mine is fast, fluid, well built and all that lacks is some decent software.
I suppose N will be our salvation.
nigelhealy said:
I just yesterday manually flashed the latest Android, and I did the fastboot flash bootloader bootloader-dragon-google_smaug.7132.295.0.img
I'm sure bootloader could be modified.
The relatively quiet Pixel C shows me there is little interest relatively for this tablet.
Click to expand...
Click to collapse
Modified =/= change from Chrome OS to Android bootloader. I too have it unlocked. I just think that changing to an Android bootloader involves hardware changes as well as firmware.
---------- Post added at 02:24 PM ---------- Previous post was at 02:22 PM ----------
Doughnut said:
It's a real shame as this tablet has a lot of potential. I guess I bought into that potential though I do consider XDA as the benchmark and if this section isn't booming....then
Doesn't help with the early woes and the normal price of the unit. I've been fortunate to have a problem free unit, mine is fast, fluid, well built and all that lacks is some decent software.
I suppose N will be our salvation.
Click to expand...
Click to collapse
N should be great. To be fair, I don't really need much past what GravityBox provides me.... I'm just a flashaholic. Really, really hoping for Remix OS though.
YevOmega said:
Modified =/= change from Chrome OS to Android bootloader. I too have it unlocked. I just think that changing to an Android bootloader involves hardware changes as well as firmware.
Click to expand...
Click to collapse
I would like there to be a ChromeOS ROM version for the Pixel C in so far as the multitasking and windowing is superior and not reliant on apps being modified, unlike Android N will take year+ to get all apps to behave.
However I don't see it happening, it makes no sense to retrofit it on the Pixel C, unless they decide to use the Pixel C as a developer option to pull ChromeOS upwards on that form factor with touchscreen.
nigelhealy said:
I would like there to be a ChromeOS ROM version for the Pixel C in so far as the multitasking and windowing is superior and not reliant on apps being modified, unlike Android N will take year+ to get all apps to behave.
However I don't see it happening, it makes no sense to retrofit it on the Pixel C, unless they decide to use the Pixel C as a developer option to pull ChromeOS upwards on that form factor with touchscreen.
Click to expand...
Click to collapse
I agree, not gonna happen.
I currently have the note 5. Before that the s5. I love to have options to flash different roms. But I have been on Sammy for the last 10 yearso and know nothing of flashing, rooting or installing custom recovery on htc. I awaited the s7 only to find out it was locked down. Same with the other Samsung. No development. So I'm looking at the htc 10. Will there be a ton of development for htc 10 sprint? Is it hard to root , recovery& flash roms? I had so much development for the s5 I miss those days
Sent from my SM-N920P using Tapatalk
djxn40 said:
I currently have the note 5. Before that the s5. I love to have options to flash different roms. But I have been on Sammy for the last 10 yearso and know nothing of flashing, rooting or installing custom recovery on htc. I awaited the s7 only to find out it was locked down. Same with the other Samsung. No development. So I'm looking at the htc 10. Will there be a ton of development for htc 10 sprint? Is it hard to root , recovery& flash roms? I had so much development for the s5 I miss those days
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
My experience with the HTC and setting it up was wonderful. I received it yesterday, and got off work about 5:00, and took it out of the plastic when I got to the hotel I'm staying at. By 9:00 PM I had fired it up, used S-Off to unlock it, flashed TWRP via fastboot, then made a backup, wiped it, and flashed a custom rom.
I'm usually a pre-order guy when I buy flagships, the M10 has been awesome because I was able to achieve s-off after unboxing it, which is the HTC version of allowing flashing recovery, roms, firmware radios, etc from TWRP or a custom recovery.
I can't thank the Sunshine team enough for making an app that allows me to pay $25 for the license, and unlock the phone simply by following the instructions. I've been rooting phones long enough that I previously had to hold a paperclip shorting two pins on the mother board while counting a certain number of seconds and typing commands with other hand to be able to upgrade firmware. So I really appreciate an app that does all the work, and allows me to get right down to business backing up and wiping. Literally, the hardest part of the setup was pointing the device to the right drivers in Windows 10, and that was a computer issue not the phone.
However, I'm an HTC guy, and you've been with Samsung a while. I've installed multiple Sense roms so far, which are HTC based, although VERY custom roms. I can't testify to the AOSP roms and their kernels yet, someone else will have to testify to that, if you're considering that route from the start.
For me, it's a great device so far. It works really well with my Pioneer blue tooth/hands free system in the car that I've been using for voice command searches and navigation, video streaming to my media players, and audio streaming with Pandora, iHeartRadio, google music, etc.
Call quality has been good, and I'm very happy with the build quality and finish of the device in general. I bought it outright from HTC, so I was apprehensive to pull the trigger at retail price, but I don't finance my devices.
Since I'm a fan of sense roms, it was worth it to me to pay more and get a better device experience for my taste than with some of the nexus (not as much cheaper as they used to be) or one of the blu oppo or CM type unlocked phones.
Pretty much what the above poster said. You may not find the sheer quantity of different ROMs that you would find on previous popular Samsung phones (or even previous HTC flagships), but still lots and lots of options. Take a look at the main 10 Dev forum, plenty of great running choices. Similarly I only stick to Sense ROMs so I can't tell you much about AOSP or CM specifically, but that's only because Sense is such a smooth, reliable and enjoyable experience for me. This is the main reason I went for the 10, having previously owned an M7 as well.
For me it comes down to this: Software-wise, if you're someone who makes use of and can't live without all of the small TouchWiz features and add-ons (e.g. hovering your hand to take screenshots, multi-windows, etc) and don't really care as much about having a consistently fluid experience, then stick with Samsung. Otherwise, Sense is the better product imo.
Thanks guys. I generally turn off all those silly features and tune the romantic more for speed
Sent from my SM-N920P using Tapatalk
djxn40 said:
Thanks guys. I generally turn off all those silly features and tune the romantic more for speed
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
The chances are great you will love the HTC10. I own all the galaxy S series from the S blaze to the S7, also the note 5 and the note 3 and I can honestly say I would trade any 1 of them for the HTC10!!! I got my HTC10 on release and have not looked back. I am loving the hell out it lol.
djxn40 said:
I currently have the note 5. Before that the s5. I love to have options to flash different roms. But I have been on Sammy for the last 10 yearso and know nothing of flashing, rooting or installing custom recovery on htc. I awaited the s7 only to find out it was locked down. Same with the other Samsung. No development. So I'm looking at the htc 10. Will there be a ton of development for htc 10 sprint? Is it hard to root , recovery& flash roms? I had so much development for the s5 I miss those days
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Why don't you wait until Tuesday to say what Google has to offer with both the pixel and pixel xl ?
Gesendet von meinem SM-G935F mit Tapatalk
Chad_Petree said:
Why don't you wait until Tuesday to say what Google has to offer with both the pixel and pixel xl ?
Gesendet von meinem SM-G935F mit Tapatalk
Click to expand...
Click to collapse
Great advice ! Yeah during my investigation last night I seen were the pixel xl was coming out... I think I want that pixel xl !
Sent from my SM-N920P using Tapatalk
Chad_Petree said:
Why don't you wait until Tuesday to say what Google has to offer with both the pixel and pixel xl ?
Click to expand...
Click to collapse
I am waiting, but only because I anticipate their release will herald a price drop in the HTC 10. I don't expect the Pixel phones to come with an SD reader, so unless they blow my mind, I doubt I'll be getting one.
Sense is such a lightweight functional skin now with really good features I really can't see the point in getting a pixel instead of this device, I can see why the pixel XL with a bigger screen would be a consideration, really wish htc would make a 5.5" 10... Got to say as well as I run a few phones htc moving the back and recent keys either side of the home button was a genius move... Had a lot of phones this HTC 10 in my opinion is as good as anything else out there at the moment...
Sent from my Nexus 9 using Tapatalk
Has anyone tried htc 10 with android auto ( car play).
Sent from my SM-N920P using Tapatalk
djxn40 said:
Has anyone tried htc 10 with android auto ( car play).
Click to expand...
Click to collapse
Yes I have. Works the same as on my M7. Mirrorlink also works though a bit useless for me.
HTC M10 Currently $150 may help makeup your mind
http://www.htc.com/us/go/buy-htc-10...n=htc10event&gclid=CLDJwLO6vM8CFYEehgodtQECqA
I know it's impossible to know for sure, but do you anticipate that Lineage and other ROMS will continue to be developed for the PIxel 2 series over the next year or two? The ROM section of the board seems decently active right now. I'm considering buying a Pixel 2 XL, but don't want to buy it only to have development stop over the coming months. Definitely want Android 12 when it comes out.
if you seriously want 12 when it comes out FWIW, may be better to get Pixel 3 (which has dev/beta images IIRC) since custom dev only kicks off then when Google opens sourcecode. (FWIW Pixel3 also has multiple Lineage device maintainers.) OTOH if repartition, apparently can hack beta GSI onto Pixel 2, tho the tricky shimming/patching wasn't yet able to do calls last I read https://forum.xda-developers.com/t/...oid-12-and-any-gsi-larger-than-2-6gb.4311135/ ). DotOS already claims some version of Monet theming engine FWIW. Best wishes
well, just read https://forum.xda-developers.com/t/...-rates-on-the-pixel-2xl.4329795/post-85593187 who says be wary of Pixel 3 and 2XL is better, so definitely do your research. And whichever, don't get a Verizon one (as can't unlock bootloader).