My question. At what point will I no longer be able to use the latest and greatest Android version? IE windows 7 isn't going to run on a windows 95 machine. When will my Vibrant be the windows 95 machine? From 95 to 7 might be to much a jump but you get my point.
Its already clear that this time is soon. With all this near field stuff that if I'm correct my vibrant can't do. And of course I only have one camera so all this video phone stuff isn't going to happen....
I also have read that google is going to slow down its releases. Will I be installing Android 2.5?
Just a question I dreamed up falling asleep last night, interesting to think about. I dread the day!
Thanks for all the work! Running Obsidian 4.2, I freaking love my phone. really. Its AWESOME. Came from a jailbroken, unlocked iPos 3g and omg did I hate it.
Thanks again.
Nick
Why isn't this in q&a? Anyways gingerbread requires a 1ghz processor. So you are good for that. As for further releases let me dust off my time machine. Considering the nexus s is virtually identical in specs to the vibrant aside from the ffc, I think we may be able to support past 2.3 but don't know.
Sent from my SGH-T959 using XDA App
NJDubois said:
My question. At what point will I no longer be able to use the latest and greatest Android version? IE windows 7 isn't going to run on a windows 95 machine. When will my Vibrant be the windows 95 machine? From 95 to 7 might be to much a jump but you get my point.
Its already clear that this time is soon. With all this near field stuff that if I'm correct my vibrant can't do. And of course I only have one camera so all this video phone stuff isn't going to happen....
I also have read that google is going to slow down its releases. Will I be installing Android 2.5?
Just a question I dreamed up falling asleep last night, interesting to think about. I dread the day!
Thanks for all the work! Running Obsidian 4.2, I freaking love my phone. really. Its AWESOME. Came from a jailbroken, unlocked iPos 3g and omg did I hate it.
Thanks again.
Nick
Click to expand...
Click to collapse
You need to do some more research to get a better idea what Nexus S is and what the NFC chip does. This topic belongs in general for starters. Realistically there is no one who is going to have an exact answer although chances of you owning a new phone by the time your Vibrant stops getting updates is pretty high.
I'm sure we'll be able to get past 2.3 there's so many nods these days, that I'm sure we will be fine.
Sent from the speed demon
My doubt in particular - especially towards the NFC Chip and Gyro Sensors.
Jibreil said:
My doubt in particular - especially towards the NFC Chip and Gyro Sensors.
Click to expand...
Click to collapse
Why? These are hardware and driver related. What is the issue removing the drivers? Like the FFC mod just needed the drivers and implementation into the Rom. Or are you referring to what these do and Vibrant being outdated?
Thread moved to Q&A.
The issue we will meet first is not whether our hardware is up to the task, but whether we have a kernel. The original Nexus One is actually slated to get Android 2.3 before the Nexus S launch date and both the Nexus phones will go well beyond Android 3.0 because there will always be kernel source code available. Contrast that with the Vibrant where we have to rely on Samsung's good will to release a kernel. We'll probably get one for 2.3 (albeit several months if not a year from now) but I would not be surprised if 3.0 is out of the question. Once Samsung stops releasing kernels, it will be entirely in the hands of developers who will be working without source code.
Have those "previously suggested but also previously confirmed to be innacurate spec requirement rumors" now NOW official? If that makes sense. .. (?)
wildklymr said:
Why isn't this in q&a? Anyways gingerbread requires a 1ghz processor. So you are good for that. As for further releases let me dust off my time machine. Considering the nexus s is virtually identical in specs to the vibrant aside from the ffc, I think we may be able to support past 2.3 but don't know.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
SWYPED from my SUPASONIC
Have no fear. As near as I can tell, the Nexus S is basically the same hardware as the Vibrant + FFC. Eugene tweeted that he plans to port 2.3 over to the Vibrant once the Nexus S source is released. If he can get it to work, I see no reason our vibrant's will not be able to be updated anytime the Nexus S is for the foreseeable future.
And its not necessarily Samsung that's causing the update issue. T-Mobile is pretty dang slow when it comes to releasing updates. I'm sure, if the Nexus S is supposed to be next in the line of Google dev phones, that Google has some kind of contract with Samsung about developing drivers for any new version of Android that gets released.
My G1 is running the latest and greatest.
There is NOT a minimum processor speed.
Our phones have incredible hardware.
Have no worries about the future.
does our sga is capeble of getting the android 4.0 ice cream sadwich update or we have to be happy with gingerbred only???????????
Just wait for cm8.
We'd be the last family of devices to get ICS TBH if ever
I believe it has the chance of getting ICS but definetly not from Samsung. SGA has a very large amount of users and skillful developers who could make it happen.
We may have to be patient though.. Even Nexus S, which has the official support from Google, hasn't even recieved the upgrade yet. CMIIW.
rhadrio said:
I believe it has the chance of getting ICS but definetly not from Samsung. SGA has a very large amount of users and skillful developers who could make it happen.
We may have to be patient though.. Even Nexus S, which has the official support from Google, hasn't even recieved the upgrade yet. CMIIW.
Click to expand...
Click to collapse
They won't be pushing ICS to Nexus S when Prime hasn't even been out and ICS unveiled in Hong Kong on Wednesday.
russ18uk said:
They won't be pushing ICS to Nexus S when Prime hasn't even been out and ICS unveiled in Hong Kong on Wednesday.
Click to expand...
Click to collapse
Yeah.. Lame old marketing tactics lol.
By the way, I've seen some leaked videos of Prime and S running ICS and from there I could understand that even S wont have the exact same version of ICS the Prime will have... Well at least for the GUI.
Have a look at this.
russ18uk said:
We'd be the last family of devices to get ICS TBH if ever
Click to expand...
Click to collapse
couldnt agree more
If I had to choose I'd rather have a completely stable and optimized Gingerbread instead of an ICS. Stable meaning every feature working the way it should, like my wifi actually reconnecting after sleep.
The main advantages on ICS are:
1) dual core support and hardware accelerating
2) New UI.
Because neither of those are relevant to Galaxy Ace, I'm fine with Gingerbread.
But XDA developers are really fast and they will port ICS even if Samsung wouldn't.
but i have heard taht the update will be for 1 yr old devices i think galaxy ace is 1 yr old only...so we can get
himzz0007 said:
but i have heard taht the update will be for 1 yr old devices i think galaxy ace is 1 yr old only...so we can get
Click to expand...
Click to collapse
Yeah maybe for some high-end devices that is..
And really, I wouldnt expect much from Samsung in the term of firmware updates.
Maybe we could just put our hope on a new ICS-based CM instead
google announced that it will be available for the first 18 months for existing phones...
Sent from my GT-S5830 using xda premium
im hoping it would come to our devices.
Yup there's a new agreement for companies to provide software updates till the 1 year or so is up. We're probably getting it but of course they will prioritize.
New version of OS is one of marketing tricks to lure people into buying new phones, I'm quite sure that we won't see ICS stock from Samsung, but nevermind, we have great developers, so just wait for CM 8 an' see
Evgenik777 said:
New version of OS is one of marketing tricks to lure people into buying new phones, I'm quite sure that we won't see ICS stock from Samsung, but nevermind, we have great developers, so just wait for CM 8 an' see
Click to expand...
Click to collapse
It'd really be pointless though. ICS is a much more optimised version of HC which should bring full SMP support through software, something that has gone begging for quite a while to take advantage of phones like the S2. Maybe they are adding GPU rendering as well. Another useless perk for the Ace as the GPU is ****.
Also, why bother porting ICS to ARMv6? It's a complete waste of resources when it's almost likely to provide little to no benefit.
My opinion at least. Don't get your hopes up for ICS/ICS-based CM8.
I know (SGA even don't have flash) but at least they'll take some interface tweaks and eyecandies
Evgenik777 said:
I know (SGA even don't have flash) but at least they'll take some interface tweaks and eyecandies
Click to expand...
Click to collapse
Best we may see is a theme.
And what about some battery improvements in ICS? Maybe the phone won 't go faster but battery life could be higher. Or am i wrong?
Don't sound so negative guys, IV seen some old android phones running a ported gingerbread so anything is possible, never underestimate what the power of coding and patience can do
Sent from my GT-S5830 using XDA App
Seeing how this is a nexus device, there should be proper source release right? But this is Samsung, who have in the past proved to be one of the worst offenders in terms of releasing source. I originally had the note 10.1 but returned due to the terribly laggy software and insanely bad build quality. I'm unwilling to buy another device that lacks developer support, especially from Samsung.
mysystem said:
Seeing how this is a nexus device, there should be proper source release right? But this is Samsung, who have in the past proved to be one of the worst offenders in terms of releasing source. I originally had the note 10.1 but returned due to the terribly laggy software and insanely bad build quality. I'm unwilling to buy another device that lacks developer support, especially from Samsung.
Click to expand...
Click to collapse
Forget who makes it, a Nexus runs Googles software and will get direct updates from them. No kies, no waiting
My old n7 got the 4.1.2 update ** the day ** it was released worldwide.
Sent from my GT-I9300 using xda premium
Kernel source is already available at https://android.googlesource.com/kernel/exynos/ . It's going to run Linux 3.4 and the codename is manta.
ben1066 said:
Kernel source is already available at https://android.googlesource.com/kernel/exynos/ . It's going to run Linux 3.4 and the codename is manta.
Click to expand...
Click to collapse
Kernel is not enough! Samsung has to release the kernel because the law says so.
I'm with the OP. I have the SGS3 and things look pretty bad with the sources problem.
Even if stock is great many of us like to experience other possibilities, and CM on a tablet would be so sweet.
So yeah. I'm very very very worried about this issue on the nexus 10. My guess is we won't have the sources. Samsung won't release them.
Didn't they release them for the Nexus S? I don't count the Galaxy Nexus since that was a TI/PowerVR SoC.
This is actually a big moment for Samsung. They've got their Exynos processor and drivers on the Google update list which should mean it'll be faster to update all their other devices (at least from what I've read concerning Exynos drivers).
Am I missing something here? The updates come from Google, so the sources will be in the Android source tree.
alias_neo said:
Am I missing something here? The updates come from Google, so the sources will be in the Android source tree.
Click to expand...
Click to collapse
This.
All Nexus devices should have source for building the ROM and kernel posted online by Google for people to build from
EniGmA1987 said:
This.
All Nexus devices should have source for building the ROM and kernel posted online by Google for people to build from
Click to expand...
Click to collapse
Is that not what I just said? They're in the source tree. If they're not public at the moment, they should be soon after the device is released, just as they have been for all past nexus devices.
The fact that Samsung built the hardware here is irrelevant.
alias_neo said:
Is that not what I just said? They're in the source tree. If they're not public at the moment, they should be soon after the device is released, just as they have been for all past nexus devices.
The fact that Samsung built the hardware here is irrelevant.
Click to expand...
Click to collapse
he actually agree with you, not the opposite
Hi! This is my first post on XDA.
As a user of CM for more than a year ago on my i9300, and after enduring a lot of bugs, I wonder: What happens to CM?
It's a known fact that the Exynos platform is a headache for developers because there is no documentation or open sources from Samsung. So, things like the camera, the sound system, the HDMI output and the GPU do not work as they should.
However, here are many good developers who have fixed these bugs, or at least improve them a bit. And most of these fixes are open source and accessible by everyone on Github.
So, what is waiting CM to implement them? Giving credit to their authors, obviously.
CyanogenMod announces itself as an alternative to the stock firmware that lets you take full advantage of your smartphone, making it better and more stable. Now they are also a company: Cyanogen Inc. As a reputable brand, it should offer a higher quality firmware. ROMs like Nameless (I'm using it right now) works better even being "not official".
This is just an opinion as a user. I'm not criticizing or forcing anyone to do anything. But if there are hundreds of people using a ROM with bugs that were fixed, why not implement them? I would be the first to help, but my skills are just about webdev.
Respect and thanks for i9300 developers on XDA, and sorry about my bad English. When I use my native language I express myself MUCH better. Trust me. lol
Thanks for reading.
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
Thanks for answering my topic. The opinion of a developer like you is very appreciated.
This situation only seems to give more reasons for not buy a Samsung phone again. This lack of support from the manufacturer is a disrespect to the user's investment. And fragmentation strikes again. Sad but true.
Thanks again for your great work of keeping this device alive for all of us.
StephenJSweeney said:
That's a real shame the device is in such a mess.
Actually, to be fair, using Omnirom 4.4.4, I'm finding that the only thing that doesn't work properly is the notification led (no one seems to know why it only works 3 times out of 4).
I'll probably end up buying a new phone next year, anyway, since buy this time next year the i9300 will be almost 4 years old. In smartphone terms, that means it's getting along a bit.
(oh, and thanks for all your work on it, JustArchi!)
Click to expand...
Click to collapse
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
ouch01 said:
I tried OmniROM few months ago, but it had some annoying bugs (like camera crashes) and I missed some customizations of CyanogenMod. Anyway, I'll try it again. My next buy might be a Motorola phone. The AOSP support is priceless.
Click to expand...
Click to collapse
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
JustArchi said:
There's no i9300 maintainer, and they accept pull requests (on gerrit) when somebody sends them.
Also, the fact that there's no i9300 maintainer is directly connected with what you already said - lack of proper documentation. Nobody wants to fix the mess that has been created since whole this time. The amount of hacks required to make AOSP work on i9300 is too damn high. I'm slowly fixing this mess, making i9300 a bit better supported, but it's still a long way until it's done. Take a look at ArchiKernel for example, why I had to create my own kernel? Because smdk4412 sources were so much outdated that they finished around update7, right after sudden death fix. XXELLA, 4.1.2 Android times, hello. So first thing was to cleanup the kernel mess, use up-to-date samsung sources (used for stocks) and make them work with AOSP. Now, if I commit my work to CM, they'll deny this instantly because new kernel supports only i9300 and this commit would break all other exynos4 variants from compiling. Yes, together we COULD fix it, make it work with other devices. But I have better things to do than trying to fix whole exynos4 family, I focus on i9300.
This is one of the reasons why we won't see any official cm12 nightly for i9300. Because nobody is going to maintain that. Even if we can fix something, nobody is going to commit that, unless we put serious effort for making it universal across all supported devices.
Click to expand...
Click to collapse
i feel you
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
StephenJSweeney said:
I had the camera crash on CM11 M11, and switched over to Omnirom shortly after that. I'm using Google Camera with an Omnirom nightly from November, and I've never had a camera crash.
Agree with you about getting a Motorola. I'd love it if the next Moto G refresh (if there is one) came with some more RAM, increased storage (16GB instead of 8), 4G, and a multicolour led. Being able to customize the colours to suit the category of app is something I love about custom ROMs. That should be baked into Android, to be honest (but at least there's LightFlow).
Click to expand...
Click to collapse
The thing with Motorola is that their stock roms are basically just stock android. No laggy touchwiz skins, just a google launcher. Bloatware is at a minimum. A low spec phone like the moto G still is great because of how vanilla its experience is.
Rumours have it that the galaxy S6 international variant will have an exynos processor. I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch. As it is now, phone's are so fast, that it's very hard to find a way of improving them. Like who compares app opening times nowadays? That will be much the case for 2015's flagships as well. I doubt I'd be disappointed if I had the next Samsung release if I thought I'd be in for a laggy UI, it's just whether I can tolerate the touchwiz experience or if I wanna switch to a vanilla aosp rom. That's where the problem arises.
arashvenus said:
SlimRoms is the answer
unlike CM, Slim has a I9300 maintainer, has support, every weekly update works properly.
Devs should really take a look at Slim's Gerrit and Freenode/#SlimDev
Click to expand...
Click to collapse
But only in your imagination. There is noone at slimrom. Just check their gerrit.
whatsgood said:
Rumours have it that the galaxy S6 international variant will have an exynos processor .... I found a thread comparing the leaked info of the snapdragon 810 vs the next exynos processor and it seems that the exynos is getting a lot of popularity from users on the thread and it ain't no slouch.
Click to expand...
Click to collapse
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Correct.
Eleve11 said:
Correct.
Click to expand...
Click to collapse
Well then, no more Samsung phones for me, then. Not unless they use Qualcomm..!
StephenJSweeney said:
Aren't the Exynos processors the cause of much grief in the open source community, though? Aren't Qualcomm processors, such as the Snapdragon, much more popular because they're easier to work with..?
Click to expand...
Click to collapse
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
whatsgood said:
Yes, that's what i thought but people are showing interests due to how powerful the processor is. I think they're saying it's more powerful than the snapdragon 810. I'm not that techy but they were mentioning that the new exynos will be smaller in size or something, whilst the snapdragon will be bigger. Apparently smaller is better, but yes the problem is open sourcing. If you want to install a stock android custom rom, it will be difficult for developers to build a rom that can push your phone to it's full potential. Snapdragon doesn't have this problem.
Basically if you love flashing different roms that are fully functional a snapdragon 810 phone is for you. If you like what Samsung offers in it's next flagship and won't be tempted to flash other roms then the exynos is for you
Click to expand...
Click to collapse
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
JustArchi said:
I prefer to have less powerful processor, with full documentation how it works, rather than exynos and big giant hackish black box, which noone understands.
The problem is not with the exynos, but with Samsung. Judging from Exynos4, their kernel sources and own experience, exynos may look like it works, but amount of hacks and dirty workarounds to make it work, is too damn high. This could all be solved if Samsung changed their policy from "respect GPL, f*ck the rest" to "respect developers, show them that our SoC can be developer-friendly, too".
The problem is that we're not even 0.01% of Samsung sales, so why should they care. I'm not going to buy Samsung phone again, regardless if it has Snapdragon inside or not. The problem is not with the Exynos, the problem is in Samsung's policy.
Click to expand...
Click to collapse
Yeah +1 for that. My next Phone will be definitly a Sony or a One plus. I think both are the developer friendliest in android ...
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
khanmein said:
what for get android with huge ram but still lag? i won't go for android for sure. just stick with ios better. with android 8gb & asop, cm etc still can't fix the bugs. android received update so slow than ios.
Click to expand...
Click to collapse
Yeah you are right but i think the most decent phone is the htc one......i would buy a windows phone rather than an iPhone
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
whatsgood said:
http://www.reddit.com/r/Android/comments/2qn8s4/new_impressive_lollipop_touchwiz_gives_nexus_line/
This is an interesting article on the new touchwiz that appears in android lollipop on the galaxy note 3. Surprisingly I can see nothing but praise from this person, apparently it seems to be running very well in comparison to touchwiz on KitKat. Is Samsung finally doing something good?
Click to expand...
Click to collapse
its useless even if they port it to our i9300..1gb of ram..maybe its time to upgrade to more stronger phone..
Oneplus x is a really nice phone , i especially like its form factor which is why i brought one just today , but i read a thread where oneplus did not release MM kernel sources and this phone's production stopped. Now i am thinking about giving it back as it would be nearly impossible for future development.
What would anyone who is a present owner suggest in such a situation ? I am only getting this phone because of its 5 inch form factor and good development team.
P.s i know onyx got some top class dev's and Nougat is already on its way, i do not doubt their potential but just this phones future development progress.
Thank you.
We don't need OnePlus for further development. We are perfectly capable of keeping it up to spec. You'll be fine. Enjoy your new toy
It's a phone. You aren't buying it for its future development, you buying it for its features and the fact that they satisfy you. Don't fall in such buyer loop.
Sent from my ONE E1001
sniper20 said:
It's a phone. You aren't buying it for its future development, you buying it for its features and the fact that they satisfy you. Don't fall in such buyer loop.
Sent from my ONE E1001
Click to expand...
Click to collapse
I am a person who is easily bored out using the same rom , i like aosp but i tend to move between different roms (once a week) just because of that . The fact that this phone has CM13 , MIUI (WIP) , SAILFISH OS excited me the most. This is the only reason i look for a phone with good dev community in it which partially require OEM & Chipset supplier support to release drivers.
Of course the phone excites me but I've looped through so many phones that the phone hardware alone does not excite me anymore.
Thank you for the advise tho.
RJDTWO said:
We don't need OnePlus for further development. We are perfectly capable of keeping it up to spec. You'll be fine. Enjoy your new toy
Click to expand...
Click to collapse
thank you for the reply , but might i ask why . I always thought OEM's have to release the kernel sources or the phone will have less chance to be supported by next android version because dev's have to depend on hacks to get things working which is never ideal.
tufli said:
thank you for the reply , but might i ask why . I always thought OEM's have to release the kernel sources or the phone will have less chance to be supported by next android version because dev's have to depend on hacks to get things working which is never ideal.
Click to expand...
Click to collapse
No. Theoretically the only thing we need kernel wise is the DTS and a few drivers. We can pull the source for the 801 from Qualcomm themselves. We don't need an OEM outside of that