yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] ThomasHW:
Look in the FAQ thread.
[Touch CDMA Android Development] fldash:
dzo, I'm not sure if this was a NBH change or what but I LOVE the fact that after I take a call, whatever I'm playing stops and I can simply restart it. Before it would stay in play but with no sound (because ending the call killed the audio) which required me to stop it, then start it again, and sometimes when trying to stop it, it would lock up and I'd have a really hard time getting audio back. Simply stopping the media server from playing whatever it is is great solution especially since I can easily restart it at the place it was stopped.
[Touch CDMA Android Development] themanwithaplan:
aa
[Touch CDMA Android Development] fldash:
I use Mixzing and it works fine. Reads all ID3 tags etc... I haven't used the default Music player.
[Touch CDMA Android Development] fldash:
I'm running Myn's warm donut that I odexed myself. I'm running the latest NBH from 7/1.
[Touch CDMA Android Development] Gersonian:
320x480 FroYo kernel

Will there be a 320x480 version of the latest kernel? I am really excited about the 11mb extra space on nand and 240x320 is just too big for me. I cannot seem to get the density to set correctly using rogue tools, which had led me to believe that its not possible unless I have a correctly sized kernel to begin with.

Thanks for everything!
[Touch CDMA Android Development] thoughtlesskyle:
i 2nd this, 320x480 is the only way i roll
[Touch CDMA Android Development] mnjm9b:
you can change res for nbh with a hexeditor or if you are still using HaRET just change the settings in default.txt
[Touch CDMA Android Development] Gersonian:
Thanks I will give it a shot.

EDIT: Something is causing major lockups and freezing so I removed the attachment.
[Touch CDMA Android Development] mnjm9b:
am I correct in thinking that any zImage posted after "zImage-02-07-10" are for froyo ONLY.

if there is going to be a difference between donut/eclair zImages and froyo zImages should there be more than just a timestamp in zImage name?

like "zImage-06-07-10-froyo"
[Touch CDMA Android Development] Gersonian:
7.7.2010 320x480 kernel

Just to let you know I had to roll back to the 7.2 kernel. The kernel was causing major freezing, was causing issues with the keyboard, and prevented menus from showing up or they would show up, but I could not scroll through to select. I flashed and reflashed it before I rolled back.

With regard to the keyboard, the best example I can give is that it either would not pop up when searching in the market, or it would pop up but no letters would show up in text boxes, or the keyboard would show up but would remain in all caps even as the word being typed was not showing up in all caps.

With regard to the freezing it would lock up the entire system, similar to what happened when I created a kernel with loser's editor. Sometimes the phone would not fully wake up from sleep. It would be very slow to load when coming back from sleep.

And just another little thing is that the unlock slider would sometimes not show up, would not slide (but would unlock), or would be slow to react to sliding.

A rollback to 7.2 has fixed all these issues. Now if I had just thought of that before I wiped my system. Initially I thought it was an issue with either the latest version of launcherpro, but it turns out it was not.

EDIT: Just a little add on - These issues did not start immediately. At first everything worked fine, then all of a sudden it just sort of had one problem then the next until the whole phone was locked up or locking up from almost the moment i restarted it. I am telling you this because if you try to recreate the problems you may have to wait several hours or up to a day to start seeing the the problems.
[Touch CDMA Android Development] thoughtlesskyle:
i can 2nd all of this
[Touch CDMA Android Development] osilvan:
I've been experiencing the same
[Touch CDMA Android Development] odz:
Yep, same problem on my att tilt running the latest kernel (7/7/10)
[Touch CDMA Android Development] dzo:
I've made some changes to the kernel to use the ramsize that is passed to the kernel to work out the pmem sizes. This should make it compatible with older systems and haret users. I've only done it for vogue, could somebody try the same thing for kaiser and polaris. I also added the option of using 6M pmem for 320x480 and 320x428, tinboot needs changing too for this to work on other devices. New kernels in the usual place.
[Touch CDMA Android Development] loserskater:
Is this now hard coded so there's no more cmdline options?
[Touch CDMA Android Development] dzo:
There are no more command line parameters, instead the pmem sizes are calculated from the memory size, this means that is should always boot but if you use haret and don't specify RAMSIZE as 0x07300000 (0x07100000 for non native resolutions) you won't get the extra RAM.
[Touch CDMA Android Development] loserskater:
Ok cool. Just wanted to make sure that my editor still works. I guess I'll need to get those settings working with kaiser and polaris though...

