yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] flintman:
Just found a little bug. I hate facebook and never really use it but my wife does and i updated her TP today and facebook causes a reboot. I was able to duplicate over and over. Some reason during the update process Facebook doesn't get updated correctly. The fix for now is to uninstall facebook and reinstall. Works fine until you do another upgrade. Im looking into it.
[TouchPad Development] sokratz:
I've been playing with this awhile and it's been lotsa fun. Couldn't ever seem to get the auto upgrades to work but I can do manually. Running the 20150103 build. Only real complaint is that it's really sluggish. Any improvements to performance in the last month or so?

Thanks
[TouchPad Development] flintman:
The updater has been repaired WOW you are on an old build. Ya you will see quiet a bit difference in performance.
[TouchPad Development] gaww:
Updated to 2015-02-20 this AM and have had a couple of reboots during the day. had no had reboots wih earlier version. Dirty flashed from week ago version (test build).

Question - does the install script wipe /system ?
[TouchPad Development] flintman:
No its block style install. I clean install would be a format of system before installing.

In regards to the reboots do you have Facebook installed?
[TouchPad Development] jsgraphicart:
As long as there is a workaround, I will give this Lollipop build a try tonight. Can't wait. :)
[TouchPad Development] flintman:
you can install if you want i did pull the downloads. I want to determine the issue. I just tried a full wipe and still can't restory my boot directory. Not sure on the cause and until i find out i have pulled the downloads. I could be as simple as a different recovery. but until i confirm i don't want anyone else to install for now. there is a work around like i posted before install kitkat then restore parition except boot but you will have to do this for everything until the cause is found. Sorry guys i did test before and it worked fine. ill get down to the bottom of it
[TouchPad Development] jsgraphicart:
Ok. Maybe I will just hold off. I can be patient. lol
[TouchPad Development] flintman:
ok i used my recovery i posted back in 4.4 which is what i original test it on and it worked fine. I still need to test a little bit more but looks like JC sullins TWRP recovery won't let you restore /boot

hmmm

http://evervolv.com/get/FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
[TouchPad Development] jsgraphicart:
So as long as we use this recovery, everything will work correctly?
[TouchPad Development] flintman:
testing now ill update if so ill post my TWRP release in the first post and restore the links.
[TouchPad Development] jsgraphicart:
Well I have been using Evervolv for a while so I may actually be using that recovery already. I'll have to check. If that's the fix then testing is back on tonight. :good:
[TouchPad Development] flintman:
Ok all set all. You have to use the recovery in the main post for now. if you are trying to reinstall and can't as you are get a /boot part can't format error install the recovery in the first post which is a flasble zip then you can reinstall. older recoveries that worked fine with kitkat should work fine with this one. I haven't looked into it yet but i think some of the new recoverys restrict format of /boot not sure just taking a little guess ATM.
[TouchPad Development] jsgraphicart:
So is that recovery only for restoring a KitKat backup or should we just go ahead and use that recovery for flashing Lollipop as well?
[TouchPad Development] flintman:
you don't have to use it but if you want to restore you will for now.
[TouchPad Development] rob_z11:
I have gone back and forth, and have no issue. My problem is that I can't go back to 5.0 again. May try to download zip again.
[TouchPad Development] rickpub:
Lol... i get the weird one.

I'll give it a go shortly. Thanks!

---------- Post added at 05:23 PM ---------- Previous post was at 05:06 PM ----------

Ok, since prior to wiping and installing lollipop i was on jscullens rom, i installed that rom then tried to restore my backup minus the b oot. Now my system partition cant be wiped plus boot still cannot be wiped..lol. hope the toolbox can f ix this...lol
[TouchPad Development] jsgraphicart:
First boot is taking FOR-EH-VER
[TouchPad Development] Moody66:
Art runtime is much slower to get going.
[TouchPad Development] flintman:
yes it does art is alot different then dalvik. im hoping with some time can speed that up. It's on the list 8)
[TouchPad Development] jsgraphicart:
Oh I know. Newer hardware like my Nexus 5 takes forever on first boot. I was expecting the longer boot time for our older TouchPad. :)

---------- Post added at 07:14 AM ---------- Previous post was at 07:01 AM ----------

