yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] JeckyllHavok:
I think you just need to select the eclair3ddrivers in system type, when creating the zImage
[Touch CDMA Android Development] drewden123:
Screens:
[Touch CDMA Android Development] mssmison:
thanks for posting the screens :)
[Touch CDMA Android Development] Reddog80p:
Drewden - How's this work for you? how's the speed for you compare to the original eclair build? I couldn't get this build working quite right but I'm going to attempt it again later today. The first norootfs build worked pretty good for me and was pretty fast for an eclair build.
[Touch CDMA Android Development] TheKartus:
I tried to add my own apps into the system image but I am getting an issue with the installation of the .tar file. Its telling me I don't have enough space... Should I make a bigger partition on my sd card for the system image?
[Touch CDMA Android Development] xtac21:
I'm in the same boat. version 1 + the update worked awesome. it was fast and never really gave any problems beside the hw3d stuff not working properly.

This build is pretty slow, and the launcher is constantly force closing or hanging the phone when trying to open the launcher.

I did get the launcher to open once, and it looked sweet. if this build could get tweaked to run as fast as the first build and be more stable it would great.

Lots of potential here, but for now i'm going back to 1.0 as the os is more stable.
[Touch CDMA Android Development] incubus26jc:
My bad wrong thread
[Touch CDMA Android Development] sshark:
I got this one running pretty alright, I am using Home++ app so no FC issue for me. It's faster and much stable compared to 1.0, Dialer/Phone app is tad bit faster. Compcache/Swap setting is cool.

But I am use to 240 build, so I am not getting any love. I am looking forward for QVGA build that Craig talked about...

EDIT: It gets even more responsive when Compcache is reduced to 16 (did after drewden said). Even dialer comes in less than a second. Now just want 240 version...
[Touch CDMA Android Development] drewden123:
It's running pretty well for eclair. it has its moments but I set the homescreen to stay in memory and enabled compcache @ 16 meg. The launcher fc's stopped after that. I'm not too sure on the compcache/swap thing so if somebody could fill me in that'd be great, as id like to know the optimal setting.
[Touch CDMA Android Development] sparky101747:
you could also try setting max app processes to 4 in development settings
[Touch CDMA Android Development] JeckyllHavok:
Hey Incubus, can you put up a list of all widgets you use on your screenshoot?
[Touch CDMA Android Development] incubus26jc:
sure,

beautiful widgets 2.36

eRay widget 2.15

Pure Messenger Widget 1.2.8

Dual Mount sd widget 1.6

Taskiller

Facebook

LastFm

News and weather widget

Xbox Live Avatar Widget

Tech Buzz

Calendar

Power Control
[Touch CDMA Android Development] mssmison:
Don't use that update with my build, it will break stuff.

I'll put out a kaiser update right away.

The bluetooth is everything I had before.
[Touch CDMA Android Development] tiagoclc:
Thanks a lot man, but i've merged your old sysinit.rc with sysinit.rc from that post and it works!
[Touch CDMA Android Development] tiagoclc:
why the command su was removed?

I noticed that the su command has been removed from this build.

Any specific reason?
[Touch CDMA Android Development] tiagoclc:
Which NBH should I use for your (kaiser) wifi patch work?
[Touch CDMA Android Development] TheKartus:
I installed this build with a new data file. My contacts APP is screwed up now.

The only letter that is displayed as a category is U. All the names are falling into one group below that. Contacts worked fine in previous builds.
[Touch CDMA Android Development] tiagoclc:
Read the first post...

"Updated Contacts app, if you keep your old data it won't order your contacts properly."

So sync with google contacts with an old build, then flash this build and then sync again.
[Touch CDMA Android Development] TheKartus:
I'm not using NAND. I cleared my data and installed the new system on my partitions. Is that not what is meant by not keeping my old data?

EDIT: Also, the 3d launcher option doesn't seem to be working. Not sure where the option for the helix launcher is, but that looks sweet.
[Touch CDMA Android Development] mrono:
My rom is very laggy when returning to the home screen, anyone else experiencing this?
[Touch CDMA Android Development] JM-PDA:
I am also getting the same result.

Installed V6 on my SD card with 2 EXT2 partitions with no data from any other build.

Used the Install utility to erase data and also requested that data be deleted when I installed the System.

I am also getting all contacts under the "U" category.

Though it does not appear to be a big deal because I can bring up the keyboard. As I type, it will bring up the names matching the letters typed.

