Database Develop

[PRJ] Linux and Android for CDMA Diamond (DIAM500)

Android 2.0 (Eclair) for CDMA Diamond (DIAM500)
Instructions
Put the files from my zip file (zImage, modules, startup.txt) in the root of your Internal Storage
From this xda post, download the latest XDANDROID build.
From the XDANDROID 7z file, extract system.sqsh, haret.exe, initrd.gz, calibration, conf/, media/, and (optionally) AndroidApps/ into the root of your Internal Storage
From stinebd's rootfs autobuild site, download the latest rootfs, rename it to rootfs.img, and put it in the root of your Internal Storage.
If you are updating from an earlier version of Android or just want to clear your settings, you can delete data.img from the root of Internal Storage.
Run haret.exe and boot
Notes
Touchscreen calibration values are stored in the ts-calibration file in the root of Internal Storage. To re-calibrate, delete the file and restart.
The "end call" button takes the phone in and out of sleep.
Android's "Menu" button is mapped to the top-left/Home button. The 5-way pad and the scroll ring both work.
Android's "Home" button is mapped to the power button on top of the phone.
Wi-Fi is working, although Linux sometimes crashes when WiFi is turned off.
If you want to try Android 1.6: From this Android build, extract haret.exe, initrd.gz, system.sqsh, calibration, calibration_diamond, and the AndroidApps/, conf/ and media/ directories into the root of your Internal Storage.
ChangeLog
3-23-2010:
Touchscreen double-tap issue should be gone, big thanks to eval- and especially bzo
HTC wired headset and 3.5mm headphones both work
3-8-2010:
Hardware 3D is re-enabled (accidentally disabled it)
3-6-2010 Update:
Bluetooth now works, big thanks to bzo
Touchscreen should be improved
Power-off now resets the phone instead of crashing
2-25-2010 Update:
When WiFi is turned off the phone shouldn't crash
2-19-2010 Update:
Power collapse now works, so power consumption should be much lower when the screen is turned off.
WiFi should work, as long as you use a new rootfs from stinebd's autobuild site. If you tried to use WiFi in the last ~2 weeks and it failed, WiFi still may not work with this new rootfs and kernel. See this post for solutions.
2-17-2010 Update:
Microphone works without having to make a call in WinMo
WiFi still isn't working, but I'll post a patched rootfs soon to fix it
2-10-2010 Update:
Hardware 3D acceleration is working under Eclair
Brought in makkonen's fixes for battery status--they're rough, but better than being stuck at 5% all the time
WiFi is not working at the moment, but I'll lean on the XDANDROID guys to get my fix in.
2-3-2010 Update:
Linux is now using much more of the phone's memory: 180MB vs. 103MB, thanks to some patches from the Hero and Droid Eris kernel source.
Touchscreen calibration is now supported with the Feb. 2 XDANDROID build, thanks to makkonen and phh.
1-27-2010 Update:
Stability should be much improved
A new touchscreen driver is included that is a big improvement over the old one, thanks to makkonen and phh. A calibration utility is coming soon. Until then, calibration is stored at the bottom of conf/eclair.user.conf, and you can put your WinMo calibration in there with this guide.
The USB product ID has been changed in the hope that ADB will work on Windows. Try it out and post back if it works.
1-22-2010 Update:
The power button (on top of the phone) is now mapped to Home, and holding it down will show apps running in the background
Sound, data, and WiFi should all be working
1-11-2010 Update:
Tested and working with Eclair
Deep sleep should be working better (use less power)
12-26-2009 Update:
Kernel improvements:
The speaker and earpiece now work (but not the microphone)
Screen backlight control works
Rootfs improvements:
Thanks to makkonen's RIL fix, cell data works in Android without having to end the connection in WinMo first
I made a change to /init that might help mjb94, hackman238 and others that have partitioned internal storage. If you were getting a "cannot mount" error on boot, let me know if this fixes it.
12-16-2009 Post
We do have a Google wave for Android--right now it's a cross between a wiki-status-report and chat room. I'm not sure how to give a link to a wave, but it's open to everyone and called "Android on HTC Windows Mobile Phones (Diamond, Raphael, Blackstone, Rhodium, Topaz)". If anyone wants a wave invite, PM me and I have a few to give out.
Enjoy Android, and if you need help or have questions, PM me or post here
Donations are greatly appreciated , or help finding an engineering job in San Diego!

thanks mr. pippy for all your work. my wife is happy that once the microphone works i wont want to buy a new phone!

wow
you are definately making progress on the diamonds android

