yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] -Arturo-:
Well, something went completely wrong after voice input stopped working I restarted the device by poking the "hole"(can wy use that method to restart Android?)

And when the system loaded it displayed a screen saying "System UIDs Inconsistent, UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable" with a button to press saying "I'm Felling Lucky". So I don't know looks like my data is corrupted and that might have been the reason why voice input didn't work. I'm wiping data at the moment and see if VI works on clean system.

Edit

Ok, Kalt Voice Input gave me two popups saying "Couldn't connect" but the third time it worked so i guess it's ok now.

Btw Market patch works great.
[Touch CDMA Android Development] incubus26jc:
very nice job. Are you going to push the changes for this today?

edit: neverind i read that you did. sorry
[Touch CDMA Android Development] samjam:
Thanks kk; that Full Market fix works nice for me; I got back my donut-install applications.
[Touch CDMA Android Development] graouxx:
Problem for me after update.

Android says "Market is not installed"

What i did :

- put androidupdate in andboot in sd card

- restart phone and launch update

- fix permission

- start android

Something wrong ?
[Touch CDMA Android Development] xport:
Same here "application is not installed on your phone"...I'm using (Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS9] [7/5/10] Custom DarkStar Theme), maybe because this version is odexed and his is not?
[Touch CDMA Android Development] graouxx:
This one doesnt work on pola100. (freez on boot)

But this one work : http://xdaforums.com/showpost.php?p=7079594&postcount=299

Maybe i need to make new install ?
[Touch CDMA Android Development] samjam:
Kaiser hangs

Sometimes my kaiser just hangs - such that I pull out the charging cable and the charging light stays on - the off key doesn't work and I have to do a reset - in fact just now it has turned on and is now hanging at the point it should be painting the launcher icons.

I'm not sure if the hang is permenant.

Also (and perhaps as a result of the reset button) at boot I see a brief message something like this:

Can't mount /data/sysfiles/su on /system/bin/su too many levels of symbolic links.

(delay)

I've since re-installed the root fs and market update and don't get that error.
[Touch CDMA Android Development] graouxx:
In my case, I have DZO all language last version

(and nbh from post 299)
[Touch CDMA Android Development] incubus26jc:
here is a nonodexed version of the market fix from kallt_kaffe

http://androidhtc.git.sourceforge.n...b;hb=2d7082baa6e6a2c10bda493ede11d71a6bb0cfe1
[Touch CDMA Android Development] golfnz34me:
Like another poster here I can't get any of DZO's latest kernels to work. The phone goes to a back-lit black screen and hangs there forever. This is on a XV6900 (Vogue) running HaRet.

I saw some posts earlier about the Vogue needing cmdline params with the newer kernels, is that true? and if so, what are the params?

Mike
[Touch CDMA Android Development] graouxx:
system says "unable to install application"

Same thing if i try to launch /system/app/vending.apk

Edit : i make an androidupdate.tar with previous vending.apk, seems to work
[Touch CDMA Android Development] myn:
NICE WORK!!!

Thanks
[Touch CDMA Android Development] Murrky:
On my Pola100 it works good without reinstalling (Dzo release 15).
[Touch CDMA Android Development] TheKartus:
Was that on 7-6? or have you tried 7-7? I have yet to see if 7-7 fixes the issue.

If it does involve more, is there no way to put it in the kernal? I don't even have abd setup. :(
[Touch CDMA Android Development] bcti:
When I had this problem I had to use a zimage file dated july 2nd 2010 from one of the eclair builds.
[Touch CDMA Android Development] thoughtlesskyle:
when i had that problem i had used a NBH editor to try to change my resolution
[Touch CDMA Android Development] golfnz34me:
It was an issue with the 7-7 kernel as well. The 7-2 kernel was the last one that worked.

Mike
[Touch CDMA Android Development] TheKartus:
Right. I'll put off trying a new one till one past 7-7 is out.
[Touch CDMA Android Development] mrkite38:
Had you edited the new '+11 MB RAM' kernel? k_k had said it probably wouldn't run 320x480 due to the extra memory it requires. that is, dzo shaved memory out of the video driver - so you may not be able to run in a higher res than 240x320.
[Touch CDMA Android Development] samjam:
WIFI Works fine for me.

I'm using kk's latest kernel and froyo image with the market update.

I've seen some posts about setting wifi power via a shell script but I can't find reference to them right now - maybe thats what you need.
[Touch CDMA Android Development] golfnz34me:
I've just flashed DZO's latest Vogue 320x240 NBH and installed his latest Froyo to NAND, and it worked just fine.

