yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] tiagoclc:
Homescreen reloading (redraw) issue solved

put the settings bellow in sysinit.rc, replacing the corresponding text:

# Define the oom_adj values for the classes of processes that can be

# killed by the kernel. These are used in ActivityManagerService.

setprop ro.FOREGROUND_APP_ADJ 0

setprop ro.VISIBLE_APP_ADJ 1

setprop ro.SECONDARY_SERVER_ADJ 2

setprop ro.BACKUP_APP_ADJ 2

setprop ro.HOME_APP_ADJ -17

setprop ro.HIDDEN_APP_MIN_ADJ 7

setprop ro.CONTENT_PROVIDER_ADJ 14

setprop ro.EMPTY_APP_ADJ 15

# Define the memory thresholds at which the above process classes will

# be killed. These numbers are in pages (4k).

setprop ro.FOREGROUND_APP_MEM 1536

setprop ro.VISIBLE_APP_MEM 2048

setprop ro.SECONDARY_SERVER_MEM 4096

setprop ro.BACKUP_APP_MEM 4096

setprop ro.HOME_APP_MEM 1536

setprop ro.HIDDEN_APP_MEM 5120

setprop ro.CONTENT_PROVIDER_MEM 9216

setprop ro.EMPTY_APP_MEM 10240

# Write value must be consistent with the above properties.

# Note that the driver only supports 6 slots, so we have HOME_APP at the

# same memory level as services.

write /sys/module/lowmemorykiller/parameters/adj 0,1,2,7,14,15

write /proc/sys/vm/overcommit_memory 1

write /proc/sys/vm/min_free_order_shift 4

write /sys/module/lowmemorykiller/parameters/minfree 1536,2048,4096,5120,9216,10240

# Set init its forked children's oom_adj.

write /proc/1/oom_adj -16

___________________

if u dont know how to do this, just download and install this update:

http://www.4shared.com/file/7DyarD1o...wmemoryki.html

dont forget to fix permissions immediately after install update.

Good Luck!
[Touch CDMA Android Development] dzo:
-17 is probably a bit drastic, 1 should work fine. I set it to 2 because there probably are times when you want the visible app to have access to as much memory as possible.
[Touch CDMA Android Development] alexinc:
what i've noticed with latest froyo is a bit tricky now. wlan only works with latest kernel and camera doesnt work at all, but downgrading to kernel with camera-support doesnt fix this issue... so working cam and wlan doesnt seem to be possible on latest froyo even with older kernel. :( (of course related to pola200)
[Touch CDMA Android Development] dzo:
Camera works fine for me on pola200 and latest kernel. For working wlan on the old kernel you just have to replace /system/lib/module/wlan.ko with the one from an earlier system.
[Touch CDMA Android Development] samjam:
Camera (stills) works fine for me on latest 2/9 kernel and 2/9 froyo
[Touch CDMA Android Development] alexinc:
how it comes that some report the green screen on pola200? are they using different components like with display? i even tried different radio but got same result! when switching back to old kernel camera worked without problem... strange!

then yesterday i tried latest froyo and older kernel. cam started but soon got fc! i'm always doing task29 + fresh install on nand, to avoid trouble.

with wlan i already got the point that it depends on wlan.ko and/or kernel... ;) no problem with that (following daily for about 2month :) )

so could you plz tell me, which radio your pola200 is running? remembering the radio often influenced cam on win mobile.

EDIT: tried it with 1.65.38.14 and 1.59.46.12, no difference. green screen on cam, which becomes photo after shooting! ;)
[Touch CDMA Android Development] Richard Langlois:
Losing Exchange configuration after a couple of days

Hi,

I've got an issue with the latest kernel and systeem where I lose my Exchange settings after a couple of days. It just disapear without leaving trace. The mail setting is gone as well of the messages, calandar and contacts. It happened 3 times in the last week or so and last time was with the latest kernel and system. I never had that problen in the last months