Is there any chance of the mic working anytime soon? I know this isn't an fast paced process but I'm just so sick of wm.

Can someone invite me to Google Wave please?
my gmail account is mike.cgy

bdusmc said:
Can someone invite me to Google Wave please?
my gmail account is mike.cgy
Click to expand...
Click to collapse
I just sent you one.

Awesome - I got it... Thanks a lot!

Wow, you're getting a lot done in a short period of time, Thanks!
Will donate as soon as I can!

the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"

For the latest version, it will boot for me, but as soon as I have a 3g connection it seems to reboot any time I touch anything.

Boots up fine
Latest build boots up and seems to run fine for several hours but after playing with it, it seems to get more and more unstable. I went 10 hours with it plugged in sleeping and then unplugged it and used it moderately for about 3 hours before it crashed. Now it's crashed 3 times within minutes of each other. Good stuff though, can't wait until it's stable enough to use full time. Diamond has plenty of nuts to run it pretty good. Sure would be nice to have a dual boot phone. No reason to upgrade and get the best of both worlds...

giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.

giovesoft said:
the boot stops on
"handhover: boot [htc_fb-1] -> real [ttyo]"
Click to expand...
Click to collapse
rothgar said:
I get the same error on my Raph500. I tried from the micro SD card and from the root of the fs.
Click to expand...
Click to collapse
Sorry, my kernels are only tested on DIAM500. The RAPH500 mtype (set in startup.txt) is 2182, you should have better luck with that. Also, this thread is for RAPH800 but there may be some RAPH500 people there.

mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting

mjb94 said:
mr pippy i still get the same error as in your other post with the failed to mount sd and the 2 partions, i tried reformatting
Click to expand...
Click to collapse
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.

Willis111 said:
Did you reformat or repartition? Would you happen to be one of those people who has a partitioned card? Basically, I think the layout of your MC can have as many partitions as you want on it as long as mmcblkp1 (the first partition) is a fat32 partition with the needed files on it. There's also a little info on this problem on the wiki, lavender.t posted a solution that works 100% of the time if you're able to enter keystrokes.
Click to expand...
Click to collapse
I simply in disk utility clicked on restore and erased the disk restoring with ms-dos fat
is there another way to do this. i have access to linux and osx not windows
it only shows i have one partition so idk!
no dice. heres what i have done
ok i restore the disk in to ms-dos fat
no dice
i repartiton with a scheme of one partition
no dice
i change the partiton table no dice
i tried lavaders thing but i couldn't get the keyboard to come up

there is a new android version called eclair 2.0 here http://forum.xda-developers.com/showthread.php?t=601751 .

i also formatted from the phone

Possible fix for microphone
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.

MrPippy said:
I haven't tested this yet, but blast3r in irc tested a workaround for the microphone this morning and said it worked:
In WinMo, start a voice call and leave it connected while you open HaRET and boot into Linux. In Android, the microphone should now work for voice calls.
Click to expand...
Click to collapse
Yep, confirmed for me. Made a phone call with android and could talk just fine. Probably can just call voice mail with win mobile and launch HaRET. Trying that right now.

Apps2SD greyed out....

