yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] captainmorris:
I have to agree with you here. I've been using Milaq's CM 11 3.0 Kernel builds since he began putting them out around New Year's Eve. It has been my daily driver since then. I'm currently running your (JCSullin's) CM 11 3.0 Kernel SNAPSHOT build from yesterday, 4/3/14. Everything seems to be working just fine, with the exception of Netflix, which will not load videos to the point of playing....this is a know issue in all of the KitKat builds on the touchpad, regardless of ROM or kernel. I've tried, at varying times, different versions of the 3.4 kernel builds. They are all progressing very nicely, but they still have quirks, like having to shut off Google Now's mic to help avoid a SOD, and battery draw is still a little high, though getting better thanks to Flintman's hard work! I don't have those issues on the 3.0 kernel builds.

At this point, I have to say that the 3.0 kernel based ROMs are the most stable and reliable. That being said, I'm in complete awe and have the utmost respect for all who have been, and continue to, develop for our old TouchPads! I understand why those who are working on the 3.4 kernels are doing so. Having the most up to date kernel helps to allow for the most room to grow in the future. It will also, fingers crossed, allow for official nightlies from CM to start up again! ? 3.0 kernel based ROMs may qualify for that as well, but I'm not sure. I've only heard the 3.4 kernel ROMs referred to in that regard.

Long story (sorry!) short, use the ROM that suits your use the best. They are all awesome, and are being looked after by quality developers, some of the best developers, in my opinion! From my own experience, the 3.0 kernel based ROMs are the most polished at the moment...and yes, the camera and the Bluetooth are working just fine! ?
[TouchPad Development] flintman:
The next nightly will contain the fix for the home key wake along with a change to the kernel sleep picked up about 2mA saving in sleep.
[TouchPad Development] blmvxer:
I've seem to have fixed my SoD by leaving it on the charger all day with the screen on after the first install. And also disabling GEL's hotword and okay Google features. I'm clocked between 384Mhz-1.5Ghz using interactive and no SoD's at all.
[TouchPad Development] Moody66:
Awesome work flintman! Only issue I have is the sound is still buggy in some apps. Everything else works perfectly. XBMC is even flawless. Can't thank ya enough for all you do for us!
[TouchPad Development] nevertells2:
So, go ask Milaq to edit his post to reflect the current state of the build instead of taking pot shots at me for using his information. I tend to take what the developer posts in HIS thread as valid information. :(
[TouchPad Development] bundys:
Still experiencing WiFi going off after a while in sleep mode on the latest build. Simply cycling WiFi doesn't work, required a reboot to get going again. Pm'd log last time, don't know if I need to again.
[TouchPad Development] agent00f:
What's the major blocker for low idle battery use? There was some major (kernel?) change back in the CM9/10 builds that knocked standby from 50ma to <10ma. Is there some reason why that hasn't been figured out yet for 3.0 kernels or whatever?

Thanks.
[TouchPad Development] flintman:
Unsure about 3.0 kernel but 3.4 been working other issues. I understand battery life is important but so is stability. It will come with time which I'm limited on. Along with maintain 3 devices and bring HTC shooter up to 3.4 kernel. Believe me its on my mind while working other issues and will tune it in. I thought the 3.0 kernel has low consumption but unsure as i haven't tested.
[TouchPad Development] flintman:
Still trying to duplicate your logs but so far haven't had luck. I plan on spending some time on this and dig down to determine the cause.
[TouchPad Development] bundys:
Great, let me know if you need anything else from me.
[TouchPad Development] agent00f:
I've seen similar wifi non-working issue couple times after wake (arrow/lights seem to blink but pages don't load), but works after wifi on/off cycle.
[TouchPad Development] bundys:
For me it takes a whole reboot cycle to get WiFi working again. Plus, while it's in limbo, the power draw is about 60 - 70 mA higher than normal sleep draw.
[TouchPad Development] masdacheri:
What this? New issue on what nightly this? Coz in my, everything is good..but sometimes sound mute it self but reboot device back normal again..one more cant share location ?
[TouchPad Development] flintman:
Ok just wanted to update everyone. I'm currently testing out some wifi, audio, and inkernel mpdecision. Hopefully this will take care of any of the rouge issues out there. Once i'm happy with it ill post a test build before moving it into the nighties.
[TouchPad Development] flintman:
Just posted a test build that will hopefully take care of the rouge audio and wifi issues. Also in this test is an in-kernel MPDecision solution that seems to be working very well. Let me know how this works out for the few that are having those audio and wifi issues
[TouchPad Development] flintman:
Just an FYI i seem to be running around -34ma to -43ma now from the -50ma i was running. Let me also know if this test helps with battery life which it should slightly. Also seems to have fixed the hotword issue with the audio updates. As long as the device is running good try to reenable it and see if its fixed. Seems to be fine on my TP
[TouchPad Development] Moody66:
Loading it now. You been busy last few days.! Thanks for the new build!
[TouchPad Development] graffix31:
New build is running pissa. Just enabled hot word. Will update tomorrow.
[TouchPad Development] Connor Baker:
Saw the new test build and decided to flash it.

Problem is, I'm coming from a non-data-media build. So, downloaded one of the re-partitioning .zips and flashed it (Gradular's one). It produced rc=4 as the error, so I flashed it again. rc=1 that time. Then, because I'm tired and wasn't thinking, I flashed the data/media build over that (of course, I did a full wipe of EVERYTHING possible in CWM before flashing).