It looks like the post 7-2 kernels work for NAND, but not HaRet.

Mike
[Touch CDMA Android Development] derringdo:
Having this exact problem with the 7-7 zImage
[Touch CDMA Android Development] dzo:
Can you try an 8-7 kernel, for haret you will need to specify RAMSIZE as 0x7300000. For resolutions other than 320x240 try a RAMSIZE of 0x7100000. No need for the pmem parameters now, they are calculated from the ramsize.

note: vogue only.
[Touch CDMA Android Development] mnjm9b:
what do we need to do to get this working for kaiser?
[Touch CDMA Android Development] dzo:
I've put two new systems here:

http://sourceforge.net/projects/androidhtc/files/

These are odexed and unodexed european language systems with all the changes from the last few days, i.e. better gmail and market.

I haven't tested these at all, let me know if anything is broken.
[Touch CDMA Android Development] dadevil666:
just tried this on my kaiser and whoa it's very fast i've got a good feeling about the new froyo :)
[Touch CDMA Android Development] god9980:
COME ON MAN.So you fix the audio.非常感谢，期待你的android2.2:)
[Touch CDMA Android Development] dzo:
OK, I'll post an image with working audio later today.
[Touch CDMA Android Development] incubus26jc:
very nice work dzo. Great job!!
[Touch CDMA Android Development] TheKartus:
Awesome. I'll give this a run when that comes up.
[Touch CDMA Android Development] jadenj5:
i really want to try this but i think my phones about had it so im really hesitant on flashing anything i might flash once every two months.... sooo is there anyway this can be sized to fit 240x320
[Touch CDMA Android Development] thoughtlesskyle:
what else won't be working once we have audio?

just bluetooth and camera?
[Touch CDMA Android Development] dlepage:
I just commited my libcamera changes to sourceforge.

From what I can see, CameraHardwareInterface hasn't changed between Eclair & Froyo so if we're lucking, a rebuild of libcamera against Froyo should be all that is required.
[Touch CDMA Android Development] BottleB:
Whaaa??? Working and usable Froyo for my vogue today?!!!!
[Touch CDMA Android Development] thoughtlesskyle:
haha dlepage you came out of nowhere man you rule

im excited to use this
[Touch CDMA Android Development] TheKartus:
Think its the same with bluetooth?
[Touch CDMA Android Development] jadenj5:
do i install just like everything else
[Touch CDMA Android Development] grktaurus83:
Copied this from my post in Myn's Warm Donut thread, but I figured it'd be worth a chuckle.

"From what people have said on Froyo's performance, it sounds like Froyo will be to Eclair what Windows 7 was to Vista (ultimately same functionality with improved performance)."
[Touch CDMA Android Development] dzo:
Thanks, I made a new branch for Froyo and it compiles (after a few changes) but doesnt work yet. Since the fake camera for the emulator doesn't work either, it may not be our fault.

I've also made froyo branches for audio and lights on the sourceforge git repo since these needed some changes.

I'll try to get the sdcard mounting properly and then post an image.
[Touch CDMA Android Development] BottleB:
Dzo, should we expect this tonight? If so, ill keep f5'ing till its there!
[Touch CDMA Android Development] dzo:
Here it is:

http://sourceforge.net/projects/androidhtc/files/system-froyo-28-06-10.tgz/download

There's still lots broken with this but audio output works, the the leds work and the gpu works.

Not Working:

bluetooth

audio input

gps

gallery works first time it starts but you have to kill it to get it to use the gpu after this.

Enjoy.
[Touch CDMA Android Development] BottleB:
UBER. ..I'm flashing as soon as my gf goes to bed!

You rock the **** outta my Vogue!
[Touch CDMA Android Development] BottleB:
Oh, before i flash i remember seeing that i have to flash 320x240? thats the same as 240x320 right?
[Touch CDMA Android Development] jadenj5:
do i have to rename it to android install??
[Touch CDMA Android Development] god9980:
Thank you very much dzo, you are a god
[Touch CDMA Android Development] PulseFate:
Hey dzo, I was just wondering what european languages are included (as in all, or just the main ones)?

I'm not requesting or anything, but I have a English-Greek Dictionary and when i last tested it, whichever build i was using could not display Greek characters.

EDIT: Gmail is fixed and no longer has headers (or whatever you call it) with large font

