Just wondering. The reason I ask if for the IM app, not myFaves. I know there are other IM apps out there, but none of them work as well (reliability-wise) and are as simple as the stock IM app, especially when you compare it to the complicated apps that try to use multiple IM clients. Meebo is the best one I've used so far, but I still have issues with that one. Unless someone is working on getting that to work for ADP1.5?
someone is definitely going to make one when we get our hands on the official update.zip
I just can't believe it's taking this long for T-mobile to push the updates (or are then even doing it on a large scale?)
On official update.zip by T-Mobile is already aviable. But the problem in my sight is, that this update.zip is only including patches, and not the full Update. So it would take a lot more time.
^
What he said.
I'm sticking to my good ol Android Open Source based builds with a touch of ADP1.5
So much more possible that way.
Hey all, brand new to rooting and flashing ROM'S, but yesterday i rooted my i747 galaxy s3 and flashed it succesfully with the most recent nightly of cm10... i dont know much about it and had a few questions that i hope people had answers for...
How can i tell what has been changed in each new nightly update? I cant find anywhere to see what bugs they fixed or what as added.
Should i be updating ever time a new nightly comes out or not?
I noticed google now is working, but not speaking back to me. is this a known error? or is there something i need to change- i have it set to always speak back.
Thanks for the help, i am incredibly new at this as i recently switched to android from iphone, and dont know much about rooting phones or CM10
anyone? the google now not speaking back is really annoying
you should be updating it and well google wasnt meant to run on it yet so it might be a bug for a certain ammount of time ...also update it when theres an update it will usually help with some bugs
ok... I already am a junky on building and updating computers....
now this is becoming fun for me, albeit I can't really "upgrade" hardward on my phone...
So... I am flashing different ROMS to my blaze... and they all seem to have some little goodies here and there...
Currently I am quite fond of SlimKat and am sitting here like a kid on Christmas Morning waiting for @InkSlinger420 to bust out the 3.2
Does anyone have particular favorites of a ROM.... and why?
OH ... one other thing... Is it safe to presume on some of these (CM11) that if you flash fresh to try it, you can just do the nightlies? Or do you have to do them sequentially? I would presume that each is just a build on the previous, so by flashing the most recent nightly that would be the most current version, and not just a bug fix on something that is supposed to be on my phone already?
Thx again!
Noooooooob (pretty soon I will start to delete some of my o's )
crazyryan1 said:
ok... I already am a junky on building and updating computers....
now this is becoming fun for me, albeit I can't really "upgrade" hardward on my phone...
So... I am flashing different ROMS to my blaze... and they all seem to have some little goodies here and there...
Currently I am quite fond of SlimKat and am sitting here like a kid on Christmas Morning waiting for @InkSlinger420 to bust out the 3.2
Does anyone have particular favorites of a ROM.... and why?
OH ... one other thing... Is it safe to presume on some of these (CM11) that if you flash fresh to try it, you can just do the nightlies? Or do you have to do them sequentially? I would presume that each is just a build on the previous, so by flashing the most recent nightly that would be the most current version, and not just a bug fix on something that is supposed to be on my phone already?
Thx again!
Noooooooob (pretty soon I will start to delete some of my o's )
Click to expand...
Click to collapse
Ok......To answer favorite question, has to be gummy rom (PAC a VERY close second)...All the fun, none of the bs..
On nightly builds, just backup current build your running through recovery, and wipe as they all say to do in the thread, and flash rom and corresponding gapps package, Newest nightlys offer the newest features added to source and MAY BE some bugfixes, depending if a dev has had a chance to work on hardware.. (but as all nightlys are NOT stable, May also break your device and require a restore of your backup)...There are NO guarantees with nightlys, so if you are new or not comfortable right away, wait for feedback from a more qualified user..
Favorite or best is really up to the individual and is based on YOUR needs and wants.
As XDA is not a support site, members are expected to test all the products offered to make this, very subjective, decision on their own.
Head over to the dev sections and flash away, and as always, read before you do. Tons of info in each individual thread.
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
In an interview of Kondik, he said that now that they're a company and this is their product, they have actual paid devs working on the updates, which should make their code more higher quality and updates faster (though now that they have to make it stable means that it will slow updates down, I hope there will be a nightly channel)
mannu_in said:
Well I think official updates are irrelevant as developers here will release their ROMs with line to the latest Google releases for the device.....I will just be buying One for Hardware.......
Click to expand...
Click to collapse
Don't bet on that. Look at how poorly the community CM builds (i'm talking official nightlies, those are "community" builds from the point of view of Cyngn) for the Oppo N1 are. It's Cyngn's official position that they don't care at all if the community builds are completely broken and that users should have no expectations whatsoever from them.
Use nightline updates and you'll be happy :laugh: it helps a lot to devs make CM better and better
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
MrAndroid-HD said:
From the official point of view CM have said in a previous interview that we should expect 4 months on a major android version upgrade in CM11S.
I think that's pretty decent, anyone in need of a faster update schedule should jump on the nightly train, or find another rom
Click to expand...
Click to collapse
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
floepie said:
Right, but in terms of waiting times, I was referring even to the nightlies cycle. After a new Android release version, it usually takes months before they start to work on it. The stable releases, even the monthly ones, would take even longer. Correct me I'm wrong, but those hoping to jump on the nightlies cycle after the next version might be in for a rude awakening. But, in terms of stability for the nightlies, I have no doubt, they could be used as daily drivers, that is, if they open up nightlies to the general public.
Click to expand...
Click to collapse
Remmember this is a special verison of CM, there is nothing like it used to that you can rely on. I know how things where in the past, but this is really one of their first projects where they are the main system on the phone from start - I know they where on the Oppo N1 also from the beginnign, but as far as I know, there weren't made a set deal like with the OnePlus..
Here OnePlus have a 2 year contract on a special version of CM.. Only time will tell us how much it differs from their normal releases..
As said before, the Cyanogen transition from a hobby to a company might give a huge benefit here.
It's true that the waiting time between stable releases has historically been quite poor, but I have extremely good experiences with CM nightlies. I'm running nightlies on my Galaxy Nexus and Nexus 7, and I can't really complain about anything. Hopefully we'll have an easy opt-in to the nightlies (like there is currently) and that the first nightlies get pushed out fast as Android is updated.
Also, we'll always have community builds.
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
LiquidSolstice said:
Honestly, as long as they open source whatever code they use for the screen-off wake gestures, I don't care what I run on the device. As previously mentioned by others, I'm buying the hardware, not the software.
Click to expand...
Click to collapse
That's done via touchscreen controller firmware - which isn't itself opensource (it's just a blob encoded into a header file within the kernel), but will work no matter what you're running on the device with a only a few tweaks to the frameworks/kernel. Plenty of projects have experience with these tweaks since the Oppo N1 had the same capability.
floepie said:
So, yeah I'm a bit on the fence with this one. I have an N5 and I love the notion that it's pretty much the first device to receive updates. But, more often as of late, Google pushes updates via its services and even more recently by making its apps available to all, at least to devices running 4.4.x. So, the importance of being able to run with the very latest Android version has been somewhat mitigated.
The thing that has me concerned right now about the One+ 1 are the very long update cycles of CM. Should Android 5.0 roll out within the next few months, it would mean, based on CM update history, an additional 6 months before CM moves on to it the latest Android version nightlies roundup. 6 months is often longer than it takes even the big manufacturers to skin and update the latest Android version, waiting periods which proud Nexus owners have been able to avoid.
Just curious to hear from Nexus people who are thinking about this device and what any inevitable updates might mean to you?
Click to expand...
Click to collapse
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
maxver0 said:
Keep in mind they were just an independent developers they were getting some random people WHO ACTUALLY WANTED to help maintain some devices even while there wasn't any driver or source code avaliable (Samsung) which is really hard. They didn't had any office and they weren't getting paid for that. Now they have access to all tools from Google and other manufacturers such as Qualcomm and other drivers which gives them much more possibilities like LG, Samsung or Sony already had from the beginning. CyanogenMod 11S will be much more stable and easier for deliever.
Click to expand...
Click to collapse
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Entropy512 said:
Except that they've already had one official partner device (Oppo N1) where the user experience was actually WORSE for most people than many of the community-supported devices.
Click to expand...
Click to collapse
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
maxver0 said:
I don't know users experiences about Oppo N1 but I do know that CyanogenMod didn't get as many tools from Oppo as they do have now from Oneplus and their hardware partners. Abhisek Devkota from CyanogenMod have been talking about it somewhere on Google plus. I'm not going to sit on cyanogenmod anyway most likely, especially when there will be support from Slimkat and francisco. Reminder: Oneplus One will be fully unlocked and sources will be avaliable for everyone.
Click to expand...
Click to collapse
That's bull****. The only thing they can blame Oppo on is the initial O-Click fiasco - nothing beyond that. (And I'm letting them slide for the O-Click mess, that really wasn't their fault)
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
dracinn said:
If anyone thinks CM is slow I had 4.4 on my tf700 within one month. Nightlies of course.
Click to expand...
Click to collapse
We're not talking about nightlies here, since there's no guarantee for users that they'll be anything but crap. Cyngn is ADAMANT about this position. If community builds (nightlies) for a Cyngn device are broken, you're SOL.
Entropy512 said:
Any failures beyond that have nothing to do with Oppo and everything to do with Cyngn. If you look at oppoforums, the Oppo section of the CM G+ community, and CM's own forums, they're full of users saying they're switching to Omni... Which happens to be maintained by people who got the N1 1-2 months later than Cyngn, aren't paid to work on the device, and didn't have anywhere close to the level of access to Oppo engineers and documentation (Cyngn signed an NDA for Qualcomm docs, we didn't).
So if users are reporting all over that they're switching to a project which had LESS of everything that Cyngn said they didn't have enough of - don't you think something is wrong there?
Click to expand...
Click to collapse
Well that someone prefer more one rom than the other doesn't prove anything. I prefer custom rom Slimkat on my Nexus 4 even if stock is super stable or even a cyanogenmod rom on my phone. I tried OmniRom on my N4 tho but I couldn't find multiwindow at all in rom so I flashed over something else...
I'm a little confused by the range of options available for the Photon Q. Of course, CM12 is still in development, but does CM11 have a stable build at this point? What are people's experiences with it, and do they recommend updating from stock?
I'm mainly thinking about it because I'm starting - very slowly - to stumble across app compatibility issues, and I want to hold off updating my phone for at least another year. Kind of holding hope that Blackberry will finally release an Android phone.
kennyminot said:
I'm a little confused by the range of options available for the Photon Q. Of course, CM12 is still in development, but does CM11 have a stable build at this point? What are people's experiences with it, and do they recommend updating from stock?
I'm mainly thinking about it because I'm starting - very slowly - to stumble across app compatibility issues, and I want to hold off updating my phone for at least another year. Kind of holding hope that Blackberry will finally release an Android phone.
Click to expand...
Click to collapse
CM11 has EOL'd. Final official release 6-26 (obviously the jbbl version for the QHD). Newer builds with stagefright patches have been released (see MCP1's builds over in RHD).
CM12 has also EoL'd.
CM12.1 is still in development.
CM13 (Android M/6.0/Marshmallow) has not started yet.
Sent from my ATRIX HD using XDA Free mobile app