So Dzo has a thread going on flashing Android to the NAND.... SWEET!!!!!!!!!
I am going to try it out, but I want input from you all.
there are SO MANY different flavors of Android (1.5 1.6 2.0 cupcake eclair ion) and I would like to try them all for myself, but obviously this isn't realistic, so I want to know what you guys like the best?
So please... Anyone, EVERYONE.... Which build do you like best on the Vogue?!
And if you tell your favorite, please tell us as well what basefiles build, Rootfs and zImage build you use for the Version
Otherwise we must ask that again...
160bpm said:
And if you tell your favorite, please tell us as well what basefiles build, Rootfs and zImage build you use for the Version
Otherwise we must ask that again...
Click to expand...
Click to collapse
Precisely bpm.
Ion 1.5 for its speed and stability.
Using latest basefiles.
I recommend a Donut build based on cyanogens work. He's added alot more features to the aosp making it more stable and including some of the best developments including the updated contacts and phone apps etc.
mssmison said:
I recommend a Donut build based on cyanogens work. He's added alot more features to the aosp making it more stable and including some of the best developments including the updated contacts and phone apps etc.
Click to expand...
Click to collapse
Wanna spoonfeed me your link?
mfpreach said:
Wanna spoonfeed me your link?
Click to expand...
Click to collapse
he means to port one(yourself) from cyanogens work
if you are flashing your phone and ridding yourself of windows, keep in mind that donut 1.6 does not have working GPS yet, so you if that is something you use, you might want to stick with a 1.5 build.
standard ion build is nice and stable.
xrom 1.5.4 build has some nice addons (better browser, customizable launcher and home screen numbers). the new launcher can be just a touch slow, however. this is what I use.
sense UI builds (tattoo, hero types) look sweet, and can run well if tweaked just right, but I hate that sms error, drives me insane. don't know if that annoying problem has been worked out yet.
if you never use GPS, flash zen's droid themed donut 1.6, or plemen's AOSP donut, and just wait until the rootfs/initrd get updated for GPS functionality. but remember that unless you keep your resolution in 320x480 from first boot, you will not always see all market apps.
for me, I won't be using NAND until we get full GPS functionality (which will be a while, if ever); I can't live without my turn-by-turn tts gps. i don't use bluetooth much, so I would not miss that. on the upside, NAND flashing gives you a r/w system, and usb mass storage, so you must weigh the pros and cons of what you use most. it'll be while before i'm flashing because i'm married to full GPS, and I don't see that being implemented on android on the vogue for a while as it is not the priority right now.
perfect solution: donut 1.6 with full gps, with market problem fixed for 240x320, then I'm flashing my NAND in a heartbeat and donating again ($50 this time) to dzo and the gang. and you can hold me to that.
hmmm something to think about I suppose....
One of the main reasons I love Android is because there is so much free software that utilizes the GPS.... I wonder just how long it will be until someone finds the missing link...
I personally like donut (1.6). I'm not a fan of the Hero UI or the Tatoo UI, I just like standard android.
I'm using all of the latest basefiles except the zimage, which I compiled from the git repository for the vogue kernel. The rootfs is the one found on dzo's website (it's the one required to even flash to NAND).
tatnai said:
if you are flashing your phone and ridding yourself of windows, keep in mind that donut 1.6 does not have working GPS yet, so you if that is something you use, you might want to stick with a 1.5 build.
standard ion build is nice and stable.
xrom 1.5.4 build has some nice addons (better browser, customizable launcher and home screen numbers). the new launcher can be just a touch slow, however. this is what I use.
sense UI builds (tattoo, hero types) look sweet, and can run well if tweaked just right, but I hate that sms error, drives me insane. don't know if that annoying problem has been worked out yet.
if you never use GPS, flash zen's droid themed donut 1.6, or plemen's AOSP donut, and just wait until the rootfs/initrd get updated for GPS functionality. but remember that unless you keep your resolution in 320x480 from first boot, you will not always see all market apps.
for me, I won't be using NAND until we get full GPS functionality (which will be a while, if ever); I can't live without my turn-by-turn tts gps. i don't use bluetooth much, so I would not miss that. on the upside, NAND flashing gives you a r/w system, and usb mass storage, so you must weigh the pros and cons of what you use most. it'll be while before i'm flashing because i'm married to full GPS, and I don't see that being implemented on android on the vogue for a while as it is not the priority right now.
perfect solution: donut 1.6 with full gps, with market problem fixed for 240x320, then I'm flashing my NAND in a heartbeat and donating again ($50 this time) to dzo and the gang. and you can hold me to that.
Click to expand...
Click to collapse
same here, bluetooth is a must for me though I don't speak on the phone without it, holding the phone is so cumbersome!
I like Zen's Droid-ION followed by Msmisson/Kb7sqi's Roger's.
Zen-droid-Donut-ION has been very smooth and I get to use it with 320 x 240 res. + with Donut, app variety in market is more.
tatnai said:
if you never use GPS, flash zen's droid themed donut 1.6, or plemen's AOSP donut, and just wait until the rootfs/initrd get updated for GPS functionality. but remember that unless you keep your resolution in 320x480 from first boot, you will not always see all market apps.
Click to expand...
Click to collapse
You mean resolution in defualt.txt right? Do you have to do it before creating a google account or just as long as your signing in the initial time when setting up your device? I've changed my default.txt but even after the change when I run Haret for the first time the resolution looks like normal qvga. Maybe I am not doing something right here's my 320 x 480 default.txt prior to signing into my google account the initial time...
I'm running Windows Mobile / Haret boot /11-16-09 Basefiles
sqsh:
http://www.mediafire.com/file/gjt2wo...stem_v233.sqsh
Rootfs (polyrythmic):
http://forum.xda-developers.com/show...&postcount=212
your default.txt is correct for 320x480. your google account does not matter, what matters is that the first time you make a data.img with a donut build (1.6) that you boot it with resolution of 320x480 (the lcd.density actually doesn't matter) and sign in to google services and use the market at that resolution. then if you change the resolution, it will actually still work for you for a while, but after a couple days or so the market will become limited again to apps designated OK for donut with lower resolutions. i don't know of a way to go back and fix it without creating a new data.img; if you want to run in a resolution other than 320x480, you could just archive your old data image each time, boot up a new on in 320x480 and log into the market, then shut down and boot back with your old resolution and data.img and you would be good again for a little while. hopefully soon enough all the apps (or all the ones that matter) will begin to show up at 240x320, but who knows how long that will take.
So will I notice a physical difference in resolution when android boots up on my vogue to reflect the 320 x 480 resolution? Larger icons, screen cut-off, etc.? Just wanting some evidence that the market thinks I'm not QVGA.
Reddog80p said:
So will I notice a physical difference in resolution when android boots up on my vogue to reflect the 320 x 480 resolution? Larger icons, screen cut-off, etc.? Just wanting some evidence that the market thinks I'm not QVGA.
Click to expand...
Click to collapse
depends what you set your lcd.density to - and lcd density of 110-120 on 240x320 will look similar to 320x480 at a density of 160. however, you should notice a slight squashed appearance at 320x480 because the aspect ratio is off, and the sreen appears just a touch fuzzy. when you boot into 320x428 or 240x320 for the first time, you will note a marked difference in the sharpness of the screen for that reason. like taking oily glasses off for the first time. you are booting from haret (not from nand) right? because the default.txt is not used when you boot from the nand.
The biggest thing I noticed with density 160 (besides the obvious blurring) is that the touchscreen is flakier (rounding / touch location -> pixel mapping issues? I haven't looked into how it's implemented yet...) when doing precise motions - for example, it's almost completely impossible to drag widgets in a Sense UI build or a stock build running with density 160 whereas a build running at native resolution is fine.
And re: the thread, Zen's Donut Droid-ION is my favorite build by far - fast, dead stable, reliable, and not too flashy.
He said over at http://forum.xda-developers.com/showpost.php?p=5137740&postcount=105 that he's going to have a working Eclair with radio and GPS hopefully today - I'm really excited for that.
Bump.
Any others out there?!!!
been running plemen's Donut AOSP, I must say it is even faster than dzo's droid donut. my new fav.
tatnai said:
been running plemen's Donut AOSP, I must say it is even faster than dzo's droid donut. my new fav.
Click to expand...
Click to collapse
Yes, do try Plemen's Donut AOSP. It is very fast and responsive. Most users switch away though due to screen lock issues and stuff. There is a fix and it is to restart your phone a few times and log into google your 2nd. Hope that helps
Related
All my future builds will be on the google code page http://code.google.com/p/vogue-android/ to make it easy for everyone to find all the files they need to run android.
**RESERVED**
**Reserved**
EDIT: Removed
cant get data sync to open. do i need dzos data.img to get to sync contacts and email?
yes, for all google apps to work you need to have already setup your google account in DZO's 1.1 build.
finally got dzo's build working and now using that data.img. quick question, does the camera work cause it didnt come on for me. not a big deal just wanted to know what all worked. nice and smooth build.
bangout said:
finally got dzo's build working and now using that data.img. quick question, does the camera work cause it didnt come on for me. not a big deal just wanted to know what all worked. nice and smooth build.
Click to expand...
Click to collapse
no, I didn't bring that over yet. I honestly never use the camera on my phone.
Why does my HaRET lock up at 100%? 1.1 booted just fine for me. When I try to load this build it locks up and has to be soft reset after that.
I am running NFSFAN's 6.5v10 WinMo ROM.
EDIT: Fixed, I had to re-extract and recopy the files over. Something must have corrupted randomly some where for me.
I am also using NFSFAN's 6.5 v10 ROM, and after running this Android build once, my WM ROM got royally corrupted... I'm going to hard reset and pray for the best... :\
I'm not trying to be a troll, here. But if anyone could help identify what went wrong, I'd greatly appreciate it.
I extracted all the files (except for data.img) and fired up Android. Waited a few minutes (like the thread said I would have to) and then I waited a minute or two before turning off the phone (through Android). Restarted the phone, and my Titanium home screem doesn't work, and neither does the Start Menu. And right when it starts I get "Cannot Start Voice Command. Reinstall and try again."
my wife had the same problems on her white vogue, I don't really know what it is... Pretty much means android is out of the question for you until we figure it out.
Thanks for this. I am finding it really hard to read the screen though. I did allign it. Is there a cleartype thing for android? non cupcake build looks real nice, but cupcake seems to have issues with readability.
Again, thanks for this, can't wait to see the final results.
After a Hard Reset, everything worked fine. I didn't really lose anything, since I installed V10 this morning.
I like the performance on the ROM. Feels lighter and faster. The only thing I don't like much is the GUI customization, more specifically the inability to switch back to the default theme. The loading intro screen is DEAD SEXY, though.
The lack of camera kind of sucks, but we all know how hit-and-miss camera has been on Vogue Android development, so it's understandable.
strange, im running nfsfans v10 rom and ran this as well and wm wasnt affected whatsoever.
harminoff said:
Thanks for this. I am finding it really hard to read the screen though. I did allign it. Is there a cleartype thing for android? non cupcake build looks real nice, but cupcake seems to have issues with readability.
Again, thanks for this, can't wait to see the final results.
Click to expand...
Click to collapse
use the different initrd that vilord posted in the other thread. There's one that has bigger type/icons etc
http://forum.xda-developers.com/showpost.php?p=3914750&postcount=3744.
robobeau said:
After a Hard Reset, everything worked fine. I didn't really lose anything, since I installed V10 this morning.
I like the performance on the ROM. Feels lighter and faster. The only thing I don't like much is the GUI customization, more specifically the inability to switch back to the default theme. The loading intro screen is DEAD SEXY, though.
The lack of camera kind of sucks, but we all know how hit-and-miss camera has been on Vogue Android development, so it's understandable.
Click to expand...
Click to collapse
I built this version as I was tired of the same old android look. I may post a default theme later, after band of brothers is done
commandant83 said:
strange, im running nfsfans v10 rom and ran this as well and wm wasnt affected whatsoever.
Click to expand...
Click to collapse
It's a real hit and miss thing. Some phones are good and some aren't. I wish I could say for sure what it is.
mssmison said:
use the different initrd that vilord posted in the other thread. There's one that has bigger type/icons etc
http://forum.xda-developers.com/showpost.php?p=3914750&postcount=3744.
Click to expand...
Click to collapse
Thanks, looks a bit better.
I'm also getting lines across my screen, very small and kind of flashing. Is that a cupcake issue, or something on my part?
could be maybe related to panel type? I'm not sure... try setting panel type to 0 in default.txt
Thanks mssmison, is working great for me with DZO's 128mb data.img.
Would love to see a standard themed version though.
Will let you know how battery life goes. Had wake up issues with original power options so changed them to match yours.
Cheers
Well since we have a thread for everything else and no place for general discussion. Here it is.
zenulator said:
Well since we have a thread for everything else and no place for general discussion. Here it is.
Click to expand...
Click to collapse
i don't know about anyone els but the one and only problem i have with hero is incoming call response time, zenulator and others have worked hard on speed. and right now i'm using the latest vogue hero.sqfs bundle. and it is pretty fast. i just need to be able to receive calls a little faster instead of one ring before vm.
i'm asking anyone that codes or knows how to code to look into what can be done to improve this.
i know that having phone not vibrate on calls, using ogg ringtones help a little, the renicer script aswell. but is there anything else we can do?
jamezelle said:
i don't know about anyone els but the one and only problem i have with hero is incoming call response time, zenulator and others have worked hard on speed. and right now i'm using the latest vogue hero.sqfs bundle. and it is pretty fast. i just need to be able to receive calls a little faster instead of one ring before vm.
i'm asking anyone that codes or knows how to code to look into what can be done to improve this.
i know that having phone not vibrate on calls, using ogg ringtones help a little, the renicer script aswell. but is there anything else we can do?
Click to expand...
Click to collapse
if someone ports the htc ril, this might fix the problem.
tatnai said:
if someone ports the htc ril, this might fix the problem.
Click to expand...
Click to collapse
Speaking of that, whats this all about on the Vogue-Hero google page? I've downloaded it to keep a copy on hand but what improvements will we see with that file?
i was using the latest hero build with the basefiles from 9/08 and everything was pretty smooth. then i updated this morning to basefiles from 9/15 and everything is slower. takes longer to switch pages and respond to anything i do.
tatnai said:
if someone ports the htc ril, this might fix the problem.
Click to expand...
Click to collapse
The HTC RIL is closed source. Its not a question of porting.
Here is my problem. I keep trying the latest donuts and sqsh based systems and even with fresh data files, I always get the dreaded Blank home screen with no icons. It takes around a minute to repaint them. The version I keep going back to is the cupcake-based hero themed system. It is distinguished by only having one arrow on the left side of the app drawer handle. It works great and hardly ever does the slow down thing. I just hope that when we get BT all sorted out that either the image will work with this system or the sqsh based systems are up to the same level of performance that this one is.
Cheers.
katmandu421 said:
Here is my problem. I keep trying the latest donuts and sqsh based systems and even with fresh data files, I always get the dreaded Blank home screen with no icons. It takes around a minute to repaint them. The version I keep going back to is the cupcake-based hero themed system. It is distinguished by only having one arrow on the left side of the app drawer handle. It works great and hardly ever does the slow down thing. I just hope that when we get BT all sorted out that either the image will work with this system or the sqsh based systems are up to the same level of performance that this one is.
Cheers.
Click to expand...
Click to collapse
I don't have any of these problems with my builds so you might be missing a step or using the wrong files. Granted the xrom and cyanogen builds at vogue-hero are experimental/beta quality and hence why they stay there and don't go to the main vogue-android page. The latest xrom is using cupcake/donut built from the android master branch and is as fast as any build out there with the right setup and you can't use it with an existing data.img because it has a different code base. And sqsh has nothing to do with the level of performance of any build infact it should be faster than cramfs. It's the code that the system image is based off of and what extra apps and libraries and frameworks are included that determines how fast it's going to be.
Zen since you seem to be up and responding I have a quick question that I am not looking for too in depth of a response, just a brief overview...
What exactly is the user.conf responsible for? If I am running just the basic ION version is there any reason to keep the rogers or hero based files? Are they ever called upon when running the regular ION build?
Thank you!
BJNK said:
Zen since you seem to be up and responding I have a quick question that I am not looking for too in depth of a response, just a brief overview...
What exactly is the user.conf responsible for? If I am running just the basic ION version is there any reason to keep the rogers or hero based files? Are they ever called upon when running the regular ION build?
Thank you!
Click to expand...
Click to collapse
you don't need them if your running ion. the user.conf files are just for people to tweak their own settings for each build. so you have the ability to turn compcache/swap on/off things like that. ion doesn't really need it but it does help it out it you run a lot of programs and widgets.
I've got a vogue and a diamond on sprint that I switch back and fourth between pretty often.
I thought maybe I could get a vzw htc vogue off of ebay, and get it working on my sprint plan, and put android on it.
If I did that, would GPS be crippled on it in android?
The main reason I wanted to do it was I like the white case and the vzw screens are all nice, I have a sprint vogue with a bad screen.
I'm excited that Zen said he was repackaging the nkhero release as it is essentially the latest-stable Ion build. The experimental builds are nice and essential to advancing development but alot of users are looking for everyday stable usage (and the added Hero theme is always sweet eye-candy)!
pmos69 said:
The HTC RIL is closed source. Its not a question of porting.
Click to expand...
Click to collapse
so I guess the question is, can it be cracked/hacked, or not possible?
i recommend everyone try out the opera mini beta 5 with android. Make sure you have Java installed on your build. I use the latest hero-vogue build. go to m.opera.com/next on your android browser and click download to pc. download the jar. it will run with java and is awesome. it runs smoother and has more eye candy than any browser i ever tried. and i really like the keyboard that comes with it!
incubus26jc said:
i recommend everyone try out the opera mini beta 5 with android. Make sure you have Java installed on your build. I use the latest hero-vogue build. go to m.opera.com/next on your android browser and click download to pc. download the jar. it will run with java and is awesome. it runs smoother and has more eye candy than any browser i ever tried. and i really like the keyboard that comes with it!
Click to expand...
Click to collapse
Nice tip. This thing is wicked fast. I just tried 4.x yesterday but this is way better for touch screens!
zenulator said:
I don't have any of these problems with my builds so you might be missing a step or using the wrong files. Granted the xrom and cyanogen builds at vogue-hero are experimental/beta quality and hence why they stay there and don't go to the main vogue-android page. The latest xrom is using cupcake/donut built from the android master branch and is as fast as any build out there with the right setup and you can't use it with an existing data.img because it has a different code base. And sqsh has nothing to do with the level of performance of any build infact it should be faster than cramfs. It's the code that the system image is based off of and what extra apps and libraries and frameworks are included that determines how fast it's going to be.
Click to expand...
Click to collapse
OK, this is the first non-mssmison build I've tried in a while. I'm trying xrom 1.5. New data, and fresh files all around. Seems to be pretty good, but still the browser chokes a bit more than the non-sqsh build. Is there a way to limit app processes anymore? I looked for dev tools but it is not included.
hey zen, is it normal for me to be getting these fsck000.REC fsk0001.REC ect..
files on my storage card? if not, do you know what they are? the number just keeps goin up after every reboot and just keeps adding files.
Also, has anyone got a driver to work with Vista?
katmandu421 said:
OK, this is the first non-mssmison build I've tried in a while. I'm trying xrom 1.5. New data, and fresh files all around. Seems to be pretty good, but still the browser chokes a bit more than the non-sqsh build. Is there a way to limit app processes anymore? I looked for dev tools but it is not included.
Click to expand...
Click to collapse
Squashfs has nothing to do with the browser. If your compairing the1.5 xrom to the 1.4 then the differences are due to different browser builds aand the fact that the 1.5 build has some donut parts that 1.4 didn't have.
incubus26jc said:
hey zen, is it normal for me to be getting these fsck000.REC fsk0001.REC ect..
files on my storage card? if not, do you know what they are? the number just keeps goin up after every reboot and just keeps adding files.
Also, has anyone got a driver to work with Vista?
Click to expand...
Click to collapse
You can delete them.
Probably something to do with the basefiles, but I haven't tracked the cause yet.
They're the result of the automatic filesystem check on the sdcard fat partition on boot.
pmos69 said:
You can delete them.
Probably something to do with the basefiles, but I haven't tracked the cause yet.
They're the result of the automatic filesystem check on the sdcard fat partition on boot.
Click to expand...
Click to collapse
anyway patiently awaiting tattoo. it should be out today in some way or another. i just want to get a hold of the pure dump before it gets messed with.
Hi everyone. I am currently running plemen’s Eclair themed Donut AOSP build (Updated 12/22). As far as I know everything works (except perhaps for Bluetooth – haven’t tried yet) including the GPS (which is critical for me). I am *very* impressed with this firmware and how "native" it feels on the Vogue. Almost like it was meant for it except for the unusual key bindings but that’s another story and not specific to plemen’s build. (Click here for details on how I wish the keys could be setup).
However I am wondering just how much of this is “donut” and now much of it is “eclair theme” and how much of it is popular 3rd party apps? I know everyone wants something different from these chefs and I apologize for even asking. Overall I am very impressed with plemen’s build.
It is also possible that I am mistaken in thinking there is a “pure base” of sorts as there is with Windows Mobile. I realize that in Android all apps are just as “native” as the next. But is there any way I can remove the eclair theme? Or would I even want to do so?
How could I achieve a “pure” Donut build with just the Google apps (Gmail, Maps, Gtalk, etc) built in? Is doing some even desirable? Or would I immediately want to go back to what I have?
Best regards,
The Fish
http://forum.xda-developers.com/showpost.php?p=4427917&postcount=1
you can try that build.
I also have a 32mb system.sqsh thats a stripped down donut build.
zenulator said:
http://forum.xda-developers.com/showpost.php?p=4427917&postcount=1
you can try that build.
I also have a 32mb system.sqsh thats a stripped down donut build.
Click to expand...
Click to collapse
Thanks zenulator, that's great! I will try it later this weekend. How could I maybe get the 32mb version?
What are the "eclair dialer buttons"? The buttons on my build are square in the dialer but are "round" (for lack of a better word) when I pull the keypad up during a call (to enter my VM password for example). I don't like the inconsistency but I live with it cause beggars can't be choosers
Also, the little arrow "thing-a-ma-jig" on the bottom of the screen that pulls up the applications... I like the one in your build better (see "home.jpg") then what I think is probably the "eclair" look (see "home2.jpg"). Also, in my current build it reverts to this when in a call and I am a diehard for consistency
I noticed in your screen shots the little microphone isn't present in then Google search widget. Does that mean that the voice recognition/search feature is not present in your build? Or is this something I just need to turn on?
Thanks again,
The Fish
you can install voice search yourself.
[TMOUS? don't bother reading it.. it's for EU Version with 512mb]
AND THERE IS IT!!!
http://forum.xda-developers.com/showthread.php?t=903002
I've been using for quite a while DHD builds and I really like them.
I've tried quite a lot of NAND builds, but the SD builds still better in terms of stability and it suits most the "daily-use" kinda of build.
[that's my personal opinion.. not relevant. the important bit is below]
On EU HD2 there's 512mb of NAND, not enough to put the whole DHD stock build, unfortunately. Few devs found few work around: either by compress it or put the data.img on the SD card.
IMO both these two solution slows down the entire build, especially in the second where also data corruption is introduced.
So I'm requesting a build where only the necessary is cooked in.
These are apps not really useful imo; therefore they should be removed [including their widget]:
-Adobe reader (install from the market if you need it)
-Amazon MP3
-Barcode Scanner (used only 2-3 times)
-Car Panel (Use software like co-pilot & navigon)
[gmail should be cooked in]
-Google Search (just use the browser)
-HTC likes (completely useless)
-Latitude
-G Maps (again, use co-pilot or navigon instead)
-News
-News and Weather (completely useless)
-Quickoffice (old version, install from market if you need it)
-Soundhound (???)
-Twitter (I use another app)
-Facebook (install from market if you need it)
-Teeter (???)
-Stocks
[g talk should be cooked in]
-ebook stuff (doesn't work yet lol)
-Youtube (as the browser has flash, why would you use it? )
-Transfer data
Stuff within the build:
- Skins (only one [I would like Slate]. download the others from HTC hub)
- Only one light wallpaper
- No notification sound; download what you like from htc hub
- No live wallpaper, no even to show to your iPhone-fan friend.
- No boot animation
Program I think should be cooked as they are essential
-SU
SetCPU http://forum.xda-developers.com/showthread.php?t=505419
support the devs
[Any other suggestion will be appreciated.]
Again, this is just me. But I think quite a few people shares my idea.
As a really light build, anyone could enjoy it personalizing as they want.
Also it should be set "SD card" as the default location for installing apps
I don't know if this is gonna work in any way. I hope it will though.
However I do remember that the space left in WinMo with cooked roms wasn't that much.. like 140mb (correct me if I'm wrong.. such a long time I don't use it).
So I'm aiming to have around 100 - 150mb of space. I think it's enough, considering that a large amount of apps will go to the SD.
We can get more than 150mb apparently. AWESOME!!!
Now I'm kindly ask if any dev around could answer my request.
2 people are working on it atm; each is making their own version
Want to join in?
Thank you
EDIT:
Few suggest that the data could be saved on a ext4 partition on the SD card.
What is the difference between data.img and a ext4 partition? Advantages | Disadvantages
How could you create it under Win7 x64?
512mb is enough for system files. good.
no more ext4
EDIT2:
All non european languages could be removed to gain further space I.e. Chinese, Japanese.
Also the related keyboard's dictionaries.
How about only English?
As a TMOUS HD2 user, I'd like to see a Desire HD/Z build that is 100% stock theme with no squashing or stripping of apps. I would like my phone to look and work like a Desire HD would, right after taking it out of the box(minus the obvious things... 720P recording, 8mp camera... etc...).
Tried to make this myself based on m-deejay's Desire HD revolution 2.1 ROM but failed epically. Would love to see one of our highly esteemed Android chef's make this happen.
dharvey4651 said:
As a TMOUS HD2 user, I'd like to see a Desire HD/Z build that is 100% stock theme with no squashing or stripping of apps. I would like my phone to look and work like a Desire HD would, right after taking it out of the box(minus the obvious things... 720P recording, 8mp camera... etc...).
Tried to make this myself based on m-deejay's Desire HD revolution 2.1 ROM but failed epically. Would love to see one of our highly esteemed Android chef's make this happen.
Click to expand...
Click to collapse
why would you like to have a stock DHD with all the boatware that only slows down Android?
hrockh said:
I've been using for quite a while DHD builds and I really like them.
I've tried quite a lot of NAND builds, but the SD builds still better in terms of stability and it suits most the "daily-use" kinda of build.
On EU HD2 there's 512mb of nand, not enough to put the whole DHD stock build, unfortunately. Few devs found few work around: either by compress it or put the data.img on the SD card.
IMO both these two solution slows down the entire build, especially in the second where also data corruption is introduced.
So I'm requesting a build where only the necessary is cooked in.
These are apps not really useful imo; therefore they should be removed [including their widget]:
-Adobe reader (install from the market if you need it)
-Amazon MP3
-Barcode Scanner (used only 2-3 times)
-Car Panel (Use software like co-pilot & navigon)
-GMail (don't use gmail. .apk easily findable in google)
-Google Search (just use the browser)
-HTC likes (completely useless)
-Latitude
-G Maps (again, use co-pilot or navigon instead)
-News
-News and Weather (completely useless)
-Quickoffice (old version, install from market if you need it)
-Soundhound (???)
-Twitter (I use another app)
-Facebook (install from market if you need it)
-Teeter (???)
-Stocks
-G talk (i use skype, again install from market if you need it)
-ebook stuff (doesn't work yet lol)
-Youtube (as the browser has flash, why would you use it? )
-Transfer data
Stuff within the build:
-Skins (only one [I would like Slate]. download the others from HTC hub)
-only one light wallpaper
-No notification sound; download what you like from htc hub
Program I think should be cooked as they are essential
-SetCPU
-SU
-XDA
[Any other suggestion will be appreciated.]
Again, this is just me. But I think quite a few people shares my idea.
As a really light build, anyone could enjoy it personalizing as they want.
Also it should be set "SD card" as the default location for installing apps
I don't know if this is gonna work in any way. I hope it will though.
However I do remember that the space left in WinMo with cooked roms wasn't that much.. like 140mb (correct me if I'm wrong.. such a long time I don't use it).
So I'm aiming to have around 100 - 150mb of space. I think it's enough, considering that a large amount of apps will go to the SD.
Now I'm kindly ask if any dev around could answer my request.
Thank you
Click to expand...
Click to collapse
I should simply say: cook the apps, which are not downloadable.
By the way I have a european HD2, have 81 apps (a lot moved to SD) and still 65 MB internernal storage free, and everything working fine.
I need a kitchen for all the various ROMs the geniuses at xda have created with detailed instructions on how to build one's own image as it was very eas, for me at least, with Windows Mobile but with Linux, my skills are virtually non-existant. Anyone?
+ 1 for this, something like a superlight-stock ROM would be much appreciated
hrockh said:
why would you like to have a stock DHD with all the boatware that only slows down Android?
Click to expand...
Click to collapse
I prefer to be given the choice to remove apps I don't want rather than have them removed ahead of time and not being given the choice. "System App Remover" from Market is the app I use for this.
Ηey corha which nand rom do u use? the 1st one from cottula or another one ?
Have you tried?
Have you tried:
[31 DEC] gauner1986's HD-FI 0.3 (Desire HD based) [KERNEL = my own ] ?
Highly Recommended ROM!
Almost as you asking for....
Enjoy!
come on guys,don,t leave me out of this conversation.i want this special rom also
dharvey4651 said:
As a TMOUS HD2 user, I'd like to see a Desire HD/Z build that is 100% stock theme with no squashing or stripping of apps. I would like my phone to look and work like a Desire HD would, right after taking it out of the box(minus the obvious things... 720P recording, 8mp camera... etc...).
Tried to make this myself based on m-deejay's Desire HD revolution 2.1 ROM but failed epically. Would love to see one of our highly esteemed Android chef's make this happen.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=898708
Just use titanium backup in chuck norris mode to remove all apps and stuff but its still too slow i love dhd sense but cm roms are runnig very quick and are very customizable and with fancy weather widget and launcher pro it looks also good, give a try
Sent from my FutureShocks HD2 MIUI using XDA App
I actually want the opposite a full working DHD Rom with everything except outsider apps like soundhound, I just bought the hd2 to give it to my wife as an alternative to DHD
there is already a solution for this, the classic desire Rom RCmixHD comes in two solutions both very good
first is splitting the Rom in two, main stuff on internal and rest like apps are installed into a2sd+ ext
second solution is data2sd running on ext partition this gives a nice boost to io speed with less risks of delete or corruption
I'm actually surprised no one copied this yet by the way gauner v0.2 runs pretty good compared to v0.3 where the extra squashing has broke it, however even v0.2 has some missing stuff like voice commands in the HTC keyboard
CorHaa said:
I should simply say: cook the apps, which are not downloadable.
By the way I have a european HD2, have 81 apps (a lot moved to SD) and still 65 MB internernal storage free, and everything working fine.
Click to expand...
Click to collapse
which build are you using atm?
dharvey4651 said:
I prefer to be given the choice to remove apps I don't want rather than have them removed ahead of time and not being given the choice. "System App Remover" from Market is the app I use for this.
Click to expand...
Click to collapse
fair enough.. personally still can't get your point.
try this out; still developing
http://forum.xda-developers.com/showthread.php?t=894965
TheAgent1982 said:
Have you tried:
[31 DEC] gauner1986's HD-FI 0.3 (Desire HD based) [KERNEL = my own ] ?
Highly Recommended ROM!
Almost as you asking for....
Enjoy!
Click to expand...
Click to collapse
it is compressed I'm trying to avoid that
but thanks
MDJ's Revolution HD NAND was released on the 2nd of Jan and has a version where all the unrequired crap is taken out to free up storage. I ran it for a few days with no issues.
I'm sure HD builds will pop up over the next few days using ext partition on SD for data storage.
imilka said:
http://forum.xda-developers.com/showthread.php?t=898708
Click to expand...
Click to collapse
This is the 100% original build with no apps removed right? As it would be out of the box if it were a Desire Z?
I don't want a ROM that has had anything removed - I want it original.
Your thread doesn't say that anything has been removed but I want to clarify this before I wipe my phone again and install something different.
It's not possible. There isn't enough space available on the Euro HD2 to store everything in NAND.
You'll have to wait until someone released an HD build which installs all of the extras on the EXT partition on SD at first boot. Or use one fo teh builds that comes with a seperate data.img which you have to store on a FAT32 partition on SD.
It's a physical limitation of the hardware.
PS. Epic thread hijack dharvey!
Sentinel196 said:
It's not possible. There isn't enough space available on the Euro HD2 to store everything in NAND.
You'll have to wait until someone released an HD build which installs all of the extras on the EXT partition on SD at first boot. Or use one fo teh builds that comes with a seperate data.img which you have to store on a FAT32 partition on SD.
It's a physical limitation of the hardware.
PS. Epic thread hijack dharvey!
Click to expand...
Click to collapse
the guy you are referring to is a TMOUS. so he should be fine.
he's quite OT.
Post Updated
imilka said:
http://forum.xda-developers.com/showthread.php?t=898708
Click to expand...
Click to collapse
Highly Recommanded ! For daily use! Works flawlessly...
ok i know the Z is 99% same, but it has bigger font size which is really not impressive on 4.3inch like the DHD fonts dpi
plus the keyboard has no arrows
The DHD rom is really smart work from htc (never thought i would say that)
this is Robocik rom from the desire forums http://forum.xda-developers.com/showthread.php?t=789830
There are two versions of the rom, if you want stable and fast version choose Old Fasion version.
The Data2ext version is still new and can be changed and updated couple of times before we get it right, so this version is for those who dont are afraid of the mighty wipe hehe *New
The RCMixHD v0.14 D2EXT uses data2ext script, so the ext partition will be your internal storage, so use a size of your ext partition as big as you are gonna need. I am using EXT2 2GB class4 Sdcard, everything is working super.
Click to expand...
Click to collapse
we will have to wait for builds that use an ext partition, fingers corssed who ever builds it will keep it purely stock like robocik did
I have a few questions about the current state of android builds for the HD2.
I've been running the Cotulla DFT Stock Desire rom for a while with a few tweaks (prj 0.3 kernel, removed some system apps, repartitioned for more /data on NAND). It's been relatively stable but I thought i'd try a Desire HD build as I like some of the newer apps and smaller menu text (it works better on the 4.3" screen).
I tried the imilka RAM Desire HD build. The build has the same WiFi sleep issue (wifi disconnects after phone left in extended sleep) that the DFT Stock build has. It also has a very obscure partition format (with RAM, but system framework on SD), odd slowdowns, and a few other things including the camera FC.
Basically I am looking for a build for the HD2, with the following:
- Suit EU HD2
- Desire HD base
- As stock as possible. No crazy RAM or framework-on-sd stuff. Fine with removed apps (like maps, youtube, etc) and /data on A2SD+
- Odexed. I want performance not fancy graphics
- Good battery life
- Fixed wifi & camera (I dont care what resolution, I just dont want FC on using the share app)
- Prefer Desire keyboard (hate the arrows, take up too much screen space).
Is this wish list too much? I might try skink clean desire but it's not a HD build.
I'm really disappointed that there are so many different android builds for the HD2 yet they all seem to have the same basic problems. I liked the DFT rom as it was well tested and had no extra crud.
HELP!
Well maybe you should ask yourself this first. What major difference is there between a desire hd and desire build in terms of looks/functions? A new music app? A different widget look for messaging and e mail? A different camera interface (Note barely any of the features in the desire hd camera work, which I assume you know)? A camcorder that doesn't sync audio and visual correctly? HTC hub, which isn't even populated with anything of relevance yet. And to top it all off, the desire hd builds are considerably slower than desire builds. I'm just saying here, there's no advantage other than eye candy I guess.
galapogos01 said:
I have a few questions about the current state of android builds for the HD2.
I've been running the Cotulla DFT Stock Desire rom for a while with a few tweaks (prj 0.3 kernel, removed some system apps, repartitioned for more /data on NAND). It's been relatively stable but I thought i'd try a Desire HD build as I like some of the newer apps and smaller menu text (it works better on the 4.3" screen).
I tried the imilka RAM Desire HD build. The build has the same WiFi sleep issue (wifi disconnects after phone left in extended sleep) that the DFT Stock build has. It also has a very obscure partition format (with RAM, but system framework on SD), odd slowdowns, and a few other things including the camera FC.
Basically I am looking for a build for the HD2, with the following:
- Suit EU HD2
- Desire HD base
- As stock as possible. No crazy RAM or framework-on-sd stuff. Fine with removed apps (like maps, youtube, etc) and /data on A2SD+
- Odexed. I want performance not fancy graphics
- Good battery life
- Fixed wifi & camera (I dont care what resolution, I just dont want FC on using the share app)
- Prefer Desire keyboard (hate the arrows, take up too much screen space).
Is this wish list too much? I might try skink clean desire but it's not a HD build.
I'm really disappointed that there are so many different android builds for the HD2 yet they all seem to have the same basic problems. I liked the DFT rom as it was well tested and had no extra crud.
HELP!
Click to expand...
Click to collapse
Try the Typhoon NAND rom, it runs very smooth on my EU HD2, very stock, and almost all other points you mentioned.
Well the rom development for hd2 has come a long way from dft/cotulla build. I'd suggest you try some newer nn sense roms which I find way faster than any sense rom, that's the only way to find out for sure.
After countless trail and error I have found my rom(HyperDroid GBX) which does what I want it to do, it fast smooth, everything seems to work for me, battery its good, GPS,Bluetooth,wifi all work as intended and that's why its my daily driver( I still try other roms but this is where I go back to), keep in mind that just because it works for me doest mean it'll work for you.
Td;lr: try other roms and find one that meets your needs (do your home work! )