Everthing else seems to be running very well.

I've been running the Turn by Turn navigation and it is very smooth.

This posting is just an FYI for mssmision...

Thanks for the build!

Enjoying it!
[Touch CDMA Android Development] preardon:
Same issue, same procedure.

EDIT: Upon further investigation, I noticed that when using the fast scroll in contacts, other groupings are displayed also out of order.

I cannot get the 3d launcher to load either. Option is enabled with no apparent effect.

Rest of ROM working real well! Will you be able to link Myn's overclock app when it goes up?
[Touch CDMA Android Development] mssmison:
The 3d launcher is partly why you'll see version a coming out this morning :)

And I'm looking to the contacts app to see what's happening..
[Touch CDMA Android Development] DmK75:
I install this build and WiFi update, but WiFi unable to start.
[Touch CDMA Android Development] mssmison:
6a posted to first page.

and a wifi update posted as well...

sorry guys :)
[Touch CDMA Android Development] TheKartus:
Just installed the new system. It reverted the resolution back to the weird small looking icons and stuff. Vogue Parts keeps force closing on me. I am going to restart and try again.
[Touch CDMA Android Development] DmK75:
Thanks!

WiFi also not starting...
[Touch CDMA Android Development] a5ehren:
I'm also getting FCs in Vogue Parts after first boot.
[Touch CDMA Android Development] mssmison:
If you are using your old data file you will probably have to clear it.

adb shell rm /data/data/com.android.vogue_parts/shared_prefs/com.android.vogue_parts_preferences.xml

That should fix up the FC with old data.

I added a full eclair market apk for qvga to the first page. (so you can see all apps) I'll include it in my next version.
[Touch CDMA Android Development] TheKartus:
Can I run that command in terminal, not through abd?
[Touch CDMA Android Development] mssmison:
of course, just don't put the adb shell part in :)

Or browse to it with Astro I suppose would work too :)
[Touch CDMA Android Development] TheKartus:
What does the rm command do? remove it? if I browse to it with Astro?
[Touch CDMA Android Development] Maranevim:
sadly, even after i installed the kaiser wifi update, im still unable to start wifi :(
[Touch CDMA Android Development] umbilicalbungee:
zimage?

Thanks for this new update. I'm really psyched to get the wired headset working!

Where is that zimage file again?

I got things working using this one: http://it029000.massey.ac.nz/vogue/files/zImage-16-03-10 but wondered if I should be using something else?

(Also in case anyone is wondering it doesn't seem that you have to reinstall to load with a new zImage file, but you do have to rename zImage-16-03-10 to just zImage)
[Touch CDMA Android Development] mssmison:
Nope that's the one you want to use :)
[Touch CDMA Android Development] mrkite38:
yes, remove.
[Touch CDMA Android Development] umbilicalbungee:
Thanks. I'll add it to my new install instructions post.
[Touch CDMA Android Development] fadimo305:
mssmison what is the status on the Camera for android(your build)???
[Touch CDMA Android Development] mssmison:
a nightmare to be honest.

and moving very slowly. I've gotten it to compile, now it's just debugging to see what I can figure out.
[Touch CDMA Android Development] a5ehren:
Yes, rm is the UNIX/Linux command for "remove". Deleting the file in Astro would have the same effect.
[Touch CDMA Android Development] djkoa:
We are with u! Be sure of it!!! Anything just tell! We support u :)
[Touch CDMA Android Development] a5ehren:
Quick note - if you're trying HelixLauncher, make sure to not check the box that shows up the first time you boot with it on...for me it's just FC, and now I can't get to any apps to disable it so I have to wipe my data :p
[Touch CDMA Android Development] mssmison:
check what box?

did you turn on 3d on a qvga system?

and because it's installed as an app just remove it from /data/app folder and you'll be back to the default launcher. :)
[Touch CDMA Android Development] a5ehren:
Yeah I tried 3D on a QVGA system - figured that wouldn't go well, but I wanted to try it anyway :p. I'm running Helix 2D now.

