Linux/Android on CDMA Touch Pro -- Now working on Verizon! And with GPS!

[Squirrels]

I have issues with my sound working even with making a phone call prior to launching Haret, however I may have found some useful data on the issue via dmesg. Fairly big copy and paste but yeah...

[ 0.742950] WARNING: at fs/sysfs/dir.c:463 sysfs_add_one+0x34/0x48()
[ 0.743011] sysfs: duplicate filename 'snd' can not be created
[ 0.743072] Modules linked in:
[ 0.743103] [<c026826c>] (dump_stack+0x0/0x14) from [<c0053ff4>] (warn_slowpath+0x64/0x80)
[ 0.743255] [<c0053f90>] (warn_slowpath+0x0/0x80) from [<c00eb628>] (sysfs_add_one+0x34/0x48)
[ 0.743377] r3:d583d7a0 r2:c02d9a45
[ 0.743408] r6:d583efa0 r5:d583c6f8 r4:ffffffef
[ 0.743469] [<c00eb5f4>] (sysfs_add_one+0x0/0x48) from [<c00ebcf8>] (create_dir+0x58/0xa4)
[ 0.743591] r5:d583c6f8 r4:d581fdf0
[ 0.743652] [<c00ebca0>] (create_dir+0x0/0xa4) from [<c00ebd88>] (sysfs_create_dir+0x44/0x64)
[ 0.743743] r8:d580a2e8 r7:00000003 r6:00000000 r5:00000000 r4:d583efa0
[ 0.743835] [<c00ebd44>] (sysfs_create_dir+0x0/0x64) from [<c0127228>] (kobject_add_internal+0xec/0x1c0)
[ 0.743957] r4:d583efa0
[ 0.744018] [<c012713c>] (kobject_add_internal+0x0/0x1c0) from [<c01273dc>] (kobject_add_varg+0x40/0x50)
[ 0.744140] r9:00000059 r8:00000004 r7:00000003 r6:00000000 r5:00000000
[ 0.744201] r4:d583efa0
[ 0.744232] [<c012739c>] (kobject_add_varg+0x0/0x50) from [<c0127428>] (kobject_init_and_add+0x3c/0x44)
[ 0.744354] r7:00000003 r6:d581fef3 r5:d583efa0 r4:00000000
[ 0.744445] [<c01273f0>] (kobject_init_and_add+0x4/0x44) from [<c0012e50>] (kernel_param_sysfs_setup+0x68/0xe0)
[ 0.744598] r5:00000003 r4:d583efa0
[ 0.744628] [<c0012de8>] (kernel_param_sysfs_setup+0x0/0xe0) from [<c0012fdc>] (param_sysfs_init+0x114/0x1b4)
[ 0.744750] [<c0012ec8>] (param_sysfs_init+0x0/0x1b4) from [<c00272c4>] (do_one_initcall+0x54/0x180)
[ 0.744903] [<c0027270>] (do_one_initcall+0x0/0x180) from [<c00085c8>] (kernel_init+0x84/0xf8)
[ 0.744995] r8:00000000 r7:00000000 r6:00000000 r5:00000000 r4:c0021780
[ 0.745086] [<c0008544>] (kernel_init+0x0/0xf8) from [<c00575c4>] (do_exit+0x0/0x794)
[ 0.745208] r4:00000000
[ 0.745300] ---[ end trace 1b75b31a2719ed1c ]---
[ 0.745361] kobject_add_internal failed for snd with -EEXIST, don't try to register things with the same name in the same directory.
[ 0.745452] [<c026826c>] (dump_stack+0x0/0x14) from [<c01272b4>] (kobject_add_internal+0x178/0x1c0)
[ 0.745605] [<c012713c>] (kobject_add_internal+0x0/0x1c0) from [<c01273dc>] (kobject_add_varg+0x40/0x50)
[ 0.745727] r9:00000059 r8:00000004 r7:00000003 r6:00000000 r5:00000000
[ 0.745788] r4:d583efa0
[ 0.745819] [<c012739c>] (kobject_add_varg+0x0/0x50) from [<c0127428>] (kobject_init_and_add+0x3c/0x44)
[ 0.745941] r7:00000003 r6:d581fef3 r5:d583efa0 r4:00000000
[ 0.746032] [<c01273f0>] (kobject_init_and_add+0x4/0x44) from [<c0012e50>] (kernel_param_sysfs_setup+0x68/0xe0)
[ 0.746154] r5:00000003 r4:d583efa0
[ 0.746215] [<c0012de8>] (kernel_param_sysfs_setup+0x0/0xe0) from [<c0012fdc>] (param_sysfs_init+0x114/0x1b4)
[ 0.746337] [<c0012ec8>] (param_sysfs_init+0x0/0x1b4) from [<c00272c4>] (do_one_initcall+0x54/0x180)
[ 0.746429] [<c0027270>] (do_one_initcall+0x0/0x180) from [<c00085c8>] (kernel_init+0x84/0xf8)
[ 0.746551] r8:00000000 r7:00000000 r6:00000000 r5:00000000 r4:c0021780
[ 0.746643] [<c0008544>] (kernel_init+0x0/0xf8) from [<c00575c4>] (do_exit+0x0/0x794)
[ 0.746734] r4:00000000
[ 0.746795] Module 'snd' failed to be added to sysfs, error number -17
[ 0.746856] The system will be unstable now.

[hotwired34]

