yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] Solsun:
Wasn't able to get the Netflix app to work from the play store until I downloaded a previous version 2.1.2. Not sure what the current version in the play store is now. Skipped jellybean and went straight to kitkat and not looking back. ?
[TouchPad Development] fattyjian:
Any idea why my storage only have internal 1.5gb?
[TouchPad Development] alexeiw123:
Have searched read and searched again, must be missing something obvious? Could you point me toward this updater? Cheers
[TouchPad Development] texastutt:
It's in your application drawer, blue icon. Came with the update a couple of weeks ago.
[TouchPad Development] alexeiw123:
Derp! I looked in the settings like official CM, then xda. Thanks!
[TouchPad Development] schultp:
I had the same issue after doing exactly what the OP has described. What worked for me was the recommendation to install 10.2using Acmeinstaller5M then install flintman's TWRP=Datamedia version and use that to load CM 11.0.

Paul.
[TouchPad Development] guxu:
ACMEInstaller works with earlier CM11 rom too. I used it to load December's nightly.

Installing an old rom then upgrading to the latest one sure works, but it is not required. If you want an absolutely "clean" install, I posted detailed steps here: http://xdaforums.com/showthread.php?t=2643345
[TouchPad Development] nooknut:
clean install?

Hi guys. I've been lurking xda for years, mod'ing my nook, and now my TP. I have a question...I had 10.2installed at some point, then went through tailor and this latest data/media transition. I'm not sure my system is "clean", meaning, old file system structure gone and clean data/media structure.

Here's one of my questions: under root explorer, it shows three folders in "storage"; emulated, usbstick, and sdcard0.

Does that sound right?
[TouchPad Development] jerryatherton:
Yes that is write for Milaq's CM11
[TouchPad Development] fattyjian:
anyone could help me with ? i cant seems to detect my touchpad sd card, it shown only internal 1.5gb.
[TouchPad Development] mpgrimm2:
You sir are on a data/media build and will need to brush up on the differences between it and the regular partition layout as well as the difference between the internal sdcard and the external_sd you are looking for.

Have a look at the following thread..

ROM-GUIDE-How-to-install-Android-4.4-Data-Media-builds-on-the-HP-TouchPad

Read at least the first 10 posts (read the TWRP data/media explanation) and pickup again around post 33 for the answers. I would lay it out for you but there is a lot you are missing if you are asking that question.

If you still have questions someone will certainly help you out. Either way u need to adjust your data partition as mentioned in the op.

PS: pay attention to my testing of the different OS/recovery combinations to figure out how to see both sdcard locations.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] edlee:
That writeup you did on all different recovery/rom installs was perfect, it should be in a locked thread on xda frontpage, thank you, thank you, thank you
[TouchPad Development] mpgrimm2:
Thanks for the positive feedback. RolandDeschain79 and I are planning to replicate the thread over here but have been working out some of the missing details (as you saw) as well as a revised step by step for newer users to more easily transition to data/media builds without all the snags that they are running into.

I would encourage anyone with questions about the differences to have a look until we get the chance to bring it over (hopefully soon).

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] schultp:
I want to officially applaud you for your approach to helping someone regarding a topic well covered here already. This was so much better than the standard "go back and read the entire thread' approach seen so often.

+1 +1 +1 +1

Paul.
[TouchPad Development] DarkShadowAy:
What kind of battery life/performance are you guys getting on this build?
[TouchPad Development] schultp:
I'm getting -8 to -10 mA drain on standby/sleep mode. However, it jumps to -150 to -200 after I have run some apps and remains there even if I kill apps. Once I reboot it goes right back down to the low drain rate. I haven't investigated what is running that causes the higher drain rate. This very likely is specific to something I am running. Since I only use the TP at home I am not as concerned since I place it on the Touchstone when not in use so I really never drain down to a critical level anyway.

Paul.
[TouchPad Development] woodytrain:
I hoped the recent patches to the kernel would have resolved camera issue, but so far no luck for me, with current nightly. More info in camera thread: http://xdaforums.com/showthread.php?t=2611497

P.S. Yes my sleep battery drain jumped up to -200mA to -250mA since 02/15/14 (when running 02-10-14 build). I suspect some recently installed app. However Settings > Battery shows "Android OS" is responsible for 76% of battery discharge, which the device was sleeping for the entire time, until the device ran out of battery charge.