After you change launchers, at the first boot it asks you if you want to use HelixLauncher or Home to open something (I assume it's the home screen), and it has a box to select on whether or not to use that as the default.
[Touch CDMA Android Development] hexto:
I tried this build for two days and v6a today and had to flash to something else. It looked nice but data was super slow on it for some reason. Market crawled and browser was no better. Opera Mini sped things up a bit but no where near what I'm used to. I also couldn't get YouTube to work which is a deal breaker for me. Everything else worked great and it looks awesome. I'm sure I'll be trying it again in the near future.
[Touch CDMA Android Development] TheKartus:
Got myself up and running at QVGA. Couldn't get it to switch the resolution to HVGA correctly.

Contacts are still not working right.

EDIT: phone keeps resetting itself also while trying to install apps via Astro.
[Touch CDMA Android Development] cp0020:
can anybody get YouTube to work on this build?
[Touch CDMA Android Development] hexto:
I never did using QVGA. Not sure if anyone got it using another resolution
[Touch CDMA Android Development] mssmison:
I don't think anyone will be getting it working. I think it's an issue with data speeds. I'll look into it tonight :)
[Touch CDMA Android Development] bangout:
I cant get youtube to work either and im not running qvga I haven't tried to take it out and try a different version of youtube yet
[Touch CDMA Android Development] preardon:
After the Market update i can not install apps. Market can find apps that were once blocked and download them but FC's one it tries to install.
[Touch CDMA Android Development] loserskater:
I'm experiencing the exact same problem, just wiped data and installed fresh without the update. Most of the apps I use are now working in 320x240 anyway.
[Touch CDMA Android Development] preardon:
I was also able to reinstall the system without wiping data to get the old market working again.
[Touch CDMA Android Development] tatnai:
i would try clearing dalvik cache from replimenu (install menu) after installing the new market.
[Touch CDMA Android Development] tiagoclc:
Try to fix permissions.
[Touch CDMA Android Development] tiagoclc:
Kaiser wifi and bluetooth working!!!

Update for the kaiser wifi. Working!

1 - Get latest nbh in http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

(i'm using http://it029000.massey.ac.nz/vogue/files/kaisimg-panel2-320-tilt-18-03-10.nbh)

2 - Flash it;

3 - Download this file: http://www.4shared.com/file/243751803/b5f2445e/androidupdate_-_kaiser_wifi_fi.html

4 - Rename to androidupdate.tar and put in andboot folder on sdcard;

5 - Reboot phone and go to install menu;

6 - Select install update and then press yes and wait;

7 - Select fix permissions and wait;

8 - Remove battery and put it back;

9 - Turn on phone;

10 - Enjoy!!!
[Touch CDMA Android Development] Maranevim:
wifi

great, with newest dzo nbh it actually works :) great job :)

on WPA2-PSK still little crappy, but on unsecured network works perfectly :)
[Touch CDMA Android Development] DmK75:
Hi, tiagoclc!

I install your fix, and WiFi start.

But after show message "Unable to scan for networks" and turning off.

Bluetooth working!
[Touch CDMA Android Development] preardon:
Tried both, new market still force closes when trying to install an app.
[Touch CDMA Android Development] mssmison:
try this.

rm -r /data/data/com.android.vending
[Touch CDMA Android Development] preardon:
Does it matter if I do it before or after the market install?
[Touch CDMA Android Development] tiagoclc:
Try this nbh: http://it029000.massey.ac.nz/vogue/f...t-18-03-10.nbh

with a clean install of version 6a from first post.

Dont forget to fix permissions
[Touch CDMA Android Development] polyrhythmic:
mssmison, I get the same FC using the Hacked market to install, every time. Browing apps and downloading works fine. I've tried removing /data/data/com.android.vending as well as chown-ing the Vending.apk, reinstalling, etc. etc. but I can't get the hacked market working. Did you ever find out how they edited the Vending.apk? I bet the fix would work for both our builds.

Here's the error from logcat:

E/AndroidRuntime( 1946): Caused by: java.lang.SecurityException: Not allowed to start service Intent { dat=content://downloads/download/13 cmp=com.android.vending/.AssetDownloader$DownloadManagerBroadcastReceiver$DownloadManagerService (has extras) } without permission com.android.vending.INTENT_VENDING_ONLY
[Touch CDMA Android Development] tatnai:
hmm. I did fresh install to partition, new data file. I added the new market by replacing it in androidinstall.tar. I'm getting force closes whenever I try to dl an app too. is it working for anyone, and if it is, what method did you use to replace vending.apk?

btw mssmison, this build rocks. faster than I expected (no swap). can't wait for the camera and bluetooth phone audio.
[Touch CDMA Android Development] mssmison:
I have to apologize guys I didn't use the 2.1 market I just trusted him that it works :(

I'll have a look into it tomorrow and let you guys know.
[Touch CDMA Android Development] tatnai:
want to change my lcd.density to 110. there is a build.prop in the androidinstall.tar in /system/, but there is none in that location once it is installed. couldn't find the value in vogueinit in /system/bin/. how do I do this? TIA.
[Touch CDMA Android Development] crackeyes:
will not switch to hvga

When I try to switch it to HVGA i go to the vouge parts and I hit the mode to switch it to read write and then try to switch to hvga and it just sits ther spinning saying running command but does nothing. This is with a fresh install and a fresh data wipe any ideas
[Touch CDMA Android Development] preardon:
This looked promising at first but after doing it and rebooting it came to the same result.

No worries, I'm fine with the old market for now. I was just more concerned that a build with the new one built in may not properly install any apps, which wouldn't be good for anyone. Thanks for the hard work mssmison.

Also, do you know if the "Keep home app in memory" option applies to helixlaiuncher or is it just the default home?
[Touch CDMA Android Development] mssmison:
Yes I'm sorry, I do know what the issue is :) When I moved all the app_store files I neglected to update my config app. Here is a new version in an androidupdate.tar file. It's already been added to my next revision.

Thank you so much for finding this and letting me know :)

I've also added it to the first page :)
[Touch CDMA Android Development] crackeyes:
not a promblem I enjoy finding issues so they can be resolved to help everyone out. Thanks for the quick fix
[Touch CDMA Android Development] crackeyes:
I can verfy the update fixed the vouge parts issue. Thanks
[Touch CDMA Android Development] tatnai:
been running 6a with default launcher from nand all day today, this is my new favorite build. here's why:

1. fast. maybe not quite donut fast, but fast enough that I don't notice a functional difference. and I am running it without compcache or linux swap. contacts load dare I say faster than wysie's on donut.

2. stable. rock solid.

3. battery life is as good as it is on donut. been running all day and I am at 89%.

4. mssmison has outdone himself with vogue parts. I'm running apps2SD with the click of a button; many other goodies in there. also use spare parts "keep home screen in memory" to stop home screen reloads. phone prioritizer running gets my phone calls coming in faster than they did on donut without phone prioritizer.

5. eclair goodies: the refinement and better integration of programs on eclair is rather nice (contacts and facebook, for instance).

I ran donut for a (long) while without taking on eclair because I didn't want to sacrifice speed or stability. this eclair sacrifices neither. and even though I don't have phone bluetooth audio or camera, for me the upsides are nice enough that I am sticking with it. mssmison has put a lot of work into this one, and it shows.

a couple requests (my wish list) for my perfect build (some apply to android in general, not just this build), these are not bugs, just things that would put the finishing touches (after camera and phone bluetooth audio, are done):

a. a way to change lcd.density to 110 instead of 120 for qvga (very minor, i just need to figure out how to do this myself with this new vogue parts thing)

b. incorporation of the "full market" settings that myn and plemen had in their donut build.prop that allow you too see all paid apps without using Market Enabler (minor)

c. prevent menu from being able to unlock the screen to force slide to unlock, preventing accidental double tap menu unlocks (minor, personal preference - maybe another option for vogue parts?)

d. now that things are getting so close to being perfect, dare I wish for us to get spare parts red button "home, then sleep" working, so we can change long press camera button to activate the running apps list rather than go to home? probably really wishful thinking.

i'm done. mssmison, you nailed this one right on the head. strong work. thanks for continuing to develop for the vogue.
[Touch CDMA Android Development] mssmison:
Thanks for the nice words man. To answer your questions

a. 120 is the way it should be for qvga, and makes keyboards fit right etc. but yeah I can change that no problem. I'll make it selectable via spare parts.

b.It's not a build.prop thing that they've done at all, they're simply running the old marketenabler script from the g1 forums on boot. that's an easy update :)

c. I did impliment this (it's an easy change to the source code) but I had some framework issues. The next version will be a complete update to the eclair base files as well so I'll look at it again then as well.

d. Sure :) I'll look at it. The spare parts source is pretty basic, so I'll see what I can figure :)

Expect a fairly large update to my build next week sometime.
[Touch CDMA Android Development] TheKartus:
Awesome news about an update. Running this in QVGA and its awesome now that its all setup.
[Touch CDMA Android Development] margosmark:
Hey I am unable to switch keyboard from the HTC one to androids default on,I checked both options in vogue parts is there something else that is needed to be done?

