yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] kallt_kaffe:
Try the attached update. I adds the following lines to build.prop:

ro.telephony.default_network=0

ro.ril.gprsclass=12

ro.ril.hsxpa=2

And that is the default settings in VaniljEclair RLS7c
[Touch CDMA Android Development] kallt_kaffe:
I've seen others complain about this too... I've had no problems entering numbers in any build I've tried or in any terminal I've tried. What device do you have? Vogue, Kaiser or Polaris? Have you changed from the default language to something else?
[Touch CDMA Android Development] mrkite38:
I've had this issue, Vogue, english. I've tried different keyboards, no luck. In fact, I just tried - I still have it with the dev tools term (blue background, tiny text.) Can't find the other one. Better term works, though.
[Touch CDMA Android Development] TheKartus:
Wrong thread
[Touch CDMA Android Development] incubus26jc:
someone said clear devalk fixed it for them. Its because you now have 2 launcher pro's in data because i forgot to rename the launcher the same name so it didnt overwrite the other one from release 9. Clearing data would fix it. Also removing the new one from the tar before installing would fix it.
[Touch CDMA Android Development] xport:
Had it happen to me today out of the blue, rebooted phone and FC for launcher. Clearing dalvik cache fix it for me.
[Touch CDMA Android Development] polecat409:
Will try when I get home from camping. I think this will work. Thank you!!

Sent from my HTC Touch/Myn's Warm Donut
[Touch CDMA Android Development] dpkform:
crash and reboot after bluetooth voice dial

I'm very pleased to have bluetooth phone and media audio working. As mentioned in more detail in a different thread I made, I am having some issues with bluetooth voice dialing.

It will work once or twice, and the bluetooth voice dialer screen hangs or sometimes the phone reboots itself. Once it hangs none of the voice input functions will work anymore.

The spontaneous reboot sometimes hangs on the animation screen i.e. it never finishes booting even after 10 min. when I manually reboot again, the boot takes less than a minute

using your latest full non-odexed on nand, with july 8 froyo 240x320 NBH
[Touch CDMA Android Development] samjam:
Google Shopper FC's

Google shopper update (that uses the camera flash) has started closing when it enables the camera.

I'm guessing that the phone capabilities file that has been tweaked to show all apps is boasting about having a light (to use as a flash) and that shopping fails when the light is not there.

This is purely guesswork, but shopping before it's update that supported the light worked fine. (That is to say it didn't crash although it never recognized the product behind any barcode I scanned).
[Touch CDMA Android Development] SuperJMN:
Audio in console emulators

I'm almost sure that there's an issue with the audio output in emulators like Nesoid, Gensoid, Snesoid, etc.

Although games run better than ever before, the audio is choppy, like if it had a really short sound buffer playing. Can somebody confirm it? The Gameboy emulator GBCoid must run every game in realtime, so the sound should be OK. It it's not, then there's a problem.

This happens with the .NBH compiled by Kallt_Kaffe for Polaris on 7/7/2010, but it's likely to happen in newer files.
[Touch CDMA Android Development] JRoque:
Hi. Thanks for the build. I can't get WiFi to work on my Kaiser (8900). The radio does turn on and the LED blinks, but there's no connection made. The same phone boots Windows and connect fine. I've tried the radio power levels as suggestion on this thread. I'm suspecting my radio firmware and was wondering what others use. My radio is at: 1.71.09.1 which is the latest I could find.

Thanks,

JR
[Touch CDMA Android Development] dzo:
Today I had my phone crash just like people have been reporting. I managed to get a logcat and it was the dalvik vm that crashed, the kernel was fine.

I think it's the jit compiler that's the problem, since it wasn't developed for our CPU. I've just put 2 new builds on sourceforge with the jit disabled (eu, odexed and unodexed).

Hopefully this will be the solution.

I don't see any drop in performance without the jit, linpack is not representative of what we do with our phones so don't worry about that. When the jit is running better on armv6 I'll enable it again.
[Touch CDMA Android Development] kallt_kaffe:
Here's a QVGA adjusted version of this modified phone app. Seems to be the one used in CyanogenMod and it allows you to force Touch UI (among other things).

The odex:ed version may only work for the eu 08-07-10_12 build but I could make a new one once I've installed dzo's latest build (the non-jit one).

BUT, the big question is this (three alternatives) what to do next?

1. Leave original Phone app in the build as it is.