EDIT: What should RAMSIZE be for Kaiser and Polaris? Or is there more work in the kernel that needs to be done before RAMSIZE is calculated?

2nd EDIT: I just added 0x07300000 to my Kaiser and it seems to be working. I have 104 total ram now... I haven't tested anything higher than 240x320 though.
[Touch CDMA Android Development] Fantatier:
Hey, im new here and a total n00b - so appologies for my silly questions...

i have a HTC Touch Viva, so pretty much identical to the normal HTC Touch.

im trying to follow your guide here

and the one from sourceforge

i downloaded the following version because it was the first zip version i found all the newer ones on SF seem to only be tar.gz for the moment.

VaniljEclair_RLS7c

the problem i think is that that version only contains 3 default.txt files namely for vouge, kaiser and polaris. not one explicitly for viva or the normal htc touch.

i tried all 3 files never the less but to no avail.

using the kaiser one does nothing.

using the vouge or polaris one i at least get to see a few lines (~5) of console but too small and fast to read.

then the mobile goes blank, vibrates and returns to windows after a minute or so.

now one thing i can imagine is that i need the correct default.txt, but that is only my best guess.

im open to suggestions :D

thanks alot for any help :)
[Touch CDMA Android Development] kallt_kaffe:
Have you pushed these changes to the kernel git? I could have a look at the Kaiser and Polaris parts once I got something to work with.
[Touch CDMA Android Development] dzo:
Sorry, I must have forgotten to push, changes are there now. For kaiser and polaris you'll have to set up the second memory bank in fixup depending on the memsize it gets from tags. Hope that makes sense.
[Touch CDMA Android Development] kallt_kaffe:
Yes it makes sense. I think I know what needs to be done, if not, I'll let you know. :)

Btw, I haven't hade any SD-card complaints from the Camera app since I stopped using compcache. Do you think there is a connection? Maybe we should compile new .ko files against the latest kernel tree? But I'm not sure where to find the source for them and even if I did I'm not 100% sure I would know how to do it.
[Touch CDMA Android Development] kallt_kaffe:
How about these lines?

83 #define MSM_PMEM_MDP_BASE 0x17000000
84 #define MSM_PMEM_MDP_SIZE 0x00800000
85
86 #define MSM_PMEM_ADSP_BASE 0x16800000
87 #define MSM_PMEM_ADSP_SIZE 0x00800000

Shouldn't they be adjusted too? Or are they obsolete?

And in the file for Vogue, judging by the looks of the fixup shouldn't the default values be:

static int pmem_size=8;
static int pmem_adsp_size=8;

EDIT: I'll fix the default sizes for the Vogue unless you tell me not to do it.
[Touch CDMA Android Development] kallt_kaffe:
I've updated and pushed both kernel and tinboot. I've flashed and tested Eclair kernel (no extra memory), froyo 320x480 (9Mb extra) and froyo 240x320 (11Mb extra) and it worked fine. Only tested on Kaiser of course but should work on Polaris aswell.

And I really recommend NOT running the compilekaiser script without modifying it first. :eek:

I suppose once we have a new libcamera for Eclair we could remove the specific Froyo version (even though the reasons sticking to Eclair are getting less for each day)
[Touch CDMA Android Development] preardon:
I'm not sure if this is a kernel or ROM issue, so I'll post it in both locations:

Recently, my Vogue has been freezing and displaying kernel text on the screen with no way get out without rebooting. Sometimes the text is backwards, but not all the time. I have only caught it after the fact, as it usually takes place while I'm charging it at night. I haven't had the chance to to try and read the text as I don't have the time to do so before work so I just reboot.

I am using the 7/8/2010 Kernel on a Verizon Vogue running RLS10 of Super Froyo on NAND.
[Touch CDMA Android Development] mnjm9b:
I discovered the same thing last night...

as soon as I disabled compcache it fixed the sdcard problems.
[Touch CDMA Android Development] mrkite38:
I've also experienced this a few times on the newer builds, although not in the last few days. It seemed to me that it was caused by notifications, like unacknowledged sms messages or missed calls.
[Touch CDMA Android Development] derringdo:
I've had this happen to me as well. Sometimes it has the backwards text, sometimes the screen just doesn't power on. I think it's caused by some notification(s) as well. The most recent time it happened, I just received an email to my gmail account.

