FORUMS
Remove All Ads from XDA

Linux and Android for Vogue [kernel thread]

2,478 posts
Thanks Meter: 5,055
 
By dzo, Senior Recognized Developer on 3rd April 2008, 11:28 PM
Post Reply Email Thread
9th June 2010, 12:33 PM |#5371  
Senior Member
Thanks Meter: 1,173
 
Donate to Me
More
Latest code also causes freeze when turning on bluetooth (once again, Kaiser with Myns Warm Eclair).

last_kmsg says this:
Bluetooth 1
High Speed
clk_set_rate 34:1843200
clk_set_rate 34:1843200
clk_set_rate 34:1843200
clk_set_rate 34:1843200
9th June 2010, 12:49 PM |#5372  
dzo's Avatar
OP Senior Recognized Developer
Flag Auckland
Thanks Meter: 5,055
 
Donate to Me
More
I see the problem, I had forgotten to update the defconfig. It needs unsafe resume enabled or it doesn't power up the card. I don't know about BT, that may still be broken. The wifi driver might also need to be recompiled.
9th June 2010, 02:25 PM |#5373  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by kallt_kaffe

Continued:

Code:
[  227.452443] RTC Update
[  227.452588] Modem Status:
[  227.452948] RTC Resume: Current time=6:31:36
[  227.453662] Slept for 15 seconds
[  227.454230] msmrtc_resume: alarm=1276065096, now=1276065096
[  227.454398] msm_rtc: Generating alarm event (src 2)
[  227.454660] hw3d_resume: resuming
[  227.470173] SDCC Resume
[  227.480170] SDCC Resume
[  227.481875] Restarting tasks ... done.
[  227.547443] ds2746: 4062mV -62mA charge: 93/100 (4032 units)
[  227.547497]         aux0: 262 (1454) aux1: 17 (80)
[  227.620437] android_power_suspend: exit suspend, ret = 0 (2010-06-09 06:31:36.668633333 UTC)
[  227.630680] active wake lock android_alarm_rtc, time left 70
[  227.666972] android_power_suspend: enter suspend
[  227.670878] PM: Syncing filesystems ... done.
[  227.708462] Freezing user space processes ... (elapsed 0.00 seconds) done.
[  227.718765] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[  227.722198] TS Suspend
[  227.723375] RTC Suspend: Current time=6:31:36
[  227.724867] Wake up in 19 seconds
[  227.724867] timer 0: val=320c, alarm=d, enable=1
[  227.724867] timer 1: val=93db60, alarm=949980, enable=1
[  227.724867] msm_pm_collapse(): returned 1
[  227.724867] timer restore 0 val=12812 vtime=13 sleep_time=0
[  227.724867] timer restore 1 val=9689952 vtime=9738624 sleep_time=0
[  227.724867] RTC Update
[  227.725012] Modem Status:
[  227.725415] RTC Resume: Current time=6:31:55
[  227.726137] Slept for 19 seconds
[  227.726768] msmrtc_resume: alarm=1276065115, now=1276065115
[  227.726937] msm_rtc: Generating alarm event (src 2)
[  227.728108] hw3d_resume: resuming
[  227.750170] SDCC Resume
[  227.760432] SDCC Resume
[  227.762255] Restarting tasks ... done.
[  227.888650] android_power_suspend: exit suspend, ret = 0 (2010-06-09 06:31:55.625978334 UTC)
[  227.900620] active wake lock android_alarm, time left 499
[  228.280973] Buffer I/O error on device mmcblk0p1, logical block 980674
[  228.290328] lost page write due to I/O error on mmcblk0p1
[  228.300430] Buffer I/O error on device mmcblk0p1, logical block 980675
[  228.310275] lost page write due to I/O error on mmcblk0p1
[  228.320358] Buffer I/O error on device mmcblk0p1, logical block 980676
[  228.330370] lost page write due to I/O error on mmcblk0p1
[  228.340318] Buffer I/O error on device mmcblk0p1, logical block 980677
[  228.350302] lost page write due to I/O error on mmcblk0p1
[  228.370462] Buffer I/O error on device mmcblk0p1, logical block 980680
[  228.390378] lost page write due to I/O error on mmcblk0p1
[  228.400407] Buffer I/O error on device mmcblk0p1, logical block 980681
[  228.410265] lost page write due to I/O error on mmcblk0p1
[  228.430737] Buffer I/O error on device mmcblk0p1, logical block 980722
[  228.440285] lost page write due to I/O error on mmcblk0p1
[  228.450333] Buffer I/O error on device mmcblk0p1, logical block 980723
[  228.480410] lost page write due to I/O error on mmcblk0p1
[  228.490507] Buffer I/O error on device mmcblk0p1, logical block 981196
[  228.500542] lost page write due to I/O error on mmcblk0p1
[  228.520330] Buffer I/O error on device mmcblk0p1, logical block 981197
[  228.530258] lost page write due to I/O error on mmcblk0p1
[  228.542838] android_power_suspend: enter suspend
[  228.560360] PM: Syncing filesystems ... done.
[  228.638625] Freezing user space processes ... (elapsed 0.01 seconds) done.
[  228.649157] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[  228.653830] TS Suspend
[  228.655002] RTC Suspend: Current time=6:31:56
[  228.656540] Wake up in 18 seconds
[  228.656540] timer 0: val=80c4, alarm=d, enable=1
[  228.656540] timer 1: val=14efba0, alarm=14f5160, enable=1
[  228.656540] msm_pm_collapse(): returned 1
[  228.656540] timer restore 0 val=32964 vtime=13 sleep_time=0
[  228.656540] timer restore 1 val=21953440 vtime=21975392 sleep_time=0
[  228.656540] RTC Update
[  228.656683] Modem Status:
[  228.657048] RTC Resume: Current time=6:32:14
[  228.657812] Slept for 18 seconds
[  228.658380] msmrtc_resume: alarm=1276065134, now=1276065134
[  228.658548] msm_rtc: Generating alarm event (src 2)
[  228.661235] hw3d_resume: resuming
[  228.680175] SDCC Resume
[  228.690168] SDCC Resume
[  228.692007] Restarting tasks ... done.
[  228.860985] android_power_suspend: exit suspend, ret = 0 (2010-06-09 06:32:14.667503334 UTC)
[  228.872273] active wake lock PowerManagerService
[  228.880125] active wake lock android_alarm_rtc, time left 70
[  228.891872] ds2746: 4065mV -84mA charge: 93/100 (4030 units)
[  228.891927]         aux0: 267 (1494) aux1: 16 (70)
[  230.799855] select 920 (ndroid.calendar), adj 14, size 4311, to kill
[  230.800384] send sigkill to 920 (ndroid.calendar), adj 14, size 4311
[  235.511177] ds2746: 4045mV -211mA charge: 93/100 (4030 units)
[  235.511234]         aux0: 266 (1481) aux1: 15 (70)
[  235.991029] printk: 22 messages suppressed.
[  236.020749] Buffer I/O error on device mmcblk0p1, logical block 980674
[  236.040412] lost page write due to I/O error on mmcblk0p1
[  238.530714] select 934 (d.process.acore), adj 14, size 4910, to kill
[  238.540245] send sigkill to 934 (d.process.acore), adj 14, size 4910
[  239.597530] printk: 55 messages suppressed.
[  239.604310] Buffer I/O error on device mmcblk0p1, logical block 554498
[  239.630434] lost page write due to I/O error on mmcblk0p1
[  239.650952] android_power_suspend: enter suspend
[  239.661352] PM: Syncing filesystems ... done.
[  239.788624] Freezing user space processes ... (elapsed 0.00 seconds) done.
[  239.798772] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[  239.802685] TS Suspend
[  239.803867] RTC Suspend: Current time=6:32:25
[  239.805432] Wake up in 19 seconds
[  239.805432] timer 0: val=597ad, alarm=d, enable=1
[  239.805432] timer 1: val=d6cd060, alarm=d6d83a0, enable=1
[  239.805432] msm_pm_collapse(): returned 1
[  239.805432] timer restore 0 val=366509 vtime=13 sleep_time=0
[  239.805432] timer restore 1 val=225235040 vtime=225280928 sleep_time=0
[  239.805432] RTC Update
[  239.805574] Modem Status:
[  239.805934] RTC Resume: Current time=6:32:44
[  239.806677] Slept for 19 seconds
[  239.807242] msmrtc_resume: alarm=1276065164, now=1276065164
[  239.807412] msm_rtc: Generating alarm event (src 2)
[  239.808472] hw3d_resume: resuming
[  239.830417] SDCC Resume
[  239.840194] SDCC Resume
[  239.842094] Restarting tasks ... done.
[  239.871049] ds2746: 4062mV -71mA charge: 93/100 (4029 units)
[  239.871099]         aux0: 269 (1507) aux1: 17 (80)
[  239.971192] android_power_suspend: exit suspend, ret = 0 (2010-06-09 06:32:44.654933333 UTC)
[  239.990312] active wake lock android_alarm_rtc, time left 70
[  240.213467] android_power_suspend: enter suspend
[  240.220437] PM: Syncing filesystems ... done.
[  240.278977] Freezing user space processes ... (elapsed 0.00 seconds) done.
[  240.289380] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[  240.293379] TS Suspend
[  240.294549] RTC Suspend: Current time=6:32:45
[  240.296069] Wake up in 17 seconds
[  240.296069] timer 0: val=3b1a, alarm=d, enable=1
[  240.296069] timer 1: val=151afa0, alarm=1523700, enable=1
[  240.296069] msm_pm_collapse(): returned 1
[  240.296069] timer restore 0 val=15130 vtime=13 sleep_time=0
[  240.296069] timer restore 1 val=22130592 vtime=22165248 sleep_time=0
[  240.296069] RTC Update
[  240.296212] Modem Status:
[  240.296575] RTC Resume: Current time=6:33:2
[  240.297302] Slept for 17 seconds
[  240.297879] msmrtc_resume: alarm=1276065182, now=1276065182
[  240.298049] msm_rtc: Generating alarm event (src 2)
[  240.300765] hw3d_resume: resuming
[  240.320177] SDCC Resume
[  240.330440] SDCC Resume
[  240.332279] Restarting tasks ... done.
[  240.510712] android_power_suspend: exit suspend, ret = 0 (2010-06-09 06:33:02.677518334 UTC)
[  240.522780] ds2746: 4062mV -63mA charge: 93/100 (4028 units)
[  240.522835]         aux0: 270 (1507) aux1: 16 (70)
[  240.540375] active wake lock PowerManagerService
[  241.265757] ds2746: 4052mV -165mA charge: 93/100 (4028 units)
[  241.265812]         aux0: 270 (1507) aux1: 16 (70)
[  243.665635] ds2746: 4052mV -162mA charge: 93/100 (4027 units)
[  243.665690]         aux0: 270 (1507) aux1: 16 (70)
[  245.975460] ds2746: 4052mV -156mA charge: 93/100 (4026 units)
[  245.975512]         aux0: 270 (1507) aux1: 16 (70)
[  247.475654] ds2746: 4047mV -162mA charge: 93/100 (4026 units)
[  247.475707]         aux0: 271 (1520) aux1: 16 (70)
[  248.966329] ds2746: 4050mV -161mA charge: 93/100 (4025 units)
[  248.966381]         aux0: 271 (1520) aux1: 16 (70)
[  250.425723] ds2746: 4050mV -162mA charge: 93/100 (4024 units)
[  250.425778]         aux0: 271 (1520) aux1: 16 (70)
[  252.125729] ds2746: 4050mV -161mA charge: 93/100 (4023 units)
[  252.125784]         aux0: 271 (1520) aux1: 16 (70)
[  253.635609] ds2746: 4050mV -156mA charge: 93/100 (4023 units)
[  253.635664]         aux0: 271 (1520) aux1: 16 (70)
[  253.797766] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.823636] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.851026] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.871526] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.903549] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.929496] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.951438] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  253.983091] EXT2-fs error (device loop0): ext2_get_inode: unable to read inode block - inode=28673, block=114691
[  254.720689] printk: 59 messages suppressed.
[  254.730743] Buffer I/O error on device mmcblk0p1, logical block 554498
[  254.741023] lost page write due to I/O error on mmcblk0p1
[  254.750366] Buffer I/O error on device mmcblk0p1, logical block 554499
[  254.760224] lost page write due to I/O error on mmcblk0p1
[  255.365633] ds2746: 4047mV -162mA charge: 93/100 (4022 units)
[  255.365685]         aux0: 271 (1520) aux1: 16 (70)
Maybe it works better for NAND users?

