Database Users

[Q] Instructions on HowTo Port existing ROM?

Hello!
Since there is a fully working CM7 for Bravo (thanks Quarkx), does anyone know how can I port an existing ROM from Defy (example: WhiteRabbit 1.3 which is based on CM7)?
Anyways, here is the link of TweetyPeety's ROM: WhiteRabbit 1.3
http://forum.xda-developers.com/showthread.php?t=1510063
Thanks!

When I port Defy roms, I start by replacing the radio files with the ones that BravoMotorola posted in an earlier thread, adding in Quarx's camera libraries, editing media_profiles.xml, and editing the build.prop. There are a few apps included with some Defy roms, like Torch and Rom Updater, that are completely incompatible with the Bravo, and they need to be removed (or never used...).
I've attached a CWM compatible zip that removes the Defy radio, Defy camera libraries, Torch, Rom Updater, media_profiles.xml, and build.prop and replaces them with BravoMotorola's radio, Quarx's camera libraries, updated media_profiles.xml, and a CM72 compatible build.prop. I've tested this with various Quarx, Epsylon3, and Maniac103 CM7 nightlies and always had success.
If you want to use this for other Defy roms (not CM7 based) either remove or edit the build.prop accordingly and check\modify the updater-script to ensure it's compatible with the rom you want to use. By modify the updater-script, I mean to either add or remove apk's or libraries your custom rom may or may not have.
The libraries included are for Gingerbread roms and won't work on Froyo or ICS. Don't bother trying cause you'll bootloop at best, flash the sbf at worst. If anyone is interested, I can make a similar patch for Froyo roms, and an ICS patch for radio and apn settings. And don't bother asking about ICS camera, I've tried many, many, many library combos and no camera or bootloop. Your best bet on ICS camera is to donate to Quarx.
Install the included zip AFTER installing your rom.
Good luck on your Defy rom porting.

Newbery ryViewse
I've been using the White Rabbit 1.3 rom for the past 6 hours or so and have really been enjoying it. It does have a few issues though. The apn settings for att are incorrect so it won't connect (same as CM9) and I can't get usb tethering to work at all. At first, the phone recognizes usb as being connected, then when you enable, it instantly disables and the phone will bootloop every 5 minutes or so. Not really bootloop, but it does reset to the boot screen. It really sucks because this is a good rom I'd like to use but usb tethering is a must for me. Other than the tethering issue, this seemed to be stable rom and its worth trying it out.
I've included a patch to fix the camera, apn problems, and an edited build.prop. Install the rom as usuall, reboot to change to 2nd_boot, go to recovery and install the bravopatch-whiterabbit1.3.zip.
Does anybody know which program controls usb tethering? I suspect usb.apk but I'm not sure. Since I haven't had any problems whatsoever with Epsylon3's 20120212 nightly, I'll try using it's usb.apk and hope it works.
I tried upb.apk and usbd from 20120212 with no success, but it did stop the bootloop issue. I also noticed that this rom was based on KANG 20.02. I've never used or ported a KANG rom, so maybe the tethering issue is kang specific? I'll flash a kang rom tomorrow to check.

full
skeevy420 said:
I've been using the White Rabbit 1.3 rom for the past 6 hours or so and have really been enjoying it. It does have a few issues though. The apn settings for att are incorrect so it won't connect (same as CM9) and I can't get usb tethering to work at all. At first, the phone recognizes usb as being connected, then when you enable, it instantly disables and the phone will bootloop every 5 minutes or so. Not really bootloop, but it does reset to the boot screen. It really sucks because this is a good rom I'd like to use but usb tethering is a must for me. Other than the tethering issue, this seemed to be stable rom and its worth trying it out.
I've included a patch to fix the camera, apn problems, and an edited build.prop. Install the rom as usuall, reboot to change to 2nd_boot, go to recovery and install the bravopatch-whiterabbit1.3.zip.
Does anybody know which program controls usb tethering? I suspect usb.apk but I'm not sure. Since I haven't had any problems whatsoever with Epsylon3's 20120212 nightly, I'll try using it's usb.apk and hope it works.
I tried upb.apk and usbd from 20120212 with no success, but it did stop the bootloop issue. I also noticed that this rom was based on KANG 20.02. I've never used or ported a KANG rom, so maybe the tethering issue is kang specific? I'll flash a kang rom tomorrow to check.
Click to expand...
Click to collapse
work full..

