Related
http://gizmodo.com/5820527/your-android-tablet-just-got-better-whats-new-in-android-32
Here's a link to a post at Gizmodo. Looks like a minor though probably necessary update. Anyone know when it will get rolled out to our Iconia's?
Thanks for reporting this....
tazm0n said:
http://gizmodo.com/5820527/your-android-tablet-just-got-better-whats-new-in-android-32
Here's a link to a post at Gizmodo. Looks like a minor though probably necessary update. Anyone know when it will get rolled out to our Iconia's?
Click to expand...
Click to collapse
Knowing Acer, August 2013.
Yup, Xoom WIFI was getting the 3.2 update a few hours ago. The most interesting feature is probably the zoom feature: http://www.androidpolice.com/2011/0...new-zoom-mode-for-viewing-non-honeycomb-apps/
Non-Honeycomb apps support? Even with pixelation, Hell yes!
brutalpanda said:
Yup, Xoom WIFI was getting the 3.2 update a few hours ago. The most interesting feature is probably the zoom feature: http://www.androidpolice.com/2011/0...new-zoom-mode-for-viewing-non-honeycomb-apps/
Non-Honeycomb apps support? Even with pixelation, Hell yes!
Click to expand...
Click to collapse
Sounds nice. Unfortunately the biggest problem isn't the resolution. The biggest problem is attempting to get them to run without FC 80000 times.
Anyone know if 3.2 supports the HSP for bluetooth? I want to be able to use my headset with this bloody thing.
from the original article. link
3.2 will offer some bug fixes and improved hardware acceleration, as well as updates to Movie Studio, Movies, Music and widgets.
I wait two more weeks and if they would not release their f***** 3.1, the tab will be sold for a better product with better support.
These Acer support people are just jokes
godsosall said:
I wait two more weeks and if they would not release their f***** 3.1, the tab will be sold for a better product with better support.
These Acer support people are just jokes
Click to expand...
Click to collapse
They HAVE released the 3.1 update. Its just taking time to roll it out to everyone, just like FOTA updates do to phones.
FloatingFatMan said:
They HAVE released the 3.1 update. Its just taking time to roll it out to everyone, just like FOTA updates do to phones.
Click to expand...
Click to collapse
Please correct me if I'm wrong, but I read the A500 3.1 update had been halted, as in no one new is getting it at all until further notice.
deedub334 said:
Please correct me if I'm wrong, but I read the A500 3.1 update had been halted, as in no one new is getting it at all until further notice.
Click to expand...
Click to collapse
What you've been reading has not been confirmed by any official Acer source, it's just what people have posted saying they were told by some guy on the phone at Acer. That's rumour, not fact.
In fact, over the last couple of days, several people HAVE been reporting getting the 3.1 update. Try taking a look in the dev section.
I think people often forget.ideally when devices computers get a update its all about fixing or providing enhancements. But often we forget that updates that come to soon.updates that are not carefully debuged and checked will almost always break something else. I would rather have fewer but larger rolled up updates then the tiny uncontrolled untested to be true. Remember your windows machine. Updates are a mess and daily. And always risky even more so on firmware.
patience wins over in the long run.
With that said.
ACER GET IT RIGHT don't make us have to wait to long or we will all stop breathing and go into a anti update shock
giggles it will come. My friends
erica_renee said:
I think people often forget.ideally when devices computers get a update its all about fixing or providing enhancements. But often we forget that updates that come to soon.updates that are not carefully debuged and checked will almost always break something else. I would rather have fewer but larger rolled up updates then the tiny uncontrolled untested to be true. Remember your windows machine. Updates are a mess and daily. And always risky even more so on firmware.
patience wins over in the long run.
With that said.
ACER GET IT RIGHT don't make us have to wait to long or we will all stop breathing and go into a anti update shock
giggles it will come. My friends
Click to expand...
Click to collapse
Exactly my points below
Too many build #.... Acer -->> no clues !!
rorytmeadows said:
Knowing Acer, August 2013.
Click to expand...
Click to collapse
It's not the update that I am concerned about ( XDA always comes through )
It's Acer's damn un-organized way of having so many build #s !!!
One thing that having so many build numbers tells me:
They have no clue as to really ironed out the bugs, that's why their are so many different builds !
with Acer.... even among their same region ( Com_Gen1.... or EMEA for example )... even with those.... there are so many build numbers for the same region !
Look at Asus... they basically have only 2 builds..... 1 for US & 1 for WW ( worldwide )
try weeding through all those build numbers with tech supports and you can see why nobody can get a concrete answer.... due to the lack of being on the same page...etc
If any one who actually have contacts with Acer on the inside.... for Godsake.... relay this problem to their head of department, please !!
how difficult is that ??
Which I imagine is why a second update is being rolled out at the moment?
I suspect that the previous update did have issues and Acer has realised this and is attempting to resolve things. Pure conjecture on my part, but it seems odd to push two updates within a one week period.
Intentional leaks to keep users happy without upsetting Google.
www.androidpolice.com/2012/02/22/an...nia-tab-a500-and-a100-ahead-of-april-release/
Might be something of using there for Pauls unofficial ICS rom?
Sent from my LT18i using Tapatalk
I wouldnt be so quick to put Acer in a pedestal. Not only do they NEVER address their customers, but also have locked and signed bootloaders with no intention of unlocking them. Now, I dont think Asus has been fast or great to their users, but at least they communicate, listen, and are delivering updates way faster than the rest. (Pretty much every honeycomb device is projected to get an ICS update during Q2 or later, Asus is working for a late Q1 update...)
This is ICS related.
I might be wrong, but I thought we had a place for this sort of stuff...
OH WAIT, THAT'S RIGHT! IT'S THAT VERY FIRST STICKIED THREAD CALLED, "READ THIS NOW !!!•••POST ALL ICS AND ICS RELATED INFO HERE ONLY !!!!!".
Just sayin'.
CrazyPeter said:
Intentional leaks to keep users happy without upsetting Google.
Click to expand...
Click to collapse
This has never had *anything* to do with upsetting Google. Google couldn't care less if Asus releases for the TF101 tonight. They couldn't care less if they never release at all. Any Google approvals were given when the Prime build was finalized; beyond that Google isn't involved any more. Asus were just trying to make excuses, and Google made an easy scapegoat, because they won't comment.
The lack of truth to Asus' claim to be waiting for Google came when Asus themselves subsequently claimed the delay was down to their own techs being off for Chinese New Year, ie. not waiting for Google at all. Truth be told, the build has almost certainly been ready--at least, in as much as the Prime build was ready--from the same day the Prime build shipped. Asus have just chosen not to release for the TF101, likely initially because they wanted to build hype for the Prime (and "reward" Prime users for spending money more recently), and later likely because they realized a lot of Primes were being bricked, and didn't want to deal with warranty repairs for an even greater number of bricked TF101s, which are in the wild in far greater numbers.
Hence, we sit and wait until Asus fixes the TF201 problems, has sufficiently long to decide they're no longer bricking tablets, twiddles their fingers a bit, and then finally releases the TF101 build that's been available inside Asus all along.
At least, that's my (logical) guess.
CrazyPeter said:
Intentional leaks to keep users happy without upsetting Google.
www.androidpolice.com/2012/02/22/an...nia-tab-a500-and-a100-ahead-of-april-release/
Might be something of using there for Pauls unofficial ICS rom?
Sent from my LT18i using Tapatalk
Click to expand...
Click to collapse
What a strange post to make on the very day ICS is released for the Transformer.
psinno said:
What a strange post to make on the very day ICS is released for the Transformer.
Click to expand...
Click to collapse
Yep! I bet now people will start whining about when ICS is going to be released in their region
There's been a lot of speculation about just how Nexus-like the Galaxy S4 and HTC One Google Play edition phones will be, particularly from a technical / software update standpoint. Now, we have some relatively concrete information that sheds light on these issues.
First and foremost, Google will not directly handle software updates for Google Play edition devices. This has been reported as true, false, and generally disputed quite a lot in the lead-up to the launch. We know for a fact now (thanks to Anandtech) that while Google will supply the necessary Android builds to OEMs, the OEMs will be responsible for maintenance of kernels and all the various drivers and firmware pieces necessary for their specific device. The result is that Google gives the OEMs the Android build, and it's then up to the OEMs to make that build work on their Google Play edition device and perform the act of actually updating the phone. Google has issued an official statement that works very hard to not expressly deny that they won't be handling the updates (Droid-life):
What's this mean for you? It means that at the end of the day, the onus to update these phones will still be on Samsung and HTC. They will be able to circumvent the carrier certification runaround, and will in theory have much less work to do in maintaining these devices, but the responsibility still falls to them, not Google. This could mean any number of things. It could mean these phones will get updates within days of their Nexus counterparts. But more likely weeks, and possibly even months depending how much attention these phones are actually given by HTC and Samsung. I wouldn't say months is what we should expect, but I'm also saying such a gap is entirely within the realm of possibility. You have to remember, these phones will sell in miniscule quantities compared to their skinned brethren, and that means they aren't as high up on the value chain for software update attention. While it's certainly worth being optimistic about the update process, there's still plenty of reason to temper those expectations until we see these devices receive their first major Android release update.
he second thing we've learned is that Google will not host factory OS images for Google Play edition devices (see JBQ's post on this topic here). This will be up to Samsung and HTC, if they choose to do so. Google will also not be hosting any proprietary binaries (essentially, drivers) for these phones (again, see JBQ). Release of any binaries is, once again, up to Samsung and HTC. Taken together, all this information - as you may already have guessed long ago - means there is very little chance we'll ever see these phones supported in AOSP. It's not impossible, but it is extremely unlikely.
So there you have it: that's basically the nuts and bolts of what doesn't make the Google Play edition HTC One and Galaxy S4 Nexuses. Does this put a damper on the situation, or is it immaterial? Let us know in the comments.
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
welp this sucks !
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
H-Streety said:
I am not flashing this until first update comes out to see how fast they actually are, ridiculous decision.
Click to expand...
Click to collapse
Since we will probably be on 4.2.2 for a while you're going to be waiting.
Sent from my HTC One using Tapatalk 2
Possibly, but I am not losing my IR blaster and camera app for half-supported stock Android. If HTC will push out the update within a week or two after it comes out for Nexus devices, then I will definitely flash it, if not then I don't see the point of it. I would rather do S-OFF + Super Cid and still enjoy all these things than losing too many good things for basically just stock Android.
Nexus Experience Device not Nexus Device
That's really unfortunate.
Pretty ridiculous actually.
-Sent from Marino's One-
Did you really expect more? Google never said they would be Nexus devices or supported by AOSP. They are Nexus "Experience" devices... hence they offer the same feel without being the same.
Sorry to burst your bubble.... that said I think there will be dedication on the part of HTC and Samsung to get updates.. there isn't any excuse and you know if the device is on Google Play then el'Goog will be pressuring them to not delay
Sent from my Nexus 10 using Tapatalk HD
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version.
I believe that more that others guessing about it.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Zero timeline given. It will get it. The second it's released? No. A month after? Maybe.
Yep, OP...sure this is stock AOSP, but if anyone thinks the S4 and One will be updated the instant the Nexus line is, they are smoking some serious ****.
Samsung and HTC still have a role in this, ala Verizon (CDMA) Galaxy Nexus. It will slow things down. It's on HTC and Samsung to instantly update their proprietary apps to play well with AOSP. We've all seen that movie before, now have we?
Sigh. Can of worms. I called it. Once you integrate manufacturer specific features into AOSP (Beats, Zoe, etc) it WILL slow down the instant (expected) release of AOSP to "OMG PURE GOOGLE) phones. Psst: they aren't Nexi.
Just deal with it. I cringe for the blasting posts from those who got the One/S4 AOSP editions once the newest Android OS is pushed out...to the Nexus line first.
I see it now:
"THE NEXUS 4 JUST GOT 5.0. WHERE IS MY KLP ON MY ONE/S4 GOOGLE!??? PETITION STARTED!!!!1111"
And so on. Grabs popcorn.
Edit: thought I'd paste in a quote I just read that summarizes this situation quite well:
I don't see the point of these devices anymore. You lose out on the few customization that OEMs provided that weren't useless (fully functional Beats, camera software, improved text messaging and browser apps, etc.) for a vanilla experience that is nearly indistinguishable from the OEM version running a custom launcher. And no guarantee of fast updates.
You'd have to be a dummy to buy these phones from the Play store.
Thankfully I have an unlocked T-Mobile One. I'll just use it or flash whatever, whenever. Paid $450 for it and am very happy with my gamble.
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
donharden2002 said:
It states in Google play that both devices will get automatic updates of the latest android version. I believe that more that others guessing about it.
Click to expand...
Click to collapse
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
BarryH_GEG said:
Automatic = sent directly to the phone.
Updates = it'll be updated.
Latest Android version = it'll get newer versions of Android.
The key words that are missing are "when" and “from whom.” I guess people can read in to that statement what they want but nothing in it makes what OP posted untrue. With so many phones orphaned on old versions of Android that statement could be as benign as "your phone will keep up with Android releases."
Click to expand...
Click to collapse
google is the only one who can update aosp devices..nobody else
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
david279 said:
http://www.androidpolice.com/2013/0...play-edition-one-or-s4-oems-will-handle-otas/
Click to expand...
Click to collapse
you are a thick one aren't you lol
hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
The first post says it isn't an AOSP device, Google isn't managing the proprietary drivers, they aren't posting the s/w images, and they aren't responsible for pushing out updates. So your statement is true; for Nexus devices. "Play Edition's" aren't Nexus devices.
The fact that it doesn't say the below which Google says about their devices probably means what OP posted is true.
M
Argenist said:
So the question still remains, could someone possibly take whatever HTC releases for the GE version and put that on a carrier locked or Dev edition phone? Sorry for my lack of understanding here, but I'm just trying to figure out which phone to buy at this point.
Click to expand...
Click to collapse
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands for resale and every day use. Hint. It isn't the Google or Dev one.
Unlock it for $7 and never look back.
Sent from my HTC One using Tapatalk 2
ericshmerick said:
You can flash whatever you want. Nothing new here.
I say get the phone with the most bands. Hint. It isn't the Google or Dev one.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Understood, but would matter then to get the GE version over the Dev?
Argenist said:
Understood, but would matter then to get the GE version over the Dev?
Click to expand...
Click to collapse
They don't ship until July 9 so no one knows.
Sent from my HTC One using Tapatalk 2
hello00 said:
google is the only one who can update aosp devices..nobody else
Click to expand...
Click to collapse
Not true..
This situation has been done before. The OG Droid (Sholes) was not a Nexus but ran vanilla software. Updates came but abit later. They came from Motorola.
Sent from my HTC One using Tapatalk 4 Beta
So as the interwebz suggest, 4.4.1 is right around the corner for the Nexus 5/GPE devices. Considering the fact that the VZW variant of the Moto X was on the bleeding edge of the Kit Kat OTA and got it before even the Nexus 4, do you think this is a trend that will continue? I'm interested to see what bug fixes there are and if the promised camera improvements will be aimed specifically at the Nexus 5, or perhaps broader improvements to the software. What do you guys think?
I don't think 4.4.1 will aim other devices. It will include fixes for Nexus 5 only IMO.
I'm worried about the next update. What if we can't get root?
natezire71 said:
I'm worried about the next update. What if we can't get root?
Click to expand...
Click to collapse
Then you buy a developer's edition.
natezire71 said:
I'm worried about the next update. What if we can't get root?
Click to expand...
Click to collapse
This is one big reason I went for the Dev Edition... I'm too much of a tinkerer to fret over such unknowns. I mean it always comes eventually, but with Dev Editions you get instant gratification! Just need to flash stock recovery, accept the OTA, reflash custom recovery, re-root. BAM, done.
natezire71 said:
I'm worried about the next update. What if we can't get root?
Click to expand...
Click to collapse
I've been using an Android phone since 2.1.
By my quick count on Wikipedia, there have been 27 versions (including minor updates) of Android since 2.1.
I'm not aware of any Android version that was discovered to be unrootable.
I suspect you don't have to be too worried...
icon123 said:
Then you buy a developer's edition.
Click to expand...
Click to collapse
Buy me one? I don't have that kind of money.
Furthermore, I have a Motomaker custom. I don't want to lose that.
kbluhm said:
This one reason I went for the Dev Edition... I'm too much of a tinkerer to fret over such unknowns. I mean it always comes eventually, but with Dev Editions you get instant gratification!
Click to expand...
Click to collapse
I beat you by about 5 sec. But really, that's what this game has come to. If you want easy root and possibly romming, then dev editions are going to be the only way to go. Right now, I think moto is making that easier for us to do.
binary visions said:
I've been using an Android phone since 2.1.
By my quick count on Wikipedia, there have been 27 versions (including minor updates) of Android since 2.1.
I'm not aware of any Android version that was discovered to be unrootable.
I suspect you don't have to be too worried...
Click to expand...
Click to collapse
I suspect you need to do more reading. Check up on what security features KitKat brought to our MotoXs.
Edit: I'm not so much worried about If you can root it, I'm worried about having it published. Jcase only rooted 4.4 because we were able to downgrade the bootloader. If that wasn't possible, I still don't think there would be root for the MotoX (non-dev).
natezire71 said:
Buy me one? I don't have that kind of money.
Furthermore, I have a Motomaker custom. I don't want to lose that.
Click to expand...
Click to collapse
You simply sell your subsidized phone and buy a dev edition. Can't help you about the moto maker though.
natezire71 said:
I suspect you need to do more reading. Check up on what security features KitKat brought to our MotoXs.
Edit: I'm not so much worried about If you can root it, I'm worried about having it published. Jcase only rooted 4.4 because we were able to downgrade the bootloader. If that wasn't possible, I still don't think there would be root for the MotoX (non-dev).
Click to expand...
Click to collapse
I suspect I've read plenty about KitKat. I know about the security features.
Jcase rooted 4.4 using the downgrade because an existing vulnerability was available. He explicitly stated that there was another vulnerability available and he just wasn't going to develop for it/reveal it. Vulnerabilities are always discovered.
What, you think Apple hasn't been trying to quash rooting for years now?
I'm just saying, I've been in IT for a long time. Exploits are discovered, workarounds are created. Root access is gained and life moves on.
binary visions said:
I suspect I've read plenty about KitKat. I know about the security features.
Jcase rooted 4.4 using the downgrade because an existing vulnerability was available. He explicitly stated that there was another vulnerability available and he just wasn't going to develop for it/reveal it. Vulnerabilities are always discovered.
What, you think Apple hasn't been trying to quash rooting for years now?
I'm just saying, I've been in IT for a long time. Exploits are discovered, workarounds are created. Root access is gained and life moves on.
Click to expand...
Click to collapse
Of course, but what if it's never published? I'm not worried about the actual exploits. There will always be exploits. I'm only concerned with an awesome dev to publish it. Who else is working on the MotoX? So far, it seems like Hashcode and Jcase. If Jcase decides not to publish... Then what?
natezire71 said:
Of course, but what if it's never published? I'm not worried about the actual exploits. There will always be exploits. I'm only concerned with an awesome dev to publish it. Who else is working on the MotoX? So far, it seems like Hashcode and Jcase. If Jcase decides not to publish... Then what?
Click to expand...
Click to collapse
Well, there are never guarantees, of course... but given that virtually every version of Android on every phone attains root eventually, I'm just going to have some faith!
I think people may be putting too much faith in what devs can do based on what has been done.
4.4 has the potential to change things big time. dm-verity combined with a locked bootloader is going to be a beast to crack. Once a device ships from the factory with it enabled and a locked bootloader, I would not be expecting root on it anytime soon. Then you will have people asking why don't we just crack the key like they were when the GS3 came out. (answer: you will never ever crack the key. --Math)
As for using the idea that Apple has tried and never got it to stick, I'd say they haven't tried this hard.
Just as a sidenote, I don't think the SELinux and dm-verity additions in android are either bad or targeted at the modders out there. These are excellent steps in securing the OS, and shows that Google is serious about making devices trustworthy. The work they did on dm-verity is just great stuff. This is good for people who don't care about modifying their device and those who only buy devices with unlocked bootloaders, but not so good for people who have a locked bootloader, and are on either ATT or VZW, both of whom really don't want you to modify your device.
TL;DR - Buy a device with an unlocked bootloader, don't count on anything, past success is not indicative of future success.
I hope 4.4.1 brings an even better ART this time.
Seems like this update is pretty specific to the Nexus 5 as a camera fix. Not sure the Moto X will even see it.
Sent from my XT1056 using XDA Premium 4 mobile app
phippsy84 said:
Seems like this update is pretty specific to the Nexus 5 as a camera fix. Not sure the Moto X will even see it.
Sent from my XT1056 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Won't really know until the 4.4.1 source is published. Could be a lot of other stuff on the back-end that was updated/fixed that wouldn't really show up in a major changelog.
Nexus 4 received the update today too so it isn't nexus 5 specific.
imnuts said:
Won't really know until the 4.4.1 source is published. Could be a lot of other stuff on the back-end that was updated/fixed that wouldn't really show up in a major changelog.
Click to expand...
Click to collapse
Very true
Sent from my XT1056 using XDA Premium 4 mobile app
Not only the N4 but the Nexus 7 LTE. SO... probably more going on than just camera
Ok, Honor 8 in every page than we open on xda..
but, do we know if they're going to release the source code?
so we can get rid of this emui and install CM without too many bug..
do we have some info?
Source is out
papi92 said:
Source is out
Click to expand...
Click to collapse
What? Where?
iRoNX said:
Ok, Honor 8 in every page than we open on xda..
but, do we know if they're going to release the source code?
so we can get rid of this emui and install CM without too many bug..
do we have some info?
Click to expand...
Click to collapse
You can start working even if you don't have the source from Huawei, We did that on the P8 Lite (Kirin 620) and no one gave us any source.
I have heard that the Honor development department is reviewing the requests list that XDA sent. (However I can't find that list, maybe I am wrong). @svetius knows for sure.
EDIT:
I read about it here: http://www.xda-developers.com/honor-8-xda-review/#Dev
papi92 said:
Source is out
Click to expand...
Click to collapse
It isn't.
Still no official release, but I guess by the end of this month.
EMUI is good, but personally I perfer CM more.
I don't know. I like EMUI, using it with my Honor 6. But I feel that devs here could really improve it much much more thant Honor themselves could. I really hope that Honor/Huawei will release the source for their SOCs, as they are some really, really good ones.
CplBasti said:
I don't know. I like EMUI, using it with my Honor 6. But I feel that devs here could really improve it much much more thant Honor themselves could. I really hope that Honor/Huawei will release the source for their SOCs, as they are some really, really good ones.
Click to expand...
Click to collapse
That's what we hope, since Honor and XDA's partnership look promising
This is also something crucial for me.
No source-code released, no order from me!
hitardo said:
This is also something crucial for me.
No source-code released, no order from me!
Click to expand...
Click to collapse
I think than they will not receive many orders from xda users if there's no source-code released
iRoNX said:
I think than they will not receive many orders from xda users if there's no source-code released
Click to expand...
Click to collapse
Exactly, no source, no order.
His very high DAS (french) / SAR (english and different method) makes me doubt some more.
hitardo said:
This is also something crucial for me.
No source-code released, no order from me!
Click to expand...
Click to collapse
iRoNX said:
I think than they will not receive many orders from xda users if there's no source-code released
Click to expand...
Click to collapse
pix106 said:
Exactly, no source, no order.
Click to expand...
Click to collapse
Every time I read the word 'Source' at this section I think that people are not getting the point. If you think that a 'source' is what you need to magically have CM, AOSP etc then you are wrong, what you need is an interested developer (more than one if possible) who owns the phone (90% of the people posting, including me, don't).
This means that:
a) If Honor releases any kind of 'source', that doesn't mean that it's going to be complete, clear, or useful for porting roms (like the kernel, it isn't needed for that )
b) Even if they release something (and I doubt they will), it's not going to be 'plug and play'.
What I mean is, don't get too excited with any 'source' that comes from Huawei, the only way to know if this phone is developer-friendly is by waiting until you see projects coming.
I'm looking for a phone and so far the Honor 8 seems the most interesting for me. None of the other available phones really caught my interest. Nexus 5x, new google phone or Mi5 maybe but they all have flaws. And I really want something with NFC.
I'm not a fan of glass back phones but it does look real fancy on this one. No selling point but a nice bonus.
I'm planning on doing 'something' with the honor 8 if I get one. Kernel sources would help I guess. Haven't really messed with system code yet, just apps.
Hope they release it soon if they haven't yet.
Does Huawei normally release their sources? The Xiaomi Mi5 looks nice on hardware level (but no sd card slot) but I'm still a bit weary of Xiaomi.
Well even if they don't, we can still make EMUI based roms right?
Good luck to all developers. Hope I'll be one of you soon
miva2 said:
I'm looking for a phone and so far the Honor 8 seems the most interesting for me. None of the other available phones really caught my interest. Nexus 5x, new google phone or Mi5 maybe but they all have flaws. And I really want something with NFC.
I'm not a fan of glass back phones but it does look real fancy on this one. No selling point but a nice bonus.
I'm planning on doing 'something' with the honor 8 if I get one. Kernel sources would help I guess. Haven't really messed with system code yet, just apps.
Hope they release it soon if they haven't yet.
Does Huawei normally release their sources? The Xiaomi Mi5 looks nice on hardware level (but no sd card slot) but I'm still a bit weary of Xiaomi.
Well even if they don't, we can still make EMUI based roms right?
Good luck to all developers. Hope I'll be one of you soon
Click to expand...
Click to collapse
So far there was no good news for Kirin SoC.
jerryhou85 said:
So far there was no good news for Kirin SoC.
Click to expand...
Click to collapse
so you all "honor fanatics" can keep your sponsor, because maybe not many powerusers here on xda really want to buy this smartphone.
sorry but I just don't understand fanboys
my2cents
iRoNX said:
so you all "honor fanatics" can keep your sponsor, because maybe not many powerusers here on xda really want to buy this smartphone.
sorry but I just don't understand fanboys
my2cents
Click to expand...
Click to collapse
Haha, that's only a tag, nothing much... Just want to see HUAWEI really improve itself.
iRoNX said:
so you all "honor fanatics" can keep your sponsor, because maybe not many powerusers here on xda really want to buy this smartphone.
sorry but I just don't understand fanboys
my2cents
Click to expand...
Click to collapse
Lol you keep posting in any honor thread, you will have that same tag on your name...just keep it up...you will join us "fanatics" in no time.
FYI...you get the blue tag per how many posts you got in anything honor if you didn't get my jiff...so if you do not want to be a "fanboy" , better stop posting lol
my2cents
XePeleato said:
Every time I read the word 'Source' at this section I think that people are not getting the point. If you think that a 'source' is what you need to magically have CM, AOSP etc then you are wrong, what you need is an interested developer (more than one if possible) who owns the phone (90% of the people posting, including me, don't).
This means that:
a) If Honor releases any kind of 'source', that doesn't mean that it's going to be complete, clear, or useful for porting roms (like the kernel, it isn't needed for that )
b) Even if they release something (and I doubt they will), it's not going to be 'plug and play'.
What I mean is, don't get too excited with any 'source' that comes from Huawei, the only way to know if this phone is developer-friendly is by waiting until you see projects coming.
Click to expand...
Click to collapse
So let me get it as I am new to this, kernel source isn't crucial, and you need proprietary and vendors files to make development happen, right?!
PalakMi said:
So let me get it as I am new to this, kernel source isn't crucial.
Click to expand...
Click to collapse
It might be in some devices, but anyway, We now have it.
PalakMi said:
and you need proprietary and vendors files to make development happen, right?!
Click to expand...
Click to collapse
Yes, but you can find them inside a firmware update or even at your own firmware.
The problem is, that Huawei instead of creating their own files (they created some), they modified the ones that were already there, so there are lots of incompatibilities.
XePeleato said:
It might be in some devices, but anyway, We now have it.
Yes, but you can find them inside a firmware update or even at your own firmware.
The problem is, that Huawei instead of creating their own files (they created some), they modified the ones that were already there, so there are lots of incompatibilities.
Click to expand...
Click to collapse
So this makes it harder to build custom ROMS, now I get it