Search results

I'm having trouble with the feature (?), which turns off my DE-JY-UMS01N2 head unit whenever i keep my finger on the screen for a couple of seconds (no matter if I move it around or not). Assuming this is really a feature (I can turn it on the same way), does anybody know how to disable that...

thx!

thx for the rom. is is a known issue, that paid apps are not working? i get an error "can't install to usb or sdcard"?

unfortunately I don't have much time currently, so i'm still using the old kernel myself. Is there any reason you upgraded the kernel as well? Because otherwise you can simply flash the old kernel over the new CM build. It should work just fine.

Maybe. But the dock is connected to the cigarette plug, so there is no usb audio device connected :)

Hm, I think it tries to route sound to a non-existent usb audio device D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb89ab810 identifier _disdev value Speaker D/alsa_ucm( 255): disdev: device Speaker not enabled, no need to disable D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb89ab810...

So the device is not crashing anymore in the car dock, but there is no sound either. Not a big problem for me, because it connects to the bluetooth audio after that anyway. Do you have a suggestion for other settings I could test? Or can I change the setting in android somewhere?

Yes. In general it was causing reboots when using it while multitasking. First we thought it was GPS, because most GPS apps use the gyro as well.

Thanks! Unfortunately the full android build does not work on my system yet, so i will wait until this lands in a nightly before testing it. Do I need to do anything about the patch you submitted for me, besides monitoring it? I do not really care about any rights (bragging or otherwise ;) )...

So, here is the patch I am using. Could maybe intervigil post that for review?

i will try to create a patch in the evening. The changes are rather trivial: i just guarded the power-on and power-off methods with a mutex (no idea if this is allowed in a linux kernel driver though?), and added an exception check when somebody is trying to read data via ioctl while the gyro...

ok, here is a shot at a more proper gyro fix. The gyro will turn off again with this kernel, so it should not impact battery life (not that i did notice a big difference with the previous version). I hope it is as stable as the first try. If this proves to be working - can anybody take this on...

did you try with my experimental kernel?

Sorry to hear that, but my kernel is just supposed to fix the reboots when multi tasking with GPS on (the theory is, that it is not related to GPS but to the Gyro). But as you get no reboots, this is at least good news for me :angel: edit: the funny thing about your log is, that it seems to...

seems to be working quite well here....so, if you are not afraid of fastboot and a little power drain (the gyro will not turn off on this build), feel free to test the attached kernel. I tried some multitasking that would previously reboot my phone reliably....but then again, i might just be...

to me it doesn't seem to be an I2C issue, even though the logs are full of I2C related stuff. I would say that the real problem is that the device that should be on the other side of the I2C is just powered off. I'm trying to build myself a kernel that does not power of the gyro, just for fun :D...

even more strange: it seems that the gyro gets powered off by accident, and then the device becomes totally unresponsive. Sometimes it just reboots, sometimes it manages to power it on. This happens when multi-tasking. e.g.: <6>[ 1494.150373] [TP] Total finger count: 0 <6>[ 1494.823134]...

found the solution, i needed to add ramdiskaddr: mkbootimg --kernel arch/arm/boot/zImage --ramdisk initramfs.cpio.gz --base 0x80400000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=qcom' --ramdiskaddr 0x81a00000 -o my_boot.img

So, as a workaround I built myself a kernel with accessory detection disabled. I can boot the zImage just fine, but i can't flash it with fastboot flash zimage (permission denied) I also tried to build a boot.img, using the current nightly as a base for unmkbootimg and mkbootimg mkbootimg...

Thanks! Does that mean that audio will be routed through USB in that case? Because I don't think that my cigarette plug does audio :eek:

Thanks, it show only the following lines between plugging in and rebooting: D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb8f83188 identifier _disdev value Speaker D/alsa_ucm( 255): disdev: device Speaker not enabled, no need to disable D/alsa_ucm( 255): snd_use_case_set(): uc_mgr...

You are definitely onto something. Not sure how to check the audio routes though. Logcat repeats the following until it dies around 60k lines later: I will gladly assist you in testing the dock - seems nobody else is using it, because its 40 € :) I/ActivityManager( 659): Process...