My expectation is that it wouldn't flash, or possibly wouldn't but, but lo and behold, it did both!

So I'm running it right now, and my question is, did I successfully re-partition? Are there any repercussions that I should be on the lookout for? Is my device going to explode!?

Connor Baker
[TouchPad Development] nevertells2:
You should not flash data/ media roms over the top of a non data/ media roms. The resize zip failed to install because you tried to flash it on top of an already existing installation. You need to run ACMEUninstaller2 and then start over clean. Use ACMEinstaller5 to install a data/media recovery and moboot. Then flash the resize zip from recovery. Now reboot as instructed and use recovery to flash your DM rom and Gapps.

J.C. Sullins 6.0.4.7 touch CWM is the best recovery to use.

For more detail on how to do this try reading post number 2 from the following link:http://rootzwiki.com/topic/40107-ro...roid-42-43-and-442-builds-on-the-hp-touchpad/
[TouchPad Development] venkythegeek:
latest nightly build camera

so finally i have 10 posts and i can post my question here. I am on the latest nightly build, and the camera worked well before all my apps updated from the play store (after clean rom install) after that I can only see blue striped screen and crash.

Anyone else experiencing same issues with the camera?
[TouchPad Development] bundys:
All OK with the WiFi so far, but noticed that power draw actually went up about 15 mA. Didn't have time for a full clean install, so just wiped cache and dalvik before installing the test build, hopefully that is not messing up my power draw. Anyways, sound and WiFi look good and the interface actually feels more responsive as well.
[TouchPad Development] flintman:
I did a clean install on this one and that is when i noticed the power drop still running around 35-40ma which is down from the 50 i was at
[TouchPad Development] scifan:
what tool are you guys running to check the current power draw?
[TouchPad Development] flintman:
http://www.xda-developers.com/android/battery-monitor-widget-for-android/
[TouchPad Development] gaww:
I had a lot of unused room, so I also flashed a resize zip (which still left a fair amount on media) and it ran fine - including setting system up to 512 mb (could not find a 600mb option). I then flashed new recovery, and data CM 10.2 ROM and GAPPs. Had to reflash moboot to have it come up when rebooting from CM. It was a "clean" install of the ROM on the new partition, but it brought over the data, and so far everything running OK.

I believe I can now simply restore nandroids of non-data ROMs from old partition if desired. I thought for awhile I had a duel boot option - lol, as the non-data ROM was still the default on moboot (fixed now), and it started to boot it up (including resetting apps in dalvek), but at the end, it would not actually boot up. removed it from moboot and reset default.
[TouchPad Development] bundys:
If I have a bit of free time, I guess I'll try a clean install tonight and see where the power draw sits at.
[TouchPad Development] graffix31:
Well I am happy to say that with the test build I had hotword on all night and no sod and WiFi worked all night to. Never disconnected. That's awesome. Does seem very smooth and snappy as well. I see a new nightly. Should we flash that or stay on the test build?
[TouchPad Development] flintman:
Nothing really changed in that nightly i believe just the data bars for phones.
[TouchPad Development] gaww:
Oh well - I was doing pretty good while doing things that i was not supposed to do, but after flashing this, got into continuous bot look at lockscreen. before I can unlock, it reboots.