Thanks in advance

Richard
[Touch CDMA Android Development] Takiyon:
Facebook Contacts

Is it possible to fix the connectivity for facebook synching contacts? I cannot seem to add it as an account no matter how I try. Any ideas on any ways to patch this issue using the console?
[Touch CDMA Android Development] alexinc:
i already tried changing build.prop and stuff like this, as with cyanogen facebook sync is working, but didnt succeed... for now its just the way it is! :(

looking for the day when froyo will work with all main-features, but for now its just awesome how far everything already came! :)
[Touch CDMA Android Development] _guzzler_:
I am not able to see 3g icon. It always shows "H". I am not sure if this is just UI related or its actually using 2g. I am on Sprint. Using the latest nbh and tgz.

I tried mobilespeedtest.com and it shows somewhere between 1xevdo and 3g.
[Touch CDMA Android Development] SuperJMN:
Maybe you're connected to a network that uses HSDPA (better than 3G).
[Touch CDMA Android Development] margosmark:
I am getting that too on bell, its cdma so it cant be hspda or whatever. It does seem slower too.
[Touch CDMA Android Development] vinny13:
Bell is a HSPA network, and HSPA is faster then 3G btw.
[Touch CDMA Android Development] mrkite38:
Maybe bell has hsdpa, but the Vogue doesn't. Regardless, I can confirm the same behavior on Verizon.
[Touch CDMA Android Development] margosmark:
Yeah thats for their utms network, not their cdma one which is evdo Rev A.
[Touch CDMA Android Development] vilord:
If you see H, that refers to HSDPA, which is 3.5G for GSM networks. If you see an E then you're on 2G.

It is mostly just UI, but our radio code was written before android supported CDMA, so it just fakes everything so the core thinks it is running on a GSM phone.
[Touch CDMA Android Development] uriahheep:
Hey all,

I was just snooping around, and it seems like despite the move to 2.6.32 there is still no ALSA support for the Vogue. According to people in #htc-linux on freenode, there has been an MSM ALSA driver in the linux kernel since 2.6.29, so I was wondering what would be needed right now to get that driver working (and to get the Vogue froyo port to use it) instead of the old/current audio interface, which limits compatibility with several (pretty much all modern) linux apps that would be a great addition to our phones.

I don't know where this stuff is at on the list of priorities, however if someone could give me a few pointers as to what modifications (if any) would be needed to both the new kernel and froyo I'd be more than happy to give it a try, despite my lack of experience ;P

Anyway, cheers, and thanks for the good work so far!

-uriah
[Touch CDMA Android Development] zPacKRat:
Phone only rings once

I am running the 9/2/2010 build on my kaiser with the 9/9/2010 kernel and I'm having an issue where the phone only rings once. It does however stay at the answer screen as if it's still ringing. This is on a Kaiser/Tilt btw if that matters.

BTW, love the work, the only other issue is that sometimes it the phone will hang at a white screen when waking it up, usually if it went to sleep doing something like installing an app.
[Touch CDMA Android Development] friedricebob:
On WinMo or Myn's donut, my phone would nearly always be on EVDO. On Fresh Froyo, I'm usually getting "3G" icon, and the system reports UMTS connection. Seldom now, I get the "H" icon, and internet is noticeably faster, and the system reports HSDPA. The difference is large, sub 100 on 3G vs 600-750 kbps on "H".

Any clue why I rarely get my EVDO connection now? Am on a 9/6 build of froyo, I think. I can double check later at home.

Edit: Sprint network, btw
[Touch CDMA Android Development] thoughtlesskyle:
hey guys i made an update.tar with the newest google apps as of today
[Touch CDMA Android Development] SuperJMN:
Thanks! I'm testing them now.*
[Touch CDMA Android Development] l1q1d:
Work great thank you (no more crash in market)
[Touch CDMA Android Development] thoughtlesskyle:
glad to hear it guys, im glad i can finally give something back (even if its small) to the community.
[Touch CDMA Android Development] matcha20:
Just wondering:

I remember that Dzo (I think) had said that his network was switching and he was therefore moving up from the vogue, but as I recall that was going to be in November. Has development for the vogue/kaiser already ceased? Is the 09-02-2010 kernel/build the last one that we'll be seeing from Dzo?

If so, that's a shame, but I also want to give a big thanks to Dzo and K_K for all the work they've put into developing android for our platform. Their work has given new life into my now 3 year-old phone (3 years, btw, is the longest I have EVER held on to a phone, I usually switch up every 6 months, but Kaiser devs are just too prolific and effective, what can I say?!). If the video playback issues had been resolved, I would say that android+kaiser = perfect. Regardless, thanks guys.
[Touch CDMA Android Development] thoughtlesskyle:
The devs have lives too Dzo is a teacher and we are in September so he is probably busy so just relax
[Touch CDMA Android Development] mrkite38:
+1. Plus, in the past, the best things have come after a period of low activity - for example, just a few weeks ago dzo was pretty quiet, then he released the 2.6.32 kernel port. So... he COULD be quietly hacking away at something wonderful... ;)
[Touch CDMA Android Development] thoughtlesskyle:
That was also what happened just before we got the ability to flash to nand
[Touch CDMA Android Development] vellowax:
I will wait even if the next rls just a few fix of the build...;)
[Touch CDMA Android Development] SuperJMN:
This lack of news is getting me sad.
[Touch CDMA Android Development] ObviousMan:
Is there a dialer for FroYo where MMI codes (##) work?

Is there a dialer for FroYo where MMI codes (##) work?

I can not activate a CDMA Touch with FroYo on it at all, tried couple different ones, but the dialer just keeps giving Invalid MMI code.

I'd hate to go to stock ROM just to activate...

OM
[Touch CDMA Android Development] immolo:
Has anyone noticed the yaffs is a little more unstable with the 2.6.32 kernel as everytime my phone is not cleanly turned off I have to wipe the davik cache from recovery to make my apps work on my phone again.
[Touch CDMA Android Development] samjam:
What phone do you have? Do you get any yaffs error messages on bootup?
[Touch CDMA Android Development] zPacKRat:
I have the same issue running dzo's 9-9-10 kernel and his 9-2-10 rom fron nand on a tilt.
[Touch CDMA Android Development] cnigro1279:
same issue here as well

I too have seen some stability issues as well. I have had to wipe and restore several times due to corruption to NAND/Data. Love the speed though and will deal with it for as long as I can...I've thought about going back to my fav Eclair build but we'll have to see how it goes....
[Touch CDMA Android Development] immolo:
I'm using a kaiser and I normally just get errors about yaffs not erasing some blocks but lately I've been getting yaffs tradigy errors
[Touch CDMA Android Development] tiagoclc:
yaffs problem

My phone got this problem when the battery dies and it shuts down.

To solve, just clear Dalvik Cache and fix permissions, in this order
[Touch CDMA Android Development] tiagoclc:
file system

what about nilfs?

comparison:

jfs:

mount: 0.44s

copy: 40.27s

sync: 11.08s

rm: 10.92s

sync: 9.69s

umount: 1.42s

total: 73.82s

xfs:

mount: 0.90s

copy: 25.13s

sync: 9.68s

rm: 1.44s

sync: 0.05s

umount: 2.38s

total: 39.58s

ext4:

mount: 0.94s

copy: 14.75s

sync: 13.46s

rm: 0.33s

sync: 1.08s

umount: 0.04s

total: 30.60s

nilfs2:

mount: 0.06s

copy: 12.28s

sync: 5.18s

rm: 0.31s

sync: 0.10s

umount: 0.02s

total: 17.95s
[Touch CDMA Android Development] mrkite38:
I think the data loss issues only occur on the .32 kernel, right? It's still experimental, guys. It's good to report them, of course, but it's probably premature to talk about switching filesystems.
[Touch CDMA Android Development] samjam:
There was other data loss before the .32 kernel, there were just no error messages associated with them.

previously there was what was known as "missing icons" and applications whose data (or code) was corrupt. For me, removing and re-installing the app was required.

With .32 we get error messages but I get less data loss - usually only no phone crash.
[Touch CDMA Android Development] l1q1d:
The data loss is due to the buggy nand driver not for fs...
[Touch CDMA Android Development] vilord:
Hey all :)

So we can't switch to nilfs for the internal memory, because it won't work ;)