I have never had a problem with the market so I don't know what the fix was for (or did you add apps?).
[Touch CDMA Android Development] dzo:
The eu languages are:

en_US en_GB fr_FR it_IT de_DE es_ES

The full languages are:

en_US en_GB fr_FR it_IT es_ES es_US de_DE nl_NL cs_CZ pl_PL zh_TW zh_CN ru_RU ko_KR nb_NO pt_PT pt_BR da_DK el_GR sv_SE tr_TR ja_JP

So I guess you need full for greek (el_GR).
[Touch CDMA Android Development] incubus26jc:
im getting force close with keayboard with latest eu unodex system and nbh 240x320. Woeked fine until i flashed 7-8 nbh

EDIT: nevermind, another reboot fixed it
[Touch CDMA Android Development] derringdo:
Tried the new 8-7 froyo kernel with the RAMSIZE you suggested and it works again! What was preventing it from booting?
[Touch CDMA Android Development] gotrandom:
Is there anything new between 6-7 and 8-7 aside from the languages? Or if I'm just using english anyway should I not use this update. (sorry if this is a newb question... I very recently got into all of this. Been using stock until a week ago.
[Touch CDMA Android Development] ws1088:
Hi Dzo, Can you build one for all language at least? Thanks!!!
[Touch CDMA Android Development] mnjm9b:
did you even click on the link???

its there....and surprise surprise it's called 'system-froyo-all-languages-06-07-10_15.tgz'
[Touch CDMA Android Development] blindguyinanorgy:
look here...you can see all of the changes between any update. device-voguge for OS kernal for kernal
[Touch CDMA Android Development] bangout:
First wanna say great build as usual. But ever since ive been using froyo I can only read things from my sd card thru astro, besides that nothing. Any ideas? Running latest build on vogue nand. I've searched, rebooted,wiped data ,fix permissions and haven't found any answers. Thanx

P.s. dev tools seems to scan card but still nothing
[Touch CDMA Android Development] ws1088:
Dzo put an update system dated 08-07-10. With gmail fix and market fix, fyi. 06-07-10-all-language does not. thanks!!
[Touch CDMA Android Development] gotrandom:
Thanks I really appreciate that, everyone here is so helpful and hard working, I really appreciate everything that everyone is doing to make our phones more and more useful and fun to use.
[Touch CDMA Android Development] milanche:
A general question regarding Froyo. Before Froyo was out there was a lot of talk about built in feature for Wifi Tethering - among JIT most anticipated feature I'd say. If I recall correctly this feature was also demonstrated by Google at Froyo initial presentation.

But it seems that out builds lack this feature? I know Vogue has no Wifi, but Kaiser devices do have it..
[Touch CDMA Android Development] dzo:
I just put an unodexed full language version of the latest build on sf.

Unless you need the extra languages, there's no point installing this one.
[Touch CDMA Android Development] TheKartus:
I changed the ramsize setting and 7-7 and 7-8 both failed to load. It is working with 7-2 though, and it seems to have the extra memory also.
[Touch CDMA Android Development] golfnz34me:
Ditto for me.
[Touch CDMA Android Development] osilvan:
Hope dzo read this. I have made a list of things that I think are not working in polaris (pola100) in order to help devs to figure out about those issues and missing features:

usb tethering

wired headset

camcorder

front camera

camera on-screen buttons (zoom, white balance)

digital compass

stability (hang-ups) with last kernels

Thanks
[Touch CDMA Android Development] Rosered:
hello maybe this is a stupid question i'f a kais130 and what is the best kernel for it

Sorry I'm legally blond
[Touch CDMA Android Development] derringdo:
Currently using the 7-8 kernel with the new ramsize and it's working fine for me. How do I check how much free ram I have?
[Touch CDMA Android Development] mnjm9b:
terminal> then type 'free'
[Touch CDMA Android Development] derringdo:
Running into a strange problem where I can't install anything from the market. I keep getting an error saying I don't have enough space, when in fact I've barely installed anything at all. Anyone else experiencing this?

Edit: I'd like to confirm, should the RAMSIZE be 0x7300000 or 0x73000000 for vogue?
[Touch CDMA Android Development] TheKartus:
I think its supposed to have 5 zeros.
[Touch CDMA Android Development] Tuvix:
Hi!

I'm new to this, but i have a problem with the newest system-froyo-full-unodex-08-07-10_18.tgz (want to have german language files)