I'm also getting it from NAND
9th June 2010, 03:26 PM |#5374  
Senior Member
Thanks Meter: 1,173
 
Donate to Me
More
Quote:
Originally Posted by dzo

I see the problem, I had forgotten to update the defconfig. It needs unsafe resume enabled or it doesn't power up the card. I don't know about BT, that may still be broken. The wifi driver might also need to be recompiled.

Yes, resume works again. BT still broken. Wifi seems to be working.

EDIT: last_kmsg after a BT freeze looks exactly like last time (se above)
9th June 2010, 09:52 PM |#5375  
Dukenukemx's Avatar
Senior Member
Flag Jersey
Thanks Meter: 47
 
More
Had a problem today where talking on the phone cut out any audio. Both me and the other person couldn't hear each other. This is the second time this happened, and both were long over an hour conversations. Had to restart to fix it.
12th June 2010, 02:12 AM |#5376  
wdbanks's Avatar
Senior Member
Thanks Meter: 5
 
More
Another Vogue Bites The Dust..
Hey DZO,

I wanna thank you for all your hard work and contribution to this community of vogue lovers. Mine died the other day and I found a Samsung Moment real cheap on craigslist so I wont be using your great work anymore. I guess another vogue bites the dust (ala Queen...lol)

Just wanted to say thanks. Anyone need a vogue let me pm me. I got my hands on one through ebay before I found my Moment.

