yashsingh1/xdaforums huggingface dataset:
[Touch CDMA General] Giggles 312:
hey i just did this, and now when i boot i get a few cannot find '/system/bin' errors. what happened? i did everything right, but it no worky.
[Touch CDMA General] kr4zyc1d:
New error

Ok, I have been creating a new data file every few days, making some minor changes to some of my things and really just putzing around, but I have come up with a new error, that I only saw today and wasn't sure if anyone else has gotten it, but it only comes up during the boot.

Application Android keyboard (in process com.android.inputmethod.latin) is not responding. I usually hit wait and go about my business, but I wasn't sure if anyone else saw or had this a knew what to do. Thanks everyone.
[Touch CDMA General] Sodbuster:
That is exactly what mine does!

I just haven't been able to read the two point type. But that sure looks like it.

But when I try to reformat my 2 gig microSD card in PocketMechanic, it tells me that 'a device attached to your phone is not working'

Nothing is attached, so. ..
[Touch CDMA General] stiltzkin:
That's probably my fault - I told you to use squashfs-tools from the Ubuntu repositories, when in fact that version (currently 4.0) does not make images that work with Android.

As polyrhythmic noted on the previous page, you have to be using version 3.1, 3.4, or 3.7 for it to work. So remove the Ubuntu package, and download and install squashfs-utils manually.

Sorry for the confusion.
[Touch CDMA General] jamezelle:
yeah i tried to avoid this problem lol:o
[Touch CDMA General] Giggles 312:
lol i got it working. i got squashfs-utils 3.3. i edited the build.prop. and now when im booting the phone it just hangs at the android load screen and keeps looping, kinda like the hero prob. just find it awkward.
[Touch CDMA General] babijoee:
What device are you running? If its a Raphael or Diamond, I made a new thread to tackle the looping/ freeze problem so we can keep this thread clean for vogue users.:cool: http://xdaforums.com/showthread.php?t=601751
[Touch CDMA General] szman22:
I'm getting the same error, but like you, I just hit wait and go about my business.
[Touch CDMA General] berardi:
anyone else have problems with settings force closing?
[Touch CDMA General] stiltzkin:
It happened to me once, but only once and it didn't come back. Is it repetitive for you?
[Touch CDMA General] berardi:
yes. So much that it is prohibitive and I've gone back to Donut :(

Also the whole thing seems laggy and unstable - Don't know why mine is so different. Donut is snappy for me
[Touch CDMA General] skydirt:
Is this OKAY to do? I have not tried because I was under the impression if I did, living in Canada, that NAV will not work for me, even with the new NAV Launcher?

Either or, gmaps works awesome for me until I want to use the NAV, it reads "No route found- Navigation to your destination is not available"

However in normal gmaps I can get directions to my destination and it even tracks me.

Is this the same problem others are having, or is the the error message when trying to use nav outside of the US?
[Touch CDMA General] plemen:
Don't download gmaps from the market if you are in Canada. Best bet is to follow the thread in the dream forum for updated hacked map apk's.
[Touch CDMA General] Pandemic187:
Is it possible to used that hacked APK if I'm using Android via haret?
[Touch CDMA General] polyrhythmic:
Sure, Pandemic187 you can easily install it. Direct download and install through browser, or put it on the SD card and install with Astro, or install over ADB. Make sure install from 'unknown sources' is checked in your Application settings.
[Touch CDMA General] Pandemic187:
Thanks for the suggestion poly, but I tried installing it with Astro and it just said the application was not installed.
[Touch CDMA General] skydirt:
Mind linking me to it? I'm trying to seach for it, but falling short.
[Touch CDMA General] polyrhythmic:
Hmm perhaps it would be better to follow the official instructions from the official thread then :p
[Touch CDMA General] skydirt:
Um the link you posted was for a version of NAV that has these not working

*No arrow indicating next turn direction

*Voice guidance is delayed, if at all present

Would'nt this pretty much make NAV usless anyways?
[Touch CDMA General] polyrhythmic:
You asked for the link. I'm sure they'd like help enabling those features if you have the time, though it is clearly useful to many people regardless.
[Touch CDMA General] skydirt:
Ya, I just read through the thread. It is pretty much usless as people are posting that they make wrong turns etc. cause there is no aroow pointing them the correct way, lol.

Asides from what you linked, doesnt Plemen have a fully working version in his rom? Its donut, but I dont see why it woruld work the same on eclair. I'm gonna find out :)
[Touch CDMA General] stopthebus:
1 question please, what resolution and density are you guys using?