I had only wiped cache, dalvek, and system. I will try once more with full wipe. If it doesn't work, have already restored data ROM CM 10.2 Ok, so will be able to get back to a good place again if need be.

Update - Also wiped data and up and running OK so far.
[TouchPad Development] Wishka233:
Anybody having issues with the screen being unresponsive when running certain games? I am on a fresh install of the 4/5 nightly and when I try to play Candy Crush [Yes I admit it I don't care :p] the screen does not seem to register any touches. I've tried wiping the cache and data for the app and rebooting but it doesn't fix the issue.

Regardless, thanks for everyones hard work! I have gotten so much more use out of my touchpad than I ever expected.

Edit: Interestingly, it does work if I uninstall and reinstall the app but then goes back to being unresponsive
[TouchPad Development] bundys:
Figured out why my power draw was higher in the test build, it actually had nothing to do with it. My Internet connection was down during the period I checked the logs for and I'm assuming that was what was causing the higher drain as background services kept on trying to connect. Once the Internet came back on, power draw returned to normal.
[TouchPad Development] gaww:
I am seeing very high power draw while in sleep mode overnight. I am only looking at the curve in Battery Monitor Widget, and it lost 20% over 8 hours. On milaq CM 10.2 nightlies, it is almost flat-line overnight. Have the same basic setup, so I would have to assume it is the ROM.

Note - the lack of any significant battery drain in sleep mode on CM 10.2 make me think that it has nothing to do with the firmware at this point (I did not reflash it) if it can be that good on any ROM. Did pretty good on Evervolv 4.3 non-data also.

Going to give it more time, and any suggestions on what to check would be appreciated. Kind of like 4.4, but need to have acceptable battery life at the end of the day.
[TouchPad Development] flintman:
Are you on the latest nightly or the test build i posted. Also did you clean install or do a dirty flash?
[TouchPad Development] gaww:
I am on the latest (2014-04-10) nightly, which I understood had the test build things in it. I tried a data only dirty flash first (per post above), but resulted in boot loop, so went back and clean installed - which worked.

Question on the stock launcher - it hides labels below the icons in horizontal mode - are there settings for this launcher (I could not find any). I pulled up APEX launcher, and it does not do this - and is very customizable.
[TouchPad Development] flintman:
Negative no test build stuff has been pushed yet. I plan on making sure the changes are good on the other devices and hat evervolv supports tonight before pushing up ill let you know when the commits hit the nightly. Ya the stock launcher is not great but if you use the proper gapps it gets replaced with the Google launcher that has all the options in it which works 100% better
[TouchPad Development] gaww:
Interesting on the test build - does it have nay battery stuff (I hope) ? I was going to flash it, but one post indicated the nightly included it (or I might have read it wrong).

I don't like the Google now launcher(which is latest Google update I believe), as it wants to steer more things Google's way, so will probably just use Apex.
[TouchPad Development] flintman:
The test build has a bunch of audio and wifi changes that seem that have solved a few issue. In return at least for myslef i have picked up about 15ma in sleep running a good solid 34ma in sleep from the 50 i was at. Those changes maybe in the next nightly but hopefully before the weekend is over. Just won't to make sure that they get tested on other device before pushing them.
[TouchPad Development] gaww:
I flashed the test build to see how it does with WiFi (I was not having any issues with the nightly), Bluetooth (ditto), audio, etc. Will post if issues pop up.

In fooling around, I tweaked the dpi, and the icon labels now show in horizontal mode in the stock launcher.

Totally irrelevant - device speed test results went down 10-15%
[TouchPad Development] mpgrimm2:
Fyi, this occurs when using stock Gapps (goo.im/Milaq's site) vs the PaGapps recommended in the OP/post 2 (micro, mini, or full). Not sure why.

Sent from my "Up All Night Sleep All Day" Nexus 5!
[TouchPad Development] Moody66:
Test build still had sound issues for me on a couple things. It did feel snappier for some reason even though I didn't see where speed was worked on. WiFi for me has always been good on evervolv. Didn't download any huge files or anything though. It was for sure a step in right direction.
[TouchPad Development] flintman:
Can u get a log when the sound issue happens??
[TouchPad Development] Moody66:
That is the weird part. Logs show nothing. Not even a hiccup. The even tried it on two other touchpads. Fresh installs. I would say it's the apps. But they work fine on non 3.4 kernel roms as well as 4.3 4.2 roms. I will try other stuff to see if I can capture something useful.
[TouchPad Development] agent00f:
The new version of BMW seems to skip records when in standby. The internal warning is that on 4.4.2 it needs monitoring setting interval set to 5min instead of real-time, but that only produces records every hour instead of 10min.

---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------

For me right now, the screen is unresponsive after wakeup, and takes another off/wake cycle to work. I'm on 3/28. I suspect it'll start working normally after a reboot.
[TouchPad Development] gaww:
Strange - will try. Was using GAPPs from one of the guides.
[TouchPad Development] sstar:
Hi I've been testing this for a couple of days everything thing appeared to be great including a working home button but I to have had some sound issues causing it to create a high pitched tone forcing me to reboot. The logcat is posted below. At the time I was listening to Spotify and this happened after unplugging the charger.

I hope that it helps and thanks for all your work.

http://paste.evervolv.com/view/91379616
[TouchPad Development] flintman:
I see an OTG error in there. Where you plugged into a wall outlet or pc?
[TouchPad Development] gaww:
My battery decline overnight was only about 7-8% this time, compared to 20%+ first night.

I went for the latest nightly to the test ROM, but also froze a few apps that might have been using battery in sleep mode (location services were off both times). WiFi was the major (as in most of) item overnight this time.
[TouchPad Development] Colchiro:
Freezing the wrong app can cause increased battery use. (Don't you have to clear the cache after freezing apps?)

When's the last time you flashed your A6 firmware?
[TouchPad Development] gaww:
When I installed it in 2012. Tried to reinstall A6 a few days ago, and it did not take. No reason now, as in sleep mode on 4.3 - battery use sleep-mode overnight was next to nothing, So A6 is not an issue.

Went to this ROM, and battery life was initially reduced. Went to test ROM, plus froze primarily social networking stuff, and net-net - it got much better. Just letting the OP know that - think test ROM mods helped. WiFi, bluetooth, and sound - no issues to report.

The acid test will be how does the battery do when turned off from within Android. I had seen significant battery drain that way for 2 years, but when turned off from moboot, recovery, or WebOS - no discharge - even for weeks at a time. Do not think that was firmware, as from all but Android , no issue.
[TouchPad Development] sstar:
Hp charger. And your built in facility to get the log in settings really does make it easy.
[TouchPad Development] gjlowe:
Hello everyone! Just did a brand new clean install yesterday. Most things seem to work fine. However, on Plex and a few games like Disney Infinity Action, I just get the blue screen. I'm guessing it has to do with a video driver or overlay or something like that. What info can I provide to help diagnose? Does a logcat get this?

I'm on the 4/10 nightly.
[TouchPad Development] flintman:
Ya if you can grab some logs that would be great
[TouchPad Development] blmvxer:
Along with logs try forcing GPU rendering and Disable Hardware Overlays via Development Settings.
[TouchPad Development] sstar:
Hi I've just had another auto shutdown with a high pitched electronic sound. I was listening to Spotify and dl a rom at the time but NOT charging the touchpad this time.

Logcat http://paste.evervolv.com/view/4e9395ff

Dmesg http://paste.evervolv.com/view/931b42dd

Kmsg http://paste.evervolv.com/view/6fb3e5ba

Hope the logs above are of some help.
[TouchPad Development] bundys:
Had WiFi die on me using the test build. Was hoping to get logs, but wife rebooted the touchpad while I was on the phone. Will try to get logs if it happens again.
[TouchPad Development] DaWolfey:
I've had the WiFi die on me repeatedly since I installed my first test build a few months ago. Before that I was using Cyanogenmod 9 - the very last nightly of it - which used to suffer from the same problem until someone produced a fix which was discussed and released in this thread http://forum.cyanogenmod.com/topic/46824-wifi-issues/page__st__100

After that, it was fine.

I don't know if a similar patch needs to be made to Evervolv, but it would be pretty great if it didn't lose the WiFi randomly!
[TouchPad Development] graffix31:
Are you disabling wifi optimization?
[TouchPad Development] bundys:
No, I had it on, but I'll try with the setting turned off and see how it does.
[TouchPad Development] gjlowe:
So I have tried setting those options with no luck. Here is the logcat when trying to launch the Disney Infinity Action! app. Again, I just get the blue line screen.
[TouchPad Development] flintman:
Thanks for the logs. Ill take a look at them along with trying to install that app and see what i can find.

Thanks
[TouchPad Development] gaww:
Test build had been running pretty good for days, but without any changes, it started getting unstable (freezes, reboots) and had to wipe it and reinstall.
[TouchPad Development] masdacheri:
[ROM] Evervolv | 4.0.0p1 [AOSP 4.4.2] [3.4 kernel] [Nightlies] With /data/media

I was had this issue with app games subway surfing and fix it after get new update app..so wait to get update that app
[TouchPad Development] flintman:
Pushed a bunch of changes up to github should be in todays nightly
[TouchPad Development] bundys:
FYI, with wifi optimization off, wifi doesn't appear to die anymore with the test build, but power draw is up from 35 to 50.
[TouchPad Development] 4GivenByChrist:
[MENTION=3716175]flintman[/MENTION] could Bluetooth have been effected by anything you pushed? I installed 04/16 and for the 1st time seem tone having trouble pairing BT devices. Devices that never had problems before. I'm going to keep testing, but the only issue I've had thus far. Even tried restoring pairings from titanium after wiping to no avail.
[TouchPad Development] gaww:
I see the new nightly - does it have the 09 test fixes in now?
[TouchPad Development] gaww:
Overnight I experienced twice the battery drain overnight then before. I have the same setup, but noticed in the statistics that WiFi was a much bigger user then previously. Any settings I should check? WiFi optimization is checked.

Thanks

Update

I had Play Store not able to connect to network after a few days from installing the 09 test. Could not get it fixed, but when I updated to latest nightly, it was OK again (did a clean flash). However, after a day, Play Store would not connect to network again. I wiped play store data, but did not restart correctly. I deleted Google account and tried to add it back, but it would not let me. I reflashed the GAPPs from the OP, and got it back OK.

Should i try a different GAPPs if this keeps happening ?
[TouchPad Development] nevertells2:
Why fix what now is working? Some times, you need to reflash Gapps to fix things. :good:
[TouchPad Development] gaww:
It has happened twice - if 3rd time - looking for an option.
[TouchPad Development] Moody66:
Every time I have seen someone with a play store issue it has always been due to the happy package installed.
[TouchPad Development] jerryatherton:
This has happened to me only when i don't flash gapps when i flash an update. Ever since JB i think this has been an issue.
[TouchPad Development] flintman:
When updating you still need to flash gapps. The install script formats system then installs the ROM. Since it formats you need to reflash gapps
[TouchPad Development] masdacheri:
I get SOD if not connect wifi on new nightly
[TouchPad Development] flintman:
Can you get a log of that? Also did you do a clean install and what gapps do you use?
[TouchPad Development] masdacheri:
I dont a clean install n i want to try clean install now..?
[TouchPad Development] dharani1234:
My touchpad doesn't charge at all when it's turned on anymore. I am using a 1 A charger as opposed to 2 A. But it used to charge well before this update.I don't think it might be th ROm , but not sure why it's behaving this way after the update.

Clean install.. GAPPS from PA .

Please let me know if any of you have any thoughts ...
[TouchPad Development] masdacheri:
it must 3.2 A
[TouchPad Development] flintman:
All,

I have been working on OTG on the TP. Now I didn't modify my device like http://xdaforums.com/showthread.php?t=2021776 what i did was purchase a OTG cable on ebay for a few bucks then took an extension USB cable and cut it in 1/2. Took another usb cable and took the male end. Spliced in the power wires red and black and now have an external powered OTG cable. I don't recommend this if you don't have experience with cable soldering and electronics but there are probably videos out there that show you how to do it. Well i have it working used a usb mouse, keyboard, and drive all working very well. There are still a few bugs im working on like you need to plug in the OTG cable first then a device like mouse, keyboard ext but ill get that 8)
[TouchPad Development] gaww:
"happy package" ?
[TouchPad Development] MerenQue:
You're unbelievable! :cool:
[TouchPad Development] bundys:
Major issues for me on the last nightly. When playing audio, if I turn off the screen the audio screeches and stops. Half the time I need to hard boot the device to get it to turn on again. This is a dirty flash, so I wanted to see if anyone else is experiencing the same before I spend my time on a clean install.