the NAND driver is a char/raw device, and yaffs knows how to talk to raw devices, whereas nilfs is a block device filesystem.

Also, just like l1q1d said, it isn't the filesystem, it is the memory driver.

But, if nilfs is getting stable, we should look at using it for the SD card!
[Touch CDMA Android Development] tiagoclc:
file system

I know that the problem is the driver.

Only suggested a faster filesystem.

Didnt know that the nilfs was not applicable.

About using an old kernel, only 2.6.32 activates the swap partition on sdcard.
[Touch CDMA Android Development] samjam:
After me saying that I just got my first vanished application - a generic icon was on the home-screen and the app was no longer installed, so I had to re-install it.

(Happened after a system hang using GPS)
[Touch CDMA Android Development] wondercow:
back button

Is anybody else having trouble with the back button on their Vogue with Fresh Froyo 9-2-10? Every time I wake up the phone from power collapse, the first time I hit the back button, it doesn't register (no lights come on), but any time afterwards it works normally.

I'm running zImage-2.6.32-froyo-06-09-10_22 on SD via ext2, but if I recall both newer zImages shared the same problem (rolled back to the 9-6-10 version for perceived stability improvements).
[Touch CDMA Android Development] derringdo:
I have this exact problem too. I mentioned it the kernel thread but I didn't see anyone else experiencing it. Did you try rolling back to a pre 06-09-10 kernel to see if it still happens?
[Touch CDMA Android Development] Takiyon:
Kernel Downgrade

I have the same problem with data corruption. Usually happens after a Sleep of Death. Gonna use the below kernel and see if I have better results.

kaisimg-panel2-240x320-2.6.32-tilt-froyo-02-09-10_16.nbh 02-Sep-2010 16:39 3.0M (same issue)

kaisimg-panel2-240x320-2.6.32-tilt-froyo-27-08-10_23.nbh 27-Aug-2010 23:35 3.0M Trying This one Now
[Touch CDMA Android Development] whoknows86:
No audio...?

Hi,

First and foremost, I want to thank everybody who has made porting Android possible to our phones, great way to extend the longevity of it. Keep up the good work! :)

I'm having a very frustrating issue: no audio in Android.

I'm currently have:

Kaiser 130

SPL-3.56 Hard

CPLD=8

Radio: 1.71.09.01

Dual booting: WinMo 6.5 and Froyo: 2010-09-09

I've installed Android via NAND, and SD card, changed the different radios from 1.65.xx to 1.71. Started from the oldest system build of June 2010 to the latest 09-09-2010.

No matter what version/build of Android I run, from Donut, Eclair, or Froyo, audio will not work. However, whenever I go back to WinMO 6.1 and 6.5, audio works just fine. That leads me to believe that my phone is fully functional?

I reinstalled to the HTC Original WM Stock ROM, as some suggested, and threw Android back on, to no avail.

I am able to force some audio. While having music play (no audio) in the background, open up "AudioManager", fiddle around with the volume settings until I am able to hear music. Once I exit out and the music track ends, so does my audio.

From what I can see, everything else seems to works fine in Froyo, minus this issue.

Can anybody help me out? Suggestions?

Thanks.

Update 09-24-2010: Audio Fixed!

kaisimg-panel2-240x320-2.6.32-tilt-froyo-09-09-10_21.nbh

