Related
Hello All,
As you all know I've been part of Xda and assiting in a positive resolution from HTC in requests from Bootloaders to source codes. Well seeing we have a great device that seemed to be given EOL to early in its game.. in my opinion due to lack of marketing skills. Well I will be posting in HTC FB to get our voice out to them for the Source Code release for our device.
Please comment "Like" and comment to request this so we can continue development for the Flyer.
https://www.facebook.com/photo.php?fbid=10151213297764443&set=o.165420456859572&type=1&ref=nf
And Here:
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Um, source code of what? They release sources of Honeycomb, and there are no sources of ICS or Jelly Bean, so what's the whole point?
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
kayoma said:
Source code for drivers which can be ported to ICS and JB. Anyway it helps coders make their own drivers for Camera/Front camera and for video
Click to expand...
Click to collapse
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
There is the kernel which is low level device specific, the kernel is mostly based on open source linux code, htc adds some board and device specific configuration on top of that.
Then there is the aosp which is also open source, an operating system provided by google that makes up most part of any ROM.
Then you have your aosp derivative like CM or AOKP, which provides board specific fixes and some customization. HTC's ROM is also based on aosp, but they add their own sense look and feel to it.
And finally and most importantly you have your close source proprietary drivers provided by chip manufactures like Qualcomm and TI. They control cameras, wifi, BT...etc. So in reality there is very little HTC could do as they don't have the rights to release these code. And that's is where most ppl run into issues.
So to create a ROM is not hard at all, anybody can download the source code and compile it to generate a ROM as most of the source code are all open source. What will be helpful is if Qualcomm releases the source code for their drivers, which I doubt they will ever do, otherwise they wouldn't be close source in the first place. The only thing we could do is try to reverse engineer the device base on logs and understanding of how each component should work and make educated guesses.
Due to HTC lack of effort on this device (No ICS - HC was slow joke) I will never buy another HTC product again, same goes for sony, though they did eventually update xperia x10i it was only due to huge pressure not because they wanted to.
I want to buy an electronic product that potentially remains relevant at least a year later otherwise forget it.
so i sent this letter to HTC
after reading this page where HTC discusses 4.1 upgrades i decided to drop them a line "
DIRECTLY FROM YOUR WEBSITE:
When will additional devices receive Android 4.1?
In addition to the HTC One X and HTC One S, we are actively reviewing our product portfolio to identify candidates to receive Jelly Bean. Our goal is to prioritize review for devices launched in 2012 with our numerous carrier partners across multiple regions and then consider our ability to provide updates to products from 2011.
What devices will not get Android 4.1?
We work hard to ensure each of our products has the optimal user experience and therefore some products will remain at their current version of Android. In general, devices with 512MB RAM or less will not be upgraded to Android 4.1. At present, these devices include the HTC One V and the HTC Desire C. As we identify other devices that will not be upgraded, we'll provide updated information.
What about a development version of Android 4.1?
For our developer community, we plan to make generic development ROMs of Jelly Bean available for both the HTC One X and HTC One S. As soon as the ROMs are ready, they will be posted to our HTCdev site (www.htcdev.com). We strongly recommend customers take the time to understand the limitations of the development software along with the terms and conditions on the site before downloading to their device.
REALLY!? have you listened to what your customers have asked/said about the HTC flyer at all?! where is OUR 4.1 DEVELOPMENT ROM! wtf! where are you for us!? I can tell you where... you are giving us 3.2 HC that takes away two very important features i bought the device for #1 GPS! completely broken by your newest update to HC. #2. Hardware Keys.... WHY?! i understand that HC introduced soft keys. so you say you "We work hard to ensure each of our products has the optimal user experience" BULL! you clearly weren't thinking about the end user when you pushed out that HC update for the flyer. Would have been smarter for you to leave us on working GB and go straight to ICS or JB when it was ready! this is lunacy! who ever is making decisions in your company needs fired. you are bleeding money from everywhere. why don't you bring it back to the old school HTC that CARED! ABOUT! IT'S CUSTOMERS! listen to what we are saying! hear our voice! we have signed petitions. we have pleaded on multiple forums. WE have poured over your FB and twitter pages asking for you to throw us a freaking bone here.... when is it gonna happen? ever?!
I still have my flyer and i love it dearly. but without updates it's falling behind the pack. I recently bought a 10.1 galaxy note. while i'm happy with it's speed and what not. it's not the form factor i want. which is what the flyer is for me. perfect. PLEASE DON'T GIVE UP ON US OR THIS DEVICE! PLEASE RELEASE A DEVELOPER ROM FOR OUR FLYER! "
this was their reply (you will want to read it for sure)
Dear Matt,
Thanks for contacting HTC!
We completely understand your concern and I thank you for your patience and am deeply sorry if this issue has caused you any dissatisfaction with HTC or its phones. I hope that it will not detract from your overall perspective of the device or the company. You are the most important part of the HTC Family.
We listen to our community and feedbacks like yours are the ones that make us revise our decisions, and try to find the correct balance between the device’s performance and usability. We cannot announce or say anything about the Flyer right now but what I can tell you is that we are, indeed, paying attention to the community´s feedback and opinions.
Should you require further assistance, please do not hesitate to contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.
Have a great day!
Let me know if I have successfully answered your question, please click here to complete this.
To send a reply to this message, please click here.
Sincerely,
Carlos
HTC
I appreciate the passion here, but HTC left this device for dead along with the Jetstream and View shortly after releasing it. We received what would amounted to a Beta of Honeycomb then they closed up shop. You live and learn, and although I still use my Flyer and enjoy it I will not buy another HTC device
I completely agree with you .. HTC should give us ICS or JB for our Flyer as a good faith. We must keep GB because honeycomb is a joke..
I use my Flyer and i try as much as possible with the optimized news on GB .. and share with you.
Hoping for a good action on their part for JB!!
Fatal1ty_18_RUS said:
Then we would need not just the drivers, but the whole 3.x kernel. I believe it's much harder to adapt ICS/JB drivers to GB/HC kernels
Click to expand...
Click to collapse
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
gersto said:
so the kernel source for HC 3.2 that's in HTCDev,,that is NOT the entire kernel sourcecode?
i know it's an old thread but i am wondering...
Click to expand...
Click to collapse
that the honeycomb kernel .
doesn't do you much good for ICS or JB
yncconsulting said:
Then we're asking the wrong ppl, it's not HTC. to understand this first you need to understand what makes up a ROM.
.
.
.
Click to expand...
Click to collapse
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
You didn't understand I think. The drivers are part of the kernel. May they be compiled into the kernel itself or in form of modules. Drivers can be binary objects to be linked (already compiled) or source code which will be compiled when the kernel is built.
If you have the drivers source code there is a fairly good chance to get them running in newer kernels with some minor changes.
So from my point of view you will have a good chance to even get 4.2 up and running as long as you have the drivers source code.
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
DigitalMD said:
that the honeycomb kernel .
doesn't do you much good for ICS or JB
Click to expand...
Click to collapse
well they must be of some good since we have ICS/JB ROMs out there that are "mostly" complete, slick and usable, although slightly buggy, so obviously yeah i get that it doesn't solve all the issues we have, since some drivers are missing: as evident by the non-working FC, no hardware decoding for video, and semi-working BT
DigitalMD said:
yeah, so my point is HTC publishes kernel source code, not drivers, they don't even own some of the drivers .,so you will never get that. You get a HC kernel ,that works with a HC blob set and you cannot build a working 4.xx kernel because you don;t have a 4.xxx blob set and HTC won't give you one because they have never written one and never will
Click to expand...
Click to collapse
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
ktp1976 said:
Not exactly. The kernel is also part of AOSP. And even if HTC does not supply the driver sources there is a slight chance to use old driver binaries or to have them reverse engineered by some genius dev. Hope is the last to die
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
DigitalMD said:
Keep dreaming. Some of the best around have tried that path.
No the device kernel is not in AOSP, the base linux (ANdorid) kernel source resides there, but if you look at the build, it calls in device , vendor, OS verson and board specific components to make a complete build. All that hooks into the blobs (drivers and libs) to make up the device specific environment that allows Android version X.XX to run
Click to expand...
Click to collapse
Thanks for clarification. So I was not wrong about the drivers, which are the device and vendor specific components. In other words if you can get the vendor to release their sources or make their chip/board manufacturers to release their sources is the only way to go. Seems a bit unrealistic though but who knows...
Sent from my GT-I9100G using xda app-developers app
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
freworld said:
All should email the HTCDev
Use this link http://www.htcdev.com/contact
They themselves posted on that link
https://www.facebook.com/photo.php?fbid=10151213304969443&set=o.101063233083&type=1&relevant_count=1
Takes just f**kin 5 seconds
May be they will listen some day
Click to expand...
Click to collapse
+1
Ok now I'm a "noob". I know nothing of coding or building but I do know basics of Android flashing and modifying from the work of amazing developers here.
Problem is I can't understand certain things about why Google makes such decisions with their stock os and being a noob with what's approaching a year with android (first device was a HTC one x but currently own a s3) I've usually avoided making a post like this to avoid the flame from users who don't even know the answers themselves but just love to yell noob and go do some searching But over these 8 months i have but to no avail. So here goes
1. Why doesn't Google support Facebook contact sync even though HTC and Samsung (may be others buy I only owned these 2) and on their jellybean updates as well. I read somewhere hat it has to do with api but if so why does everyone (I know) use it but them?
2. Why doesn't the stock gallery app support gif images?
3. Doesn't want cyanogenmod using multi window but Samsung can with no public threats made?
4. What do they have against large storage volumes(32-64gb/expandable memory)
5. Why do they not do a pc host update. I mean like how apple has updates through iTunes. I don't mind questioning 3rd party manufacturers like Samsung or HTC but I mean come on why do they NEED to wait for carriers to push an update to phones they provided the code for (I use that loosely)
Those are the five questions that just tug at me when using an aokp based rom as I love the speed but hate the absence of functionality and other questions that I'm curious about.
Thanks in advance and please don't flame me
Sent from my GT-I9300 using xda app-developers app
large storage devices
"It's a conspiracy, man!"
Read somewhere that Google wants to know everything about you. So, having no expandable storage on their devices will force you to find "cloud" based storage, preferably with any of Google's services.
I don't care, as long as it is not Apple.
Cuz HTC and Samsung have different GUI.. Samsung has Touchwiz while Htc has Sense..
Sent from my GT-I9300 using xda premium
Concerning question 4 it's not a question of size... as you know..
It's a question of filesystem format. Exfat used for 64gb cards is Windows proprietary, so only available with Sammy Rom, as they bought the right to use the license. As long as no(open) source is available, official cm and others won't provide compatibility.
And yes, Google phones, nexus ones are sold without sdcard, to push cloud use up. And Google develops mainly for... Google.
CHEVYbarracuda1 said:
Cuz HTC and Samsung have different GUI.. Samsung has Touchwiz while Htc has Sense..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I'm guessing you don't understand what I asked
Hello. Prompt, please, can I port android 4.4 (in this case CyanogenMod 11) in this manual ( http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305 )? Is it even possible to port it, at least 4.0. Sorry for my bad English.
Can anyone try it?
No drivers. It is completely infeasible. Stop asking.
bad news
bad news
This device would be amazing with kitkat on it.
I wish.
The HP touchpad just got CM11 and it uses the same snapdragon s3 APQ8060 as the jetstream. Maybe its possible to port that?
Sent from my Nexus 5 using XDA Premium 4 mobile app
i'll tell show_p.
the problem is the HTC drivers, which cannot be ported from any other device. maybe there's something in the HP.
killahrey said:
The HP touchpad just got CM11 and it uses the same snapdragon s3 APQ8060 as the jetstream. Maybe its possible to port that?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As silly as it may sound. I literally now have no use for my jetstream as I am fully fed up of the OS it has. I have it rooted and CWM 6.0 installed on it and flashed BMW Boy rom on it. At this point, I am willing to work with developers to come up with a custom rom for it. I will be more than happy to test it on my device if they need me to. Plus, I can provide any information needed about this device. I am getting into developing, so perhaps Jetstream could be used as an ultimate sacrifice lol.
Just rooted SGH-I317M (NOTE II-Rogers) and installed CM 11 Nightly on it. I refuse to go back to stock. Im loving my phone so much more.:good:
can we?
Is it possible to build the drivers from scratch? Even if it is not for free we can all pitch in and pay a developer. Hopefully HTC can help despite our many failed efforts. I am willing to pay to get this device up to date, it feels to wrong to let something so full of potential go to waste. Even today it still looks better than most tablets available. I love my jetstream !
e1rokr said:
Is it possible to build the drivers from scratch?
Click to expand...
Click to collapse
Go to www.codeaurora.org and find the Android for MSM project. I tried to backport some of the code from that project into Hive kernel.
finniest said:
Go to www.codeaurora.org and find the Android for MSM project. I tried to backport some of the code from that project into Hive kernel.
Click to expand...
Click to collapse
Will do! Just talked to an HTC rep. She apologized for the lack of support and sent a ticket of the conversation to HTC in hopes of assistance. She is even going to try to talk to her higher ups and hope that they are generous! My hopes are not that high but i was really glad to talk to someone who was concerned with the matter. She could not even believe what i was telling her ( she never used honeycomb so i am guessing she was surprised with what we have to go through.) I hope 2014 will be different for the Jetstream. O and i never thanked you for your hard work so ill take the time now. Thank you for your assistance, it means a lot to me and the other people with the jetstream here at xda! Great work and an awesome rom!
Salm sava
http://blog.gethuawei.com/huawei-device-usa-updates/
Sent from my MT2L03 using XDA Free mobile app
Was just about to post this. Disappointed. There better be a damn good reason for this.
The Instagram page says "Stay tuned to see what the future holds."
Sent from my MT2L03 using XDA Free mobile app
Look for their facebook page. Huawei devices usa or something. Mine should be the first comment.
Sent from my MT2L03 using XDA Free mobile app
Those developers that got a free Mate 2 are our only hope now.
I guess that's why they gave them out. "Can you guys make ROMs for us? We're too lazy."
Sent from my MT2L03 using XDA Free mobile app
Would like to ask everyone who reads this and wants kit late to post all over their Facebook and twitter pages
"We want Kit kat for the ascend mate 2.
But you chose not to.
NEVER AGAIN"
Maybe some negative pressure will make them rethink.
Sent from my MT2L03 using XDA Free mobile app
ScoobSTi said:
Those developers that got a free Mate 2 are our only hope now.
I guess that's why they gave them out. "Can you guys make ROMs for us? We're too lazy."
Sent from my MT2L03 using XDA Free mobile app
Click to expand...
Click to collapse
Huawei is basically saying "you're on your own" to anyone who received a device as a devloper. That's not a great position... It's a pretty solid slap in the face. My first thought as a developer is "ok, they are out, why would I bother". I'd cut more slack if the device was 18-24 months old but they are pushing this as their flagship currently and an alternative to the more expensive phablets on the market. Even Samsung provides "reasonable" support for "old" flagships better than this.
The crazy thing is the hardware should be more than able to keep up with 4.4/5.0. Unless they are jumping right to 5.0 this move makes 0 sense to me.
Modding. Mymind and xordos with my continual softbrick testing have managed to port a pretty much fully working TWRP onto my MT2-L05 device and I have uploaded a decrypted 4.4.2 rom for my Mate 2 in this forum, so why don't we collectively try and port it to your device, any help you need that are within my skillset I will happily provide....just a thought.. .... Download the rom I posted and see what you can come up with.. ..... .
4L0M said:
Modding. Mymind and xordos with my continual softbrick testing have managed to port a pretty much fully working TWRP onto my MT2-L05 device and I have uploaded a decrypted 4.4.2 rom for my Mate 2 in this forum, so why don't we collectively try and port it to your device, any help you need that are within my skillset I will happily provide....just a thought.. .... Download the rom I posted and see what you can come up with.. ..... .
Click to expand...
Click to collapse
Does Huawei use a tool like RSD or Odin for system images or are devs stuck with manual disk images and the like via recovery?
Hmm, I was thinking about getting one of these, now I'm having doubts. If we only
get third party firmware, would I still be able to run software which will not run with root access ?
Have any of those developers who received the free phones mentioned their intentions?
dzr said:
Hmm, I was thinking about getting one of these, now I'm having doubts. If we only
get third party firmware, would I still be able to run software which will not run with root access ?
Have any of those developers who received the free phones mentioned their intentions?
Click to expand...
Click to collapse
Right now I'd hold off. Buy something else. The operating system on this phone is already a year old. Support for things like Android wear etc will be questionable in 6 months.
If Huawei doesn't update it's phones you should go with something else. Just my opinion.
Sent from my MT2L03
I saw the blog post on my G+ feed earlier today. I'm not really shocked, but it still really feels like a kick in the teeth.
I'm not sure what kind of luck we'll have getting a custom KK/LP Rom running on this phone. Usually the manufacturer-provided ROM is used as a baseline for other modifications to be made. If we were to spin our own AOSP Rom, could we even find the drivers and kennel modules to make everything work?
Where do we go from here?
UrticantOwl said:
I saw the blog post on my G+ feed earlier today. I'm not really shocked, but it still really feels like a kick in the teeth.
I'm not sure what kind of luck we'll have getting a custom KK/LP Rom running on this phone. Usually the manufacturer-provided ROM is used as a baseline for other modifications to be made. If we were to spin our own AOSP Rom, could we even find the drivers and kennel modules to make everything work?
Where do we go from here?
Click to expand...
Click to collapse
The kernel is up on one of the hosted Huawei sites. A quick once over at the BABBQ indicated it's a fairly vanilla Qualcomm 3.4 kernel with some Huawei bits sprinkled in. Shouldn't be much of an issue for 4.4. getting a 3.10 kernel up for 5.0 will be trickier and is a big question mark as 5.0 isn't officially released just yet. At the BABBQ we also discovered they didn't implement all of the modem modes in the ROM. Another developer told me they might take a closer look but gave no detail for timing.
I've been tinkering with adb backups, titanium and xposed lately and I'm not liking the stock ROM much. They omitted large chunks of the adb backup stuff rendering apps like Helium useless, the SD cards don't come through to the root context properly forcing you to enable a compatibility flag in SuperSU in order to make titanium work and apktool and other standard tools choke nicely on the system apks. I had to fall back to running the smali decompiler by hand to find the right hooks in SystemUI for a simple xposed hack.
Adding to the fun their version of Settings.apk is missing a number of standard features which you can only adjust via Tasker/SecureSettings or by hand behind the scenes. They also didn't implement encrypted storage in the vold storage stuff so you're screwed in an enterprise setting.
Based on what I've seen thus far a source based build is almost necessary if you want everything android has to offer. However, vetting a ROM to ensure various new functionality is 100% will be a pain.
Huawei left out a lot and the lack of 4.4 is a serious kick in the teeth.
Horrible
I just purchased this phone from amazon on July. I wouldn't mind the no update but I want to get a google watch in the next few months so I'm not very happy about this announcement. For some odd reason, Amazon is still letting me return this phone so I'm thinking of returning the phone. What is another phone that I can get at this price range?
kemonine96 said:
Does Huawei use a tool like RSD or Odin for system images or are devs stuck with manual disk images and the like via recovery?
Click to expand...
Click to collapse
You can use Huawei's Hi-Suite software to flash roms to phone from pc. You can also pack roms up into Huawei's update format and flash them in quick update mode from your phone's external sd card, or you can install via recovery.
I bought mine on September 29 (didn't get it until early October) through the gethuawei site. I wonder if I can return it... I'll find out when there livechat is live today, the 29th of October.
After just one minor OTA update they officially announce no additional updates for their only US device... That's a deal breaker for me.
Damn, I was just about to buy this phone. Does anyone know of any good alternatives in Canada?
drvenom123 said:
I just purchased this phone from amazon on July. I wouldn't mind the no update but I want to get a google watch in the next few months so I'm not very happy about this announcement. For some odd reason, Amazon is still letting me return this phone so I'm thinking of returning the phone. What is another phone that I can get at this price range?
Click to expand...
Click to collapse
_Perpetrator said:
Damn, I was just about to buy this phone. Does anyone know of any good alternatives in Canada?
Click to expand...
Click to collapse
Nexus 5? Used flagships?
Sent from my MT2L03 using XDA Free mobile app
Go spam them on g+! + my comment! (Seth Hin)
https://plus.google.com/116259104144339004134/posts/MwgooqkQpwK
Not surprised , saw this coming from the early start . Thing is , there is no alternative with these features / size at the 299$ price tag . There are phones like the ZTE nubia / moto g / Blu products / etc but they don't hold a candle to this phablet . On another note , I've customized my phone to the max and i don't need a major OS update . Just me , this phone runs perfectly for my use . Fine if they just push minor OS fixes via OTA . Developers can be our saviours ! Let's not forget this isn't really a flagship ! You're paying for the experience as created/intended at the time . Let's wait and see :thumbup:
_Perpetrator said:
Damn, I was just about to buy this phone. Does anyone know of any good alternatives in Canada?
Click to expand...
Click to collapse
Probably the Samsung Galaxy Mega.
Sent from my MT2L03
Does anyone know if there are manufacturers that are not determined to lock down their devices against user modification, i.e. who deliberately make their devices easy to root and flash for those of us inclined to do so?
[Some context: I just bought a Fire 7 (5th gen) that was unfortunately updated to 5.3.3.0, and definitely feeling frustrated about the lack of options, and willing to pay more for a device that has such options available. ]
***Feel free to move if this isn't the right forum, or post a link if this question has already been answered.***
a better thread can be found here https://forum.xda-developers.com/showthread.php?t=1620179
but other users can post their thoughts here as well
Feenix0 said:
Does anyone know if there are manufacturers that are not determined to lock down their devices against user modification, i.e. who deliberately make their devices easy to root and flash for those of us inclined to do so?
[Some context: I just bought a Fire 7 (5th gen) that was unfortunately updated to 5.3.3.0, and definitely feeling frustrated about the lack of options, and willing to pay more for a device that has such options available. ]
***Feel free to move if this isn't the right forum, or post a link if this question has already been answered.***
Click to expand...
Click to collapse
Google Nexus and Google Pixel devices are not locked down, nor will they be in the future I believe. They want them customizable so that users participate in Android Open Source Project(AOSP) development. They encourage the community to tinker with their devices, they may come locked when you buy it but the unlock, rooting and flashing methods are pretty easy to do on all of them.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Google Nexus and Google Pixel devices are not locked down, nor will they be in the future I believe. They want them customizable so that users participate in Android Open Source Project(AOSP) development. They encourage the community to tinker with their devices, they may come locked when you buy it but the unlock, rooting and flashing methods are pretty easy to do on all of them.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
While true for the nexus this is not the case with the pixel. Google is closing off the OS for their devices and not pushing that code to aosp.
The only real dev friendly oem right now and I really hate to say this, is the One plus.
zelendel said:
While true for the nexus this is not the case with the pixel. Google is closing off the OS for their devices and not pushing that code to aosp.
The only real dev friendly oem right now and I really hate to say this, is the One plus.
Click to expand...
Click to collapse
Well bugger, I didn't know that, what is Google thinking, that's gonna ruin the whole global participation in development.
I knew the One Plus devices were also developer friendly but I had the impression that Google devices were slightly more so.
Sent from my SM-S903VL using Tapatalk
Droidriven said:
Well bugger, I didn't know that, what is Google thinking, that's gonna ruin the whole global participation in development.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yeah. The whole system ui is completely different. You have to remember Google hates what we do here. The only people they really want messing with the OS is the oem. Not so much people like us.