Edit
3g and Usb Tethering don't work. My apologies on that. I only use wifi and 3g only when necessary. Data plans suck. Calls work with good signal, not sure about texting, don't really text much.
It's fully working if you don't require usb tethering . The touchscreen in the installer is sometimes unresponsive when pressing the next and previous buttons, but the menu key works as next and back as back. No other issues with the installer. While it may have been wifi and running a lot of crap in a short time as a basic stress test, I thought the battery drained faster than usual.
The rom is worth checking out. I really like its theme and set up more than anything.

Just tried your patch, yet it I get the bad zip, and aborts... any ideas?
Sent from my MB525 using XDA

ianstump said:
Just tried your patch, yet it I get the bad zip, and aborts... any ideas?
Sent from my MB525 using XDA
Click to expand...
Click to collapse
After typing all of the below, I realized I for got to ask--Did you enable signature verification by accident or have a bad download? I've been using the cm72 patch since the day Quarx released a proper bravo rom and haven't ever had a bad zip error, and the white rabbit patch is identical to the cm72 patch other than the build.prop and apns-conf.xml. I'm not sure if it matters, but I've only used the wr patch with the recovery from epyslon3's latest cm72 nightly 0212.
If its the patch for white rabbit, remove the build.prop from the patch and remove the line
"/system/build.prop"); from /META-INF/com/google/android/updater-script. We probably had conflicting installer options. Once you reboot after updating both zips, make sure to boot into 2nd boot like the installer says...although 2nd init booted it up just fine after the initial post-install bootloop last night for me.
You'll also need to edit the build.prop for the camera and device settings with the ones I included. You also need to make sure do delete strings for flash under OLD Tags as well.
I have a habit of editing the build.prop manually before flashing a new rom, and the one in the patch was also the build.prop in the white rabbit rom, both times I installed it.
#///////////////////////////////////////////////
#OLD Tags///////////////////////////////////////
ro.media.capture.maxres=3m
ro.media.capture.classification=classA
ro.workaround.noautofocus=0
#///////////////////////////////////////////////
#[Product Tags]/////////////////////////////////
ro.product.model=MB520
ro.product.brand=MOTO
ro.product.name=MB520_KOBE
ro.product.device=umts_kobe
ro.product.board=kobe
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=omap3
#///////////////////////////////////////////////
#[Build Tags]///////////////////////////////////
ro.build.product=umts_kobe
ro.build.description=umts_kobe_emara-user 2.3.4 4.5.1-134_DFP-74 1313117579 release-keys
ro.build.fingerprint=MOTO/MB520_KOBE/umts_kobe:2.3.4/4.5.1-134_DFP-74/1313117579:user/release-keys
ro.cm.device=kobe

Tried out latest KANG cherry pick today and its usb tethering works, 3g doesn't however. Tried multiple basebands and replacing radio with no luck. The att apn wasn't correct, and fixing didn't help.
Also, the 3g on White Rabbit doesn't work either. Anybody here port a defy cm7 after 0212? Other than these two I really haven't, and I'm wondering if newer defy cm7's are bravo incompatible, glithcy, or just that the KANG cherry picks don't like us.
I've also since downloaded the White Rabbit patch from here and didn't get any zip errors. Here's how I installed if anybody's interested:
reboot recovery
select WhiteRabbitEdition-1.3.zip
English
Install Type->Custom
Rom Options->Full Wipe, Moto Defy MB525, Google Apps, ICS Standard
Tweaks Options->AGPS Version, CM7 Stock, Off, Gingerbread, Standard
Style Options->ExDialer, ADW Launcher, CM7 DSP Manager
No other changes
Exit Installer
apply bravopatch-whiterabbit1.3.zip
reboot to bootmenu
set 2nd_boot to default
reboot to bootloop
remove and insert battery
power on
enjoy

I just realized I downloaded it wrong. Working great! Thanks!
Sent from my MB520 using XDA