system-froyo-02-09-10_17.tgz

Radio: 1.70.18.02

I decided to re-do everything over to see if it would make any difference, lo-and-behold, I got audio! Ding Ding! :)

I wiped my system clean, installed Froyo via NAND (much better than running off the SD card) and changed the Radio.
[Touch CDMA Android Development] guerchele:
Hi dzo,

Installed it on my phone, but audio, gps, wifi and camera are not working. Any idea when will these device problems will be fixed? I don't have much spare time and I am a newbie, but would like to help somehow (testing or whatever).

To format my sdcard, I used Ubuntu 10.04 and on my first bet, I partitioned [fat32],[ext4],[ext4], but noted only ext2 is mounted successfully during install time. Although I created two ext2 partitions (one for system, other for data), I noted some programs (Google Maps, as an example) is recording to /sdcard/ which is [fat32], by the way.
[Touch CDMA Android Development] mrkite38:
Which phone?
[Touch CDMA Android Development] wondercow:
Hmm, I missed your earlier post or would have chimed in. I rolled back to the zImage-2.6.32-froyo-24-08-10 (the earliest 2.6.32 zImage available) and it worked, but when I moved to zImage-2.6.32-froyo-27-08-10_23 (the next stable kernel) it had the back button response problem. It's tough to confirm, but I think the d-pad buttons might have the same issue (I rarely use them so it's hard to tell).

So, I guess this is a kernel issue, not a Fresh Froyo issue. I'll bring it up over there--thanks for the troubleshooting suggestion.
[Touch CDMA Android Development] dzo:
I've put a new Froyo system image on Sourceforge. This is 2.2.1 (frg83), I don't know what changes it has and it hasn't been well tested, I just did "repo sync;make"

http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download

Let me know if something has broken.
[Touch CDMA Android Development] lunigma:
Everything is running smoothly for me so far.

Changes I've noticed:

Superuser app has been updated.

The gmail app seems to be the latest.

Google maps is not the latest.
[Touch CDMA Android Development] alexinc:
adding facebook account incl. syncing still doesnt work... ;)
[Touch CDMA Android Development] SuperJMN:
With this kernel: http://xdaforums.com/showpost.php?p=8385928&postcount=5730

And this build: http://sourceforge.net/projects/androidhtc/files/system-froyo-01-10-10_16.tgz/download

And Polaris --> When you turn Wifi ON the device freezes completely. Can somebody try the same configuration to see if there is a problem or it's only my device?

Thanks.
[Touch CDMA Android Development] n2rjt:
SuperJMN: That combination works nicely on my Kaiser.
[Touch CDMA Android Development] vinny13:
One thing I noticed with the latest build is that Rogue Tools seems to work again? Haven't really tested it with NeoCore though..
[Touch CDMA Android Development] johansson.richard:
Wifi issues

Hi!

I have the exact same problem as SuperJMN, except for I'm running on HARET and Polaris: When activating the wifi, the phone freezes completely. I have tried to first run the HARET from an entire 2 Gb FAT32 SD-card partition but after having followed the instructions to create an Ext2 partition onto which I did put the data.img files, I soon found that this made no difference.

Running the same build as SuperJMN (2010-10-01).

The zImage in my system at the moment is the one from 2010-09-09.

Does anyonoe here have any reasonable suggestions?

Thanks

System info:

POLA100

Kernel: 2.6.32.9 martin@it0044296#289

Build: full_vogue_userdebug 2.2.1 FRG83 eng. martin.20100930.233345 test-keys

R 1.65.30.09

G 215.101.40.08

D 3.3D.WM65X
[Touch CDMA Android Development] SuperJMN:
I was out all the weekend, but I'll come home tonight. I'm gonna try it again go see if it happens the same, but I'm pretty sure I flashed and installed the latest files correctly.
[Touch CDMA Android Development] manu33xtro:
WIFI corrections

Hi,