In previous builds, I was able to get Voice Dialer to start by holding the phone button in for a few secs. Now when I do that, the Bluetooth Voice Dialer opens instead. Is there any way to re-map the button back to Voice Dialer? I tried looking within the forums, but was unable to find anyting on that.

Thanks in advance for any assistance.

[makkonen]

Squirrel: That's interesting. Does sound consistently not work for you, or just intermittently? I don't know what else would be populating that spot in sysfs, and I never had consistent problems with sound working.

hotwired34: Sorry, I have no idea. I never had much luck with the voice dialer, so I didn't pay too much attention. And I'm not really sure where the settings for that long press are stored. I suspect it's somewhere fairly high-level within Android, but I don't have a specific location to check.

[Squirrels]

I have tried many builds (in versions 2.1 and 2.2) from June to now occasionally and I have had sound work maybe 3 times total out of the dozens of times I've loaded it; that error is the only thing I've noticed in my limited search for an answer.

I wanted to originally 'cat /var/log/syslog' but /var/log doesnt exist so I went with the only other option i could think, that being dmesg. I had found that error and I started to wonder, hmm could module 'snd' not being loaded be the cause of my sound issues? :P

On an additional side note, idk how to bring up the pipe symbol ("|") or (">") to feed output to file so I had to use Androids 'mail to' option for Terminal Emulator.

[bechard]

Good day good sirs.

Is it possible to increase the touch sensitivity for the 2.2 build? I've got 2.2 running quite well (appbrain+fast web installer = gold) and my only problem seems to be that I need to push a lot harder for Android than I do for WinMo.

I'm currently using the latest AIO, but with a new initrd, kernel, modules, rootfs, and system, so...basically upgraded mostly everything now that I think about it.

[joeyz34]

so currently running the newest package with no problems from the SD card... i keep seeing lots of mentioning of partitioning and running from an ext2 partition... what is the benefit of doing that vs just running it from the sd card whenever i want to play with android?

[Squirrels]

this is a link to a full log of a second dmesg I ran after attempting to change ringtone, after a fresh boot (only tried to change ring tone to see what error was thrown out into dmesg when it tried to play the preview for the ringtone).

http://burst.neonblu.com/xda_dmesg_090110.log

[makkonen]

Originally Posted by Squirrels

I have tried many builds (in versions 2.1 and 2.2) from June to now occasionally and I have had sound work maybe 3 times total out of the dozens of times I've loaded it; that error is the only thing I've noticed in my limited search for an answer.

I wanted to originally 'cat /var/log/syslog' but /var/log doesnt exist so I went with the only other option i could think, that being dmesg. I had found that error and I started to wonder, hmm could module 'snd' not being loaded be the cause of my sound issues? :P

On an additional side note, idk how to bring up the pipe symbol ("|") or (">") to feed output to file so I had to use Androids 'mail to' option for Terminal Emulator.

That's really strange. I haven't heard of anyone else who has had such consistent issues with the audio. I've had it fail to come up maybe 1 in 10 times, but never more than that. I wonder if you have something running at startup in WinMo that's monopolizing the hardware, and causing the init in linux to get confused. That's the only place I can think of where something in your setup would differ.

Originally Posted by bechard

Good day good sirs.

Is it possible to increase the touch sensitivity for the 2.2 build? I've got 2.2 running quite well (appbrain+fast web installer = gold) and my only problem seems to be that I need to push a lot harder for Android than I do for WinMo.

I'm currently using the latest AIO, but with a new initrd, kernel, modules, rootfs, and system, so...basically upgraded mostly everything now that I think about it.

There is, as far as I know, no way to change the touch sensitivity. Android doesn't seem particularly well-suited to working with resistive touchscreens in the first place, and this is probably exacerbated by the hacked together drivers we're using. You can see the problem if you play around with the pointer location tool in dev-tools. All the information about pressure is just tossed out -- it doesn't quite line up with the resistive touchscreen driver we've got (or, really, with the general operating method of resistive touchscreens).

Originally Posted by joeyz34

so currently running the newest package with no problems from the SD card... i keep seeing lots of mentioning of partitioning and running from an ext2 partition... what is the benefit of doing that vs just running it from the sd card whenever i want to play with android?

running from an ext2 partition on your sd card was claimed to lead to faster operation. I never found that to be the case. It also allowed for utilizing USB Mass Storage mode for the rest of the sd card (though whether that would actually work, I'm not sure), as well as modifying the files in /system without compiling a new package.

Unless you have some specific need, the effort to do it is not sufficiently rewarded.

On the other hand, the TP2 forum has a some movement lately on partitioning and running from the internal NAND storage. That would totally wipe out Windows Mobile, lead to a further speed increase (if in nothing else, just in startup), and make the whole thing feel a lot nicer.

However, it's got about half a dozen showstopping problems, like no USB, no audio, no 3d, etc.... things that are expected when you no longer have windows mobile initializing the devices, but make it not quite usable yet.

[Squirrels]

idk, I don't see any weird processes running on startup, hell im not even running titanium, im using the old old winmo interface with just "Date" and "Messaging", its almost (some regedits and apps installed) a stock rom from nrgz28. but i posted this over at xda as well, hopefully someone knows. I'll try booting up into winmo and killing anything off thats non critical and then making a call and trying to boot xdandroid.

[makkonen]

Have you tried not making a call before booting? That hasn't been necessary for most people for months. (But, clearly, you've got problems that aren't affecting most people.)