what does this mean ive done a search but carnt findout what this means
Hboot : Stock for now
Use Android Terminal to enable A2SD
as this is what it says i've got to do in install the jelly bean rom.
i will follow the instructions that are porvided with the Android terminal but just no clue to what the hboot thingy is
pandashoe said:
what does this mean ive done a search but carnt findout what this means
Hboot : Stock for now
Use Android Terminal to enable A2SD
as this is what it says i've got to do in install the jelly bean rom.
i will follow the instructions that are porvided with the Android terminal but just no clue to what the hboot thingy is
Click to expand...
Click to collapse
If you don't know what hboot is, then you have stock.
pandashoe said:
what does this mean ive done a search but carnt findout what this means
Hboot : Stock for now
Use Android Terminal to enable A2SD
as this is what it says i've got to do in install the jelly bean rom.
i will follow the instructions that are porvided with the Android terminal but just no clue to what the hboot thingy is
Click to expand...
Click to collapse
But if you don't know your phone hboot......you SHOULD read a LOT before doing ANY CHANGES to your phone. Please be careful.
Regards
Sent from my HTC Desire using xda app-developers app
---------- Post added at 01:01 AM ---------- Previous post was at 01:00 AM ----------
pandashoe said:
what does this mean ive done a search but carnt findout what this means
Hboot : Stock for now
Use Android Terminal to enable A2SD
as this is what it says i've got to do in install the jelly bean rom.
i will follow the instructions that are porvided with the Android terminal but just no clue to what the hboot thingy is
Click to expand...
Click to collapse
One more thing.... Android terminal has NOTHING to do with INSTALLING the jelly bean Rom ....
As I said, please read tutorials and guides before attempting anything.
Regards
Sent from my HTC Desire using xda app-developers app
pandashoe said:
what does this mean ive done a search but carnt findout what this means
Click to expand...
Click to collapse
Then you are not using the internet properly.
via xda app
stankyou said:
Then you are not using the internet properly.
via xda app
Click to expand...
Click to collapse
thanks again for your help
When it says "Use android terminal to enable A2SD", what it means is after you have installed the rom (which you would do by flashing the zip file through a recovery mod like clockwork recovery or 4ext recovery) you enter the android terminal in your apps tray (it will be installed already as 'Terminal Emulator' or such) and type
Code:
su
You will get a super user request asking you to allow the terminal emulator root access. Allow this.
Code:
a2sd install
You wil be prompted for install options. The recommended values were.
Code:
y
n
y
at which point your phone will reboot and you will have activated the A2SD features of the rom.
But in order to do this, you will first need to repartition your SD card into two partitions.
Back up all of your data before you even attempt this so you don't lose anything.
This can be done with a number of tools like GParted or MiniTool Partition Wizard.
The first should be a FAT primary logical partition the size you want to store your documents on and the second should be a primary logical ext3 file system (not all roms support EXT4 and journalling can degrade SD card quality faster).
I have mine as an 8GB partitioned into a 6.5GB FAT and a 1.5GB EXT with about 1.3GB of apps installed split across A2SD and androids internal apps to SD function while still keeping 80MB free on my data partition.
I hope this helps.
Psytechnic said:
When it says "Use android terminal to enable A2SD", what it means is after you have installed the rom (which you would do by flashing the zip file through a recovery mod like clockwork recovery or 4ext recovery) you enter the android terminal in your apps tray (it will be installed already as 'Terminal Emulator' or such) and type
Code:
su
You will get a super user request asking you to allow the terminal emulator root access. Allow this.
Code:
a2sd install
You wil be prompted for install options. The recommended values were.
Code:
y
n
y
at which point your phone will reboot and you will have activated the A2SD features of the rom.
But in order to do this, you will first need to repartition your SD card into two partitions.
Back up all of your data before you even attempt this so you don't lose anything.
This can be done with a number of tools like GParted or MiniTool Partition Wizard.
The first should be a FAT primary logical partition the size you want to store your documents on and the second should be a primary logical ext3 file system (not all roms support EXT4 and journalling can degrade SD card quality faster).
I have mine as an 8GB partitioned into a 6.5GB FAT and a 1.5GB EXT with about 1.3GB of apps installed split across A2SD and androids internal apps to SD function while still keeping 80MB free on my data partition.
I hope this helps.
Click to expand...
Click to collapse
Thanks mate, also helped me, no about hboot, but how to enter in android terminal.
cheers
like said above, terminal emulator is an app u can get from play store but i think JB has it already installed. open the app and type
su (then grant permission)
y (press enter)
n (press enter)
y (press enter)
then ur phone will reboot and android will upgrade (make the changes) then ur done.
Sent from my HTC Desire
Related
The following information is for those who are still unsure of whether Apps2SD has been installed and if it is working correctly after root.
Open a Terminal Editor on your phone (I currently use ConnectBot, which is available for download via the Android Marketplace, comes with hotkeys, and it's free, link <here>).
When you have the client open, type "su" to gain super user access, and then hit enter. Now type "ls -l /data" and hit enter. You should see a few lines, a couple of which should read on the far right column:
dalvik-cache -> /system/sd/dalvik-cache
app-private -> /system/sd/app-private
app -> /system/sd/app
Notice the -> indicating symlinks and the 'sd'
You can also run: busybox df -h to check the /system/sd that the folder is being used
If this output is visible to you, then Apps2SD is working properly and you have installed it correctly. You will notice that by checking Menu > Settings > SD & phone storage, there is still some internal memory going down due to cache, other data, etc, but the main apps all go on the SD card given the above result. I currently have 29 apps installed (including Google Earth, which is 22.1 MB in size itself) and my internal memory currently shows 119MB of available space.
You can perform more extensive checks by executing the following command:
ls /system/sd/app (this will list all the apps which you have installed to the SD card)
If you prefer to run it from a PC with your phone connected, then this can also be checked via ADB by installing the relevant Android SDK for your OS. Downloads for SDK versions, link <here>.
Alternatively, you can use the script (written by theboxman from MoDaCo.com), which you can run via GScript Lite to test if Apps2SD is working correctly, link <here>.
how about unlock?
thank you for the info. btw, i havent seen in the forum if there a way to unlock the Desire form a certain network. any idea? sorry i know its the wrong place to ask and post this.
Hi Mastoid,
Could you tell me how exactly to run this from PC?
I've got the whole SDK installed but no idea what i have to do...open a prompt or something? Please inform as i'd really like to check.
You need to download the Android SDK and also Java.
http://java.sun.com/javase/downloads/widget/jdk6.jsp
http://developer.android.com/sdk/index.html
Then open a command prompt in Windows, plug in your Desire (your phone does not need to be in hboot/fastboot to access adb shell).
1) Open a command prompt on your computer and cd to your adb tools directory (it will be wherever you extracted the sdk; ie, c:\android-sdk_r04-windows\android-sdk-windows\tools
2) In that window enter the following commands:
adb shell
su
ls -l /data
this should list the top 2 items as:
lrwxrwxrwx root root 2010-04-28 22:54 app-private -> /system/sd/app-private
lrwxrwxrwx root root 2010-04-28 22:54 app -> /system/sd/app
ls -l /system/sd/app (will list apps on installed to your SD Card)
Now, for final proof, type:
busybox df -h
iom_jack said:
thank you for the info. btw, i havent seen in the forum if there a way to unlock the Desire form a certain network. any idea? sorry i know its the wrong place to ask and post this.
Click to expand...
Click to collapse
Do you mean to have it sim-unlocked?
http://uk.answers.yahoo.com/question/index?qid=20100328154024AA1abkl
Great!
That worked, though the items you mention are not at the top but a couple of rows down. Busybox did show the apps installed on the SD.....ah, peace of mind
thx for the instructions!
no problem bud, glad it worked out for you
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Question about APP2SD.....if anyone can answer
can it stop working halfway? i mean at first it really looked like apps were on SD but now it takes the flash memory instead....
i have 38m left with APP2SD
totorip said:
can it stop working halfway? i mean at first it really looked like apps were on SD but now it takes the flash memory instead....
i have 38m left with APP2SD
Click to expand...
Click to collapse
I posted a thread recently showing how to check if Apps2SD has been installed correctly and is working:
http://forum.xda-developers.com/showthread.php?t=677073
How to setup App2SD?
Anyone got a clear, easy guide on getting it working? Can you install it on the standard rooted ROM from MoDaCo? Do you need to have it cooked into a ROM?
A video or something would help but I'm interested in getting it setup incase I need to get a load of apps
î did your think i i use better terminal pro
app => system/sd/app
dalvik cache => /system/sd/dalvik cache
app private => /system/sd/ app private
so how can i have around 40mb left only?
Re: Question about APP2SD.....if anyone can answer
How many apps have you installed?
How have you partitioned your sd card? i.e. swap size?, ext2 size?
Have you applied the Apps2SD update zip?
-------------------------------------
Sent via the XDA Tapatalk App
ive got maybe 40/50apps
i partitionned , 66 cache 1280m EXT 2=> EXT3
and no update....i dont need with the latest modaco R2 custom rom do i?
im afraid to reboot everything again, spent the whole day to isntall everything
30mb left :x
Re: Question about APP2SD.....if anyone can answer
I would suggest that you apply the dalvik-cache update zip and that should hopefully fix it. Note that you should only allocate 512MB to 1024MB (max) for the ext2 size and, you do not require a swap of 66MB, it is not recommended. I have my swap set to 0MB, ext2 set to 512MB which is more than enough space for apps, and rest to FAT32.
Search google for the "Apps2SD mini guide" (found via MoDaCo website) click the link and scroll down to the bottom of page one, the update zip file is available there.
-------------------------------------
Sent via the XDA Tapatalk App
is it bad? (64 swap)
i calculated, i installed 170m worth of app. And i have "43" left (started at 138)
so , somewhere, APP2SD is working...but not verry effective
Re: Question about APP2SD.....if anyone can answer
I think it is working, run the command (ls /system/sd/app) in terminal editor in the link i posted earlier and check what apps are stored to the sd card. Also, download and install "cachecleaner" from the marketplace (free) to free up some cache space.
-------------------------------------
Sent via the XDA Tapatalk App
Re: Question about APP2SD.....if anyone can answer
You have something wrong. I have also this Rom with about 53 apps and have still 134MB free.
Sent from my HTC Desire
i installed the update.zip
i went from 38 to 53mb
then i use cache cleaner , i now have 60....
and still 170m worth of app...
so is my app2sd working in half?
Re: Question about APP2SD.....if anyone can answer
I ran the command in Su, and only the 2 app ones said sd, my dalvic cache didn't say SD card. I ran the suggested update fix but had bootloop, do I need to wipe anything first? I'm using evil 1. 0 Rom and thought it came pre app2sd. . .
Id like to get dalvic moved. . .
Thanks
-------------------------------------
Sent via the XDA Tapatalk App
Lol since thazt update zip i have no more wifi....cant start wifi it says. Great
Hi
I have rooted my phone with unrevoked, s-off'ed with alpha rev 1.8, partitioned 1gb of my 4 gb card to ext 3 and installed Gingerbread F1 V3 Ap2SD ENG.
On first load of the rom i can see that my SD card FAT 32 storage has been reduced but the only other memory internal memory which was at 147mb when i first booted the rom.
All apps are installing to the internal memory by default with only the option of moving to the SD FAT 32 partition. and there is no option to move to the sd ext3 part as there is no option - so I have lost 1gb off my sd card.
What have i done wrong?
on a 2nd note i appear to have a call delay when answering the phone my radio version is 32.49.00.32U_5.11.05.27 - do i need to update this ? will it solve the problem ? my carrier is vodafone UK.
appreciate the help
ararararar... Sorry had to do something.
This has been explained SO many times by me included. The way a2sd works is by symlinking the folder containing the apps(/data/app) to you ext-partition.
You cannot see this partition listed in the system info, as the partition is not supposed to be there. The system have no way of knowing that you are using an ext-partition, as it just installs apps to /data/app, however as it's symlinked to ext, they are actually being placed in sd-ext/app.
This means that you will only see you internal memory, but it still works. Your apps will just take up less space on internal, as the apk file is placed on the ext-partition. They will still take up some space for data and dalvik cache.
edit: bonus info. Install "quick system info" or "titanium backup" from the market to see the size of your ext-partition in those apps.
edit2: and if i did not make my self clear. The partition-size info in the system settings is not supposed to be a partition manager. It's written to be userfriendly, and it only provides the regular user with the partitions they should care about(/data and /sd-card). If you want a detailed view of all your partition(and there is more than a few) go get root explorer. It'll let you play around with all the partitions mounted.(you won't have access to recovery, bootloader and so on from here)
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Well i take it that your cache partition is too small(this is why people using alpharev cm hboot cannot use recovery for this). In that case you have already flashed another hboot(using "fastboot flash hboot hboot.img") if you haven't done this, you cache-partition should not be too small, and the recovery method should be able to do this just fine. If you have done this, use the same command to flash the radio eg "fastboot flash radio radio.img"
Either way it is very unlikely to fix your call delay(read: it won't fix your problem, as it's got nothing to do with the radio). It's a problem caused by some incompatibility between the htc libs and GB. It's quite common on GB roms apparently. Wait for HTC to release the real GB update, and we might very well be able to solve this problem.
dazzr123 said:
Ok thanks. I'm new to this and there's so much info to take in
With regards to the radio is there a simple way of flashing as I have alpha rev installed the method via recovery wont work. I see alot of people talking about doing this through a terminal but I could not find a comprehensive guide for this like the xda root guide. Thanks.
Darren
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Install android sdk:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Copy the downloaded radio.img to e.g. partition C: on your computer (if you downloaded a zip, extract the radio.img from there). Check the md5sum!!!
Boot your into fastboot mode (start it with pressed back and power button) and connect your phone to your computer.
Now open command prompt on your computer and type
Code:
fastboot devices
It should list your device now. If it does, type
Code:
fastboot flash radio C:\radio.img
(in case your radio.img was copied to C: ).
Now, observe the computer and be patient TOUCH NOTHING!!
The process will copy the image to your phone, write the image to the radio partition and perform some magic be patient TOUCH NOTHING!!
Watch the little indicator at the top of your phone screen.
Once the process appears to finish (it may not say complete) wait a further FULL 60 SECONDS and be patient TOUCH NOTHING!!
Then, and only then, reboot your phone.
Click to expand...
Click to collapse
A nice guide about adb/fastboot can you find here:
http://androidforums.com/desire-all...fastboot-windows-updated-1st-june-2011-a.html
Flashing radio is a risky thing. Because if there something is wrong, your phone won't be more than a paperweight.
Hello,
I have two questions regarding the BCM b0.3.5_1 rom.
1. When I do a full wipe and install 0.3.4 and then upgrade to 0.3.5_1 (without any changes made on 0.3.4 and without installing any app) my internal memory is only 76 MB without any app installed? On older version of ROM I had more then 100 MB free (at least I think I had). I have ext-3 partion with 500 MB.
2. When I type in terminal SU M2SD DATA ENABLE and SU M2SD DALVIK ENABLE all I get is a list of commands, but when I type the same thing withot SU it says "M2SD data enabled. reboot to apply". Now how do I really know if data to sd and dalvik to sd is really enabled when I didn`t use SUPERUSER command? I know that it says in terminal that it is enabled but I am a litlle confused!
the su command issue it on its own then superuser will ask you to allow then do rest
seanpr92 said:
the su command issue it on its own then superuser will ask you to allow then do rest
Click to expand...
Click to collapse
thanks
thanks
A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
lovingboth said:
A first post here, please be gentle with me, and huge thanks to everyone who has made posting here unnecessary until now.
After a long time using CynogenMod 7.1 on my Desire, when I came to switching SIMs on it, I decided to look for a new ROM too because I was having a problem with shortage of app space and I was missing a few features I have become used to on JellyBean.
A look at the options found the one in the title by WoH (development forum link). It separates out the ROM and the Google Apps. I can install the ROM, and I like it a lot. I can't get the Google Apps to install.
Tried: flashing the zip file at http://woh-roms.weebly.com/gapps.html via the recovery menu, and installing a2sd. It has the right MD5 and appears to go OK, but the apps don't appear when the phone is rebooted, or appear in the list of things moved by a2sd. I have made repeated attempts, both with wiping user data before and afterwards, and doing it before rebooting after installing the ROM and after an initial boot with it, all without success.
Tried: reading the instructions there. However I don't have adb installed and because I don't have Google Play, I can't install a file manager that unzips files (the one in the ROM doesn't appear to - no unzip option is given).
Tried: installing the ROM mentioned in the development subforum thread by timvdlinde which does have Google Play. That works, but I am not so keen on the ROM itself. This may be incredibly shallow, but I liked WoH's use of the Nexus boot animation, and the timvdlinde ROM has the Nova launcher which I am not interested in.
The phone: an unlocked, rooted, AMOLED GSM Desire. The recovery is the Clockworkmod ROM Manager one. I don't remember ever changing the hboot settings. There is a sizeable ext4 partition on the SD card and it is being used by a2sd.
Click to expand...
Click to collapse
Repartition your sd-card by using the partitioning guide in my sig.
onknope what
abaaaabbbb63 said:
Repartition your sd-card by using the partitioning guide in my sig.
Click to expand...
Click to collapse
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
lovingboth said:
Thanks, but I did that before starting this. I used gparted, ending up with a large FAT32 partition, followed by a smaller ext4 and finally a small swap.
Click to expand...
Click to collapse
Theres no need for a swap partition. If you are using PA it will just act as a waste of space, since the rom doesnt utilize it in any way.
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
chromium96 said:
Try doing a full wipe and reflash the rom. Then flash these gapps. I can guarantee those work, as i use the same rom with those gapps and everything is fine. After flashing run the a2sd script through terminal.
Click to expand...
Click to collapse
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
lovingboth said:
To quote Napoleon Wilson, you can't argue with a confident man even if that's the file I've been trying - same source, same MD5
OK, I'm about to give it another go.
(And apologies if you don't identify as a man!)
Click to expand...
Click to collapse
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
chromium96 said:
Lol, weird. Im on the same rom and used the same gapps. Everything worked fine.
Click to expand...
Click to collapse
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
lovingboth said:
Not for me. I took some photos of the process, which I can put somewhere, but it was...
Repartition the SD card
Boot into recovery
Wipe data
Wipe cache
Install ROM.zip (using the one downloaded from the right place, no reported problems)
Install Gapps.zip (ditto)
Reboot
Notice that the Google apps aren't there
Do the su / mount / a2sd install anyway
Reboot (through saying yes to the third question)
Notice that the progress of the move to the ext4 partition says its moving 59 items, none of which are Google apps
Confirm that the Google apps still aren't there
I'm about to try again with another SD card on the basis of 'why not'
Click to expand...
Click to collapse
Go to system/app. Are the google apps installed? What permissions do they have?
abaaaabbbb63 said:
Go to system/app. Are the google apps installed? What permissions do they have?
Click to expand...
Click to collapse
Ah, no they're not.
About sixty are, owned by root, with rw (owner) and r (group and global) permissions.
I am being tempted to bite the bullet, install the ADK on something and try the adb method.
What about /sd-ext/gapps/system/app. Anything there?
chromium96 said:
What about /sd-ext/gapps/system/app. Anything there?
Click to expand...
Click to collapse
Yep, they are there, with what I presume are the right permissions: as above, owned by root, rw-r-r.
Doing some more nosing around, and looking at the alternative installation instructions on woh-roms.weebly.com/gapps.html
$ adb shell ls /sd-ext/gapps/system
app etc framework lib usr
Click to expand...
Click to collapse
Yes, doing
ls /sd-ext/gapps/system
produces that.
# enable extgapps (quotes needed)
$ adb shell "echo x > /sd-ext/gapps/.extgapps"
# gapps dir should look like this (if .extgapps doesnt exist the init script wont run)
$ adb shell ls -a /sd-ext/gapps/
.extgapps system
Click to expand...
Click to collapse
Yes, doing
ls -a /sd-ext/gapps/
produces that.
.extgapps is a zero byte file, rather than one byte containing 'x' as there, but the root explorer instructions would produce a zero byte file, so presumably a) there's no touch command and b) it's the presence of the file that's important, not what it contains.
BUT...
... if I do
logcat -C
(after doing logcat -c, going oops, rebooting, and getting it right )
then the lines that are supposed to be there aren't.
I'll get the email working, email the output to myself and stick it in a pastebin or similar.
pastebin.com/Qtrps3A8 has the whole thing.
At the start, various links are possibly not set up:
I/run-parts( 75): ln: /system/etc/permissions/com.google.android.maps.xml: Out of memory
I/extgapps( 155): Created /system/etc/permissions/com.google.android.maps.xml
Click to expand...
Click to collapse
is just one example, then later
D/AlarmScheduler( 1300): No events found starting within 1 week.
I/Goo Parser( 839): GAPPS: No file, skipping item 0
I/Goo Parser( 839): GAPPS URL: http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130702-signed.zip
I/AlarmReceiver( 839): gooVer: 3601
Click to expand...
Click to collapse
.. so what file is it looking for, and is this down to trying to do things with the card before it is ready?
What has changed:
The search 'app' has gone from the list - I can see from the logs that it is supposed to be replaced, but here it's just missing.
The browser is now very like Chrome... and I don't remember that being the case.
Having just run through applying the CyanogenMod 10.1(by vijendrahs - refere below) to 4.2.2 on my HTC Desire, I've now come across the above error with some of the applications that I've been trying to install.
I've partitioned my SD card and am running mounts2sd and am using link2sd. I've also downloaded and have tried the marketfix app. I've also tried killing apps and restarting the phone none of which seem to make a difference.
The research I've done indicates that this is appears to have something to do with memory. What I've noticed is that there doesn't seem to be any particular pattern to those apps that will install and those that won't. For example the Tasks app won't install nor will Yahoo but Skype, Maps, and Gmail installed fine.
I am beginning to suspect that the error message might not actually reflect the problem that is being reported. Is there a tool or some debugging routine that I can run to expose any further insights into this?
http://forum.xda-developers.com/showthread.php?t=2070704
Why did u use mounts2sd or link2sd if in threat is recommend a2sd in terminal? I used this ROM with a2sd and all was fine, no any error according memory.
Vijendrah's JB 4.2.2 has build in A2SD. Just open Terminal Emulator from menu and type:
"#su" then hit Enter;
"#a2sd" install then hit Enter;
"Y" then Enter when first question pops-up;
"N" then Enter when second question pops-up;
"Y" then Enter when third question pops-up.
Note: type only what's inside the commas.
Thanks for the replies. In my defense, it was my first attempt at a ROM flash and I probably didn't follow the instructions properly. I I'll try a re-flash over the weekend and see how that goes.
That said, I still think that the error message is misleading unless there is something in the installation routines for those apps that is validating for a minimum amount of available RAM.
Two ideas:
1.Android will give you that error when you try to reinstall app which you tampered with using lucky patcher try running it once before attempting to install and it will remove any leftover odex files it is responsible for.
2.Or the original a2sd script is messing up link2sd, try removing 10apps2sd from system/etc/init.d with root explorer or es file explorer. Reinstall link2sd afterwards.
3.you are simply running out of internal memory, link2sd leaves dalvik in there. You can explore your sdext with es file explorer and see what's going on there or use 'df' command in terminal emulator to check if there really is no space left in internal or sdext
freebird24h said:
Two ideas:
1.Android will give you that error when you try to reinstall app which you tampered with using lucky patcher try running it once before attempting to install and it will remove any leftover odex files it is responsible for.
2.Or the original a2sd script is messing up link2sd, try removing 10apps2sd from system/etc/init.d with root explorer or es file explorer. Reinstall link2sd afterwards.
3.you are simply running out of internal memory, link2sd leaves dalvik in there. You can explore your sdext with es file explorer and see what's going on there or use 'df' command in terminal emulator to check if there really is no space left in internal or sdext
Click to expand...
Click to collapse
Curious. I reran a2sd and answered no to the second question regarding data. Upon reboot, I was able to install apps that previously failed. On the downside, I've lost the home key!
I use MildWild