Has anyone tried Clemsyn's updated kernels from the Kaiser section on the Vogue? I'd like to try them since people say they are more stable, but ATools doesn't work for me and can't properly get the kernel to install on nand... Keeps making system and data .imgs regardless of settings.
Anybody have a working kernel they could post?
Have had the same issue. Would love to try clemsyn's rom on Vogue but can't get it to work through Atools.
I've gone back to Incubus's v12 froyo just for the battery life. I think v10.5 had the best battery life, but was a bit buggy. Using the latest rom from liq1d (Nov 30? i think) Relatively stable with v12 and decent battery life again compared to thoughtlesskyle's v17.
Try this out...
Download the latest Atools 1.1.4 here:
http://sourceforge.net/projects/androidhtc/files/AtoolsRelease/
Open Clemsyn's Kernel - located here:
http://forum.xda-developers.com/showpost.php?p=9768617&postcount=63
With the Atools 1.1.4.py - choose Vogue, screen res, Froyo, then save it somewhere.
Now - use the attached Atools to open that new saved NBH and edit it how you want for your Vogue.
Save this atools-old.zip - this is the one I always use to modify kernel NBH for my vogue.
Forgot - also for the newer NBH files, l1q1d had an update file that needed to be applied
to Froyo builds so that it would allow it to boot - attaching that as well as it can be hard to find.
@Does_It_Matter: Does work the USB mass storage with this kernel?
Josue_181 said:
@Does_It_Matter: Does work the USB mass storage with this kernel?
Click to expand...
Click to collapse
Nope - can't get it to work for me.
Last working kernel for the Vogue - WITH USB support working, was the
10-31-10 2.6.25 NBH kernel - I tested all of them - lots of flashing!
I can say that it does not work, but the smart thing to do for stability right now is to use data on SD anyways for space reasons also stability if on .32 kernel. With that you could just pull the card out and put it in a reader. That is what I do with my card.
Does_It_Matter said:
Nope - can't get it to work for me.
Last working kernel for the Vogue - WITH USB support working, was the
10-31-10 2.6.25 NBH kernel - I tested all of them - lots of flashing!
Click to expand...
Click to collapse
Ok, thank you very much for the information I will continue with that kernel because the solution that I mentioned aceoyame not seems best.
aceoyame said:
I can say that it does not work, but the smart thing to do for stability right now is to use data on SD anyways for space reasons also stability if on .32 kernel. With that you could just pull the card out and put it in a reader. That is what I do with my card.
Click to expand...
Click to collapse
Improved stability with data on SD? This is the first I've heard of this, but I'm definitely interested. Are you talking ext2 or data.img? Is this related to the yaffs thing, or just personal experience? I would love to see my phone freeze less.
It is related to YAFFS. On SD it uses EXT2 or an image file. The image file is the best as it has file checking on it every boot/mount. YAFFS is the file system on the NAND and we don't have it working 100% stable just yet. If you do go the SD route just have a fast SD card. Don't spend extra on a class 10 card as it will be a moot point. The card can't push 10 MB/s in our devices. Even 6 is almost pointless, I wanna say it pushes around 5 MB/s
Thanks for the nice explanation. I guess I had discounted the .img method because it was the "old way", but I guess that means it's just extra well tested. Would ext2 have performance benefits over the .img? I'm not entirely sure what's in the .img file--is that just a virtual partition of ext2? Or is it a different file system altogether? Is it using any compression, or is it just a direct read/write file?
Now that I think about it, my phone was at its peak stability back in the days of Fresh Froyo using ext2 sys/data through Haret (before I had the courage to flash to nand). Nand brought speed and ease of rebooting once crashed/dead battery, but in the stability department it never held a candle to the SD card.
I like the idea of mixing system on nand and data on SD. I think I will try that tonight. No sense messing around with yaffs corrupting my files every day.
wondercow said:
Thanks for the nice explanation. I guess I had discounted the .img method because it was the "old way", but I guess that means it's just extra well tested. Would ext2 have performance benefits over the .img? I'm not entirely sure what's in the .img file--is that just a virtual partition of ext2? Or is it a different file system altogether? Is it using any compression, or is it just a direct read/write file?
Now that I think about it, my phone was at its peak stability back in the days of Fresh Froyo using ext2 sys/data through Haret (before I had the courage to flash to nand). Nand brought speed and ease of rebooting once crashed/dead battery, but in the stability department it never held a candle to the SD card.
I like the idea of mixing system on nand and data on SD. I think I will try that tonight. No sense messing around with yaffs corrupting my files every day.
Click to expand...
Click to collapse
Yep thats the logic I used. Any Odex'd build with Clemsyns kernel with Sys on Nand and data on an img file will last a long time. I haven't had corruption in over a month I wanna say with light usage on my kaiser. The odex'ing helps just because it makes for less writes to NAND.
Related
Copied here, cos it was posted wrongly elsewhere.
---------
Hello all, sorry if this is a basic question, but wasnt able to find any results.
Over the past few days, I have been staying up late almost every single night and trying out different ROMs in this forum.
1. The Dude's ROM
This rom looks nice, but almost all applications crashed like nuts. Then I realised the developer has gone on a vacation, so cant really use this.
2. Cyan's ROM
Fast, but still uses SD for theapps. I have a class 2 sdhc, and that isnt fast enough and hence the apps are a bit slow to respond. Crashes are much much lesser than #1.
3. Hero's ROMs
Very well made, fantastic ROM, absolutely stunning UI but again dependency on the SDCARD is immense and is thus a limitation to me. Also I saw the actual HTC Hero has much higher ROM space (512mb compared to 288 of Dream/G1 and more ram 256 vs 198 of G1) and hence is much better suited to run the HTC's Rosie.
So now I think my needs would want me a basic android cupcake ROM without much fancy stuff. The bare minimum. Do we have such a ROM?
If we do, please let me know.
---------------------------
Update : I am looking for a base android system with root. If possible maybe start building on something. I have experience tweaking kernels on a desktop , but has _never_ tried anything mobile.
I was suggested to use Haykuro's 6.0r1 , but it does use apps2sd and so does cyan's rom.
Well my idea is to find/create a ROM which would be light and fast and we could do some work optimizing the kernel for faster loads and quick runs.
Any suggestions, guides, materials on how to start would be greatly helpful.
----------------------
Goal : A quick to boot, fast ROM with low battery consumption.
The search button is your friend.
Visit JF's blog
Search for JF 1.51 =]
Here to save you some time:
http://andblogs.net/2009/05/jfv151-images-are-out/
JF tends to work on the stock roms, and just roots it, with very minor modifications. But super stable, fast, and works excellent.
Haykuro's ion rom
Use Haykuro's IOn Rom its fast stable and just your basic android goodness
avallark said:
I was suggested to use Haykuro's 6.0r1 , but it does use apps2sd and so does cyan's rom.
Click to expand...
Click to collapse
Actually, most ROMs that make use of some form of A2SD (apps on SD cards) do so conditionally. Both Haykuro and cyanogen have ROMs that put the /system/app directory on the SD card only if the SD card has a prepared ext2/3 partition present at boot. What this means is that if you are using a regular SD card, or if you repartition your card as FAT32, then the ROM will not implement A2SD.
However, I am in agreement with you for the gist of the request. I would also like to see an optimized ROM based on AOSP (like cyanogen or TheDude), but one that implements fewer customizations. Personally, I am currently using cyanogen's 3.9, which has great performance, and the fastest boot times I have had from any other ROM. It seems to run through the battery a little faster than others, but it is the best so far.
jf or cyanogen
even though u have an class 2 apps2sd would work good. i had a lame stock 1gig tmo gives with the fone and i had no problem with it. or jf as close to stock as possible
You do know that Apps2SD is not a requirement for CyanogenMod, right? If you have a single Fat32 partition on your card, Apps2SD is disabled and all apps will go to the phone's internal memory. Of course in this case you are limiting yourself to the amount of apps you can have installed at any given time due to the relatively small space left on the intmem after the OS is installed. Also, if you install too many apps your phone will start slowing down considerably because the apps basically eat up the available RAM.
Personally, half the reason for rooting my phone in the first place was running apps on SD card. My co-worker has yet to root his G1 and he constantly has to juggle apps and games so that he can have at least 10MB internal memory free, otherwise his phone starts slowing down to a crawl.
I'm working on an HTC ADP version of what you seek!
I've had two other people ask for this from me!
I create a "US specific" version for T-Mobile Users.
See thread (http://forum.xda-developers.com/showthread.php?t=538456).
Would you be interested in a HTC ADP plain rooted (no features) version? I'm trying to gauge the need here ?
I'm tryin to finish a lite version of ion. I don't think I can strip anything else out without it breaking. The whole purpose behind the lite version will be to put what customizations you want on it. It a lot slimmer than a standard jf release.
soulife's ion - probably another good bet
Soulife's ION build (lite), (as it sounds), would also be a another good build for you likely!
He makes/ports good/stable ROM's.
pistol4413 said:
i had a lame stock 1gig tmo gives with the fone and i had no problem with it.
Click to expand...
Click to collapse
Lol I still use this P.O.S. It's actually not too bad since I haven't experienced the greateness of a class 6 card. I'm happy with my G1 performance.
did you try this: http://forum.xda-developers.com/showthread.php?t=538456
and I just rooted someone's phone with a stock 1gb no class card and it runs Cy3681 great. Compcache is the best.
where can i get the default g1 wallpapers? i realize how dumb that sounds but ive googled them, looked for them in the themes section, and searched through the files of the 25 or so builds i have downloaded from here...i am not smart.
I also wanted a stock rom with just root and without the piles of shi.... code that are being piled on top of the custom builds. I found two easy ways to it;
1. JF's roms. All he does is root it and release it. Unfortunately, for the cupcake builds, he got the awful idea of talking with crazy narcissist haykuro and actually implemented a2sd on 1.51 and 1.51r2. Getting rid of it is nastily simple, though. Just delete a2sd from /system/bin and you're done.
2. Get a dump of an official OTA rom, put the modified su binary in /system/bin, superuser.apk on /system/app, and pack it with a rooted boot.img, or if you can modify kernel (i don't know that much linux) root your own boot.img. Look through somebody else's update-scripts so you can make your own (I've found cyanogen's and JF's to be amongst the cleanest, easiest to read and figure out).
soulife, I'd love to see what you come up with. I have among my stash of experimental stuff a slimmed down ION r2 that only kept a few apps (Phone, contacts, browser, mms, cameras, and settings), but quickly felt that there really was no reason to slim it down so bare. With ION, there's still a lot of space left in system, even with a stock spl, and after an install it's never used again, so I felt I should be adding instead of removing apps than let that empty space go to waste, specially since there's really no replacement or improved app for the ones that were removed
I suggest you go out and buy a new micro sd card, preferably a class 4 or 6 micro sd card. Then you can really begin enjoying the capabilities of root.
4gb class 4 by adata for 12 bucks i believe on newegg.
8gb transcend class 6 for $19, also on newegg.
i just switched back to JF 1.51 with the hero theme 1.4.5. I think it might still have the a2sd script in it but it's optional, but boot time is MUCH faster than cyanogens current builds.
The stock ION and Rogers ROMs are good as well, but I do enjoy the hero theme on JF , although the Rogers dialer is a great thing to have.
jubeh said:
I also wanted a stock rom with just root and without the piles of shi.... code that are being piled on top of the custom builds.
Click to expand...
Click to collapse
Wow...**** code. Who'd a thunk that people would be modifying stock ROMs on a developers forum. If you are going to debase a developers work, at least specify which developer. The way your statement reads, nothing but crap comes out of this forum.
Hello, I would like to know what steps that I can take to increase the performance of android on my vogue. I am using myn's warm donut rom, with the system installed on the nand and the data installed on my ext2 partition on my sd card. I have heard that Its a good ideal to enable swapping, but I do not know how to enable it. I already have my 8GB class 6 sd card partitioned with one fat partition, one 256MB ext2 partition, and one 1GB ext2 partition (for Data). If anyone has any suggestions or tips, please let me know. Thanks!
PS: is there a way to overclock my vogue while using android? I have tried using the clock.sh file from mssmison's legendary build, but that didn't work.
EDIT: Can i use an ext3 or ext4 instead of ext2 for the partitions on the sd card?
Soon there will be an app for overclocking. Myn is currently working on it.
Other that that, make sure you're always on the latest nbh and Myn release.
Get yourself a task manager and be mindful of what processes you actually need.
Use clearcache often.
go into dev tools/development settings and set the window and transition animation to OFF. i noticed that not only does everything open super quick but it did increase the overal performance
you can't use ext3 or 4 no. First thing is to make sure if you are running data on your sdcard that you are using a fast sd card (not a cheap one).
That's what is giving you the biggest performance hit right now.
There is an OC app coming but to be honest it really should be running quite snappy for you.
Thanks guys for all of the info. I have just one more question. should I enable swapping on my android? Advanced task manager usually reports that I have around 46-40MB of free ram.
If you have a lot of free memory already, there is no reason to use swap.
Ok, I have one last question (I apologize if I'm being a bit annoying). I tried installing and using Adfree on my vogue, but when I run it, it says "Cannot locate the 'cat' util on your system". Does anyone know how I can fix this? also, when my phone is connected to my charger, my phone's 3g speeds are really good, but when It's not on the charger, the 3g slows down. Normally I'm ok with it, but it may make playing some games online a bit more difficult when off the charger. Is there some way I can fix this? Thanks!
slow88lx said:
Soon there will be an app for overclocking. Myn is currently working on it.
Other that that, make sure you're always on the latest nbh and Myn release.
Get yourself a task manager and be mindful of what processes you actually need.
Click to expand...
Click to collapse
Can you install a new .nbh without updating the release you are running, or do you need to wipe the phone every time?
conanford said:
Can you install a new .nbh without updating the release you are running, or do you need to wipe the phone every time?
Click to expand...
Click to collapse
you can flash nbh without wiping system or data
This has been updated to be deodexed+root+busybox only (though it still supports JAC kernel out of the box). At this point there are so many different lag fixes that it's hard to keep up with them all.
What it does have:
ROOT
No .odex files (deodexed)
Newest Busybox
ext manipulation files and libs, so it makes it easier to e2fsck or tune2fsck if you want ext4.
Also thanks to eugene373 for his work in establishing a baseline update.zip without which this would have taken a great deal more work.
Should work in clockwork, doesn't seem to need a wipe. If you have problems, use regular recovery, just rename it to "update.zip" on the root of your sdcard and it should flash just fine.
WARNING:
This should be completely safe. Nonetheless, should loss of job/loss of fertility/nuclear war ensue, I am not responsible.
Instructions:
1. Load the .zip file onto the root of your internal SD card (/sdcard)
2. Using Clockwork recovery, do "Install zip from SD card", then "Choose zip from sdcard", choose the VibrantDeodexed.zip, and choose "Yes"
2b.(ONLY If you don't have Clockwork) rename the download to "update.zip" and place it on the root of your sdcard. Then reboot into recovery and choose "Update packages".
3. (Optional) Flash JAC's kernel with ODIN using the directions specified HERE It is more stable and gets better benchmarks but there do seem to be some issues with the screen taking a while to wake up.
http://www.getyourboneon.com/VibrantDeodexed1_2.zip
NOTE: The first boot takes a long time because it has to dexopt stuff.
Version 1.0:
Just stock and rooted w/busybox
Version 1.1:
Uses the latest version of busybox and comes with support for JAC kernel out of the box (no need to flash the init.d update.zip and supersedes my method if his kernel is flashed.)
Version 1.2:
Updated busybox, added ext tools. Removed all lag fixes, though it will still work with the JAC kernels.
There are so many lag fixes out there at the moment that I didn't want to "lock in" people to a particular one.
Part of the high quadrant score is the 90 million triangles/sec. The data script boosts the data score.
Sent from my SGH-T959 using XDA App
what is the ext hack? and how does it make the phone faster?
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
original link is here for the hack--http://forum.xda-developers.com/showthread.php?t=739647
anomalous, thanks for all your hard work...
so if we get a good deodexed rom, someone could compile JIT for our 2.1 right?
junkdruggler said:
the ext hack puts the data and dalvik cache on the sdcard on an ext2/3 partition...
it brought my quadrant score from 850-950 up to 1400-1500
its like apps2sd but the apps part is still on the phones internal memory...
Click to expand...
Click to collapse
why does the phone run faster with the data stored externaly? or is it because of the partition type?
im not quite sure, I would have figured our internal mem had a faster transfer rate than an sdcard, but Im on a class 2 and still getting better results... so it cant be a faster transfer rate...
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Just so everyone Knows, the Format via the update script don't work, still trying to find the correct command for it....
But, in clockworkmod, just format the system / data / cache partition's before flashing.
designerfx said:
@freedom: put simply, EXT formats run way faster than Fat32, which is what the rest of the storage is.
wiki: EXT3 (common format) and ext4 (latest)
edit: better explanation here
However, I'd most love to see either one of the internal storage (app storage or the other internal) finding a way to be put into EXT3, as that would probably run better than any sdcard.
Click to expand...
Click to collapse
Er, the internal storage is "rfs", samsung's proprietary fs. (And the read/write speed of fat32 tends to be a little faster than ext2, and TONS faster than ext3/4 - journals slow it down in exchange for stability after crashes)
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Disconn3ct said:
The increase in speed is just that - faster underlying hardware. The onboard "sd card" (same "disk" that /data is partitioned out of) is heartbreakingly slow.
Click to expand...
Click to collapse
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
FastKatt said:
Is there an app to test thr transfer speed on the phone? I ask because I have moved my data/dalvik to ext3 on a class 6 sd card. When I benchmark reads from Linux the speed and seek time between internal and my sd are not that great yet the actual performance of the phone is as different as night and day.
I wonder if this is more an issue with the rfs implementation than a hardware speed issue. My other thought is that maybe the benefit comes from having a separate I/O lane for loading data/dalvik. Not sure the hardware actually supports multiple/parallel I/O but it's a theory.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I'll see what I can do to test it out this afternoon. (If you want to jump the gun, what I'm figuring is finding a static-linked arm version of bonnie++ or similar. Booting recovery, mount data or sdcard - not both - and test. Reboot recovery, test the other one. Maybe test dbdata and external sd as well, but the interesting numbers will be the first two - onboard-with-rfs and onboard-with-vfat..)
ivanmmj said:
How did you de-odex the the core.jar? I've unodexed the whole thing myself as well, as well as optimize the heck out of every jpeg, png and gif inside the apks (excluding 9.png's of course) but I'm having an issue deodexing core.jar. Did you just replace it with the one from the deodex'd SGS ROM?
Click to expand...
Click to collapse
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
anomalous3 said:
Honestly, used the ROM kitchen for most of it; it uses a brute-force approach to sort out dependencies. Only one I had to do manually was TouchWizCalendar.apk (because it needed both twframework.jar and com.google.android.maps.jar). I'll work on getting the update script working during work later today.
Click to expand...
Click to collapse
Which ROM kitchen? I used my own script. Does the ROM boot up and run doing it that way? Should be interesting to play with.
Hmm, got the update script working almost perfect, but now it causes crashes. Seems to be missing dbus.conf.
OP updated - it works.
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
theMAGNUM said:
I did something very noobish.
I formatted the cache, system and data and forgot to throw the update.zip file onto the internal sd card prior to doing this. I can get into the stock recovery but as far as rebooting the phone to put the update on the internal storage I can't do that. I am able to take out the 2g memory (avatar) and load the update.zip on there but, of course, the stock recovery won't recognize that.
Is there a way to put the update.zip onto the internal memory in the position that I am in? Is there anything I can do?
I think I just made a HUGE no-no.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
ArbitrageMan said:
Have you tried connecting your phone to your computer while at the recovery, and see if you can access it via ADB?
Click to expand...
Click to collapse
No adb shell doesn't find my device
What are the diference between super froyo and cyanogen and the rest of the android? I'm a noob and would like to install one of this to my kaiser.
Thanks
The "builds" you're asking about are just different versions of the same build.
The 29-8-11 build is version 2.2.2 Froyo, Super Froyo (IIRC) is build 2.2.1, and Cyanogenmods are just that, "mods" to an originally stock build, wether it be Froyo, Gingerbread, Eclair, etc.
I honestly can't say I hate or dislike any build or modded version, as they all have their benefits. The one great thing about Android is the ability to "make it your own" through customization, where-as iOS (iPhone) pretty much locks you into a certain form and functionality, which the benefit is stability.
My suggestion... grab the 29-8-11 build on sourceforge and build a kernel with 3-4mb above the total install size of 87mb, give yourself a 15-20mb cache file and install it. Customization comes with time, trial and error, and some effort, but you will be happy with the results.
PoXFreak said:
The "builds" you're asking about are just different versions of the same build.
The 29-8-11 build is version 2.2.2 Froyo, Super Froyo (IIRC) is build 2.2.1, and Cyanogenmods are just that, "mods" to an originally stock build, wether it be Froyo, Gingerbread, Eclair, etc.
I honestly can't say I hate or dislike any build or modded version, as they all have their benefits. The one great thing about Android is the ability to "make it your own" through customization, where-as iOS (iPhone) pretty much locks you into a certain form and functionality, which the benefit is stability.
My suggestion... grab the 29-8-11 build on sourceforge and build a kernel with 3-4mb above the total install size of 87mb, give yourself a 15-20mb cache file and install it. Customization comes with time, trial and error, and some effort, but you will be happy with the results.
Click to expand...
Click to collapse
Can you give me the sourceforge link.
I follow this :http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret
I partition using the atools but nothing happen.Receive an error message someting like ext2 ext3 and something missing.Get an error using the above.Maybe it's my bad.
This is the latest error
did you keep the D-Pad pressed ?
That is nothing to do with the D-pad, that is a fault of not installing the system to NAND, something I'm unfamiliar with as I never used or even liked HaReT.
It appears as if you're installing to SD, but the card is not formatted correctly with the 3 (maybe 4 now) partitions needed, one for system, another for data, and the rest for your use.
It should be easy peasy to install to NAND as ATools is really optimized for NAND installations now.
Now I made ext 2 & 3 to my sd card. 1st attempt took 6hrs and still installing files and now trying 2nd attempt.
I use atools and choose haret.once Linux running I choose ext 2 . I follow everything but android doesn't seems to run. Now under file folder there's only ext2 appear ext3 is missing . Have been trying to install few times but nothing happens. My card is 16gb class4.
Can I have the link for the latest froyo dated. 29.8.11.
First off, forget about keeping Windows Mobile and go straight to Android. I never liked running from a SD card.
Here's the link..
http://sourceforge.net/projects/androidhtc/files/2011-08-29-froyo/
Select the correct build for your Country (eu, us or all), preferrably an "odexed" version, download it and copy it to your FAT32 formatted SD card in a folder labled "andboot" without the quotes.
If you check around, I have a post or 2 with the "KAISIMG.NBH" file attached. I always build a new kernel for any new installs as I like to make modifications depending on build size. The one I posted is for this build with a meager 500MHz overclock, 15mb for cache and around 92mb for data with an EXT4 FS.
If you use the 29-8 build, there is no need to update anything as the update modules are included.
How many partition do i need and how many mb do i need on each partition.I'm using 16 gb.
update: I make 1 fat32 and 3 ext2 with 200mb each using gparted.
where does the downloaded or installed apps goes to.Is it on the fat32 or the ext. what's the difference ext2, ext3,ext4.Can I reformat the sd card once my device is androided to add more mb to the ext. If my ext. not enough to install apps (if the apps need to be install to ext. not fat32)sorry for so many question.
Do I need 'bse'( *img -> Virtual disk on sdcard (you need to create it, you can create it with bse) to create virtual disk.?
First off, you're speaking in HaReT terms, a completely different language for me.
I only know how to install /system and /data to NAND, NOT an SD card. No 3 separate partitions on my SD, only 1 formatted to FAT32.
Again, you're running Android "through" Windows by clicking an .exe file in file explorer, not the way I'm running it, which just involves pressing the power button, so you are, in fact, speaking a different language.
Build a kernel with ATools for NAND, not HaReT, and leave everything alone when presented with where to install. /system goes on NAND, /data goes on NAND.
That is my recommendation because I'm all about speed, and a class 6 SD couldn't provide that. Think of NAND as class 10...
I follow this for Nand : http://sourceforge.net/apps/trac/an... pls guide me on how to install through Nand.
Make sure you are using a FAT32 formatted SD card when attempting a kernel update. If you are sure it is formatted correctly, try another. I have 5 SD cards here, 2 of which won't work for kernel update, regardless of format.
If all else fails, look around for the RUU installer for the Kaiser.
Am i getting this right? i'm installing it to my device from yesterday night.
Edit:How long does it going to take 1 day? 1 week? now the number is [43617.514121]android_usb gadget:full speed config #1:android
I connected it on my pc and change to power supply.Is this normal?
Very simply, keep your phone away from any computers!
The only problem I see is the USB is connecting and disconnecting.
DO NOT keep the phone connected to the computer.
If you have followed all the instructions for a NAND install, this conversation would not take place... its THAT simple.
Reformat your SD card, out the KAISIMG.NBH directly on the SD, not inside any folders. Once thats done, make a new folder on the SD called "andboot" and place the androidinstall.tar file inside the new folder. If you're using a rom other than Scoot's or the SourceForge, you'll need an update for the cache.
Install takes less than 2 minutes with even the slowest SD card and first boot usually runs 3-5 minutes. ALL up and running, ready to use in less than 10 minutes.
@PoxFreak, at last i manage to install Android to my Kaiser HaRET way.I think i know what's the problem.I think it's due to my radio. I was using 1.71 and 1.70 it doesn't work. So i install shipped rom to my kaiser and install android .
@Poxfreak,
I manage to install CyanogenMod 6.1.2 Release 6 by using NAND.It took me .... like you say about 5 mins+.I was wondering I have 2 Kingston 4gb microsd card both can be use to install HaRET but only one of them can install NAND.So now I would like to use back my 16gb sd card as an external to install apps.Will I be able to do that instead of using the 4gb? Can I partition it?
Thanks
Hi
What is different betwen (NAND) rom and (EXT3) rom and who is the better and faster rom for xperia x1 :angel:
aLT-bug said:
Hi
What is different betwen (NAND) rom and (EXT3) rom and who is the better and faster rom for xperia x1 :angel:
Click to expand...
Click to collapse
Please ask questions at the question section next time.
NAND ROMs are Android ROMs that replace the Windows Mobile OS. They provide faster speeds and better battery life. The developers really did a great job on them this year. They do, however, contain some bugs like USB mass storage not functioning properly (there's a workaround). The most annoying issue I've experienced is the button and keyboard freeze. But the latest Cyanogenmod build I think has already fixed the problem. But I still have Button Savior just in case.
EXT3 ROMs are the ones that run from the SD card. So you would still be able to run Windows Mobile on your phone. It's kind of a dual boot. You have to make partitions on your SD card. It used to have the least bugs. But it's no longer being developed. So now, the NAND ROMs are actually better for my opinion. I think BrianXP7 is the only one left developing EXT3 ROMs, or at least converting his NAND ROM to an EXT3 ROM. EXT3 ROMs used to be faster than NAND ROMs, but it's only because of the CPU speed. NAND ROMs have more free RAM. The CPU speed of NAND ROMs are also now the same as the EXT3 ROMs. You can also make a swap partition to make your phone a little faster on NAND.
how I can make a swap partition to make faster my phone
aLT-bug said:
how I can make a swap partition to make faster my phone
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1659231
A swap file is also known as a page file or virtual memory. So it's more like the page file on your hard drive. It's not ReadyBoost for Android.
There's also an SD boot bug on this device. So you'll have to format the SD in a special way in order to fix it. But after making the partitions, the fix may be lost. So before partitioning your SD card, apply the fix to your SD card. Then make the partitions. But instead of wiping the SD card, choose the "delete all partitions" option. You then apply all the necessary partitions.
So have you successfully managed to install an android ext3 rom? Because no matter which rom I choose or what I try, it always hangs during the loading with the black screen and all those white lines. It just stays that way forever and then I have to pull the battery and restart my phone. Do you know what I may be doing wrong?
BrianXP7 said:
Did you copy the "Windows/*.csv" files to the root of your microSD card?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes! It you was Brian that told me to do that when I was trying to install your Butter rom. But although, I got further with your rom, compared to other android roms, it wasn't successful because it hanged up. Is it maybe the fault of custom roms or maybe mods in the Windows rom? Because whenever I left overclocked my X1 at boot the haret application never ran. It always failed to start! So what I did was to removed the overclocked values of my X1 but still I can't get Android to boot! I need help!
Hey Brian. I tried to run again android on my device and it still doesn't work. What happened this time is this: I placed all files in the right place and clicked haret. The loader starts, CWM opens and I select install zip package. Then the bar that appears is fully loaded and tells me installation is complete. I then proceed with rebooting go back to custom rom with WM6.1 and start again CWM. But this time, even after waiting for more than 15 minutes it never manages to load into android, it hangs with many white lines on a black screen, although if I press some buttons then some words start appearing but nothing happens. Do I miss something?