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
Related
This ROM is built from Cyanogen's github repositories with some additional features added by myself.
More specifically, the primary goal of this build is to test a new method for doing Apps2SD that is a bit more friendly. You can read the brainstorming thread for this process here.
The implementation is working, and there are known issues with it. I expect to make regular releases as I perfect the code. As of right now, this should be considered an alpha.
All source code is available on GitHub.
ADDITIONAL "SNACKS":
- Apps2SD w/ enable&disable setting in native Settings application.
- SD EXT partition mounted at /sd-ext
INTRUCTIONS:
You will need an ext partition on your SD card for this to work. Wipe first, flash the update, and optionally flash the Google Addon (see below). The included kernel supports ext2/ext3/ext4.
DOWNLOADS:
Version 0.2.1 - Updated 02/28/10
Download
md5sum: d9b4fb2bd79e45f28548d6241410e6e4
Google Addon ERE36B-2
Download
md5sum: 2f6a93654d1cfe191ff709b360ad60fc
CHANGELOG:
Version 0.2.1
- Bootloop fix.
Version 0.2
- Removed prompt for install location, too buggy right now.
- Added Enable/Disable setting in "Settings->Applications". Enable this to install new applications to SD, disable to install to Internal. Does not require a reboot.
- Added "Install Location" to application info (Settings->Applications->Manage Applications).
- Applications installed on SD are now also dexopted on SD.
- Full orientation hacks by optedoblivion.
- Custom "sexy nexus" LWP theme. Enable by going to the "Settings" option in the Nexus LWP.
- Anything included in CM5.0.4.1 is also in this version of SnackPack.
Version 0.1
- Initial Release
THANKS:
- Cyanogen for his feedback and for letting me bounce ideas off him.
- Wysie for sparking the brainstorming on this A2SD idea.
- Kmobs
- Optedoblivion
- And anybody else that has given me ideas and contributed to these mods.
Booting it up now.
nice! im going to have to keep an eye on this one...
sure why the hell not, anything built from cyanogen source has gotta be good and a new toy to play with too? sweet, downloading now, BTW can I flash my oc-uv kernel and have this still work?
Gr8gorilla said:
sure why the hell not, anything built from cyanogen source has gotta be good and a new toy to play with too? sweet, downloading now, BTW can I flash my oc-uv kernel and have this still work?
Click to expand...
Click to collapse
yep, just be sure to push the wlan drivers included with the oc-uv
my man chris! doing some big stuff. make it desire ROM friendly and im all over this!
Iman07 said:
my man chris! doing some big stuff. make it desire ROM friendly and im all over this!
Click to expand...
Click to collapse
that won't happen as there are too many framework changes going on
so this means each time Cyanogen updates his rom you will be updating this to match? Or once this is stable cyanogen will include it in his rom?
this is awesome- and why i bought a nexus- the development of android is flying along with this device- Google must be very happy with how all this is going...
Bug list as I can see now:
1. Installed apps from market with prompt fine.
2. Hangs up when trying to install apps from sd. (yes I have pirated apps, sue me)
3. Installed AndExplorer and Metamorph both from market, (both to sd) when starting Metamorph, it says it needs AndExplorer. Reinstalled AE and it picked it up.
4. Rebooted after morphing, and then everything I had just installed was gone.
MontAlbert said:
so this means each time Cyanogen updates his rom you will be updating this to match? Or once this is stable cyanogen will include it in his rom?
this is awesome- and why i bought a nexus- the development of android is flying along with this device- Google must be very happy with how all this is going...
Click to expand...
Click to collapse
From talks with cyanogen, theres a chance he will include it once it becomes stable (he has even hinted towards lending a hand in the development). To answer your first question, when Cyanogen updates his stuff those changes will be pulled in to this ROM as well.
ok installed linpack to sd and the scores suck, I asssume this has to do with the sd card speed, also to open linpack I had to go to market, I couldnt see it in my menu. infact no apps I chose to install to sd showed up. If I go to market and select them they say installed and I can choose to open them but without going thru this process I cant access them.
NO SH-T! THis is awesome work man!...kudos!
amazing work chris... kudos... using your snackpack for a couple of hrs now... loving it!!!! gonna try to install a hell of a lot of apps and test it out as much as I can... but so far, it's been behaving amazingly...
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/mtdblock3 148480 99228 49252 67% /system
/dev/block/mtdblock5 200960 27800 173160 14% /data
/dev/block/mtdblock4 97280 48804 48476 50% /cache
/dev/block/mmcblk0p2 467918 12895 430058 3% /sd-ext
/dev/block//vold/179:1 3334952 16852 3318100 1% /sdcard
got abt 12 apps installed (installed from market) sd-ext... and all work well... even after several reboots...
Ok, so I ussed this for a while last night and mostly it seems good, I went to my standard Cyanogen Rom, have 3 back ups, one desire, this and my Main CM5. when I tried to restore the back of this ROM it failed. My other back ups work fine. I have a Nan+ext back up of everything. I will try to reproduce it this afternoon after class.
Gr8gorilla said:
Ok, so I ussed this for a while last night and mostly it seems good, I went to my standard Cyanogen Rom, have 3 back ups, one desire, this and my Main CM5. when I tried to restore the back of this ROM it failed. My other back ups work fine. I have a Nan+ext back up of everything. I will try to reproduce it this afternoon after class.
Click to expand...
Click to collapse
why would u have a nand.+ext back up of CM 5 if it doesn't support a2sd
jroid said:
why would u have a nand.+ext back up of CM 5 if it doesn't support a2sd
Click to expand...
Click to collapse
Yes it does.
I have 224 programs installed and I have only used 12Mb of internal memory.
CM does support Apps2sd.
CM supports apps2sd but you have to initialize it yourself. You have to set up the partitions and then you have to set it up.
I'm already have old AP2SD on CM ROM, can we install only the new AP2SD on the existing CM ROM?
This is great. I am loving it.
Bump for 0.2
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!
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.
Morning guys - i'm a sort of noob (go easy.!) that needs help with my HTC desire. I took plunge and decided to try rooting & applying custom ROM, but now have problems with the screen freezing completely at any point, then on restart the phone boots into the home launcher but screen does not respond or will not wake.
So far:
Rooted with unrevoked
HBOOT flashed to Cm7r2
Latest version of clockworkmod recovery via app
Aurora 4.1 (all dalvik caches wiped at correct points).
V6 supercharger applied on setting 5 (balanced).
Tried with kernel built in ROM (0.7) & gingercakes 0.9cfs no2way havs.
SD card partitioned with GParted (fat32 primary, 2gb primary ext4).
I've had the ROM working fine, the only other thing i can place it to is swapping the SD card, which i've changed from 4gb class to, to a samsung 16gb class 6. Does anyone think that this error could be anyway caused by the fact the card readers i've used (tried 2 different readers) both have had trouble recognising the 16gb card?? (Gparted still recognised it however)
Is it possible to be a hardware issue? Please note recovery works perfectly - wiping caches, reinstalling zip files, backups etc.....only problem is now this freezing of home launcher and no response.
Any help be greatly appreciated, give me a nudge if i haven't given enough detail.
Regards, Nick.!
Additional:- Tried unsupercharging & rebooting - no difference.
Only other thing i can think that i've done prior to the fault is attempting to install busybox for V6 supercharger - which failed every time and affected my root access on the phone. I've found that the Aurora ROM has busybox installed already. However, is it possible me trying that install has somehow affected the rooting of the phone?
So many questions, sorry guys!
Bump.....would ADAO file manager (which isn't on google market I notice) affect anything on ext4 perhaps? That was one app that i downloaded from net.
Have you tried reverting your busybox to the default version? Also, are you overclocking and or overclocking? Going to high or to low with CPU speed can cause problems like that. It has also been said that partitioning an SD card can damage them, which may be an issue you have now. You could try formatting the SD card to its default state and run like that for a while. I ran a 16gb SD card in a Droid Eris for months and it never caused a problem like that. Of course, I didn't have a partition set up on it.
Sent from my ADR6350 using Tapatalk
I've literally left the settings for speed in daemon controller alone, although i'm still learning and not sure if they are default overclocked or not?
Possibility with the SD card, i'll give it a try for sure, that'd mean i'd have to revert to an alternate ROM would it, as Aurora specifies an ext4 partition?
Thanks again though, it's a start at least
Do you set profiles in SET CPU?
Accidentally sent from my Google Nexus S using XDA Premium
Excuse noobie brain here, where will i find those CPU settings?
If so, fully wipe and install again. And what rom are you using currently that causes freeze?
Accidentally sent from my Google Nexus S using XDA Premium
Aurora V4.1 ROM i'm using. Don't think it's the ROM itself as i have had it stable for week or so, before swapping SD card from 4gb to 16gb.
I'm thinking this may be the root cause as i've just tried a complete fresh partition with Gparted & fresh install of literally just the ROM itself and on first boot it froze again. Rebooted and now seems to be stable with nothing reloaded back on it but we'll wait and see. If it freezes again i'll try my 4gb card. Didn't want to revert back to that as its only class 2.
[Q] Noob help - Rooted desire keeps freezing.! Update...!
UPDATED - Still getting same problems - have now tried a different SD card & alternative ROM (Cool3d v5).
Is it possible it could be heat related fault? The more i use the phone the more readily it happens - from the occasional freeze (okay after reboot) to complete freeze and no response on every reboot.
Does the CPU therefore have a cut out or could be freezing based on the settings that are initially loaded through daemon controller? What are safe settings for the min/max values?
Only other thing i've noticed is once fault starts to occur - clearing dalvik cache in recovery is quite unresponsive - menu holds before allowing me to clear.
Got to get to the bottom of this - don't want to revert back to original, or throw my phone in the river!!
Save clock is 1ghz. No over clock is the safest.
Do your phone wear case? If yes, it may be the caused of heat.
I'm sure the rom caused you the freeze. You can try to change a more stabler rom, eg aosp
Accidentally sent from my Google Nexus S using XDA Premium
Bit more progress - as my phone literally would freeze on loading home launcher, i connected it to pc and mounted via recovery - and deleted everything i could see for V6 SUPERCHARGER - and hey presto, very slowly, but phone booted up and is now working again.
I see the devs of V6 say about removing hardtokill if any lags occur - i think it's this portion of the script affecting my bravo.
SO, i'm going to run it totally without V6, and may try to just run the memory portion, but the instructions to disable hardtokill are a little unclear to me, could you guys tell me in simple terms how to acheive??
Thanks again for all your responses, a great help
V6 now off and all fresh re-installed with cpu max turned down also, and set to ondemand gov, will see how we go
[Q] Noob help - Rooted desire keeps freezing.! PT3.!
Still no joy with this issue guys - pulling my hair out now - after a few hours use (usually overnight) phone just freezes, then freezes on reboot, before getting worse and now will not pass alpharev's boot screen.
Installing fresh gets me into home launcher, but becomes unresponsive and freezes again.
I've tried different ROM's, different SD's, basic clean install, all without any luck. I'm thinking now it is more a hardware issue with the phone?
nikh667 said:
basic clean install
Click to expand...
Click to collapse
Did you wipe data/cache partitions/dalvik cache before flashing the rom? Did you wipe dalvik cache and cache partitions after flashing the rom?
Yep all wiped before and after.
nikh667 said:
Yep all wiped before and after.
Click to expand...
Click to collapse
Have you tried flashing a new kernel?
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
nikh667 said:
Yep fault happens with any kernel I've tried (so far 0.9c no2way havs cfs, also 2way version, 0.8f cfs havs, 0.7c)
Click to expand...
Click to collapse
Has your device went through any physical damage (around the time the problem started)?
No physical damage apart from the battery cover being pulled off more than once(!) and a lot of obscenities being flung it's way, lol! But no, not dropped or damaged at all.
I've used the phone now all afternoon, longer than normally, with the same details on same hboot, but left some of the sense widgets off the home launcher, and it hasn't locked up once.