I'm using my phone to compile ghostscript. Because it executes some programs to compile, it has to be done on the hardware it's being compiled for.
The phone has an ARHD ROM, and ElementalX kernel. It's been installed fresh recently (within the last week,) with the latest of both.
When linking a large executable, make is getting killed.
I attempted to make a 1GB, 512MB, and 50MB swap file on both the internal and external sd's. Failed on all.
Has anyone got a working swap setup?
Related
So I have been playing with android builds for some time now.
I had successfully ran cupcake and donut builds using the HaRET on sdcard method.
(not every time was perfect but worked more times than not)
eclair has been very troublesome. with the introduction of the new installation method.
I have had limited success even getting it to install.
sometimes it would install without a hitch.
other times it wouldn't even get to the install screen.
SO HERE ARE MY FINDINGS.
while installing the latest polymod2.1g eclair build (actually with any version) I was watching the screen messages.
I know they are fast scrolling, but I can usually pic out errors.
I noticed almost every time I installed there were at least a few I/O errors of some kind.
and the times that I tried and didn't get any errors, the build would often install OK.
I obviously have either a crappy sdcard OR the phone is having problems writing to the sdcard.
either way is a problem, being that the new version of installing creates(writes to the sdcard) the system.img
with the installer program ON THE PHONE.
when using the previous android versions (cupcake & donut), the builds came with a system.img that was already built.
only the data.img was needed to be built on the phone.
that lead to fewer if any bad installs.
Now that there is more to write on the phone, its almost impossible to get a stable eclair build.
SO HERE IS WHAT I DID. (being that I am too stubborn to go buy another card yet...)
I first decided to go the route of partitioning the sdcard. (assuming there might be "bad" sectors on the card)
(1) fat32 followed by (2) ext2.
I then tried installing with the new 'install to partitions' options in the installer.
I was still getting I/O errors...
I tried again putting data on partition and system as an img.
still errors...
then data as img and system as partition.
still errors (but it worked)...
I reformatted the ext2 partitions and ran a check. (NO PROBLEMS)
at this point I got a crazy Idea....
ON MY COMPUTER I EXTRACTED THE ANDROIDINSTALL.TGZ AND PUT THE CONTENTS FROM THE SYSTEM FOLDER TO THE SYSTEM PARTITION ON THE SDCARD.
THEN I PUT THE CONTENTS OF THE DATA FOLDER TO THE DATA PARTITION OF THE SDCARD.
still having the andboot folder on the fat32 partition I confirmed the files: HaRET.exe, initrd.gz, zImage-eclair, and startup.txt.
Ran HaRET...
skipped installer...
NO ERRORS>>> INSTALLED>>>>> WORKS!!!!!!!
EDIT: OK, I did have a problem.
I couldn't install any apks. just got message that application was not installed.
first I reboot to installer and tried to fix permissions.
still couldn't install anything...
then I tried installing from market. got error message that there was no room left to install.
then I uninstalled an application and tried to install something else...
still no install...
it Had to be a permission issue. there is more than 50% free space on all partitions.
WENT BACK TO COMPUTER CHANGED PERMISSIONS ON ALL FOLDERS ON THE DATA PARTITION TO RW.(not sure if this is bad???)
and now everything works GREAT!!!!
the only problems are sometimes with the newly installed apps (probably due to I/O errors)
and I just re-install the app and it works.
*********I guess it is time for a new sdcard*******
but for now it is a nice work around.
however, it still doesn't rule out either the installer or the phone itself as the problem.
I will report back if I ever get a new sdcard.
mnjm9b said:
#1
Click to expand...
Click to collapse
This is an interesting approach, copying the files manually instead of using the installer script for that.
I have to say, I have tested with several micro sd cards (class 2,4,6) and I never had any problems with the installer (replimenu 0.9) using ext2 partitions and booting from haret
However, NAND is giving me massive problems still after flashing dzo's or vilord's nbh
After a cold boot, it's extremely slow and getting stuck at several places during the loading process
So I stick with Haret at the moment.
Using class 6 SD memory, the whole process from power on to Android just takes me only 45 seconds, which is working much faster for me than NAND. Another advantage is that the /system and /data mount points are only limited by the size (of the created partitions) of the sd card. I use a 8GB card.
Using Kaiser's internal memory for NAND only gives you 50-80MiB free space left for /data
Update...
I broke my data, which was to be expected.
after I installed a bunch of apps and had problems with many of them.
it finally crapped out on me.
Luckily I backed up my data partition using partimage on linux
so after I re-formated and restored the data partition
everything worked smooth again.
the system partition seemed to be unaffected....NICE!!!
although this time I manually added the apks that I wanted
to the data partition before I put it back in the phone.
they all work great now.
this is way to damn easy...
THANK YOU
Hi,
Tonight I installed some updates for apps on my phone running Leedroid 2.2d A2SD+. Some of them stubbornly decided to stay on the SD card so I went to move them (I haven't managed to get pm setInstallLocation 1 to work, though I have yet to try it from ADB and that was the way I got setInstallLocation 2 to work before I rooted). I moved several at once and suddenly had the applications manager restart itself and found one of my games that was being moved (Cordy) was no longer working and couldn't be moved either to or from the phone (said move failed). So I tried restarting the phone incase that would fix it.
The phone wouldn't get past the HTC logo so I thought it might be a corrupt A2SD partition, but since it was ext3 that I could probably just get fsck on the computer to replay the journal. Upon putting the card in the computer (using an SD adapter) and booting into Ubuntu 10.10 I tried running disk utility with 'check filesystem' and it reported an error and that the filesystem was not clean and changed the partition to unknown. The same thing happend for the FAT32 partition and I couldn't mount that either. I tried running fsck from a terminal and it said something along the lines of 'Bad superblock or possible short write' and was unable to check the partitions and exited immediately (sorry I have since rebooted and assumed the same error would occur next time so didn't write it down specifically).
I restarted into Windows 7 to see if it could fix the FAT32 partition so I could get my Nandroid backup I made yesterday and it worked fine and said the partition was fine! Usefully Nandroid makes an md5 checksum of the backup so I was able to confirm at least that was intact and make a copy (I didn't really have anything else not backed up on the card as I only rooted a week ago).
I then rebooted back into Ubuntu and it now reports the FAT32 partition as clean, and actually makes some attempt at repairing the EXT3 partition but reports huge quantities of nasty errors like multiply allocated blocks and allocated blocks marked as free and an error with the journal when I run from terminal using 'fsck -t ext3 /dev/sdb2'. I don't really have any experience with fsck as I mostly use windows but there were a lot of errors that sounded pretty unresolvable (from memories of my couple of lectures on ext at university).
Yesterday I flashed an UOT theme using (ClockworkMod 2.5.0.7 as installed by Unrevoked3) install from zip for battery percentage and some icon changes, I chose Leedroid 2.3d from the file list. I had also installed DSPManager using the flashable zip on the Leedroid site.
My card was partitioned using GParted with FAT32 first followed by a 512MB EXT3 partition as recommended on the Leedroid site. I was sure to create the EXT3 partition second as I noticed adding it first at the end made it the first partition in the table. The card had been made a goldcard (though this might be gone as I erased the card with disk utilities Format drive button which may have deleted the MBR, I'm not really sure).
I'm guessing somehow Android tried to do multiple writes at once but I was under the impression these kinds of issues were solved by putting the partitions in the correct order, besides, shouldn't Andorid work correctly with its built-in support for ext anyway like any other version of linux? If this is a known, common problem with A2SD+ why doesn't every ROM have a big warning about this like Data2SD ROMS generally have about SD wear and being able to persist system settings?
PS: I realise there are some other threads on this but they are fairly old and seem to all involve connecting the phone to the computer or after a reboot.
Hi,
I know this properly have been asked many times ind here before, but I hope someone can help me out anyway.
To solve the classic problem with "low memory", I tried to root and install CM7 to my phone. Which I did manged to do, also more then just one time. But I allways run into the memory problem later on. So I read a few more threads, which said that I just use S2E and A2SD together. I even installed A2SDGUI.
But know matter what I do, I allways sees the problem with "low memory" eventually, perhaps 4 months later perhaps sooner. To my understanding, this should not be a problem, when you use S2E and A2SD scripts. Which make me think that I haven't done it right.
So my wish is that someone can give me a detailed manual to follow, so I can get past the f...... memory problem, and especially how to test to se if it works.
My SD Card is a Samsung 16GB class 10 card. I know your not excited about class 10 cards, but I'l give it a go, and I'llthink I have a smaller class 8 at home.
I like CM7, but as CM is my first and only custom rom I have tried, I can't say I don't like the others. So I'm not bound to any version, I just want to get the newest possible version of Android, which is fully functioning.
Hope someone can and will help.
Pick any ROM you want, open the .zip file, go to /system/etc/init.d/ and delete the 10apps2sd script (it can be named like this or something very similiar), if there is no a2sd built then it's even better - dont do anything.
Now download - http://d-h.st/1vK , place it on the root of sdcard.
Wipe everything, make sure you have 1-1.5GB ext3 or ext4 partition (i suggest 1GB)
Flash the ROM, and then without leaving recovery flash the above a2sd script. ( http://d-h.st/1vK )
Voila, done you have 1 - 1.5GB internal memory. (depending on how big you ext partition is)
Keep in mind this script will keep all kind of app data on SD, so it might be slower (most a2sd scripts keeps /data/ partition on internal memory for performance reasons)
But since you're looking for a unlimited space it should fit you.
If you dont know how to flash a ROM, or ROOT then you need to read some flashing guides first.
Well I would like both when some app are on the internal memory, and other on the sd card. Cause some apps don't work well, when on sd card. So if there are a way to make this happen, it would be great. But that isn't the case is it?
Any I coming to try this.
It seems to be working, but when I through Titanium Backup restore a game (Big Business), I can't start that. It begins to load, and the switch back to startscreen. Then it switchs back and forth, before it eventually stops the game.
Is that because the backup is from another setup, with a2sd's?
Try to remove the application data and try again.
Nope, that didn't help
Hi there,
Almost every app seems to be too big for my Galaxy Gio flashed with custom ROM Jellybean 4.2.2 (CyanogenMod 10.1) 20130908.
I always get the following message:
Error downloading. There is insufficient space on the device.
Is there anything I can do to being able to install larger apps such as WhatsApp?
Thank you!
I created a secondary (primary) ext4 platform on my sd card and installed Link2SD. On launch it asked me for the partition system (I checked ext4) and created the mount script.
Now after reboot, what am I expected to see?
My internal partitions are still full:
/data: 144 out of 178 used
/system: 193 out of 206 used
Consequently, I still cannot install or update most of the apps.
What to do?
Any advice is appreciated!
I went for the Plus version of Link2SD which also allows me to link data files.
Furthermore, I moved even system apps such as the Play Services and the Play Store.
Now I have sufficient place to install most of the apps, which are then automatically linked to the sdcard by Link2SD.
I also tried the initext method which, however, did not work for me on CM 10.1.
I will stick to this approach now!
hi folks, I've been given a wildfire s (cdma I believe) and I love it's size so wanna make it a rock stable cute little backup handset. I've unlocked the boatloader and rooted it and flashed TWRP and slimomatic 4.2.2 on it (mainly for the OC kernel). I also flashed a cronmod script INT2EXT or INT2EXT+ (can't remember which) before suffering a very persistent inconsistent UID on system apps error.
now weeks later I ready for another try at squeezing the best out of this device and I need a little help please.
1) how do I remove the 2nd partition cronmod has made ? I've decided to use a bigger faster SDcard so the 2nd partition is not found obviously.
2) are there any roms AND kernel combos out there that support F2FS and overclock ? I'm not that bothered about the version as long as it's ICS or above.
3) is using a script to increase storage and add swap better than using an app like APPS2SD ? is it faster to not use apps that create Symlinks ? (APPS2SD supports F2FS where kernel and rom allow).
if you can see where I'm trying to go with all this and have a suggestion that I've not mentioned I would be glad to hear about that too...
whenever I click on the "search this forum" box it disappears instantly, 135 pages is too much to wade thru, this is why I'm making a thread...
scrub question 1, I've just read that it's only a matter of opening the zip file and visiting the locations that it deposits files and deleting them before rebooting.
replace question 1 with how do you fix SDcards not mounting ? I've tried two cards now, when you click mount storage it pops up on nb card safe to remove. the card works fine in another phone for reading and writing.
this started after a "unfortunately package access helper has stopped" error. if I try to mount it in settings it goes from preparing SDcard to card safe to remove and settings hangs and then FC's. I've cleared cache and dalvik, factory reset, formatted the card in another phone but nothing changes. I'm stuck on cwm6 which doesn't see it.
save my satiny please !!!!!!! without a card I can't even flash another rom...