Does usb tethering and 3g work? I never had them working with White Rabbit. To be specific, does turning on wifi then using usb tethering work. I use my phone as a wireless nic instead of running an ethernet cable through the house to my linux box. Kinda hard to update debian with no internet.

Ugh miui Pikachu edition works before I try to make camera work then just bootloops... Darn it's such a good rom!
Sent from my MB520 using XDA App

How were you trying to make the camera work?
I've also heard good things about that rom, just haven't bothered trying it yet.
Also, the latest quarx cm7 nightly is pretty stable. Using it now... my earlier cm7 patch works, but a new line in build.prop is needed and the apn-conf.xml from the white rabbit patch is required unless you like setting up the apn each time. Actually, I've had to change\fix the apn-conf.xml for every cm7 nightly after epsylon3's feb 12 nightly. epsylon3's feb 12 nightly is a real good rom to use if you want a good defy rom to use. I used it as my primary rom till quarx's latest 7 and I'm switching to epsylon's tomorrow.
add to build.prop under #Default Network Type
ro.telephony.ril_class=motow3g

skeevy420 said:
How were you trying to make the camera work?
I've also heard good things about that rom, just haven't bothered trying it yet.
Also, the latest quarx cm7 nightly is pretty stable. Using it now... my earlier cm7 patch works, but a new line in build.prop is needed and the apn-conf.xml from the white rabbit patch is required unless you like setting up the apn each time. Actually, I've had to change\fix the apn-conf.xml for every cm7 nightly after epsylon3's feb 12 nightly. epsylon3's feb 12 nightly is a real good rom to use if you want a good defy rom to use. I used it as my primary rom till quarx's latest 7 and I'm switching to epsylon's tomorrow.
add to build.prop under #Default Network Type
ro.telephony.ril_class=motow3g
Click to expand...
Click to collapse
I tried using the CM7 patch that was posted earlier in the thread and it made it stuck at the M logo
Sent from my MB520 using XDA App

