I now have jf adp 1.5, but I want an apps2sd firmware, but I can't decide which one is the best! probably both are the best, I know!
which are the difference between Lucid Rem and the Dude?
JF's firmware comes already supporting Apps2SD. In fact you can do it all right from the terminal on your phone. And where did you d/l from again? Because I know for a fact JF not only states this fact on his blog (the page you probably got it from) but also links to a page of concise and easy to follow instructions. Personally I think you should try all 3 (be sure to READ everything TWICE when using any firmware w/ unionfs).
Also it dosen't hurt to search as I know EVERY freaking bit of this info is w/in the first 2 pages of this forum or on JF's site....RTFM
yes I know JF is compatible to app2sd, but the process to have apps2sd is not so concise and easy: lucid Rem and the Dudes seem to be more easy!
I'm sorry if I asked: I actually red the first 3 pages, not only 2, but it is not so easy to summarize tons of information!
i went through about 8 hours worth of wiping upgrading and testing the builds.
first thing i did was wipe the ext2 partition onthe card using gparted on linux. (i actually removed the partition and repartitioned it to do so. for more stability in case of bad partitioning from before] and then i wiped the phone. before upgrading.
- original JF 1.5 stable. but apps2sd was a bit complicated.
rewipe. repartition.
- thedude's rom is stable, but i found that i could not for the life of me install games. at all. it kept coming up as con.[game].whatever and i couldn't run any of them. [tested with jewellust and tangram pro]. also, the apps2sd is in collaboration with marcusmaximus and while i love the way he did the apps2sd, there wasn't much in instructions on how to make upgrading to thedude's build + marcus' app2sd work perfectly. [i got it to work, but it was w/o it's share of problems]
another rewipe. repartition.
- using Lucidrem's modded 1.5 + apps2sd steps laid out by mailman. simple perfect. 73mb free. apps2sd and stable as hell. i would recommend this.
but most of all, just wipe the ext2 partition for stability reasons. the move from rc33 to 1.5 was not a simple upgrade with apps2sd involved.
Exegence said:
i went through about 8 hours worth of wiping upgrading and testing the builds.
first thing i did was wipe the ext2 partition onthe card using gparted on linux. (i actually removed the partition and repartitioned it to do so. for more stability in case of bad partitioning from before] and then i wiped the phone. before upgrading.
- original JF 1.5 stable. but apps2sd was a bit complicated.
rewipe. repartition.
- thedude's rom is stable, but i found that i could not for the life of me install games. at all. it kept coming up as con.[game].whatever and i couldn't run any of them. [tested with jewellust and tangram pro]. also, the apps2sd is in collaboration with marcusmaximus and while i love the way he did the apps2sd, there wasn't much in instructions on how to make upgrading to thedude's build + marcus' app2sd work perfectly. [i got it to work, but it was w/o it's share of problems]
another rewipe. repartition.
- using Lucidrem's modded 1.5 + apps2sd steps laid out by mailman. simple perfect. 73mb free. apps2sd and stable as hell. i would recommend this.
but most of all, just wipe the ext2 partition for stability reasons. the move from rc33 to 1.5 was not a simple upgrade with apps2sd involved.
Click to expand...
Click to collapse
really thanks a lot! it answers to my question!
just a dubt: my G1 is from uk, so originally it had the RC9, and after few change I came up to adp jf 1.5., the sd card (a trascendent 8gb class 6) is brand new, I just partitioned it for making ext2 partition and I didn't write anything on it. Should I wipe it as well? if yes how I should do?
if lucid rem is rteally smooth I'll go for it!
Hey there, I have the same card, if you already partitioned it but havent written anything to EXT2 you should be good. As for Lucidrem I have been using the modded JFRC33 since day one and props to all the other methods and designers of apps to sd but lucid's was the easiest for me since I dont have a home CPU. I was able to use terminal emulator to run the commands and it was extremely quick & simple. If you're unsure or not able to run adb shell on a cpu like me I would definately go with his modded version
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
borodin1 said:
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
Click to expand...
Click to collapse
I do agree that the dudes build is awsome but is it faster at first it was fast but now that i have almost 100 apps on my class 6 sd card I see the phone almost pausing when I oper certian apps. emample it I go to bettercut and try to change an icon and click on use icon pack if i have one or two icon packs its fine but if I have 6 or 8 it has a hard time opening the pop up window with the different icon packs... I have no tryed JF with apps to sd only without apps to sd and it was fine maybe i need to give it a shot and see which one is faster!!!!
borodin1 said:
Just to add to this mess
I am using Dude's build (mainly because I had it since .05) and once you update the script in 1.1 your games and protected apps should be fine.
MarcusMaximus states that unionfs method is much more stable an powerfull but I am yet to be convinced in that. It has a HUGE potential (move individual apps back and forth, boot up without sd, etc) and I see why everybody seems to jump on that boat but the question is... do we need it? If you're putting your apps on SD you probably don't want them back on your phone, and, honestly, why do you need to boot your phone without SD? I also think (and this only MY opinion as noone else stated this) that unionfs slows down you system slightly, I could be wrong. At this point, I find it more of the hassle to use it so I'm going back to JF firmware and doing sym-links.
Re-inforcing Exegence's statement, I've used sym-links (Lucid's way) since December with absolutely no problems (app, app-private, dalvik-cache, and caches for market, browser, maps and streetview).
I may see where unionfs goes in few months but at this I'll stick with true and tried.
Good luck to everyone
Click to expand...
Click to collapse
A slight oversimplification of my reasoning in using unionfs, so I'll try to explain my motivations here. My primary motivation was to make the process of moving apps to the sd card more stable. Unfortunately, I think many have misunderstood what I mean by that. I don't actually mean that it will have fewer problems, it pretty much has an equal amount from what I've seen.
What I mean by it is that in the case of a problem, the phone will still start. With the symlink method I was seeing constant problems of boot looping for no clear reason. It seemed to work *most* of the time but when it didn't the system crashed... hard. With unionfs it's extremely rare that I get any reports of problems causing the phone to not start, and when I do it's always a corrupted file system on the sd card. By far the most common problems have been certain specific apps not working(at this point togglesettings is the only one I know of that just straight doesn't work with this method... and it actually works, it just force closes on boot) and some apps having to be re-downloaded when the method is applied. There's no more than a handful of more serious problems(such as apps showing up perfectly in their correct locations on the filesystem but not showing up in the launcher... wtf) which I definitely couldn't say for the symlink method. Actually even problems with a corrupted file system are massively down from the symlink method now that mine won't let you move the app caches(responsible for every single freakin' report of stale nfs handles).
Aside from that was the ability to have some apps/storage on the sd card. This is primarily for stability reasons, just in case there's any apps that freak out(or go really slow) from being on the sd card, they can be moved to the internal memory without having to undo the whole process.
At any rate, I'm not mad at anyone(just in case anyone thought I'm upset about anything said about the unionfs method), just explaining my motivations behind making it a reality.
Maybe I'm missing something, but I really don't understand why there's umpteen different threads about moving apps to the SD card, why there are *paid* apps to do this, etc.
Is it really that hard to type:
cp -a /data/app /system/sd
cp -a /data/app-private /system/sd
rm -r /data/app
rm -r /data/app-private
ln -s /system/sd/app /data/app
ln -s /system/sd/app-private /data/app-private
Why do people make this complicated?
As for instability with the symlink method, I haven't experienced any, and I think it's specifically because I did NOT move the dalvik cache, and there are a number of good reasons for leaving it in place regardless of the method used.
ok, now everything is more... clear but complicate
another question (remember I'm a noob): what is the dalvik cache? why I shouldn't move it? is it huge?
anbd the last (for now ) which is the difference between unionsf and symlink methods?
iso67 said:
ok, now everything is more... clear but complicate
another question (remember I'm a noob): what is the dalvik cache? why I shouldn't move it? is it huge?
anbd the last (for now ) which is the difference between unionsf and symlink methods?
Click to expand...
Click to collapse
Dalvik is the name of the Java VM on Android. It's what's used to run all of the Java programs.
Dalvik-cache is a directory on the filesystem that stores optimized versions of the dex files that are contained within an application's apk archive (think of the dex file as the executable and the apk as a zip file that contains the dex file and other files).
The reason moving it can cause problems is that if dalvik-cache is not accessible, no Java programs (including system programs) can run.
I have tried every combo of build and SD card mods and must say.........they all work, and I think 90% of problems are user error, I know 9 out of 10 of my mistakes were.
My biggest advice, if you dont understand what is happening you will always make dumb mistakes and be "that guy". Try to understand what you are doing before you do it and it you may be able to understand how to fix your own problem.
brandenk said:
I have tried every combo of build and SD card mods and must say.........they all work, and I think 90% of problems are user error, I know 9 out of 10 of my mistakes were.
My biggest advice, if you dont understand what is happening you will always make dumb mistakes and be "that guy". Try to understand what you are doing before you do it and it you may be able to understand how to fix your own problem.
Click to expand...
Click to collapse
While I completely agree with you, I still think that this community needs to agree on whichever way is better and stick with it. This would make it better for developers and users.
I thinks that a pro (hint: MarcusMaximuss) needs to do some bench testing and see if both ways are equal in speed and reliability. If we prove that unionfs method is as fast as symlink onem and stays that way after few weeks of use we can conclude that it is ready for prime time and gear all efforts towards using only that method.
I am in the process of doing a so called "user test". Dude's 1.1a with unionfs apps2sd felt slow to me. At this point I switched to JF1.50 and did symlinks and it's blazing fast!!! Give me couple of days and I'll convert JFs build to unionfs and see if that stays that fast or slows down. I'll do the same thing on Dude's build once 1.2 comes out. But these will be just my impressions, no solid data to back them up.
As always, thank god for Nandroid and good luck to everyone.
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
I think another group interested in advancing these methods should come together and do a test that is more "third-party", so we can have clear and unbiased results.
Having said that, I feel that this method (unionfs) will continue to stabilize as he works on it. Especially since he has commissioned the guidance of the 3 top ROM devs. Very promising in its infancy and just needs to be refined.
cal3thousand said:
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
.
Click to expand...
Click to collapse
Agreed !!!
cal3thousand said:
I think MarcusMaximus does enough. He doesn't need more work, especially since he's not being paid (only donations).
I think another group interested in advancing these methods should come together and do a test that is more "third-party", so we can have clear and unbiased results.
Having said that, I feel that this method (unionfs) will continue to stabilize as he works on it. Especially since he has commissioned the guidance of the 3 top ROM devs. Very promising in its infancy and just needs to be refined.
Click to expand...
Click to collapse
Well... I haven't quite gotten Haykuro on board yet.
Related
Hi all...
I've been getting a lot of suspicious errors recently (force closes and app shortcut names disappearing) and I'd like to go from apps2sd back to just a normal setup with my apps on the internal phone storage.
Can somebody please verify that the instructions here are up to date? I'm a little nervous about wiping my data (or bricking my phone).
http://wiki.cyanogenmod.com/index.php/Apps2SD
Also, can somebody tell me whether doing this will wipe out the (single) app I paid for from the Marketplace? If so, can I redownload it, or will I need to pay for it a second time?
I originally got apps2sd set up by using the recovery ROM prior to flashing Modaco's custom ROM v1.1.
The easiest thing to do would be to load the new RA 1.5.1 recovery image.
Then boot into it.
Go to Partiton SD
Select FAT EXT3 SWAP
and then set the partition sizes of EXT3 and SWAP to 0
Is there a reason you want to do this???
This runs a very very minimal chances of bricking your phone. The other method on that Wiki page has more potential to get you in trouble.
Did see the market place question.
There is a method laying around somewhere to copy all of your apps back to the phone instead of loosing them. Restoring a Nandroid backup would likly put them all back into the /apps/ directory sd card or not. apps2sd just changes the location of that directory really.
But the market does keep track of your google account and what apps you purchase, you wont have to re purchase (maybe on a totaly new handset).
hope my jiberish has made sense
jashdlfjasdhfjablgjkasgjlkasfhlajshf
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
mkhopper said:
At first I was interested in the whole apps2sd process, but have yet to implement it on my rooted, Fresh 1.0 Hero since so far, I haven't really seen a need for it.
But if you were to 'turn on' apps2sd and then decide later that you don't want it, there's a possibility of bricking?? Although I assume you can always reflash the RUU if something like that were to happen? Hopefully?
Think I'll stay away from the whole offloading applications thing for awhile.
Click to expand...
Click to collapse
The possibilities of bricking the phone are very slim, but they still exist. If a phone is truly a brick, not even RUU can help. RUU has to be able to detect the phone is there in Windows, so if its beyond that RUU is useless.
Nothing to worry about as long as follow the *usually* very well written step by steps across the interweb.
If it makes you feel any better I have only heard of one or two people to brick the Hero. Most things are recoverable.
Yeah, sorry, I didn't expect it would brick the phone so much as badly mess it up - like if it expects to run apps from the SD card and they aren't there I could see the phone being tough to use as a phone, but it wouldn't really be "bricked" in the sense of not responding to user input at all.
As far as why I want to do this, I haven't really seen a huge need for apps2sd yet, and when I was recently helping an app developer to debug their app it was just one more weird variable that seemed like a possible source of problems. I'm also hoping to start developing apps myself soon, so having a more vanilla phone seems like a good idea. (I also was influenced by the Fresh ROM apps2sd rant, to be honest.)
Anyhow, thanks for your replies. I'll probably repartition the card from RUU and then restore from Nandroid at that point. Will a repartition wipe the card filesystems out, or is the partitioner smart enough to preserve the existing data?
What I did is RUUed back to 1.2, OTA updated to 1.6
Flashed to the 1.5.1 image
(At this point I went to mess with the partitions and there was no ext)
Flashed to Fresh 1.0
Okay, I finally cleaned up what I've been working on the past few weeks
New sqsh with tattoo senseui!
so this is senseui from the tattoo, so it runs at native resolution 240x320. I have not tested it at *any* other resolution.
I haven't done a lot of testing so I can't guarantee everything works... ie I think that bluetooth might be broken? who knows... other folks please post your experiences!
Please note: I *have* seen the whole thing crash due to WifiService dying on my vogue once... and I've also seen a hard lockup on the polaris once... not sure why or workaround, but it doesn't seem to be commonplace.
I use the tattoo.user.conf and I *don't* use rosie, and it runs nice and speedy... YMMV.
New rootfs that cleans up a *lot* of little things... you can now use the volume-down installer to *update* your nand partitions and back up your nand data! (you first have to have a the nand flash complete before this will work, and you need to use the rootfstonand with the updated rootfs)
Maybe I'll post some screenshots? who knows...
Everything is HERE
EDIT: Forgot the most important part... Credits!
This build is almost entirely from the Belgian HTC Click image posted somewhere out there. Lots of time was spent getting the RIL to talk to the phone application without crashes, but it seems somewhat stable now.
At my disposal I had donut and tattoo builds from enatefox, zenulator, plemen, and maybe a couple others.
Some bits needed to be swapped out to work, and that took the bulk of my time... oh well
I'll also give some creds to the folks over in kaiserland, but I'm not sure who (sorry).
Thanks muchly! Been beating my brains out trying to dyi a port of Tattoo and you've done all the hard work. Made my day, now I can go to sleep....
Trying this out tomorrow. I'll write about anything I see. Nice job.
Thanks Vilord
I'm a big fan of tattoo native resolution senseui.
testing.
lauyanyameric said:
it says:
No sys found on SD, booting Part/NAND
(e2fsck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
/dev/block/mmcblk0p3: clean, 11/130560 files, 18794/522112 blocks
Using partitioned system
e2fsck 1.41.4 (27-Jan-2009)
/dev/block/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
mount: Device or resource busy
Failed
Failed to mount /system
_
Click to expand...
Click to collapse
that is likely due to my new partition/nand management code...
What is your partition setup?
I'll poke at it in a few minutes
vilord said:
that is likely due to my new partition/nand management code...
What is your partition setup?
I'll poke at it in a few minutes
Click to expand...
Click to collapse
I don't know what could be causing the bootup issue
I dropped in some debugs and catchalls that might help
The faster!
This is the fastest version ever.
i'm using haret and no paritions, works perfect!
i wish i could put it on nand, but i'm using a NIKE and the NBH is for vogue...
NICE JOB VILORD!
Hi,.
Thanks vilord, this is the best build with sense that i have tried.
I have the mount system error the first time i try to boot it, the second time it boot without problem.
Im wrting this from this build
arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?
all: I'm still not 100% sure why the installer's choking, but I'll poke it when I get home (I still need to partition the SD on my POLA200, so I should be able to see exactly what you see when I do it)
Sigh, more user freindly
I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.
Or am I just full of it?
no you're completely right.
Once I get things ironed out with the installer, and after I've gotten some more feedback, I'll put it together with two zip downloads, one for NAND installation and one for haret/SD installation.
vilord said:
arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?
Click to expand...
Click to collapse
Since the vibration was disabled (2009-09-22) all the builds works almost like vogue, except for:
Camera: never worked, maybe because the drivers are diferent or because nike camera max resolutuion is 2MP (force close)
Bluetooth: never worked, maybe drivers
Vibration: disabled
everythig else works perfect.
gjbnh said:
I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.
Or am I just full of it?
Click to expand...
Click to collapse
I think this is a good idea too..thanks.
Im having trouble with data connection. it was one for a moment then stopped. Any suggestions?
Never mind I got it working. It was turned off in the settings. great build!
I'll make this nandable and post soon.
got it booted - without ext partitions
lauyanyameric said:
it says:
No sys found on SD, booting Part/NAND
(e2fsck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
/dev/block/mmcblk0p3: clean, 11/130560 files, 18794/522112 blocks
Using partitioned system
e2fsck 1.41.4 (27-Jan-2009)
/dev/block/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
mount: Device or resource busy
Failed
Failed to mount /system
_
Click to expand...
Click to collapse
I am really looking forward to this, but get the same result as lauyanyameric on my Kaiser, afterwards I am dropped to shell .... Anything I can do to help debug?
Tried it without partition, and I get data error and it created a 34 mb data.img.
Tried with a blank data.img (no partitions) and I was able to boot!
Grateful for your work! Thanks.
try formating your sd card again...
So far, so great.
Running via Haret and this is working superbly. Everything that should be working, is working.
So far have tested audio, data, GPS, camera (via Camera Pro), and apps such as Voice Search, Exchange Sync, Market and they all work and are quite responsive.
Noticed a few rosie reloads after using memory intensive apps, so I added a 32mb swap in the conf file. So far no more rosie reloads.
Also, the USB to PC app doesn't appear to like my work machine. Not sure if this is an issue with the desktop or the app.
Will be flashing to NAND after a bit more testing.
Thanks again Jesse!
Cheers
Nick
First off thanks for all the hard work you and others have done bringing android to the vogue. I have donut running off of nand right now and love it but am wanting to try this build but have no idea how to reflash it on there. i have tried searching and searching but i havent found a good answer on how to do it.
nabicat said:
So far, so great.
Running via Haret and this is working superbly. Everything that should be working, is working.
So far have tested audio, data, GPS, camera (via Camera Pro), and apps such as Voice Search, Exchange Sync, Market and they all work and are quite responsive.
Noticed a few rosie reloads after using memory intensive apps, so I added a 32mb swap in the conf file. So far no more rosie reloads.
Also, the USB to PC app doesn't appear to like my work machine. Not sure if this is an issue with the desktop or the app.
Will be flashing to NAND after a bit more testing.
Thanks again Jesse!
Cheers
Nick
Click to expand...
Click to collapse
Im getting the Rosie reloads too... how do you add the 32mb swap or better yet can you just upload your conf file? Thanks
vilord said:
no you're completely right.
Once I get things ironed out with the installer, and after I've gotten some more feedback, I'll put it together with two zip downloads, one for NAND installation and one for haret/SD installation.
Click to expand...
Click to collapse
Thank you I think doing this will add a layer of usability to the releases, and gain a greater community of users as a result. Personally I would rather have releases further apart in time with this kind of thing rather than a rush to try the newest toy.
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Firstly it needs to have a recovery image installed I recommend Amon-Ra v 1.6.2.
Secondly you need to find the radio rom you wish to flash and put it onto the root of you phones sd card.
Thirdly enter the recovery image you have installed by holding power and home button from the phone being off.
Then select the radio.zip to flash.
Everything I have said here can easily be found how to do via searching this forum or its wiki.
also www.theunlockr.com will help with installing the recovery image.
lohtse said:
Hi Folks.
Just been issued heros at work and wish to update the radio rom...How is this accomplished??
regards
Lohtse
Click to expand...
Click to collapse
First you will need to install the custom recovery console if you haven't done so already.
Then download your updated radio, put it on your SD, load into the recovery, then apply update. DONE!
If that is too brief,... let me know,...
EDIT... Ooops,... too late.
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Lennyuk said:
really? its not complicated at all when you know what your doing. In fact I can say its a damn sight easier (and safer) than modifying blackberry roms and from what I hear also Windows Mobile.
Click to expand...
Click to collapse
I came from wimo to android, and as it is said, it's quite hard to catch the thing at the beginning, but after everything seems easier than in wimo !! and more reliable... you have almost no chance to brick your hero after you installed the recovery boot.
radio : boot in recovery then select the good option.
rom : nandroid backup / install whatever rom you want / if you don't like it go for nandroid restore ( all you need is two Sd card.. the good one and the one for the "tests" ).... etc....
But at the beginning i was totally out but with a little time.. reading some posts (here and on the web) ... one day everything was more clear !
Ciao
Fred
lohtse said:
way to complicated...
Too much to do and can screw up..... At least with winmo and symbian was a few clicks...
hmmmmm think will ditch android.....
Click to expand...
Click to collapse
Its not hard at all. You can have the recovery installed and the radio updated in 5 minutes.
For step by step instructions follow the "Installing a recovery image" section in BTDAG's guide linked in my signature.
Then further down the same post, in the second yellow box there are instructions on "Updating your Radio".
Guys, the OP said he was issued the Hero at work, then two hours later said he was going to ditch Android... so what then, he's quitting his job? Troll alert. Don't feed the troll.
As to troll comment(yes offence has been caused)....hmmmmm.... Am going back to the trusty Kaiser... WE DON'T HAVE TO USE THE HERO.... We live in free(ish) world.. And the Phones are issued as an update to our old duty phones... Also I'm not the only one who uses them that feels the same.
Now to updating being easy. Gulp I must be eeer dum!!! Du hu Du HU must be the TROLL in me!
I have tried to install recovery image thing and well just cant get it to work... And now I find I have to root the hero too so things will install to sd card!!!! WTF this should all be standard like winmo and symbian etc...
I have been using smart phones since the Ericsson r380 and so far Android has failed to impress to the degree I am beginning to hate it....
Am far to used to having simply andfull access to everything..
Android is a HUGE learning curve that I suspect I may not have the patience for..
regards The TROLL sorry I mean Lohtse
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL
My final questions are this how do I root so I can install to sd card(just point me in the right direction) And do I have to unlock Phone to any network to have custom roms on..
regards
TROLL
Click to expand...
Click to collapse
Wahey!!!! Good job man.
Ok,... So now you have the recovery image all you need to do is pick a custom ROM. Personally, I highly recommend MCR3.2 (link in signature at botom). It is an Android 1.5 ROM but is stable and fast, what more could you want for a work phone.This ROM is rooted and has apps2SD enabled. Once you have installed the ROM you will need to remember to create an ext2 partition on the SD card (easily done through the recovery). Then you are set to go!!!!
lohtse said:
Now I have finally managed to get recovery image on and updated the radio...Being called a troll did it !!!!!!.....LOL TROLL
Click to expand...
Click to collapse
You're welcome And what ddotpatel said. MCR is fast & clean. By installing a custom recovery you've already done the only tricky bit.
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
lohtse said:
Yep installed 3.2 from modocca. seems nice but how do you know if the apps are installing to sdcard???? I'm not sure they are lol..
Click to expand...
Click to collapse
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Someone with more knowhow than me correct me if I am wrong?... CAULI?,... LENNY?
Can someone who knows please answer this question:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Thanks!
ddotpatel said:
You need to create an ext2 partition on your SD card through the recovery again. I cant remember the exact wording but something like "create ext2 + fat" or something along those lines.
As far as I know, once that has been done all apps will install to SD.
Click to expand...
Click to collapse
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition. All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer, if you're curious. Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed. The saving you make just from shifting the apks to sd is more than enough for most people it seems.
cauli said:
Yup, certainly as far as MCR is concerned. On the first reboot it will move all files from /data/app to /system/sd/app (& similarly for app-private) Nb /sysytem/sd is the mount point for the ext2 partition.
All it does is move the files over & then replaces the /data/app (& app-private) directory with a symlink to the new location. That way future installs, updates etc all automatically go to the new location.
You can always check yourself with a terminal emulator & the command ls -l, or using a file manager like Root Explorer.
Some people think it's not working because they see available space in internal flash drop as apps are installed, but that's because app data & the dalvik cache remain on internal flash, principally aiui for reasons of access speed.
Click to expand...
Click to collapse
hmmmm I certainly noticed a drop in available memory on the phone to the degree of only having 54 megs free...
SebHTCHero said:
Are you 100% sure that flashing the Radio ROM does not affect the phone RF Calibration ?
Click to expand...
Click to collapse
what is rf calibration?
What is radio rom used for by phone?
kendong2 said:
what is rf calibration?
Click to expand...
Click to collapse
A set of tables usually stored in NVRAM that takes into account the slight differences in the components used to build your phone. Every single phone is calibrated during manufacturing.
If the calibration is erased, it will look like it works but you can have all sort of problems from poor battery life to random drop from the network or poor sensibility (not to mention the higher than expected radio levels you could be emitting right next to your brain )
This is a quick walkthrough of how to apply my variant of "Mimicans speedfix" using my kernels on the Captivate. The speedfix essentially consists of making an ext3 or ext4 filesystem on an sdcard, and using that as our /data directory. This method is different from the original method in many of the details, but the underlying basis is that the stock /data partition is slow as molasses so we replace it.
This method should be pretty safe. As you will notice we dont copy around stuff and create a symlink mess. We just mount a partition over the current one. Yes we still mount the old one as well, even though it wont be used unless you take your card out. If that happens the phone will mount your old /data (that will probably be very out of date at the time) but itll get you up and running right away.
Right now there are two kernels, these mount the default partition, ext3 or ext4 on the second sdcard partition, the two options are:
Stock clock speed and Overclocked.
The overclocked kernel will clock from 100 to 800 Mhz as stock, then skippinig 1Ghz going to 1.2 Ghz.
Also, before we begin make sure you have this version of Odin. I used Samsung windows drivers that I found here.
You'll also want to read this thread about download mode. here you'll learn that you will have to try real hard to actually brick these phones, and even then it may still boot.
Ofcourse you also want to have root on your captivate.
You'll also need the android sdk.
If you are on Windows or Mac you will need some software to partition and format the sdcard, this live cd will work. You could also just get an ubuntu live cd or similar.
So, now we have the necessary tools and our new kernels and can get started.
Partition the disk:
There were reports from the modaco forums when mimocan first released his fix that ext3/4 partitions larger than 2gb were a problem, so keep your 2nd partition 2gb or smaller.
Use your favorite partitioning sofware to create 2 partitions on your sdcard. the first one will be formated FAT32 (vfat), and the second one ext3 or ext4. Make sure both are 'primary partitions'. You may want to make the second partition have partition type 83 (linux native).
Copy data files to sdcard:
If you are coming from stock, (eg without an existing a2sd /data partition on your sdcard) boot the phone without your formatted card and hotplug it before starting this process.
Using the sdk you need to connect the phone and use 'adb shell' to get a prompt on the phone.
Then follow these steps:
Code:
$
$ su -
# mkdir /sdcard/mnt
# mount -t ext4 /dev/block/mmcblk1p2 /sdcard/mnt
# busybox cp -a /data/* /sdcard/mnt
# umount /sdcard/mnt
# exit
$ exit
Flashing the kernel
1) Disconnect USB cable.
2) Open up odin.
3) Put your phone into download mode.
4) Connect USB cable, wait a second Odin should detect your phone, if not fiddle about with your drivers and reboot windows or something. This can be a real PITA.
5) In Odin load the kernel tarfile as "CSC"
6) Click "Start" in Odin, flashing should only take a few seconds.
You may run into issues here randomly and have a phone with the phone-!-computer image (I did!). Just go read up on the 'download mode' thread linked above it tells you how to proceed.
7) When you have booted your new kernel and /data partition you may have some issues with a few widgets/apps. Reinstalling or waiting/fiddeling with them seems to solve the issue. Maps was slow to open the first time after a new /data partition was mounted for me a few times, but subsequent launches were snappy.
If you want you may donate to my beer fund. It is not necessary but much appreciated
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Worked great for me using ext4 partition/kernel. It brought my quadrant to 1817! Thats with a poor little 4gig, class 2 micro sd card. Im also running the i9000 JM2 firmware with Samset 1.6.
Thank you for all your hard work!!!! My phone is now complete (for now lol).
andy2na said:
I get 1716 scores in quadrant, but with real world running tests Touchdown and Dolphin HD browser still lag like holy hell.
I originally had the "method 2" hack (moving apps to the NAND) and that worked wonders, especially with these apps.
Can anyone test these two applications and see if there is lag for you?
Dolphin - try opening a new tab, closing it, and goto a large page and scroll with the volume buttons - it should all be smooth and quick
Touchdown - It should be very quick going between emails, I get a 5+ second delay before showing the email
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Its a brand new Kingston 8gb class 4 card, havent used it before applying this hack
Postal76 said:
Didn't work for me. I partitioned my external SD card, flashed the speedup2 kernel, then ran the commands you posted, replacing 'ext3' with 'ext4'. My quadrant score is still in the low 900's.
Can you explain exactly what those commands do? The mimocan fix makes a lot more sense to me. Why did you decide to take a different approach?
Thanks for your help and effort!
Click to expand...
Click to collapse
All you do is copy the files from your original /data partition onto the root of your ext{3|4} partition on the sdcard. Then that is mounted on reboot ontop of /data so you can use the new data partition from your card.
I feel this is a MUCH cleaner method than the original Mimocan fix, that copis a full copy of data into the root of the device (unnecessary backup since you still have your original /data partition as well), then it mounts your sdcard on /disk and symlinks that to /data.
I just don't see the need for the symlinks and stuff and honestly I thought this was a simpler method, no symlinks or anything.
If you arent seeing any speedups I'm betting something didn't go right, you are probably still running of the old /data partition. Are you sure you are running the speedup2 kernel and not the ext4 only kernel?
spyz88 said:
The captivate speedup kernel link is dead. Can soneone please post a mirror? Thanks
Click to expand...
Click to collapse
It seems to work from here...
_Opiate_ said:
Might be tome for you to pick up a new SD card. I have used both fix's and find this fix to be way better. I get no lag in Dolphin HD.
Click to expand...
Click to collapse
Except the Quadrant scores do you notice any real speed boost?
andy2na said:
.....
Also in Quadrant, even though I get 1700 scores, do you guys get stuck at I/O Database writes for a good 3+ minutes?
Click to expand...
Click to collapse
yeah database I/O takes forever still.
Like I said in the other thread, try to reinstall the apps, Dolphin is very very fast here (thanks for getting me a new browser btw.)
I'm still a complete failure and now i get stuck at the galaxy s boot screen
Nuke, after doing the ext4 only method, I only get quadrant scores of 900.
Am I doing something wrong? I go through all the steps fine and everything seems like it went well but it seems like I'm doing something wrong down the line.
one thing I do notice is that I have A LOT MORE AVAILABLE MEMORY in advanced task killer. I use to only have 100 now I have 180MB.
Is it crucial to have to flash the Speedfix2?
after i put in
busybox cp -a /data/*
nothing happens it just sits there
igm503 said:
after i put in
busybox cp -a /data/*
nothing happens it just sits there
Click to expand...
Click to collapse
that part took like 15 min for me since I have a lot of application and app data
but there is no trailing dot it just repeats what i typed and then leaves a blank space
same thing it just repeats it
igm503 said:
but there is no trailing dot it just repeats what i typed and then leaves a blank space
Click to expand...
Click to collapse
What do you mean by "there is no trailing dot" ? Did you type it in? You need to include the trailing dot in your command; based on what you posted it appears you did not do that.
WOW! Okay... So now I'm getting 1756...
You just have to leave Quadrant on for like 15 minutes sometimes! This is very strange!
Notice the period after the asterisk. In the old forum, someone had a problem with that.
I did this fix last night after countless times of my messing up and figuring out how to partition with my phone still being able to read the card, flash problems with Odin, etc etc. I'm using an 8gb Classic 6 and just got an 1805 in Quadrant, and the phone is incredibly, noticeably faster. Did have some weird app problems when it was first applied, but some reinstalls fixed it. Thanks again Nuka!
Sent from my SAMSUNG-SGH-I897 using XDA App
Question...
I moved a lot of applications to my SD Card. The problem is that it seems to move every app off of the root directory which makes for a messy SD Card directory structure.
Is there no way to move the apps to a directory called /apps or something like that??
Milkman00 said:
Question...
I moved a lot of applications to my SD Card. The problem is that it seems to move every app off of the root directory which makes for a messy SD Card directory structure.
Is there no way to move the apps to a directory called /apps or something like that??
Click to expand...
Click to collapse
It should move it to sdcard/data/app/
Whosdaman said:
It should move it to sdcard/data/app/
Click to expand...
Click to collapse
I have a few files in my root directory starting with . (like .android_secure, .dataviz, .downloadTemp, etc.), and also having some start with com., and others that are regular applications.
In my apps/data directory there is only like one app... I don't get why this is so messy?
Milkman00 said:
I have a few files in my root directory starting with . (like .android_secure, .dataviz, .downloadTemp, etc.), and also having some start with com., and others that are regular applications.
In my apps/data directory there is only like one app... I don't get why this is so messy?
Click to expand...
Click to collapse
any directory starting with a "." is a hidden directory and thus should not be accessed by the user. just let android handle the directories and return to stock as you wont have any issues if you are using an ext4 with journaling turned off. EXT4 sucks data loss and fc all the time after a few days unless you allways reinstall your rom everyday i usually do.... i decided to use one rom for a few days and then i get those stupid errors.
dzuchowski said:
any directory starting with a "." is a hidden directory and thus should not be accessed by the user. just let android handle the directories and return to stock as you wont have any issues if you are using an ext4 with journaling turned off. EXT4 sucks data loss and fc all the time after a few days unless you allways reinstall your rom everyday i usually do.... i decided to use one rom for a few days and then i get those stupid errors.
Click to expand...
Click to collapse
You state these problems with EXT4 as if they are standalone facts. They are not.
I have had none of the problems you refer to with EXT4, and have benn enjoying this technology since Bonsai 3.0.0 on DK28. I do not experience any issues compared to RFS, do not have to reinstall my ROM, etc. I am a very happy user of EB13-based Bonsai 3.0.1.
The only issues I've had have been generic EB13 problems-- Bluetooth connectivity, audio routing after disconnecting BT A2DP, and some problems with apps moved to SD via Titanium Backup that were not available to be moved via the standard method in Manage Applications.
With many thousands of people using EXT4 via Bonsai, ACS, and all the other bleeding-edge ROMs, and the lack of problems for most --perhaps 95% or better -- the issue is obviously something YOU'RE doing, not the EXT4 technology.
I know that isn't helpful to you, and I sincerely have sympathy. I hope the community can help you, and others, figure out the cause of your difficulties.
Regardless, it is not helpful, nor does it contribute to the community, to spread false information. It's true that for you and a handful of people that EXT4 is problematic; it is not true that EXT4 if some sort of risky feature that should be avoided.
Rather, EXT4 is a solid, very useful step forward in technology with major advantages. No one here should fear using it any more than any of the other mods they're willing to risk beyond using the official stock software.
Sent from my mind using telepathitalk