I have my Original Developer Edition turned into the GE so I can get the 4.4 update quickly.
Do you think its possible that the Developer Edition gets the 4.4 update before the GE?
This is based on now about 12 days until the DE gets the 4.4 update. This update controlled
by HTC not Google. Seems Google is holding back the GE 4.4 upgrade until
it sends out the 4.4 to all the Nexus devices. The Nexus 4 has to date not gotten the OTA.
What do you think? I am thinking to getting my Developer back the the 4.3 Sense version............
CC
Is 4.4 more important than Sense or not? It's surely better to wait than speculate.
my point
BenPope said:
Is 4.4 more important than Sense or not? It's surely better to wait than speculate.
Click to expand...
Click to collapse
My point is that the Developers Edition with Sense will receive the 4.4 update possibly before the Google Edition version
CC.
I know what your point was.
The difference between having Sense or not is far more than the difference between 4.3 and 4.4.
You seem to think being first to get 4.4 overrules that.
Nobody knows when the release dates are.
yes
BenPope said:
I know what your point was.
The difference between having Sense or not is far more than the difference between 4.3 and 4.4.
You seem to think being first to get 4.4 overrules that.
Nobody knows when the release dates are.
Click to expand...
Click to collapse
I hear ya, I am so right in the middle on this. Sense or Vanilla Android, I can't make up my mind!
What are you running? I have switched back and forth several times. (I am S-off so its easy to do)
CC
I'm on developer edition. I tried GPE, and having Chrome as the default browser was a deal-breaker. No way that I've found for pages to display in desktop mode without changing the setting every time I use it. I preferred the Sense interface anyway.
It is simply a matter of preference.
Related
Moving right along.
https://twitter.com/LlabTooFeR/status/353173541807616000
eXplicit815 said:
Moving right along.
https://twitter.com/LlabTooFeR/status/353173541807616000
Click to expand...
Click to collapse
At this rate I wouldn't be surprised if we see 4.3 and never see 4.2.2.
Sent from my rooted HTC One...
pmacevad said:
At this rate I wouldn't be surprised if we see 4.3 and never see 4.2.2.
Sent from my rooted HTC One...
Click to expand...
Click to collapse
Considering Google seems to have planned 4.3 as a "breather" update, that wouldn't be surprising to me in the least-- and I certainly wouldn't mind a jump right into 4.3. Here's hoping, though.
Rirere said:
Considering Google seems to have planned 4.3 as a "breather" update, that wouldn't be surprising to me in the least-- and I certainly wouldn't mind a jump right into 4.3. Here's hoping, though.
Click to expand...
Click to collapse
i doubt we will see 4.3 till september or so, or december
flex360 said:
i doubt we will see 4.3 till september or so, or december
Click to expand...
Click to collapse
Until we actually see 4.3 released at all, speculation is pretty useless one way or another. I was somewhat surprised it didn't turn up at I/O, but considering Google's continuing focus on severing out core platform elements from Android, that's not actually altogether surprising.
Waiting is getting a bit tedious. The only part I'm looking forward to is a new radio. The rest is just icing on the cake.
I'll just be glad when it is released so that we can use a wide variety of ROMS that are being used on the International HTC One such as Android Revolution and the AOSP ROMS
Sent from my HTCONE
What about 4.3 ?
everesee said:
What about 4.3 ?
Click to expand...
Click to collapse
lol
legendary1022 said:
I'll just be glad when it is released so that we can use a wide variety of ROMS that are being used on the International HTC One such as Android Revolution and the AOSP ROMS
Sent from my HTCONE
Click to expand...
Click to collapse
You know, all ARHD roms are really just stock with a fancy name.
Rirere said:
Until we actually see 4.3 released at all, speculation is pretty useless one way or another. I was somewhat surprised it didn't turn up at I/O, but considering Google's continuing focus on severing out core platform elements from Android, that's not actually altogether surprising.
Click to expand...
Click to collapse
Released at all? I see you are not aware that there's a 4.3 leak for the Google edition S4? That means that Google has made the source available to the OEMs before making it public. Maybe even in the hopes of faster updates. Either way, it looks like Samsung's trying to pull a fast one on HTC.
The reason 4.3 did not show up at the I/O is because it's a very minor upgrade from 4.2.2. If you run it yourself, as I have, you will practically not notice any changes from 4.2.2.
However, Google chose to make sure that KLP WAS at I/O.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
CNexus said:
Released at all? I see you are not aware that there's a 4.3 leak for the Google edition S4? That means that Google has made the source available to the OEMs before making it public. Maybe even in the hopes of faster updates. Either way, it looks like Samsung's trying to pull a fast one on HTC.
The reason 4.3 did not show up at the I/O is because it's a very minor upgrade from 4.2.2. If you run it yourself, as I have, you will practically not notice any changes from 4.2.2.
However, Google chose to make sure that KLP WAS at I/O.
Click to expand...
Click to collapse
Thanks for the assumption, but wrong on both counts. I've been aware of it since leak date and have run it on a spare device, and from what I've seen and read, I don't consider it to be complete. Just because something runs, as I'm sure you're aware, does not mean that it's either ready or close to release date.
Rirere said:
Thanks for the assumption, but wrong on both counts. I've been aware of it since leak date and have run it on a spare device, and from what I've seen and read, I don't consider it to be complete. Just because something runs, as I'm sure you're aware, does not mean that it's either ready or close to release date.
Click to expand...
Click to collapse
The point of 4.3 was to give carriers and OEMs a chance to catch up update-wise, it only makes sense that 4.3 will be a minor upgrade so that carriers and OEMs can easily patch it in. It's only natural that a an update meant to give a breather will contain minimal changes.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
CNexus said:
The point of 4.3 was to give carriers and OEMs a chance to catch up update-wise, it only makes sense that 4.3 will be a minor upgrade so that carriers and OEMs can easily patch it in. It's only natural that a an update meant to give a breather will contain minimal changes.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
Click to expand...
Click to collapse
And if you look back at my posts, I don't disagree with this-- and in fact, this was even the subject of my first post. I don't think it's an incomplete leak because the changes so far have been minimal-- it is possible to have an unfinished point update.
I've been reading alot about the Google Editions lately and where there updates come from, on this page it says that the updates are provided by Google:
http://blog.htc.com/2013/05/htc-one-google-nexus-experience/
But apparently the kernels are provided by HTC, what do you guys think and how long do you reckon HTC will take to come out with the updates if they do come from them due to there past history?
jwtrockz1998 said:
I've been reading alot about the Google Editions lately and where there updates come from, on this page it says that the updates are provided by Google:
http://blog.htc.com/2013/05/htc-one-google-nexus-experience/
But apparently the kernels are provided by HTC, what do you guys think and how long do you reckon HTC will take to come out with the updates if they do come from them due to there past history?
Click to expand...
Click to collapse
in retrospect, Google updates for Google Edition phones at provide by Google. But google is not responsible for distribution, HTC is.
HTC deal with the ROM as well as the GE HTC One uses an HTC kernel, not a Nexus kernel, so until the kernel is ready the ROM won't be released. We'll soon find out as there is a Google Announcement on the 24th so depending on how long after that it comes out will show how quickly HTC are making the kernel
Considering there's already been 4.3 leaks for the S4 GE, and 4.3 Spotted on the One GE - seems like the next update won't be a problem when it comes.
bbedward said:
Considering there's already been 4.3 leaks for the S4 GE, and 4.3 Spotted on the One GE - seems like the next update won't be a problem when it comes.
Click to expand...
Click to collapse
Yeah hopefully Google announce Android 4.3 and a new Nexus 7 2 tablet (been waiting for it all year lol) next Tuesday finger crossed
I know there was a system dump of 4.3 on t Mobile, but it was said to still be in development. Some people were thinking the moto x would get faster updates being so close to stock android. However at this point we're getting close to when the heavily customized galaxy s4 is *supposed* to get its update.
Could the major camera firmware update have delayed them on 4.3? Or are we looking at another phone that will still be several months delayed getting android updates?
From what I've seen there were 3? leaks of 4.3 engineering builds so far to date for the Moto X. In addition to the standard 4.3 features, they seem to also be updating Touchless Controls, Active Display and the Camera App. Now I saw that 4.3.1 is rolling out to the Nexus 7 LTE and I'm sure we will see it released to AOSP "soon" with a list of changes as well as 4.3.1 updates for the other Nexus devices.
What I think happened is Motorola was told that 4.3.1 would be rolling out "soon" so rather than keep working on fixing bugs in 4.3.0 that could be fixed in 4.3.1, Motorola tackled the main issues such as the camera, call quality, etc for the OTA and will resync their builds with AOSP so they can go straight to 4.3.1 for their OTA.
Now I could be totally wrong but given Motorola's previous update history, the Bionic for example went from Gingerbread straight to 4.0.4 and skipped 4.0.2 and 4.0.3, from there it went straight to 4.1.2 and skipped 4.1.1. I know Motorola is rebranding themselves right now but I guess they made a calculated decision to get the biggest issues fixed first, then release the big update which will take more testing.
I also think that because Samsung and HTC released Google Play Edition devices, they got earlier access to 4.3 than Motorola did so this would explain how they've had additional time to work on integrating their UI's into 4.3. I think Google is just playing it a bit too safe in trying to ensure no one thinks Motorola is getting prefered treatment over other companies.
dpw2atox said:
From what I've seen there were 3? leaks of 4.3 engineering builds so far to date for the Moto X. In addition to the standard 4.3 features, they seem to also be updating Touchless Controls, Active Display and the Camera App. Now I saw that 4.3.1 is rolling out to the Nexus 7 LTE and I'm sure we will see it released to AOSP "soon" with a list of changes as well as 4.3.1 updates for the other Nexus devices.
What I think happened is Motorola was told that 4.3.1 would be rolling out "soon" so rather than keep working on fixing bugs in 4.3.0 that could be fixed in 4.3.1, Motorola tackled the main issues such as the camera, call quality, etc for the OTA and will resync their builds with AOSP so they can go straight to 4.3.1 for their OTA.
Now I could be totally wrong but given Motorola's previous update history, the Bionic for example went from Gingerbread straight to 4.0.4 and skipped 4.0.2 and 4.0.3, from there it went straight to 4.1.2 and skipped 4.1.1. I know Motorola is rebranding themselves right now but I guess they made a calculated decision to get the biggest issues fixed first, then release the big update which will take more testing.
I also think that because Samsung and HTC released Google Play Edition devices, they got earlier access to 4.3 than Motorola did so this would explain how they've had additional time to work on integrating their UI's into 4.3. I think Google is just playing it a bit too safe in trying to ensure no one thinks Motorola is getting prefered treatment over other companies.
Click to expand...
Click to collapse
That was my other thought. Maybe have to wait longer but be better off with 4.3.1 over 4.3
Hopefully 4.4 is quick though!
mikeosu said:
That was my other thought. Maybe have to wait longer but be better off with 4.3.1 over 4.3
Hopefully 4.4 is quick though!
Click to expand...
Click to collapse
or it could be skipped over for 4.4, google does have more control over it now. I am getting my moto x tomorrow I can't wait.
Maybe the S4 having been released months in advance also has something to do with it....
Sent from my XT1053 using Tapatalk 2
enigmaco said:
or it could be skipped over for 4.4, google does have more control over it now. I am getting my moto x tomorrow I can't wait.
Click to expand...
Click to collapse
Very true. I would be ok with that if it meant an earlier update! I'm probably getting one soon with that best buy deal. Too good to pass up!
The biggest fix in 4.3 was the trim support (and SE Linux, but you won't notice that)... Moto X already has trim built in so there really isn't much rush on the 4.3 front.
I'd prefer a skip to 4.4 if that makes it a faster release.
Most newer HRMs require it and would like to know before buying one
newneonova said:
Most newer HRMs require it and would like to know before buying one
Click to expand...
Click to collapse
I could be mistaken, but I was under the impression that 4.3 brought that feature. But like I said, I could be wrong.
Yup your right
TriBeard said:
I could be mistaken, but I was under the impression that 4.3 brought that feature. But like I said, I could be wrong.
Click to expand...
Click to collapse
You are actually correct, that was one of the major features that android 4.3 brought. Google made a big deal out of it too lol. So yeah basically if you wanna guarantee a rom has BTLE support, than make sure it is based on 4.3 or in the near future 4.4 (hopefully )
If it's possible to get kitkat on our device with dalvik run time, please someone port it.
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
No it is not possible. Someone can't just port Kit Kat because there are a lack of drivers and binaries for it.
Apps will just have to get to the times and update to make it more optimized for Lollipop, or get "better" or more frequently updated apps to follow with the times.
zephiK said:
No it is not possible. Someone can't just port Kit Kat because there are a lack of drivers and binaries for it.
Apps will just have to get to the times and update to make it more optimized for Lollipop, or get "better" or more frequently updated apps to follow with the times.
Click to expand...
Click to collapse
That is actually quite a silly statement.
It actually would NOT be all that much work to build 4.4 for this hardware.
For one, all of the blobs needed can be pulled from Droid_turbo / Moto_maxx. They are basically the same hardware, and ship with 4.4.
Second, qualcomm supports the apq8084 platform on 4.4 directly. I have a liquid 8084 tablet with 4.4 on my desk right next to me right now.
Having said that... I'm not going to build 4.4, because it is pointless.
---------- Post added at 06:49 PM ---------- Previous post was at 06:38 PM ----------
dustin4vn said:
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
Click to expand...
Click to collapse
What exactly do you mean by "aren't optimized"??? As a developer, I have to say that this statement is completely meaningless. There is nothing special that need be done from a software developer point of view to take account for ART, as long as you aren't doing weird and unsupported hacks (which very very very few people actually do).
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
Click to expand...
Click to collapse
What do you mean by "stutters"? Is there heavy I/O happening when it is "stuttering"? Do you realize the serious impact that forced encryption has on the device's I/O and CPU performance? Do you realize that the display on N6 has nearly TWICE as many pixels as your "old" S5? That means that it is GOING to take a lot more to keep things fluid on N6 than S5. Something that will be helped when software starts to take advantage of the newer OpenGL available on 5.0. NONE of this will be improved by downgrading to 4.4. In fact, because 4.4 will NOT be taking advantage of the newer OpenGL, doing this downgrade will make certain, even after software starts to make use of it, that you WON'T be able to benefit from it.
doitright said:
That is actually quite a silly statement.
It actually would NOT be all that much work to build 4.4 for this hardware.
For one, all of the blobs needed can be pulled from Droid_turbo / Moto_maxx. They are basically the same hardware, and ship with 4.4.
Second, qualcomm supports the apq8084 platform on 4.4 directly. I have a liquid 8084 tablet with 4.4 on my desk right next to me right now
Click to expand...
Click to collapse
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
i would have chimed in a while ago, but for certain reasons i didnt. normally, id say that it wont happen, since there arent any binaries for kitkat and the nexus 6. but guess what, there are! they arent anywhere where the public has access to them, but they do exist. as google had kitkat on the n6 before lollipop. and a very few people have even gotten their n6 with kitkat(when they just selling the n6). so, in the future, we might be able to see a kitkat build on our n6
zephiK said:
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Click to expand...
Click to collapse
I'm not going to, because it is a waste of time and I have no interest in having a **** measuring contest with some random person on the internet.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Click to expand...
Click to collapse
That's hilarious. Especially since hardware wise, the only real difference between those phones I mentioned and Nexus 6 is the screen size. In fact, we know for a fact that those two devices very nearly WERE stamped "shamu" and sent out AS Nexus 6. Something happened between Google and Verizon that decided what size went under whose label. Also, you should see all the Sony blobs I used on my Samsung phone... also a bunch from LG.
But just to make things even more interesting, on what grounds do you claim that Android 4.4 won't run on blobs from 5.0? That same Samsung phone I referred to above running on Sony and LG blobs... is running 5.0 on such mishmash of blobs pulled out from 4.[0-4]. And perfectly happily at that. Blobs DO NOT HAVE an intrinsic "works with Android version X and nothing else" stamped on them.
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
Click to expand...
Click to collapse
THAT is essentially what I am saying. Not the "even if" (because it *IS* possible), or the dirty hack part, because though it may make you FEEL dirty to downgrade, it wouldn't actually be a hack. I'm saying that nobody WILL do it, because it is pointless and backwards.
dustin4vn said:
If it's possible to get kitkat on our device with dalvik run time, please someone port it.
I hate lollipop. why? almost all the apps on the play store aren't optimized for ART/lollipop.
It's just pain to see my new nexus 6 stutters on apps that can run on my old 5S smoothly
Click to expand...
Click to collapse
This phone would have been awesome on Kitkat. I also do not like Lollipop. It burns the eyes and there are too many bugs. I don't think anyone is going to go to the trouble though.
Evo_Shift said:
This phone would have been awesome on Kitkat. I also do not like Lollipop. It burns the eyes and there are too many bugs. I don't think anyone is going to go to the trouble though.
Click to expand...
Click to collapse
As far as bugs go, its no different than any previous version. They patched a bunch of bugs that were there before, and added a few new ones. I wonder though, what bugs you think you've spotted? List them, and tell me why you believe that they are bugs...
Just port android 1.5 cupcake and call it a day lol
md1008 said:
Just port android 1.5 cupcake and call it a day lol
Click to expand...
Click to collapse
haha, lol. Now that... might actually not be possible.
doitright said:
haha, lol. Now that... might actually not be possible.
Click to expand...
Click to collapse
Time to do a change petition from google to make official cupcake ROM lol
zephiK said:
If it's not that much work then why you don't do it and prove me wrong? You'd need proprietary vendors, drivers for 4.4 and not to mention you'd need a backward port of dalvik.
Just because they share similar hardware doesn't mean you can just pull blobs from another phone with similar hardware specifications from the same manufacturer then hope that it works because development doesn't work that way
Even if it was possible no one would do it because its a step backwards and it would be a dirty hack.
Click to expand...
Click to collapse
I am gonna go ahead and just attach it to your post. There is a port being worked on as I post this, yes there are people who want kit kat on the phone and there are other reasons than running cm, aosp or stock. Enough said and more will be revealed in the nexus 6 forums hopefully within the next week we will see how bad it really gets
fun..
to bad kitkat will not work on the n6 without drivers for kitkat. unless its a lollipop rom thats just themed like kitkat.
simms22 said:
fun..
to bad kitkat will not work on the n6 without drivers for kitkat. unless its a lollipop rom thats just themed like kitkat.
Click to expand...
Click to collapse
You may be right and I might be wasting time. Something to do though
jhr5474 said:
You may be right and I might be wasting time. Something to do though
Click to expand...
Click to collapse
i actually think you should keep trying, seriously. maybe it is possible to modify the lollipop drivers for kitkat, or modify the n5 drivers for kitkat for the n6. anyways, it woukd be neat to try kitkat on the n6
I thought the Nexus theory was to have the latest and greatest and never look back. Time would be better utilized squashing bugs in M.
prdog1 said:
I thought the Nexus theory was to have the latest and greatest and never look back. Time would be better utilized squashing bugs in M.
Click to expand...
Click to collapse
it is.. but we also cant forget about nostalgia D
my n5 died this week, after flashing m, seriously. andvi found my old sgs4 that hasnt been powered on in nearly 2 years, its running android 4.3
simms22 said:
it is.. but we also cant forget about nostalgia D
my n5 died this week, after flashing m, seriously. andvi found my old sgs4 that hasnt been powered on in nearly 2 years, its running android 4.3
Click to expand...
Click to collapse
My son got robbed of his S6 by knifepoint. Ran my S3 4.3 for a couple days. Verizon Samsung on ATT not a beautiful experience. Lol Ran an old HTC Inspire on 2.3 Ginger for a week or so. Sister gave him Note 3 so he back to Lolli now.
prdog1 said:
My son got robbed of his S6 by knifepoint. Ran my S3 4.3 for a couple days. Verizon Samsung on ATT not a beautiful experience. Lol Ran an old HTC Inspire on 2.3 Ginger for a week or so. Sister gave him Note 3 so he back to Lolli now.
Click to expand...
Click to collapse
i actually rooted it and flashed safeline recovery, first time ever! lol. i used kingsroot, a one click app to root. its a verizon phone, so i cant ever use it on a provider. but makes good calls over hangouts
simms22 said:
i actually rooted it and flashed safeline recovery, first time ever! lol. its a verizon phone, so i cant ever use it on a provider. but makes good calls over hangouts
Click to expand...
Click to collapse
Why can't use it on provider. He has used Verizon Rezound on TMO and S3 on ATT. Not perfect but they work. He bad about breaking **** and never buys insurance.