That's the problem, that patch was made for cm7 only.
The steps to PORT CAMERA ONLY to any GB ROM.
Does not work with MS2Ginger2.1
Do everything preflash.
Open WhateverRomForDefy.zip in Archive Manager
Under system/etc, delete cameraCalFileDef5m.bin & cameraCalFileDef8m.bin, and replace mot_ise_imager_cfg.bin & media_profiles.xml from cm7 patch
Under system/lib, replace libcamera.so, libcamera_client.so, & libcameraservice.so with the same from cm7 patch.
Edit build.prop for camera like in post 7 under the OLD Tags. While the post is for WR, the camera changes are the same, & all changes are almost at bottom of build.prop. If you can read, you'll see them....
If the above doesn't work, whatever rom your trying is either
That's how I port roms normally. Again this is bare minimum camera. If that doesn't work, you\we're up the that creek with that rom in regards to the camera. FYI, I do all my rom edits with Archive Manager and GEdit\JEdit on Debian Linux. I'm not sure of the Windows alternative (7zip and Notepad++ I'd imagine) cause I haven't used Windows for anything more than SuperOneClick and other Win exclusive\non-wineable apps since XP was released....Win2K was awesome, I miss it.

skeevy420 said:
That's the problem, that patch was made for cm7 only.
The steps to PORT CAMERA ONLY to any GB ROM.
Do everything preflash.
Open WhateverRomForDefy.zip in Archive Manager
Under system/etc, delete cameraCalFileDef5m.bin & cameraCalFileDef8m.bin, and replace mot_ise_imager_cfg.bin & media_profiles.xml from cm7 patch
Under system/lib, replace libcamera.so, libcamera_client.so, & libcameraservice.so with the same from cm7 patch.
Edit build.prop for camera like in post 7 under the OLD Tags. While the post is for WR, the camera changes are the same, & all changes are almost at bottom of build.prop. If you can read, you'll see them....
If the above doesn't work, whatever rom your trying is either
That's how I port roms normally. Again this is bare minimum camera. If that doesn't work, you\we're up the that creek with that rom in regards to the camera. FYI, I do all my rom edits with Archive Manager and GEdit\JEdit on Debian Linux. I'm not sure of the Windows alternative (7zip and Notepad++ I'd imagine) cause I haven't used Windows for anything more than SuperOneClick and other Win exclusive\non-wineable apps since XP was released....Win2K was awesome, I miss it.
Click to expand...
Click to collapse
Thanks man. I will try later.
Sent from my MB520 using XDA App

Any luck? I have some free time today and can make a pikachu patch if necessary. Currently I'm trying out Idiot to port the WR framework over to Epsy's latest nightly.
Why are most of the cool Droid tools windows/dos based? You'd think there'd be more Linux tools for modding a Linux-based os.

skeevy420 said:
Any luck? I have some free time today and can make a pikachu patch if necessary. Currently I'm trying out Idiot to port the WR framework over to Epsy's latest nightly.
Why are most of the cool Droid tools windows/dos based? You'd think there'd be more Linux tools for modding a Linux-based os.
Click to expand...
Click to collapse
If you want you can me a pikachu patch. I won't have time today to try it out
Sent from my MB520 using XDA App

Got busy with MSGinger today.....I'll have a patch up sometime tomorrow.

marquae11 said:
If you want you can me a pikachu patch. I won't have time today to try it out
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
Here ya go. Got busy with real life the past few days. This isn't flashable, but isn't hard to do either.
Instructions:
Open PikachuEdition2.3.2b.zip
Delete boot.img and devtree.img
Replace files under /system with the ones provided
Make sure to delete the *.jordan.so's under /system/lib/hw
Replace updater-script @ /META-INF/com/google/android/updater-script
When Installing:
Install as Defy
Don't use any Defy+ options or settings, some of them change files we just replaced.

Thanks man! You are helping us alot!

initrd.gz problems

I am at a loss here. I am running CLK 1.5 PA 1.1a with tytung r3, however, the device gets icon flash similar to icecreamtosti, where the icons do not respond without a reboot.
I wanted to flash Dorimanx v6.9 or v7.2 HWA, and understand I need to place the ROMs initrd.gz file in the initrd-custom folder. I have tried this on Snow Leopard & XP to no avail using a variety of different compression programs including 7-zip. I unzip the kernel and the ROM, put the PA 1.1a initrd.gz in the correct folder and rezip it. Each time though, even after re-downloading the kernel and ROM, I get an error within CWM, which reads that the installation has been aborted. Why is this? Do I need to re-compile the kernel in Android Kitchen? (I do not know how to do this by the way) or what else am I doing incorrectly? I have trawled the XDA HD2 forum, but had no luck. Suggestions?

aldersonalex said:
I am at a loss here. I am running CLK 1.5 PA 1.1a with tytung r3, however, the device gets icon flash similar to icecreamtosti, where the icons do not respond without a reboot.
I wanted to flash Dorimanx v6.9 or v7.2 HWA, and understand I need to place the ROMs initrd.gz file in the initrd-custom folder. I have tried this on Snow Leopard & XP to no avail using a variety of different compression programs including 7-zip. I unzip the kernel and the ROM, put the PA 1.1a initrd.gz in the correct folder and rezip it. Each time though, even after re-downloading the kernel and ROM, I get an error within CWM, which reads that the installation has been aborted. Why is this? Do I need to re-compile the kernel in Android Kitchen? (I do not know how to do this by the way) or what else am I doing incorrectly? I have trawled the XDA HD2 forum, but had no luck. Suggestions?
Click to expand...
Click to collapse
You don't unzip the contents. By doing so you break the signing. What you wanna do is open your ROM zip using 7 zip then browse to the initrd.gz file copy to your desktop, close everything. Now open the kernel zip file browse to the initrd-custom folder open it. Now double click and drag the initrd.gz file from your desktop to the 7-zip window which has the kernel zip opened to the initrd-custom folder.
Sent from my GT-I9100 using Tapatalk

elesbb said:
You don't unzip the contents. By doing so you break the signing. What you wanna do is open your ROM zip using 7 zip then browse to the initrd.gz file copy to your desktop, close everything. Now open the kernel zip file browse to the initrd-custom folder open it. Now double click and drag the initrd.gz file from your desktop to the 7-zip window which has the kernel zip opened to the initrd-custom folder.
Click to expand...
Click to collapse
I did exactly as you said, but still the same end result :/

aldersonalex said:
I did exactly as you said, but still the same end result :/
Click to expand...
Click to collapse
Have you tried installing the kernel without adding the initrd.gz? I remember getting that error when the download was inturupted or something. So if you still get that error without editing the zip, then it most likely is the zip file and you need to redownload. Because if you did exactly as i said then it should be working. Im a long time user of his kernel's on almost every ROM out there and never once ran into any troubles. But we will surely figure this out
Can you post a link to the ROM you are using, and i'll download it and edit the kernel then repost it in this thread for you.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
Here it is i found the thread. its kernel 7.2 from DM.
Here

elesbb said:
Have you tried installing the kernel without adding the initrd.gz? I remember getting that error when the download was inturupted or something. So if you still get that error without editing the zip, then it most likely is the zip file and you need to redownload. Because if you did exactly as i said then it should be working. Im a long time user of his kernel's on almost every ROM out there and never once ran into any troubles. But we will surely figure this out
Can you post a link to the ROM you are using, and i'll download it and edit the kernel then repost it in this thread for you.
---------- Post added at 03:33 PM ---------- Previous post was at 02:43 PM ----------
Here it is i found the thread. its kernel 7.2 from DM.
Click to expand...
Click to collapse
Thank you so much, is this the HWA Kernel though?

aldersonalex said:
Thank you so much, is this the HWA Kernel though?
Click to expand...
Click to collapse
Yes 7.2 hwa from dorimanx
Sent from my GT-I9100 using Tapatalk

elesbb said:
Yes 7.2 hwa from dorimanx
Click to expand...
Click to collapse
Thank you so much, I wanted to experiment whether v6.9 is better than v7.2. Would it be possible to repack that kernel too?

aldersonalex said:
Thank you so much, I wanted to experiment whether v6.9 is better than v7.2. Would it be possible to repack that kernel too?
Click to expand...
Click to collapse
Haha yes I could, I personally preferred 7.2 over 6.9 but my favorite is 6.5D xP
Did you flash the zip yet?
Sent from my GT-I9100 using Tapatalk

elesbb said:
Haha yes I could, I personally preferred 7.2 over 6.9 but my favorite is 6.5D xP
Did you flash the zip yet?
Click to expand...
Click to collapse
I flashed it with success, but it doesn't feel as snappy as tytung r3, it takes a few seconds to unlock and load programs, even clocked at 1612mhz and experimenting with ZRAM on and off. Thank you though, I will probably stick with tytung's for the moment though, did you use 7-zip to transfer the initrd.gz file?

aldersonalex said:
I flashed it with success, but it doesn't feel as snappy as tytung r3, it takes a few seconds to unlock and load programs, even clocked at 1612mhz and experimenting with ZRAM on and off. Thank you though, I will probably stick with tytung's for the moment though, did you use 7-zip to transfer the initrd.gz file?
Click to expand...
Click to collapse
Hmm i wonder if its cause i took the initrd.gz from an older version of Paranoidandroid. I have version .6 on my computer thats why i used it. I'll redownload the latest and try with that. I might even flash it myself and test it out. Maybe the lib files need to be transfered as well. Dorimanx has by far been the best kernel for myself, but i dont really care for ICS yet but when i was testing the waters i used DM kernel and i loved it. Snappy responsive and pretty awesome. It just lacks a boat load of features i rely on in CM7. CM9 claimed they will re add the features once they iron kinks out so once they release a better build i will most likely convert

elesbb said:
...but i dont really care for ICS yet but when i was testing the waters i used DM kernel and i loved it. Snappy responsive and pretty awesome. It just lacks a boat load of features i rely on in CM7. CM9 claimed they will re add the features once they iron kinks out so once they release a better build i will most likely convert
Click to expand...
Click to collapse
Very curious by this statement, and admittedly, my own android experience is limited... I've used ACA SD android for a number of months, and have switched over to ICS. Currently with ICT & DM's 6.9 kernel, but love the UI in hybrid mode of PA... and so, am really curious what you meant when you alluded to 'missing features' that were in CM7, but not CM9. What was lost? What am I missing? (sincere question) Thanks, -Rob

RobE. said:
Very curious by this statement, and admittedly, my own android experience is limited... I've used ACA SD android for a number of months, and have switched over to ICS. Currently with ICT & DM's 6.9 kernel, but love the UI in hybrid mode of PA... and so, am really curious what you meant when you alluded to 'missing features' that were in CM7, but not CM9. What was lost? What am I missing? (sincere question) Thanks, -Rob
Click to expand...
Click to collapse
Well, there are two that i pretty much LOVE and cannot live without xD
Those are,
1. Disable full screen (status bar remains visible no matter the app, has a "hide" button if you wish to use full screen in a game or app, then you can unhide by pressing home key(my choice))
2. Really big one, lockscreen gestures. I love being able to draw a 'C' on my lockscreen and open the phone whitout having a custom app slot being taken up. Plus, gestures allow for an app to run while still displaying the lockscreen.
THose are the only two big ones i will miss, there are a few more small ones but i dont remember without flashing CM9 and checking And its been awhile since ive tested the waters, so i might download the latest AOKP and CM9 to see where they are at. But they both are good and pretty cool. CM7 is just perfect for me. No issues what so ever.

elesbb said:
Hmm i wonder if its cause i took the initrd.gz from an older version of Paranoidandroid. I have version .6 on my computer thats why i used it. I'll redownload the latest and try with that. I might even flash it myself and test it out. Maybe the lib files need to be transferred as well.
Click to expand...
Click to collapse
It would be brilliant if you could test out the kernel with the initrd.gz from 1.1a PA, that might explain why it felt slow when I tested the original.

[ROM][UNOFFICIAL][4.4.4][3.4 Kernel] CyanogenMod 11.0 Nightlies (tenderloin)

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

[Q] Problem with Quarx's CM11 ROM

Hello,
first: Sorry for opening a new Thread. I think it should be placed into the ROM's developing Thread, but I cannot because I've less than 10 posts and it's an developer Thread or sth like that.
I've Installed the newest (2014-01-24) Nightly. Since the one from 20-Jan-2014 I cannot open "Springfield: Tapped Out". It force close right before the loading screen should appear. All other apps (as far as I know) are still working fine. I'll attach a log-file of the start-sequence.
Does anybody has an idea how I can solve this? Is it because of the zRAM-feature that is enabled right from the 20th Jan build by default?
#SplashmasterBee

hello, i have no answer to your question. But I wanted to ask if CM11 is runs better than CM7.2 ?
I'm still on 7.2, it's quite stable, but it's quite old.

I can't remember if i had cm7.2 installed in my phone, but cm11 runs really smooth. And till the 20th Jan nightly i had no problems, too.

SplashmasterBee said:
Does anybody has an idea how I can solve this? Is it because of the zRAM-feature that is enabled right from the 20th Jan build by default?
#SplashmasterBee
Click to expand...
Click to collapse
Maybe try to reinstall app and wipe cashe/dalvik.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Isukthar said:
But I wanted to ask if CM11 is runs better than CM7.2 ?
I'm still on 7.2, it's quite stable, but it's quite old.
Click to expand...
Click to collapse
The speed as for me is the same. Better are the new interface features, worse is stability (but I hope it will be correct soon).

[email protected] said:
Maybe try to reinstall app and wipe cashe/dalvik.
Click to expand...
Click to collapse
I've already tried that, did a clean install from sbf.
Both doesn't help...
How can I (de-)activate zRam option. I'd like to try out if it works then...
Sent from my MB526 using XDA Premium 4 mobile app

[email protected] said:
Maybe try to reinstall app and wipe cashe/dalvik.
Click to expand...
Click to collapse
I've alredy tried it several times. I made an install from sbf, too ('cause system didn't boot anymore, but I think it was a problem with the incremental update), but it just don't work. Deleted the whole data of the app. Still the same...
In my opinion it could be caused by zRAM (enabled by default since 20th Jan build). I've tried to copy the ovcerclock_defy.ko like Quarx described, but it didn't help (I don't know if it worked so far...).
I'll try a newer build. Gonna report if it works with it...
#SplashmasterBee

Seems to be a general cm11 issue, not device dependent.
Builds before (including?) 20140118 work, later builds don't.
http://forum.xda-developers.com/showthread.php?t=2622325

CyanogenMod 11.0 Stable Released - what is working, what is not?

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