Best wishes!
16th June 2010, 01:39 AM |#5377  
Betho180's Avatar
Senior Member
Flag Unkonw
Thanks Meter: 6
 
More
thanks a lot
16th June 2010, 04:21 AM |#5378  
dzo's Avatar
OP Senior Recognized Developer
Flag Auckland
Thanks Meter: 5,055
 
Donate to Me
More
I've rewritten the touchscreen driver and now vogue, kaiser and polaris all share the same driver, the old driver was horrible! I also made some panel changes to vogue and polaris which save lots of power during suspend on my pola200. Audio input is still broken on kaiser and polaris. New NBHs for all devices are on my site.
16th June 2010, 04:26 AM |#5379  
JM-PDA's Avatar
Senior Member
Flag Sacramento, CA
Thanks Meter: 62
 
More
Thumbs up
Quote:
Originally Posted by dzo

I've rewritten the touchscreen driver and now vogue, kaiser and polaris all share the same driver, the old driver was horrible! I also made some panel changes to vogue and polaris which save lots of power during suspend on my pola200. Audio input is still broken on kaiser and polaris. New NBHs for all devices are on my site.

Dzo,
Downloading now.
Thank you very much ! ! !
16th June 2010, 05:16 AM |#5380  
myn's Avatar
Retired Senior Recognized Developer
Thanks Meter: 4,003
 