Between Battery Doctor, Greenify, Wakelock Detector and Battery Monitor, hope to get this sorted.
[TouchPad Development] _litz:
One thing to check ...

Make sure WiFi is set to "Always on only when plugged in".

WiFi sleep works now ...

Also, if you're not using a BT device, you can try turning off BT unless you need to connect to something ...

(although BT shouldn't add much load, power-wise ... certainly not 200+ma)
[TouchPad Development] schultp:
Try wiping cache and dalvik cache in recovery. This helped move my battery drain down to the lower rate.

Paul.
[TouchPad Development] woodytrain:
How often do you propose this be done?

Does mlq's new auto install routine wipes cache and dalvik cache?

---------- Post added at 01:59 PM ---------- Previous post was at 01:37 PM ----------

After updating to current nightly and recharging, sleep drain is back to -5.

Will watch apps/services to see what might be the drain culprit.
[TouchPad Development] schultp:
I can't give an answer since I only had to do it once. I had the high drain rate after using Milaq's updater but I am going to assume this was likely a coincidence. I can't tell you if his updater wipes cache/dalvik either.

Paul.
[TouchPad Development] cdzo72:
Yes it does wipe cache and dalvik
[TouchPad Development] woodytrain:
Recent commits to this ROM:

cm11-3.0_kernel-milaq

milaq/android_kernel_hp_tenderloin

Feb 22, 2014

• Merge pull request #4 from vbelo/patch-2

• Adding missing MT9M113 camera sensor call

Thanks koalala/vbelo, milaq and dorregaray.

P.S. I should add these commits should appear in the Feb 23, 2014 nightly.

Update: Did not solve the camera issue.
[TouchPad Development] rtenuso:
screen cut off

I don't know if this is bug and I've searched but came up with nothing. A sliver of the screen on the far left is cut off and appears on the far right side.

You can see a sliver of the icons when swiping left on the far right moving.
[TouchPad Development] woodytrain:
Installed both the 02-22 and the 02-23 nightlies. Same issue with camera.

Launching the stock camera still shows "Camera error: Can't connect to camera" then clicking OK the app closes. Whereas the Nexus 7 camera doesn't display an error and launches with the camera controls appearing on screen , but with black background and no image from camera lens appearing on screen. Same thing when attempting to do a video.

On a related note, before installing the 02-23 nightly, I had two separate camera icons, one for the native camera app and another for the Nexus 7 camera app. Now the icon for the Nexus camera is no longer present, on both the desktop and the app drawer. Whereas the icon for the native camera app is still accessible.

When clicking on the single camera icon two options are displayed: "Complete action using: Camera or Nexus Camera". And selecting the Nexus camera app launches correctly so the nexus camera app is still installed. Why would the third party camera icon 02-23 install rid of the app icon? Any easy method to get the Nexus 7 camera app icon back, besides uninstalling and reinstalling?

---------- Post added at 09:02 PM ---------- Previous post was at 08:59 PM ----------

I observe this as well. The issue was dealt with awhile back, but returned on a more recent nightly (several weeks ago I believe). The same issue has been reported in other Tenderloin KitKat ROM threads.
[TouchPad Development] alexeiw123:
I get this too. My DPI is 120 if that's relevant.
[TouchPad Development] woodytrain:
The m|q updater worked fine for installing 02/22 update. However when I employed the updater to download/install the 02/23 nightly with the m|q updater, the install process did not go well and I ended up with a BSOD. (will spare you all the details).

So I manually downloaded the 02/23 nightly and flashed in the recovery, and back to normal now. Settings > About Tablet shows a 02/23 build date. (However the the camera issue is still present.)

However the m|q updater is confused and still shows the "newest version (02/23) is downloaded and ready for installation", and reports current install as 02/22 nightly. How do I reset the updater?

For now I will go back to manually downloading nightlies and flashing via the recovery rather than using the m|q updater.
[TouchPad Development] mpgrimm2:
As Woodytrain stated, I am also seeing it on Invisiblek's CM11 with 3.4 kernel (2-20-14 release). I only see it in landscape, not portrait orientation.
[TouchPad Development] woodytrain:
In Build Properties

ro.sf.lcd_density

Change DPI to 155

I was set at 160 and after changing to 155, I no longer see the vertical sliver of pixels on the far right side of the display.
[TouchPad Development] rtenuso:
Thanks. Changing DPI to 155 fixed it.
[TouchPad Development] The Jack of Clubs:
The screen offset is know by the devs. It's not been randomly fixed and reintroduced, it just shows up randomly. Its there in portrait. Is just at the bottom of the screen.
[TouchPad Development] guxu:
Last night's build fixed the screen offset issue.
[TouchPad Development] zoser42:
Chrome black screen workaround

I no longer get the initial black screen when launching Chrome which initially shows the bookmark page.

After flashing a new rom and launching Chrome the bookmarks page would display fine. But when I close Chrome and relaunch it the screen tab is black every time afterwards.

I went into Settings/Developer Options and checked the Disable HW Overlays, exited settings and Chrome displayed fine.

I then read that this can use more RAM and slow some apps down so I unchecked the box.

Then I opened Chrome and went to the chrome://flags url and changed the first dropdown menu for Accelerated overflow scroll from Default to Disabled and retested Chrome. It displayed fine. Then I changed the same dropdown to Enabled and Chrome still worked fine. Then I changed it back to Default and Chrome displays fine every time.

All of the settings are now back to the way they were before I started fiddling with them so I"m not sure why it still displays fine. Perhaps changing the dropdown from Default to another setting, exiting settings, and then changing it back to Default might work.

I'm not sure what effects this has on other web pages but the dread black screen is gone. :)

-------

Also, the second use of the OTA MlQ updater did not work for me. I cleared out the mlupdater folder so maybe it will work next time with only one rom in it.
[TouchPad Development] The Jack of Clubs:
thats not true.
[TouchPad Development] marcustaz:
I just clear out the folder each day before Dling the new update.

Another thing I found interesting is one of my TouchPad's is on build number 6.4.6 CMW recovery instead of the 6.4.7 recommend by Milaq. For me this build actually works better.
[TouchPad Development] zoser42:
Going back to CWM 6.0.4.6 didn't work for me so I flashed 6.0.4.7 back, cleared the mlqupdater folder again, and ran the updater again which downloaded today's rom. After rebooting it started the update but almost immediately failed. The android robot fell over and a triangle with a red exclamation mark briefly showed above it and then rebooted.

I installed it manually(clean system wipe first) with cwm from the mlqupdater folder followed by gapps. Android works fine but the updater is still failing.

Are others having problems with the mlqupdater and do you have any other suggestions?
[TouchPad Development] Flyinace2000:
Easy question.

I am running a mid feburary build (i think 17th). I launch BSPlayer to watch a movie today and the screen went black. Stuck. Backlight on and i can't reset it. Last time i had to wait for the battery to die and then re-charge. I have tried holding down the power button + menu & power button + VOL down, but neither seemt o force the restart. Any ideas?
[TouchPad Development] koalala:
Did you hold the button for a long time ? (i think it's around 30s, it is actually very long).
[TouchPad Development] Flyinace2000:
Yeah, just tried it again and did a slow count to 40.

Also, the center button's backlight is also stuck "on".
[TouchPad Development] guxu:
Interesting. I actually never noticed the problem until I saw the posts here. Then I confirmed I had the same issue by moving the desktop icons and moving the google map. Before I tried the dpi fix, I did a OTA update last night. My icons are fine now. I will check the google map tonight.

Update: confirmed the problem has not been fixed. But I had to look it in the dark.
[TouchPad Development] Czo:
It seems to be today (and yesterday) build has some problem with ART. Installed after formatting /system and /cache, and removed /data/dalvik-cache/*.

adb logcat output on the first boot: http://pastebin.com/Ssnm9bat

The following configurations checked:

cm-11-20140220-UNOFFICIAL-tenderloin.zip seems to be fine with gapps-kk-20140105.zip or pa_gapps-modular-micro-4.4.2-20140213-signed.zip with ART or with dalvik.

cm-11-20140223-UNOFFICIAL-tenderloin.zip with pa_gapps or gapps linked in the OP can't boot with ART.

cm-11-20140224-UNOFFICIAL-tenderloin.zip with pa_gapps or gapps linked in the OP can't boot with ART.

I switched back to 20140220 build.
[TouchPad Development] _litz:
You need to hold power and home to force a reset
[TouchPad Development] Flyinace2000:
Tried that. Held it down for 10 seconds, held it down for 40 seconds. Doesn't shut down.
[TouchPad Development] _litz:
Oh, it'll reboot. You just have to hold power+home until it does.
[TouchPad Development] Flyinace2000:
Before or after the battery dies??? ;)

I just tired holding it for over 60 seconds. No response. Time to buy an iPad or Nexus 7?
[TouchPad Development] _litz:
I've never seen a TP locked up so badly, the power+home reset doesn't work.

I guess it could happen, but it's very very rare.
[TouchPad Development] nevertells2:
I have never had a situation in almost three years using a TouchPad that holding power and home would not force a reset. As far as I know, that is a hardware function and should work no matter what Rom is installed. Unless you have a faulty button, it should work.
[TouchPad Development] Flyinace2000:
Yeah, the reset never failed me either. O well, battery just died and now getting the PITA "not the right charger error". Just gotta leave it plugged in to trickle charge. I think i've had a good run with this tablet, but might be time to set it free. haha
[TouchPad Development] mpgrimm2:
I had a few sleep o death issues on Invisiblek's CM11 DM 3.4kernel build (as mentioned in his op) and recently switched to Milaq's 3.0 kernel version to try it out.

So far I have been able to do the hard reset, but occasionally it would appear to not work and i would let go of the home button for a second or two and retry with both buttons again without issue.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] woodytrain:
I've observed general flakiness as to button responsiveness after installing the last couple of nightlies. And my settings to not vibrate and to not enable home button led, keep getting reset after nightly updates. Previous nightly updates did not do this

However my sleep drain has returned to excellent once again, at -6.

If anyone on this board has ability to compile, koalala (vbelo) has posted in the camera thread that he needs some assist so he can continue working on the 3.0 kernel camera issues.

http://xdaforums.com/showpost.php?p=50590411&postcount=57
[TouchPad Development] TJude:
Paste bug

Having a firmly reproducible error in 0222. Using SwiftKey keyboard and pasting into the open editor causes the app to crash. FWIW

2/26: Fixed in 0225. Thanks.
[TouchPad Development] ZeroZorro:
Has anybody Spotify working on this CM11kitkat? I have Spotify installed using TitaniumBackup but the app gives an error about no ext-storage or SDstorage and continues with an empty screen.
[TouchPad Development] jeppo:
Same here. Clean install of both ROM and Spotify.

I'm on 24/02 build.
[TouchPad Development] nevertells2:
Don't you have the original HP wall charger? That is the best to get a TouchPad quickly charged back up. Plugging it to a non-standard, after market charger or one's PC is only going to charge at 500mA which can take forever if you have the TouchPad asleep. If you are using it, it just won't discharge as fast.

---------- Post added at 05:11 PM ---------- Previous post was at 05:05 PM ----------

What happened to the volume switching setting in this Rom that allows you to choose how the volume slider behaves in either portrait or landscape? If it is in settings, I can't find it. Anyone seen it?
[TouchPad Development] mpgrimm2:
SETTINGS -> DEVICE -> BUTTONS

But it doesn't seem to wake my TP.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] mpgrimm2:
New question,

Prior to the data/media builds (on CM11 3.0 Kern now) I was able to connect my Touchpad to WiFi Tether 3.4 experimental_1 on my Nexus-5 using "profile LG Optimus Black (G)" without issue.

Currently I can not see my tether's hotspot at all on the Touchpad to connect. Manual setup doesn't connect either. Several other devices can see and connect to my N5 just not the TP anymore. The Touchpad connects fine to my WiFi network at home.

I believe there are some other Nexus-5 users here with Touchpads (or WiFi tether users)

anyone else have or notice this issue or just me?

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] noseph:
Can't say about Nexus 5, but tethering right now on my CM11 3.0 TouchPad from my CM-REMIX Galaxy Nexus.
[TouchPad Development] mpgrimm2:
Thanks. Same tether app?

Sent from my "Up All Night, Sleep All Day" 4.4KK DM Touchpad
[TouchPad Development] noseph:
Probably not, I am using what is baked-in the CM-REMIX rom.
[TouchPad Development] nevertells2:
Thanks! Man, I hate when they move stuff around!:(
[TouchPad Development] suzib6sw:
[MENTION=1594835]milaq[/MENTION].

Just wondering if you had chance to see if you can merge vbelo's patch 3 into the build and test it and what were the results..

Many thanks for all your efforts..

Pete
[TouchPad Development] nevertells2:
OK, who can answer this question. Since installing the 0224 nightly, I have not been able to find a way to add or remove home screens.

And BTW, what is this launcher called, it's not GEL is it? Thanks
[TouchPad Development] jerryatherton:
I think there are two OK launchers. The Google Experience Launcher and the Google Now launcher. The only way that I have been able to add on is to fill one screen up and then another is added. I have been using them and gotten used to it. I usually used Nova.
[TouchPad Development] woodytrain:
Koalala/veblo posted some progress.

http://xdaforums.com/showpost.php?p=50659314&postcount=59

He's made two pull requests (an updated patch3 and a new patch5). Appears Milaq has not committed either to the Feb 27 nightly. Maybe waiting for koalala to do further testing? Crossing fingers for a TP camera by the end of the month.
[TouchPad Development] maxexcloo:
Hey All,

I'm on the nightly from the 24th and am having issues with the WiFi being slow occasionally. Wireless Optimisation is turned off and prior to the update (I fresh installed from 4.3) I had no issues. Is this a known problem?
[TouchPad Development] woodytrain:
No wifi issues with 02-23. I have Wi-Fi Optimization CHECKED to save battery. Have limited bandwidth at my current location thus have not flashed 02-27 nightly. When new camera commits make it into kernel, will flash an update.
[TouchPad Development] jeppo:
Last Spotify update fixes Kitkat SD problem, so it was not a CM issue.

Sent from my XT890
[TouchPad Development] airtower:
Google Experience Launcher (GEL) is now called Google Now Launcher. In contemporary Google fashion, it has very few options, but you get the Google Now homescreen to the far left. It's closed source, so you get what you get from Google. Just like Gmail vs Mail, Hangouts vs SMS, etc. All part of Google's long term plan to differentiate Google branded apps from the alternatives offered by the other OEM's.

Launcher3 is Trebuchet. This is/is based on the AOSP launcher, which looks very similar but does not have the Google Now homescreen. Since it's AOSP, the CM team can forward port customization options from 10.2. Although there haven't been very many. I for one really want to see the ability to hide apps merged back in. I can't stand an app drawer cluttered with system apps I don't use or can access through other means.
[TouchPad Development] ZeroZorro:
True....but i had tot clear the data through 'app info' and restart Spotify and sign in again.

Now it works again! #happyme
[TouchPad Development] _litz:
depending on how the camera stuff is setup, this :

http://review.cyanogenmod.org/#/c/60053/

might affect things ...
[TouchPad Development] koalala:
It won't. It still a kernel issue for now...
[TouchPad Development] nevertells2:
Sure miss the ability to set the screen sensitivity to a stylus rather than a fingertip. I can use my stylus but the sensitivity to it really sucks. Any chance we can get this added back in?
[TouchPad Development] nevertells2:
Hah! I figured out how to add extra home screens, although by accident. Grab any icon and drag it to the right, a new screen is added to drop it on. :good:
[TouchPad Development] woodytrain:
It appears camera support may not be coming to the 3.0 kernel after all, at least that has been suggested in the camera thread. Also most of the dev energies appear to have focused on the 3.4 kernel. Myself, this means it is time to place emphasis on helping test/support 3.4 kernel ROM development for the TouchPad, where the camera appears to be working (but not always reliably).
[TouchPad Development] milaq:
both kernels have their advantages.

i decided to include 3.0 intially because of the fact that it was more stable than the 3.4 branch. except camera almost everything is working with 3.0 (esp. direct fb recovery). power consumption, cpu pm and audio-in is a problem with 3.4 atm (which is worked on and eventually will go along just fine).

until stated problems with 3.4 are worked out going with 3.0 is more beneficial for using the tp as a daily driver imho. the 3.4 branch is also a very good option but there are a few minor quirks here and there (vide supra).

personally i dont really use the cam and my freetime is very limited until mid-march (thanks to [MENTION=621394]koalala[/MENTION] for taking time to work on it).

we *have* the choice to utilise either 3.0 or 3.4, which have almost the same performance/featureset so the switch to 3.4 may or may not come and the device tree can be accomodated very easily thus happening on the fly.
[TouchPad Development] Bionic_Merlin:
I'm running Apex on the TouchPad and also on my Galaxy S4 Mini. I got tired of fighting with Google Homescreen and TouchWiz. I prefer Trebuchet to the Google launcher and Apex to Trebuchet.