Editing to say that within the past day, my phone's screen has failed to wake up from sleep about 3-4 times. It seems like the phone is still responding to button presses (long press on camera or red button causes the phone to vibrate as normal, etc) but the screen does not turn on, so I'm forced to soft reset. I'm loving the speed and features of the Fresh Froyo build, but the instability is starting to put me off from using it.
[Touch CDMA Android Development] kallt_kaffe:
I'm trying a 70Mb swap on sd-card parition (not loading compcache kernel modules at all) at the moment to see if the problem is connected to using swap or to using compcache. I'll report back.
[Touch CDMA Android Development] SuperJMN:
Headset working for you?

Hello everyone, I've been trying the latest .NBHs and I always have the same problem: the headset is not working, like if it was disconnected. In some (rare) cases it works, but this happened 2 - 3 times only.

Can somebody check this out? The last kernel that kallt_kaffe build for us (Polaris owners) dated 7/7/2010 is failing, as well as the new ones.
[Touch CDMA Android Development] dzo:
Running from nand or SD?

If you are running from SD it's possible that the SD card power down is the problem. When the device suspends, it turns off power to the sd card and has to rescan when it resumes. This seems to work fine for me when running from nand but with /system on SD it might cause problems. Try booting with

msm_sdcc.vreg_off_on_suspend=0 in cmdline.

Even after boot you can change this setting by doing:

su

echo 0 > /sys/module/msm_sdcc/parameters/vreg_off_on_suspend

in a terminal or from adb
[Touch CDMA Android Development] Gersonian:
Before you get rid of froyo, I suggest going back to the 7/2 kernel. More than likely its not the system, its the latest kernels which have been having some real issues. Remember that these kernels are all test kernels... some more stable than others. If you find one that works well and the next one doesn't its always worth trying to roll back.
[Touch CDMA Android Development] kallt_kaffe:
I've compiled new compcache 0.5.4 modules (attached) against our kernel and I also did the recommended kernelpatching (and pushed the changes). I also pushed the new modules to the Froyo repo.

I'm trying this out right now on Froyo.

You likely will need to compile a new kernel for those modules to work as they expect the kernel to support the swap notify thing...

EDIT: It worked for a while but now the "insert SD card" complaints are back again. I can't see why using compcache would affect this. And the sdcard is still mounted and accessible in the terminal but Music and Camera does not agree.
[Touch CDMA Android Development] kallt_kaffe:
Do you think this could be related to the compcache and SD-card problems? Compcache adds a blockdevice /dev/block/ramzswap0 and perhaps if the SD card is powercycled during sleep something happens that won't happen when /dev/block/ramzswap0 does not exist?

I can't see any other connection between compcache and the sdcard except that they both use block devices.

Maybe some kind of dynamic renumbering that makes the system believe that the SD-card is gone even though it is in fact still mounted.
[Touch CDMA Android Development] SuperJMN:
I also had some problems when I enabled CompCache. Applications like Titanium Backup complained that I didn't have a SD Card. So, yes, it has something to do with it. You're not the one that had problems.

Let me make a question, Kallt_Kaffe: couldn't the swap into the SD Card degrade its life? It could make it useless after some time. Am I wrong?
[Touch CDMA Android Development] kallt_kaffe:
It propably can. But cards are cheap. :cool:

I use an 8Mb card and I made a 70mb partition in the end for swap. If that part get read/write errors after some use I could leave that part unpartitioned and move the swap down and propably enjoy swap on the same SD-card for quite some time. But this time I only used it for testing but if you would want to use it for swap permanently I wouldn't worry to much about it.
[Touch CDMA Android Development] kallt_kaffe:
I've added this to my tinboot.S now and made and flashed a new NBH just to see if it affects the compcache-SD-card-problem.
[Touch CDMA Android Development] derringdo:
Running from SD. I'll try this and see if it helps, thanks!

Edit: didn't help with the strange backwards white text on black screen bug.
[Touch CDMA Android Development] kallt_kaffe:
Actually that did not help but what may have helped is inserting a 2 minute delay in the script that enabled compcache at boot time. It's still to early to be sure but it makes sense, sort of. Propably something with vold needed to be started before ramzswap0 is created or something like that.