Ok, I don't know what the current status on the charger-reboot issues is exactly. But here are my observations - if anyone has any suggestions on what I could try - hints are very welcome. I'm an embedded-systems dev (not on linux though), so I can compile my own kernel if necessary. (I'm on a...

Exchanged a black gpad because of a 0.5 inch yellow line at the top of the screen. Don't know the serial number unfortunately. Got a 312 now as replacement. This has the light bleed at the bottom as well. But I have not seen any of the other issues like the blue line or the issue above. The...

Lots of browsers in the market allow you to disable the mobile version. E.g. ics+ browser.

I'm using mantano and am rather satisfied.

Actually, your post sums up my opinion on this matter pretty well.

as was repeatedly stated by the android team, 2D HW acceleration does not automatically translate to awesome, fluid animations. Example: If you scroll through a list, the objects that will be shown next may be generated on the fly. If the creation of the next item takes too long, you will still...

that's why it is called a _preview_ SDK. not all apps are finished, as they most likely finish the tablet layouts first to be able to push out the XOOM as quickly as possibly. But before the final release, those things will have to be cleared up, because devs do not want to use two different...

i have to use a no-audio-boost kernel with my jabra headset, otherwise the call quality is abysmal. lots of metallic clicking and other strange effects going on. but i have seen no differences in the overall connection stability otherwise.

just port the new Dalvik (and maybe the new bluetooth stack - AVRCP 1.3 by an chance?) to CM. everything else i can live without. (and i'm definitely skipping the device, although the touchscreen on the nexus one is driving me nuts from time to time)

thanks a million. i have been waiting for the NOAB version for a long time. great work!

i guess that's because the nexus is no real multi-touch device. and its limited dual touch is way to inaccurate to be of any use to a keyboard. it can't even get the button presses right in FIFA 10 (which only has 2 buttons on one side and a d-pad on the other side of the screen). this might be...

for anyone who wants to buy it from market - give ultra keyboard a try. it can type and swipe, and has a gazillion of options. i for one like it better than swype. only downside is that it does not work with CoPilot...but that may very well be copilots fault.

so where exactly do you think the N1 resp. its components are being built?

that really just depends on when google pushes the sources of 2.2 into AOSP. so chances are that a stock 2.2 will be available sooner than a cyanogen 2.2, but it will be worth the wait :)

battery life is not _horrible_ for me, but it's not great either. i do have the extended 2800 mAh battery from SEIDO, and i manage to get 3 days out of it. now if this were the performance with the stock battery, i would be a happy camper.

the only thing that really annoys me about the phone is battery life. but i guess this is something that no smartphone will do any better in the forseeable future.

i had the hero before, and there it could be a real problem with mp3s. delays could be as long as 5 seconds. oggs otoh would play almost instantly. now i'm using a mp3 on the nexus, and don't notice any real delay. might be .5 seconds, but this is absolutely no problem at all. it might even be...

just in case you didn't know: you can also select "subscribe to thread" from the thread tools menu near the top-right of the page.

i use stock for gmail, and k9 for all other imap accounts.

how hard is this on the battery - do you have to wake up the CPU every time you change the color?

got mine today. tough choice - i think the original form factor is too thin to hold the phone with any kind of comfort. the added 6mm otoh are just a bit too much. i may eventually get used to it, but i think 2 mm less would be perfect for me. so how about a 2400 mAh battery then? :)

The only problem is that those 6 most recent applications are not neccessarily running anymore, so there might be nothing to show.

you guys need to realize how multitasking is done on android. as soon as an application loses the focus, it can and will be closed by android at will. all applications that really run in background are services without any kind of GUI. so for this to happen, android would need to change a...

did you check md5 sum? or did you try to flash the whole zip file, which is a full rom, not an update.zip you can flash from recovery.

any way to auto-activate the car-dock mode? maybe a DIY mod? edit: btw: i had a bad experience with the holder for my hero. to be more exact with the tilt swivel. the screw was too short, and the adhesive was in the wrong place, so it would always unscrew itself and fall of. had to replace it...

as you said, there is no perfect phone. but give it a little time, android is only a year old after all. i for one have little to no problems with FCs from any of the apps i'm using, so it also depends on what you like to do with your phone. my main issue atm. is the lack of good bluetooth...

anyone else with nonfunctional network location (beta4+new radio+new gapps)?

got a crash over night with beta3 (stock .29.6 no-highmem kernel). btw: all .32 kernels suck the life out of my battery in an instant (read: about 10 hours of standby) logs