By the way, here's a little article I found regarding this ROM. Also has a pretty nice video in it.

http://liliputing.com/2014/11/hp-touchpad-gets-android-5-0-lollipop-unofficially.html
[TouchPad Development] Moody66:
Hnmm. His is running much faster than mine. Guess i will completely wipe and start from scratch. Thanks for sharing.
[TouchPad Development] moonlonely:
I actually did a dirty flash, because I was lazy (and just wanted to give this ROM a quick try before shooting that video). It's still kind of sluggish, but I didn't have to reinstall any apps.

When there's a more stable version of the ROM I might do a wipe and clean install.
[TouchPad Development] flintman:
Working on speeding up now. Checking out these art settings. I've been running for a day or two not much on it but smoothed out after a little bit. I m holding off on camera for right now. Want to stabilize it.
[TouchPad Development] jsgraphicart:
We don't need no stinkin' camera. :p
[TouchPad Development] suzib6sw:
I updated my 16G to 2/20/15 earlier.. This TP hasnt had Facebook logged in before. On tapping the Facebook App, the machien froze for about 2 minutes and rebooted.. It then allowed me into Facebook so I could sign in and browse around..

This flash was not over the 18th's and wiped the dalvik and cache though the updater..

Im just trying the 32Gb TP now.. I tried FB on the 18ths with no problem. Just flashed 2/20 and wiped Dalvik and cache as per "normal".. FB worked fine first time on the 32Gb..

Pete
[TouchPad Development] sokratz:
Nice. Once more into the fray ;)
[TouchPad Development] flintman:
I'm noticing its random. Once it loads its usually fine. I'm randomly using it and working every time after that initial issue. Nothing good in the logs to explain why. Still looking.
[TouchPad Development] flintman:
Facebook just had an update and it seem to fix the problem just updated three times and Facebook worked every time. Must have been a Facebook issue
[TouchPad Development] EricBlade:
I've been playing around with Dev options and toolbox options just for fun :) enabled the Dev option to force all apps to use the GPU, and the toolbox zram option at 30%... After some pretty serious initial bumpyness at the first start, it has smoothed out a ton, and is a lot smoother operating things like gmail than it was before...
[TouchPad Development] gaww:
Never use facebook.

If I continue to have issues with latter updates I will wipe system. Used to crack flash CM dailies, and after a week or two they headed south. Wiping system usually cleared it up but occasionally had to wipe everything..
[TouchPad Development] EricBlade:
* note: zRAM option does seem to make the system somewhat less stable. Using the 2/20 build. Once it gets up and running, it's quite smoother sailing, but less stable. Just figured I'd let others know, since I did mention the zRAM option, which I dont' recall being in prior builds.. hoping it will get more stable, but for now i'm turning that one off again.
[TouchPad Development] Vash:
Man, I don't know what you've been doing, but keep doing it!

20150221 got rid of a lot of delays across the board, especially when switching apps.

Every time I flash an update I get a bit closer to the perfect tablet.

Also, I just switched from Chrome to Ghostery, you people should try it out, it's much faster on the Touchpad.
[TouchPad Development] nevertells2:
I gather that you don't miss the ability of Chrome to link things like bookmarks, calendar, etc across all your computing platforms. I like the fact that no matter which device I use, cellphone,tablet, laptop, or desktop, all my bookmarks, contacts and calender information is there. Does Ghostery do something like that?

NT
[TouchPad Development] emph4tic:
Xposed?

I finally had a chance to make the switch over from KK and am really impressed how well this is running on my old TP4G.

I was hoping to try out the Xposed alpha to get my tweaking fix but kept getting bootloops after flashing and rebooting. Out of curiosity, has anyone else been able to get Xposed successfully installed on Evervolv?

Otherwise awesome work as always flintman!
[TouchPad Development] suzib6sw:
[MENTION=3716175]flintman[/MENTION]

I May have narrowed the audio down a little?

If you turn off sound using the volume button while on , say the home screen, start up Crackle or netflix or youtube and try and increase the volume, nothing happens.. BUT if you then go into settings , sound and then move the sliders up and down, it all works fine..