2. Force Touch UI in the original Phone app but leave everything else as it is. (I think I got this one figured out but compiling the build on my machine is painfully slow so I haven't tried it yet)

3. Replace the original phone app in th build with this one.

EDIT: Added odex version for the latest build.
[Touch CDMA Android Development] kallt_kaffe:
Just some notes on the new build regarding compcache.

1.It has the new compcache modules that I compiled which is good but it will expect the patches I pushed for the kernel to be present so a kernel later than the ones currently available is needed. Not sure what happens if you try to enable it without the patches.

2. It does not include the latest compcache.sh with a 120 second delay before enabling compcache so it will cause SD-card detection problems if enabled.

So basicly, for now, avoid compcache. It will work fine (hopefully) in the next build and with a later kernel.

If you know what you are doing you can compile a new kernel and insert the delay in the script.
[Touch CDMA Android Development] kallt_kaffe:
On the same subject... Here's the alternative 2, original phone with touch ui forced onto it (and no way to turn it off)

I'm going to push this one to the repo but I hope we can get a discussion going about our three alternatives.

For those who do not know what Touch UI is heres a screen shot of the default drawer keypad and the touch UI.
[Touch CDMA Android Development] scooter1556:
K_K, how are you getting on with swap?? I don't use compcache because i felt a swap partition on an class 6 SD card gave more benefit and a noticable speed improvement, especially with a swappiness of 60. I found compcache messed up too much because of it's complexity and 25% RAM is a lot to take away. I noticed the benefit for a few hours but once a few apps have been opened and closed i found the phone started to slow down whereas with swap i don't get this.
[Touch CDMA Android Development] kallt_kaffe:
I didn't run with swap for very long but with our limited memory I wouldn't be surprised if is the most effective alternative. Also according to this wiki other seem to share your experience.

However partitioning SD-cards aren't something that Average Joe is capable of so compcache can be an alternative.

The thing that you experienced btw may be related to the "swap free notify" not being supported in our kernel, or least it wasn't supported untill I added support for it.

On this page you can read this:

The page is actually about compcache 0.6.2 and we are stuck with 0.5.4 due to our older kernel version but a similar patch exist for 0.5.4 and I've added it to our kernel source and the new compcache modules in the latest Froyo build are compiled with support for it.

So maybe it works better now?
[Touch CDMA Android Development] kallt_kaffe:
New kernels

Here's some new 240x320 Froyo kernels (with support for the new compcache modules in the latest Froyo release) and an compcache.sh update that adds the 2 minute delay before adding compcache.

The kernels also have an updated initrd.gz (also attached to be used by HaRET users). The new initrd.gz should work better for chinese users (and likely others aswell) as it mounts the sdcard with an option that allows it to work with UTF16 characters.

It may be safest to use a hexeditor to change paneltype and keypad type (attilt) because I'm not sure if the NBH Editor is up-to-date with the new RAMSIZE parameters.

NBH users please understand that these kernels are 240x320 ONLY until we have an NBH Editor that let's us tweak the RAMSIZE.

(If you know what you are doing the RAMSIZE is located att offset 0x134c and the byte order is reversed. If you do NOT understand what that means DO NOT TOUCH!)

HaRET users use the following in default.txt

set RAMSIZE 0x07300000 (for 240x320 Froyo)

set RAMSIZE 0x07100000 (for 320x428 or 320x480 Froyo)

set RAMSIZE 0x06800000 (for Donut or Eclair)
[Touch CDMA Android Development] mnjm9b:
what would be the difference between 2 & 3?

what is the 'everything else as is' part?

other than that I am sure most people would prefer the touch ui.
[Touch CDMA Android Development] mnjm9b:
do you know if the new initrd.gz and zImage are eclair/donut friendly?

meaning, will they play nice with things like camera?

or should eclair/donut stick with the older ones still?
[Touch CDMA Android Development] kallt_kaffe:
Alternative 3 has a lot more changes than just to force toich UI. And alternative 3 has the Touch UI as something you can turn on and off at your own choice but alternative 2 has it forced on and you cannot turn it off (without recompiling).

Alternative 3 is what you have in CyanogenMod, in other words VaniljEclair. Alternative 2 is nothing extra except that Touch UI is turned on.

The only drawback, and the reason it's not used by default, is that you can accidently hangup and do other things with your face when you are on the phone.

For me I'd be OK with Alternative 2 and it means we have the source and compiles it ourselves but Alternative 3 is more flexible although it means we get a precompiled apk and adjust it for QVGA.
[Touch CDMA Android Development] kallt_kaffe:
It should be as long as you set up RAMSIZE correctly in your default.txt. Also the NBH's can be used with Donut/Eclair if you do some hexedit magic on them.
[Touch CDMA Android Development] mnjm9b:
I would say 3 would be good then.

as for the face thing...didn't there used to be a screen lock that would show a

"double tap to unlock" or something like that?

I thought that it was the new zImage that was freaking out the eclair camera.

is this fixed now?
[Touch CDMA Android Development] kallt_kaffe:
I don't think the touch UI has that one, I've only seen it in the standard UI.

If you set RAMSIZE to 0x06800000 it should reserve 16Mb for framebuffer and camera. That should allow the Eclair and Donut camera to work but you will loose the extra 11Mb that Froyo can use. 0x07100000 will give 9Mb extra for Froyo and still allow HVGA and 0x07300000 will give 11Mb extra but restrict you to QVGA.

A new libcamera for Eclair would propably allow it to use the extra 9 or 11Mb aswell.

That said, I haven't tried the kernel on Donut or Eclair but it should work given you setup the RAMSIZE correctly. (which means if you plan to dual boot Froyo and Eclair, say goodbye to the extra 11Mb or to the Camera in Eclair)
[Touch CDMA Android Development] taupe47:
Thank you for all your staff :-)

