anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
hki_peter said:
anyone know that what is difference between Unofficial CM9 Nightly and alpha 0.6 ?
Click to expand...
Click to collapse
Nightlies are probably going to be less stable.
Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly.
And now you know.
And knowing's half the battle.
sean is here. said:
Nightlies are probably going to be less stable.
Basically, when you get a nightly, it's not yet been released. It's what somebody was working on last night...when they quit working on it, whether successful in what they had been working on or not, it was uploaded - hence the name, nightly.
And now you know.
And knowing's half the battle.
Click to expand...
Click to collapse
Well its slightly more than just something someone happened to be working on and left it!
I'm using the KANG of 20120216 and finding it is far better than my experience with .06!
And I'm about to flash 20120217.
pa49 said:
Well its slightly more than just something someone happened to be working on and left it!
I'm using the KANG of 20120216 and finding it is far better than my experience with .06!
And I'm about to flash 20120217.
Click to expand...
Click to collapse
EDIT: I re-read this reply after posting my response, and the first sentence is just incorrect. A 'nightly' is nothing "more than just something someone happened to be working on and left it".
The rest is subjective opinion, but the definition of what a nightly is can be found clearly explained below.
I think you've misunderstood me, or something else somewhere along the line.
I'm not saying that they're better or worse than official releases.
I was merely pointing out that the way they come about, is that they aren't fully evaluated and tested for stability in order to be released publicly as a finished product.
Before a major release, devs will typically spent time testing their software themselves, in addition to sending it out to 'focus groups' (they aren't REALLY focus groups but serve the same function) where they are further tested...then upon completion of testing, or when a threshold of minimum functionality has been reached (often with a pre-specified maximum number of bugs or critical failures) they can be released publicly.
Nightlies don't go through that extensive testing. That's where the name comes from. The devs 'clock out' and the ROM is built, and posted as a 'nightly'.
From the CM Team:
... Lastly we have the Nightlies, which are as volatile as a firmware can get. These releases keep coming at an interval of a day or two and if you do end up trying one of these, do not be alarmed if the your device goes cuckoo on you. These ROMs are largely untested, and as advised by CyanogenMod, not meant for use for an average user. These releases, are meant to test untested waters with tweaked codes that may or may not break your phone.
Click to expand...
Click to collapse
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
joggerman said:
My understanding was that the nightlies were being built automatically by a script that pulls the most recent source from the cm server. As new code is added daily by devs it is automatically put into nightly builds for testing.
Click to expand...
Click to collapse
As far as I'm aware, you are correct.
Hey guys,
I just want to add, the one of the developers of the official CM9 alpha release is recommending users install the nightly as there may not be an official update pushed put anytime soon.
http://liliputing.com/2012/02/nightly-builds-of-cyanogenmod-9-for-the-hp-touchpad-now-available.html
Anyone know which nightly is pretty stable?
wonshikee said:
Anyone know which nightly is pretty stable?
Click to expand...
Click to collapse
go for alpha 1 as dalingrin said the nightlies won't be based on alpha 1 until a few days later.
Related
Hi, first up, my apologies if this has been asked before, but I did search without success.....
During reading various threads on XDA, I've come across words such as Alpha, Beta, Release Candidate, Stable, Nightly and Experimental.
Some speak for themselves....
Alpha.....the beginning of a ROMs development.
Beta......a little bit further along than Alpha.
Stable....everything works, no further development planned.
But where, and in what order do you get Nightly, Experimental and Release Candidate.....
Not a terribly important question I know, but I'd like to find out so that I can understand at a glance (by reading that one word) what I can (sort of) expect from any given ROM.....
Thanks in advance.....
Sent from my CM10.1 powered Galaxy S2 with tapatalk 2
Nightlies are nightly (or something close to it) builds with usually small changes each time. This nightly stage will overlap the entire rom building phase (from alpha/beta to the stable ones).
Release candidates are builds that are called 'almost stable enough' to come close to the final stable release (not a real technical explanation but I think you get it).
Experimental builds.. Not really sure, but what I understood from them is that they sometimes contain some differences from the usual nightlies to test features that are not always included in the RC's or stable builds.
Anyone who has to add/change anything: please do
Sent from the Matrix
Thanks for your answer fella.....I understand your explanations of the terms.....but that "muddies the water" even more....I guess what I was hoping for was some sort of "linear chronology" when it came to applying these names.....
Alpha>>Beta>>Experimental>>Nightly>>Release Candidate>>Stable……………
But I see now that's not the case....so what IS the best way to tell how "mature" a ROM is, how suitable it is for "daily" use.....look at the "known issues" I guess?
Sent from my CM10.1 powered Galaxy S2 with tapatalk 2
keithross39 said:
Thanks for your answer fella.....I understand your explanations of the terms.....but that "muddies the water" even more....I guess what I was hoping for was some sort of "linear chronology" when it came to applying these names.....
Alpha>>Beta>>Experimental>>Nightly>>Release Candidate>>Stable……………
But I see now that's not the case....so what IS the best way to tell how "mature" a ROM is, how suitable it is for "daily" use.....look at the "known issues" I guess?
Sent from my CM10.1 powered Galaxy S2 with tapatalk 2
Click to expand...
Click to collapse
Just install the latest nightly If the known issues (or the issues you find yourself) aren't bothering you, you'll be fine.
Sent from the Matrix
So i'm a bit confused. Which builds are better for fireball? The official cyanogen nightly or the unofficial mdm builds? I can't post in the offical dev post for cyanogen so i have to post here.
Right now i'm running the latest nightly. All seems to be be pretty stable. Just missing 16:9 for the camera, and once in a while while i'm running with my nikeplus app and the google music playing, if i hit the power button to turn off the screen it resets the entire device.
Anyways, i can't tell which builds are better / ahead of the others?
Sorry i know i posted this in another forum, but it was the wrong forum.
danjfoley said:
So i'm a bit confused. Which builds are better for fireball? The official cyanogen nightly or the unofficial mdm builds? I can't post in the offical dev post for cyanogen so i have to post here.
Right now i'm running the latest nightly. All seems to be be pretty stable. Just missing 16:9 for the camera, and once in a while while i'm running with my nikeplus app and the google music playing, if i hit the power button to turn off the screen it resets the entire device.
Anyways, i can't tell which builds are better / ahead of the others?
Sorry i know i posted this in another forum, but it was the wrong forum.
Click to expand...
Click to collapse
I use MDM builds because I have the flicker issue from the cynagen 3.4 kernel. I don't think I've had any random reboots on the MDM like I did with the cyanogen nightlies.
Why then are the mdm releases.. or the guy behind the mdm releases, not working on the official releases? I mean why is his hard work not going into the official releases?
I feel like if i switch to mdm i'm going to miss fixes in the official nightlys.. as it's just one guy working on it.
Just doesn't make sense. the official releases are open sourced at git hub right? So why isn't the mdm guy working on the official releases?
danjfoley said:
Why then are the mdm releases.. or the guy behind the mdm releases, not working on the official releases? I mean why is his hard work not going into the official releases?
I feel like if i switch to mdm i'm going to miss fixes in the official nightlys.. as it's just one guy working on it.
Just doesn't make sense. the official releases are open sourced at git hub right? So why isn't the mdm guy working on the official releases?
Click to expand...
Click to collapse
@mdmower is working on official releases. instead of merging patches that might cripple the officials he is doing "beta" test outside of it. hence why he's always asking for feed back.
once he gets enough feedback on the mdm builds he submits a patch to cm and it gets merged into source. ^_^
i would go with the mdm5 build because it has a working camera focus but once he merges the RIL commit i will be going back because i like the stability of the officials minus the RIL hickup i had. but everyone is different and will react differently.
where did you get the 3.4 kernel?
Sum Dumb Guy said:
I use MDM builds because I have the flicker issue from the cynagen 3.4 kernel. I don't think I've had any random reboots on the MDM like I did with the cyanogen nightlies.
Click to expand...
Click to collapse
where did you get the 3.4 kernel?
synisterwolf said:
@mdmower is working on official releases. instead of merging patches that might cripple the officials he is doing "beta" test outside of it. hence why he's always asking for feed back.
once he gets enough feedback on the mdm builds he submits a patch to cm and it gets merged into source. ^_^
i would go with the mdm5 build because it has a working camera focus but once he merges the RIL commit i will be going back because i like the stability of the officials minus the RIL hickup i had. but everyone is different and will react differently.
Click to expand...
Click to collapse
This is mostly right, just couple clarifications:
mdm releases exist because CyanogenMod cannot publish releases that include a certain proprietary camera file. They are based on the latest stable CyanogenMod release (10.1.2) with a few tweaks that improve stability. Typically, these changes are backports from nightlies. In my opinion, these are the most functional CyanogenMod releases to date. Unfortunately, the kernel in use by these releases had to be dropped in order to prevent legal repercussions to CyanogenMod from closed-minded manufacturers.
I am actively working on the official nightlies. Unfortunately, HTC has not released kernel source for this phone that is meant to work with jellybean. Furthermore, hardware support (for every phone out there) still relies on closed-source manufacturer drivers/blobs, and this phone hasn't seen a jellybean release yet. Long story short, there's stuff that just doesn't work because of lack of jellybean-compatible kernel/firmware/drivers from HTC.
mdmower said:
This is mostly right, just couple clarifications:
mdm releases exist because CyanogenMod cannot publish releases that include a certain proprietary camera file. They are based on the latest stable CyanogenMod release (10.1.2) with a few tweaks that improve stability. Typically, these changes are backports from nightlies. In my opinion, these are the most functional CyanogenMod releases to date. Unfortunately, the kernel in use by these releases had to be dropped in order to prevent legal repercussions to CyanogenMod from closed-minded manufacturers.
I am actively working on the official nightlies. Unfortunately, HTC has not released kernel source for this phone that is meant to work with jellybean. Furthermore, hardware support (for every phone out there) still relies on closed-source manufacturer drivers/blobs, and this phone hasn't seen a jellybean release yet. Long story short, there's stuff that just doesn't work because of lack of jellybean-compatible kernel/firmware/drivers from HTC.
Click to expand...
Click to collapse
and thats why i like the XDA page system. ^_^ straight from the source ladies and gentlemen. thank you for clearing that up.
bad_christian said:
where did you get the 3.4 kernel?
Click to expand...
Click to collapse
3.4 are part of the official nightly releases. MDM uses 3.0.xx Kernels that are more stable for my phone.
I now it's not the latest or greatest, but could a kind dev please build a CM11 rom for our devices? CM12 isn't fleshed out enough for me and stock is annoying.
Would this be a big ask?
I am in vacation, can make a build next week if it's not to long for you
I'm in the same boat. I'm not sold on CM12. Or rather, Lollipop in general. The lack of functional xposed mods is what's really killing it for me right now.
moritz31 said:
I am in vacation, can make a build next week if it's not to long for you
Click to expand...
Click to collapse
Is this still being worked on?
**** forgot that, will try to make a build today
Looked into it -> my opinion is that it makes no sense, because cyanogenmod didn't adapt the sources for cm 11 and the cm 12 sources for cm 11 will be a bit tricky
Is it undoable?
Not undo able but it makes no sense
well, go ahead and take your time. I'm definitely excited and thankful, though.
I don't suppose anyone's considered building liquidsmooth on the z3 tablet compact?
moritz31 said:
I am in vacation, can make a build next week if it's not to long for you
Click to expand...
Click to collapse
Would it still be possible to build CM11? I share the same sentiments regarding CM12... the lack of video playback being the deal-killer.
moritz31 said:
**** forgot that, will try to make a build today
Click to expand...
Click to collapse
Not to rush you or anything, but is this still being worked on?
And I don't suppose anyone would consider building Liquidsmooth?
Or is this being dropped?
Calamityx1 said:
Or is this being dropped?
Click to expand...
Click to collapse
guys...read post #5 and #7
let me rephrase this for you: "too much work; not gonna happen; be patient and wait for CM12 to improve"
I've made a request thread on the CM boards:
http://forum.cyanogenmod.org/topic/106183-requestxperia-z3-tablet-compact-lte-sgp621/
I commented on the post. Anyone else willing to run cm11 please request it in the thread.
And bump
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
t3chn0s1s said:
I know this is yesterday's news but I felt compelled to post this and get other users input on this topic.
http://www.cyanogenmod.org/blog/releases-11-12-final
What I don't understand is Cyanogen's priorities when it comes to which devices get 11, 12 or 12.1. I completely understand about phasing out CM11/KitKat as that is now a rather "old" version of android. However what I don't understand is why a device as new/old as ours (Aug 2013 is not THAT old) is stuck on CM12 (and now a final Snapshot build as of 6/25)? I mean, the Galaxy S3 is even getting 12.1 builds. I'm wondering if its because that was a far more popular device than the G2 was?
Just wanted to put this out there and see what other people think and find out what they're running currently on their G2 variant. I own the US T-Mobile D801 variant and do NOT want to run stock (LG) Lollipop since my device tends to run extremely HOT on it. I know not everyone was complaining about their G2 overheating on stock LP but I notice a considerable difference running CM12.
So, how do you guys feel about this? Do you even care or what?
Click to expand...
Click to collapse
We haven't had nightlies for a while now. What you see as nightlies aren't really worthwhile builds, they didn't have any device or kernel fixes for the g2.
A new 11 build is coming probably because half the android userbase relies on kitkat at the moment.
As for the s3, it's not getting CM12 nor 12.1, not the international version at the least. Archi is maintaining an unofficial version, but it still carries the bugs from 10.0/10.1.
Lastly, this is the commit that requires to be merged in order for the builds to even be considered started:
http://review.cyanogenmod.org/#/c/93181/
Without it, nothing CAF related can be merged, and as such, no CM12.1 builds can be had for our device. I believe the reason it's not merged because not all of the variants have a lollipop release, if they ever will get one. Also the whole bootstack/amount of users who don't reed is astonishingly dangerous to handle, so rashed simply preferred to skip building for now.
Finally, it's not that popular of a device. It's a nexus without being a nexus with a locked bootloader, which is a pain in the ass and not too many maintainers have it left (they either went with G3 or skipped LG entirely, as did a whole bunch from the exynos team back in the day).
t3chn0s1s said:
I saw you responded to my post about CM12 nightlies not continuing for the G2. Wanted to ask you (since you didn't mention) what 5.1 (CAF source) ROM you're running? What would you suggest for a stable AOSP ROM that has device/kernel specific updates for our G2s?
Click to expand...
Click to collapse
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Choristav said:
Why not reply to me in this thread then?
I'm running official euphoria builds. Any caf roms run fine. They are all based on the same LG-devs CAF device source + kernel source. Some roms have specific tweaks, but as far as functionality, they all work the same way (ie: if bluetooth deep sleep is broken, it's most likely broken in every rom).
Click to expand...
Click to collapse
Sorry - was on my phone when I saw your replies and it was just easier for me to respond in the other thread.
Anyways.. thanks for the info. I've done some research and I'm a bit more informed about CAF and what it means to device specific sources, ROMs, etc. Are you just using the stock Euphoria kernel or something else?
On this forum @varund7726 builds his rather excellent ResurrectionRom from the latest CM code release. I suggest you use that. For the D803, @zr239 has beaten all odds including LG not releasing CAF code, to build a fully functional pure CM 12.1 ROM that closely tracks official CM repos.
Lg G2 has it pretty good !
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
t3chn0s1s said:
@Choristav
I wanted to clarify something you said in your initial response to my OP. You said the S3 wasn't going to get CM12 or 12.1 but when I navigate to the CM downloads page for ANY S3 variant - they ALL have CM12.1 nightlies still being generated. What exactly did you mean?
Click to expand...
Click to collapse
I checked, you are right, several of the qualcomm variants have cyanogenmod support. This means that they have active maintainers, but they also don't have to deal with locked bootloader crap, which is why the bump commit is so important for our device.
I only mentioned the international version, which support was dropped because it had a lot of issues thanks to its closed source exynos processor (it requires extra work, and some stuff doesn't end up working anyway).
Not really much to say, the commit is already in CM's gerrit, it's just waiting for review. Maybe it's a CTS-side issue?
Aside from that, being a maintainer doesn't really require much, just effort and presence. It's not an easy task, I'm just saying anyone can apply to be a maintainer and get nighties rolling for a device you might not even have heard of.
@Rashed97 is the man for our G2 when it comes to CM. Dont mind nightlies as long as Rashed is around
Note: he is currently busy with the One M9 but we will hopefully see some cool stuff from him in the future.
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Ploxorz said:
Not really a big deal, last I remember those nightlies were still using outdated jellybean components. I wouldn't use them, I would use something on the G2 forums like Rashed97 builds like someone else said.
I don't think that the availability of nightlies has to do with the device itself so much as it has to do with someone maintaining the g2 and building roms, so nightlies could come back at any time if someone steps up and does it.
Click to expand...
Click to collapse
And it appears you're correct as there is another nightly build up with today's date. I apparently posted this thread prematurely.
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
zelendel said:
Guys I wouldnt worry to much about CM, its not like they are the only (or even best) option in the forums. If you guys want development then dig in and make some for it.
Click to expand...
Click to collapse
You are absolutely right. I had no idea until I posted this thread that CM nightlies did not contain any device specific updates. I honestly NEVER used to like CM at all. I honestly hated it... until owning a OnePlus One. I originally had the G2 right when it came out in 2013 and sold it off long ago & moved on to better devices - but when my OPO got stolen about 2 months back or so - I had to find a relatively cheap, but decent device and the G2 was the best bang for the buck (5.2" display, quick charge 2.0, 3000 mAh battery) and no other phones in 2013 came close to the specs the G2 had at the time.
So, now that I know CM is basically a sh*t ROM for this device I'll be moving on to a ROM that is compiled using CAF sources. Thanks everyone for your input!
Somehow doesn't look too good so far:
https://jira.cyanogenmod.org/browse/CYAN-6556
But why oh why?
The LG G2 still is such a modern and powerful device. It might be almost two years "old", but it's way better than a lot of other current devices.
I am using AICP on my g2. It is based on CM(5.1.1).
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
seanp25 said:
What's the best place to follow updates / changes to the CAF stuff?
I know there's a handful of ROMs based on CAF sources, I'm not too interested in the changelogs of those ROMs, more following the progress of CAF before it eventually all gets merged into CM12.1.
Is this it? https://github.com/lg-devs/android_device_lge_g2-common/commits/cm-12.1-caf
Click to expand...
Click to collapse
I would watch the Code Aurora forums where CAF comes from.
zelendel said:
I would watch the Code Aurora forums where CAF comes from.
Click to expand...
Click to collapse
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
adamz667 said:
It's better to watch public activity on Rashed97's github. He is CM maintainer for LG G2 and he brought up CAF sources for our devices.
Click to expand...
Click to collapse
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
zelendel said:
No. It's far better to watch the main code base. Cm messes too much up by not testing code before merging.
Click to expand...
Click to collapse
Okay, but @seanp25 probably want to follow source changes for our device, not common CAF source.
Just saw this:
Çetin ÇÖNE wrote on Jul 26 11:18 AM:
Why there is no nighlies it's really stable. Merge it please
Seth Shelnutt wrote on Jul 26 1:26 PM:
There are no nightlies because SELinux is not enabled. Sensors break with it enabled and I don't have time to address it yet.
Click to expand...
Click to collapse
Source:
http://review.cyanogenmod.org/#/c/103673/
Some days after that there came this:
http://review.cyanogenmod.org/#/c/103674/
So maybe there soon will be 12.1 nightlies?
Just wanted to bring some good news, in case you havn't heard. Oppo has reviewed their OS-strategy and even though they’re proud of ColorOS they’ve realised it’s not what everybody wants, especially in countries outside Asia.
So they’ve decided to split their devteam and let one part focus on delivering a near stock android version based on AOSP. For the R5/R5s, apart from the camera app and screen off gestures, the ROM will be 100% AOSP.
As for updated to the rom, the initial AOSP ROM will be released based on Android 5.1.1 and the Find 7 has already received the update. R5/R5s is next in line and will get 5.1.1 soon and a promise of 6.0 early 2016.
There still is hope for Oppo!
Cheers!
Source:
http://community.oppo.com/en/forum.php?mod=viewthread&tid=42151&page=1#pid512161
Does anyone know when is ETA for R5?
also want to know...r5 are superb phone...but lack on rom support...
https://www.youtube.com/watch?v=WklHXS7EoGg
if you look in the comments, The closest thing to an eta is February
AOSP has been release in closed beta... i've signed up and will get back to you guys as soon as i've flashed it.
Cool thanks, led us know as soon as you have news .
Do you have a link to the sources? And/or to the rom to download?
Edit: nevermind, I found the link to the forum and how to apply :good:
rodman01 said:
Cool thanks, led us know as soon as you have news .
Do you have a link to the sources? And/or to the rom to download?
Edit: nevermind, I found the link to the forum and how to apply :good:
Click to expand...
Click to collapse
Nice to see you here.
Your Lollipop Rom for SG3 LTE is fantastic. My son is enjoying Lollipop.
I am still on KitKat with R5.
Hope that when you have sources to start your magic
Nice to hear that you and/or your son is enjoying some of my builds :good:
That would be great, but oppo github has no activities since weeks, but I am watching other repos too .
So, I got in the private testing group and finally got around installing the new ROM part of the Spectrum project.
The ROM is based on 5.1.1 and definitly feels snappy, however, there are quite a few bugs needing ironing out.
I made a little teaser for you guys: https://youtu.be/9EYWkox82Ew
Feel free to ask any question you might have.
Cheers!
Hey cool sounds good thanks for the info...do you have an idea how long it will last till it will be released? And whether sources (and if "only", local manifest, device, kernel and vendor repos) will be uploaded to github?
rodman01 said:
Hey cool sounds good thanks for the info...do you have an idea how long it will last till it will be released? And whether sources (and if "only", local manifest, device, kernel and vendor repos) will be uploaded to github?
Click to expand...
Click to collapse
Some update, a new alpha was released two days ago and it's MUCH more stable... almost all the bugs are gone and the ones that are left are minor or insignificant.
I feel the public release is very close now
The sources will be uploaded to git as soon as the dev's feel the build won't risk bricking devices, in other words colse to public release
Cheers!
super many thanks for the info and the update!
What is the time to release project spectrum
Sent from my R8106 using Tapatalk
mrx_vip said:
What is the time to release project spectrum
Sent from my R8106 using Tapatalk
Click to expand...
Click to collapse
There is at least one more alpha build coming out before public release... i would guess mid/late februari.
faldo said:
There is at least one more alpha build coming out before public release... i would guess mid/late februari.
Click to expand...
Click to collapse
community.oppo.com/en/forum.php?mod=viewthread&tid=43672
Within next week
Please faldo reply my pv message
Public release will come this weekend if everything goes well.
Alpha 2 is somewhat stable. Batterylife and some rarely signal drops and laggy performance are the last bugs.
Nilmotoo said:
Within next week
Click to expand...
Click to collapse
That ship has sailed...
Mux89 said:
Public release will come this weekend if everything goes well.
Click to expand...
Click to collapse
I'm not so optimistic... It all depends on how good the devs want to public release to be. If they didn't care so much, alpha 2 would have been the public release already. I think they do care and i think it's important for them that this project gets recieved well since it's somewhat a new concept.
But i hope i'm wrong and they're compiling public beta 1 as we speak (write)
faldo said:
That ship has sailed...
I'm not so optimistic... It all depends on how good the devs want to public release to be. If they didn't care so much, alpha 2 would have been the public release already. I think they do care and i think it's important for them that this project gets recieved well since it's somewhat a new concept.
But i hope i'm wrong and they're compiling public beta 1 as we speak (write)
Click to expand...
Click to collapse
look at the last Post from Marton: http://community.oppo.com/en/forum.php?mod=viewthread&tid=43748
This Friday or Next week
AAAAAAAANNNNNNNNNNNNNDDDDD HERE IT IS : http://community.oppo.com/en/forum.php?mod=viewthread&tid=43768&extra=
is it stable version or beta version only?
ciqbalz said:
is it stable version or beta version only?
Click to expand...
Click to collapse
A beta can be stable until proven otherwise... so your question is hard to answer.
There are still some issues but the phone works fine for every day use.