Could that be related to these audio lockups?

cheers..

Pete
[TouchPad Development] Vash:
No, but I don't use the browser on the tablet enough to care about that. I'd rather have decent speed :)
[TouchPad Development] emph4tic:
I suppose you're right. It's just hard not being able to jump on the Xposed-3.0.0 bandwagon what with all the useful improvements devs have made atop of L. Hopefully it doesn't take too much more time to sort out the SELinux and install workarounds for it.
[TouchPad Development] flintman:
Well i was looking at the Xposed framework today and i dont think this will ever work with the touchpad. The reason for this is there is one ART hack in order for the TP to work. Since the framework replaces the libart.so file this hack isn't there anymore which will cause the device to boot loop. I have looked at this hack for a work around and still haven't located one. This also goes for the CM ROM as they use the same hack on the TP. So sorry to say Xposed won't work unless they add this hack for a device specific Xposed release. Sorry all for the bad news.
[TouchPad Development] Tripple-c:
I was wonder if there was a technical reason why photos are scrambled if take with any level of zoom some of the photo Android apps can do. You see it working but the captured image is what is distorted with best described as Horizontal bars. I am currently working with "Camera ICS" but there are others and do the same thing. Its not a big deal since it is a front facing camera so selfies are pretty much it. Taking a photo of something else is problematic as I have to guess at the field of view of he short and button location.
[TouchPad Development] flintman:
The camera isn't 100% and is low prioirty to make 100%. I have owned and used my TP for over a few years now and only use the camera to test it. I have it operational for now and maybe down the road get more features going along with the blue tint when recording. Its a very useless camera only good for video chats and thats about it. I don't see the purpose of zoom and looking to pull that out. But like i said low priority.
[TouchPad Development] gaww:
Totally agree = don't know why anyone finds it important.
[TouchPad Development] potatohead:
Camera on my TP never worked, I believe it 'committed suicide'! LOL

When flintman released the 0206 rom, I 1) dirty flashed it, camera didn't work (goes without saying); 2) deleted the camera app and re-installed (as proven to work by others here), didnt work too.

Finally sat down to clean install the rom some time last week, camera crashed upon launch (camera has stopped), I was taken aback as was expecting it to work without problem.

