THREAD CLOSED
20th April 2012, 05:47 PM
Senior Member
Thanks Meter
311
Posts: 1,363
Join Date: Dec 2010
Quote:
Originally Posted by
chicle_11
Try flashing the kupdate kernel, oc'd to 1.7 max, 384 min.
Those are the settings I use and I don't have sound problems. I hope it works for you.
Which app did you use to up your Min clock. I'm wondering if my sounds problems have something to do with that.
Devices:
GINORMOUS Samsung Note II -
WHOMP 2.9
HP Touchpad - Schizoid CM10/AOKP/PA
[deceased]Samsung Epic 4G - CM10 Nightlies
Happy Wife, happy LIFE
20th April 2012, 06:08 PM
Junior Member
Thanks Meter
3
Posts: 24
Join Date: Jan 2011
Quote:
Originally Posted by
chicle_11
Try flashing the kupdate kernel, oc'd to 1.7 max, 384 min.
Those are the settings I use and I don't have sound problems. I hope it works for you.
Tried this and I still have the same issue. I have another logcat here, this time I rebooted the device. Turned on logcat. Let it sleep for 3 minutes and then woke it up and paused the logcat.
Code:
build.board: tenderloin
build.bootloader: unknown
build.brand: generic
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: tenderloin
build.display: IMM76D
build.fingerprint: hp/hp_tenderloin/tenderloin:4.0.4/IMM76D/223971:user/release-keys
build.hardware: tenderloin
build.host: marjory
build.id: IMM76D
build.manufacturer: unknown
build.model: cm_tenderloin
build.product: touchpad
build.radio: unknown
build.serial: 6d2092c8a14f55aa15b6b794e3cdd6a6e1fd97e1
build.tags: test-keys
build.time: 1334763995000
build.type: userdebug
build.user: cm-hudson
version.codename: REL
version.incremental: eng.cm-hudson.20120418.094527
version.release: 4.0.4
version.sdk_int: 15
04-20 19:00:49.289 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:00:49.309 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:73728 offset:18612224 fd:39
04-20 19:00:49.319 D/memalloc(1490): /dev/pmem: Mapped buffer base:0x46e90000 size:18685952 offset:18612224 fd:70
04-20 19:00:49.319 D/ALSAModule(155): open called for devices 00000000 in mode 0...
04-20 19:00:49.349 I/ALSAModule(155): Set global parms
04-20 19:00:49.349 I/ALSAModule(155): Setting interleved PCM
04-20 19:00:49.549 I/ALSAModule(155): Buffer size: 2400, chunk 4800, latency 54421
04-20 19:00:49.549 I/ALSAModule(155): Initialized ALSA PLAYBACK device default
04-20 19:00:49.549 E/AudioHardwareALSA(155): RE-OPEN AFTER STANDBY:: took 262 msecs
04-20 19:00:49.729 D/dalvikvm(1490): GC_CONCURRENT freed 992K, 17% free 6919K/8263K, paused 3ms+5ms
04-20 19:00:51.919 D/dalvikvm(517): GC_FOR_ALLOC freed 278K, 10% free 7375K/8135K, paused 24ms
04-20 19:00:52.739 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:00:52.799 D/memalloc(1490): /dev/pmem: Unmapping buffer base:0x46e90000 size:18685952 offset:18612224
04-20 19:00:53.339 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2dc26000 size:73728 offset:18612224 fd:39
04-20 19:00:56.809 I/lights (221): Disabling touch screen
04-20 19:00:56.809 D/lights (221): Send ts socket 1 byte(s): 'C'
04-20 19:00:56.809 D/ts_srv (148): Socket received 1 byte(s): 'C'
04-20 19:00:56.809 D/ts_srv (148): uart closed: 0
04-20 19:00:56.809 I/ts_power(148): touchscreen_power: enable=0, ts_state=1
04-20 19:00:56.809 I/power (221): *** set_screen_state 0
04-20 19:00:56.809 D/SurfaceFlinger(152): About to give-up screen, flinger = 0xf918
04-20 19:00:56.809 D/Sensors (221): sensor activation called: handle=3, enabled=0********************************
04-20 19:00:56.819 D/Sensors (221): sensor activation called: handle=0, enabled=0********************************
04-20 19:00:56.829 V/TransportControlView(221): Create TCV com.android.internal.widget.TransportControlView@2beba768
04-20 19:00:56.889 D/dalvikvm(221): GC_FOR_ALLOC freed 610K, 13% free 10026K/11463K, paused 44ms
04-20 19:00:56.919 I/CpuGovernorService(221): intent action: android.intent.action.SCREEN_OFF
04-20 19:00:56.979 D/dalvikvm(221): GC_FOR_ALLOC freed 66K, 9% free 10432K/11463K, paused 37ms
04-20 19:00:57.049 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:00:57.089 D/ALSAModule(155): open called for devices 00000000 in mode 0...
04-20 19:00:57.109 D/dalvikvm(221): GC_EXPLICIT freed 21K, 9% free 10493K/11527K, paused 2ms+11ms
04-20 19:00:57.119 I/ALSAModule(155): Set global parms
04-20 19:00:57.119 I/ALSAModule(155): Setting interleved PCM
04-20 19:00:57.119 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:3014656 offset:12582912 fd:39
04-20 19:00:57.139 D/memalloc(221): /dev/pmem: Mapped buffer base:0x4c6b3000 size:15597568 offset:12582912 fd:255
04-20 19:00:57.149 I/TabletStatusBar(354): DISABLE_CLOCK: yes
04-20 19:00:57.179 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:3014656 offset:19005440 fd:43
04-20 19:00:57.189 D/memalloc(221): /dev/pmem: Mapped buffer base:0x4e51e000 size:22020096 offset:19005440 fd:258
04-20 19:00:57.309 I/ALSAModule(155): Buffer size: 2400, chunk 4800, latency 54421
04-20 19:00:57.309 I/ALSAModule(155): Initialized ALSA PLAYBACK device default
04-20 19:00:57.309 E/AudioHardwareALSA(155): RE-OPEN AFTER STANDBY:: took 257 msecs
04-20 19:00:57.359 D/dalvikvm(1490): GC_CONCURRENT freed 239K, 15% free 7081K/8263K, paused 4ms+6ms
04-20 19:00:57.539 D/memalloc(152): /dev/pmem: Allocated buffer base:0x2ca66000 size:3014656 offset:6029312 fd:54
04-20 19:00:57.549 D/memalloc(221): /dev/pmem: Mapped buffer base:0x4d593000 size:9043968 offset:6029312 fd:264
04-20 19:01:00.229 W/ThrottleService(221): unable to find stats for iface rmnet0
04-20 19:01:00.549 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:01:31.889 D/dalvikvm(517): GC_FOR_ALLOC freed 258K, 10% free 7374K/8135K, paused 27ms
04-20 19:03:47.730 I/power (221): *** set_screen_state 1
04-20 19:03:47.760 D/Sensors (221): sensor activation called: handle=3, enabled=1********************************
04-20 19:03:47.770 D/Sensors (221): sensor activation called: handle=0, enabled=1********************************
04-20 19:03:47.800 I/CpuGovernorService(221): intent action: android.intent.action.SCREEN_ON
04-20 19:03:47.800 E/WifiStateMachine(221): set suspend optimizations failed!
04-20 19:03:47.830 I/lights (221): Enabling touch screen
04-20 19:03:47.830 D/lights (221): Send ts socket 1 byte(s): 'O'
04-20 19:03:47.830 D/ts_srv (148): Socket received 1 byte(s): 'O'
04-20 19:03:47.830 I/ts_power(148): touchscreen_power: enable=1, ts_state=0
04-20 19:03:47.830 I/WindowManager(221): Lock screen displayed!
04-20 19:03:48.010 D/SurfaceFlinger(152): Screen about to return, flinger = 0xf918
04-20 19:03:48.030 D/ts_srv (148): uart opened at 15
04-20 19:03:48.150 D/dalvikvm(1490): GC_CONCURRENT freed 365K, 15% free 7105K/8263K, paused 2ms+3ms
04-20 19:03:48.920 D/dalvikvm(517): GC_FOR_ALLOC freed 258K, 10% free 7374K/8135K, paused 34ms
04-20 19:03:49.340 D/OpenGLRenderer(221): Flushing caches (mode 0)
04-20 19:03:49.350 D/memalloc(221): /dev/pmem: Unmapping buffer base:0x4c6b3000 size:15597568 offset:12582912
04-20 19:03:49.350 D/memalloc(221): /dev/pmem: Unmapping buffer base:0x4e51e000 size:22020096 offset:19005440
04-20 19:03:49.350 D/memalloc(221): /dev/pmem: Unmapping buffer base:0x4d593000 size:9043968 offset:6029312
04-20 19:03:49.350 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2d666000 size:3014656 offset:12582912 fd:39
04-20 19:03:49.350 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2d026000 size:3014656 offset:6029312 fd:54
04-20 19:03:49.360 I/ALSAModule(155): ALSA Module: closing down output device
04-20 19:03:49.380 D/dalvikvm(354): GC_CONCURRENT freed 430K, 8% free 7657K/8263K, paused 4ms+1ms
04-20 19:03:49.380 D/ALSAModule(155): open called for devices 00000000 in mode 0...
04-20 19:03:49.400 I/TabletStatusBar(354): DISABLE_CLOCK: no
04-20 19:03:49.410 I/ALSAModule(155): Set global parms
04-20 19:03:49.410 I/ALSAModule(155): Setting interleved PCM
04-20 19:03:49.440 V/TabletStatusBar(354): setLightsOn(true)
04-20 19:03:49.470 I/ALSAModule(155): Buffer size: 2400, chunk 4800, latency 54421
04-20 19:03:49.470 I/ALSAModule(155): Initialized ALSA PLAYBACK device default
04-20 19:03:49.470 E/AudioHardwareALSA(155): RE-OPEN AFTER STANDBY:: took 113 msecs
04-20 19:03:49.500 W/InputManagerService(221): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@2bec6328
04-20 19:03:49.610 D/memalloc(152): /dev/pmem: Freeing buffer base:0x2dc86000 size:3014656 offset:19005440 fd:43
04-20 19:03:52.670 I/ALSAModule(155): ALSA Module: closing down output device
Just taking a wild guess here but it might be this:
Code:
04-20 19:01:00.549 I/ALSAModule(155): ALSA Module: closing down output device
20th April 2012, 10:17 PM
Senior Member
Thanks Meter
197
Posts: 801
Join Date: Jan 2011
Location: Miami, Florida
Quote:
Originally Posted by
MeetFace
Which app did you use to up your Min clock. I'm wondering if my sounds problems have something to do with that.
I use Antutu CPU Master, but I doubt that's the problem. I guess I'm just lucky....
21st April 2012, 08:42 PM
Senior Member
Thanks Meter
26
Posts: 607
Join Date: Sep 2010
Using the 4-20 build and getting lots of force closes. Anyone else seeing this?
Sent from my cm_tenderloin using xda premium
Galaxy Nexus (LTE/CDMA)
Nexus 7
HTC Incredible
HP printer with Zeen Tablet (2.2)
HP touchpads
22nd April 2012, 02:50 AM
(Last edited by bbkmods; 22nd April 2012 at 05:59 AM .)
Junior Member
Thanks Meter
2
Posts: 15
Join Date: Aug 2009
Someone please explain this to me. There are really only two items left to solve on the Touchpad, the audio distortion when display is off and the camera functionality. Having only these two items left, has been like this for sometime now. I see that Classicnerd seems to have solved the audio problem in their Classicnerd-Butta-0.1.0-v4.02.1 . I don't seem to be hearing to much chatter in any of the forums about this, and I believe solving the audio problem throughout ALL the different roms out there should be a big deal. No one seems to care all that much about the camera, which is one of the reasons it hasn't been solved yet. So really the audio fix, for most of us, is the last thing to get worked out and the we can all start enjoying our tablet instead of constantly changing/trying different developer's roms.
22nd April 2012, 12:08 PM
Senior Member
Thanks Meter
197
Posts: 801
Join Date: Jan 2011
Location: Miami, Florida
Quote:
Originally Posted by
bbkmods
Someone please explain this to me. There are really only two items left to solve on the Touchpad, the audio distortion when display is off and the camera functionality. Having only these two items left, has been like this for sometime now. I see that Classicnerd seems to have solved the audio problem in their Classicnerd-Butta-0.1.0-v4.02.1 . I don't seem to be hearing to much chatter in any of the forums about this, and I believe solving the audio problem throughout ALL the different roms out there should be a big deal. No one seems to care all that much about the camera, which is one of the reasons it hasn't been solved yet. So really the audio fix, for most of us, is the last thing to get worked out and the we can all start enjoying our tablet instead of constantly changing/trying different developer's roms.
You forgot the microphone .....
Not everyone has the audio problem. I, for one, don't. I use the unofficial nightly and/or cherry Kang, and have never had sound problems. There are several threads about this. Search and you will find them.
26th April 2012, 01:44 AM
(Last edited by deathsycthehe11; 26th April 2012 at 01:58 AM .)
Member
Thanks Meter
9
Posts: 80
Join Date: Jun 2011
Anybody CM9 reboots a lot by itself? I did a clean install from cm7. I used acmeuninstaller and intall cm9 cleanly. All the files are the newest ones. Now it reboots like every 5 minutes and sometimes even shorter.
I know this use to be a big bug in the early builds. Just wondering if it still happens to other people or just me.
26th April 2012, 02:19 AM
Senior Member
Thanks Meter
8
Posts: 117
Join Date: Sep 2007
April 16th nightly works fine for me.
Quote:
Anybody CM9 reboots a lot by itself? I did a clean install from cm7. I used acmeuninstaller and intall cm9 cleanly. All the files are the newest ones. Now it reboots like every 5 minutes and sometimes even shorter.
I know this use to be a big bug in the early builds. Just wondering if it still happens to other people or just me.
Sent from my cm_tenderloin using Tapatalk
26th April 2012, 03:38 AM
Senior Member
Thanks Meter
4
Posts: 263
Join Date: Aug 2010
How can I get it read my HP on computer? I have all drivers installed .
Sent from my SPH-D710 using xda premium
26th April 2012, 12:54 PM
Senior Member
Thanks Meter
582
Posts: 2,028
Join Date: Mar 2011
Location: Heredia
DONATE TO ME
Quote:
Originally Posted by
zedmay
How can I get it read my HP on computer? I have all drivers installed .
Sent from my SPH-D710 using xda premium
If you had all the proper drivers installed then your computer would recognize your TouchPad
Sent from my cm_tenderloin using Tapatalk 2
THREAD CLOSED
Thread Tools
Search this Thread
Display Modes
Linear Mode
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
Go to top of page...
Most Thanked In This Thread
22 Well guys.. it's been a
fun ride, but … 18 Due to all the merges
today we now have … 11 Sorry guys, I was out of
town this … 9 So jcsullins has been hard
at work (as … 7 Morning.. there we some
changes being …