Database Users

Cyanogen Rom 6 RC1

This thread was initially an inquiry on the Cyanogen Rom however is now a Rom thread so here we go.
Background on the Rom is here http://www.cyanogenmod.com/about
On the Hd2/Leo mod see here http://pastebin.com/BBf1hr50
memin1857 said:
INSTRUCTIONS
Cyanogen Mod RC1 - Leo build by Zego WITH ADOBE FLASH and 3G WORKING
There is a new nice build called CM6-HTCLEO (Cyanogen Mod RC1 - Zeto)
It needs a lot of prep work to get to good working order, then its really good.
I have also managed to get adobe flash working. (It doesn't work out of the box)
This build
(after all the steps) have gps, camera (with proper flash exposure), camcorder, camera flash/led/torch, adobe flash, nice look and most other goodies available.
Here are the steps
1) Download cm6-htcleo.7z from:
http://www.mediafire.com/?kzo7fxi2hp917s8
2) Download phone button (keypad) fix:
http://www.mediafire.com/?qrs4w0kd470keqm
3) Download MTU fix from:
http://www.mediafire.com/?tqggvgrzb79gm24
or
http://www.megaupload.com/?d=JL368N3N
4) Download Cotulla 23 July nospeed zimage from:
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
5) Extract the cm6-htcleo.7z file and put the cm6-htcleo to your sd card root.
6) Extract the cm6-htcleo_keypadfix.7z file and put the FOLDER NAMED root UNDER cm6-htcleo folder in your sd card. (Not to sd card root folder. I really mean a folder named root. You will see it in the archive)
7) Extract the cm6-htcleo-datafix.zip file and put the FOLDER NAMED root UNDER cm6-htcleo folder in your sd card. Just merge them. (Say yes when windows asks) Credit: ElBartoME
8) Extract Cotulla_zImage_CABDET_NOSPEEDDY.rar
and put zimage file to cm6-htcleo folder and overwrite.
credit: cotulla
9) ONLY DO THIS STEP IF YOU CANNOT BOOT (linux complaining about mmcblk0): Open startup.txt with notepad and
replace the line
set cmdline "rel_path=cm6-htcleo"
with:
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
credit: dusty_nz
10) Run clrcad and haret as usual but from cm6-htcleo folder. Once Android has booted start terminal app.
11) write
su
and press enter. It will ask for superuser permission. Tap allow.
12) write
mount -o rw,remount /system
and press enter. You should not get any response or error.
13) Now launch ES File Manager and tap \ on top left.
Navigate to /system/app and find
com.adobe.flashplayer apk file and delete it.
14) Power off your phone in a normal way and reboot to Android CM6.
15) Go to Market and install Adobe Flash 10.1 Beta 3 (use your gmail account)
Done!
Notes:
-FIRST BOOT WILL TAKE A LOT OF TIME! BE PATIENT. IT WILL TAKE A LOT LONGER THAN YOUR USUAL BUILDS.
-ADOBE FLASH does not work out of the box. You have to reinstall it but since it was cooked in to the rom as system app and you can't uninstall it, you need to mount /system directory read/write and delete flash so you can install it again. This time it works properly.
-You may not be able to boot if you do not edit the startup.txt
-You may not be able to wake up if you do not replace the zimage with the older 23 july one. You can use 25 july panel on off zimage if you CAN wake up from sleep. It depends on hd2 lcd panel type which is more than one.
Optional: Install Launcher Pro and make it default home screen to get a smoother experience.
After ALL these operations, this seems like the most functional build.
Cyanogen is normally a mod for android and someone named zego turned it into a hd2/leo build. A lot of stuff was missing and there was no central infromation. That was what I did. You don't need to read 6 pages to get this build working this good now.
I recommend disabling live wallpaper. Static wallpapers are faster. Formatting sd card beforehand and using a class 6 sdhc card is also recommended.
I don't have time to package all this stuff into a build. Maybe someone who does above steps can package it in a new single file and put to megaupload/mediafire (mskip/Mark?) For now you have to do it yourself. You will like the end result.
Packagers please don't call yourselves devs and give credit to original hard working people. Donation is also recommended.
I am sorry if I forgot to give credit to anyone.
I got all this information by reading all the pages of this thread and some more. Now you don't have to.
Click to expand...
Click to collapse
From makavelitha
Good
+ Successfully booted on the first try
+ Camcorder is finally working with the original HTC app (i hope someone will port this to the other android builds)
+ Flashlight is finally working with the original HTC Flashlight App
+ No SOD or GSOD with cotullas zImage 25.07 (maybe i have a Sharp Panel?)
Bad / Problems
- Bad Performance (especially at scrolling)
- Can't Download anything from the Market, i get always the message that my Storage Card is full, i've checked it and android shows me 0mb left on my SD Card, but i have more than 4GB free on this Card (it was working in all other Android Builds)
- Needs time to boot-up
- No or Bad Battery Management (already optimized in other Android Builds)
- USB Storage not working (already working in other Androids)
- Bluetooth finds other devices but can not be paired
- Compass works but it doesn't show magnetic north.
- Low volume issue is already known. During a call other party hears echo of his own sound when speaker is on. No echo in normal mode.
Performance Tweaks
Update I:
Using Cotulla zImage 7/25/10 makes a huge difference in speed!
The only thing still sluggish is scrolling through the apps....
Otherwise from that this is a very good build. Nice pre installed apps, good out-of-the-box build.
Update II:
Changing the application drawer to "Horizontal" like on the Galaxy S eliminates scrolling speed issues when scrolling through the apps.

dusty_nz said:
So looking at the Cyanogen rom, Swapping out the Zimage and trying to boot.
Has anyone tried this?
Would it work?
Looks like it has heaps of Qualcomm optimized components
Click to expand...
Click to collapse
http://www.mediafire.com/?kzo7fxi2hp917s8

And don't forget to add the phone button fix:
http://www.mediafire.com/?qrs4w0kd470keqm