320x428 is a little too small for me.

240x320 is a perfect EXCEPT for the dialer, which is too large and has clipping on top and bottom.

Thanks
[Touch CDMA General] szman22:
Yeah, I got the dialer clipped too. I was OK to live with it, because I prefer that resolution due to its "crispness". 320x428 is too fuzzy.
[Touch CDMA General] zenulator:
240x320 lcd.density=110

This scales the screen a little more than 120 and shows the whole dialer and music player while leaving the crispness of qvga. You can prob do 115 or 118 as welll and see the whole dialer.
[Touch CDMA General] sshark:
When is new build going to come?
[Touch CDMA General] stiltzkin:
Interesting. Well, if you want to replicate exactly what's running on my phone just in case, I'm actually using a different zImage than the recommended one (dzo's latest). I prefer the old keymap, so I'm using "zImage+OldKeymap" from these basefiles. Not sure if it will make any difference, but it might be worth a shot.
[Touch CDMA General] enatefox:
Just so you know, the kernel's keymap is lowest priority. What you set in /system/usr/keylayout will trump any other settings. Personally I like the old keylayout and I will drop them onto the system's folder. That takes priority over anything else and will be the one used.
[Touch CDMA General] cbaty08:
noob question...

I have been searching and cannot for the life of me figure out the new way to switch orientation on this latest build....
[Touch CDMA General] TheKartus:
Hold the menu button down for 2 seconds then release. It should switch.
[Touch CDMA General] cbaty08:
strange, is there a special way? It switched into landscape but I cannot for the life of me get it out now... at least 50 times I have tried the 2-sec. hold and nothing... either the options menu pops up, or my keyboard...

Edit: nm... and thanks!
[Touch CDMA General] plemen:
Turn off automatic orientation in settings.
[Touch CDMA General] kiwilime:
After I boot from haret, my phone goes through the usual (screen with the linux penguin), and afterwards, the screen goes blank with a gray tone.

Can anyone help?
[Touch CDMA General] bchi49:
I have the same problem with map update, I tried the v1.6 image too, same problem.
[Touch CDMA General] stiltzkin:
Ah, good advice! Thanks, I didn't know how to do this...
[Touch CDMA General] stiltzkin:
First check your panel type in default.txt - you will get a gray/white/black screen if it's not set right. Should be 1 for Verizon and 2 or 3 for Sprint or other carriers, as I mentioned before.
[Touch CDMA General] bri3d:
@stiltzkin this will happen before the penguin - if he sees the boot console the panel got powered up properly.

@kiwilime this is normal for this build because it has no bootscreen - wait 5-10 minutes. if you want to see what's going on (or it takes longer or crashes) install adb and run logcat (there are guides available all over on how to do this).
[Touch CDMA General] enatefox:
I have a bootscreen just like ye olde times.
[Touch CDMA General] TheKartus:
I do too. Since I'm not running QVGA
[Touch CDMA General] sshark:
For rotation problems when in landscape mode, open dialer to switch back to portrait mode...easy said easy done
[Touch CDMA General] bchi49:
Here's a solution but...: http://www.google.com/support/forum/p/Google+Mobile/thread?tid=75cc937c841f8bda&hl=en

I wasn't able to remove the files because they were read only... I think because they are on the system.sqsh file which is read only. I also had the same problem when updating Facebook. I think the main problem is because Facebook and Google Map came with the system.sqsh so it couldn't be removed or reinstalled.

I'm not using NAND, would that allow me to modify the system.sqsh files?

I unsquashfs the system.sqsh file and removed the facebook and google map apks, then mksquashfs, but didn't work-- couldn't boot up.

It didn't work even if I don't make any changes and mksquashfs the same file... so I must be doing something wrong. BTW I'm using the mksquashfs and unsquashfs on Max OS 10.6.2

I'm using squashfs 4.0 from http://sourceforge.net/projects/squashfs/files/squashfs/squashfs4.0 could the version be the problem or Mac?
[Touch CDMA General] enatefox:
yes

or ext2 image

yes
[Touch CDMA General] kr4zyc1d:
any word on an update for the system that fixes the sleep issue? I went back to 1.6 because I needed my phone more off of the charger rather than on, but would love to get back into 2.0!!! so sleek!
[Touch CDMA General] jamezelle:
even the dream users are having this issue so... its just a waiting game:rolleyes:
[Touch CDMA General] zenulator:
I'm using donut until i have time to fix it. The plain 2.0.1 SDK image doesn't sleep either.

If anyone wants they can download the 2.0.1 Android-SDK and unyaffs the system image under platforms and drop in the eclair libs in /system/lib and remove a couple files in /system/bin then add our apns.xml then then put eclair.build in /system/ and make an ext2 image and then sqshfs that it will boot just fine. It runs a little better and still has the lock screen. No force closes but the battery still drains faster because it doesn't sleep.
[Touch CDMA General] kr4zyc1d:
no worries, good update thanks. great work zen.
[Touch CDMA General] Giggles 312:
i want to change the lcd.density in the build.prop to 160 so i can flash the 320x428 [or] 320x480 (idk which yet).

i did it before in ubuntu with squash-utils 3.3 and once i repacked the .sqsh file and booted it with my phone i get cant find system/bin/ errors.

did i mess something up or what lemme know.

Here's what i did.

unsquashed the .sqsh file

edited the lcd.density in the build.prop to 160

then repacked the .sqsh
[Touch CDMA General] yes_senpai:
Any news on the sleep issues?
[Touch CDMA General] loserskater:
Go HERE and you'll see this:

for cupcake/donut images

genext2fs -d ./system -b 80000 -a system.ext2

this will make ~80mb ext2 system image.

This system.ext2 is now bootable and you should be able to copy it to your sdcard and run it.

To turn this into a system.sqsh you need to mount it

mkdir tmp/system-ext2-mnt
mount -o loop system.ext2 tmp/system-ext2-mnt

Then make a squashfs image of the mounted directory

mksquashfs tmp/system-ext2-mnt/ system.sqsh
[Touch CDMA General] TheKartus:
Looks like the G1 people have made a lot of progress on 2.0. Does that help us? This thread shouldn't get left behind.
[Touch CDMA General] zenulator:
i'm working on this on and off and have some bugs fixed. fixed keyboard/search fc. added the nexus bootscreen but the sleep issue is still there even in the plain sdk image. i also have a aosp 2.0 build. and maybe by christmas 2.1 flan from the nexus one.
[Touch CDMA General] zenulator:
so except for camera and sleep 2.0.1 is looking very good. i ran it last night for a little it seems that any button press will "wake" the phone. so that could be part of the problem.
[Touch CDMA General] bri3d:
@zenulator I think you might have your cause and effect switched - any keypress wakes the phone because it's not sleeping, not vice versa.

If you intentionally break sleep on an image with working sleep (by holding a wakelock or otherwise), any keypress will reactivate the display as well.
[Touch CDMA General] polyrhythmic:
Hi there Vogue devs, we've been chipping away at the sleep issue as well. I've learned a few new commands to try and 'force' Android to suspend, and Newbie16 has helped narrow down the issue:

[ 1918.049999] android_power_suspend: enter suspend
[ 1918.051417] PM: Syncing filesystems ... done.
[ 1918.089421] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 1918.096499] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 1918.100376] RTC Suspend: Current time=7:46:13
[ 1918.102144] Wake up in 108 seconds
[ 1918.102144] sleep_delay=0
[ 1918.102144] msm_pm_wait_state(80, 0, 0, 0) failed 10929
[ 1918.102144] msm_sleep(): msm_pm_wait_state failed, 10929
[ 1918.102144] RTC Resume: Current time=7:46:13
[ 1918.103599] msmrtc_resume: alarm=1261295281, now=1261295173
[ 1918.122452] Restarting tasks ... done.
[ 1918.249477] android_power_suspend: exit suspend, ret = 0 (2009-12-20 07:46:13.732353325 UTC)
[ 1918.251407] android_power_suspend: pm_suspend returned with no event
[ 1918.292242] ds2746: 4191mV 15mA charge: 100/100 (4509 units)
[ 1918.292271] aux0: 237 (1299) aux1: 16 (70)
[ 1918.399982] android_power_suspend: enter suspend