I test at this moment the latest kernel modified by l1q1d with the last build of DZO modified by Thoughtlesskyle : Wifi doesn't work at the first time !

I have to upgrade with the file (see attachment) and it's work very well after :)

The problem is I don't remember who makes those corrections :confused::confused:

Cheers.
[Touch CDMA Android Development] johansson.richard:
Hi again!

So, is it possible to run the update as named (androidupdate.tar) directly from andboot folder, or does one have to rename it to androidinstall.tar? I have seen the option "Install update" in the Android install program, therefore my question.
[Touch CDMA Android Development] pentagramII:
Dont change the name of update file. It's ok, just hit install update in repli menu... Everything will be fine...
[Touch CDMA Android Development] johansson.richard:
Thank you Pentagramll! I will try to do this, as my other functionality is just great. I assume that the "repli" menu you are referring to is the one accessed by pressing and holding Volume up when booting, right?

Is it preferred to run the system with data.img on ext2 partition for wlan to work, or doesn't it matter?
[Touch CDMA Android Development] vellowax:
it doesn't matter with the data.img. the wlan file will update the system image.
[Touch CDMA Android Development] johansson.richard:
Hi all again

So, I ran the androidupdate and WiFi now works great. Instead, Bluetooth seems to refuse to start. Bluetooth worked before and isn't working now.

Has anyone else experienced the same behaviour?

Must say the xda-developers.com is the greatest source of knowledge that I know of.

Cheers!

Richard

Polaris with Windows Mobile 6.5 3D from pcarvalho + Android (10-10-01) by Haret
[Touch CDMA Android Development] karlosreza:
HI a dude?

First of all congratulations on the development they have achieved.

I made it to the installation menu of Froyo with my kaiser but really did not want to take wm for now, I'd like to try the Froy from 2.2 in SD as I have done the other times, if I select in the menu install wm deleted?

Greetings

srry for the bad english >.< (translator)
[Touch CDMA Android Development] johansson.richard:
Hi karlosreza

What kernel version are you using? What release are you using? If it is the way that I did it, then despite that the Android installer tells you that this will erase you current system, that only goes for the previously installed Android that you have on the SD card, not the Windows. If you downloaded the Haret and run it from the File Explorer in Windows Mobile, the phone told you "Booting Linux", then you should be set to go. Just press yes on the question on whether you would like to wipe the current system. If you are very keen on keeping you previous data, then choose No on the second question whether you want to erase the data as well.

Was this an answer to your question? please provide details about your phone.
[Touch CDMA Android Development] arvinchugh:
How to enable GIT and How to get sense for this build

First of all i want to thanx DZO for getting this build to us.. its most stable and fastest build i have come across till now.. to change looks i added AWD launcher and theme and it works like charm.. so fast and smooth.. i was just wandering how can i get bit and compcache support in this build and is there any way i can get htc Sense UI in this build too.. i'm using it on kaiser with latest kernel..

thanx for ur reply in advance..

Arvin..
[Touch CDMA Android Development] Rondador:
arvinchugh, your touchscreen works?, mine dont since i use the 2.6.32 kernel, it gives lots of i2c related errors on dmesg, and touchscreen works in winMo.
[Touch CDMA Android Development] arvinchugh:
everything works fine.. i'm running it on nand..
[Touch CDMA Android Development] Rondador:
me too, but at start i always see the message "msm_i2c.0: Bus still busy, status 2100m intf 100" and i must use the phone like a cheap nokia with android; everything else works great and i dont want to go back to older kernels. ¿What kernel do you use?
[Touch CDMA Android Development] arvinchugh:
i'm using 2.6.32.9 kernal..

also does anyone knws is there a way to sync it with windows 7.. wen i turn it on in storage mode it still dont detect anything in lappy :(

thanx again for ya help
[Touch CDMA Android Development] samjam:
Try power off and remove the battery - try to power-on with the battery removed; then insert the battery and power-on and see if that solves the problem.