I'll give it some time then I'll push a new compcache.sh to the Froyo repo.

EDIT: For the impatient. Add a "sleep 120" before the first insmod in compcache.sh. Still working fine here.
[Touch CDMA Android Development] derringdo:
Here's a picture of the "backwards text" crash that I've been seeing lately. I've mirrored it so you can see what it says more easily (on the left is what I see, the mirrored image is on the right). I have to soft reset after seeing a crash like this because it doesn't respond to anything. Any idea what's going on?
[Touch CDMA Android Development] grktaurus83:
I just had this happen to me today for the first time.

My phone was in the process of waking itself up due to a phone call that was coming in. I know this because 30 seconds before this I had JUST ended a conversation with a friend due to a dropped call (the other person lost service) and they were calling me back.

Either way, I hope that provides some context to where the bug might be.

Furthermore, our screens oftentimes seem to display a momentary "backwards" display (sometimes the colors are even inverted) whenever they wake up just before showing everything correctly. Most people don't notice it because it just flashes by really quickly.

I was always meaning to ask about this. Isn't there any way to avoid this? I mean, the image is correct when the phone goes to sleep, so why does the image get flipped the next time the GUI is brought up? It's almost like the graphics are initialized and some parameters are passed to it afterward that orient the display properly.

Just kind of curious to see if there's an explanation since I don't know how this side of things works.
[Touch CDMA Android Development] kallt_kaffe:
Hmm, I wonder... On my Kaiser (panel1) distorted graphics flash by when it wakes up and sometimes I find it with the backlight on, frozen, showing the distorted graphics. Sounds like it may be the same freeze only that it looks different on different devices and/or panel types. It's does happen often, but it happens.

Once I found it in this state when my son just minutes before had pulled the charger from it. I use the "stay awake when charging" option and I know that when I pull the charger and the phone has been inactive it instantly turns off the display. So just maybe it happens when the phone goes to sleep, rather than when it wakes up.

The times I've found in this state I had not tried to wake it, just pulled it out of the pocket to see garbage graphics and backlight on. But on the other hand it could mean I missed a phone call but I haven't had anyone complaining about not being able to reach me so I'm not so sure about that.
[Touch CDMA Android Development] SuperJMN:
New buttons mapping

POLARIS: With the new buttons layout I can no longer get to the recent programs list because the Power button acts like the End button. Also, going back to Home is not possible before you use Spare Parts to give the End button a new behavior (Home, then sleep).
[Touch CDMA Android Development] l1q1d:
I'm preparing a new button behaviour, i'm waiting for new phone.apk :-)
[Touch CDMA Android Development] osilvan:
Does this change allow to continue hanging up calls with red key?
[Touch CDMA Android Development] l1q1d:
It's only proposal and it is in testing.

The latest kernel has this config:

The end/Home works after spare part end call button modification.
[Touch CDMA Android Development] my2sense:
I've always gotten the backwards text whenever my Vogue wakes up from sleep. It's been doing that with Donut, Eclair, and Froyo from day 1 since I moved to Android in April. I've been flashing to NAND and haven't had a crashed yet.
[Touch CDMA Android Development] dnessl:
compcache, random hangs

(I'm running latest kernel and Inc's Super Froyo RLS10 on a Vogue off of SD card w/ real ext2 partitions ...)

I added the "sleep 120" to compcache.sh and rebooted. The compcache.sh script does a swapon, but the "free" command still shows no swap allocated. (And no /dev/block/ramzswap* device exists.) If I manually invoke compcache.sh it does create the block device and turn on swapping to it. So, compcache.sh isn't being run automatically at boot/init -- how do I enable that? (I don't see the usual SysV-style inittab and runlevel scripts)

I've had random hangs like those described (sometimes every few days, sometimes twice a day) since the Warm Donut, Warm Eclair, and now Super Froyo -- blank screen, but pressing some keys cause the red and green buttons to light up. But the really interesting thing is just figured out is that I still had access to a shell prompt via adb, which would seem to imply that the kernel was still OK, but Android's java environment was out to lunch. (Maybe in a deadlock?) The next time this happens, what should I look for (other than saving the dmesg output)?