BTW great build
[Touch CDMA Android Development] incubus26jc:
long hold somewhere your wanting to type like a search engine or text and select input method
[Touch CDMA Android Development] margosmark:
Oh sorry I should have mentioned that, yeah all it shows is touch input, which is the htc input, I am running 320X240 v6a, with the update for vogue spare parts
[Touch CDMA Android Development] cp0020:
hey mssmision whats the word on youtube?
[Touch CDMA Android Development] daganb:
Having same problem as your previous version, that is running from Haret / sd card I am unable to get 320x480 resolution working. Running with default.txt set to "set cmdline "ppp.nostart=0 mddi.width=320 mddi.height=480 " everything looks ok in the booting process, then screen is TINY, looking to be running in 640x480 resolution or higher, setting to 240x320 resolution in vogue spare will making it run in 240x320 resolution.

Now if i change my default.txt to "set cmdline "ppp.nostart=0 mddi.width=240 mddi.height=320 " phone boots up in 320x240 then setting to HVGA phone resorts to a lesser resolution making everything offset, huge and ugly.

I really like 480x320 resolution, what am I doing incorrectly?
[Touch CDMA Android Development] cp0020:
whem running 240x320 you need to change your lcd density in the default.txt to 110 or 120. 120 looks better than 110. and in 320x480 your lcd density needs to be at 160
[Touch CDMA Android Development] daganb:
Nope, no dice.

Adding lcd.density=160 to my default.txt when running in 320x480 from haret is still causing android to run in a higher resolution then 320x480, items on screen are much smaller then they should be and games run in 1/4th of a window instead of full screen.

This is a issue I had in msmission's previous version as well. Resolution is messed up when running in haret + 320x480. I believe in the last version I got around this by having default.txt set to 320x480, then setting in spare parts to run in HVGA mode, giving me the same resolution and look as when I was running myn's build from harret in 320x480 mode.
[Touch CDMA Android Development] cp0020:
hhmmmm... thats strange. so youve changed your lcd density to 160 and then went into spare parts and changed to hvga. also if you were running in 240x320 before and you swithed to 320x480 but kept your data.img then it will look messed up. sorry im just tryimg to eliminate all the possibilities.
[Touch CDMA Android Development] daganb:
I totally appreciate it, I enjoy bug testing these things.

I installed v6a with 320x480 from the first run, from the "touch the android to continue" it's been in a resolution that is defiantly higher then 320x480. Haret is booting in 320x480, however when android starts is when it hits the higher resolution. lcddensity does abs nothing from what I have seen. Again this is the same situation that happened on ms's previous build, however I can't boot with a default.txt set to 320x480 and then select HVGA in spare parts to fix this and run in 320x480 anymore, doing that puts it in 320x240 mode now.
[Touch CDMA Android Development] kanakaris1:
mmsison's Eclair v6a

First off props this installs great and seems to be running pretty smoothly.

The one question I have is how to get speaker phone to respond from in-coming calls under this build, it doesn't seem to be working for me.

Also, I have noticed a sync compatibility issue on my windows 7 machines. this morning the phone seemed to totally bug out while in sub debugging mode

Another comment, my hexlauncher two responded once which seemed like it was a resolution that my vogue could not handle, and now the hexlauncher two is not responding at all.

All of these issues are almost non issues since I am just avoiding them in my use.

Let me know if there are any simple resolutions or if anyone is having the same issues.

Thanks
[Touch CDMA Android Development] mssmison:
win 7 and vogue are not adb buddies :)

hexlauncher 2 is for hvga only (320x480)

Spreaker phone is good, press the menu button in call to enable (assuming your on a vogue of course)
[Touch CDMA Android Development] garringm:
I was playing around with this one yesterday while patiently waiting on your sense builds. The only little thing that bugs me is the Launchers granted I really like the hex launchers but I use task killer to keep my system running good and while using them on your builds it kills the Launcher too is this due to what part of the system it is installed to.
[Touch CDMA Android Development] mssmison:
What? task killer doesn't kill apps based on where they are installed to? At least I didn't ever hear of that before. The default eclair launcher is in /system/app so that would fix your issues.

The reason hexlauncher is installed to /data/app is because it's an app on the market so this way you can update it :)