any changelog of this mod/port ?

Readme:
http://pastebin.com/BBf1hr50

on this build flash doesn't work for me in the browser.

I am running it at this moment, it boots correctly until android froyo wizard.
It runs correctly for a minute and SOD
Ah it wake up, great
For the first time in the leo android world, the camera works
I give you more feedback later ...
Update:
- GPS works perfert
- Reboot not work, like other builds
- Import contact from SD not works
perhaps the one based on RC2 will be better, where have you find the links for this build ?

I can't get this to boot.
Initrd keeps looking to mount /mnt/sdcard against /dev/block/mmcblk0p1 and falling over. I only have the one FAT32 partition on my sdcard which normally is at /dev/block/mmcblk0.
Also should I be extract the .tar.gz file into the CM6 directory or put it up at the root of the sdcard.
Thanks.

idcom said:
I can't get this to boot.
Initrd keeps looking to mount /mnt/sdcard against /dev/block/mmcblk0p1 and falling over. I only have the one FAT32 partition on my sdcard which normally is at /dev/block/mmcblk0.
Also should I be extract the .tar.gz file into the CM6 directory or put it up at the root of the sdcard.
Thanks.
Click to expand...
Click to collapse
Try replace cmd cmdline
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"

m4ck said:
Try replace cmd cmdline
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
Click to expand...
Click to collapse
Thanks. Worked a treat. Now to play.

Nuja said:
any changelog of this mod/port ?
Click to expand...
Click to collapse
Yeah I agree guys, can you please be a bit more specific about what is additional from other froyo with/witout sense or Eclair?
readme file does ntoe give much in fact.... A couple of screen shots would be fantastic...;-)
general statement: Donate, so all mods/chefs/devs can eventually pay some flowers or perfums or sex toys to their girls friends (all of them so angry that they spend so much time developing stuf !!!)

Well.... more info on what cyanogenMod is on:
http://www.cyanogenmod.com/about

Anyone having problems with 3g on this build?

nordicfastware said:
Well.... more info on what cyanogenMod is on:
http://www.cyanogenmod.com/about
Click to expand...
Click to collapse
Thank you, but there is no mention of build for our HTC HD2
Who is the maker of this build for HD2 ?

the build is done by Zego from the IRC channel compiled from source of CyanogenMod 6.0.0 release candidate 1
I tried it last night and it gives me SOD repeatedly, it's fast, but the SOD is killing me, I am falling back to Darkstone's FroyoV1

Hmmmm
Not booting for me.
Formatted a SD card. Single Fat32 partition.
Extracted zip to \cm6-htcleo\startup.txt etc.
Changed the Startup.txt to
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
error
/init: line 88: mmcblk0=mmcblk0: not found
Logical sector size is zero
mount: mounting /dev/block/mmcblk0 on mnt/sdcard failed: invalid argument

lucian777 said:
Anyone having problems with 3g on this build?
Click to expand...
Click to collapse
Yes. I had the same with Dan's Froyo v.1 but Darkstones works a treat. Changed the apn's to voda uk and all that.

booted first time - took a while but OK
Loaded with apps
camera working
Video recorder working
GPS working
man it's fast..........
will test further and report back

dusty_nz said:
Not booting for me.
Formatted a SD card. Single Fat32 partition.
Extracted zip to \cm6-htcleo\startup.txt etc.
Changed the Startup.txt to
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
error
/init: line 88: mmcblk0=mmcblk0: not found
Logical sector size is zero
mount: mounting /dev/block/mmcblk0 on mnt/sdcard failed: invalid argument
Click to expand...
Click to collapse
took out the set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0" ands its booting further. Got wizard

I for one am excited for this development. The collaboration from the devs here along with cyanogens work is fantastic. Any chance of getting cyanogen directly involved and/or once a build is completed would an official thread on this be desired?
I am not a coder but I'm working on it. Until then I'm just a fan and a donor. I've been a long term user of cyanogens work and I can safely say with the joint efforts of everyone here, this would be a powerful development. Keep up t the awesome work!
-------------------------------------
Sent via the XDA Tapatalk App

Tayutama One Click Lag Fix!!!