i can't install google maps or astro file manager. it downloads, then tries to install and then says that the installation failed. anyone else got that problem?
[Touch CDMA Android Development] loserskater:
It's supposed to be 0x07300000 for a total of 8 numbers after the x.
[Touch CDMA Android Development] ben.kank:
Market Fix

Even with the latest fixes the market still doesn't show all the apps I need. The Forward Locking mechanism appears to be interfering with updates and installs in some instances. While trolling through the nexus one threads I noticed this post on how to fix it. http://xdaforums.com/showthread.php?t=687371 The build.prop included with the fix when applied does fix market but as one would expect it screws up other things namely the resolution of the screen. After clumsily navigating around it did allow me to get my apps installed. Then I simply put my old build.prop back. I am not suggesting anybody try this unless their desperate or a glutton for punishment but perhaps dzo could integrate this fix into the next build.
[Touch CDMA Android Development] kallt_kaffe:
:) I was just about to suggest this myself. All you need to do is to replace the fingerprint in build.prop with these lines (and it won't mess up anything else like it will if you just replace the whole build.prop with one made for a Nexus):

ro.build.description=passion-user 2.1-update1 ERE27 24178 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys

That will make it identify itself as Eclair to the Market and I suppose the missing apps that now can be seen has not been flagged as Froyo compatible in the Market or something like that.

I needed to do this to be able to download a banking app for the bank I use here in Sweden.

I don't think it would harm to identify as Eclair until the Market becomes more up-to-date with Froyo. On the other hand it's easy to make it an optional update instead and keep the build more a proper Froyo.
[Touch CDMA Android Development] manu33xtro:
How to pair with audio car ?

Hi DZo and all,

First : thank you for the latest build, I use the European for French language and I love it !! It's the better than better...

But Just one thing missing for me : to pair with my audio car with BT because I'm out of my home a lot of time for my work and a lot of time in my car... The problem is that I can't heard any sounds, just a breath... I can see my phone without problem, compose a phone number for example but when I try to call my answering machine, I hear nothing...

cheers.
[Touch CDMA Android Development] dzo:
The "container error" happens if you don't have "unknown sources" ticked in settings..applications.
[Touch CDMA Android Development] dwardu:
I just bought this phone to develop some windows mobile programs for the imagine cup 2010 but now you gave me a reason not to sell this phone :D
[Touch CDMA Android Development] aruna1975:
Wifi and bluetooth does not work me

Wifi and bluetooth does not work me, otherwise build is fast
[Touch CDMA Android Development] grktaurus83:
Here's a bug I found with the dialer (currently in incubus' RLS 10 but not sure if other releases were affected).

If you go into your call log, scroll down to a name you want using the d-pad, and hit the send button, that isn't necessarily the number that is dialed. I've tried to figure out the pattern, but it's not really consistent. It looks like there is some sort of indexing bug in the call log.

Anyone else see this? I installed RLS 10 and always wipe data. I might try installing again from scratch sometime later to see if this fixes it.

Furthermore, there's an issue with the contact information screen (and various other places in the dialer app). Normally, when you open up a contact's information screen and hit the send button (without highlighting any options), it will dial the contact's default phone number. Usually the default is the mobile number, but some builds had the default number set to "the first number in the list" and auto-sorted the numbers so that the home phone number was first (which was kind of annoying).

However, the send button currently does none of those and reverts back to the call log. It's as if Android is intercepting the send key before the contact information screen gets it, and Android interprets the send key action as if it is meant to bring up the call log (as it normally does in the general Android environment).

dzo, is this due to the hack you used to have Android to keep the dialer app in memory?

I figured I'd post this first since I don't have the time right now to install from scratch and test it all out again. If other people see it, then it might be a real issue. However, if it's just me, then a reinstall should probably fix it.

Let me know if any of you see these issues.
[Touch CDMA Android Development] apurvjawle:
Thanks dzo and K_k

I am using the latest odexed eu version and its super fast and stable as well...awesome work!!
[Touch CDMA Android Development] kallt_kaffe:
FYI: I think I could make simple script to allow switching fingerprints easily. I'll give it a try and push the results when I'm done. I suppose there may allready be some Froyo-only apps in the market so we may want to be able to switch back to access them.

EDIT: The attached androidupdate adds the script /system/bin/market.sh (which has also been pushed to the repo)

Instructions:

$ su

# market.sh eclair

<restart phone>

To change back:

$ su

# market.sh froyo

<restart phone>

To enable paid apps:

$ su

# market.sh paid

