Oct 18, 2009
loserskater uploaded a new motoblur 0.76 build with some fixes. it's up at vogue-hero.
Oct 8, 2009
I uploaded a new motoblur with working data. Create a new motoblur account with whatever username and your gmail address. If you want to login to your google account make sure to use the same user name/gmail you used for your motoblur account. This is a beta test so have fun. Use it like ion. You might want to use the hero resolution. I haven't tested any others. Call/sms/audio/fxcamera all work. Haven't tested gps or bluetooth. Make sure you turn on animations.
Here is a video from Drizzys G1 port. Ignore some of the info about sdcard/wifi since it doesn't apply to the Vogue Port.
http://www.youtube.com/watch?v=NJhqxcpUK4o
How is its stability and speed? Appropriate for everyday use?
Aaaaaaaaand downloading. Any issues you've noticed right off the bat?
use task killer to kill of some apps that load up at start. other than that it's runs like regular cupcake builds. sms goes through fine. calls work. speaker phone. in call volume. it might need the audio hack to get the volume a little louder. camera should work but not tested. if not i'll bring over the pulse default camera because that actually works.
So far this is pretty effing sweet!
I've noticed the keyboard is a little laggy, sometimes it hangs for a sec, causing doubled letters or mistypings. It could just be that I have a slow SD card though
zakkain said:
So far this is pretty effing sweet!
I've noticed the keyboard is a little laggy, sometimes it hangs for a sec, causing doubled letters or mistypings. It could just be that I have a slow SD card though
Click to expand...
Click to collapse
nah it's just the build. i'll tweak some stuff tomorrow and put out a beta2. picture gallery/video gallery hangs so those are getting replaced.
ill see what i can do as far as getting some of the pink out later
EDIT: wrong thread lol, for the pulse
oh, n as far as resolution goes, i've got it goin at 240x320 @ 120 lcd.density..most things seem to work s'far.
I'm finding power (end button) no workie..just me or known issue?
Damn, I'm running at 320x480 with no lcd.density entry in default.txt
also, I have no power button action either
PS: This is awesooome! Totally revitalized my interest in the Android Vogue projects. Keep it coming, Zen, you rock.
Confirming BLUR at 320x240 on a Kaiser. Only shtick is that without wiFi, I can't resolve the setup process.
I like this so far. anyone using it on kaiser? also I get the error message about invalid number
Merlin_reloaded said:
Confirming BLUR at 320x240 on a Kaiser. Only shtick is that without wiFi, I can't resolve the setup process.
Click to expand...
Click to collapse
the trick is to auto enable mobile internet in your default.txt. do you have that? or do you rely on wifi?
Running MotoBlur at 480x320 with backlight at 120 on Sprint Touch. Does run a little sluggish though, but still going through setup so it might just be during this time.
From mobile-review.com:
The DEXT makes use of Google Android 1.1 operating system with MOTOBLUR tacked on top of it.........
http://www.mobile-review.com/review/motorola-dext-en.shtml
So it is android 1.1? :-(
how to power off?
Merlin_reloaded said:
Confirming BLUR at 320x240 on a Kaiser. Only shtick is that without wiFi, I can't resolve the setup process.
Click to expand...
Click to collapse
If you push the menu button, you have access to network configuration (APN and wireless conf).
The Mototrola builds expect a seperate button for power on/off instead of using the red phone button. The hardware key mapping may need to be adjusted.
I will confirm that it is working on my kaiser quite well actually I have gotten a few force closes mainly voice stuff.
is it possible to run this build without connection?
I'm really liking the feel of this, the status icons on the desktop are cool (facebook, etc..)
Making calls is kind of challenging, face hits the hangup button, and screen won't power off in a call. Some hangups, slow downs, and the lack of a power button.
I'd like to see this one further developed though, i think it has potential.
Thanks Z!
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
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.
Hello i'm new android user.I was wondering what more will 2.1 update give me.If someone can explain me i will be very pleased.Thank you.
I dont know that much about 2.1 but thats what im looking for:
VPN (Which i need)
unlock touch pattern (whatever you call it)
More applications from Market
Speed (especially the dialer)
Cooler overall for sure, with the live background stuff.
Proper bluetooth! Finally!
So you can bluetooth photos and music to another phone.
Working bluetooth
So I can finally use the blasted thing in my car instead of my 2006 xda, and stop getting my coat when my mates are passing por* erm files around
list
Bluetooth
3D Gallary (In some ROMs)
Much Better Integration of Social Nets in Contacts
Lot of A2.1 Dedicated Apps in the Market
Market it self.
Navigation
Googles
Sound Input
Some stability and performance
etc etc etc
EDIT: Not to forget Live Wallpapers(in Some ROMs) and Enriched Camera.
Navigation is the big one that will make a difference I feel
Sent from my T-Mobile_G2_Touch using Tapatalk
harsha_aithal said:
Some stability and performance
Click to expand...
Click to collapse
overclocked 2.1 is going to be
I have not moved to Android 4.0 so far mainly due to the camera issues. Now it seems the chefs have finally resolved these issues and there are a few ROMs out there that are 'fully working'. I have tried a few of these and am fairly impressed so far - I have managed to import the ROM into the DSIXDA kitchen and add my own apps & customisations etc - so a big thank you to everyone for your work.
In my testing I have hit an issue with the Internet Calling functionality (SIP) in that I cannot make calls - I can receive them but cannot make calls. I have tested three different ROMs so far and all exhibit the same behavior (not ROMs I have cooked; ROMs I have downloaded - Blackout 3.0, Sabsa 3.0). I have two DHD's - my everyday one that has a 'stock' Android 2.3.5 ROM (3.12.405.1 rooted with my own apps etc) and this works fine so I know it is something in the Android 4.0.x ROMs. It appears to be the SIP proxy authentication that isn't happening with the 4.0.x ROMs although I haven't gone through the Wireshark traces too deeply yet.
Does anyone else use Internet Calling and have it working with Android 4.0.x?
Andy
Internet calling need 3g or wifi ...you can make a call.if it didnt work please use new settings
posted by www.mobilecrackerz.tk
mobilecrackers said:
Internet calling need 3g or wifi ...you can make a call.if it didnt work please use new settings
posted by www.mobilecrackerz.tk
Click to expand...
Click to collapse
Erm thanks for the reply, however if you read what I wrote I have two DHD's both with the same SIP configuation - the one running Andorid 2.3.5 works, the one running Android 4.0.3 or 4.0.4 does not. Both DHD's are on the same WiFi network via the same Access Point, the only difference is the version of Android.
'Just tested with Nik Project X and the behavior is the same. Has anyone got an'official' Android 4.0 device that can test this? i.e. is it just an Android 4.0 issue or an issue specific to the DHD?