Yeah, first thing the 'uber coders' will think is 'google it' or 'rtfm'. Well been all over and still can't get it to work. But I'll jump though the hoops and hopefully someone will point out where the missing information is. As much documentation that is out there for Android, there is much left to be desired and checked for clarity. So here it goes:
After having many issues with Clockwork Mod recovery, I finally got AmonRA installed and was able to install CM5.0.7 (8 would not install properly at all...too many broken thing like FCs on settings and such).
Things I have done to try to get Apps2SD working:
1/ Manually partitioned SD card
2/ Use Recovery option to partition the card (converted to EXT4 as per Cyanogen's suggestion)
3/ Tried following advice here: http://code.google.com/p/android-roms/wiki/A2SD
4/ Tried following advice here: http://forum.xda-developers.com/showthread.php?t=520582
- which leads to here: http://forum.xda-developers.com/showpost.php?p=3879988&postcount=41 (which seriously need to be re-written.you can't type adb push while already in adb shell....not recognized)
5/ Ubuntu's Disk Utility tells me the EXT4 partition is clean.
So where to go from here? Nothing seems to make any sort of impact on this phone.

...to the QnA section.....
have you enabled apps2sd?
Settings>Applications and tick the Apps2SD box

Moved as not development.

garok89 said:
...to the QnA section.....
Click to expand...
Click to collapse
Nope, looking now....so far I've got 3 tabs opened because of that....this process is seriously sad. Why are there so many ways (some more poorly written than others) to do the same damn thing that the ROM is supposed to do itself? Don't worry, I'll try yet again another set of instructions to get this to work. Geeze....wasn't this hard the last time I enabled it. Seriously, I do't know why I torture myself with this....
garok89 said:
have you enabled apps2sd?
Settings>Applications and tick the Apps2SD box
Click to expand...
Click to collapse
See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.

So, following the directions outline here: http://forum.xda-developers.com/showthread.php?t=534714
NO freaking change. This is on a fresh ROM install of 5.0.7. Seriously, My card size in 8GB, like his, so I used almost his numbers, just a few bytes different, and nada.
Talk about a sad state.
Yes I repartitioned the card, yes I wiped the partitions (after reinstalling the first time and getting nothing but FCs, wiped each section available in the Amon RA recovery menu....three times each.)
So, let's try yet another method.....
I downloaded Apps2SD.apk. Installed it and ran it....guess what...it aid my card wasn't paritioned?!?! Umm....wft? Why the hell was CM NOT seeing the paritions? This card has been partitioned at least 20 times in the last month, in various methods. Yeah, this i good for it's lifespan....
So I went through it's partitioning process...guess what...still greyed out.
Opened the app again... "It looks like your SD cars isn't partitioned..."...are you kidding me?? (yes the app was granted Super User permissions when it ran....)
So....where do I find the part in CM that is broken and not allowing Apps2SD to work?

How is it that after wiping each item THREE TIMES in th recovery list, and a FRESH INSTALL that my background is still the same????
What is not being wiped?

with 2.1 theres an option for all your settings to be backed up to google. if your background is stored in the same folder on the fat32 partition of your sd card, when you load the new rom, your phone will set your background to what it was.
i know because i went from 5.07 with one background to jubeh's 2.2 with another background, needed gps, wiped EVERYTHING(data, system, ext partition etc.) in RAmon's recovery, flashed 5.08 and had my old background from 5.07 set, along with all my old apps downloading automatically...half hour later and my phone was done syncing and set up exactly how i like it, w/o me doing anythin.
that's how your background is still the same. =P
edit: looking at your signature..is your ext fs first on your sd card? i might be wrong but i think the fat32 needs to be first???

JadedTech said:
Nope, looking now....so far I've got 3 tabs opened because of that....this process is seriously sad. Why are there so many ways (some more poorly written than others) to do the same damn thing that the ROM is supposed to do itself? Don't worry, I'll try yet again another set of instructions to get this to work. Geeze....wasn't this hard the last time I enabled it. Seriously, I do't know why I torture myself with this....
See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.
Click to expand...
Click to collapse
i was not attempting to be insulting, i run the cmupdater support and have received numerous "app2sd is greyed out" emails when in fact it was the "move to sd" that was greyed out, not the apps2sd toggle. so get down from your high horse and dont assume that you are better than anyone else. in my experience dealing with hundreds of support requests, i have found it is the person who asks the question, not the people who attempt to help, who are the problem.
"computers don't make mistakes, people using computers make mistakes" comes to mind...
although ubuntu is showing it as clean, choose the "repair SD.ext" option in the recovery...
and although it is unlikely to correct it, fix apk uid mismatches. apps2sd can be a funny thing which can work one day and not the other at times.....
i dont know why i am still trying to help you after pretty much calling me mentally retarded, but hey....
oh, and by "the qna section" i meant that you asked a question in the development area, ie. the wrong section

See, now that's just insulting. Although I will forgive you if you have some sort of mental deficiency and missed reading the subject of this thread.....but just in case, I'll return the favour. If "Apps2SD" is greyed out, that means I am at Settings/Applications and quite have the capability to select option on the phone by pressing/touching the screen. Guess what.....it stayed greyed out. This is why I have a new thread here with the 5 other things that I've read, quite exhaustively, to whit there have been no positive results.[/QUOTE]
you have to have a partition and it will not be greyed out

Either the poor behavior in this thread is going to stop or I'll close it. There is no need to be insulting in any way.

garok89 said:
i was not attempting to be insulting, i run the cmupdater support and have received numerous "app2sd is greyed out" emails when in fact it was the "move to sd" that was greyed out, not the apps2sd toggle. so get down from your high horse and dont assume that you are better than anyone else. in my experience dealing with hundreds of support requests, i have found it is the person who asks the question, not the people who attempt to help, who are the problem.
Click to expand...
Click to collapse
Ok, a few things to clear:
1/ This has truly been one of my frustrating experiences in all the tech I have ever played with (and that's pushing 30 years). Granted you would not know my experiences and my tenaciousness in following directions, despite them having me going off-the-beaten-path because something does not fit any proposed remedy.
What was insulting was the fact that you assumed that I wouldn't check the most basic thing when the ONLY indication that Apps2SD was not working was that tick being greyed out. But that would be because I didn't go into great detail about that. I was kinda hoping that was a given because without it being ticked, it obviously doesn't work.
So, since there was some bas assumptions made, allow me to be the first to apologize deeply and hopefully we can move forward.
garok89 said:
"computers don't make mistakes, people using computers make mistakes" comes to mind...
although ubuntu is showing it as clean, choose the "repair SD.ext" option in the recovery...
Click to expand...
Click to collapse
Did that, no change. Although I will add in that your quote applies just as well to programmers as it does the users
garok89 said:
and although it is unlikely to correct it, fix apk uid mismatches. apps2sd can be a funny thing which can work one day and not the other at times.....
Click to expand...
Click to collapse
Well, doesn't seem to work at all here.<shrug>
garok89 said:
i dont know why i am still trying to help you after pretty much calling me mentally retarded, but hey....
Click to expand...
Click to collapse
That would be because I think you recognized how frustrated I have been and in reality, I'm not really venting at you but at the lack of a solution, despite there being soo many ways to supposedly fix this issue. That would also be because you are most likely the kind of techie that hates to see things not work and will spend more time trying to fix it rather than give in and simply 'reinstall' because you want to know the reason why it happened in the first place. Maybe I'm wrong there, maybe I'm not. I'm am seriously glad that you are taking your time because not a single other person has.
garok89 said:
oh, and by "the qna section" i meant that you asked a question in the development area, ie. the wrong section
Click to expand...
Click to collapse
Yeah, I forgot to apologize to the mod for that. Sorry Mod....
So, have any other ideas how to fix this? I am rather loathe to just try to 'update in hopes that it automagically fixes the issue' approach.

tdt1345 said:
you have to have a partition and it will not be greyed out
Click to expand...
Click to collapse
You might want to read my first post again.....
"Things I have done to try to get Apps2SD working:
1/ Manually partitioned SD card"

jamesd86 said:
with 2.1 theres an option for all your settings to be backed up to google. if your background is stored in the same folder on the fat32 partition of your sd card, when you load the new rom, your phone will set your background to what it was.
i know because i went from 5.07 with one background to jubeh's 2.2 with another background, needed gps, wiped EVERYTHING(data, system, ext partition etc.) in RAmon's recovery, flashed 5.08 and had my old background from 5.07 set, along with all my old apps downloading automatically...half hour later and my phone was done syncing and set up exactly how i like it, w/o me doing anythin.
that's how your background is still the same. =P
edit: looking at your signature..is your ext fs first on your sd card? i might be wrong but i think the fat32 needs to be first???
Click to expand...
Click to collapse
Yeah...I realized this after I left the house and was getting into the car. Just too frustrated when I posted. It was one of those 'don't drink and drive' but more of a 'don't vent and post' type of deals....well, at least not here. Thanks any ways.

have you tried ext2 before upgrading to ext4?
ext4 didnt like my spare g1 too much....but my main one got along fine with it

JadedTech said:
1/ Manually partitioned SD card"
Click to expand...
Click to collapse
Is the partition system ids correct:
Code:
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 8166 MB, 8166309888 bytes
252 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15624 * 512 = 7999488 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 952 7436993 b Win95 FAT32
/dev/block/mmcblk0p2 953 1020 531216 83 Linux
Command (m for help):
The 'b' for the vfat partition and '83' for ext
The startup scripts use there values for some autodetection in cm5.
If all you change is the Id data wont be lost but you are at fault if you don't backup.

garok89 said:
have you tried ext2 before upgrading to ext4?
ext4 didnt like my spare g1 too much....but my main one got along fine with it
Click to expand...
Click to collapse
That is a very interesting observation as I have been automatically upgradeding to EXT4 (as I did read that is what Cyanogen uses...figured if it was good enough for him....) so I just reformatted my SD card from the Recovery partition into EXT2 with a 32MBswap and the rest in FAT32. No change. Damn....seemed like one of those 'simple and yet not obvious' type of answers that may have worked too...

ezterry said:
Is the partition system ids correct:
Code:
# fdisk /dev/block/mmcblk0
Command (m for help): p
Disk /dev/block/mmcblk0: 8166 MB, 8166309888 bytes
252 heads, 62 sectors/track, 1020 cylinders
Units = cylinders of 15624 * 512 = 7999488 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 952 7436993 b Win95 FAT32
/dev/block/mmcblk0p2 953 1020 531216 83 Linux
Command (m for help):
The 'b' for the vfat partition and '83' for ext
The startup scripts use there values for some autodetection in cm5.
If all you change is the Id data wont be lost but you are at fault if you don't backup.
Click to expand...
Click to collapse
Now this produced something interesting.
Code:
# fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 243328.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help):
#
So, how does one go about fixing this if this is the reason that "in certain setups cause problems"? This seems to be a likely candidate for the root of the issue.
Redo partitions in Fdisk?

instead of doing it from recovery
do it from ubuntu via gparted

Sorry for jumping in here but... A while back Dusty wrote a great tut for doing this correctly. Did you follow his thread instructions? If not, take a look. It may have the key to your happiness.
http://forum.xda-developers.com/showthread.php?t=534714&highlight=51dusty

JadedTech said:
So, how does one go about fixing this if this is the reason that "in certain setups cause problems"? This seems to be a likely candidate for the root of the issue.
Redo partitions in Fdisk?
Click to expand...
Click to collapse
The size warning only applies to the short falls of BIOS booting x86 PCs. We don't boot the dream from the sdcard or is the phone booted with a x86 BIOS...
If it was you need to ensure the boot partition is near to the beginning of the disk.. you can safely ignore it

[Q] partition SD on Milestone w/parted - SWAP enabling (brainstorming)

Hi!
Last 48h I've been digging forums for an answer. Is it possible to partition SD Card in Milestone using "parted" and THIS guide?
The problem comes with one little thing:
Code:
C:\Users\DrNO>adb shell
Milestone-Recovery:/
# parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
bash: parted: command not found
Milestone-Recovery:/
# exit
After sleepless night I'm richer in knowledge that (probably) parted is not included in AOR (it's 3.3 that I'm using) [as zeppelinrox posted HERE]
OK, 51dusty used CM recovery, I've tried CMR2.5.0.7, with little success. Maybe I've used it the wrong way but hey!... First I had trouble finding it, then tried to install/flash it through "ROM Manager 4.x", ok it said that's done, reboot into recovery > "Error". Then I looked into the package it looked like an "update" to apply in AOR. It worked, but "adb shell" freezes, it unfreezes after closing CMR. wtf... it was 3 a.m.
1. Am I doing something wrong?
2. Is it possible to implement "parted" in AOR
3. Is it possible to use mentioned above guide on Milestone?
The reason is to part SD "the right way" and split it: FAT32+EXT2(3)+SWAP
Please, help

You can't have swap on Milestone.
And... that's the guide that I used as well... I made a step by step post about it... see my Handy Dandy Fixes thread I linked to it in there... I think I called it "The Hard Way" but ended up being fun...
Oh... and it took me a whole weekend to get it right!

ok, i'll try that anyway, also I'll try to "mount" swap using app called "A2SDGUI", it did miracles with ext2 and it has swap initialing capabilities. when I try to punch it, it flashes short text for half a sec, something about not finding suitable partition, if I get it right, it might work...
two additional Qs:
1. call me retarded but where do I find proper "parted"?
2. is there a windows app that can part disk and make not only ext but swap too? currently I don't have any linux system running, I could install one or make live CD but it would be only for one thing only so I think that you can understand my lazyness ;P

DrNO[PL] said:
2. is there a windows app that can part disk and make not only ext but swap too? currently I don't have any linux system running, I could install one or make live CD but it would be only for one thing only so I think that you can understand my lazyness ;P
Click to expand...
Click to collapse
http://www.partitionwizard.com/free-partition-manager.html
Guide to using Minitool partition wizard.
http://forum.xda-developers.com/wiki/index.php?title=SD_card_partitioning

DrNO[PL] said:
1. call me retarded but where do I find proper "parted"?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=12361294&postcount=842

thank you Sir for those above and more that I've already read around forum search module is not so great as I thought, because it never returned that post withw "parted".
will report soon how's the battle evolving...

Good luck.

ok then...
parted worked, SD8GB splited nicely:
FAT32 7,25GB
EXT3 512MB
SWAP 32GB
that was easy
next thing "apps2ext", reinstalled Darktremor script, restored ext2 backup, worked, mounted FAT, copied backup, reboot, OS did't even noticed any change (except cutting ext2 by a half and upgrading to ext3, in a good way). then swap. first i've tried some apps, like DroidSwap (only FC's), then Swapper2, which found swap partition, but is still limited by the "f" kernel. formating went OK, (un)mounting part. FAILed. then I've started messing arround > in short, bricked soft :] nothing serious, only /system could not mount, thank you nandroid you exist. now I'm back to the point after spliting SD, having Firefox weighting something like 0.8GB in memory with opened tabs about swap vs milestone. after much reading I'll try more serious approach, more digging, lower coding, no apps, console yes, wish me luck.

quick question, people keep saying linux-swap on milestone is not possible, therefore why are you still including it?

I believe it's possible but the commands the set it up / use it are unknown. It doesn't follow the standard "linux way".
Someone please correct me if I'm wrong.

Swap relies on the kernel being compiled with CONFIG_SWAP. Unfortunately for us, Motorola did not enable swap in the kernels they release. Coupled with the kernel verification scheme, we are unable to swap the kernel with one that has CONFIG_SWAP enabled.
If you do a mkswap and swapon on Milestone, you'd get "Not Implemented". So, swap support is not possible. I'd like to be proven wrong though.
Sent from my Milestone using XDA App

swap enable = impossible, dude..

If you read some threads at droidforums, alot of guys don't use swap anyway as it kills the sd card quicker.
Compcache is more interesting... you can squeeze more apps in the same amount of free ram via compression.
The debate is that it takes time to uncompress the app from ram when it's recalled but ram is fast and it would be even faster with a V6 under the hood lol

SWAP is impossible, because motorola kernel don't support it. So, as long as we can't compile our own kernel on Motorola Milestone, this will remain impossible.
Sent from my Milestone using XDA App

[Script]Swap2cache (make use of unused Memory)

i finally get it to work.
this script (if kernel support) create a swapfile on mostly unused /cache partition
-copy the script to phone
-chmod
-add it to end of hw_config.sh (or any other way of bootexecute)
have fun
inteks
update:
new version creates own loopdevice (thx to hygge)

pls guider install ??

niceee.
Does this work on rooted and locked 2.3.4 Arc ?

dubist said:
niceee.
Does this work on rooted and locked 2.3.4 Arc ?
Click to expand...
Click to collapse
sorry but you need a kernel with swap support ...

le_manhpro said:
pls guider install ??
Click to expand...
Click to collapse
the easiest way is to use i.e. rootexplorer to run the script but then you have to do it after every reboot.
maybe a good idea for testing

will it work on ray?

What's benefits we have using swap file?
Thx for answer

inteks said:
sorry but you need a kernel with swap support ...
Click to expand...
Click to collapse
So what kind of kernel, is DoomKernel support? why you dont give a sameple?

Interesting idea, I have setup swap as descriped but I had to change loop device to /dev/block/loop18 which was the only unused loop device on my mobile.
It was wierd, because all new loop devices I created was quickly reserved for the same app by the system, rather annoying. But luckily I had one unused allready available.
I will let you know how it works, how the system performance is percieved after some testing. I would think it could slow down the device, the memeory is increased but it will be on slower memory.

donghungx said:
So what kind of kernel, is DoomKernel support? why you dont give a sameple?
Click to expand...
Click to collapse
yepp, doomkernel support swap
Sent from my MT15i using Tapatalk

Hi inteks
Thanks allot for your script, it actually feels like its memory has been increased with 64MB. I have a few times experienced a slight lag when starting up memory hungry games but the homescreen no longer has to redraw when returning from the game
It is usually problematic in the Order and Chaos game to chat as the game loads the default keyboard which takes some time as it is removed from memory again as soon as you have send your message. The swap makes the keyboard stay in memory and open up instantly
I am also able to keep more applications open during normal use, I would normally have problems having mail, web and other document open at the same time.
I had to modify your script and manually create a new loop device, all loop devices from loop0 to loop38 was allready used.
# mknod -m640 /dev/block/loop50 b 7 50

hygge said:
Hi inteks
Thanks allot for your script, it actually feels like its memory has been increased with 64MB. I have a few times experienced a slight lag when starting up memory hungry games but the homescreen no longer has to redraw when returning from the game
It is usually problematic in the Order and Chaos game to chat as the game loads the default keyboard which takes some time as it is removed from memory again as soon as you have send your message. The swap makes the keyboard stay in memory and open up instantly
I am also able to keep more applications open during normal use, I would normally have problems having mail, web and other document open at the same time.
I had to modify your script and manually create a new loop device, all loop devices from loop0 to loop38 was allready used.
# mknod -m640 /dev/block/loop50 b 7 50
Click to expand...
Click to collapse
pls guider install tks

le_manhpro said:
pls guider install tks
Click to expand...
Click to collapse
Here is the script with my modifications manually creating a new loop devices. I have used loop50 as 0-38 was allready in use and it would leave some room for new loop devices.
I am using scriptmanager to either run the script manually or run it at boot.
Have marked my changes with bold
#!/system/bin/sh
if busybox [ ! -f /cache/swap/swapfile.swp ]
then
echo "Create Swapfile"
mkdir /cache/swap
busybox dd if=/dev/zero of=/cache/swap/swapfile.swp bs=1M count=64
busybox mkswap /cache/swap/swapfile.swp
busybox chmod 0600 /cache/swap/swapfile.swp
else
echo "Swapfile Exist"
fi
echo "connect loop devices"
mknod -m640 /dev/block/loop50 b 7 50
losetup /dev/block/loop50 /cache/swap/swapfile.swp
echo "use loopdev for swap"
swapon /dev/block/loop50
echo "raise swappiness 2 "
echo 90 > /proc/sys/vm/swappiness
cat /proc/sys/vm/swappiness
free

Thanks a lot for the script. What is this loop anyways?

matus201 said:
Thanks a lot for the script. What is this loop anyways?
Click to expand...
Click to collapse
It is a device driver in linux, the loop device driver is created as a block device which functions as disc device. The loop device driver are used to loop back into local imagefiles on the existing filesystem.
You then use losetup to point the loop device file towards an imagefile on the existing memory devices. In this case it is configured to point towards the new empty 64MB file that are created in the beginning of the script.
You now have a small 64MB filesystem attached that we can use as linux swap

Why not making a 128 swap file to improve even more?!
I'm a noob... So I just intested to know how it works...
Sent from my LT15i using XDA App

must this be added for your kernel to start swapping inactive applications from the RAM to the cache partition ?!
thanks man
---------- Post added at 09:30 PM ---------- Previous post was at 09:29 PM ----------
haimelf said:
Why not making a 128 swap file to improve even more?!
I'm a noob... So I just intested to know how it works...
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
the cache partition is only 100mb

yes
Sent from my MT15i using Tapatalk

i heard that swap would wear the cache partition in time thus making it un-useful @ all for it's original use , i believe that cache is used for stuff like downloading apps from market !
thanks

What is "chmod" ??
Sent from my LT15i using xda premium

[Q]Is there a possibility to install rom on sd

Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)

-AsA- said:
Welcome. Already he was just asking about the same with the addition of some suggestions.The init.d directory has the opportunity to start up the concrete near the beginning of a comment, start the machine.One could initiate concrete partitions on the SD card to have played a role partition "mtd" for example / system / data / cachefrom what I noticed the kernel to jb has otherwise changed little these partitions (size).I do not know exactly how it looks with them, but if one could perform 2 partitions by mtd / system (small to perform the basic start-up and later redirects to / systemsd and the rest used as a framework or a particle cache?)
examples of partition
mtd / system (start-up)
mtd / ram (unless you know)
mmc / fat32
mmc / systemsd (the rest of the system)
mmc / data
mmc / .......
and so onthat was a minimum of 4 block
for it is our memory that was on the phone at the same time much bigger and faster (unless there think) than a swap sdanother thing that applications were loaded into the framework so that if they were around 500 + mb ram for the system to switch on only long landing and later had to speed up.I came up with this idea a bit strange when I have made applications to change fat32, after connecting the USB cable.for me my memory card is slightly odd partitions of personal reasons
Class10+ 32gb
fat32 / sdcard 26gb block1
ext4 / 4gb sd-ext Block2
swap ... 2gb block3
fat32 / sdcard2 2gb block4
sorry to my poor english. I hope you understand my gibberish (a lot of words I could not remember so I used google translator)
Click to expand...
Click to collapse
I didn't get you.
But it is possible to install rom on sdcard with High read/write speed.(class 6 or higher)
all U need is a dual-boot recovery
(I don't know that u must have a Rom installed in internal memory or not(
Sent From My "ULTIMATE ROM- gb - WP8 edition" via Tapatalk

yes, but not on my mind
dual-boot umount dir and make new to port img file. mtd block is not changed
my idea if edit mtd block
Memory phone
mtdblock0 /system size 206 mb
mtdblock1 /cache size 50 mb
mtdblock3 /data size 211mb
mayby mtdblock2 is block ram1, ram2 ..... size ~200mb
all ~667mb
my idea is
mtdblock0 /system (basic start-up i don't know mayby 20mb-67mb)
and mtdblock1 is block ram 600mb
of sd card make block to /system /data etc
this is my idea but I do not know if possible

@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow

sgt. meow said:
@-AsA-
Hi. I am working on a dual-boot project. I sent you an invite to our group. It would be awesome if we could work together. I have a test kernel ready, if you want to test. It's still a WIP. Everything modified is mentioned there. Please take a look. Thank you.
Looking forward to working with you.
sgt. meow
Click to expand...
Click to collapse
im helping you on dboot project

The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Nevertheless, you can definitely have ROM images in the sdcard and use those while booting android (basically you only have to update init.rc for that).
Check 'multiboot' in my signature for more details.
Click to expand...
Click to collapse
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
First make it unlockable for newer devices
Then edit
sent from my W8 using client-server technology

fotak-x said:
Can we edit bootloader?
Sent from my XPERIA X8 using xda premium
Click to expand...
Click to collapse
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app

As for the bootloader, what could be the first real-time editor hex can perform a large change in the machine switched on.
When it comes to dual boot I can help not only the development of a test.
slightly going back bootloader to my x8 from the beginning she had unlocked (date of manufacture 10W40 surprisingly). I had not unlocked. To change the kernel or other heavy operations.Never failed to I managed to brick trying to do specifically
not worried about the phone I'm always ready to purchase a new...

The idea of a modified bootloader is nice, but it have two problem.
1. Modify the bootloader to add capability to boot directly from sdcard is basically useless because this is possible with a simple script in a modified ramdisk. Check the post from nAa, or search the thread about nBoot from feherneoh. This is easy and not need to do dangerous things.
2. The modification of the bootloader is near impossible because:
- the working of S1Boot is not documented
- this is a non-standard raw binary, hard to disassembly/decompile
- if someone can disassembly it correctly, need VERY HIGH skills in native arm assembly programming
- need special hardwares to revive the dead phone after all failed modifications (special cables, setool, etc...)
Don't forget: we had to wait more than a year to get unlocked bootloader (and this modification only skip the security verification), and this is working only with devices what older than 1-1,5 years.
I think if someone have these prerequisites, better if he/she working on valuable things instead of boot from sdcard (add fastboot support to bootloader, etc...)

I was thinking of making nBoot work with JB (it didn't). If that fails we will come up with a new method.
It's almost impossible for us to re-write the bootloader.
It would be super cool if someone added fastboot support to our bootloaders.

nobodyAtall said:
The bootloader won't boot directly from the sdcard.
Click to expand...
Click to collapse
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437

stamatis said:
maybe not in our device but its not impossible
http://forum.xda-developers.com/showthread.php?t=2061437
Click to expand...
Click to collapse
Obviously I was talking about these devices not some Samsung one...
@sgt. meow fastboot support is not something that can be added to an existing bootloader. The bootloader itself has to support this protocol. Hence the only solution would be to switch to another bootloader which would have to be ported from scratch for these devices.
The job would require a tremendous amount of effort since not even miniloader works for them!

Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).

sgt. meow said:
Can we use dd to write an entire directory to a .img file? I'm thinking of something.
@nAa
I know. I was just unaware that bootloaders could be ported for our device (even if it meant no sleep for 6 months for the brave dev).
Click to expand...
Click to collapse
Mtd devices are not block devices. What are you trying to achieve?
Sent from my Galaxy Nexus using xda app-developers app

I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.

sgt. meow said:
I was thinking of using feherneoh's nBoot, but in a different way. My idea was to somehow write the current ROM's /system to system.img on sdcard and the same thing with data and cache. Then install another ROM that uses the same kernel (JellySony for example). Then if XXX is present in /sdcard, it would mount system.img as /system (and the same with data and cache), thus enabling dual-boot. In a kinda stupid way.
Click to expand...
Click to collapse
This is how my multiboot mod worked actually - except from the fact that back in those days we couldn't flash custom kernels and the whole job was done via the chroot/hw_config.sh hack.
The bummer is you can't switch kernels so multiboot between say gb and jb is not possible.

nobodyAtall said:
S1loader is not open source to work with. You could hex-edit it if you had some easy way to flash it and recover from the countless hard bricks the bootloader development process has. Unfortunately this is doable via jtag only. My knowledge is limitted on that area.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
...where can i find s1loader in phone? can i pull it out?just curious.....

fotak-x said:
...where can i find s1loader in phone? can i pull it out?just curious.....
Click to expand...
Click to collapse
There are two options:
- Export all the partitions (I think the file is nand_partitions.c) from kernel. The mtdump/dd it.
- Use the mtdmapper module that is in the unlocking bootloader tool to get all the partitions to map and then dump it.
Both ways basically do the same thing and they both have a pretty BIG chance of getting your device hard bricked (even when you are in read-only mode).