<start market>
[Touch CDMA Android Development] zennehoy:
Hi,

after trying out this amazing succession of builds with haret for a few days, today I decided to take the plunge and eradicated WinMo by flashing Froyo to NAND on my Kaiser. Runs perfectly, so thanks for your great work! (Though I haven't noticed much difference in performance compared to running from SD)

One thing that bothers me somewhat is the low amount of memory that is available - free tells me that I'm using over 100MB, with around 3-4MB free. And this directly after a reboot. Under WinMo I consistently had around 80-90MB free, almost making me thing that the free and used column labels of free are reversed...

Anybody have an explanation for this, or as to what might be hogging all that memory?

Thanks!

Zen
[Touch CDMA Android Development] kallt_kaffe:
Don't worry. Linux uses the free memory for caching. You'll get similar results on a linux PC aswell (unless it runs some old pre-historic kernel)

Also Android will keep closed apps in memory until the memory is needed. You'll notice that sometimes when the time it takes to start an app can differ enough to be noticable. If it has been thrown out of memory it will take a longer time to start.

There are taskkilling apps in the Market that can both give you a better number of the real free memory and also allow you thrown apps out of memory manually.
[Touch CDMA Android Development] polecat409:
Will this fix the Market issues I'm having with "Download was unsuccessful" for everything I try to download? Actually, I did get Astro to download AND install after four tries. That's been my only good download.

When I had "Incubus26Jc's Super FroYo RLS10 Themed" or the ODEXED version of DZO's, my downloads would fail immediately after the file transfer started. With DZO's UNODEXED it would download the file completely before telling me that the download was unsuccessful.

I've cleared data between every install of Android and I don't know why I seem to be the only one who can't download AND install anything from the market...:confused:

HTC Vogue

voguimg-240x320-froyo-08-07-10.nbh

system-froyo-full-unodex-08-07-10_18.tgz
[Touch CDMA Android Development] kallt_kaffe:
No, it will only affect the number of avialable apps. Sounds more like you have transfer problems try the following:

$ su

# gprsclass.sh 10

# hsxpa.sh 1

<restart phone>

If it still fails try:

$ su

# gprsclass.sh 12

# hsxpa.sh 2

<restart phone>
[Touch CDMA Android Development] polecat409:
My terminal won't allow me to type any numerals. This also happened when I was running your most excellent "VaniljEclair RLS7c" - which would let me download from the market, along with Myns Warm Donut.
[Touch CDMA Android Development] mrkite38:
search for 'better terminal emulator'. There's a free version, should work.
[Touch CDMA Android Development] polecat409:
I installed the apk with Astro since Market won't install anything... and it force-closes when I run it.

I've gone back to Myns Donut until this gets sorted-out. I've tried three different FroYo nbh's with three different FroYo builds (odexed and non-odexed) and none of them will play nice with the Market.

VaniljEclair RLS7c and Myns Donut are the only builds I can get to work with the Market.

I love the speed and features of Froyo...but I need the Market.
[Touch CDMA Android Development] mnjm9b:
the market problem in froyo has been fixed....

try using search.
[Touch CDMA Android Development] polecat409:
So there's a downloadable build with the fixed market?

I'd like to try some of the fixes that are in this forum, but for some reason I can't type NUMBERS in the Terminal Emulator while using FroYo.

It seems I'm not the only one "not getting it." Fresh FroYo install, log in to Google and sync, go to Market, all installs unsuccessful. Is anyone else seeing this and fixing it?
[Touch CDMA Android Development] mrkite38:
There's a downloadable build with a fix for a limited number of apps showing up in the market, that's what he was referring to. Where'd you get the bettertem apk?
[Touch CDMA Android Development] polecat409:
Free version:

http://handheld.softpedia.com/get/System-Utilities/Enhancements/Better-Terminal-Emulator-Magic-84558.shtml

Sorry, I must have missed the Market fix update... I'll do another search.
[Touch CDMA Android Development] dzo:
Try enabling unknown sources in settings..applications.
[Touch CDMA Android Development] polecat409:
I've done that also. Maybe there's something wrong with my phone.

Cherry install of DZO's latest FroYo nbh and EITHER odexed/non-odexed from 08-07-10, Market will fail to install any app 90% of the time. If I go back to Eclair or Donut, all is fine.

And my number keys don't work in Terminal Emulator in FroYo only. Better Term and Dev Tools term both don't display numbers when typed. They work in those same apps when running Eclair and Donut.