I've been reading over in the Dream forum but only a few people complain about the sleep issue, most people seem to not care (or aren't having this problem). Does anyone have enough kernel knowledge to guess why the function* is failing for us? My (uneducated) guess is that maybe Eclair doesn't call the function correctly or we're getting something unexpected from the 'state' variable.

*To see the kernel source, visit http://gitorious.org/kaiser-linux/kernel/blobs/master/arch/arm/mach-msm/pm.c line 149
[Touch CDMA General] KERKEDAGAIN:
need any beta byters? i no mind testing the latest..
[Touch CDMA General] zenulator:
I'm looking at just doing a straight port of manup456's build for the dream since it has just about everything working. I'll post it up later tonight if I have time.
[Touch CDMA General] KERKEDAGAIN:
sweeeeeeet
[Touch CDMA General] mssmison:
The two things I would suggest would be to check cyanogens git for his kernel as well as the anroid msm kernel and find the required changes.

http://github.com/android/kernel_msm

http://github.com/cyanogen/cm-kernel
[Touch CDMA General] zenulator:
OK I uploaded a new build. There are no force closes on start and it has the Nexus One bootanimation (even in qvga). I removed a lot of apps and put them in a separate package so you can pick and chose what you want installed. It comes with a rootfs.img that I use to boot from windows mobile through haret. I also uploaded a seperate standard rootfs.img for nand/sdcard partitions/haret boot with adjusted memfree values.
[Touch CDMA General] babijoee:
hi, whenever i try to modify and save a new sqsh image it always loops or crashes. Can you please let me know what i'm doing wrong.