I booted to webOS subsequently, launched its own camera app and the app just hanged (webOS didn't hang though, I was able to close the hanged camera app by swiping it up).

By now I kinda conclude there is some hardware error with the camera module in my TP, I have never used camera on the TP before nor ever dropped it.

Anybody with similar experience or is there any hardware test out there which can conclusively tell me what is wrong?

Any help is much appreciated, thanks!
[TouchPad Development] flintman:
Like i have in the first post try and delete the DCIM folder from your sdcards. Reboot and try again. See if it works. I had that issue with the camera app crashing and there was a corrupt file in the DCIM folder causing it.
[TouchPad Development] potatohead:
thanks, but no joy.

there was the first thing i tried when i dirty flashed (pointless, but i tried anyway) and also after uninstalling and re-installing the camera app (worked for others)

in fact I have just checked both the internal and 'external' sd, no DCIM folder in either

I really started clean when i clean flashed and converted to f2fs - formatted every partition and neither backup nor restore, set up the TP from scratch

tell tale sign that mine is a hardware problem - i cant get the camera to work even in webOS; just needed suggestion or how to conclude that it is really a hardware problem.
[TouchPad Development] gaww:
If also not working in WebOS - it most likely is hardware.
[TouchPad Development] suzib6sw:
The Tp suffers from a mechanical disconnect of the camera module. Power it down completely and gently squeeze either side of the camera lens. Be careful not to crack the screen but often this fixes the issue. Or open it up and reseat the camera cable. .. Boot into webos to check. If it works there it will work in lollipop.

Pete
[TouchPad Development] potatohead:
my thoughts exactly, asking ard if there is a set of tests for TP's hardware to turn this conjecture into conclusion.

Thanks Pete for the advice, but no joy here too, have pulled up the guide for removal of TP's camera module from iFixit previously to understand the position of its connection, after which tried to nudge the area where the module connector meets the board gently to see if that changes anything, to no avail regretfully.

The guide did mention any attempt to open up the TP will most likely result in broken clips (that secure the top and bottom), as such I am not too willing to carry out the operation. It is afterall the camera module only that malfunctions, not really worth the broken clips.
[TouchPad Development] MicroChip:
I used tp toolbox to clean and install 2/21 on my tp 32gb and i am losing sound a while after a reboot. Hoping for a fix as i use my tp as an alarm clock and the alarm goes off but no sound. It comes back after a reboot but only for a while.

Thanks!
[TouchPad Development] flintman:
Is it a 4g model?? Also can you get a logcat and dmesg. Seems a select few are having this issue. I have three tp and i have listened to music via spotify for 8 hours straight on all of them not once loosing sound. I have also tried to get them to loose sound and i cant. Logs will be needed to help me determine what is happening. The fix maybe out with 5.1 as well as it states that some devices are loosing sound.
[TouchPad Development] MicroChip:
It is not a 4g. I will get logcat and dmesg. Might have to wait for the weekend.

Thanks!
[TouchPad Development] gaww:
Am on 21 and no sound issues. I only used toolbox to resize partitions coming from 4.4 and use molded TWRP to clean install an early version and then updated without wiping to the current version. Maybe try reflashing with recovery.

Basic camera works so-so also (no video but don't care - don't use it).
[TouchPad Development] gabhroo123:
Video Issue

Thanks for all your hard work flintman!

I have noticed that the video (youtube/netflix) stops working after certain time. You can keep playing it continuously, and it works. It is mostly after you stop the app and restart it, that the issue appears. It is also accompanied by sound loss in general.

I have attached logcat if that helps.

Thanks!
[TouchPad Development] chmcarro:
What did you do to clean it up?
[TouchPad Development] flintman:
So I have spent the last few days not programming but using my TP pretty hard to test out everything over the course of a few days. I have been very stable no audio drop offs or anything along that line. I have been looking at the chrome flashing red border. Now strictmode is disabled and there are no more settings to eliminate this. Im starting to think its chome itself. Anyone try this on CM? Im curious if CM is having the same issue if so then its the app itself. If not ill keep digging. Let me know please

Thanks
[TouchPad Development] EricBlade:
So, I flashed 2-21, and then I took off with it for a work trip for a week. I had zero sound failures, and only one total failure that required a hard-reset (it was stuck at black-screen with the notification light flashing). However, it spent most of it's time during this trip sitting on a touchstone, being my daily calendar. As soon as I took it off, and started seriously using it, I had a sound-related lockup.

It seems that a possible cause is letting the screen timeout happen, and then almost immediately turning the screen back on. Seems especially prevalent when the screen timeout is set to 30 seconds (I set it this low because I wanted to try to get the battery to last during my entire plane trip.. didn't happen)... screen timeout -> press power -> sound dead. if screen lock came up, entire device is dead.

What I'm not sure is if this is happening when the screen timeout occurs, or when turning the screen back on. Of course, I don't have logs because I was on an airplane :-S

I've reset my timeout to 2 minutes, but it does seem like using it while on charge most of the time prevents this from happening. I did use it quite a bit from the touchstone, but I rarely took it off the touchstone until it was time to get back on the plane.. and once I did, I ended up having to reboot it several times.

Will go digging for logs next time it happens, since I'm back home now where I have all the tools :)

I also noticed during the trip, that the Battery app showed a "Miscellaneous" drain of almost 50% of the battery capacity .. ie, in the Battery app's "Unaccounted" budget. Would this lend any possibility to my theory that the 4G radio is running, despite the software not having any idea how to operate it, and my device being in airplane mode?
[TouchPad Development] EViollet:
Hi.

I tried all 3 variants of CM12 available on this forum starting with Evervolv. I managed to stick with it for a week, having to restart the TP at least once a day because of the sound issues. I also had the red blinking with Chrome, but I can live with that.

I then tried the CM12 nightly with 3.4 kernel. Same issues. Sound was dropping at least once a day.

I am now running a CM12 nightly with 3.0 kernel and I have 0 issues : no more sound dropping, and, strangely enough, Chrome doesn't have the red flashing border.

I don't know if there are any other differences in the 2 CM12 nightlies apart from the kernel version, but I found it quite interesting.

Good luck.
[TouchPad Development] flintman:
Im going to try something. I'm not having any issue with sound but i have an idea on what might be going on. If all works fine ill post a test build and everyone with audio issues can test with this i may add some additional debugging to pinpoint the problem if it is still happing after what im trying. Ill keep you posted.
[TouchPad Development] flintman:
Ok AUDIO test build up. If you can upload logs via the toolbox under settings after you loose audio(Hopefully you don't). Just select DMSG and logcat.

Thanks
[TouchPad Development] topdawg7793:
Will try this tomorrow morning. F2FS support is permanently implemented right? It wasn't just for that specific build in the OP? Is there a noticeable performance gain at all?
[TouchPad Development] bundys:
Did a wipe and restored my last working backup image from TWRP.
[TouchPad Development] flintman:
f2FS will be there in all builds going forward. Benchmark test slight increase in i/o.
[TouchPad Development] flintman:
Newer build up. Elginsk8r updated the kernel a little more last night which there was some audio updates in there as well. I hammered my device trying to kill the sound and works everytime. Same goes for the logs if you loose audio. Also please if you can give me some detailed steps on how you lost audio that would be great as well. I have tried everything that was suggested in the post when people had issues with audio and so far i can't get it to do it. Hopefully its fixed. Let me know.

Thanks
[TouchPad Development] EricBlade:
I'm going to give it a shot. Not usually able to get to Settings/Toolbox, because the system UI halts when it plays the unlock sound :)
[TouchPad Development] Trainer_H:
does the rom automatic format my partition to F2FS or should i do it by my self?
[TouchPad Development] nevertells2:
You are not keeping up with "required reading" [MENTION=528728]Trainer_H[/MENTION]. :p Go back and start reading from post #723.

NT
[TouchPad Development] flintman:
Just curious. Is the audio fixed?? Haven't heard

Thanks
[TouchPad Development] EViollet:
If you haven't heard then the audio must still be broken... ;)

Sorry about that... :) :silly:

As I stated previously I switched to another ROM and haven't had time to try your test version I'm afraid. I'll try to get down to it this weekend.
[TouchPad Development] EricBlade:
http://paste.evervolv.com/view/09d34ca2

Logs immediately after a sound crash, then a hot reboot.

Hope it helps? Let me know if I can do more.

I picked it up off the touchhstone, did a bunch of email things, set it down while I got ready for bed, picked it up, the screen was off. Turned it on, swiped the lock screen up, and that was all she wrote.
[TouchPad Development] flintman:
Thanks will be studying this. Anyone else that had audio issues still having them??
[TouchPad Development] EricBlade:
I did forget to add, that was the last testing build that you posted, with the changes you mentioned might help, on the 4G.
[TouchPad Development] Torqd505:
I had the audio issues on previous builds, but since installing the testing-2015.03.02 build audio has been perfect.

I have the 32gb wifi.
[TouchPad Development] flintman:
the 3-3 nightly isn't the most up to date. the test build is the newest. We are having issues with google syncing on our nightly box. Ill let you know when its fixed
[TouchPad Development] silvbm:
Last test build is running really good! Flintman, what do you think about RRO/Layers?
[TouchPad Development] flintman:
Never used so i can comment on it. We do use CM theme engine.
[TouchPad Development] silvbm:
Maybe you want to check this.
[TouchPad Development] gtallmadge:
Just installed and am really impressed. Only issue so far is Chrome and Chrome beta having the red flashing.
[TouchPad Development] dewman:
OTG

I am new at this but the nightlies have been working pretty good. Just a quick question, how do we enable OTG with this?

Thanks
[TouchPad Development] Torqd505:
Touchpad does not have hardware to power OTG. The only way it kind of works is with external power supply.
[TouchPad Development] nevertells2:
I believe it has to be supported by the build you install, so Flintman will have to answer that part. It was supported in older builds.

Try Googling "HP TouchPad OTG" and check out the hits you get.

NT
[TouchPad Development] flintman:
It is supported but needs an external power source to work. I have hooked up mouse, keyboard, and USB drives to it.