Related
hey just wondering if anybody would had the best thread to follow for cm 10 on the galaxy note
Sent from my GT-N7000 using xda premium
trea916 said:
hey just wondering if anybody would had the best thread to follow for cm 10 on the galaxy note
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Yeah seriously I don't know what's the mystery about it.. Already running cm10 on my gtab and gnexus I know they don't like people ask when their phone will get CMXX. but CM developers should try to communicate better with users... Open source, free work in this scale is not excuse for blindness
Enviado desde mi GT-N7000 usando Tapatalk 2
Maybe it's worth posting a note on the cm forum and getting as many of us to sign it, that's how we got cm9 in the first place. I'm pretty sure they're already working on it.
Sent from my GT-N7000 using xda premium
Track xplodwild's twitter account. Thats ur best bet.
Sent from my GT-N7000 using xda premium
Xplodwild does a great job on implementing the s3 cm10 previews. I tested the previews from the beginning. I have now migrated to N7000 and cannot wait for the First previews there.
Gesendet von meinem GT-N7000 mit Tapatalk 2
There will be long wait to have a fully working jellybean on the Note.
Mostly due to Samsung who delays Note updates for newbies critical bugs (ie brick bug) and also to sell the Note 2. Why users will buy Note 2 if they have a fully working ICS/Jellybean on the first one ?
Kernel/FW sources will be released in a long time.
Concerning CM10, hope they will not face issues like working camera etc.
As an example, CM9 & Aokp/Aosp are ready for months on galaxy tab but still missing functionnalities & working camera which make them useless. Cause of no sources available for devs.
Sent from my GT-N7000 using xda premium
Phenryth said:
There will be long wait to have a fully working jellybean on the Note.
Mostly due to Samsung who delays Note updates for newbies critical bugs (ie brick bug) and also to sell the Note 2. Why users will buy Note 2 if they have a fully working ICS/Jellybean on the first one ?
Kernel/FW sources will be released in a long time.
Concerning CM10, hope they will not face issues like working camera etc.
As an example, CM9 & Aokp/Aosp are ready for months on galaxy tab but still missing functionnalities & working camera which make them useless. Cause of no sources available for devs.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Cm9 works with 4.0.4 way before samsung releases 4.0.4.. Drivers compatibility its for 4.X.X that's well known.. And cm team several weeks ago (since jb source droped into aosp) started the merge with ics and they said it was a piece of cake since the drivers from ics are the same... We don't need samsung sources to get JB.. Cm can deliver a jb rom with what they already have..
And in the case of gtab 10.1 we don't have working camera because our kernel developer Wich also is the cm9/10 maintainer for tab ported all the drivers from honey comb Wich were a slightly improvement over ginger bread drivers.. That's why we don't have a working camera yet.. But hey everything else works. Hwa/gps/sound/wifi/3G and cm10 its running on the tablet buttery smooth with the lack of camera.. And those are drivers from honey comb..
So tell me what's wrong with cm10 for note when they have every single driver for ics available... Makes no sense to me... Most of the popular phones/tabs cm supports in cm9 already have a cm10 preview
Difference here its that our cm developer I'm gtab is an angel.. What a nice guy he baby every single person that uses cm9 and or his kernels... He takes care of every single case one by one and he didn't move to merging jb until the last of us solved his personal issue...
Pershoot (our cm developer for tab) is not thinking he's a all mighty god untouchable its what he says and everyone else is bull$hit its an attitude problem here
Enviado desde mi GT-N7000 usando Tapatalk 2
trea916 said:
hey just wondering if anybody would had the best thread to follow for cm 10 on the galaxy note
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
the cm9 thread for now ....a new thread will be started when the cm crew are happy they can release it and not have a bunch of people going arhh why this dont work why that not work...as umbelievable as it might seem there is a lot of time consuming work and fixes that go into making your new rom..PATIENCE is a vertue ,,whinging is just plain annoying
@denny said:
the cm9 thread for now ....a new thread will be started when the cm crew are happy they can release it and not have a bunch of people going arhh why this dont work why that not work...as umbelievable as it might seem there is a lot of time consuming work and fixes that go into making your new rom..PATIENCE is a vertue ,,whinging is just plain annoying
Click to expand...
Click to collapse
This its not true something like this works
ATTENTION: THIS IS JUST A PREVIEW. MAY CONTAIN A LOT OF BUGS!
NO SUPPORT!!!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (JB), which is designed to increase performance and reliability over stock Android for your device.
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
First time installing CyanogenMod 10 to your Galaxy S II, or coming from another ROM:
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10 ZIPs to your internal SDCard
- Boot into Recovery
- Flash CM10 zip from internal SDCard
- Flash GApps zip from internal SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore Apps using Titanium Backup!
Upgrading from earlier version of CyanogenMod 10:
- Copy CM10 ZIP to your internal SDCard
- Boot into Recovery
- Flash CM10 zip from internal SDCard
- Reboot
Experimental builds:
20120725: Download (md5)
20120725 (Mirror): Download (md5)
Google Apps:
Get the latest Version from Rom-Manager.
Newer, unsupported versions can be found at http://goo.im/gapps
CWM flashable Modems:
LPX Modem: Download
LPW Modem: Download
LPS Modem: Download
LPR Modem: Download
Have a look at ROM-Manager (Developer: codeworkx) for more Modems.
Webchat: http://webchat.freenode.net/?channels=teamhacksung-support
Server: chat.freenode.net
Channel: #teamhacksung-support
Don't expect any support if you:
- are not running stock cm-kernel
- have installed any mods
- have modified system files
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't meant Out-of-Respect!!!
http://forum.xda-developers.com/showthread.php?p=29280368
If you want to donate a few bucks for the work we're doing in our freetime, goto teamhacksung website and hit the big donate button.
Thanks to all donators!
Enviado desde mi GT-N7000 usando Tapatalk 2
msedek said:
Cm9 works with 4.0.4 way before samsung releases 4.0.4.. Drivers compatibility its for 4.X.X that's well known.. And cm team several weeks ago (since jb source droped into aosp) started the merge with ics and they said it was a piece of cake since the drivers from ics are the same... We don't need samsung sources to get JB.. Cm can deliver a jb rom with what they already have..
And in the case of gtab 10.1 we don't have working camera because our kernel developer Wich also is the cm9/10 maintainer for tab ported all the drivers from honey comb Wich were a slightly improvement over ginger bread drivers.. That's why we don't have a working camera yet.. But hey everything else works. Hwa/gps/sound/wifi/3G and cm10 its running on the tablet buttery smooth with the lack of camera.. And those are drivers from honey comb..
So tell me what's wrong with cm10 for note when they have every single driver for ics available... Makes no sense to me... Most of the popular phones/tabs cm supports in cm9 already have a cm10 preview
Difference here its that our cm developer I'm gtab is an angel.. What a nice guy he baby every single person that uses cm9 and or his kernels... He takes care of every single case one by one and he didn't move to merging jb until the last of us solved his personal issue...
Pershoot (our cm developer for tab) is not thinking he's a all mighty god untouchable its what he says and everyone else is bull$hit its an attitude problem here
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
You just did not understand what i've written.
I am hoping that CM teams won't face these issues like camera even if they should not be concerned.
I am certainly not speaking about their awesome work but about the fact that if issues raise with CM10...it can be hard to fix since Samsung are not going to release the eventual sources needed before months.
Nevertheless, i am running CM9 and I love it. But there are still missing stock functionnalities. It is for users to know if they can live without them or not. Some absolutely need S-suite...other the Mhl...and for me, working camera especially for skype is a must have. That is why I have to run that **** of samsung stock over my gtab 8.9.
I am angry towards Samsung...not towards the different developers teams who litterally save us.
As an example, they fix the emmc brick while Samsung did not do it yet and force most of Note users to remain at Gingerbread..which just innacceptable for the ones who's getting the most money between manufacturers.
I also have the Xperia S...comparing Gb/ICS to samsung stock is just day and night. At the end...comparing to any devices I had/have..Samsung provides the best innovations and hardware but the worst system.
Sent from my GT-N7000 using xda premium
Phenryth said:
You just did not understand what i've written.
I am hoping that CM teams won't face these issues like camera even if they should not be concerned.
I am certainly not speaking about their awesome work but about the fact that if issues raise with CM10...it can be hard to fix since Samsung are not going to release the eventual sources needed before months.
Nevertheless, i am running CM9 and I love it. But there are still missing stock functionnalities. It is for users to know if they can live without them or not. Some absolutely need S-suite...other the Mhl...and for me, working camera especially for skype is a must have. That is why I have to run that **** of samsung stock over my gtab 8.9.
I am angry towards Samsung...not towards the different developers teams who litterally save us.
As an example, they fix the emmc brick while Samsung did not do it yet and force most of Note users to remain at Gingerbread..which just innacceptable for the ones who's getting the most money between manufacturers.
I also have the Xperia S...comparing Gb/ICS to samsung stock is just day and night. At the end...comparing to any devices I had/have..Samsung provides the best innovations and hardware but the worst system.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have cm10 in all my devices but gnote and I completely love it.. What I don't get its the cm developers attitude here.. Handling people like they are gods and not giving a small preview or a single word about the jb rom
Enviado desde mi GT-N7000 usando Tapatalk 2
Originally Posted by msedek View Post
Cm9 works with 4.0.4 way before samsung releases 4.0.4.. Drivers compatibility its for 4.X.X that's well known.. And cm team several weeks ago (since jb source droped into aosp) started the merge with ics and they said it was a piece of cake since the drivers from ics are the same... We don't need samsung sources to get JB.. Cm can deliver a jb rom with what they already have..
:good: totally agreed with that.
it's depending to Samsung. their to busy making big money instead of customers who facing problem with their own product. working too slow to solve their own problem and not appreciates value customers.
and yes ! i'm totally agreed with you, here Devs making a lots of improvement and modifications just to ensure satisfaction to enjoyed what we all paid of.
lets be patient. Xplodwild will start a new discussion thread once he releases it in the general section here
Phenryth said:
There will be long wait to have a fully working jellybean on the Note.
Click to expand...
Click to collapse
Like a few hours?
(if you don't mind project butter not fully working)
XpLoDWilD said:
Like a few hours?
(if you don't mind project butter not fully working)
Click to expand...
Click to collapse
Nuff said
Enviado desde mi GT-N7000 usando Tapatalk 2
XpLoDWilD said:
Like a few hours?
(if you don't mind project butter not fully working)
Click to expand...
Click to collapse
Love you, man!
Sent from my GT-N7000 using xda premium
XpLoDWilD said:
Like a few hours?
(if you don't mind project butter not fully working)
Click to expand...
Click to collapse
Here's come the legend! RESPECT!
Seriously, we can't wait to test JB in Galaxy Note!
I'll wait for the Butter.
Yeah, we got lucky. Unlike GB audio blobs in ICS, ICS audio blobs worked with a backwards-compatibility wrapper in JB.
I don't think anyone was expecting it to work but it did. I would've started working on the Note tree last night, but I got home late and am away from home almost all day today. xplod will probably have a tree up before I get home, he cheats by being 6 hours ahead of me in timezones!
Due to certain limitations of our graphics blobs, the majority of "butter" will not be present.
Entropy512 said:
Yeah, we got lucky. Unlike GB audio blobs in ICS, ICS audio blobs worked with a backwards-compatibility wrapper in JB.
I don't think anyone was expecting it to work but it did. I would've started working on the Note tree last night, but I got home late and am away from home almost all day today. xplod will probably have a tree up before I get home, he cheats by being 6 hours ahead of me in timezones!
Due to certain limitations of our graphics blobs, the majority of "butter" will not be present.
Click to expand...
Click to collapse
Out of curiosity, would the limitations be fixable, given time? Or is it just not-fixable and our Notes would forever be dry and crusty, without any butter?
Great news sony is just like xperia s working on aosp project
http://developer.sonymobile.com/201...r-xperia-z-on-sonys-github-open-source-video/
This would definitely help us!
Yep. Some of the devs doing apps and kernels for the device would probably be helped even more than us, and if they send fixes to the repo Sony could be helped as well.
Open source. It works, *****es!
Hey guys, as you have some knowledge that I don't, can someone explain me something...
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
I really do not understand the difference between these two projects.
As I understand it, CM usually uses proprietary blobs (binaries) extracted from the device they are building for, rather than open source alternatives coded by the community.
AOSP aims to use all open source code.
Someone correct me if I'm wrong
Sent from my C6603 using Tapatalk 2
Hi Entropy, could you help answer a question that was brought up in another thread while were on this AOSP topic. I'm curious to your thoughts on this.
profete162 said:
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Entropy, while were on this topic,could you enlighten us for this question that was brought up in another thread.
profete162 said:
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2
Perfectly clear and nice answer, thanks.
Tom Fagerland said:
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Click to expand...
Click to collapse
profete162 said:
Hey guys, as you have some knowledge that I don't, can someone explain me something...
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
I really do not understand the difference between these two projects.
Click to expand...
Click to collapse
In some cases, our handling of blobs is a pretty serious grey area. That is, for example, why our official build instructions use the extract-files approach. Also, why our blob repos used for builds are maintained separately from our main source repos.
That reminds me, I need to look through the manuals/stock software for my device to see what sorts of legal terminology there is - e.g. what is actually said about the blobs in about->legal.
In some cases (such as modem and camera), the OEM has weirdo restrictions in terms of permission to release binaries. Qualcomm has some especially arcane rules for some items (mostly modem-related).
Also, in the case of AOSP master, blobs must be compatible with the current codebase - as a result, some of our backwards-compatibility hacks to work with released blobs aren't valid for "official upstream" AOSP.
If I am not completely stupid and understood previous post, can we summarize like this:
1) "drivers" for camera and modem are proprietary compiled files on the device that nobody can edit
2) Sony has the right to include these files on a Sony Rom (I guess they paid for these files?)
3) Sony cannot include these files on other Rom than the one shipped with the device, like an AOSP ROM. (even as a separate package?)
4) Cyanogen include these files on CMxx but (is? // is not?) allowed to
Is that right?
does AOSP mean turning the Z into a nexus phone basically? Sorry I am still new to the Android thing. What does this mean for update? Do we get it as soon as Google release a new one?
Gitaroo said:
does AOSP mean turning the Z into a nexus phone basically? Sorry I am still new to the Android thing. What does this mean for update? Do we get it as soon as Google release a new one?
Click to expand...
Click to collapse
Will still require time to adapt it. But it'easier for the community devs and chances to get it are much higher than on other phones.
Sent Form my CM powered Sony Xperia Z.
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
babylonbwoy said:
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
Click to expand...
Click to collapse
All Snapdragon S3 (Scorpion) devices are in the same boat there. Samsung Scorpions just saw 4.1 only in the last week or so.
I hope they can retain Bravia engine!
I'm dowloading the source code now, let's see what I can do
Sent from my C6603 using xda app-developers app
Tom Fagerland said:
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers
then what are these binaries for Nexus devices?
Do devs use those closed-source binaries for building AOSP for nexus devices? (and difference is that Google obtained permissions from everyone to release the binaries?
I was about to create a thread to share the news hehe
http://developer.sonymobile.com/201...or-xperia-z-on-sonys-github-open-source-video
I hope by doing this xperia z will turn to a nexus phone *grins*
babylonbwoy said:
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
Click to expand...
Click to collapse
wouldnt Z be different. The S didnt have on screen navi keys and on top of that it was using a snapd 3 chip with 1gb of ram. Touch up was clearly needed for the S, however...
The Z is nearly the same as a Nexus 4 in nearly every way.
paperWastage said:
https://developers.google.com/android/nexus/drivers
then what are these binaries for Nexus devices?
Do devs use those closed-source binaries for building AOSP for nexus devices? (and difference is that Google obtained permissions from everyone to release the binaries?
Click to expand...
Click to collapse
Read my post again.
Hey all
Does anyone know if MIUI is going to release a version for the GS4?
CM already told they will NOT be adding any roms for the GS4, so MIUI is my last hope..
Maybe someone made an unofficial release of MIUI-Like rom?
Thanks
This is where owning the I9505 instead of the I9500 becomes a big advantage for people who like non-stock bulds like MIUI, CM and AOKP. Because, unlike Exynos, it's based upon an open-source architecture, it doesn't take much to convert builds to it from other devices. This is shown by the fact there is already a working CM10.1 build for it, created by someone who doesn't even own the phone.
As for the I9500, I'm sure someone will take the challenge up that the official CM team are passing up on. It will just take longer to appear and won't run as well. I don't know the score with MIUI and whether they will bother, time will tell.
But didn't I hear that the official CM team might be having a change of heart? It was back in March when they first said they would pass up on the GS4.
EDIT -- https://www.facebook.com/miuiromchina saying they won't support it for now. Not sure if that will change or if someone else will take it upon themselves to overcome the challenge of developing it for a closed source chipset.
Pagnell said:
This is where owning the I9505 instead of the I9500 becomes a big advantage for people who like non-stock bulds like MIUI, CM and AOKP. Because, unlike Exynos, it's based upon an open-source architecture, it doesn't take much to convert builds to it from other devices. This is shown by the fact there is already a working CM10.1 build for it, created by someone who doesn't even own the phone.
As for the I9500, I'm sure someone will take the challenge up that the official CM team are passing up on. It will just take longer to appear and won't run as well. I don't know the score with MIUI and whether they will bother, time will tell.
But didn't I hear that the official CM team might be having a change of heart? It was back in March when they first said they would pass up on the GS4.
EDIT -- https://www.facebook.com/miuiromchina saying they won't support it for now. Not sure if that will change or if someone else will take it upon themselves to overcome the challenge of developing it for a closed source chipset.
Click to expand...
Click to collapse
Codeworkx and Faryaab are working on the i9500.
I thought I read about a change of heart, like I said. Surprised about Coderworkx though, all the signs were that he had given up on Samsung for good. Have you got a link with confirmation that he is working on the S4? And with the I9505 being the official North American device I'm sure an official build of that will arrive soon enough.
The Samsung devices I currently own (i9100, i9100g, i9300, i9305, t0lte, p5100) are the last ones i will officially support. Some of them might be dropped with the next big android release. Yes, i’ll NOT touch the Galaxy S 4 and whatever comes after it.
Click to expand...
Click to collapse
http://codeworkx.de/wordpress/category/cyanogenmod/
Strong words to go back on but good news nonetheless.
Yes, things doesn't look too good for the i9500
Will Faryaab save my day? who is he?
Pagnell said:
I thought I read about a change of heart, like I said. Surprised about Coderworkx though, all the signs were that he had given up on Samsung for good. Have you got a link with confirmation that he is working on the S4? And with the I9505 being the official North American device I'm sure an official build of that will arrive soon enough.
http://codeworkx.de/wordpress/category/cyanogenmod/
Strong words to go back on but good news nonetheless.
Click to expand...
Click to collapse
https://github.com/CyanogenMod/android_device_samsung_i9500
So there's a chance after all :angel:
It's no longer only for Nexus 4!
http://www.jollausers.com/2014/04/wip-sailfish-os-running-on-google-nexus-5/
Waw...tq
Sent from my GT-I9500 using XDA Premium 4 mobile app
Im waiting so hard... cannot wait anymore i love SailFish design.
Development is getting there, WLAN and Audio is working now, in time, we'll see a ROM.
I'm really exited about this os... hope that jolla releases soon the rom.
-Fabione- said:
I'm really exited about this os... hope that jolla releases soon the rom.
Click to expand...
Click to collapse
The source code has been available on github, from the following link , this has been available for some time, but I lack the knowledge, and time to build the ROM, and kernel.
The kernel is a modified CM11 kernel, and the kickstarter file from the repository should setup the rom with all the repo dependencies (including the actual sailfish os part) that it relies on to work, providing I correctly understand what a kickstarter file does.
DinoSoup said:
It's no longer only for Nexus 4!
http://www.jollausers.com/2014/04/wip-sailfish-os-running-on-google-nexus-5/
Click to expand...
Click to collapse
Is it possible to port it to galaxy s4 i9500?
If yes, can some port it? or can someone teach me how to port? or is there any tutorial for porting it?
This looks Promising ...
I want that ^^ can't weit till we can get a shot at it
yeah, I hope we will get some news soon, I'd fancy a nexus 5 sailfish-rom most of course
Anyhow, it seems the nexus 5 wasn't that of a good choice imo. Sure, it has good specs for that low price, but owning a Nexus S before I thought the N5 is a good choice also towards support for new roms (like the Nexus S was: you always got new / experimental roms for it first). Now the N5 seems to have bad hardware in the way that it is hard to implement in new roms (e.g. find suitable driver) which is a shame. Well, I'm not sure if I'd buy another Nexus phone again, thankfully there are many alternatives now (the fairphone, jolla phones etc).
Umm.. Guys? The rom has been out for over a month already.
http://forum.xda-developers.com/showpost.php?p=53018643&postcount=60
How long will android L take for the Galaxy S4 (Unlocked i9505)?
Forever I guess
Sent from my GT-I9505 using Tapatalk
If you're willing to install a GPE based ROM on your device, then it should be possible to get ~2 weeks after source release (some sites suggest a 1st of November release for the sources). As for a normal OTA, there are hopes for December. Though, based on Samsung's previous history, somewhere in 2015 might be more likely.
Takenoko_ said:
If you're willing to install a GPE based ROM on your device, then it should be possible to get ~2 weeks after source release (some sites suggest a 1st of November release for the sources). As for a normal OTA, there are hopes for December. Though, based on Samsung's previous history, somewhere in 2015 might be more likely.
Click to expand...
Click to collapse
Yeah, there is one right now but its not very stable (wifi not working, USB MTP broke , etc). Either way im guessing early 2015 for samsung to catch up like usual.
lohacks4pone said:
Yeah, there is one right now but its not very stable (wifi not working, USB MTP broke , etc). Either way im guessing early 2015 for samsung to catch up like usual.
Click to expand...
Click to collapse
That's a ported version of the developer release for the Nexus 5 though. The Google Play Edition ROMs come from the I9505G, and are officially released by Samsung for the device, usually only a few weeks after the latest Android sources are available, as they come without TouchWiz. These also work on the normal I9505, which makes it possible to get hold of a fully working build with support for original accessories fairly quickly
That said, if one would want the TouchWiz experience from Samsung (or simply prefer not to install custom ROMs ), there's sadly no choice but to wait indeed.