Related
Now that the Nightly Builds are back, figured their should be one thread were all of that is maintained.
First things, first. I take Zero, Nada, Zilch credit for any of these builds. For that we all have Cyanogen and TeamDouche to thank. This thread is merely a place to discuss all things nightly and link to download the Nightly Roms.
This Rom does not include the Google Apps and those you have to flash separately.
As always, Nandroid before installing.
Nightly Builds can be found here:http://mirror.teamdouche.net/?device=crespo
Google Apps here:http://goo-inside.me/gapps/
Status of latest nightly build: http://buildbot.teamdouche.net/builders/cm_crespo_full
Changelog for Nightlies: http://cm-nightlies.appspot.com/?device=crespo
UPDATE: A kang is an unofficial nightly that someone with a spare computer builds from CM's github. It is NOT AN OFFICIAL NIGHTLY AND ONLY THOSE WHO KNOW WHAT THEY ARE DOING SHOULD FLASH THEM.
If anyone's tried this can they please confirm if google "car home" works ?
thank you....
linkisoc said:
If anyone's tried this can they please confirm if google "car home" works ?
thank you....
Click to expand...
Click to collapse
if it works on Android 2.3.1 then it'll work on CM7.
Edit: Installed it and it doesn't appear on apps menu. Market comments also says the same.
Hooray beer!
No wipe needed coming from crackflashers, but I guess that makes sense since they are really the same thing (same should apply to Alpha2/3 from koush).
Itried installing Car Home, it seemed to install OK but it didn't show up in the app drawer. I uninstalled and tried again with the same result.
hey
is there somewhere a list waht is includet or not?
thanks for your Work!
flo
As the OP seem busy, I will add the known bugs and what is still missing
Missing from usual CM features:
* Numeric battery indicator
* Status Bar customisation (colors)
Bugs:
* Some issues with GMail (fix permission or uninstall/reinstall seem to fix)
* Phone reboot during phone call (Known Gingerbread bug)
* Torch is not working.
* Some people report random reboots (Never had one, seem very unusual)
footballpics.info said:
hey
is there somewhere a list waht is includet or not?
thanks for your Work!
flo
Click to expand...
Click to collapse
Thanks, I will add something about the change list in the OP
yeah! nexus s official nightly thread
seems like gaaps have changed since last i flashed on my N1
correct me if im wrong but the GAAPS version universal DPI is what we should be using
what are u think dude Bionix Kernel gonna work? or it's same with
Crackflasher Builds?
Oh yeah, lets get this started.
Just flashed Nightly and Gapps with Rom manager over the Alpha 3 with Gapps and gmail is force closing everytime I use it.
slowz3r said:
seems like gaaps have changed since last i flashed on my N1
correct me if im wrong but the GAAPS version universal DPI is what we should be using
Click to expand...
Click to collapse
Yeah you want the universal DPI one.
avetny said:
what are u think dude Bionix Kernel gonna work? or it's same with
Crackflasher Builds?
Click to expand...
Click to collapse
Unfortunately it doesn't work. It freezes when trying to boot up.
profete162 said:
Just flashed Nightly and Gapps with Rom manager over the Alpha 3 with Gapps and gmail is force closing everytime I use it.
Click to expand...
Click to collapse
clear the app data/cache for the gmail app. in main phone settings, applications, manage applications, all, gmail...
Any idea if Pershoot will start cranking out kernels for the NS?
irishrally said:
Any idea if Pershoot will start cranking out kernels for the NS?
Click to expand...
Click to collapse
Sadly, no. At current, he's only developing for the N1 and G2. I don't think he has the NS and don't think he'll build for a device he can't test for.
jlevy73 said:
Sadly, no. At current, he's only developing for the N1 and G2. I don't think he has the NS and don't think he'll build for a device he can't test for.
Click to expand...
Click to collapse
I've got $5 on it [pershoot's new NS].
Radical
10char
Running this currently... VERY pleased thus far.
hello guys..
so i made my first build of CM9 from sources...
since i have a broken usb, i cannot flash cm9 kernel and test it...
so i request someone to please test and tell me if it works...
rom(v1)
rom(v2) (built this on my newly setup build machine)
kernel
please be informed that i downloaded cyanogenmod's latest source code and compiled from there...
i have made no changes (except the color bug fix)
all the work has been done by cm team, and freexperia team...
i am looking forward to build aokp for x10, so to just make sure that i can build a rom from source, i tried doing this
please report how it goes ??
The kernel looks suspiciously like wifi module. Do I use CM9#121 kernel?
It boots.
TAL333 said:
The kernel looks suspiciously like wifi module. Do I use CM9#121 kernel?
It boots.
Click to expand...
Click to collapse
fixed link now
... i'm sorry
P.S.
really relieved to know that it boots
now i can concentrate on aokp....
was pretty much a major achievement for me to compile a working rom from source... as i have no formal knowledge on programming and all that...
downloading now and will get back with edit after testing
championswimmer said:
fixed link now
... i'm sorry
P.S.
really relieved to know that it boots
now i can concentrate on aokp....
was pretty much a major achievement for me to compile a working rom from source... as i have no formal knowledge on programming and all that...
Click to expand...
Click to collapse
Yes, you did wonderfully well. Truly an Achievement. You should be proud of yourself........ But......
The Camera Doesn't Work......
---------- Post added at 03:22 AM ---------- Previous post was at 03:15 AM ----------
Apollo force closes from menu. Use widget and no more force closes . Every time screen turns off, upon any screen on event it reboots. Sleep issue?
I just set screen timeout to 10 minutes to check things out. Wifi, data, browser, fixing permissions; all work. Also, on screen off, it is not doing a full reboot as apps were upgrading and continued when it rebooted so it didn't lose the data signal. Great Job. Anxiously awaiting your AOKP release.
Going to test it too,i will give feedback after a day of usage.
thanks for your efforts.
@champ,mates
i was unable to use the rom,it was giving me FC's,i was just able to use the settings menu,i tried wiping cache,fixing perms,but nothing,i really want to test this,any suggestions? please.
kalel29 said:
Going to test it too,i will give feedback after a day of usage.
thanks for your efforts.
@champ,mates
i was unable to use the rom,it was giving me FC's,i was just able to use the settings menu,i tried wiping cache,fixing perms,but nothing,i really want to test this,any suggestions? please.
Click to expand...
Click to collapse
it boots fine for me dude...
just that when i close display it reboots... but otherwise its fine
Sent from my X10i using XDA
championswimmer said:
it boots fine for me dude...
just that when i close display it reboots... but otherwise its fine
Sent from my X10i using XDA
Click to expand...
Click to collapse
I just read in CM Discussion Room that FXP CM9#122 reboots every time screen turns off and the colors are still buggy. So, you did a great job of porting. And on yours the colors are fine. So, have you tried doing anything with the Camera files on CM9?
TAL333 said:
I just read in CM Discussion Room that FXP CM9#122 reboots every time screen turns off and the colors are still buggy. So, you did a great job of porting. And on yours the colors are fine. So, have you tried doing anything with the Camera files on CM9?
Click to expand...
Click to collapse
tried building from. sony's source...
the lib that i get works only on stock gb rom, not on cm roms...
the source needs to be worked upon....
maybe fxp can shed more light on it
Sent from my X10i using XDA
championswimmer said:
it boots fine for me dude...
just that when i close display it reboots... but otherwise its fine
Sent from my X10i using XDA
Click to expand...
Click to collapse
yes ,i had that too,it reboot when locking the phone,but i really dont know why i was not able to test an app,i will try later.
and yes in your port,colors are more accurate,and trasnsitions are nice,not too smooth,but they no have lag.
made another build..
want to know if it solves the reboot issue
http://icxperia.com/championswimmer/x10-semc-es209ra/cm_es209ra-ota-eng.championswimmer-2.zip
for me version v2 stuck on bootanimation
championswimmer said:
made another build..
want to know if it solves the reboot issue
http://icxperia.com/championswimmer/x10-semc-es209ra/cm_es209ra-ota-eng.championswimmer-2.zip
Click to expand...
Click to collapse
For me doesnt boot get stuck at cm9 bootanimation too
Put together using PA GApps's structure and updated files from different ROMs, together with factory images.. The install script will show the it'll install pa_gapps-full-4.4-20131126-signed.zip, but, in reality, it will install the new files compatible with 4.4.x The backup script works, but I highly recommend installing GApps at each ROM update, since, sometimes, it just doesn't work very well. I always flash GApps when updating, and I never have issues this way.
You can either wait for the OP of PA GApps to update the package, or use this.
I am not responsible for any damage to the device. Do a backup before, just in case! A boot loop is the worst case scenario that can happen. Didn't happen on my end, and I hope it won't happen to you guys, either.
Enjoy!
UPDATE 12-Dec-2013
Pack updated with 4.4.2 files.
NOT compatible with ART (didn't test, though - might as well work, since the base structure and files from PA's GApps and BaNkS' GApps are ART-compatible; in case you want to test out, do a nandroid first!)
PhotoSphere installs only on hammerhead, manta, mako, razor; no Google Dialer
Link #1
PhotoSphere and GDialer for all devices (Might cause errors, two dialers & two cameras, beware! It's a forced method, by including both the dialer and camera in /system/app and /system/priv-app)
Link #1
GApps mini modular package
Link #1
Credits go to BaNkS for letting me use files from his GApps.
Credits go to hanschke for testing out.
Credits go to TKruzze for the structure of GApps.
Looks like when this was inside PA thread, there were a lot of questions, but in separate thread, everthing is clear, and no problems or questions reported so far :thumbup:
Sent from my Nexus 4 using Tapatalk
This is exactly what I'm looking for. Thank you so much! ^_^
Are you going to continue this if ever there will be an update?
Dan1234567890 said:
Looks like when this was inside PA thread, there were a lot of questions, but in separate thread, everthing is clear, and no problems or questions reported so far :thumbup:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Weird, indeed, hah. Maybe some users are not interested in this package.
aini12aian said:
This is exactly what I'm looking for. Thank you so much! ^_^
Are you going to continue this if ever there will be an update?
Click to expand...
Click to collapse
Maybe. I'd like to push updates as fast as I can, since I am also using this GApps.
Working on nexus s with latest CM11. Thanks!
Flashed this with KITKANG 4.4.1 and I get constant force closes on the dialer and it also says I have no sim card.. Man I really want that google dialer so I'm not giving up just yet..
Intellectua1 said:
Flashed this with KITKANG 4.4.1 and I get constant force closes on the dialer and it also says I have no sim card.. Man I really want that google dialer so I'm not giving up just yet..
Click to expand...
Click to collapse
From what I know, not even the official PA Gapps works well with CM. By the way, what kernel are you using? Do you know about the CAF business on CM?
Intellectua1 said:
Flashed this with KITKANG 4.4.1 and I get constant force closes on the dialer and it also says I have no sim card.. Man I really want that google dialer so I'm not giving up just yet..
Click to expand...
Click to collapse
Kaydin said:
From what I know, not even the official PA Gapps works well with CM. By the way, what kernel are you using? Do you know about the CAF business on CM?
Click to expand...
Click to collapse
I'm on CM and haven't had one force close. I'm also not using ART.
Only problem is when I flash a nightly the photosphere camera and the google dialer are gone. Guess I'm gonna have to flash gapps every time like the old days (instead of crying like a baby about it)
Kaydin said:
From what I know, not even the official PA Gapps works well with CM. By the way, what kernel are you using? Do you know about the CAF business on CM?
Click to expand...
Click to collapse
I don't think it's true... I had no problems running the PA GAPPS on CM 11 nightlies, including a working photosphere camera.
Different kernels on CM 11 are trickier, because of the CAF issues you mentioned, but as far as I know the GAPPS work just fine.
I flashed these gapps on slimkat and everything is running great.
Thanks.
Sent from my Nexus 4
anshumandash said:
I flashed these gapps on slimkat and everything is running great.
Thanks.
Sent from my Nexus 4
Click to expand...
Click to collapse
Same here only I'm on the 12-7 cm nightly.. Working most excellent thanks a bunch kaydin!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
---------- Post added at 03:21 AM ---------- Previous post was at 03:19 AM ----------
Kaydin said:
From what I know, not even the official PA Gapps works well with CM. By the way, what kernel are you using? Do you know about the CAF business on CM?
Click to expand...
Click to collapse
Everything works except the Google dialer.. Just doesn't flash no biggie cause I like the aosp dialer anyway. But I can confirm full functionality with cm11 4.4.1
Sent from my Nexus 5 using XDA Premium 4 mobile app
cjwaggsrx8 said:
Same here only I'm on the 12-7 cm nightly.. Working most excellent thanks a bunch kaydin!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
---------- Post added at 03:21 AM ---------- Previous post was at 03:19 AM ----------
Everything works except the Google dialer.. Just doesn't flash no biggie cause I like the aosp dialer anyway. But I can confirm full functionality with cm11 4.4.1
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which gapps should I flash if I'm on purity 4.4.1 hammerhead? Thanks
Sent from my Candy Painted Nexus 5
Click here for my NFL Lockrings and other mods
Guys, i have issues with this package, i constantly get the error message "Unfortunately, com.android.phone has stopped" how do i fix this issue?
Xxderek0822xx said:
Which gapps should I flash if I'm on purity 4.4.1 hammerhead? Thanks
Sent from my Candy Painted Nexus 5
Click here for my NFL Lockrings and other mods
Click to expand...
Click to collapse
You can flash any version, depending on your needs. I go for the first version (PhotoSphere installs only on hammerhead, manta, mako, razor; no Google Dialer), though. I don't need the Google Dialer, but I do need PhotoSphere, and, on my Nexus 5, it will install automatically.
jameseytickner said:
Guys, i have issues with this package, i constantly get the error message "Unfortunately, com.android.phone has stopped" how do i fix this issue?
Click to expand...
Click to collapse
What ROM and kernel are you using?
paychex said:
I'm on CM and haven't had one force close. I'm also not using ART.
Only problem is when I flash a nightly the photosphere camera and the google dialer are gone. Guess I'm gonna have to flash gapps every time like the old days (instead of crying like a baby about it)
Click to expand...
Click to collapse
Great to hear it's running great! Well, I always flash GApps when I install a new nightly on Omni. It's just another few taps.
goldenratio said:
I don't think it's true... I had no problems running the PA GAPPS on CM 11 nightlies, including a working photosphere camera.
Different kernels on CM 11 are trickier, because of the CAF issues you mentioned, but as far as I know the GAPPS work just fine.
Click to expand...
Click to collapse
Oh, I might have read wrong that PA GApps doesn't work on CM11 nightlies. Good to hear they actually do work.
My phone doesn't support photosphere because lacks of hardware. Which gapps that's doesn't have photosphere that support my device? Thanks
muhammadnajmi96 said:
My phone doesn't support photosphere because lacks of hardware. Which gapps that's doesn't have photosphere that support my device? Thanks
Click to expand...
Click to collapse
PhotoSphere installs only on hammerhead, manta, mako, razor; no Google Dialer. This will only install PhotoSphere camera on hammerhead, manta, mako, razor, and it won't include Google Dialer.
Also, for all of you, you are all welcome.
Kaydin said:
You can flash any version, depending on your needs. I go for the first version (PhotoSphere installs only on hammerhead, manta, mako, razor; no Google Dialer), though. I don't need the Google Dialer, but I do need PhotoSphere, and, on my Nexus 5, it will install automatically.
What ROM and kernel are you using?
Great to hear it's running great! Well, I always flash GApps when I install a new nightly on Omni. It's just another few taps.
Oh, I might have read wrong that PA GApps doesn't work on CM11 nightlies. Good to hear they actually do work.
Click to expand...
Click to collapse
Im using the CM11 LG G2 D802 Nightly, with stock kernel
Woks fine with omniRom 4.4.1 release nightly (homemade), here.
I'm impatient and pagapps 11/26 was NOT playing well with others causing force closes, rail especially with ART.
I wiped system, cache and dalvik (kept data), flashed omni v2 of yr apps (i have m7ul) and supersu, flashed omni and it stopped my apps fc's (yay!) only thing is it gave me a second camera and gallery (i thought gallery is gone on 4.4.1) but I just fixed my nova homescreen and so far so good.
I'll report any issues should arise. Thank you, for the quick fix, it.can.make testing a pain, and also for understanding that flashaholism is a real-life disease (thats not a noob asking for an ETA, it's his addiction talking ):silly:
Are you going to update your gapps to 4.4.2? (if there are any changes)
DaringDomino3s said:
Woks fine with omniRom 4.4.1 release nightly (homemade), here.
I'm impatient and pagapps 11/26 was NOT playing well with others causing force closes, rail especially with ART.
I wiped system, cache and dalvik (kept data), flashed omni v2 of yr apps (i have m7ul) and supersu, flashed omni and it stopped my apps fc's (yay!) only thing is it gave me a second camera and gallery (i thought gallery is gone on 4.4.1) but I just fixed my nova homescreen and so far so good.
I'll report any issues should arise. Thank you, for the quick fix, it.can.make testing a pain, and also for understanding that flashaholism is a real-life disease (thats not a noob asking for an ETA, it's his addiction talking ):silly:
Click to expand...
Click to collapse
You probably installed "PhotoSphere & Google Dialer included for all devices".
Thank you for reporting! And yes, indeed, flashaholism is a real-life disease. That's why I built this package. Couldn't wait for the factory images to get released, haha!
totom96 said:
Are you going to update your gapps to 4.4.2? (if there are any changes)
Click to expand...
Click to collapse
Yeah, I will update the package today.
It's been requested that I create a new thread for this so as not to clog up @milaq's thread.
As some of you may have seen in flintman's Evervolv and milaq's CM threads, there has been a lot of work on the 3.4 kernel for tenderloin. Its a pretty awesome feat to have this running on our good ol tenderloin. =)
The gratitude for this kernel and build needs to be given to almost anyone but me. (Flemmard, flintman, jcsullins, Dorregaray and everyone that came before me on this device (dalingrin, green, and other's I'm sure that I'm missing)). I've had my tenderloin for quite awhile but never really done much with it until recently.
Anyway, without further ado, I present to you nightlies of CM-11.0 for tenderloin with a 3.4 kernel and -caf based HALs. Basically what this means is we'll be running the latest code from codeaurora on our msm8660 tenderloin.
THERE WILL BE BUGS! This thing is not perfect. It is still in active development.
CURRENT BUGZ (in no particular order):
- Bluetooth steals battery, but DOES work (jcsullins) - also sixaxis app doesn't work =(
- Camera is a bit derpy still, major wip, it takes pictures though (Dorregaray)
- Other stuff? Probably, yea
Destructions: PLEASE READ
1. This is a /data/media rom (relevant). What that means is you should be partitioned with a very small 'media' partition and a very large 'data' partition. The benefit of this is that your /sdcard and /data partitions share the big chunk of your usable space, just like any newer phone does these days. Use TPToolbox to achieve the new partition scheme: http://forum.xda-developers.com/showthread.php?t=2756314
2. You'll need a recovery that has both /data/media support and selinux support. Any of the following will work. Flashable via recovery.
-PhilZ Clockworkmod 6.0.4.7 (non-touch)(will backup and restore in both cwm and twrp format)
-Milaq's ClockworkMod 6.0.5.4
-Flintman's TWRP
3. Now you're ready to flash the rom. Downloads here: http://www.invisiblek.org/roms/cm-11.0/tenderloin/
4. Gapps here: http://wiki.cyanogenmod.org/w/Google_Apps
I'd recommend wiping data when coming to this rom or going to a different one (going between milaq's and this should be fine).
These are automatically built on my personal server at home and then uploaded. There may or may not be issues during the build times so don't always expect a fresh build every day. You can follow the automated twitter account here which will spit out a tweet once the build is finished uploading.
Sources:
-Kernel
-Device Tree
-CM Sources (the rest of what's needed)
There are a couple more changes and a couple other repos that are required to build this. Add this stuff to your .repo/local_manifests/roomservice.xml in order to build this yourself (after syncing the cm source of course)
http://pastebin.com/jKAMWM8T
You'll also need to cherry pick this commit from jcsullins: http://review.cyanogenmod.org/#/c/54380
Feel free to fork and fix!
Again -
Thanks to everyone that has contributed to making this rom.
Flemmard, flintman, jcsullins, dalingrin, green, milaq, the entire CM team and I'm sure many others.
Good new year present.
Looking forward to when Bluetooth is working. That and the black boxes were the only thing keeping me off KitKat.
Sent from my TouchPad using XDA Premium 4 mobile app
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
k4ever said:
invisiblek, I used your 20131226 ROM. It kept crashing and rebooting every time I played a video. Netflix would crash immediately on loading and reboot the tablet. Has this been fixed with your 20131231 build?
Sent from my Touchpad using Tapatalk
---------- Post added at 08:53 PM ---------- Previous post was at 08:39 PM ----------
I almost forgot… I also had major issues with apps not installing or disappearing after a reboot.
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
vinukondamahesh said:
i am trying to move uImage.ClockworkMod after rename the file its asking file already exit ,should we need to replace ?
i tried to keep both but it never successful...
is there any way to intall from zip file like upgrading recovery
Click to expand...
Click to collapse
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
k4ever said:
allstar319, what about the disappearing apps? Has that been fixed?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
No clue. I heard of apps disappearing from the Google Home Launcher, but not getting completely removed or preventing apps from being installed. Is that the launcher you're using? Only remedy I heard from that (Milaq's CM11 thread, somewhere around page 40) was to just readd them from the app drawer.
Best advice is to wait for todays build to get uploaded and see what happens.
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
allstar319 said:
I believe Flint said video playback was still a bit broke around that date. I remember loading that build and Diceplayer would crash upon playing a video, but it would only crash back to the home screen (not entirely crash and reboot). I think Flint said he fixed it earlier, so try 20140101 when it comes out.
Replace it so you can use the new CWM to flash this build. I believe /boot is limited to 30mb so trying to keep both may not work.
Click to expand...
Click to collapse
thank you its working nw
milaq actually has a flashable zip in his thread. that is the easiest. i was on 4.3 went into that recovery, made a backup then flashed the new cwm, rebooted recovery did a full wipe and flashed the rom and gapps and i am up and running. who would have ever thought we would have kitkat on a touchpad. not to mention a 3.x kernel. unreal, thanks for everyones work. Happy New Year
jerryatherton said:
2. You'll need a recovery that has both /data/media support and selinux support. This clockworkmod will do the trick: http://invisiblek.org/tenderloin/openrecovery-twrp-2.6.3.0-tenderloin-selinux.img (thanks @milaq)
Push it to /boot/uImage.ClockworkMod
Great ROM far, I loaded the recovery but i named it TWRP instead because it says TWRP in the file name. It ran as TWRP . Is the above just a typo or can I call it either one?
Sent from my Touchpad using XDA Premium HD
Click to expand...
Click to collapse
Oops, I had the wrong image there. Link updated with the cwm =P
EDIT: Also added a flashable zip for it, had trouble downloading milaq's so I made my own =/
Anyone else getting a Core Process failure message when booting to the 01012014 Build?
I went back to the 12312013 build and all appears to be back to normal.
To be clear, I went straight to this build from a fresh CM9 image without booting into Android - ever. Got a second-hand device back from a relative, and pushed it to CM11, so it may have been a result of my own process.
I'll reflash 01012014 and see if the error persists.
--McBean
Really looking forwards to a stable version of this to try. Thanks for the effort.
BillzillaAus said:
Really looking forwards to a stable version of this to try. Thanks for the effort.
Click to expand...
Click to collapse
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
k4ever said:
So am I. Right now I'm using invisiblek's CM 10.2 ROM. It's stable (although a little slow). I don't want to jump to CM 11 again until it is a lot more stable.
BTW, can someone point me to a thread that discusses that benefits of the 3.4 kernel on the Touchpad?
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
allstar319 said:
IIRC, a long time ago, someone mentioned that there were some benefits of Jelly Bean that we couldn't use because of the version of our kernel we were using. I would assume the same still applies today if that was the case. Also, with CM11, black boxes are present in many apps that prove them to be unusable. The default browser is unusable on CM11 with the old kernel, so you'd have to either use Chrome, or wait for a new kernel. I'm sure there are some performance enhancements as well.
On todays build, video playback still seems to crash to the home screen with Diceplayer (I could of swore Flint said he fixed that in his build at least). I haven't tested Milaq's test build of the 3.0 kernel to see if that's the same case over there.
Click to expand...
Click to collapse
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Click to expand...
Click to collapse
Also, the old kernel was preventing us from having "official" CM builds.
Getting SoD's once I turn the screen off. Tried the old way to fix that by raising the min clock, but that didn't seem to help. Any ideas?
k4ever said:
Thanks for the quick reply. Bummer!
Sent from my Touchpad using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:48 PM ----------
One more question for invisiblek, will you be making any updates/improvements to CM10.2 or has all development shifted to CM11? The last 10.2 ROM was on 20131209. I'm having issues with the camera not working..
Sent from my Touchpad using Tapatalk
Click to expand...
Click to collapse
The 3.4 kernel, minimally, resolves an issues with the other CM11 builds where the core/stock apps were experiencing "black boxes" which prevented users from reading mail, using the browser to navigate and some other issues. Right off the bat, the new kernel resolves that issue.
--McBean
They just released CyanogenMod 11.0 M6. However it really is the "Stable" C11.0 since they stopped calling "Stable" Releases "Stable". Now there are just the Milestone Releases every 2-4 weeks.
Read all about it: http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m6-release
Here you can download the newest Stable (a.k.a. M6): http://download.cyanogenmod.org/?type=snapshot&device=ovation
Please post in this thread what works and what does not.
Cheers,
sb
I'm running the M4 right now.
Just install M6 via cwm recovery? Or do I need to do anything specific?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
---------- Post added at 08:24 AM ---------- Previous post was at 08:15 AM ----------
Also is ART working in this?
__________________
Sent from my LIFE PLAY using Tapatalk Pro.
Yes and yes.
Installed CM11 M6
I just installed the M6. Everything was running great until I had to plug in the charger. Now I am also getting the screen flicker. I did not clear the caches and I am using ART. As for ART I have not noticed that it is any faster than dalvik. I will probably switch back to test.
extrem0 said:
Yes and yes.
Click to expand...
Click to collapse
Yes and yes what? Please more details?!
Automan4966 said:
I just installed the M6. Everything was running great until I had to plug in the charger. Now I am also getting the screen flicker. I did not clear the caches and I am using ART. As for ART I have not noticed that it is any faster than dalvik. I will probably switch back to test.
Click to expand...
Click to collapse
Which method did you use for flashing? Link please
CM11 M6
sirbender42 said:
Which method did you use for flashing? Link please
Click to expand...
Click to collapse
I had a working CM10.2 so I downloaded the cwm-recovery-ovation-6.zip from the first post in the EMMC CM11 Install - updated 1/18 thread in the developers forum to my Nooks download folder. Then I downloaded the M6 snapshot from the get ovation builds link on the same page to my downloads folder. Finally I got the latest Google apps signed zip. All 3 downloaded to my Nook downloads folder. I then booted the Nook with a cwm that I had from installing 10.2 and flashed the newer cwm-recovery-ovation-6.zip to my internal emmc memory. Rebooted into the new recovery and flashed the cm11 m6 to internal emmc. Then flashed the google apps rebooted from recovery to cm11.
EMMC C11 Install - updated 1/18 thread http://forum.xda-developers.com/showthread.php?t=2600572
Latest Google apps http://www.google.com/url?sa=t&rct=...T134JI&usg=AFQjCNF5-cVMwChR1F7kICnKoFUjZ83OWg
I followed the For upgrades from CM10.x basic instructions on that page.
I find that the M builds aren't all that stable, even though they are considered to be. I haven't tried on a Nook yet, but on the Galaxy Nexus, the latest M6 constantly freezes my default launcher (Trebuchet) and I'm not the only one with this problem either (there are more similar cases on the CyanogenMod forum.)
HiddenG said:
I find that the M builds aren't all that stable, even though they are considered to be. I haven't tried on a Nook yet, but on the Galaxy Nexus, the latest M6 constantly freezes my default launcher (Trebuchet) and I'm not the only one with this problem either (there are more similar cases on the CyanogenMod forum.)
Click to expand...
Click to collapse
Well, the Nook HD+ has a fairly reproducible bug. About 30% of the time I swipe down the notification bar it crashes the currently running app and freezes the screen (black screen). After about 10 sec. you are back on the homescreen.
Strange that this wasn't catched in the most basic stability tests.
This bug even appears without pulling down the notification area. Sometimes the screen just turns black and freezes for 10 sec. After that you are back on the home screen. Very annoying. Luckily this doesn't happen very often. Unluckily it is very difficult to reproduce...and thus to fix I assume.
Alternative?
sirbender42 said:
Well, the Nook HD+ has a fairly reproducible bug. About 30% of the time I swipe down the notification bar it crashes the currently running app and freezes the screen (black screen). After about 10 sec. you are back on the homescreen.
This bug even appears without pulling down the notification area. Sometimes the screen just turns black and freezes for 10 sec. After that you are back on the home screen..
Click to expand...
Click to collapse
I've got the bug too...
Is there any KitKat ROM for the Nook HD+ that's stable? and does not have these "hiccups"? I'm getting no touch sensitivity during these lock screen resets, and have to restart via the physical button.
Well I have using the M4 build, and apart from a some rare crashes, it has been rock solid.
I think I will stick with for now, and not risk getting the bugs that you guys are reporting in M6. Also, I have it set up just right for my needs and would hate to start from scratch if I install to M6.
Palmahnic said:
I've got the bug too...
Is there any KitKat ROM for the Nook HD+ that's stable? and does not have these "hiccups"? I'm getting no touch sensitivity during these lock screen resets, and have to restart via the physical button.
Click to expand...
Click to collapse
Strange. I can always use the tablet after the hiccup just as before.
I would suggest you install the latest nightly. Since the bug is so obvious, they probably have already fixed it.
sirbender42 said:
Strange. I can always use the tablet after the hiccup just as before.
I would suggest you install the latest nightly. Since the bug is so obvious, they probably have already fixed it.
Click to expand...
Click to collapse
Not yet
Darrian said:
Not yet
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/63867/
In the next nightly this will be fixed (assuming this is the bug we have).
Update: Here is the Ovation Nightly Changelog: http://www.cmxlog.com/11/ovation
A couple of Cyanogenmod bug reports related to this issue have new comments saying that the problem is no longer happening.
https://jira.cyanogenmod.org/browse/CYAN-4047
https://jira.cyanogenmod.org/browse/CYAN-4091
I haven't tested it yet.
Hey guys, why do you think there are no nightlies for ovation anymore?
lerkin said:
Hey guys, why do you think there are no nightlies for ovation anymore?
Click to expand...
Click to collapse
The answer is in the CM11 thread. One of the users there reported there was some kind of glitch in the building process.
Sent from my BN NookHD+ using XDA Premium HD app
I put M6 on my HD for a while. I really missed all the Trebuchet tweaks that are available with 10.1 and 10.2 so I went back to 10.2.1 for now.
Sent from my BN Nook HD using XDA Free mobile app