Hi,
I am talking about those cm-11-201312??-NIGHTLY-maguro.zip from: http://download.cyanogenmod.org/?device=maguro&type=nightly
Maybe something is completely broken there?
Runs faster than CM10.2 stable?
bat0nas said:
Hi,
I am talking about those cm-11-201312??-NIGHTLY-maguro.zip from: http://download.cyanogenmod.org/?device=maguro&type=nightly
Maybe something is completely broken there?
Runs faster than CM10.2 stable?
Click to expand...
Click to collapse
gots it on my toro as of today. wanted to check out the screen record feature/app but cyanogen still says i dont have a device capable of running it lies
Running CM11 Nightly since 7 december.
Everything is working, its stable and smooth.
For my daily use it's ok.
Had only problems with auto-restore, solved with the right gapps package.
Try SlimKat
I tried the CM11 and wasn't impressed. Try the latest SlimKat Beta. I've been running SlimKat since their first Alpha release, and it has improved significantly over the past couple weeks. SlimKat Beta is updated to the latest Android 4.4.1 software which improved the camera's functionality. Only issue remains an occasional random reboot...maybe once per day, if that.
bat0nas said:
Hi,
I am talking about those cm-11-201312??-NIGHTLY-maguro.zip from: http://download.cyanogenmod.org/?device=maguro&type=nightly
Maybe something is completely broken there?
Runs faster than CM10.2 stable?
Click to expand...
Click to collapse
I've been running the nightlies since they became available and I've never had any problems. No reboots, graphic glitches etc.
-----------------------------------------------------
Sign up for COPY with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=m3arsR
Free GiffGaff SIM with £5 credit: http://redir.info.giffgaff.com/r/?id=h4d8d850,c0e1337,c0e139c&p1=d3xp2pc
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Using the 1209 nightly, and the stability improved significantly compared to Euroskank's CM11 KitKang. That's all I can say, since performance stays largely the same.
Sent from Samsung Galaxy S Relay 4G @ CM11
I am running swordrune10's version for toro. I am having some trouble with the wifi switching, google backup/auto install apps on wipe and google play killing my battery but it runs great with art besides those issues.
I can say they work flawlessly. Huge improvement from 4.3, never had a crash / freeze, etc. It does lag a bit on received call, not a major issue for me though.
I've had wifi switching problems since 4.3 dropped. Its ok on CM11 but just barely
CM 11 nightlies since 12-6 have a major issues with LTE. Some users are either not getting it at all or having issues toggling between 3G and 4G in which 4G will not turn back on.
I have been using cm 11 since unofficial alphas and have had very minimal issues. I think the hand off issue fix was merged in the latest nightly as in the one you can flash tomorrow.
Related
Hi All,
I have recently installed this build cleanly on an AT&T Galaxy S3 (d2att) build from:
goo im nightlies (sorry - wont let me post link - under 10 posts)
I love this build. The UI mods available and the battery life (which was absolutely amazing) were well done and polished.
One of the big issues I had was that Bluetooth would not turn on at all.
I just wanted to know if this has been disabled (or not implemented yet)?
Thank you all and I look forward to using AOKP in the future. Unfortunately, without this, I had to move back to CM10.1 Nightlies.
snoopspecial said:
Hi All,
I have recently installed this build cleanly on an AT&T Galaxy S3 (d2att) build from:
goo im nightlies (sorry - wont let me post link - under 10 posts)
I love this build. The UI mods available and the battery life (which was absolutely amazing) were well done and polished.
One of the big issues I had was that Bluetooth would not turn on at all.
I just wanted to know if this has been disabled (or not implemented yet)?
Thank you all and I look forward to using AOKP in the future. Unfortunately, without this, I had to move back to CM10.1 Nightlies.
Click to expand...
Click to collapse
Bluetooth turns on for me, I don't use it but for what I hear you can make calls with it. Audio streaming is borked though.
Bluetooth doesn't work on any 4.2 rom yet, AOKP and AOSP (ie. CM10.1).
It's a very known issue.
Jsick said:
Bluetooth doesn't work on any 4.2 rom yet, AOKP and AOSP (ie. CM10.1).
It's a very known issue.
Click to expand...
Click to collapse
Sure it does - I am using bluetooth in my car with 4.2.1 (CM 10.1 NIGHTLY Jan 13-13 and previously builds) for some time.
Using it for audio has been laced with issues, like the no bass issue.
DarthDerron said:
Bluetooth turns on for me, I don't use it but for what I hear you can make calls with it. Audio streaming is borked though.
Click to expand...
Click to collapse
Can you provide me more details on the build/gapps/device/etc that you are using?
snoopspecial said:
Can you provide me more details on the build/gapps/device/etc that you are using?
Click to expand...
Click to collapse
Running RootBox now but 10/13, 12/12 gapps, Kt747
DarthDerron said:
Running RootBox now but 10/13, 12/12 gapps, Kt747
Click to expand...
Click to collapse
Hmm. RootBox looks interesting too!
Might try it out later tonight!
Thanks!
Wasn't there a kernel that said something about driver issues with bluetooth and wifi. I will have to look
Sent from my SGH-I747 using XDA Premium App
At my house I get a fairly weak LTE signal. It seems like I get much slower speeds while on LTE when I'm running an AOSP based ROM on this weak signal. I've tried CM10.1 nighties & CarbonRom. Like I said, the signal is pretty weak so sometimes I'll lose it when on either TW or AOSP but it seems like TW works better with it. What's causing this? Is there a way to fix it? Has anyone else noticed the same thing?
It is pretty much impossible to narrow down the culprit of signal strength, just think of how many variables are out there. It is said by many AOSP ROMs give a more accurate signal bar reading than TW. TW supposedly adds some boost to make it look stronger. One thing you can do is switch modems, they work different for different areas. I personally prefer to be on the most recent one always which right now is MA6. you can also go back to a TW ROM temporarily and make sure your prl and profile are up to date. Also you want to go to settings>about device>status to see you real reading for signal strength don't just rely on what the bars say. There is usually a way to even change this in your notification bar for most ROMs. Or you can download something like sensorly or open signal in the play store to keep track.
Sent from my Nexus 7 using Tapatalk 2
GiantJay said:
It is pretty much impossible to narrow down the culprit of signal strength, just think of how many variables are out there. It is said by many AOSP ROMs give a more accurate signal bar reading than TW. TW supposedly adds some boost to make it look stronger. One thing you can do is switch modems, they work different for different areas. I personally prefer to be on the most recent one always which right now is MA6. you can also go back to a TW ROM temporarily and make sure your prl and profile are up to date. Also you want to go to settings>about device>status to see you real reading for signal strength don't just rely on what the bars say. There is usually a way to even change this in your notification bar for most ROMs. Or you can download something like sensorly or open signal in the play store to keep track.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The thing is that it isn't just the reading. When I do a speed test I generally get less than 1 mbps on AOSP, but with TW I get 3 to 8 mbps usually. This is from the exact same spot in my room & at the same time of day too. I don't know if there is a difference anywhere else I go because I don't switch ROMs while I'm out. I'm using the MA6 modem right now & found that it works best for me. I'm just confused on how LTE speeds on TW could be so much better when my modem & everything is the same.
I figured out something really weird last night. I clean flashed the CM10 stable build & LTE worked just as well as it does on TW. Then I clean flashed the latest CM10.1 nightly and LTE was performing poorly again. Could it be a problem with Android 4.2?? Anyone experience the same thing ever? I'm going to try some more tests tonight.
Fire Ball said:
I figured out something really weird last night. I clean flashed the CM10 stable build & LTE worked just as well as it does on TW. Then I clean flashed the latest CM10.1 nightly and LTE was performing poorly again. Could it be a problem with Android 4.2?? Anyone experience the same thing ever? I'm going to try some more tests tonight.
Click to expand...
Click to collapse
Strange. May be just some bugs that havent been fully worked out yet
CNexus said:
Strange. May be just some bugs that havent been fully worked out yet
Click to expand...
Click to collapse
Possibly. I did a lot more testing today. LTE signal & speed was better on all CM10 nightlies while it was still performing poorly on all CM10.1 nightlies, Slim Bean stable, and CarbonRom stable. The CM10 nightly from 12/26 (the last CM10 nightly before CM10.1) works great while the CM10.1 nightly from 12/18 (the first CM10.1 nightly) performs poorly. I tried a few more nightlies at random dates for both CM10 & 10.1 also and results were the same. So I'm guessing it has to do with Android 4.2 since all ROMs on 4.1 work fine! I'm not really sure what else I can try.
Try not using nightlies and only use stable or m snapshot. Of course you won't get stable results from a nightly. That's why they are called a nightly.
Sent from my Nexus 7 using Tapatalk 2
GiantJay said:
Try not using nightlies and only use stable or m snapshot. Of course you won't get stable results from a nightly. That's why they are called a nightly.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Haha, true. I just find it really weird that CM10 nightlies are fine while CM10.1 has the problem. The Slim Bean & CarbonRom builds I tried were supposedly stable releases.
GiantJay said:
Try not using nightlies and only use stable or m snapshot. Of course you won't get stable results from a nightly. That's why they are called a nightly.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Eh well it depends. I've found that developer builds and test releases and the such tend to function better than the "stable" releases of the same rom or package
But thats just my experience
Was wondering if there was a recommended Cyanogen nightly in terms of stability, things working etc? Or alternativley are there other roms (other than stock) that are more stable/working? Downloaded last nights nightly but there seem to be quite a few things not functioning...
Sgt7 rom works great
--
Sent from my mind to your screen.
Thanks!
elitelemming said:
Was wondering if there was a recommended Cyanogen nightly in terms of stability, things working etc? Or alternativley are there other roms (other than stock) that are more stable/working? Downloaded last nights nightly but there seem to be quite a few things not functioning...
Click to expand...
Click to collapse
I haven't noticed anything not working, and I've been on the nightlies since they started.
What things ate not working for you?
Sent from my MB860 using Tapatalk 2
chronicfathead said:
What things ate not working for you?
Click to expand...
Click to collapse
I may have spoken too soon, a few issues were just me not being familiar with JB 4.2 and how to set it up, couple of issues I've been having is that formerly full screen games and other apps are no longer hiding the on screen buttons (with the Amazon firmware there was a small pull-out tab to get them), though perhaps there is a configuration switch I am missing for this? Also some video appears to be tearing, though to be fair this might just be the video app... Also CM seems to be ignoring whatever I set the homescreen grid to be.
Does any one know if there's an issue with Bluetooth on the 2/3 build of the Unofficial Liquid Smooth? The processes crashes and resets every time my phone connects to car. the 1/18 build is the last one that worked for me.
54852845511
fryediablo said:
Does any one know if there's an issue with Bluetooth on the 2/3 build of the Unofficial Liquid Smooth? The processes crashes and resets every time my phone connects to car. the 1/18 build is the last one that worked for me.
Click to expand...
Click to collapse
I Have had no problems with bluetooth with the 1/18, 1/25, 2/3 or 2/5 builds . I have not tried the 2/6 build yet. Though I did dirty flash the 2/3 And 2/5 builds. Then when connecting to the car I found every there already
where did you download theese unofficial liquid builds?
erghetto said:
where did you download theese unofficial liquid builds?
Click to expand...
Click to collapse
I loaded the unofficial nightlies from the forum [ROM][Unofficial] LiquidSmooth v3.0 (KitKat4.4.2) TORO This is a great active forum for the Galaxy nexus. The present on on page 1 of that forum is dated 2/6.
The 1/25 version is an official nightly found from the LiquidSmooth G+ community
Thanks for the reply. Every build after 1/18 crashes on me, even the 2/13 I dirty flashed yesterday. Every time I get on my car it connects, then resets. I've tried deleting and repairing my phone, I tried both dirtyv and mpokang kernels. And I've cleaned flashed a couple of builds, but still nothing.
Sent from my Galaxy Nexus using xda app-developers app
Tried a clean flash if the latest build and still no go. Can't seem to figure out why the process keeps crashing. Even a Google search showed little information. Best I could find was this was an issue of some earlier version of 4.4 builds of various roms, but they all say they were fixed around mid January.
Sent from my Galaxy Nexus using xda app-developers app
Just a quick question for everybody! I've been using Liquid Nitro for a while now, but I'm getting a bit frustrated with the occasional spontaneous resets, and how slow it is. What does everyone here use, and what do you think is the best in terms of stability and speed?
Currently I am using sphinx rom. It is snappy ,good on battery, jelly bean. Be sure to apply both patches. I have found the kitkat to be unstable.
Sent from my LG
notzippy said:
Currently I am using sphinx rom. It is snappy ,good on battery, jelly bean. Be sure to apply both patches. I have found the kitkat to be unstable.
Click to expand...
Click to collapse
You have an LG P930, right? is it this one?
i also use liquid nitro, and tried most other jb,kk roms, but always back to liquid for its stable.
the next stable rom for *my* p930 is cm 10.1.3.
Sent from my LG-P930 using xda app-developers app
I used the version in this thread
http://forum.xda-developers.com/showthread.php?t=2294709
Sent from my LG-LU6200
notzippy said:
I used the version in this thread
http://forum.xda-developers.com/showthread.php?t=2294709
Click to expand...
Click to collapse
So it's fast, and works with my p930. Is it stable for you (no random restarts?)
It is better then CM, but it still has random reboots. I did not find the reboots to occur as frequently as CM
Nz
So far, after changing the default language from Russian, I am finding Sphinx to be a lot faster and smoother than liquid nitro, though that might be because I don't have all my apps loaded yet. I also just experienced my first random reset (not even 6 hours! not looking good,) which put my phone into a boot loop (it gets to the lock screen, give a "system UI has crashed" error, and reboots,) that I fixed by pulling the battery.
AND SPEAKING OF THE BATTERY my phone now thinks my battery is at ~ %1-%5 power (it was at about %60 when I installed the ROM,) and is constantly telling me to plug it in, and the phone refuses to charge (it won't charge with any cable or wall adapter I have, and won't even recognize when I plug it into a computer.)
In short: lots of problems, but if I can fix them, I will probably keep sphinx.
*Edit: I just went and wiped everything (including battery information) in CWM and installed the "official unofficial" ROM from the same post. It seems so far to be decent (and it's charging the battery!) It's a bit laggy (like the stock ROM, but not as bad a Liquid Nitro got for me.) Tomorrow I will do the full data wipe again (including the battery info) and re-install sphinx to see if it helps.
In my P930, I use the last PAC-ROM, it gets me stability, battery friendly, smooth, it doest get lagged.
It's fully customizable, I recommend it.
The last version I installed is the nightly of 2014-03-28 or so.
[emoji41]
Send from my SGH-I337M using Tapatalk.
Don't forget to install both patches for sphinx.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 04:30 AM ---------- Previous post was at 04:29 AM ----------
Also you should never need to yank battery, just unplug USB then hold Power down for 20 seconds.
Sent from my Nexus 7 using XDA Premium HD app
I'm looking at the Pac ROM releases, but I'm not sure which one to download (I'm not going to do nightly releases.)
keboose said:
I'm looking at the Pac ROM releases, but I'm not sure which one to download (I'm not going to do nightly releases.)
Click to expand...
Click to collapse
Why dont you try the RC1?
because there are two labeled RC1?
Not the Milestone, but the pac-p930-22.2.0-rc1.zip
Send from my SGH-I337M using Tapatalk.
ultimate_neet said:
Not the Milestone, but the pac-p930-22.2.0-rc1.zip
Click to expand...
Click to collapse
Well, it's going (somewhat) well. With the stable release, I haven't had to restart yet, but there are still problems: mainly that the home button doesn't work. along with that, the "cLock" app keeps crashing, and gapps looks like it wasn't installed properly (no gapps except gmail are there, and it doesn't work.) Did you experience any of this with the nightly build you use?
I made doubly sure I installed the correct gapps zip, could it be I have an old version of CWM that's messing it up? I have CWM v6.0.1.5
Installl the gapps core only.
I didn't have any problems with the clock.
You did full swipe?
Send from my SGH-I337M using Tapatalk.
gapps core? I installed the gapps they linked to in the official thread.
I followed their instructions as well: factory reset, flash ROM, flash gapps, reboot.
Never mind! I installed the nightly you said you use (03/29/2014) and it works! I'm loving kitkat. It's being a bit slow right now, but I'm hoping that's because the phone's been downloading the files for GTA 3 since I installed the ROM (and linked my google account) earlier today.
hey, I don't know what is going on, but I'm not finding any of these ROM's to be stable at all. They seem to work alright at first, but once I get my apps back, it all goes down the tubes. Even the Pac ROM, which so far has been the MOST stable, is frustrating to use. I found that my music player (PowerAmp) causes it to be a bit more unstable, but both it and the default music player often crash 'android.process.media' and then I have to reboot my phone.
Along with that, randomly, and frequently, when I try to wake my phone up from sleeping with the power button, the screen will just go black, the buttons will stop responding, and I have to pull the battery. This one is particularly frustrating because this morning my phone tried to turn on the screen to play an alarm and the phone locked up!
I've wiped my phone again and haven't installed any apps. Let's see if the problems still happen.
keboose said:
hey, I don't know what is going on, but I'm not finding any of these ROM's to be stable at all....
Click to expand...
Click to collapse
I've had this phone since it came out. From my experience, ICS ROM's are the most stable, followed by JB ROMS, then KitKat ROMs. If you want the best stability, battery, and for daily use go with either stock ICS or one that's based on stock. The only problem with that is that you miss out on any of the new improvements in JB and KitKat. For daily use, non of the KitKat ROMs are stable enough. Currently, I'm running CM 10.1.3 with Wind Kernel 2.6. It's not as stable as ICS stock. I get random locks/restarts about once or twice a week. It does however offer the best compromise in stability and features/improvement over just running ICS ROMs. Specwise, this phone was ahead of the curve when it came out. But battery and performance issues kept this from being a good phone. Because it's not well used, there's very little support and development for this phone.