All works for me, but I have only one problem... I tried a lot of "solutions" but any one works for me :/ My problem is when I finish a download (100 %) from the Android Market I got this error :

"Download was unsuccessful, please try again." Sometimes it's works, but rarely !

// EDIT: My downloads are also anormaly slow (very slow!)

// EDIT2: When I try with another version (old: Myn’s Warm Donut - [RLS 5]) , I don't have any problem's.
[Touch CDMA Android Development] jcatt:
Strange Radio Issues

I seem to be having an issue with my Att tilt, I don't know if this is a kernel issue or a user space issue. But it seems that sometimes when the phone wakes up from a long sleep, I loose all network connectivity. The phone will still say I have signal and It appears to still be connected to EDGE and receiving traffic, but I can't call, txt, or use data unless I reset the Modem with the modem app.

I also have noticed that this only happens if data is enabled. If I leave data disabled in the modem app, I don't seem to have the same problem. I have also noticed that I have a higher signal strength with the data disabled and loose signal more with it enabled.

I am running on T-Mobile USA and have the appropriate APN setup, I am also running with the latest kaiser radio, and the 7-8-10 Kernel.

Thanks for your support,

JCatt
[Touch CDMA Android Development] kallt_kaffe:
Try this:

Open terminal (there is one i "Dev tools")

$ su

# hsxpa.sh 2

# grpsclass.sh 12

Then restart your phone. These are the mobile data settings used by Myn's Warm Donut RLS5.
[Touch CDMA Android Development] toasty_:
Maybe I'm the last one who sticks with donut. But I like it. its stable, i had only a few FC's and the speed is much better compared to the eclair builds i ve tested - e.g. opening Dialer, sms... - YES, I am from yesterday...

But I am wondering if donut users can also profit from this RAMSIZE setting. What does this setting effect in Donut builds? Do I have no camera or are there other issues? Has anyone tested it?
[Touch CDMA Android Development] kallt_kaffe:
This what dzo says on the subject:
[Touch CDMA Android Development] toasty_:
thx for this info. but only one question, is there a significant increase in performance for froyo with this setting? Or is it increasing stability (launcher reloads...)
[Touch CDMA Android Development] taupe47:
I tried this but it doesn't work. Moreover i obtain this error "grpsclass.sh not found".

For information I don't use "mobile" data but i use my wifi.

I can download with success small files but only small files :-/
[Touch CDMA Android Development] muscles:
I have a Tilt running on AT&T. I am in the process of updating to the latest build...

build: system-froyo-odex-eu-nojit-11-07-10_20.tgz

kernal: KAISIMG-PANEL1-320-TILT0-FROYO.zip

Some issues I need help with:

1) I've put all my APKs on the SD-Card in a directory called "AndroidApps". The apps do not install. Is there something else I am supposed to do?

2) Using I.Hex, I changed the kernal to board-kaiser-keypad.atttilt=1 AT&T tilt. I cannot get the keyboard to type uppercase letters.

3) Does the eu version of the build work OK in US on AT&T?
[Touch CDMA Android Development] mnjm9b:
Alright, I posted this question before. and because nobody answered and it seems nobody else had the same problem, I figured it was just me.

so I reinstalled and wiped data, yet I am still seeing the same issue.

The issue is, none of the installed apps that I either download or install from backup show any info under 'manage applications'

