Related
UPDATE: 7.1 "stable" is OK but personally I prefer nightlies.
They are not stable! In fact RC1 boot loops! Please flash the latest nightly and google apps going forward!
Nightlies available here:
http://download.cyanogenmod.com/?type=nightly&device=speedy
Change log and link to nightlies here as well:
http://cm-nightlies.appspot.com/?device=speedy
Gapps here:
http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip
http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip
1) Copy zips to sd card
2) Backup with ti backup
3) Flash latest clockwork recovery through rom manager
4) Reboot into clockwork recover and run backup from clockwork recovery (aka nandroid)
5) mount usb storage in clockwork recovery and copy ti backups and clockwork recovery backup to your computer. Also copy any other important files on the sdcard (Especially pictures in the DCIM folder).
6) Copy nightly and gapps zips file to phone's sdcard
7) Wipe cache, wipe dalvik cache (under advanced), wipe battery stats
8) Install zips from sd card in this order:
a) CM_Speedyxxx.zip
b) googleapps 828-signed.zip
c) newtalk.zip
9) Reboot phone and wait 10 minutes phone should be in cm7 and working.
10) verify you can open market.
11) If you have problems try starting back at step 7 in clockwork and wipe data/factory reset
Questions/problems should be posted here:
http://forum.xda-developers.com/showthread.php?t=1001578
Optimal settings for CM7 on Sprint here (work in progress):
http://forum.xda-developers.com/showthread.php?t=1262313
These builds may be marked as Rc1 and stable but they are way old and NOT stable.
Before you ask, as of right now the nightlies are the most stable version of CM7 being release right now.
bump.
Please sticky this.
I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.
linuxman008 said:
I agree with these not being stable, and the nightlies are far more stable. But you might want to revise the bootlooping on RC1 statement. It can be stopped from bootlooping by flash it, full wipe while its flashed, flashing gaps, and then it will work fine. I haven't tried another kernel after doing that though.
Click to expand...
Click to collapse
Pointless. Just like flashing RC1.
VICODAN said:
Pointless. Just like flashing RC1.
Click to expand...
Click to collapse
Eh, I use mikshift anyway, but when It came out, it was the only rom I had on my sd card, and I needed to make a phone call, so I was forced to make it work. That method saved my life, or at least made it so I could get a ride home, other than that, I wouldn't use it.
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)
You don't have to pay for the nightlies, don't know if you are aware of the mirror for the nightlies, but no pay there. Only have to pay if you want to download thru rom manager. Just thought i'd point thay out
Sent from my PG06100 using Tapatalk
linuxman008 said:
In fact, the only reason I would consider the "stables" would be so that I can not have to pay so that I can get updates (with the only paid roms for the shift being the nightlies, I think there is no reason to buy full rom manager)
Click to expand...
Click to collapse
perhaps you missed this thread
http://forum.xda-developers.com/showthread.php?t=1001578
....
cm7 never charges for anything - even with all the crazy amounts of bandwidth they use...
Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?
sdk234 said:
Just to confirm, it's preferable to flash the nightly rather than CyanogenMod 7 for the HTC Evo Shift 4G :: V7.1.0 (9 Oct 2011) just posted?
Click to expand...
Click to collapse
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
VICODAN said:
Yes, I'd still rather flash a nightly.
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
You're 100% sure CM7.1 has bugs? Have you used 7.1?
I'm using update-cm-7.1.0-Speedy-signed.zip, released 10/9, without issue. OC'd to 1.5 gHz, using ScaryKernel 3.
jesusice said:
You're 100% sure CM7.1 has bugs? Have you used 7.1?
Click to expand...
Click to collapse
Keyboard shortcuts.
Bug.
VICODAN said:
Keyboard shortcuts.
Bug.
Click to expand...
Click to collapse
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.
jesusice said:
So, you HAVE used CM7.1? Can you elaborate more as to what the bug is?
This thread was needed when our last RC was months old but it's now outdated and no longer needed. It should be unsticked. CM7.1 is rock solid.
Click to expand...
Click to collapse
You remember that bug when you opened the keyboard and pressed e and it opened email? The one that was only fixable on a reboot?
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".
VICODAN said:
I'm 100% sure 7.1.0 Oct 9 2011 has bugs. Maybe not the bootloop 7.1 RC1 had but nightlies usually have newer features and more bugfixes than any milestone release.
Click to expand...
Click to collapse
VICODAN said:
You remember that bug when you opened
I have not flashed it. Why would I? How is it different than a nightly? It's a nightly build that's labeled "stable".
Click to expand...
Click to collapse
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.
jesusice said:
If you haven't flashed it then you should avoid advising others not to flash it. And I have had that weird KB issue before but not in the last month or more, so I wouldn't assume a bug that you once had is still present in a ROM that you haven't flashed yet. And if it's no different than a nightly build, what's the point of telling people not to flash it but to instead flash a nightly? People should flash CM7.1 if they want to have official support. Bug reports on nightlies are laughed at.
Again, this PSA is outdated and unneeded now.
Click to expand...
Click to collapse
Changed the thread title, updated OP.
VICODAN said:
Changed the thread title, updated OP.
Click to expand...
Click to collapse
Works for me
The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.
Philpot85 said:
The only bugs that I've noticed are with Music Folder Player Free and a one time bug with the camera.
Music Folder Player Free - With the screen on songs play fine until I go to scroll through a folder/list of songs or if the screen is rotated. It starts to stutter and skip while I'm interacting within the program. With the screen off music will randomly stutter and skip and get worse as the song plays. Stock Android music player doesn't have this issue.
Camera - I tried to take a picture today and my phone seemed to lockup; none of the capacitive buttons would work and a menu pop-up didn't go away. When I pulled my phone back out of my pocket the screen was completely garbled and grainy. Had to pull the battery, but afterward everything was fine again.
Click to expand...
Click to collapse
You could always try a nightly?
Why is the latest 7.1.0 stable for Speedy not posted on Cyanogen Mirror Network? I grabbed it elsewhere not long after it came out, but seems weird that it still does not show up there.
Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.
So who wants to be the Guinea pig? I'm already running that KANG that was posted up earlier this weekend. I may try it after I charge up.
yea...guinea pig here....goes through boot animation and then system ui and trebuchet (the launcher) fc...i would say stay away until some official announcement is made
Yeah. It doesn't even boot up probably. :-(... going back to stock
Sent from my Galaxy Nexus using XDA App
You have to start somewhere.
Now at least we have an official CM9 branch, which means someone is working on it
brzgw said:
Hello people,
I was looking through the nightly builds on download.cyanogenmod.com
I saw a fresh build for TF101 dated for 2/27.
Check it out. I will flash it and see how it is.
Someone also needs to create an Official CM9 Nightly page in Dev section.
Click to expand...
Click to collapse
ehm where from?
Edit: http://download.cyanogenmod.com/?device=tf101
Found IT ^_^
I got launcher force closes when i had an overclocked kernel with a stock rom. Gonna check this out a little later.
Sent from my Transformer TF101 using Tapatalk
I'm surprised that this news seems to be not generating much buzz here. Not knocking any of the other devs, because most of them do amazing work, but CM is the bee's knees. When those nightlies get semi-mature, I'll be running them and never look back. They've never done me wrong before. Any device I've ever had that was supported, was the best ROM available for my needs. YMMV, of course.
I think when its own thread is created youll see the buzz, cm rocks lol
Sent from my R800i using xda premium
I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet
shadrach47 said:
I tried flashing it and got the same fc, the system ui and launcher. I tried it again but formatted system this time. Got the same results but was able to see the clock and tablet reboot options.
Guess it's not ready yet
Click to expand...
Click to collapse
Yep, same here, even with wipe dalvik and fix permissions, FC´s :S
Let us wait for a new update....
Alas, I ran across this on get.cm also. Got excited and then had the FC issues like everyone else. At least it is a step in the right direction.
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Was just about to try flashing it until I saw how many people were unsuccessful. Oh well, guess I'll wait until an official release.
ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.
shadrach47 said:
Not sure if it's related or not but my wifi on a Kanged version of CM9 is acting weird, disconnecting and saying out of range.
I tried this one first but it could just be the ROM I'm on.
Click to expand...
Click to collapse
Ok got it to work again, had to use Super Wipe Lite from http://forum.xda-developers.com/showthread.php?t=1245892
after running the script flashed latest revolver and got wifi backup....
Same here, will try your suggestion below.
Edit: Had to run the wipe zip, reflash and boot into current rom and the restore a backup to get it working again. PITA But it works.
ferreinf said:
Don´t know if its related,
lost my wifi hability after trying this, anyone else?
it just won´t turn on :S
Click to expand...
Click to collapse
CM rocks
lollazzo said:
CM rocks
Click to expand...
Click to collapse
i would like to see MIUI V4 on tab, as it will be easier to port than 2.x was ^_^
New official CM9 nightly on get.cm. It boots!!! Gonna test it and report back in a bit.
EDIT1: Wifi works and was able to log into my Google account. Currently restoring my Titanium Backup and will test a bit more after that. Also, camera makes the tablet reboot on first launch, but works after that. Odd. More info to come.
EDIT2: Face unlock is there, but doesn't recognize my face, so I can't test it out. It couldn't recognize my face on my Nexus S 4G either. Maybe my face is just derped up. Anyway, there is nothing that I could tell that is broken. Even the MicroSD mounted with no issue. I don't have a keyboard dock to test it out, otherwise I would. Games and videos both work fine.
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!
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
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