Which app did you use to up your Min clock. I'm wondering if my sounds problems have something to do with that.
[ROM] TouchPad UNOFFICIAL CM9 Nightly Builds [DISCONTINUED]
- Thread starter eyeballer
- Start date
- Status
Which app did you use to up your Min clock. I'm wondering if my sounds problems have something to do with that.
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 deviceJust 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
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.
Last edited:
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.
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.
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.
Last edited:
Z
zedmay
Guest
How can I get it read my HP on computer? I have all drivers installed .
Sent from my SPH-D710 using xda premium
Sent from my SPH-D710 using xda premium
cdzo72
Senior Member
If you had all the proper drivers installed then your computer would recognize your TouchPad
Sent from my cm_tenderloin using Tapatalk 2
Make sure in that in settings > storage, on the upper right (USB computer connection ), under the 3 dashes, you have media device (MTP) checked.
Quick question from a noob,
I have four hp touchpads, all of them using CM9 nightly, I will like to keep them all the same, meaning apps, accounts, etc.
The question
Can I create a backup, copy it to all pads and then restore, will it work?
I have four hp touchpads, all of them using CM9 nightly, I will like to keep them all the same, meaning apps, accounts, etc.
The question
Can I create a backup, copy it to all pads and then restore, will it work?
Although I haven't done it, I do not see why not. Have the same version cwm installed on your TP'S, make a nandroid (cwm backup) and copy that to all of them, then restore. It should work.
So, only me is having reboot problems? Hmm, I going to try a clean install thru CWM this time then.
I did that when I had 3 TPads, before I sold the extra 2 to friends and family. So yes, there should be no problem, although if you are just flashing a nightly I'm not sure which is easier, i.e.,
flashing one nightly, making a nandroid, then flashing 3 nandroids.
vs
flashing 4 nightlies and then making one nandroid as a backup for all.
Guess it really depends on what new apps are being installed or if you are updating any apps in the process.
Last edited:
Thanks Q.a.T
Im just trying to make sure all pads have the same apps and accounts, and look and act the same at all times. But thanks for the observation. Im glad to know it might work.
Im just trying to make sure all pads have the same apps and accounts, and look and act the same at all times. But thanks for the observation. Im glad to know it might work.
And incremental updates are live! Update Goo Manager in the play store (v2.0.4).
Currently incremental updates will ONLY be offered by the app when attempting to update from the previous night's build. If you miss a night, you'll have to flash the full rom, then incrementals will be available again. Incremental updates are 35-40mb (depending on how much changes of course) vs a full 120mb nightly. They also don't format /system each flash like a full rom does. So faster downloads, faster flashes and less wear on the flash memory of your device.
Please note:
1) This feature is still experimental, please let me know if you hit any issues.
2) Incremental updates will work with CWM but require handing off or manually flashing. If you use TWRP the updates happen at the press of a button.. TWRP offers the best user experience. You can install TWRP via goo manager by going to menu-install openscriptrecovery.
Huge huge thanks to s0up for making this possible!
Currently incremental updates will ONLY be offered by the app when attempting to update from the previous night's build. If you miss a night, you'll have to flash the full rom, then incrementals will be available again. Incremental updates are 35-40mb (depending on how much changes of course) vs a full 120mb nightly. They also don't format /system each flash like a full rom does. So faster downloads, faster flashes and less wear on the flash memory of your device.
Please note:
1) This feature is still experimental, please let me know if you hit any issues.
2) Incremental updates will work with CWM but require handing off or manually flashing. If you use TWRP the updates happen at the press of a button.. TWRP offers the best user experience. You can install TWRP via goo manager by going to menu-install openscriptrecovery.
Huge huge thanks to s0up for making this possible!
Just tried to update from 0428 goo says there's an update and downloads the full 0429 rom and not an incremental, I am using the latest goo manager 2.0.4 and it doesn't give any option of incremental updates am I missing something, after updating goo I rebooted and wiped the caches.
After downloading goo gives an error, md5 checksum mismatch, tried 5 times so far.
Edit: finally downloaded but not an incremental update but a full 114.2mb one
Last edited:
I have the same issue with the incremental updates. It worked yesterday when I went from 27 to 28 but only the full ROM is showing up for 29.
- Status
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
546/27/12: Unofficial nightlies are discontinued: http://xdaforums.com/showthread.php?p=27955579#post27955579
This is a centralized thread to discuss any issues pertaining to my unofficial nightly cm9 builds. As Dalingrin stated, he doesn't plan to release many more Alphas for now unless there's a major change to test so this will be the best way to get the latest CM9 additions (other than building yourself!).
You should only need to wipe caches coming from a previous cm9 build. Remember, these are not tested builds, simply latest source, so there's a chance of "broken" builds as new features are merged in. Always keep a recent backup and/or be willing to do a full wipe. If you're coming from CM7 you should wipe /data if installing in CWM or use ACMEinstaller2 - see the original CM9 Alpha thread.
These builds are mostly a straight sync from source each night, no other extra modifications have been made (other than fixes to ensure is builds). You can find the latest merges into CM9 here: http://tinyw.in/cm9tpmerged (thanks jcsullins for the custom search). The build is sync'd at approx 4am EST and will be ready to download at approx 4.15am EST.
Downloads
There are multiple ways to get the nightlies:
1) Simply browse and find the latest build directly on our host: http://techerrata.co...angs/tenderloin
2) For live announcement of a new nightly arriving on the server follow our Tenderloin twitter account: https://twitter.com/...!/cm_tenderloin - PLEASE NOTE THIS IS AN AUTOMATED TWEET BOT NOT A LIVE PERSON (i.e. do not tweet @CM_Tenderloin expecting a reply)
3) *NEW* The nightlies also support OTA update notifications using the Goo Manager app, details here: http://tinyw.in/feSQ
Latest gapps are here:http://goo-inside.me/gapps
LCD Density fixes: These were taken from dalingrin's Alpha2 thread and are just updated with a new build.prop.
Change to 120dpi: http://tinyw.in/Ja5P
Revert to 160dpi: http://tinyw.in/VUht
Updates:
For updates/announcement on the builds follow me on twitter, or check back here.
4/2/12: http://xdaforums.com/showthread.php?p=24346202#post24346202
3/27/12: TouchPad now has official nightlies! See my post here about the future of my builds: http://xdaforums.com/showpost.php?p=24120253&postcount=219
3/11/12: Due to some merges on 3/9 you may need to reflash gapps when going from a nightly prior to 3/9 to later than 3/9.
2/28/12: HW video decoding (HD youtube and netfix) are now incorporated (still unmerged in mainline CM code). Thanks dalingrin and jcsullins for getting this together. This means the nightlies currently include everything in Alpha2 and whatever else merged since.
Credit and Thanks
Of course major thanks to Dalingrin, jcsullins, fattire, green and the rest of the CM touchpad team for making these builds possible. Thanks to my fellow winners in TeamWin and a special shout out to kevank for hosting and onicrom for build support22Well guys.. it's been a fun ride, but I'm going to stop the unofficial builds.
Officials are running every night, and I just haven't had as much time to cherry-pick ahead as I'd like to, so there's really no difference between the builds other than differences picked up based on the time of the build. Also, as we get closer and closer to a somewhat "finished" product, it'll be more productive to get accurate bug reports with everyone using the same builds.
You should be able to find the official builds directly on get.cm or via goo manager, differentials are not enabled AFAIK for these, but I will discuss with s0up to see if they'll make it available for those using it. We may also mirror the builds to techerrata/our twitter acct for those who like to follow that for the downloads but we need some scripts in place to do that, so I'll post back and let you guys know.18Due to all the merges today we now have a working "official" cm9 repo for the touchpad which is great. Up until now the builds required a few "hacky" changes to make them work. There's a couple of outstanding issues that won't be in the official builds just yet, the main one being the reboot menu - which still needs some hacky stuff (http://review.cyanogenmod.com/#change,12782). Otherwise the builds should be mostly identical from this point forward (my build tonight will include all the merges today obviously).
Official nightlies is a great place to be for any device - fully merged into the mainline repo.
With that said, personally, I'll still be building for myself and (for now) will continue to have the builds posted to our server for anyone that wants them, I may cherry-pick some extra stuff in time to time.
It was a fun ride11Sorry guys, I was out of town this weekend so didn't have a chance to respond to all the questions.
At this point, the reboot fixes and other outstanding issues are all 100% merged into main CM code, so there should be no difference between the official and unofficial builds (other than the new adreno drivers in mine - which don't seem to matter much right now - probably until we move to a 3.0 kernel).
There was some confusion regarding 4.0.3 and 4.0.4 - I'm not sure why the 3/30 build missed the 4.0.4 build id change, it's possible there was an error in the repo sync that night so it didn't get pulled, but the underlying OS changes were already in place from the day before so really there was no significant change other than the ID being wrong - the base OS changes to 4.0.4 did not go through gerrit, they are just applied.
Hope that answers the questions, this week i'll look at the higher fps boot animation and maybe add that as stock into my builds too. Other than that the only differences between the two sets of builds will be based on the time of the repo sync and build.
I don't intend to provide "support" for these builds, if there's something fun I've cherry picked in I'll post but otherwise, flash away9So jcsullins has been hard at work (as usual!) on the new wifi driver and now has a build ready for testing with a wider audience, so we'd appreciate some feedback so that eventually this can be merged for everyone.
To use this you must be on nightly 5/13 or 5/14. Please update first then flash this in recovery: http://goo.im/devs/j...0513-signed.zip
The driver is designed to sleep when not needed although will wake if something needs to pass through - so what you set in wifi policy is irrelevant and won't make any difference. It's "smart" and battery life seems very good so far.
Please test and post feedback good or bad on your experiences. People who have been hitting wifi issues are especially encouraged to help provide feedback.