they seem to be locked at 'computing...'

which then makes it unable to do things like 'clear data' or 'move to sdcard'

this problem has been an issue for at least the last few versions of dzo's froyo.

using any of the latest kernels.
[Touch CDMA Android Development] blindguyinanorgy:
1. there is no auto install anymore (i think) you can also put them in system/app tar it and name it androidupdate.tar

2. i had this problem too. after each boot i just used the on screen keyboard once and i was able to do caps from then on.

3. yes, it has alot more languages. do you need more than english?
[Touch CDMA Android Development] blindguyinanorgy:
same for me
[Touch CDMA Android Development] dzo:
I found a fix for this, add:

export ASEC_MOUNTPOINT /mnt/asec

to /system/sysinit.rc or wait until this change works it's way into the next build.

I don't know if storing apps on the sdcard works yet.
[Touch CDMA Android Development] muscles:
1) I did this and it worked for some of my apps. For some reason most of the APKs did not install. I have the install untrusted apps option enabled too. Any ideas?

2) this worked

3) Only need English.
[Touch CDMA Android Development] dzo:
Some apps need to register a native library, copying them isn't enough. The best way to install an app is with adb. Just type: adb install apkname.
[Touch CDMA Android Development] lunigma:
I haven't been able to "Move to SD Card". I'm running your latest build with the Jul-8 kernel.

I know not all apps support this, I'm trying it on an app that does support it (Transdroid). I get a pop up "Failed to move application."

I'm using an 8GB SDHC Class 6. Formated as fat32.

I've tried different cards and even ext2.
[Touch CDMA Android Development] kallt_kaffe:
Sorry, typo... gprsclass.sh.

In that case try this:

$ su

# wifi-level.sh high

Then stop wifi and start it again. Some people seems to need the high setting.
[Touch CDMA Android Development] samjam:
Thanks for spotting that and the quick fix
[Touch CDMA Android Development] dertester123:
Sounds good. Im not sure if it would help.. But maby someone could write a little guide with tools or tipps to collect data for the devs if something like this happens. Its just a thougt of users uploading better errorlogs so its easier for you to figure out :)

But maby its just to complex
[Touch CDMA Android Development] taupe47:
Thank for your answer!

I tried but it doesn't work. After "wifi_level.sh high" a download (in the android market) seems to be a little more faster (but it stay anormally slow :-s) and at the finish of the download it all the time says me 'Download Unsuccessful. Try Again'. Sometimes after a download, when it installs it, my phone reboot android (not the phone but android).

// EDIT: When I try your other version "VaniljEclair RLS7c" based on Android 2.1 , I don't have any problem's except that the camera doesn't work on this version!
[Touch CDMA Android Development] blindguyinanorgy:
i said that wrong before...you want EU it has english and 2 others. all languages has, well all of them
[Touch CDMA Android Development] citrit:
I have been running this new version for over 24 hours with no lock ups. Prior to this I would have experienced at least one. Everything is working as expected.

Thanks Dzo.

EDIT: I spoke too soon. I just had a lockup, it wouldn't wake up from sleep. I guess I spoke too soon.
[Touch CDMA Android Development] mnjm9b:
Worked great, thank you...

although, still no 'move to sdcard'

could it be that the actual apps need to be programmed for that?

or should it work with any app?
[Touch CDMA Android Development] mrkite38:
the apps have to be programmed for it.
[Touch CDMA Android Development] Joe1981AL:
So far best that I've tried on my Kaiser. Runs smooth and fast, using Launcher Pro Beta from Market, and DialerOne for phone.

Everything I've tried seems to be working, did have some total freeze ups, but trying the nojit version now to see if that fixes it.

The few things I'm waiting to see are:

Autofocus On Camera (May just be my phone)

Whitebalance Working on Camera (Yellow Tint Pictures)

Tower Location
[Touch CDMA Android Development] mnjm9b:
alright, cool.

I found this list of apps that are supporting 'move to sd card'

here http://androidforums.com/android-applications/105650-froyo-apps-2-sd-list.html

I installed jewels and it did indeed show the 'move to sd card' was now available.

however, it isn't working yet...

"failed to move application"

pretty cool though... can't wait for this to actually work.
[Touch CDMA Android Development] muscles:
Google Voice