Note: I have already tried just straight unsquashfs and edit files the mksquashfs like you mentioned awhile ago but that still seems to loop.

here are the steps i taken.

-sudo unsquashfs system.sqsh

-added new apps to app folder.

-sudo mv ./squashfs-root ./system

-sudo genext2fs -d ./system -b 100000 system.ext2 (I'm not sure what value i should be using. Perhaps this may be the problem.)

-mkdir ext2mount

sudo mount -o loop ./system.ext2 ./ext2mount

-sudo mksquashfs ./ext2mount system2.sqsh

put on sd and rename to system.sqsh
[Touch CDMA General] myn:
Something is definitely going on with the market. When I search for popular apps, like say facebook or google docs I get no search results, with xRom none the less.
[Touch CDMA General] myn:
Really?

I never noticed Google navigation in any of donut roms.

http://www.engadget.com/2009/10/28/google-navigation-video-hands-on-you-want-this/
[Touch CDMA General] zenulator:
thats motorola's app. it just interfaces with google maps. i have the apk if you want but it's no good without gps working.
[Touch CDMA General] jamezelle:
im sure you have, but i have to ask, have you tried the app in cupcake?:D
[Touch CDMA General] mattcoz:
Nope, it's Google's, available for any Android 2.0 phone.
[Touch CDMA General] katmandu421:
+1, Here is a video from google, nothing to do with Verizon or Motorola

http://phandroid.com/2009/10/28/google-maps-navigation-announced-video-demos/
[Touch CDMA General] myn:
Anyone tested the new Google Navigation in cupcake or donut?

Is an APK available?
[Touch CDMA General] garringm:
I greatly appreciated the work that all developers did even if it wassn't for my phone model, but I feel it must be said, yes this is the vogue thread and I'm sure if there were anyone over on the kaiser threads doing any real developement to the code then most of us wouldnt even be over here chiming in.I haven't seen enate or pmos pipe up for quite some time now. I gave up a 3day old iphone because I seen hope in the android for my ATT phone but its just small snide comments like this that really do kill it for a lot of people. You want people to get more interested in Android thats not the way to do it, this is a community of xda-developers at least thats the website I log into every day not vogue-developers, or

kaiser-developers. I do understand that there are a lot of BS post and most of you may see this as one of them, so be it. After more than a year of being involved with this I do believe I will be calling it quits with the entire android movement. I here those guys over at maemo are doing wonderful things in open source. November's the month it all happens too. C-ya
[Touch CDMA General] zenulator:
All I have to say that this is a vogue thread. I don't mind kaiser users posting but it gets confusing to vogue users when you have page after page about no data in kaiser and people start to think that there is no data in the donut builds on vogue. I think that something like that should be resolved in the kaiser threads. Also there nothing stopping kaiser users from starting their own donut thread in their own forum. I didn't create donut. I just get the system image together to make it work on the vogue which in turn runs on kaiser/polaris/nike. I'm good friends with a couple kaiser users and I'm not trying to make a divide or push them out of development. I personally asked pmos and kb7sqi if they had problems but they have been busy. So it's not like I don't want to see working kaiser builds.

If kaiser users get 2.0 fully working and start their own thread about it and we go over and invade with bugs specific to our phones thats cool right because its xda-developers not kaiser developers. But if you want to leave android development over the fact that we'd like to keep the threads on the topic of vogue in the vogue sub forum then go for it. Maemo looks pretty sweet.

This is just my view. I spend more time at this than I should.
[Touch CDMA General] tallnerd1985:
Just Got To Play With The Motorola Droid All Day Long Today!!

I would say the least that I have been very happy with Vogue-Android since the day DZO implemented GPU acceleration because it seemed to me that my phone was a lot more responsive and snappier than the stock G1. I tried the Sprint flavor the HTC Hero when it first launch and wasn't all that impressed, it still had the lag issues that our phones had but not as bad. Today, when I popped into worked, low and behold, a fully activated Motorola Droid was sitting at my desk.

Should I Check The Office To See If Anybody Was Messing With Me?

When I got to my desk, I see what appears to be the Motorola Droid sitting in the multimedia dock. As I am sitting there looking at it in amazement, I think to myself, is my coworkers playing a practical joke on me by setting up a dummy model in the dock so that I get excited for no reason. I cautiously reach for the phone, and as I reach for the phone...............................IT STARTS FLICKERING AND RINGING!!!!!

Holy Cow!!! Its A Live Phone!!

To Be Continued......
[Touch CDMA General] jamezelle:
howzabout a system dump!:D
[Touch CDMA General] zenulator:
I might have to go get a job with you then..
[Touch CDMA General] tallnerd1985:
Well, Big Red is always hiring especially in my neck of the woods.
[Touch CDMA General] zenulator:
So how was the droid?
[Touch CDMA General] tallnerd1985:
Part 2

So Now The Phone Is Ringing???

So now I am shocked in amazement that their is an actual live droid in my presence on my desk. When I looked down to see the caller ID, it shows my boss's name and picture on the the gorgeous huge screen. I pick up the phone, being slightly heavy and all, and answer the call to find the audio is crystal clear and no distortion out of my boss's voice. I start talking to him asking whats going on with this phone and out of nowhere, he pounces on my back and scares the living **** out of me!!

Why Is There A Droid On My Desk??

After regaining my composure, I ask my boss how in the hell is there a live Droid on my desk?? He looks at me and says that he knows my deep, dark obession with Android and how I used to claim that it was going to knock the pants off the iPhone and Crapberries. So he figured that if anybody gets the right to play with the Droid for a day, that it should be me.

One Stipulation Thou

He says that I can play with it as much as I want but it has to stay in the back office at all times and none of the other employees can touch it since its logged in my name. As disheartened I may be, to hell with it, I am first one in the area that gets to exclusivley play with the Droid all day even thou I cant show it off to anybody besides my coworkers.

This Thing Is Fast As Bill Clintion Denying A BJ From His Secretary The First Time

To Be Continued.....
[Touch CDMA General] KERKEDAGAIN:
dump it! dump it!!
[Touch CDMA General] tallnerd1985:
There is already a dump on the dream forums
[Touch CDMA General] KERKEDAGAIN:
but of course..m'scuzi
[Touch CDMA General] zenulator:
That dump in the dream thread is old. It's from a umts test build. I'm sure we'll see a new one soon.
[Touch CDMA General] tallnerd1985:
Part 3 Finale

This Thing Is Fast...

Like I said before, my vogue-android phone compared to an actual G1 stock runs alot faster and smoother but nothing compared to The Droid besides one little thing. Everything from opening an app, zooming in and out of google maps, surfing with the web browser runs super smoothly and opens in one second. The only thing that disturbs me is the homescreen when moving across the desktop kind of lags and stutters a bit but I am guessing thats because of the high resolution screen and the new 2.0 OS.

It Feels Rock Solid In My Hands

The weight and feel of the phone is incredible. I can tell that this phone is top knotch and the build quality is second to none. I like that the slideout keyboard is not spring loaded and that you have to pull the keyboard out because from past experiences with slider phones is that the slider mechanism always breaks. The screen is georgeously clear and brilliant but the auto-dimming sensor can be annoying at times but thats why I turned it off. Lastly, with the compacitive screen, using the onscreen keyboard and rolling thru the menus is exact and precise.

Now For The Only Bad Part

As far as everything goes, the phone is great besides the marketplace with the new 2.0 OS. I downloaded a variety of apps to play around with to see how the phone handles them but soon came to be horified by some of the experiences. It seems to me that Google hasnt fixed the marketplace to filter out incompatible apps because a lot of the apps I downloaded gave me a lot of force closes or didnt function right like the Reality Browser 2.0 and how it interfaced with the camera because it was inverted and distorted. Hopefully they will fix that before the phone launches to ensure a smooth start on America's superior network.

Other than that, I love the phone and cant wait to pickup my personal one when it launches. Happy Halloween and thanks for all the hardwork from the developers and the community here.
[Touch CDMA General] soundmind:
I Love the new build, but i cant seem to get the keyboard in english ive changed the language under settings but its not changing.