-david
[Touch CDMA Android Development] kallt_kaffe:
$ su

# compcache.sh enable

That will set a persistant property that will make sure compcache is always enabled after restarting the phone.

I just had another one of those and I'm found some strange stuff in last_kmsg.
[Touch CDMA Android Development] derringdo:
I know. Normally the most you see of the backwards text is a quick flash, and then the phone goes back to Android. However, this is a crash where the backwards text stays on the screen and you have to soft reset the phone in order to get it working again. Just trying to figure out what is causing these crashes.
[Touch CDMA Android Development] loserskater:
I had some issues that dealt with i2c and I think it might be THIS COMMIT

I'm not entirely sure but I've been trying to get somebody to revert that commit, or atleast the things dealing with i2c, and build a kernel and see if it still happens.
[Touch CDMA Android Development] SuperJMN:
This buttons layout seems to be very useful at the first glance. Will it be an official layout, optional or configurable?
[Touch CDMA Android Development] kallt_kaffe:
Sorry, I haven't been listening. Here you go, I only reverted the changes in the i2c-msm.c files.
[Touch CDMA Android Development] osilvan:
But with this layout, will the red key be used to hang up calls?

Tks
[Touch CDMA Android Development] l1q1d:
No you need to use screen end call button but you can refuse calling with back button.

@SuperJMN it would be official if next version of android use on screen end call button.

Continue this conversation here
[Touch CDMA Android Development] osilvan:
I prefer actual layout. Maybe you could open a poll in polaris forum.
[Touch CDMA Android Development] kallt_kaffe:
I've been using my phone a lot today, lots of gps usage, several calls, web browsing, charging in the car etc... and it has been rock solid. Then I thought, maybe it only happens after using the camera so I turned on the camera once. Within 30 minutes I had another sleep-freeze. And this was with the kernel I posted this morning. May be a coincidence but I thought it would be worth mentioning.
[Touch CDMA Android Development] samjam:
Hmm, I've had some msm messages I don't recall before and boot failures with your latest kernel although it has been working well today till about an hour ago: http://xdaforums.com/showpost.php?p=7158471&postcount=489
[Touch CDMA Android Development] scooter1556:
I think i must just be lucky with my kaiser. I haven't had compcache switched on but i do have a swap partition. I'm running the latest build of Froyo with jit disabled and i have had no lockups at all. In fact i'm really happy. Used GPS, received calls, made calls, sent and received many text messages, browsed the internet, charged randomly, it's rock solid so far and battery life is good. I have no issues with programs not recognising the SD card but i guess that is a compcahce issue.

K_K, what changed are there in the latest kernel other then code changes for the new compcache libs?? Are there any fixes that will benefit users not using compcache?
[Touch CDMA Android Development] taupe47:
With your kaiser, have you any problems with the market on froyo?

I obtain 95 % of the time this error 'download unsuccessful' :-/ but it's only on froyo version !
[Touch CDMA Android Development] samjam:
I've had market problems if I do some other task while market is downloading or installing. So I just let it run to completion before it does something else.

When kaiser froyo was dalvik & jit etc. I always seemed to hang when I had got too many things running. Maybe the oom stuff isn't working too well in all cases...
[Touch CDMA Android Development] scooter1556:
I agree with that, but otherwise i can't say i've had any market issues int erms of downloading updates or installation errors.
[Touch CDMA Android Development] derringdo:
I've been running Froyo with this setting and it seems to have made it a lot more stable. I've been getting calls, text messages, using bluetooth, and I haven't had a crash yet. The battery life seems to be a bit worse now though, should it be that noticeable from preventing the SD card from sleeping?

I'm going to try K_K's zImage with the reverted i2c changes, without the SD power down line to see if this fixes the problem in a different way
[Touch CDMA Android Development] *M*:
I can also generate a crash by turning the volume up & down repetitively, though for general use this crash sometimes happens only when adjusting it once while listening to music or w/e. The phone crashes to the loading animation and loads the OS back up.
[Touch CDMA Android Development] t1mman:
I've got crashes / hangups when using the market for build 07-07 and 08-07 from there

http://it029000.massey.ac.nz/vogue/files/?C=M;O=D

Anyone knows what the 15-07 fixes? Is there a thread for those releases?
[Touch CDMA Android Development] mensa07:
it's in fresh froyo thread