Related
Is it possible to put rosie on a rom that isn't hero (like one of jf's roms).
I was thinking the same thing. What I did was updated to the hero rom and then backed up rosie.apk. Then went to the ion rom and tried to install rosie.apk through astro and it said that the apk cannot be installed on this phone. Could be some version check or something but I didnt bother to try any further.
There would be alot of HTC framework you would need to implement to a point where it would be pretty much hero to get it to work from my understanding.
From what I've read, Rosie (and few other HTC apps require a modified android core, so to get Rosie on a JF release, you'd use a rom that contained a majorty of the Hero code.
By the time you're done getting all the files for Rosie and it's associated widgets to run on a Google core you'd be running Hero. What's the point? Are we done asking this question now?
uberingram said:
By the time you're done getting all the files for Rosie and it's associated widgets to run on a Google core you'd be running Hero. What's the point? Are we done asking this question now?
Click to expand...
Click to collapse
No. There will be at least 6 more threads about this very topic.
Hi,
I actually tried on 5.02h.
It says that it cannot be installed.
So yes the answer is no.
uberingram said:
By the time you're done getting all the files for Rosie and it's associated widgets to run on a Google core you'd be running Hero. What's the point? Are we done asking this question now?
Click to expand...
Click to collapse
have you tried it on Rogers? i ask b/c u list it in your sig.
since that is HTC based (to my understanding at least)...this might be a possibility.
still though...i don't see much point
Technically, yes it can, since in reality, all rosie is is rosie on a non-hero rom (it's still very much android at the core). If you're talking about a simple file swap, it is possible, but by the time you're done swapping files, you'll have the htc modified framework again. However, rosie is still also very much the same Launcher apk from google, it's got a few tweaks here an there, and i think that with some heavy modification of the source it can be made to work similarly on a stock android framework. That's just for the desktop elements. The widgets are a different story, if you want binary compatibility with the rosie widgets, then, again, you have to import the HTC library, or reverse engineer it and implement your own.
It is possible, after all, Android is in many ways a community OS, so you can modify it as you please, but a simple patch up work and file swap? then no, it's not that easy.
::sigh:: quit asking these questions, think of it this way:
Have you tried running a .NET app, without having the .NET framework installed.
It's gonna say missing framework.
Hero is basically Android + a bunch of HTC written frameworks. And that framework is written under the assumption that there is 512MB ROM/256 RAM. (on their unreleased phone)
Hence the slowdowns on our lovely G1 with only 256MB ROM and 192RAM
Other Thoughts:
T-Mobile always does this crap though, give us the crappiest hardware (bare minimum, so they save money.)
Remember the MDA and then the WING, whilst at the same time AT&T's Pocket PC specs were far superior.
alapapa said:
have you tried it on Rogers? i ask b/c u list it in your sig.
since that is HTC based (to my understanding at least)...this might be a possibility.
still though...i don't see much point
Click to expand...
Click to collapse
I've given it some preliminary tries from an informational standpoint but that means going back to a plain Jane Rogers build. The really ****ty thing about the Hero build with Rosie is that Rosie and it's associated widgets are all interlaced with each other. You pull a few and that whole house of cards comes crashing down. The Hero Music widget for example requires the htc.framework. Before htc.framework and associated libraries releases permissions to the Music widget it references a series of DRM library files. I stopped after that but I can almost guarantee that the DRM libraries have some other off the wall dependencies only found on that specific build. HTC did this for a reason and it's obvious that they consider their Home replacement and widgets as a single package. Even if you managed to retain the HTC framework and replace all the dependencies it wouldn't surprise me in the slightest if some of these outer lying files made references to specific bit of code only found in the HTC core. HTC has done it before and it's name is TouchFlo3D.
Unless someone really wants to break down Rosie line by line it really ought be considered an all or nothing venture here at XDA. We really need to drop the mentality that HTC builds are drag and drop like theming was pre-cramfs. And even then, cramfs are just identifiers anyway. HTC is a tricky bastard. Always has been, always will be. In my honest opinion, if you want Rosie on a non Rosie build you best brush up on your mimicry skills.
Maybe it's just me...but aside from the HTC widgets, what exactly do you all love about the rosie UI so much? the little wheel that you can scroll between your desktops? How many people use that much desktop space? in all honesty, it's not *THAT* much more functional. For me the important portions of the Hero build are more behind the scenes..solid twitter app, lockscreen tied to music, notifications, and calendar events..the nice black notifications window...most importantly, without losing performance. /shrug - my version of the hero build is screenshotted here..works for me, even though I don't have the 'rosie' UI i get all of the important things that matter to me.
What build is that? Or is it custom?
afflaq said:
Maybe it's just me...but aside from the HTC widgets, what exactly do you all love about the rosie UI so much? the little wheel that you can scroll between your desktops? How many people use that much desktop space? in all honesty, it's not *THAT* much more functional. For me the important portions of the Hero build are more behind the scenes..solid twitter app, lockscreen tied to music, notifications, and calendar events..the nice black notifications window...most importantly, without losing performance. /shrug - my version of the hero build is screenshotted here..works for me, even though I don't have the 'rosie' UI i get all of the important things that matter to me.
Click to expand...
Click to collapse
Question: Does the lockscreen actually have the slide unlock? If so, you may have just sold me on your Hero mod. That's the ONE thing that I'm still utterly and completely in love with, and there are a LOT of bugs in the current Hero build, though w/o widgets it does run at least tolerably. I'm still hating the lack of landscape mode and led notifications.
/grumble
uberingram said:
What build is that? Or is it custom?
Click to expand...
Click to collapse
It's the hero build from haykuro..with a lot of work done to it to make it perform the way that I'm after. I'm out of town next week but I'm hoping to get a list of all of the changes that I've made compiled and make it usable if anyone wants it.
afflaq said:
It's the hero build from haykuro..with a lot of work done to it to make it perform the way that I'm after. I'm out of town next week but I'm hoping to get a list of all of the changes that I've made compiled and make it usable if anyone wants it.
Click to expand...
Click to collapse
I would be one. You've done exactly what I want out my Rogers build and the only reason I'm on it is for Exchange. I've started to learn how to do all this myself for that very reason.
TooSlo said:
Question: Does the lockscreen actually have the slide unlock? If so, you may have just sold me on your Hero mod. That's the ONE thing that I'm still utterly and completely in love with, and there are a LOT of bugs in the current Hero build, though w/o widgets it does run at least tolerably. I'm still hating the lack of landscape mode and led notifications.
/grumble
Click to expand...
Click to collapse
Yep - lockscreen works fine and also includes the music/notification functionality...attached a screenshot of that just now.
no LED notifications still - which is a pain in the ass I agree. The build I'm using is running Launcher.apk - not Rosie - and does autorotate.
afflaq said:
Yep - lockscreen works fine and also includes the music/notification functionality...attached a screenshot of that just now.
no LED notifications still - which is a pain in the ass I agree. The build I'm using is running Launcher.apk - not Rosie - and does autorotate.
Click to expand...
Click to collapse
Thanks for the heads up. I thought running the Launcher.apk might remove the awesome lock screen. I'm a bit more happy about running this build, if only we could get some working notifications!
uberingram said:
I would be one. You've done exactly what I want out my Rogers build and the only reason I'm on it is for Exchange. I've started to learn how to do all this myself for that very reason.
Click to expand...
Click to collapse
yea uh, you'll have to push Mail.apk and libHtcMail_jni.so back -- but it should work. my corporate exchange servers here suck **** apparently and only work with moxier for anything. I've never been able to get the Mail client or anything but Moxier to work with my corporate account.
afflaq said:
Yep - lockscreen works fine and also includes the music/notification functionality...attached a screenshot of that just now.
no LED notifications still - which is a pain in the ass I agree. The build I'm using is running Launcher.apk - not Rosie - and does autorotate.
Click to expand...
Click to collapse
You've officially got me salivating. I have zero need for Rosie and everything you have listed is exactly the things I wanted out of Android.
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.
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
Thread updated 17/01/2011 (d/m/y) to include FlyKernel 12a and a download for AngryBirds 1.3.5 for those who needed it. thread has also been cleaned up and old content removed. Instructions have been updated accordingly. Please let me know of any bugs or tweaks that need to be made.
Install for fully working Android Gingerbread Keyboard and newest Market at the bottom of this post!
This is a collection of packages that can be found around these forums that I believe amounts to the perfect Hero Setup. I am NOT a developer (although I have been known to make some themes and do some graphics work in the past), and I do not claim to have created any of this content. Instead what I am bringing you is a kind of gathering of the choicest picks from the Hero development forums, as well as the CyanogenMod 6.1 Final base. Most of this post is entirely optional, so this will allow you to build your own device, based on your preferences. Leave out things you feel you do not want, or add in extra steps if you feel you need them. Either way this will allow granular control of your Hero, for you to set it up just the way you want.
If nothing else this should be treated as a learning experience, if however you are unsure, and the post below looks a little daunting, you should consider flashing Floyo (created by the very talented erasmux) which is a complete packaged ROM. A lot of the content here has been taken from offerings that he has made available.
I take no responsibility for you destroying your phone. But for ME, my Hero is now the fastest it has ever been, with much better signal (and hugely faster browsing speed) with a theme I really love. So, presuming your Hero is already rooted, do a FULL wipe of everything, and then:
1) Flash Cyanogen Mod 6.1 FINAL in recovery (no need to reboot yet).
2) Flash Cyanogen Google Apps Addon.
3) Reboot your phone, log in and go through the initial setup. Once this is completed, reboot into recovery again.
4) (UPDATED) Flash Flykernel 12a (HUGE thanks to erasmux, this kernel is amazing). The version linked here is the one I have found to work best with this particular Hero setup (352-576, as such this is not overclocked, but performs exceptionally on my hero and doesn't have the annoying wake up issue, info on how to rename the file to overclock the kernel can be found at the erasmux flykernal post if you wish to do so). NOTE: Do NOT use the "-noatime" switch as this caused reboot loops for me in CM6.1.
5) Flash this notifications fix (provided by erasmux) which should fix some slightly hinky notification issues (jogball etc). This should now not be required with the newest Cyanogen build, I will do more testing and completely remove this section if this is confirmed.
6) Boot phone and let it get to the homescreen.
7) Reboot into recovery for the final time.
8) Flash The Latest Radio from this thread.
9) Reboot the phone (this may take a while after the radio installation).
OPTIONAL SETTINGS!
10) If you like using the HTC_IME mod, you can install it by manually installing the Clicker and then THIS version of the HTC_IME mod created using the AMAZING theming tool provided by gIMpSTa. I have created a theme that suits the feel of this CM6.1 based ROM using his tool, and it is working perfectly on my phone.
11) Enable JIT by going in to Settings > CyanogenMod Settings > Performance Settings > TICK "Use JIT" - And then reboot your phone (You can turn this off if you have issues with it turned on). In the latest Cyanogen 6.1 FINAL JIT is working perfectly, so unlike with RC1, I would now recommend having this turned ON!.
12) If you have issues fixing GPS sats, or if GPS does not update correctly when using it to navigate etc then you can try flashing THIS FIX (GPS libraries taken from FroydVillain and provided by erasmux as a fix for his Floyo ROM). If you are having issues actually fixing satellites you can also try flashing either the Europe, US or Asia sat-packs which can help GPS lock speed in your continent (if everything is already fine, you might want to avoid flashing these). Personally, I DO NOT use GPS on my device, so I can't comment on how well any of this works, but erasmux really knows his stuff, so I'm sure it will work if you are having problems.
13) CM6.1 comes with the NEW (official) Apps2SD built-in. However, the app needs to support this method or it will not allow you to move the app to the SD card. For those of you that prefer to use the OLD STYLE Apps2SD you can download it and flash it separately to enable this feature on this build of CyanogenMod.
That's the main setup sorted. You MAY have an issue with the Market following the radio installation (I did). If this happens, follow the instructions in this thread, the first fix (clearing the data) worked for me.
OK! Now on to apps. There are a few apps that really are a must if you want your Hero to both look and feel smooth as silk. So head over to the market, and download the following:
1) LanucherPro (Cyanogen comes with ADW, but I MUCH prefer LauncherPro). I use the XTG mod created by signals23 which has much more attractive widgets (if you have purchased the LP-Plus edition (I strongly recommend you do). You can, of course, use ANY homescreen, but LP is definitely my choice for beauty and speed. I actually DELETED ADW using: adb shell - rm /system/app/ADWLauncher.apk once I had LauncherPro installed, so it was no longer on the phone at all.
2) Beautiful Widgets - You have to pay for this, but trust me, it is absolutely worth the small amount of money. Once you have it, you can install any clock theme you like, such as SwirlClock made by yours truly
3) SMS Popup. Seriously, this app is amazing. Go into the default messages app, and turn off notifications. then head into the SMS Popup settings, and go into additional settings, turn ON "Quick Reply" and turn OFF "Screen on for Popup".
3) Youlu Address Book. I no longer recommend DialerOne on the Hero, as I find it too slow, especially when using the T9 "Dialer Search" function to call contacts using the numeric keypad. I find Youlou to be much faster, with a nice interface with an easy to navigate tabbed UI.
4) Advanced Task Killer. Once installed, open it up, turn off the notification bar icon in settings, and add your most frequently used apps to the ignore list (so the killer always leaves them running for speedy access). I usually leave: Messaging, Email and DialerOne in the ignore list.
5) SyncMyPix. Lets you properly sync your facebook contacts pictures so that they show up in DialerOne and LauncherPro.
6) Facebook app, or, whatever
7) Photoshop Express. I only add this here because there is no way of uploading multiple images to Facebook using the standard "Gallery" app, but you can do this using Photoshop Express, pretty nice little app, but this feature makes it worth having.
8) THEME! If you want to change the stock theme from white to black, go to: Settings > CyanogenMod Settings > User Interface > Tweaks Extras > Select a Theme and change your theme to STOCK_Black and then reboot your phone. This makes all of the theme a very nice gloss black effect WITHOUT having to flash a seperate theme ROM over Cyanogen (which is a much better way of doing things, as you are not replacing the newer .apk's with older, themed ones... Yes, I know the browser icon kinda sucks, but you can always download the nicer icon .png from here
9) Android 2.3 (Gingerbread) Keyboard. If you want to install this keyboard, it will overwrite the existing Android 2.2.1 Keyboard (and currently there is no way of going back). The Gingerbread keyboard is FULLY FUNCTIONAL, this version now has working dictionary and autocorrect. You CAN still use the HTC_IME keyboard with this installed though, so if you hardly use the stock Android keyboard anyway, there shouldn't be much harm installing it and giving it a shot. HERE it is for those of you that just can't wait
10) The newest Android 2.2.6 Market. Flash in recovery, tested working great on my Hero, very lovely interface and nice and fast
11) (NEW) Angry Birds 1.3.5. for those of you who were wondering how I got angry Birds to run pretty well on the Hero, use this version rather than the latest one available on the market
DONE. Of course, you can modify this in any way you like, but after completing all of this you will have your own, pieced together ROM, without any strange extras or crap you don't really need. On top of this, you can head in to the ROM manager that comes with Cyanogen and install ClockworkMod recovery (if you are still using an older Amon-Ra or something), which is nice and easy.
Also, I'm not joking. It's fast... The screenshot below is with common apps (messages, emails, dialerone) running, and I still have 86mb of free memory. The battery life is fantastic, signal is great, call speed, wifi locking etc all seem faster than I have had them before. So, let me know your results (I have not tested GPS!).
And there yo go, your own freshy squeezed Hero, complete with all the trimmings. Baste lightly in your own choice of apps and serve.
Zeb
This post will be updated as newer packages are released.
</walloftext>
interesting, thanks. There's also an ADW-remover script on the Floyo page.
I didn't realise people were theming LauncherPro widgets to that extent, will have to investigate!
m8 you have done about 90% of the changes that i have put to my hero.
definitely is the perfect setup for me too.
Can I just flash this kernel over VR12 ? And do I have to flash radio if I flash new kernel? What radio really does? thanks
p.s. great work
Dark Emotion said:
Can I just flash this kernel over VR12 ? And do I have to flash radio if I flash new kernel? What radio really does? thanks
p.s. great work
Click to expand...
Click to collapse
If you are coming from VR12 you will have to do a FULL wipe of everything (nand, battery setting, dalvik etc) in recovery before flashing all of these packages. So make sure you have backed up everything you want to keep before starting! I have no idea what effect flashing this stuff over an existing ROM will have as I did it all from scratch with a blank phone.
The Radio is possibly the riskiest aspect of this setup, and you can choose to leave it out alltogether if you wish, but for me this made possibly the largest difference, as everything from connecting to Wifi, switching back to 3G/HSPDA is much faster. Signal is better, and small things like initialising the dialler (the time it takes from me choosing to call a contact, to it actually ringing) feels much speedier, so I personally do recommend it! You don't need to use this Radio to use Flykernel 11c, so feel free to leave it out if you wish.
Zeb
Edit: I just noticed, do you mean, can you use Flykernel on it's own with VR12 without any of the other stuff? Yes, I believe you can, check you the Flykernel thread for more information, but I think it works for most ROMs.
Dark Emotion said:
Can I just flash this kernel over VR12 ? And do I have to flash radio if I flash new kernel? What radio really does? thanks
p.s. great work
Click to expand...
Click to collapse
If you flash only the kernel, you don't need to do anything else - No wipe at all necessary. Updating the radio is not related to the update of the kernel but still recommended as usually it also improves the hero experience and if there are problems you can always go back
I just received my refurbished hero (the digitalizer was dead) and am trying your setup. So far everything on the setup side was fine though I had a random reboot after flashing the kernel.
I will update with my feelings on this setup, thx for the guide!
I like this post ... what are the advantages of elelinux or floyo over the standard CM 6.1 release though? I tend to go for one of those instead for some reason!
mdon874 said:
I like this post ... what are the advantages of elelinux or floyo over the standard CM 6.1 release though? I tend to go for one of those instead for some reason!
Click to expand...
Click to collapse
I believe that the authors of these releases make modifications to the kernel, as well as making theme changes, adding packages of their choice etc. Some distributions are modified more than others (and not ALL of them use Cyanogen as a base I believe). You'd have to look at the specifics of those other ROMS to see exactly what is different (sometimes it's small things, such as the way the jog-ball flashes or how the LED behaves, and sometimes it's bigger, like having hacked settings, or adding otehr keyboards like the HTC_IME mod (which Cyanogen doesn't have as standard, but I prefer the android keyboard anyways). You can always add these things in yourself later if you know how, which is what I have chosen to do using this setup. this way you have complete control over what is added to your phone.
Also, Flykernel, and the Radio mentioned here have serious performance benefits over other offerings as far as I am concerned. you COULD just flash those two over the ROM of your choice, but doing things the way I have mentioned above just gives you a larger level of granular control, if thats what you really want that is
Also, I have wanted to use Cyanogen as a base for a while to see how it was, but I found it very hard to find decent documentation on how to set it up correctly, that is why, once I worked it out, I decided to post the method I used here for other people to try.
Zeb
thanks for the quick reply I kinda like flashing and starting from scratch on a clean install and adding things bit by bit so I'm guna follow ur guide and set my hero up myself.... also thanks for pointing me in the direction of the alternate launcher pro mod ... looks pretty cool!
mdon874 said:
thanks for the quick reply I kinda like flashing and starting from scratch on a clean install and adding things bit by bit so I'm guna follow ur guide and set my hero up myself.... also thanks for pointing me in the direction of the alternate launcher pro mod ... looks pretty cool!
Click to expand...
Click to collapse
No problemo! Just as a side-note, the kernel that COMES with Cyanogen 6.1 seems good enough, but I had problems with waking the phone up (sometimes I had to push the power button 3 or 4 times to get to the unlock screen). This is a pretty standard issue with a lot of kernels where the minimum clock speed is a little too low and the phone doesn't quite rev up enough when waking up. So, if using CM6.1 as a base (as posted above) Flykernel is a must (using the clockspeeds I posted above), as it removes this issue entirely and boosts overall performance.
Zeb
agree for the configuration, is the best(for now )
however,instead of sms popup i use handcent sms, the application is very similar to the application of the iPhone, and has a built-in sms popup...try it!
magokh said:
agree for the configuration, is the best(for now )
however,instead of sms popup i use handcent sms, the application is very similar to the application of the iPhone, and has a built-in sms popup...try it!
Click to expand...
Click to collapse
Nice addition, thanks! I have used ChompSMS before, but I really like the messaging app in Android 2.2, so I prefer to stick with that and use SMS Popup to handle the quick reply (which is an awesome feature). Also, the theme I posted skins the SMSPopup notification screen to fit with the rest of the device, to it looks extra good and as though it was really all put together into a proper ROM package.
I haven't tried Handcent myself but I have heard good things about it, so yea, probably worth a try if you aren't keen on the stock SMS app!
Zeb
Thread moved to General.
thanks for this, very useful especially the sms popup thing
Hello to all and thank you for the great topics on whatever is needed to tweak the Hero to full potential. I would like to flash a new rom (from VR12). Should i flash CyanogenMod 6.1.0 RC1 or wait for a custom rom based on CM 6.1 like Floyo or Elelinux's ROM. What would you suggest?
HTC_ime simply does not work. every time i try to to start it it force closes. I followed instructions as i usually did every single time before. help?
marcinr said:
HTC_ime simply does not work. every time i try to to start it it force closes. I followed instructions as i usually did every single time before. help?
Click to expand...
Click to collapse
Honestly, I don't use HTC_IME mod so I haven't even tried installing it! I will try tomorrow and let you know if I make it work.
Sent from my HTC Hero using XDA App
vladsk8 said:
Hello to all and thank you for the great topics on whatever is needed to tweak the Hero to full potential. I would like to flash a new rom (from VR12). Should i flash CyanogenMod 6.1.0 RC1 or wait for a custom rom based on CM 6.1 like Floyo or Elelinux's ROM. What would you suggest?
Click to expand...
Click to collapse
Personally, I much prefer this method! That's why I made this thread! Give it a try, if you don't like it you can always wipe the phone nice and easy and install Floyo!
Sent from my HTC Hero using XDA App
Settings
Any chance you can add some of the settings you use, like cyanogen or spare parts settings? I followed your guide completely and its pretty fast but i think enabling JIT might help but im too afraid to try. Thank you
Well, even though I actually don't have a problem with WinMo 6.5 outside of a few minor annoyances I've decided to make the switch over to Android...guessing NAND...though, still looking to here about WinMo 7...
I'm just noticing that there is more support and apps being developed for Android and the future of my HD2 suddenly shows more growth...have my fingers crossed waiting for Netflix to resolve the DRM issues they have with Android!
I was always waiting for a solid Android build that actually replaced WinMo (NAND is finally here). During that time I used WinMo and actually liked it. First thing I will miss is the customization. I don't think there's another Mobile OS that beats it in that department...and I REALLY like customizing.
I've been using Android more now and still don't understand how the NAND will work. Have read a lot...as far as installing, that won't be a problem with me. My questions start with customizing. Where will the media folder be? Is there a folder on the SD card that Android associates ring tones with? I make my own ringtones as mp3 files, so i need to know the structure of how Android handles media. WinMo was simple. Also, the Android build I was using did not support USB without major hickups...well...it just didn't work. I'm not going to assume all Android builds are like this, but can I expect Android to be able to link via USB and I can work with it as a storage device and create folders and organize in this manor?
I know you guys work hard and appreciate it, so please do not take this the wrong way. Which Android build is the most stable at this time with all features working? I ask this cuz I notice there tends to be some builds that come along much slower than others and bugs as well as a lack of hardware support can occur. Is there a build that's considered stable and all hardware is supported?
I've basically been trying to make Android provide the same experience as far as apps and ease of use I had with WinMo...I think I'm there.
Does Android have a set structure with Wallpapers...ringtones...documents and such? Example...does each file type have its own folder on the device or storage card in which Android associates the tools which manages them? I always keep my device clean and move all files to the card that don't NEED to be on the device. Is this possible with Android?
Android play well with Microsoft Docs?...Word?
I've always felt that Android ran smoother than WinMo 6.5. I noticed after a while it can get a little sluggish. Is Android like that? I believe Android is Linux base? I'm expecting memory management to better. On PC, I'm use to any Unix based OS to out perform WinAnything with resource management.
I also noticed something strange about some of these apps in the Android market. One, a lot of adds within the apps. Two, a lot of these apps tend to require access of priveledge areas that can be security risks...to make it worse you fine yourself saying why a browser would need access to anything else outside on internet and maybe GPS. Other apps have access to areas that make no sense to me.
Are their security issues with Android...it's market...or apps?
That's all i can think of now. Didn't have a moment to proof read, so please excuse me. Have to take care of a few things. be back shortly.
Thanks.
WOW! What can I say... Ditto. I love WinMo, but I'm fearful that I'm watching it's death rattle. Win Phone 7 seems like a illegitimate infant in a world of fast moving, focused, college freshmen (albeit, not the brightest).
I had a lot of reservations with switching from WM. Mainly related to the phone being able to handle work related stuff. So I too ran WM and android on SD. I must admit though, that after having run android for almost 2 months without loading WM, (I basically pretended I had bought a new phone and forgot all I could do with WM), I had figured out work-arounds and got it running more than sufficiently. The only problem I had was having to back-up the SD in fear of a random reboot corrupting the data.img. Now with NAND, it's no longer a problem. I can honestly say that the switch was easy, and I'm glad I no longer have winmo in my life.
IMO Android is a far superior OS, and I can't sing it's praises enough.
As for all the questions:
Media folder is built like this:
media
->audio
->->alarms
->->notifications
->->ringtones
->->ui
Different folders are available for their obvious uses (i.e. go into ringtone selection, and you don't get the ui folder listed).
USB is more than stable (for me at least), never had a problem since NAND. Having most stuff moved to SDCard the phone hates it when I plug it in as a disk drive, (widgets disappear etc.) but within a minute of unplugging it it's back to normal.
I personally feel the desire build are the best, however as for more stable? I believe we are reaching a plateau where stability is the norm. I have tried nexus builds, and have had no problems with them either, it's just personal taste. The HD builds (Desire HD Base) are a little more 'experimental' but with reading, you'll learn what works on each build, and what doesn't. Figure what's important to you, and check.
The best advice I can give is get hold of SPB Backup (For WM). Do a full backup. Then jump in at android's deep end. (After reading how obviously). If you don't like it, re-flash winmo, redo your backup, and it's like you never left. You won't regret it though.
Man I'd love to dump WM as well, bu I can't bear the thought of all the days going by where I can't be the dude on the bus who reboots into ubuntu to pass the time...sigh.
MattOG said:
The best advice I can give is get hold of SPB Backup (For WM). Do a full backup. Then jump in at android's deep end. (After reading how obviously). If you don't like it, re-flash winmo, redo your backup, and it's like you never left. You won't regret it though.
Click to expand...
Click to collapse
Microsoft My Phone actually does fine with all the backup I need.
I'm still wondering about security issues. Example: http://news.cnet.com/8301-1009_3-20026804-83.html
Also, hit a bump in the road. It would seem that Android doesn't support the Mugen 2600 Extended battery!
The primary security issue with Android isn't Android or Linux, it's Google. Google's security is very problematical, Gmail has been hacked (as has Gmails security software) by someone.*
*Some think it's the Chinese government, the official Chinese response is, "No, it's just kids" but since all hacked accounts we know about have been dissidents, the government theory looks pretty solid....
The primary issue is NOT Google. It's the user.
If you're loading up banking apps on a device that you could lose, be stolen, or bluetooth hacked, then don't blame anyone but oneself.
I've yet to know anyone who's been phone-hacked if that's any consolation.
As a former hd2/android user Id have to say It makes the entire experience of the phone better.
I think it also depends on what you are use to. as far as customizing I would venture to say that there is just as much customization with winmo as there is android. Though id have to say I found myself looking for skins more often than not cause winmo was so ugly to me.
I enjoy having almost direct access to all my data without it having to look like winphone7.
As far as security I think its always been tighter because most people were on different types of phones. now that we have blackberrys and iphones and android phones I think possible viruses will show.
I believe google has a built in kill switch for rogue apps. Also if you buy apps from the legit market you should have no problem!
Ok two things that I'm trying not to get frustrated about before I put a little research into it...
First, why in the world does Android want to crop every image instead of using the entire image as a wallpaper?
I even have wallpapers that are the exact size of the display and Android still wants to crop a small portion of that image?....help please...
Second, why can't I get a simple widget or window dedicated to favorite contacts, such as sense in WinMo does without having to pay for it?
Android doesn't have a simple tool that allows you to setup a favs like Sense does in WinMo? There's this LaucherPro that wants to charge me to do so?
Thanks
Why does Photoshop Express require access to personal information, phone calls and full internet access?
Devils1stBorn said:
Why does Photoshop Express require access to personal information, phone calls and full internet access?
Click to expand...
Click to collapse
checking the install notes It says
the only one that bothers me is the it reads contact info.
the phone state is different than phone info. it basically should shut down when you recieve a phone call. why it needs access to your contacts is why im uninstalling it.
I can also set basic contacts by long pressing a blank spot on the screen and selecting shortcuts>contacts>the actual contact.
wallpaper I believe if you set the picture with the proper resolution it shouldnt crop it
Devils1stBorn said:
Ok two things that I'm trying not to get frustrated about before I put a little research into it...
First, why in the world does Android want to crop every image instead of using the entire image as a wallpaper?
I even have wallpapers that are the exact size of the display and Android still wants to crop a small portion of that image?....help please...
Second, why can't I get a simple widget or window dedicated to favorite contacts, such as sense in WinMo does without having to pay for it?
Android doesn't have a simple tool that allows you to setup a favs like Sense does in WinMo? There's this LaucherPro that wants to charge me to do so?
Thanks
Click to expand...
Click to collapse
1. You can just expand the crop window so it encapsulates your entire wallpaper, if it indeed is in perfect size. Keep in mind the crop window is sized for 3 homescreens or 5 or however many you have, so if your perfect size is for just one screen (480x800) you'll have a bit of a problem there.
2. You can just place contacts on the desktop. That's the closest you'll get without paying for this in LauncherPro. While you're at it, even if you don't want to pay - get LauncherPro and replace the default Launcher already. You'll love its speed superiority immediately.
A lot of devs put permissions on to prevent possible problems, also, not sure if it relates to android, but I know some permissions are needed for things that you would not normally relate them to, possibly things like automatically pausing operations when a call comes in etc...
schunniky said:
1. You can just expand the crop window so it encapsulates your entire wallpaper, if it indeed is in perfect size. Keep in mind the crop window is sized for 3 homescreens or 5 or however many you have, so if your perfect size is for just one screen (480x800) you'll have a bit of a problem there.
2. You can just place contacts on the desktop. That's the closest you'll get without paying for this in LauncherPro. While you're at it, even if you don't want to pay - get LauncherPro and replace the default Launcher already. You'll love its speed superiority immediately.
Click to expand...
Click to collapse
I figured out the contacts on desktop, thanks though!
As for the wallpapers, I do try to expand the Window and it never completely encapsulates the entire image. I just dont get why Android doesn't allow the Wallpaper to remain static while your homescreens maneuver over it.