NexusHD2 Android Forum

famewolf wrote:For the users asking about using swap space with their HD2 and this rom:


I've verified that the following script works with 2.4 and the HD2. It creates a swapfile on either /data or the external sd....I personally would recommend using the external sd...better to replace a $20 microsd than deal with bad blocks in the nand...IMHO......so no need for a special swap partition....and it appeared to speed up my hd2 nicely. The thread has more info......

http://forum.xda-developers.com/showthr ... ?t=2359182

What will this script do?

It will do three things: (1) it will create a swap file that is a size specified by the user [note: user also has two choices for swap file location]; (2) it will create an init.d script that enables ram swap and sets the swappiness level to a user specified value during each boot process; and (3) it will create 'shift' scripts so as to facilitate turning swap on/off and changing swappiness on the fly.

He provides a .zip that can be flashed (I chose this one...simple) or for those braver another file with just the needed scripts.

Contrary to this note: "Note: JB users will likely have to choose /data for their swapfile location so as to avoid swapon/swapoff errors." you do NOT have to use /data....microsd works fine. The user this referenced did not have a physical SD card card as it was all "internal storage" like the nexus 4 or nexus7 and had to use /data.

The op answers most anything you can think to ask in his first post but is also active in the thread.

famewolf wrote:It creates a swapfile on either /data or the external sd....I personally would recommend using the external sd...better to replace a $20 microsd than deal with bad blocks in the nand...IMHO.

NYLimited wrote:
You are supposing /data in in NAND. With DataOnEXT it would be on the card in the ext4 partition.

Since either scenario keeps it on the card would you place the swap file on FAT32 or ext4? ^_^



---
Which is worse: ignorance or apathy? Who knows? Who cares?

agbommarito wrote:
It seems it would be better to have the swap file on ext4. The developer's OP talks about a restriction if the swap file is on the FAT32 SD card. If you want to turn on USB mass storage with a PC, you must first manually turn off the swap file, then reenable it when USB mass storage is turned off. If the file is on ext4, I don't think this restriction would apply.

famewolf wrote:@tytung

On one of my other devices I changed the adb device id on bootup via a script in /etc/init.d because it conflicted with the hd2 one....at that time I noticed the path /sys/devices/virtual/android_usb/android0 does not exist on the hd2 rom. Is the information such as iSerial stored somewhere else?

tytung wrote:
No. I have my own android_frameworks_opt_telephony git.
I didn't pull the latest source code from CM this time.
So SMS middleware patches were not included.

If you would like to test PushSMS, please flash telephony-common.jar_SMS_middleware_patches_for_CM-10.1_updater.zip and report back. Thanks.

famewolf wrote:

I tested this and it appeared to work fine. I think he made some additional code changes on July 12th's nightly but the current version seems fine.


I found out...the version tytung provided is meant to be used with babel-2.....if you use a device with cyanogenmod nightly July 12th or newer that apk will break and you will need the beta3 apk. Neither works with the other so you have to match them.

tytung wrote:
Thanks for the feedback.
The patch has been added into source code.

Actually, I have already built a new ROM. But I won't release it so far.
To solve the false virus warming, I have removed Settings.apk's source code and downloaded clean source code again from GitHub, but Settings.apk was still detected as a virus by Avast. Not by other companies this time.
https://www.virustotal.com/en/file/02de ... 374510864/
No idea so far.

tytung wrote:The path /sys/class/android_usb/android0 is created by the kernel 3.0.