Any idea why the tilt will not update the phone's voicemail service to Google Voice?
[Touch CDMA Android Development] kallt_kaffe:
Try the kernel I posted in the kernel thread this morning.
[Touch CDMA Android Development] stheod:
Hi Dzo,I would appreciate it if you could make your magic and include Greek lang also to your excellent 'EU' Froyo builds. It is not a big loss but it will make "more" complete my Froyo experience. Thank you for giving new life to my old Polaris.
[Touch CDMA Android Development] Barogi44:
What are the differences between odex and unodex builds?
[Touch CDMA Android Development] muscles:
Which thread are you referring to? Is the kernel for the tilt? Thanks.
[Touch CDMA Android Development] mrkite38:
http://xdaforums.com/showthread.php?t=382265
[Touch CDMA Android Development] samjam:
Me too... Screen stayed black, but if I held the power button or the explorer (home) button down, the vibrator buzzed as it would - so it was just the screen not lighting up.

Then I held the power button down a very long time and the screen went white, and stayed white.

Now, after a reset it won't boot - it gets stuck on the 4 colour boot animation.

It will boot to the ram-disk with the 10 menu options, but slowly and I think not properly, it seems to behave as some USB initialization problem! As if it were a usb host with ethernet! Maybe it always said that and I didn't notice. I got some screenshots with my camera that I will attach to this post if I can manage it.

A kernel re-flash did nothing and I can't see how a system re-flash will.
[Touch CDMA Android Development] samjam:
I'm using the kernel you posted here http://xdaforums.com/showpost.php?p=7141910&postcount=448 which I think is the most recent one you posted (I don't find a later one in that thread.

Now I have trouble booting, which I report in a post in a few minutes.
[Touch CDMA Android Development] muscles:
Thanks! I should have come back and said that I found it.

I loaded the new kernel in that thread. Now I boot to a black screen. I boot to a black screen even if I revert the kernel now.
[Touch CDMA Android Development] samjam:
kernel stuck booting

Using this kernel for kaiser: http://xdaforums.com/showpost.php?p=7141910&postcount=448

boot-up to the ram-disk that allows me to press the centre-button to re-install an image takes too long and shows this output:

clk_get usb_hs_clk

clk_get usb_hs_pclk

usb_function_register() 'adb'

usb_function_register() 'usb_mass_storage'

msm_hsusb: functions bound. starting.

usb_mass_storage usb_mass_storage Number of LUNs=1

usb_ether_setup()

usb_function_register() 'ether'

hsusb: IDLE -> ONLINE

hsusb: reset controller c64c9800

usb: notify offline

hsusb: ONLINE -> OFFLINE

No IRQF_TRIGGER set_type function for IRQ 190 (Kaisergpio)

(pause for few seconds)

msm_i2c msm_i2c.0: Error: waiting for notbusy

.... (wizzy screen)

clk_set_rate 21:25000000

set sd click - 0 1

mmc1: host does not support reading read-only switch. assuming write-enable.

SD Init Retry

mmc1: new SDGC card at address d555

mmcblk0: mmc1:sd555 SU04G 3979776KiB

mmcblk0: p1

Hold down Volume Up or DPad... etc...

I then get normal pre-boot animation boot with this message:

mounts: mounting /data/sysfiles/su on /system/bin/su failesd: Too many levels of symbolic links

And the boot animation never goes away

EDIT: It did go away when I took the SD card out.

but the touch screen does not work

I tried the latest kaiser image from: http://it029000.massey.ac.nz/vogue/files/?C=M;O=D and same problems now!

So taking the battery out and pressing a few keys to discharge capacitors and good luck made it work again!

So it seems like maybe the msm changes got the hardware into a dodgy state that needed power off?

I'm now going to try this one of kk's: http://xdaforums.com/showpost.php?p=7150158&postcount=5509

EDIT: Also boots nice and fast past the DPAD ramdisk message and then to Android.

Conclusion: the msm/i2c stuff put the hardware in a weird state that required loss of power to fix.

Maybe kk's this morning kernel from http://xdaforums.com/showpost.php?p=7150158&postcount=5509 (and now I know where to look) will be fine.
[Touch CDMA Android Development] know.patience:
i'm having the sdcard issue that was noted back on page 16 of this thread. my camera and gallery apps can't see the sd card (same with my gdocs app). it seems to be app related because astro can see the card with no problem. did anyone find a fix for this?
[Touch CDMA Android Development] garringm:
Is it just telling you it isn't. Mine keeps saying that but it does work as it should

-------------------------------------

Sent via the XDA Tapatalk App
[Touch CDMA Android Development] know.patience:
when i start the camera app it says 'please insert sd card before using the camera' and the gallery app says 'sd card not mounted or present'.