Donate to Me
More
Quote:
Originally Posted by dzo

I've rewritten the touchscreen driver and now vogue, kaiser and polaris all share the same driver, the old driver was horrible! I also made some panel changes to vogue and polaris which save lots of power during suspend on my pola200. Audio input is still broken on kaiser and polaris. New NBHs for all devices are on my site.


Hey dzo,

I just gave zImage-16-06-10 a try.

It seems as though the touch input isn't as sensitive and responsive as it was previously for me on the vogue using Warm Eclair.

It seemed as though upon rebooting into Android the first minute of use the touch input was not responding. I let it sit and it got better but it still seems a little off. I find myself tapping on things I didn't mean to touch and double tapping things that didn't activate. For example the notification bar seems harder to pull down now. I used to be able to flick it down really fast. I find myself having to click on the home screen launcher and keys on the keyboard multiple times to activate them.

I'd love to hear other peoples experiences with the new touchscreen driver.
16th June 2010, 05:27 AM |#5381  
Dukenukemx's Avatar
Senior Member
Flag Jersey
Thanks Meter: 47
 
More
Quote:
Originally Posted by dzo

I've rewritten the touchscreen driver and now vogue, kaiser and polaris all share the same driver, the old driver was horrible! I also made some panel changes to vogue and polaris which save lots of power during suspend on my pola200. Audio input is still broken on kaiser and polaris. New NBHs for all devices are on my site.

Awesome, but what do you mean audio input is broken still?
Post Reply Subscribe to Thread

Tags
android, linux, vogue

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes