ALL CREDITS TO DALINGRIN & BRIANF21
* All warnings implied and applies... so use at your own risk
* I'm NOT a DEV nor is this something special, so get over it
This CWR flashable kernel is ONLY for Nookie Froyo 0.6.8 (yes, the 10 of us still using it), is based upon Dalingrin's 3/13/11 OC Kernel, derived from Customized Nookie Froyo 0.6.8 CWR for eMMC Update by Brianf21.
Who can use it?
* Anyone using Nookie Froyo 0.6.8 based roms, including Nookie Comb and wants working BT on their Nook.
* People who like their setup and don't want to flash brianf21's Customized Nookie Froyo version 7, but just want the BT and OC
* It's essentially for senior citizens and dinosaurs (lazy ones)
What it does?
* Allows you to turn on BT and therefore make your Nookie awesome (without actually being awesome by going with CM7)
* Allows you to turn your outdated WiiMote into a BT controller for your sweet SNES (or other) emulators so you can play Super Mario cause you're a senior citizen.
update-froyo068-BT-3.13.11-Kernel.zip
Mods - if this is not acceptable, please move it/delete/or throw a fit.
Would you be able to make this work on the 2/25 kernel thats stock OC'ed 1.1ghz? I've found that kernel to be the most stable out of them all.
thanks for this. I like nookiecomb froyo,,, i'm on cm7 now and I'm still getting used to it. I'm struggling to get the interface/functions as nice as nookiecomb. There just isn't a perfect hc theme for nook color yet on cm7. This will make my move even harder....
dexx0008 said:
thanks for this. I like nookiecomb froyo,,, i'm on cm7 now and I'm still getting used to it. I'm struggling to get the interface/functions as nice as nookiecomb. There just isn't a perfect hc theme for nook color yet on cm7. This will make my move even harder....
Click to expand...
Click to collapse
This one is pretty nice.
http://forum.xda-developers.com/showthread.php?t=1041588
Nburnes said:
This one is pretty nice.
http://forum.xda-developers.com/showthread.php?t=1041588
Click to expand...
Click to collapse
that is the one i'm using, i have it setup pretty good but a few changes I need to figure out yet. thanks for point it out though.
anyone find out if this is OCed or not? Also, I have Nookie Comb 4.13, will this work on that?
jv
johnnyv5 said:
anyone find out if this is OCed or not? Also, I have Nookie Comb 4.13, will this work on that?
jv
Click to expand...
Click to collapse
This isnt OC'ed I also get ALOT of sleep death with the kernel also if I connect USB it doesnt allow me to share to PC or debug. I reflashed to the 2/25 kernel and everything goes back to working fine. If you could do the bt fix on the 2/15 kernel that would be perfect. Attached
Can we get Bluetooth to work in a rooted stock 1.2???
This is Dalingrin's 3/13/11 kernel for CM7. I just put it in one of my images due to a request. All credit should go to Dalingrin. Yes, it can be overclocked. You could also play with this kernel. http://nook.handhelds.ru/dalingrin/kernels/031011/ I think he has bluetooth working here too. This was the last kernel before it took separate paths for froyo and cm7.
perfect. thanks brainf21
How does the 3/31 kernel you linked to above compare to what you have in your nookie froyo 0.6.8 thread???
(http://forum.xda-developers.com/showthread.php?t=922324)
Currently running nookie froyo 0.6.8 on EMMC and would like to continue, how can I add the BT kernel to what I'm running now?
Thanks in advance for your help, I've searched and all the flashing info I've read is confusing me
Geekbabe said:
Currently running nookie froyo 0.6.8 on EMMC and would like to continue, how can I add the BT kernel to what I'm running now?
Thanks in advance for your help, I've searched and all the flashing info I've read is confusing me
Click to expand...
Click to collapse
So you want it spelled out for you eh?... lol there's some good guides out there to read, and it's probably important to know what you're doing if you're flashing stuff. Anyways, here's the cheat sheet:
* First thing's first, download the BT update kernel .zip in the OP. DO NOT modify it or unzip it. Simply copy it to the root of your SD card.
1. If you flashed Nookie Froyo, then you have seen or know what ClockWork Recovery (CWR) mod looks like or maybe how to load it. If you have the latest CWR and can boot into it, then skip #2.
2. Go into market, search and install Rom Manager. Run it, click flash recovery, choose "nook color" NOT the (old). Now select "Reboot into Recovery". It should reboot you into CWR, if not, hold power until it restarts and hold down the "n" button until the "touch the future of reading" disappears, then into CWR.
3. In CWR, select "install from zip", select the BT kernel zip, then yes to flash.
4. Clear cache if you wish, reboot system... try turning on BT and it should work.
There's a few issues with these kernel related to wifi sleep. My suggestion is to set wifi sleep policy to "never" and once in a while, "forget" all your wifi profiles and reconnect to them. Also if you don't use your nook for a while, your device might go into the sleep of death and you'll just have to hold down the power button for a while to restart it. The downside: annoying. The upside: saves battery. Good luck.
HTCF4N said:
So you want it spelled out for you eh?... lol there's some good guides out there to read, and it's probably important to know what you're doing if you're flashing stuff. Anyways, here's the cheat sheet:
* First thing's first, download the BT update kernel .zip in the OP. DO NOT modify it or unzip it. Simply copy it to the root of your SD card.
1. If you flashed Nookie Froyo, then you have seen or know what ClockWork Recovery (CWR) mod looks like or maybe how to load it. If you have the latest CWR and can boot into it, then skip #2.
2. Go into market, search and install Rom Manager. Run it, click flash recovery, choose "nook color" NOT the (old). Now select "Reboot into Recovery". It should reboot you into CWR, if not, hold power until it restarts and hold down the "n" button until the "touch the future of reading" disappears, then into CWR.
3. In CWR, select "install from zip", select the BT kernel zip, then yes to flash.
4. Clear cache if you wish, reboot system... try turning on BT and it should work.
There's a few issues with these kernel related to wifi sleep. My suggestion is to set wifi sleep policy to "never" and once in a while, "forget" all your wifi profiles and reconnect to them. Also if you don't use your nook for a while, your device might go into the sleep of death and you'll just have to hold down the power button for a while to restart it. The downside: annoying. The upside: saves battery. Good luck.
Click to expand...
Click to collapse
Thank you so much! LOL, I am an idiot, the rom manager was staring me in the face in my apps, I copied the file, booted into recovery, installed the zip, cleared cache and here I am again!
Related
First off - I must acknowledge that that code this came from, is not mine. All credit goes to Geniusdog254, fat-tire, mbm (irc advice), and those who have committed to their branches; i would like to eventually make my own branch, but for now, this is a great start. Hopefully this is ok with them - if not, i will happily take it down.
UPDATE AT YOUR OWN RISK.
So, for all those lucky 2.1 users, you have have a nice overclocked kernel. Well, today lucky 2.2 users get the same enjoyment! Just as a teaser - Quadrant gives a score of 1618
0.2:
950Mhz: http://www.mediafire.com/?mbfnt3i39cz8q9o
900Mhz: http://www.mediafire.com/?opmajiyx1puf11t or http://www.megaupload.com/?d=AQKPIPHR
Changes:
***ROTATION IS FIXED***
Original Kernel base proved unstable for the Froyo build. So, went back to basics, and modified the original Nookie Froyo Kernel, as found here: https://github.com/fat-tire/nook_kernel
Future code will be branched from this for the time being.
Built two different kernel speeds, for those whose systems dont like 950.
0.1:
http://www.mediafire.com/?aoadpgt2foxhby9
Compiled from https://github.com/fat-tire/Quickie, as of 1/18/11.
Kernel defaults to 950Mhz
Kernel made compatible to 2.2 standards, with other minor fixes (as noted in Github
To Install:
[Pre Install]
Wipe Dalvik Cache
As suggested here: http://forum.xda-developers.com/showpost.php?p=10749287&postcount=12, it is best to wipe the dalvik cache (if this is not the first boot of the system,). To do so (after connecting your nook to a PC):
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
This can also be done in root explorer.
[Install]
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.
[Tested on]
I have tested this Kernel on both a fresh copy of .5.8, as well as the custom .5.9 as posted here: http://forum.xda-developers.com/showthread.php?t=922324
[Recomendations]
Get SetCPU (from this friendly forum!), and change the governor to on-demand. It is currently defaulted to conservative for battery, but OD should give better performance.
Future & Reserved:
Ideally, i would like to build on this kernel, and add features other kernels have, such as different governors, BFS, and HAVS. I don't know much I can actually do, but as time goes I am sure i will learn more. Please be patient with me, and remember this is a WIP. While i am not new to coding, I am new this kind of kernel work, so I am still picking up things here and there..
Issues -
Quadrant is stupidly picky. I am not sure what i did to get it to run when I did, but the best i can say s to keep trying. Right now, it seems to really hang at 2/4 on the I/O.
I believe the default governor is set to conservative; i recommend downloading SetCPU and setting it to ondemand.
Woot Saw the IRC work and couldnt wait.
And i was going to say the wait at 2/4 on I/O was like that before
1607 Quadrant score
Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.
kassemja said:
Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.
Click to expand...
Click to collapse
Just boot a copy of nookie froyo from a mircosd and mount the /data partition from the emmc to delete the davlik cache. That's how I was making changes to nookie froyo when I was running it off the emmc. Once hardware decoding for media is supported I will put NF back on the emmc. Can't wait till clockwork supports froyo. I will be all over this!
Nook [email protected]+Nookie=Awesome
Not working on my Froyo'ed Nook
Divine_Madcat said:
To Install:
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.
Click to expand...
Click to collapse
Hi! It sounds really promising.
I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.
Any idea? TIA
xyzolog said:
Hi! It sounds really promising.
I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.
Any idea? TIA
Click to expand...
Click to collapse
Same thing happening here.
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
I have used the 950 kernel on 2.1 for about a week no issues. I'm happy to test again with a davlik cache wipe. On the way to work now. So hopefully you can post new build by then.
Divine_Madcat said:
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk
Divine_Madcat said:
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
Click to expand...
Click to collapse
Yes. 950 Mhz ran fine for me. The 1Ghz though did not.
I didn't do a Dalvik cache wipe first. When i get a chance I'll try that and give it another go.
deitiphobia said:
Same thing happening here.
Click to expand...
Click to collapse
I have the same thing happening - flashing loading; then the screen going blank, but staying on ... after about 2-3 retries, I can get it to boot. As long I keep it booted, I don't have any more problems.
Been running the 950 kernel w/ 2.1 no problems ...
jasoraso said:
I have the same thing happening - flashing loading; then the screen going blank, but staying on ... after about 2-3 retries, I can get it to boot. As long I keep it booted, I don't have any more problems.
Been running the 950 kernel w/ 2.1 no problems ...
Click to expand...
Click to collapse
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
watzone69 said:
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
Click to expand...
Click to collapse
Gave this a shot, hopefully this helps!
EDIT: first two reboots > boots fine!
watzone69 said:
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
Click to expand...
Click to collapse
I can get it to boot every 4th or 5th time, but only into instability. It will crash shortly thereafter for one reason or another. Currently it's bootlooping, but NOT off the SD card and Nookie Froyo, it's bootlooping off of the internal memory and 2.1.
I think I'm going to give up on this for now till a more stable solution is reached.
My 2.1 is still running fine at 950Mhz though despite not being able to get this to work for Nookie Froyo.
FOr anyone interested - There are two new Kernels posted, based off different (more stable) code, with one built at 900Mhz, and the other at 950. Please test and use, i think you will find them more stable than the previous..
Excellent, trying the 950 now. I couldn't get the 900 to download. I just keeps looping.
Homer
Homer_S_xda said:
Excellent, trying the 950 now. I couldn't get the 900 to download. I just keeps looping.
Homer
Click to expand...
Click to collapse
Download from the server? Or working on the nook?
Divine_Madcat said:
Download from the server? Or working on the nook?
Click to expand...
Click to collapse
Cannot download it from the server. The 950 was fine, but I could not get the 900 zip from the server.
My NC/NF is rocking 950! Cleared the Dalvik cache via Root Explorer, powered off via QuickBoot, swapped the uImage (after backing up the NF 0.5.9 one and verifying that my backup worked) and powered on. Booted on the first go and it already seems snappier. In the About Phone the kernel now shows as
2.6.29-omap1
[email protected] #2
UPDATE: WOW just wow! Dolphin HD is actually usable now, it was really dragging before. When this gets stable from the internal memory it will be amazing.
Excellent!
Homer
Homer - not sure why its doing that, but i put up an alternate mirror just in case.. but it sounds like you don't need it.
For everyone who is trying it - please drop some feedback. I really want to learn and support this kernel, but can only do so with feedback. Thanks!
Divine_Madcat said:
Homer - not sure why its doing that, but i put up an alternate mirror just in case.. but it sounds like you don't need it.
For everyone who is trying it - please drop some feedback. I really want to learn and support this kernel, but can only do so with feedback. Thanks!
Click to expand...
Click to collapse
The alternate server worked fine. I dl'd the 900 version just in case. Will you be trying a 1GHz version?
Also, any chance you can figure out how to implement IPtables? I'm dying to get proxy for wifi working at least near to how it works on my iPod touch. I can't get over the fact that Google really doesn't seem to want to get into businesses with Android.
Homer
CREDITS TO GabrialDestruir,et al (MN 4.5.6) & Dalingrin (OC kernel)
* All warnings implied and applies.. your Nookie might turn into a Cookie... so use at your own risk!
* I'm NOT a DEV nor is this something special, so get over it
This CWR flashable kernel is ONLY for STOCK Barnes and Noble's Froyo 1.2 update. MiniRooter V2 is based upon GabrialDestruir's MN 4.5.6 & Dalingrin OC kernel for stock Froyo 1.2 release 5/13.
Why should I jump on this bandwagon??
MiniRooter will make you 35% happier... j/k it might make you sadder. Ok, maybe not, but it will save you some headaches. It was made for my own selfish use, but I decided it was time to share.
It is NOT for people who wants FULL Android tablet functionality! Go install CM7, Nookie Froyo, or use the ManualRooter.
The purpose of Mini Rooter is to allow stock BN 1.2 users access to SU, overclock, install third party apps (sideload), and install apps from Amazon app market. It is intended to mainly add and NOT modify any essential NOOK files, thus keeping the BN Nook experience as functional as possible for its intended purpose. However, you can really make it bi-polar and install other stuff too if you want. For a GREAT & free exchange email client w/calendar, find MoxierMail from the Amazon appstore. It is awesome.
The main reason for not modding file systems and installing the google market is to avoid problems I ran into with the MN 4.5.6 install, ie. touch page flips of children's book, BN store not working on purchases, instore access, and other headaches.
NO install issues with Angry Birds from the Amazon app store. When installing, choose "Package Installer"
Essentially, this mod is for newbies and/or tree-hugging hippies and minimalists with a lust for power and a thirst for frozen lemonade. mmm.. frozen lemonade.
What it does?
* Installs SU & busybox (rooting)
* Replaces stock kernel with Dalingrin's OC Kernel (up to 1.2ghz!!)
* Installs these apps:
adbwireless
Amazon Appstore
Button Savior
Calculator
SetCPU - you should donate (its also on the android market)
TouchRecalibrate
Zeam
Nook Color Tools - change settings, install 3rd party apps
Rom Manager - CWR & backups
Youtube - for learning how to dougie
Pick a Flavor:
MiniRooterV2-BN1.2-OC
MiniRooterV2-BN1.2-OC-dualboot
*Added 5/17
Flash these files after the previous if your girlfriend/sister/wife keeps nagging you this Nook Color is too fast, and you want to put an end to that.
Stock Kernel - BN 1.2 - Froyo
Stock Kernel - BN 1.2 - Froyo - Dual Boot
* These should work for other practical applications as well, so feel free to snag them just in case.
Devs - please let me know if you wish me to remove any/all of your work that have been included in this release. Thank you for your hard work and dedication, which inspires me to learn and contribute to this community.
Mods - if this is not acceptable, please move it/delete/or throw a fit.
FAQ:
ghintx said:
Unfortunately, I am having 2 issues. One is getting apps from the Amazon App store to install. I keep getting told that the system will only install apps from the Andoid app store, even though the settings are correct. The second issue is with button savior. the back button is not working in the applications section of the settings...
Click to expand...
Click to collapse
1. Go into Nook Color Utils - uncheck and then recheck "Allow Non-Market Apps"
2. Button Savior needs Super User permission, so make sure you press "Allow" when the pirate greets you.. in some cases it will not work since the stock BN codes has set the 'n' button to be "back" in fullscreen apps. In cases where there's a "back" button on the taskbar, that will also take priority from button savior.
Great work! Exactly what I was looking for. Only a few questions:
Do side-loaded apps appear in the APPS menu or do I have to use Zeam to access them?
Is it possible to replace Dalingrin's kernel with stock afterward?
Thanks
MK[PCTF] said:
Great work! Exactly what I was looking for. Only a few questions:
Do side-loaded apps appear in the APPS menu or do I have to use Zeam to access them?
Is it possible to replace Dalingrin's kernel with stock afterward?
Thanks
Click to expand...
Click to collapse
Use Zeam for sideloaded apps to show, download AppHome if you want to use the 'n' button to default to Zeam and still return to stock Home.
Just flash a stock kernel over it if you don't want to OC... or just not do anything to setCPU.
Btw: GOOOO THUNNDDERRR!!! Wooohoo... Durantula!!!
Something told me to look at XDA one more time before getting back to work. This is awesome, thanks.
Question
Sorry if this is a noob question, but how do I boot from this? I just got a replacement Nook Color that came pre-loaded with 1.2 and I can't seem to nooter it for the life of me!! I've downloaded this and copied it to an SD card, but it doesn't boot. I can't get it to boot from a Clockwork Recovery SD card either. Any help would be appreciated!!
More than happy to be corrected, but isn't SetCPU a paid app?
GabbleRatchet said:
More than happy to be corrected, but isn't SetCPU a paid app?
Click to expand...
Click to collapse
SetCPU is here... yes, you should donate or buy it if you wish. Thanks for pointing this out. I added the link to SetCPU from XDA. I might remove this if it becomes an issue and include No-Frill or something.
Zephyr757 said:
Sorry if this is a noob question, but how do I boot from this? I just got a replacement Nook Color that came pre-loaded with 1.2 and I can't seem to nooter it for the life of me!! I've downloaded this and copied it to an SD card, but it doesn't boot. I can't get it to boot from a Clockwork Recovery SD card either. Any help would be appreciated!!
Click to expand...
Click to collapse
First of all, you have to be able to get into Clockword Recovery. If you can boot into CWR from and SD card, all you have to do is choose "install from zip", choose the file from the OP, yes, and flash it. That should do the trick. It's not a "bootable" file by any means. If you still have problems, keep reading and try different methods. It's hard to give you advice since I don't know your level of knowledge.
Unfortunately, I am having 2 issues. One is getting apps from the Amazon App store to install. I keep getting told that the system will only install apps from the Andoid app store, even though the settings are correct. The second issue is with button savior. the back button is not working in the applications section of the settings...
ghintx said:
Unfortunately, I am having 2 issues. One is getting apps from the Amazon App store to install. I keep getting told that the system will only install apps from the Andoid app store, even though the settings are correct. The second issue is with button savior. the back button is not working in the applications section of the settings...
Click to expand...
Click to collapse
1. Go into Nook Color Utils - uncheck and then recheck "Allow Non-Market Apps"
2. Button Savior needs Super User permission.. in some cases it will not work since the stock BN codes has set the 'n' button to be "back" in fullscreen apps. In cases where there's a "back" button on the taskbar, that will also take priority from button savior.
HTCF4N said:
1. Go into Nook Color Utils - uncheck and then recheck "Allow Non-Market Apps"
2. Button Savior needs Super User permission.. in some cases it will not work since the stock BN codes has set the 'n' button to be "back" in fullscreen apps. In cases where there's a "back" button on the taskbar, that will also take priority from button savior.
Click to expand...
Click to collapse
That did it! Thanks! Now I just need to figure out how to dual boot this...
ghintx said:
That did it! Thanks! Now I just need to figure out how to dual boot this...
Click to expand...
Click to collapse
Glad to hear that.. Dual booting is kind of hairy, so make sure you do a lot of reading and do a nandroid backup before plunging in.
I have the stock BN 1.2 minirooted on the dual boot of the emmc. Primary partition has been back and forth between cm7 and nookie froyo.
HTCF4N said:
Glad to hear that.. Dual booting is kind of hairy, so make sure you do a lot of reading and do a nandroid backup before plunging in.
I have the stock BN 1.2 minirooted on the dual boot of the emmc. Primary partition has been back and forth between cm7 and nookie froyo.
Click to expand...
Click to collapse
That's what I was looking to do, but using the phiremod 6.2. Any suggestions?
HTCF4N said:
Glad to hear that.. Dual booting is kind of hairy, so make sure you do a lot of reading and do a nandroid backup before plunging in.
I have the stock BN 1.2 minirooted on the dual boot of the emmc. Primary partition has been back and forth between cm7 and nookie froyo.
Click to expand...
Click to collapse
How about using [ADV][DEV][CWM]Copy Nook Stock to SDcard Image[5/9] thread to move your image to SDcard.
Keep whatever we want in emmc, and boot this from the SDcard.
I currently have phiremod v6.2 in emmc, with Dal's beta 3.1 32 kernel on verygreens SDcard. Going to try installing [UPDATE ZIP] Stock 1.2 update.zip flashable from CWM, your ROM, and then using rack's [ADV][DEV][CWM]Copy Nook Stock to SDcard Image[5/9] thread to move your image to SDcard to move it to another SDcard.
From CWM will do nandroid backup before and will restore after I complete the above procedure. When I boot phiremod v6.2 from emmc, I have a 16GB data/video/music SDcard in my nookcolor.
lschroeder said:
How about using [ADV][DEV][CWM]Copy Nook Stock to SDcard Image[5/9] thread to move your image to SDcard.
Keep whatever we want in emmc, and boot this from the SDcard.
I currently have phiremod v6.2 in emmc, with Dal's beta 3.1 32 kernel on verygreens SDcard. Going to try installing [UPDATE ZIP] Stock 1.2 update.zip flashable from CWM, your ROM, and then using rack's [ADV][DEV][CWM]Copy Nook Stock to SDcard Image[5/9] thread to move your image to SDcard to move it to another SDcard.
From CWM will do nandroid backup before and will restore after I complete the above procedure. When I boot phiremod v6.2 from emmc, I have a 16GB data/video/music SDcard in my nookcolor.
Click to expand...
Click to collapse
Used emmc CWM to install Stock 1.2 update and this ROM. Did factory reset and then install both from CWM before rebooting. Will setup some before moving to SDcard.
Edit 1: Will report status as I go here.
HTCF4N said:
[*] The main reason for not modding file systems and installing the google market is to avoid problems I ran into with the MN 4.5.6 install, ie. touch page flips of children's book, BN store not working on purchases, instore access, and other headaches.
Click to expand...
Click to collapse
For the record, a fix for the kids books was posted last week (it's in the OP for MN) and the other things still work with MN 4.5.6 for most people (I have two with none of those issues). Nice work though!
You might want to update the versions though. SetCPU is at 2.13. And Zeam is up to 2.9.5 (looks like this is 2.9.2)
GabbleRatchet said:
More than happy to be corrected, but isn't SetCPU a paid app?
Click to expand...
Click to collapse
It's free for XDA members so you don't have an issue there, but let your conscience be your guide to donation.
Zephyr757 said:
Sorry if this is a noob question, but how do I boot from this? I just got a replacement Nook Color that came pre-loaded with 1.2 and I can't seem to nooter it for the life of me!! I've downloaded this and copied it to an SD card, but it doesn't boot. I can't get it to boot from a Clockwork Recovery SD card either. Any help would be appreciated!!
Click to expand...
Click to collapse
This is quite concerning actually because there was a report of another recent Nook that would not boot from SD. They "determined" that was a faulty Nook, but your situation worries me. Please keep us posted on this one.
Zephyr757 said:
Sorry if this is a noob question, but how do I boot from this? I just got a replacement Nook Color that came pre-loaded with 1.2 and I can't seem to nooter it for the life of me!! I've downloaded this and copied it to an SD card, but it doesn't boot. I can't get it to boot from a Clockwork Recovery SD card either. Any help would be appreciated!!
Click to expand...
Click to collapse
Zephyr - What are the first six digits of your Nook's S/N? Something like 201146....?
doncaruana said:
For the record, a fix for the kids books was posted last week (it's in the OP for MN) and the other things still work with MN 4.5.6 for most people (I have two with none of those issues). Nice work though! ...
Click to expand...
Click to collapse
If I wanted couple of the gapps, say gmail and google voice could I just use my side loaded Titanium Backup to restore them from my CM7 data disk that contains them?
In MN what gapps are they using? Could I add them here later if I wanted to? I guess that defeats the purpose of this ROM.
Is there an alternative to gmail that anyone would recommend? I use google voice in CM7 for texting, how about an alternative for google voice?
doncaruana said:
For the record, a fix for the kids books was posted last week (it's in the OP for MN) and the other things still work with MN 4.5.6 for most people (I have two with none of those issues). Nice work though!
You might want to update the versions though. SetCPU is at 2.13. And Zeam is up to 2.9.5 (looks like this is 2.9.2)
It's free for XDA members so you don't have an issue there, but let your conscience be your guide to donation.
This is quite concerning actually because there was a report of another recent Nook that would not boot from SD. They "determined" that was a faulty Nook, but your situation worries me. Please keep us posted on this one.
Click to expand...
Click to collapse
I don't have my NC with me (at work right now) to verify the S/N, but I was able to root my previous NC (very seasoned with rooting many other android devices) with no problems. I'm beginning to think that I may have a "faulty" one, but I don't know how I can get it swapped again within the warranty. I did notice ONE dead pixel, but I doubt they'll swap it out for that! This thing is virtually useless to me without being able to root it!!!
Can install Keyboards automatically or will I work the same as 4.5.6?
Sent from my PC36100 using XDA App
lschroeder said:
If I wanted couple of the gapps, say gmail and google voice could I just use my side loaded Titanium Backup to restore them from my CM7 data disk that contains them?
In MN what gapps are they using? Could I add them here later if I wanted to? I guess that defeats the purpose of this ROM.
Is there an alternative to gmail that anyone would recommend? I use google voice in CM7 for texting, how about an alternative for google voice?
Click to expand...
Click to collapse
You could try installing gapps and google voice and see if it works. It might not without modifying system files, and that's something this release tries to avoid. You don't need an alternative to gmail since the included BN email app is a multi-email client (gmail, yahoo, etc) but doesn't include exchange (Moxier Mail is a great alternative).
Can install Keyboards automatically or will I work the same as 4.5.6?
Click to expand...
Click to collapse
what??
For the record, a fix for the kids books was posted last week (it's in the OP for MN) and the other things still work with MN 4.5.6 for most people (I have two with none of those issues). Nice work though!
You might want to update the versions though. SetCPU is at 2.13. And Zeam is up to 2.9.5 (looks like this is 2.9.2)
Click to expand...
Click to collapse
That's nice.. I only had to format/reinstall 23523434x to find out after MN, the BN store doesn't even load, give me these weird errors and check barnesandnoble.com blah blah. I then became a hippy and did it my way. And sometimes, less is more... even in version numbers of apps (which doesn't add anything to the functionality except a new version number).
@ Zephyr757 - hope you didn't get a lemon. I thought you just copied the zip file to the uSD and tried to boot that.
I am new to the forum and the G Tab but have been browsing. I just got the G Tab today and wanted to pursue the Roebeets+Clemsyn's Honeycomb COMBO alpha path!
I have a few questions...
Assuming I have the 1.2 BL (4349) out of the box do I still need to re-partition the G-Tab with 2048/0MB and wipe before proceeding?
Can I skip the following steps?
1. Nvflash to 3588 STOCK DO NOT USE CWM FOR 3588
2. Do not install CWM (we need the stock recovery)
3. DO NOT INSTALL CWM (we need the stock recovery)
4. PLEASE DO NOT INSTALL CWM
5. Reboot
And start from here assuming the partition sizes are correct?
6. RENAME COMBO FILE NAME TO Update.zip
7. Move Update.zip to /sdcard folder
8. Unzip recover.zip and move recovery folder to /sdcard folder
8. Turn off
10. Press Power+Volume up then this will install Update.zip
I know I should NOT install CWM as it wont work until after I flash the ROM which I assume is included in the ROM image.
Is there anything else I need to do before proceeding? I will backup the original ROM of course.
Thanks in advance and what an excellent resource
Do you know what what alpha means? It means it's not recommended for new users. There are many things that still don't work.
That said, technically you can skip all of that. Do you even know why we recommend people to repartition to 2048/0? It's because of compatibility issues. If you don't repartition from the beginning, the system will eventually force closes everything.
I highly recommend you visit my sight. It's written for beginners.
http://viewsonic-gtablet-for-dummies.webs.com/
Yes I do know what alpha means I deal with devs all of the time. I wanted to clarify the partition sizes because it wasn't mentioned in the dev thread as most users there were already coming from previous mods. I will check out your site though and I appreciate the advice. I may be a noob to the G-Tab and Andriod but am an IT admin by trade.
Thanks!
Ok. Still, chances are you will eventually have force closing issue. And I do mean it's bad. That's why the recommendation nowadays is for people to repartition right away before they start putting their own crap into the sdcard. Partitioning erases everything in the sdcard. So, better do it now than later when you already have all your crap in there.
Agreed! I went through your sight and it was very helpful. Thanks. I didn't realize that VS kept the same partition scheme I thought maybe with 1.2 they would have made some changes for the better. But it doesn't matter I will wipe and reformat anyway. I got the G-Tab yesterday and fired it up. WOW is it slow for a dual core. My Droid X runs circles around it...
Thanks again!
Oh by the way... I configured WiFi and I dont broadcast my SSID. I setup the G-Tab for my network and but it stated "Network out of range". So I enabled the SSID and then it connected. Everything worked just fine until I turned off the SSID broadcast again. Now the G-Tab cannot states it's out of range again. Is there anyway to force it? My other Android device and iPad dont have this issue. I hate broadcasting my SSID.
Thanks!
Hey GI,
Can you verify this step from your site? In Part D after the backup you don't want to go to Install ZIP? I skipped that because it is repeated after the wipes and that made more sense...
Thanks!
Part D (flashing a 1.2 ROM)
After backup is done, ----->>>>>>go back out and select "install zip from sdcard". <<<<<<<---------
Choose "wipe data/factory reset".
Choose "wipe cache partition".
Once it's done, go back out to root menu and choose "advanced".
Choose "Wipe Dalvik Cache".
Go back out and choose "install zip from sdcard".
Go into folder "Rom" and choose the Rom that you picked from the list. Watch it install.
After ROM installation is complete, repeat steps 6 and 7 for the GAPPS file IF YOU NEED TO.
Once everything is done, go back out to root menu and choose "reboot system now".
Well, we have a rooted and ROM'd G-Tab and man it is way more snappy. Thanks again to GI for his excellent web site. The new ROM also fixed my WiFi issue
G-Tab Rom
DroidxManiac said:
Well, we have a rooted and ROM'd G-Tab and man it is way more snappy. Thanks again to GI for his excellent web site. The new ROM also fixed my WiFi issue
Click to expand...
Click to collapse
Which Rom did you end up going with? My GTAB will be here Monday. I want to get rid of the stock sluggishness but I'd also like my first ROM to have full functionality , etc so I can check out the camera, videos and all that on my new device. Maybe after some playtime I'll jump to an HC beta that still has issues.
I've done plenty of modding and ROM swapping for the last year on my Cappy, Atrix, and Aria so I'm no noob. I would just like to jump right into the most feature rich, yet stable ROM on day one so I can really check out my new device.
Thanks!
grayfoxx said:
Which Rom did you end up going with? My GTAB will be here Monday. I want to get rid of the stock sluggishness but I'd also like my first ROM to have full functionality , etc so I can check out the camera, videos and all that on my new device. Maybe after some playtime I'll jump to an HC beta that still has issues.
I've done plenty of modding and ROM swapping for the last year on my Cappy, Atrix, and Aria so I'm no noob. I would just like to jump right into the most feature rich, yet stable ROM on day one so I can really check out my new device.
Thanks!
Click to expand...
Click to collapse
Pretty much all froyo roms listed on my site have full functionality (HW accel, video, sound, wifi, camera, etc.). And all of them can be overclocked.
With gingerbread roms, you really need to overclock to get the same video smoothness that you see in froyo because of the lack of HW accel. This is not the developer's fault. And no, it's not my fault either. The mofos NVIDIA and VS decided to stop supporting their product a couple months after they were released.
I'd stay away from the honeycomb roms if I were you. All of them are in their alpha stages right now. Even though most functions work, there are still instability issues. They're only recommended for testers right now.
goodintentions said:
Pretty much all froyo roms listed on my site have full functionality (HW accel, video, sound, wifi, camera, etc.). And all of them can be overclocked.
With gingerbread roms, you really need to overclock to get the same video smoothness that you see in froyo because of the lack of HW accel. This is not the developer's fault. And no, it's not my fault either. The mofos NVIDIA and VS decided to stop supporting their product a couple months after they were released.
I'd stay away from the honeycomb roms if I were you. All of them are in their alpha stages right now. Even though most functions work, there are still instability issues. They're only recommended for testers right now.
Click to expand...
Click to collapse
@goodintentions. I thank you to provide your useful advice.
grayfoxx said:
Which Rom did you end up going with? My GTAB will be here Monday. I want to get rid of the stock sluggishness but I'd also like my first ROM to have full functionality , etc so I can check out the camera, videos and all that on my new device. Maybe after some playtime I'll jump to an HC beta that still has issues.
I've done plenty of modding and ROM swapping for the last year on my Cappy, Atrix, and Aria so I'm no noob. I would just like to jump right into the most feature rich, yet stable ROM on day one so I can really check out my new device.
Thanks!
Click to expand...
Click to collapse
I tried three or four ROMs so far. Among them, my favorite is:
Calkulin + Clemsyn Combo Overclock at 1.5 ghz v5 (Froyo)
It is impressively fast, and the phone function works right of the box. It integrates nicely with either Google voice or Skype.
Calkulin's rom is by itself an already super fast rom. It's actually based off of the TnT. Incredible how he was able to make it work so well.
Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.
thank you.
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.
nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.
Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.
Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!
Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.
DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.
Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.
I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.
Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.
Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?
mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
dvigue said:
i have tried TSMressurection, and Powerwashed GB roms (followed the ops directions to the T)and i cannot get around all this lag. it seems after about 1 or 2 hours of using the phone i have to reboot. menues open SUPER slow, sometimes screen freezes for about 10 secs...i installed these roms thinking it would get rid of it...i am using Voodoo...
what can i do? what have you all done/used to make it run better? i have tried the supercharged scripted as well and nothing changes...
help me cause i LOVE the screen on this phone and want to keep it..
thanks
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
There is a huge debate about this, but if you are not ready for a new Kernel, you can try an app call Autokiller Memory Optimizer and set it to the Optimum setting.
This will kill apps that are eating up your RAM and over time can slow your phone. This is one simple and quick solution.
This app adjust the memory killer that is already used by the phone. This just helps it to work more efficiently.
dvigue said:
**OH CRAP, i did not realize i was posting this in the DEV section...MODS can you please move for me? thanks and sorry!!**
Click to expand...
Click to collapse
Join the club; I just did the same thing
Has anyone seen John Connor?
moved
sageDieu said:
try miui or cm7 with glitch kernel, the difference is night and day.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my Fascinate was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Relaxasaurus said:
Big plus one to this. It's like CM7 (CyanogenMod) or CM7-based MIUI should have been released for our devices from the start. I couldn't believe how smooth my device was after installing andmer's MIUI.
Here's his twitter where he links to his releases: http://twitter.com/#!/andmer_
And here's the latest release as of this post: http://goo.gl/Pja9F (includes jt's CM7 kernel) + patch: http://goo.gl/OquBU
Click to expand...
Click to collapse
oh trust me i want to be on CM7 or MIUI, but i CANNOT get around the SD mount error. i have another thread about it. i have tried everything and nothing works. i was thinking of ordering a smaller 8 gig card to try and see if its my cards, what class/type card should i get just to install and MTD rom?? i cant CM7 and MIUI bad
Where's your other thread? I had an SD Card mount error but found a fix and posted it here:
http://forum.xda-developers.com/showthread.php?t=1296694&page=2#post18859876
Let me read your thread and I'll see if it's the same issue.
here is mine http://forum.xda-developers.com/showthread.php?t=1325525
Jsut so I have the steps down:
1) You have the ROM zip file on your SD Card
2) Reboot into ClockworkMod
3) Select install Zip from SD card
4) Navigate to the Zip file
5) Install
You're saying the process breaks for you at #3 because CWM can't read your SD Card?
If the above problem is true, try using rom manager to find and flash the file. if not try a different sd card.
Sent from my MIUI SCH-i500
back to the lag issue...when running these roms are you restoring backups from Titanium. If so, are your backups from a froyo rom, that could be part of the problem if you also get force closes. I had the same problem a while back. I have also noticed if changing fonts(such as with absolute system root tools) certain more elaborate fonts can cause some lag as well. also check into the widgets you are using, even on CM7.1 i get insane lag and launcher force closes if I use Fancy Widgets but everything else is fine.
Hopefully one of those things will solve the issue...if not wipe it clean and start fresh lol but seriously hope you figure it out
after re-reading the op it really sounds like your problem could be with restoring apps, it sounds identical to when I first switched to the GB roms. You run smooth as butter for a while the it all goes to hell. I would start with wipe data/factory reset but when intalling backups try WITHOUT DATA if you still get lag, wipe again and install your apps manually from the market or where ever. I ended up going with the latter and haven't had issues since.