********Please Mods remove thread if possible!! New Tatuyama fix (ext4) has been incorporated into SuperRooter by DesignGears ********
LINK: http://forum.xda-developers.com/showthread.php?t=751934
DISCLAIMER
DO IT ON YOUR OWN RISK.
ME OR ANYONE ELSE ON THIS FORUM IS NOT RESPONSIBLE FOR BRICKED/DEAD DEVICES AND/OR DEAD SD CARDS.
YOU SHOULD UNDERSTAND EVERY STEP IN THIS HOW-TO BEFORE ATTEMPTING TO FOLLOW.
**********EDIT LOG*******************
8/10/2010: Added Startup Issue Reversion
8/11/2010: Added Alternate Manual Method that might work better than AUTO
8/11/2010: Added Possible Method of Backing EXT2 Partition
Here everyone... I have been trying lag fixes all over the place and I always seem to have issues partitioning the external sd for the apps... so after so many attempts, this was BY FAR the best lag fix out there.... It doesn't rely on the externalsd for functionality.
Easy and nothing special needed.
The steps below are pretty good, but I did things a little different.
Copied the update.zip to my external sdcard.
Then used Root Explorer to copy the update.zip to my internal sd card.
(******Here is the updated filed: http://forum.xda-developers.com/attachment.php?attachmentid=376882&d=1281390347******)
Then I used ROM Manager (Reboot into Recovery) to boot into the Linux Loader
Then I said update using update.zip (not install update.zip)
Then Reboot
For some reason it didn't install busybox 1.17.1 so install it manually
(located: http://forum.xda-developers.com/showpost.php?p=7574130&postcount=229)
Make sure after you install busybox.apk that you go into busybox and check to MAKE SURE you are running 1.17.1 ONLY. You might have an older version or newer version but it must be 1.17.1; if different just click install.
After that follow the MCR Scripts below. (Took about 6 minutes to do everything)
*** If MCR Scripts DOES NOT show up, its probably because you don't have the non market install hack on your phone. In the update.zip you can find the apk and install via ADB, but I didn't do it this way. ******
(Original Thread! Alternate method on OP in link below! Some people say it worked better for them.)
http://forum.xda-developers.com/showpost.php?p=7587405&postcount=417
@Tayutama
I ran the Tayutama update.zip using the up+power+menu button method, it installed in seconds and I restarted the phone. I ran the benchmark but still got 8xx scores. I'm an Noob, so needed more thorough instructions. These are now given below. NOTE: THIS METHOD IS MUCH MORE NOOB FRIENDLY AND DOES NOT REQUIRE A PC OR USB DEBUGGING MODE.
EDIT I had realised I needed to launch the newly installed MCR app after restart and choose a lagfix file to run. I ran the file and 'all complete'. This worked a treat. Ran Quadrant and now have a top score of 2114 running on JM2. System is much snappier. This mod of RyanZA fix by Tayutama is the most noob friendly also. Full instructions as follows:
EDIT Requirements: Make sure your phone has 'superuser' app installed by checking your app list. If it isn't installed, you can use a newer beta version of Tayutama's update.zip
available at; http://forum.xda-developers.com/atta...4&d=1281437129
Full instructions:
1. The update.zip installs all the files needed. It is attached here; http://forum.xda-developers.com/atta...2&d=1281390347
2. Place it on your internal sdcard
3. Turn off your phone.
4. Hold down Up+powerbutton+Menubutton for a couple of seconds until u see the galaxy logo .
5. Use the up and down buttons to get to update.zip.
6. Press menu button on update.zip to select it
7. It installs root, correct busybox (1.17.1) as well as all the scripts needed for the fix and the 'MCR Scripts' app to run the scripts. (NOTE: This version does not install superuser.app which is needed, although the beta update.zip does, so read 'requirements' above if needed)
8. After install, the phone restarts.
9. Go to the newly installed 'MCR Scripts' application from the app list, open it and choose from 3 scripts. For example, Lagfix10024 is the 1gb ex2 version.
10. The script should run and take a few minutes.
11. You should see an 'all complete' prompt, and this means you can close the application.
12. Run quadrant to test if the fix was applied.
Originally Posted by Tayutama
Don't know if you mind me posting this here RyanZA, but i made a update.zip out of your script. NOTE THIS ONLY WORKS ON 2.1
What this update.zip file does is that it copies a few files to your internal sdcard and installs ASE which can be used to run .sh files without the need to use a terminal.
There are 3 scripts included:
LagFix1024.sh - Makes a 1GB file on /data
LagFix512.sh - Makes a 512MB file on /data
RemoveFix.sh - Removes the lagfix
This also includes BusyBox 1.17.1 so no need to install that first.
Testet this on JM1
Click to expand...
Click to collapse
********Alternate Method that might even work better!! ****************
All the files are located in the update.zip file that you need to download.
1. Connect phone to PC, make sure adb can see it:
adb devices
2. adb kill-server
3. adb push createlagfix.txt /sdcard/createlagfix.sh
4. adb push playlogos1 /sdcard/playlogos1
5. adb push userinit.sh /sdcard/userinit.sh
6. adb shell su -c "/system/bin/sh /sdcard/createlagfix.sh"
7. adb kill-server
8. adb reboot
************ Reverting back if there are boot up and black screen issues ****************
If you have black screen and doesn't boot into the desktop, this is the fix to return back to normal state:
To fix that problem:
1. Boot into Recovery Mode (Vol Up + Vol Down + Power) Let go of Power after you see AT&T.
2. Delete User Cache
3. Delete All User Data
4. Then see if your phone boots up
5. If your phone does boot up then navigate to Settings -> Security -> Factory Reset
6. After factory reset your phone should be useable again.
DO NOT INSTALL THIS UPDATE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
**********Possible method of Backing up Your EXT2 Partition **********
BTW I would also perform a NANDROID Backup as well which can be done by using ROM Manager to boot into the Android Loader....
Nandroid does NOT back up the apps off your SD card.
AppsToSD (I'm speaking re MoDaCo's rom here) uses the ext2 partition on your SD card for the /data/app and /data/app-private folders, where your actual downloaded application files are kept. Nandroid does NOT back this up, and simply mounting your SD card and copying the files off also does not back this up.
The only way to back up these critical folders is to directly copy them to somewhere else. You can use command line or Droid Explorer.
If you want to use command line, do this from an ADB shell or terminal:
mkdir /sdcard/backup/
mkdir /sdcard/backup/app
mkdir /sdcard/backup/app-private
cp -r /data/app/* /sdcard/backup/app/
cp -r /data/app-private/* /sdcard/backup/app-private/
This will create two folders on your SD card: app and app-private, both in a folder called Backup. It will then copy the entire contents of your /data/app and /data/app-private folders to your SD card.
After you do this, back up the entire contents of your SD card as normal.
To restore the files after replacing/partitioning your SD card, head to this thread:
http://forum.xda-developers.com/showthread.php?t=585349
Click to expand...
Click to collapse

Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6

slider2828 said:
Quadrant score was 917 and was on stock roms.....
Now Quad score is 2193 and still on stock roms.....
Tested on 2.1 Update 1 Captivate
Baseband: I897UCJF6
Click to expand...
Click to collapse
Does it show strong real world improvements?

good job explaining nothing. troll harder

So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.

This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.

Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.

hm... i applied the update in clockwork mod recovery, i have super user and the correct busybox version installed and rebooted the system. i went to the app list and could not find the "MCR SCRIPT" you mentioned i should be seeing... am i doing something wrong?

THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....

solufein said:
good job explaining nothing. troll harder
Click to expand...
Click to collapse
What the hell does that mean.... You saying it doesn't work? Why not try it and it is an EXT2 fix.
max_warheads said:
So....
This is a ""one step"" that isn't one step... ?.. ?
Oh, and for anyone wondering....
This appears to be the ext2 fix.
Click to expand...
Click to collapse
This isn't one step because I don't have the USB cable with me. I just had a USB adapter for the microsd and I can't boot into the linux loader correctly without the cable, so I used ROM Manager. It would have been easier if I did.
Zilch25 said:
This IS the same fix from the otger thread, just packaged in update.zip format. Id be a bit more cautious using this one as it hasnt had as much testing among the I9000 crowd much less Captivate users.
Click to expand...
Click to collapse
Yup it is but on the internal card. Are you sure its the same? Look at the OG thread, a LOT of people have tried it with great success....
darth_vato said:
Thanks for confirming this. I am seeing strong real world improvements, too. Dolphin Browser HD is very snappy and everything seems a lot faster (I am on stock captivate, btw, couldn't get this to work on I9000 for some reason).
Only thing is you should back up frequently because it can be corrupted a lot more easily since it is on ext2.
Click to expand...
Click to collapse
How do you back it up?

i updated the zip and rebooted used busy box and i dont have that MCR app

Bionicboto said:
i updated the zip and rebooted used busy box and i dont have that MCR app
Click to expand...
Click to collapse
Same instructions before, did you download the update.zip? I just added that instruction. Can you try again after that?

slider2828 said:
THat is weird I saw mine in the apps list.... its just called MCR with a green dog bowl and light bulb....
Woops sorry for the truncation in the quote.... I have attached the update.zip file that you need to download.... The update.zip file you used is probably a ROM Manager Update.zip, so just rename it and copy the new update.zip file to the internal sd....
Sorry.....
Click to expand...
Click to collapse
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.

its still the same cant find the app i reboot to recovery apply sd card update.zip go to yes and it says installed reboot and its not there

arsinic said:
when you say put the update.zip into the phone... do i put it in the internal sd card root? or do i put it in the ROM MANAGER folder? when i choose apply update, it only gives me one option to update from: /sdcard/update.zip. i choose that it installs properly and i reboot. i still don't the app, lol.
i also have removed the the recovery-update.zip or renamed it and tried to reboot into recovery mode via ROM MANAGER but it doesn't let me do it because it can't find the zip. then i tried to put the update into the the ROM MANAGER folder and it says it can't the find update.
Click to expand...
Click to collapse
Sorry for the bad reply.
Rename the update.zip that is already on the internal sd cards root because that is ROM Managers using ROOT Explorer
Then copy the update.zip that you downloaded to the external SD card.
Then copy update.zip from the external sd card to the internal sd cards root.
Then use ROM Manager to reboot into the linux loader.
Hope that helps?
-Ken

slider2828 said:
Sorry for the bad reply.
The update.zip that you use download, copy it the the internal sd card's root... (Basically where ROM Manager update.zip was. Like you did Rename the update.zip that is already there, because that is ROM Managers).
Hope that helps?
Click to expand...
Click to collapse
hm... the only update.zip i have is in the Recovery Mod folder named: recovery-update.zip. the only update.zip i have in the sdcard root is the update.zip i downloaded from the your url and have been applying that as the update. i seem to be having the same problem as Bionicboto.
should i have the rom manager's update.zip in there also or it doesn't matter? and i also have no external sd card. is that something i need in order to get this update working properly?

Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Basically when I log into root explorer and click on SDCARD.... you should see the update.zip in that folder along with Android folder, busybox folder, clockworkmod folder, DCIM folder, downloads folder, etc etc....

slider2828 said:
Did you ever perform a backup with the ROM Manager? That usually creates a update.zip.....
Click to expand...
Click to collapse
i preformed a backup right before i did all this. i did notice the update.zip in there. i took it out and put in the update.zip you uploaded. do i need both in there?
thanks for the quick replies btw.

Nope... Try this... with ROM Manager,
Choose Flash ClockWorkMod Recovery and that will recreate the boot files for ROM Manager.... and also backup your current ROM again.
Then try the steps again.
OMG Dude I noticed you in oakland, I am in hayward/san leandro.... We can try after I get off work which is in 30 minutes. and then take 30 minutes to get back to SL....
You wanna meet at the starbux on marina?

Flashed and installed perfectly. Bumped my quadrant up to 2117. Good post, thanks.

[n00b] SETCPU bootloop cure -No need to Nandroid Restore-

Just sharing some info for noobs.
So you set your CPU to 1.22 Ghz and checked 'set at boot'. You enjoy your 10% speed increase until suddently you get a random reboot. You know it is because you set the CPU too high (for your phone, every phone is differnet) so you wait for it to reboot so you set it back but then BAM! another reboot. Now Sh!t hits the fan because of the 'set at boot' flag has been checked. You didn't do a nandroid backup recently or you don't have any set up. What to do??
I found this on android developers forum and thought I should share this in an OP because it's very valuable for us overclockers.
Basically, to remedy this, you need to delete the SetCPU config file from the internal memory. To do, follow this:
1) Boot into recovery
2) Connect USB
3) open ADB shell - 'adb shell'
4) mount the Data folder - 'mount /data'
5) navigate to the Data folder - 'cd /data/data'
6) Remove the config file - 'rm -r com.mhuang.overclocking'
7) exit and reboot phone
Now you should be all set. SetCPU is now in its default form.

havn't needed this yet but very useful for everyone who does need it
good job

Nice find bro, wish I would have none this a few weeks ago

Awesome. Thank you

Or, if easier, you can just pull the SD card, and put a text file named 'setcpu_safemode' in the root of the card, then reinsert and boot. The dev added that feature a while back.

Thanks man, first day owning my droid inc, and I'm a little too used to cranking my old moto droid up all the way without consequence. I don't even need the little scosh of a speed boost I'm just always effing with things. Oh well lesson learned, no harm no foul.

Shushunmire said:
Or, if easier, you can just pull the SD card, and put a text file named 'setcpu_safemode' in the root of the card, then reinsert and boot. The dev added that feature a while back.
Click to expand...
Click to collapse
Thanks this worked perfectly!

i Found an app i hate setcpu piece of garbage spent an hour fixing my phone found this and it worked

wyllem said:
i Found an app i hate setcpu piece of garbage spent an hour fixing my phone found this and it worked
Click to expand...
Click to collapse
Don't blame SetCPU for the fact that you didn't know what you were doing. That's not the app's fault, it's yours.
(from... Evo/MIUI/Tapatalk)

Ok, played with setcpu today, for the first time, and after awhile set the orevclock to max and now the phone reboots everytime I try to open anything. I found this thread and put the .txt file on my sd's root, but it didnt help. I am using amon_ra and cant figure out how to try the other method with it. Can someone please help me out.
Update, I made another .txt file and this one seemed to work, but I now see there is a flashable .zip you can extract in setcpu itself.

Err...there's a failsafe built into setcpu. It places a file on your sd to flash in the event of a bootloop.
Simply look in the setcpu settings for it.

You could also mount SD card from recovery and do it that way
Deck's + SZ + SuperCharger script + ViperMod script.

New to NC; Whats the hot setup?

Hey all!
I am new to the NC community, but have quite a bit of experience working with my Samsung Fascinate. I have some minor themeing experience.
Just ordered a NC from ebay for 119 and was curious what sort of setup (ROM, KERNEL) etc are stable and working well?
What OC is stable?
Is Honeycomb worked out as fully functional?
I have done some sticky reading, and I would like to just make a bootable sdcard, and leave the Emmc alone for now.
What are the recommendations?
Thanks!

CM7 is definitely the best for this. Honeycomb did not have access to the sources and so was more of a demo.
We hope that ICS may make it onto the NC one day but for now CM7 gives a really good stable experience.
You can choose to use the latest stable CM 7.1 or choose to use one of the late nightly builds. There has been an issue with what is called SOD (Sleep of death) where the device occasionally doesn't wake up from sleep and needs a reboot. This was an issue even with 7.1 on some devices. It now appears to have been solved but requires an extra patch which should make it into a nightly soon.
Installing onto a boot SD or emmc is both easy tasks and there are plenty of guide material on this. If you are going to boot from SD make sure you use a Sandisk card (e.g. a class 4 16 or 32GB). These give much better performance when used in this role over other brands.
If you end up primarily using CM7 and not reverting to stock then I would say it is worth going full emmc. It is easy to revert to stock if you ever need to. Running from emmc gives more overall memory and makes management and back up more straightforward.
Most Nooks OC fine up to 1300 and remain stable. The boost in performance is fairly dramatic. For some reason some graphics benchmarks peak at 1200MHz and get worse if the OC is pushed higher. I guess the GPU may end up clocking lower if the main clock is pushed too far.

Thanks BOB!
I had used CM7.1 on my fascinate, but it was a short stay as it wouldn't play nice with wifi at my house. Hopefully that's not the case with the NC.
How is MIUI on the NC? From what I see it has done pretty good. Do you have any particular experience with it?
As far as kernels, what are the stable ones by name?
I have plenty of experience of writing ROMS to the internal memory with CWM so I shouldn't be too far off if I need to do that, or choose to go that route.

If you use cm7 can you still use the stock Nook Reader? or what is the reader of choice?

I believe you can only use the Stock reader in the Stock ROM. There is a standard Nook App for Android but it is not the same. Works OK for your standard reading etc but not as nice as the stock reader.
If you want to use the Stock Reader and CM& then I think your choices are ...
1) Run CM7 on the SD card and boot into Stock whenever you want to use the Stock reader.
2) Make a Stock ROM set up on a SD card, Install CM7 on emmc and reverse the procedure of 1.
3) Install a dual boot Stock and CM7 off the emmc. At start up you then choose whether to boot into Stock or CM7 and the SD card remains fully usable as data.
I did use method 3 for a while when I first started with Nook but I so rarely went into stock and I don't really need to access the stock reader that I gave up and redid the emmc as full CM7.
I did try MIUI out but I ended up reverting to standard CM7 really just to keep compatibility with other CM7s I use.

Advantages of Internal Dual boot over SDcard boot?
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles

charles_w said:
Been running CM7 off an SDcard for almost a year...
Considering moving too a dual boot internal setup stock 1.4.2 + CM7.2...
But not really sure of the advantages/disadvantages of dual internal vs. emmc stock + CM7 on the sdcard.
The only thing I can think of is that dual internal would allow bot stock and CM7 to use my new 32GB SD card...though I haven't decided if that's an advantage or disadvantage
I do want to keep stock around for the kids books, read in store...plus at least with the old version of CM7 I was using the Nook app didn't do well with my magazines.
Appreciate any guidance!
Charles
Click to expand...
Click to collapse
I personally would stay away from dual booting on emmc. It plays with your internal partitions which is not a good idea. I would keep stock on emmc and the newly released 7.2-RC1 on SD. By making one simple change to stock you can have both systems share the 32GB card and not have to take the card out ever. The boot menu of CM7 makes it very easy to boot between the two.
Sent from my Nook Color running ICS and Tapatalk

Thanks for the reply.
leapinlar said:
By making one simple change to stock you can have both systems share the 32GB card
Click to expand...
Click to collapse
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles

charles_w said:
Thanks for the reply.
Don't suppose you happen to have a link to a post that describes that one simple change do you?
Hope to hear from some others...as it seems many use the dual boot internal...so there must be some advantages for certain scenarios.
Charles
Click to expand...
Click to collapse
It does have advantages, you don't have to worry about SD card switches, etc. I was just saying it is non-standard and risky to your partitions. One of the partitions, (2) is vital to your system (it has your serial #, etc in it) and since you have to write to the partition table to accomplish dual boot, you risk the possibility of corrupting it as you are setting up dual boot. But a lot of people have done it with no problem.
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file. But there are plenty of rooting threads that tell you how. You can even unroot after you have fixed the file if you want. The other way is to change the file on your PC using adb. Both methods take a little extra effort, but it is worth it to not have to swap SD cards all the time. Both systems then share the SD card storage area. By making this change, I know of no advantage to dual boot and it is much safer (and you already have the SD set up).
And you use the boot menu to select which operating system you want to boot to. That comes with CM7. (But you know that having run CM7 for a year).
Sent from my Nook Color running ICS and Tapatalk

found the link for sharing sdcard
leapinlar said:
I don't have a link on how to make the change. It is a very simple change to one file. There is a text file in /system/etc named vold.fstab. In it there is a line that contains 'sdcard auto' in it. Change that to 'sdcard 4'. (without the quotes.) Now the hard part. You have to be rooted on emmc to have access to the file.
Click to expand...
Click to collapse
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles

charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmx to be rooted.
Charles
Click to expand...
Click to collapse
good job!
Sent from my Nook Color running ICS and Tapatalk

charles_w said:
Found it, http://forum.xda-developers.com/showpost.php?p=13668471&postcount=529
and it doesn't even require emmc to be rooted.
Charles
Click to expand...
Click to collapse
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
Seems the File Expert feature to mount system as read write is no longer included in the free version. Is there a terminal command for that?
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
The free version of ES Explorer allows mounting system as r/w.

Little update....
I have found that the best setup I have found so far is CM 7.2 RC1 (03042012) with V6 (Update 9 RC6.9) supercharger set to option 9 (super 1000HP) supercharge (link for the V6 is on Mr666's page). The ICS transitions included in RC1 are swift and with the supercharger everything is super smooth. I can say I have noticed a small increase in my battery life as well. I toyed around with the UV/OC settings and returned to the sleep of death's I was getting on 7.1. So I re-flashed and just have left everything set to default in the peformance settings that comes with 7.2. So far, no SOD"s and I have a very capable tablet.

leapinlar said:
The free version of ES Explorer allows mounting system as r/w.
Click to expand...
Click to collapse
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
When I set the option in ES Explorer, I get an error message that it failed to mount r/w. Possibly this is not possible without rooting emmc. In terminal I can't make the Nooksys folder.
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
You don't need to mount it where racks said. You can mount it in /data, which you should be able to make r/w. Where it says /mnt/nooksys, substitute /data/nooksys. First go to /data with es explorer and manually create the nooksys folder (you need to set your home directory to / in es explorer before you can see /data). Then follow his steps except don't do the mkdir command since you did it manually. And wherever it says /mnt substitute /data.
Edit: you need to modify the mount command, it now needs to have appended to the end, -t ext4. - Scratch that. It's only necessary if you are trying to do it from CM9. CM7 works OK as written.

I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2

Sherip said:
I created nooksys in data with ES. In terminal I tried:
$su
# mount -o /dev/block/mmcblk0p5 /data/nooksys
and it returns
mount: not found
Any idea how to fix?
I have cm7.2 RC-1 on SD (verygreen but boot partition was resized) and stock 1.42 on emmc (untouched except by b&n)
Sent from my NookColor using Tapatalk 2 Beta-2
Click to expand...
Click to collapse
What is the -o in the line for? And you manually created the folder first? And you did check the root button in settings?

All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"

Sherip said:
All the options for Root Settings in ES File Explorer are checked. I have / set as the home directory. I created a folder named nooksys manually inside /data using ES. I closed ES and started terminal. I'm not sure what the -o is for, I found it in some other posts and I guess I was just trying to fix it myself, but the error message
mount: not found
is the same with and without the -o
Edit: also the version of ES File Explorer is the latest version per "Check Now"
Click to expand...
Click to collapse
After you created the folder, did you check it. By that I mean open it? It should be an empty folder. Exit out of the folder, but leave Es explorer open. Use the home key to get back to home screen so you can open terminal. I don't know much about es, maybe it has to stay open to keep root access.
Edit: the :not found error is saying it cannot understand the mount command. Are you using all lower case? Very important. Terminal does not like upper case.

Thread closed.

Thread closed.

Thread closed.

Yank555 said:
Hi,
REMEMBER
FIRST OF ALL, do a Nandroid backup, as well as a backup of your sd-card content !
You're doing this at your very own risk, I'm not to be held responsible if something goes wrong
Now that said, let's get going
In case somebody wants to check it out, here is the swap activation script I wrote (attached) as well as explanations on how to make it all work :
1) Partition your sd-card (Minitool Partition Wizard, 4ext, CWM...)
2) Boot your system with the partitionned sd-card
3) If necessary customize the 99swap script (attached to this post) and then put it onto your sd-card's root folder, you'll need it while executing the commands in step 4.
4) Open a terminal and type the following
NB: Change "mkswap /dev/block/mmcblk0p3" accordingly to point to the swap partition you've created in step 1.
5) Reboot your phone, start a terminal again and type free, you'll need to see something different than 0 in your swap line, look at the attached print-screen
Swappiness will be set to 50 by the script, which is a rather conservative swap use, made sense to me since SD-swap is slower than ram, better not to use it too agressively. Feel free to experiment with the swappiness variable in the script (values between 0 and 100, 0 meaning "try not to swap", 100 meaning "try to swap all the time")
If you want to try and have a question, just let me know !
JP.
PS: You can find the thread for hard swap for the htc Sensation / XE here.
Click to expand...
Click to collapse
Hi JP,
This is a gem of a post! Thanks alot for the script and the detailed breakdown. Before I get into it though, I must warn you that I am more of a beginner with no coding/scripting experience (I don't know how to use adb or anything)...
Here's what I'm trying to do: I'm trying to activate hard-swap on my hd2 (currently) running the ParanoidAndroid by Xylograph. I've created 3 partitions on my 16gb class 6 sd card: first, fat32 (32k cluster), next, 1GB ext2 (default), 500MB swap.
Procedure:
1. I extracted the script and copied it directly to system/etc/init.d folder of the Rom (I looked at the terminal commands you posted and the first few lines looked like copying the file from the sd root to the init.d folder (it was just a guess though), so I figured might as well put it into the rom before I flash it)
2. Flashed the rom
3. To activate it, I typed the following into the terminal:
su
mount -o remount,rw /system
mkswap /dev/block/mmcblk0p3
mount -o remount,ro /system
exit
after the mkswap command, I did get an activation notification that a certain amount was assigned to swap. But my celebrations were cut short after I rebooted and used the free command to check. The entire swap row still read 0.
I was wondering if you can point me in the right direction... thanks!
Also, is there a way to create a cwm flashable version?

bullcrapr said:
Hi JP,
This is a gem of a post! Thanks alot for the script and the detailed breakdown. Before I get into it though, I must warn you that I am more of a beginner with no coding/scripting experience (I don't know how to use adb or anything)...
Here's what I'm trying to do: I'm trying to activate hard-swap on my hd2 (currently) running the ParanoidAndroid by Xylograph. I've created 3 partitions on my 16gb class 6 sd card: first, fat32 (32k cluster), next, 1GB ext2 (default), 500MB swap.
Procedure:
1. I extracted the script and copied it directly to system/etc/init.d folder of the Rom (I looked at the terminal commands you posted and the first few lines looked like copying the file from the sd root to the init.d folder (it was just a guess though), so I figured might as well put it into the rom before I flash it)
2. Flashed the rom
3. To activate it, I typed the following into the terminal:
su
mount -o remount,rw /system
mkswap /dev/block/mmcblk0p3
mount -o remount,ro /system
exit
after the mkswap command, I did get an activation notification that a certain amount was assigned to swap. But my celebrations were cut short after I rebooted and used the free command to check. The entire swap row still read 0.
I was wondering if you can point me in the right direction... thanks!
Also, is there a way to create a cwm flashable version?
Click to expand...
Click to collapse
Thanx
In fact you understood correctly that is was about copying the file to init.d.
By the way, these commands do the following :
mount -o remount,rw /system - Mount system partition in read-write
mount -o remount,ro /system - Mount system partition in read-only
So to format the swap partition "mkswap /dev/block/mmcblk0p3" there was no need for it, but it didn't harm in any way, so you're fine there
I guess what is missing is the "chmod 755 /system/etc/init.d/99swap" command which will set the correct file access to the script so it can get executed at boot.
You might do the following in a terminal :
su
mount -o remount,rw /system
chmod 755 /system/etc/init.d/99swap
mount -o remount,ro /system
exit
It should be fine then.
Alternatively you could set the rights with your file explorer (in root explorer mode), they must be "rwxr-xr-x" (which is Read-Write-Execute, Read-Execute, Read-Execute), most file-manager will allow you to do that as well.
I've been working on the script variant for htc Sensation, it is more advanced, dynamic so it can find the swap partition by itself.
I'll make a CWM flashable as soon as I get to it that will handle everything except partitioning the SD card, obviously, for both devices.
As soon as I'm done I'll post the HD2 version here as well (very little change, between both devices, just the access path to the sd-card partitons to change (=1 line in the script).
JP.
Edit ------------------------------------------------
I just reread your post, if in fact you put it into the ROM zipfile, then file access should be correct !?
Could you post the following file (if it exists) :
/data/swap.0.log ?
JP.

Yank555 said:
Thanx
In fact you understood correctly that is was about copying the file to init.d.
By the way, these commands do the following :
mount -o remount,rw /system - Mount system partition in read-write
mount -o remount,ro /system - Mount system partition in read-only
So to format the swap partition "mkswap /dev/block/mmcblk0p3" there was no need for it, but it didn't harm in any way, so you're fine there
I guess what is missing is the "chmod 755 /system/etc/init.d/99swap" command which will set the correct file access to the script so it can get executed at boot.
You might do the following in a terminal :
su
mount -o remount,rw /system
chmod 755 /system/etc/init.d/99swap
mount -o remount,ro /system
exit
It should be fine then.
Alternatively you could set the rights with your file explorer (in root explorer mode), they must be "rwxr-xr-x" (which is Read-Write-Execute, Read-Execute, Read-Execute), most file-manager will allow you to do that as well.
I've been working on the script variant for htc Sensation, it is more advanced, dynamic so it can find the swap partition by itself.
I'll make a CWM flashable as soon as I get to it that will handle everything except partitioning the SD card, obviously, for both devices.
As soon as I'm done I'll post the HD2 version here as well (very little change, between both devices, just the access path to the sd-card partitons to change (=1 line in the script).
JP.
Edit ------------------------------------------------
I just reread your post, if in fact you put it into the ROM zipfile, then file access should be correct !?
Could you post the following file (if it exists) :
/data/swap.0.log ?
JP.
Click to expand...
Click to collapse
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?

bullcrapr said:
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
Click to expand...
Click to collapse
Hi,
You're welcome
The file '/data/swap.0.log' is a text-file containing info on the execution of the script...
If it's not there, then the script didn't run at all...
I should have a little time later today, will try to make the CWM flashable solution for you, should be a no fuss solution, as long as the sd-card has a swap partition
How did you partition the card ? CWM ?
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium

I created a 256Gb partition...
Click to expand...
Click to collapse
man thats a helluva sd card ya have there! hehe.

samsamuel said:
man thats a helluva sd card ya have there! hehe.
Click to expand...
Click to collapse
Haha I noticed that too :') I want one of those now

Nigeldg said:
Haha I noticed that too :') I want one of those now
Click to expand...
Click to collapse
Thanx for pointing that out Mb of course, but in a few years that might be possible
My first hdd had 60Mb, and that's not soooo long ago
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium

heh, my first was a 20mb HDD mounted on a pcb card and plugged into an ISA slot, took up the full length of the PC, weighed LOADS, could have beaten burglars to death with it.

bullcrapr said:
Hi JP
You are incredibly helpful and I appreciate it!
I finally got some time off and tried out what you mentioned... but to no avail. I applied the necessary permissions through the terminal (chmod 755) as well as through the root browser, but it was still the same. After that I even retried the terminal commands, and included the "chown 0:2000...", but that didn't work either...
... and then I saw your post update...
About that, i just typed it into the terminal, and I got "not found".
Was that what I was supposed to do?
Click to expand...
Click to collapse
+1 with this (also on Paranoid Rom 1.1a) but I think that it's something with the ROM coz on earlier build v1 this method worked verry good I hope that Yank will find a solution coz it reallly helps wit our 576 ram

samsamuel said:
heh, my first was a 20mb HDD mounted on a pcb card and plugged into an ISA slot, took up the full length of the PC, weighed LOADS, could have beaten burglars to death with it.
Click to expand...
Click to collapse
Mine was huge at the time, was on of the first to have such a big one, even partitioned it into 3 since it was just too big And it was an external device, the size of a pizza-box (it was en Atari Megafile 60, I still have it !!).

triggaz said:
+1 with this (also on Paranoid Rom 1.1a) but I think that it's something with the ROM coz on earlier build v1 this method worked verry good I hope that Yank will find a solution coz it reallly helps wit our 576 ram
Click to expand...
Click to collapse
I'm working on the CWM flashable right now, should be done within 1-2 hours at most

Yank555 said:
Hi,
You're welcome
The file '/data/swap.0.log' is a text-file containing info on the execution of the script...
If it's not there, then the script didn't run at all...
I should have a little time later today, will try to make the CWM flashable solution for you, should be a no fuss solution, as long as the sd-card has a swap partition
How did you partition the card ? CWM ?
JP.
Sent from my Android Revolution HD 6.6.5 XE / faux kernel 007b3 powered htc Sensation XE using xda premium
Click to expand...
Click to collapse
Hi JP, once you told me it was the address to the file, i just navigated there using my explorer and lo and behold!, there it was (attached). If you must know, in my earlier post, the idiot in me just typed it in the terminal and the terminal replied not found.
I made my partition using freeware called Minitool partition wizard. Is 500mb too big for swap in your opinion? I was thinking of compensating for zram, and hence the size... thanks for your speedy responses...
edit...
and hey! whadya know? in the meantime, this place is coming alive!!

bullcrapr said:
Hi JP, once you told me it was the address to the file, i just navigated there using my explorer and lo and behold!, there it was (attached). If you must know, in my earlier post, the idiot in me just typed it in the terminal and the terminal replied not found.
I made my partition using freeware called Minitool partition wizard. Is 500mb too big for swap in your opinion? I was thinking of compensating for zram, and hence the size... thanks for your speedy responses...
edit...
and hey! whadya know? in the meantime, this place is coming alive!!
Click to expand...
Click to collapse
Hmm ... strange, the content of the file looks like a logcat ?! Not what I was expecting to see
Give me a little hour, and I think I should be done with the flashable hard-swap and we'll go from there
Minitool is excellent, but did you pay attention to only create "primary" partition ? If it is a logical partition it won't work...
Can you insert your SD card into your card reader, start Minitool an post a print screen of it ?
JP.
EDIT :
About size ... I believe 256Mb is enough, even read somewhere t shouldn't be more than 256, but I think there was no specific reason given.

Yank555 said:
Hmm ... strange, the content of the file looks like a logcat ?! Not what I was expecting to see
Give me a little hour, and I think I should be done with the flashable hard-swap and we'll go from there
Minitool is excellent, but did you pay attention to only create "primary" partition ? If it is a logical partition it won't work...
Can you insert your SD card into your card reader, start Minitool an post a print screen of it ?
JP.
EDIT :
About size ... I believe 256Mb is enough, even read somewhere t shouldn't be more than 256, but I think there was no specific reason given.
Click to expand...
Click to collapse
Here we go...
Minitool image attached... I typically pay attention to the partition type and made sure both of them were primary
About the logcat, I suspect you're right... I was trying to do one from my pc for the first time using adb and tried the only few commands I know (mkswap...), I think that's what you saw then...
Incidentally, do you feel if I reduce the swap size, the script has a better chance at surviving the boot?

bullcrapr said:
Here we go...
Minitool image attached... I typically pay attention to the partition type and made sure both of them were primary
About the logcat, I suspect you're right... I was trying to do one from my pc for the first time using adb and tried the only few commands I know (mkswap...), I think that's what you saw then...
Incidentally, do you feel if I reduce the swap size, the script has a better chance at surviving the boot?
Click to expand...
Click to collapse
Don't bother, I will test 500Mb and let you know if that is the issue
JP.

I have 512mb partition and it worked without problems as I mentioned earlier so I think that opposite to the "size does matter" in this case it doesn't plus I used it with zram from marc1706.

triggaz said:
I have 512mb partition and it worked without problems as I mentioned earlier so I think that opposite to the "size does matter" in this case it doesn't plus I used it with zram from marc1706.
Click to expand...
Click to collapse
Hi triggaz, are you using the built in zram on Para1.1a? Or have you applied a script from elsewhere? I enabled the built-in zram, but get a "not found" reply when i try zram_stats in the terminal. Can you tell me how you got zram working? thanks...

bullcrapr said:
Hi triggaz, are you using the built in zram on Para1.1a? Or have you applied a script from elsewhere? I enabled the built-in zram, but get a "not found" reply when i try zram_stats in the terminal. Can you tell me how you got zram working? thanks...
Click to expand...
Click to collapse
https://www.dropbox.com/s/xr3z102gxiw2f62/marc1706_zram_100MB.zip
all credits to Dorimanx for ZRAM mod and mark1706 for modifications
I flashed this and then used the compcashe options in Paranoid (set to 26%)