yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] googlephone:
From my observations,it's router dependent, not router settings dependent.

When I use my premium Asus ac68 U router, WiFi will drop regularly even if I use only 2.4G hz.

After I switch to a cheap tenda router, which has only 2.4g Hz channel and the same settings as the ASUS,no WiFi drops anymore.

Edit: the same result for me for all android builds on touchpad, including cm11, cm12, cm12.1 and evervolve 6.
[TouchPad Development] Do Not Touch:
I just sent a donation to the Evervolv team -- I hope flintman gets it.

I hope others in this thread remember the developers when you make your list of Christmas tips.

I would be "one cheap bastard" in anybody's book, yet I still saw fit to send a couple nice donations to both the Evervolv team and to jcsullins for their continuing work on keeping our 4+ year-old HP TouchPads current. I know there are other deserving developers, I wish I could afford to donate to everybody who's ever had a line of code merged. Maybe some of you can step up for them.

Merry Christmas, everybody!!!
[TouchPad Development] Globaltraveler5565:
Marshmallow 6.0.1 v2015-12-13 WiFi shutdowns

Flintman, I tried to send the logcat today around 12:12pm est using the power button bug report mechanism, but I don't know where that went. I'll try to attach a tar compressed view now, but I'm not sure the XDA app will allow the insertion of attachments. Here goes...

Total commander file list (copy)

Total files: 1

/storage/emulated/0/Documents

GlobalTraveler5565-WiFi-failure.tar199682015-12-20 15:10:07

Argh, that didn't work. How do I upload the logcat file for easiest submission to you? Do I have to use the Web browser access Avenue or something else?
[TouchPad Development] johnjingle:
I am trying to install: ev_tenderloin-6.0.1-testing-2015.12.13.zip

With the latest recovery: http://evervolv.com/get/FLINTMAN-TWR...0-12-17-15.zip

For some reason I get to: Installing Evervolv... Patching system image uncondintionally...

and it stays like that... I've even left it for over an hour with no change.

Is there something I am missing, I have tried with F2FS, without F2FS, downloaded the ROM on multiple different devices, used TouchpadToolbox to completely start fresh twice and still no luck.

ANY help or direction would be greatly appreciated. I have never had a problem like this before with the Touchpad. Older versions of Evervolv still install with no problem.

Thank you and Merry Christmas!!!
[TouchPad Development] flintman:
Format your system partition. then try and reinstall evervolv and gapps. Make sure you use nano gapps. Others may be too big. Remember only data, and cache can be formatted to f2fs
[TouchPad Development] EricBlade:
Just upgraded from 5.1.1. Rss its time i finallu upgrade from my ancient recovery since i cant install gaps. Having keyboard and double tap/swipe issues juwt like in 5.1.1. Other than that, text input into chromium is extremely slow, havent tried anything els. I had read somewhere that android 6.0..1 is supposed to put the soft buttons in the left and right corners on tablets, but that doesnt seem to be the case here. Some option setting perhaps?
[TouchPad Development] Moody66:
If you don't clean install you will have issues.
[TouchPad Development] EricBlade:
Install was clean, complete system reset before hand. Looks like all the same problems from 5.1.1 have carried over exactly into 6.0.1, except for the new problem of Chromium being *extremely* slow to accept input. Just pointing it out, not complaining. :) And was hoping for the corner soft-buttons, that's something that i've really disliked since they moved to the center after 4.1 :)

On the bright side, the kernel is working on the 4G. I'm going to update my recovery to one of the recommended ones, and see if that makes any difference. I doubt it will, it didn't last time, but now I have to update it to be able to install the gapps. :( I liked my old one better than the current ones
[TouchPad Development] Moody66:
I have it on 16 touchpads. Not one is having those issues. Try a different gapps. Notice noone else is reporting it either. UI will need work to make the tablet style buttons.
[TouchPad Development] EricBlade:
Currently no gapps installed at all. Could be 4G specific issues, although I'd really only expect that to affect the radios, as the differences in the 4G and standard kernel should be almost exclusive to radio differences (there are API differences between how the WiFi and BT radios work when the cell radio is attached). In other releases, increasing the minimum CPU speed has made the problem effectively go away, which bothers me about it. I haven't tried that yet with this one. I should have my WiFi only unit back in hand in a few days to give it a try there too.
[TouchPad Development] flintman:
Ya my 4g is dead and no recovering it so i cant test and continue on with the 4g. I have been keeping my eyes open but the only ones are on ebay for 250+ 8(
[TouchPad Development] rickpub:
Same thing here with my asus ac68u running dd-wrt
[TouchPad Development] Moody66:
May have one amongst the many. I will be glad to send it to you. I never use the 4g model but bought a lot of them a couple years back. Will be after Xmas though. To much going on to dig through basement at the moment. Appreciate all you have done for touchpad users over the years.
[TouchPad Development] Nomad1600:
First time I've received an ota notification.
[TouchPad Development] googlephone:
There is nightly available: http://evervolv.com/get/ev_tenderloin-6.0.1-nightly-2015.12.24.zip
[TouchPad Development] flintman:
Yes they got them going last night. 8).

Merry Xmas all.
[TouchPad Development] Nomad1600:
Merry Christmas Flintman, and thanks!
[TouchPad Development] potatohead:
for all those who faced this problem after a fresh install - you probably flashed the ROM first, booted it and then went back to TWRP to flash the gapps.

to get around the 'setup has stopped' error, simply flash BOTH the ROM and the gapps file BEFORE the first boot, and you will be greeted by an error free setup page once your TP successfully booted.

:)
[TouchPad Development] Abaddon:
is fb , fb messenger and snapchat working on the latest nightly?
[TouchPad Development] Nomad1600:
I downloaded the latest via the OTA notification and flashed dirty using TWRP 2.8.7 (lined up both the ROM from the OTA location and the GAPPS from my Download location). Seemed to take way longer than normal (don't know if due to the new ROM, the new TWRP, or due to flashing dirty since I usually flash clean). Both the ROM and the GAPPS took longer than normal, but both booted up fine and its running well. Need to see what was changed. Thanks Flintman!
[TouchPad Development] babcocca:
Merry Christmas Flintman! As always, thank you for all your hard work!
[TouchPad Development] rfoster2009:
This ROM is nothing short of phenomenal. Had to go back to Evervolv 5.0.0 since it has working Bluetooth which I need. The working camera was a nice bonus too, even though it locks up on me when trying to do video.

Great work Flintman, I hope more great things may come for 2016
[TouchPad Development] jerryatherton:
Great job on the Marshmallow Flintman. I have always used you updates in the OP, how do the "nightlies" differ and which do you feel are more stable?

Thanks for the work you do.
[TouchPad Development] csmall:
By nature nightlies are more unstable. This is labeled as an alpha release to begin with which also by nature is unstable.

You want stability? Wait for a stable release.
[TouchPad Development] flintman:
Ok since we moved to nightlies i will be updating the thread. I will still release test builds as i have been working on BT. Doing something a little different here with bluetooth is we are trying out Bluez. I have it compiling and connecting via command line but when i go to hciattach i loose connection. Bluez needs a little work but i think its the best alternative to the HP as it supports bcsp.

I hope everyone had a Merry Xmas.
[TouchPad Development] rfoster2009:
This stack sounds very promising Flint. I haven't dealt much with Linux in years, but reading up on this seems to give us much hope for the longevity of TP!
[TouchPad Development] Nomad1600:
Flintman, 11/24 version, flashed dirty, significantly smoother than previous version. Great work!
[TouchPad Development] rfoster2009:
When you run the hciattach, what sort errors are being reported if any at all?
[TouchPad Development] flintman:
bcsp initialization failure. can chat with the chip via bccmd i just got to figure out what setting i may be missing in the psr file
[TouchPad Development] Nomad1600:
any changelogs... or is the gerritt the best source? DL'd and flashing the new nightly (12/25) but curious as to the best way to judge whether skipping a nightly is called for. Thanks!!

UPDATE: getting a storage space running out error message. I know MM takes up more space, and have removed lots of stuff already (all but the latest ROM DL, just the GAPPS DL (OpenGapps Nano). Running a pretty small list of apps, ie along with the stock apps I use XDA, Google+, Nova Prime, Netflix. I only have one TWRP nandroid. Any suggestions on what I can do to free up more space? btw, says I have 10.98GB of 12.1 GB internal storage used.
[TouchPad Development] flintman:
Nightlies script is being quirky right now but you will be able to click on log to see whats changed in that nightly. The script will generate for all devices even if there is only a device specific change. Example. Shamu gets an update to device tree. TP will get a new nightly. Nothing has changed TP wise in that nightly. So look at the logs to see what changed. There may not be anything new TP wise as i have been focusing on BT ATM. Im on vacation this week but have alot of other stuff going on. I hope to get BT going by the end of the year but not looking good ATM
[TouchPad Development] Nomad1600:
OK, thanks for the info. Since 11/24 seemed to have no issues including storage and 11/25 doesn't have any changes I decided to do a full wipe and reflash 11/24. Hopefully that avoids the storage issue. Have a great vacation!
[TouchPad Development] endofwed:
Hello. I am currently running evervolv lollipop. Its great but a little bit laggy here and there but nothing major.

Did anyone see any speed performance when upgraading to 6.0? Thanks!
[TouchPad Development] Hikikomorikruge:
Yes, I noticed a significant speed increase when upgrading from a LP nightly to MM. I'm haven't upgraded to the most recent MM release, but it should be just as fast.
[TouchPad Development] endofwed:
Hi,

I downloaded 6.0 using the updater but when I boot into recovery and select the option to install zip from sdcard, I am in the wrong directory. How do I get into the evervolv directory where the file was downloaded to?

I think i tried all direction options but I seem to be stuck in this directory :(
[TouchPad Development] Nomad1600:
It should download the zip in /sdcard/EVupdater . If you are using TWRP and are in the /sdcard/downloads you should be able to push the "up one folder" button, then choose EVupdater. Or, find the "/" and then click on /sdcard then /EVupdater.
[TouchPad Development] oinop:
Hi guys.

I have CM12 installed on my touchpad.

What would be the best way to install this ROM?

Is there a guide that I can follow to do a clean install?
[TouchPad Development] rfoster2009:
Clean install is a must per developer's instruction. Now, a clean install will entail wiping the data, cache, and dalvik. TWRP makes this easier in my opinion. Flash the TWRP 2.8.7.0 in the OP.

what recovery are you using currently?
[TouchPad Development] oinop:
Thanks for the reply.

I got CWM v.6.0.5.1 installed at the moment, and yes, I was planning to do a clean install regardless.

I was just wondering if there's any special process for this ROM.
[TouchPad Development] rfoster2009:
I went to EV from CM 12 and I did not need to use TP Toolbox as my partitions had plenty of space. For CWM, a factory reset, then wipe the dalvik. For the built in updater though, it's set to automatically work with TWRP. if you keep CWM, you'll end up having to manually flash the updates each time.
[TouchPad Development] oinop:
OK Thanks. I'll try to clean install and see how it goes. If I do install TWRP 2.8.7.0 with F2FS, is there something that I should be worried about?

I'm asking because for Note 2, I remember partition requirement being completely different depending on the ROM, and I just want to be careful since I don't know what F2FS means.
[TouchPad Development] rfoster2009:
F2FS is a flash memory based file system, whereas ext4 has been around much longer and is used with traditional hard disks. Twrp will not convert your space to f2fs automatically. Flintman compiled this version of TWRP that is compatible with the F2FS.

Basically, you can flash the TWRP and not change to ext4.

Hope I made a little sense
[TouchPad Development] oinop:
Yes, Thanks, Man.

You cleared things out perfectly. And I just flashed the latest Evervolv and it's working fine.

Thanks a bunch bro. Or sis.
[TouchPad Development] rfoster2009:
You had it right... I'm a guy :D

EV is my go to ROM for my TP, but all the devs have done great work keeping this 5 year old tablet relevant.
[TouchPad Development] firepower9966:
Saw this and thought it might be good to add to rom if it applies.

So what is Adreno idler?

Quote:

It is an idling algorithm,

an efficient workaround for msm-adreno-tz's overheads.

Main goal is to lower the power consumptions while maintaining high-performance.

http://xdaforums.com/android/software-hacking/adreno-idler-idling-algorithm-devfreq-t3134872
[TouchPad Development] Globaltraveler5565:
I flashed the Christmas release yesterday OTA using normal updater method and noticed TWRP 2.8.7 took a long time to load the OS and gapps. It was successful but took over 20 minutes; normally this process only runs for 10-12 minutes. I wasn't given the option to wipe the system partition by the updater routine. The updater set up the script after downloading the nightly and booted directly to TWRP which automatically began wiping delvik/cache and flashing the two zip files I had previously selected. Finally it restarted MM which finished rebuilding all apps normally. There was no indication of what was happening during the flash... Just the normal ones very slowly.

The nightly flash updater is a great development. It really works. But I can't explain why TWRP would run slowly like this.

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

Christmas is over

Now that Christmas is over, can the colorful gift wrapped logo on startup revert to normal Evervolv heartbeat image? I appreciated and enjoyed the amusing colorful light show during the holiday season, but isn't this the time to go more professional again? Just sayin'... ?
[TouchPad Development] Moody66:
MM has doze. You don't need anything else.
[TouchPad Development] Globaltraveler5565:
XDA App not connecting

After upgrading to the Christmas release 6.0.1 I can't get the XDA app to connect to the base server. It just sits there with the spinning gray wheel forever. I've left it go untouched for hours and it never completes the initial server touch. Other network based apps work fine. I'm actually writing this note from the LP - based TP, which works fine on the same WiFi network.

---------- Post added at 01:43 AM ---------- Previous post was at 01:33 AM ----------

Second issue: network drops

The WiFi network still drops out / turns itself off occasionally. I've noticed it happening about every hour or so, but good news, it turns back on within about 15 seconds and connects to the Internet automatically. This an improvement. At least it does restore the network. But the dropouts will disrupt any long up/downloads.
[TouchPad Development] Nomad1600:
I am replying via xda developers on my TP running the Christmas release. And havent had any wifi drops. Did you clean flash?
[TouchPad Development] Globaltraveler5565:
No, I used the updater which goes thru a stream of events with little input from me. I'll try to refresh it again in manual mode and being sure to wipe the system partition. Good suggestion. Thx

Edit: I refreshed Christmas release again manually via TWRP 2.8.7 using the saved zip files by wiping system, cache, delvic first. The flash process ran at normal, historically expected speed; previous flash via updater ran very slow. After ROM came up (it optimized 14 apps out of 69) I waited for everything to settle down over night. When I ran the XDA app, I encountered the same inability to connect to the server. XDA did raise a notification over night that a new entry existed. When I clicked thru that notification, same result stalling connection to server. Any other suggestions? I'll try reinstalling the app fresh and check out the firewall.
[TouchPad Development] heavyt:
Is there a seting to select full desktop.
[TouchPad Development] Globaltraveler5565:
Edit to post 363

Reinstalling XDA seems to have corrected the problem I'm seeing. However, when I tried to edit the previous posting 363, XDA popped up a brief note "invalid postid". Then it went into infinite swerling icon and stalled. It would allow the go back button and I could view other areas (notifications, participation, etc).

Edit: when I retried to edit post 363 above a few hours later, it worked like normal. I don't get it, but it's working fine now. Very strange...
[TouchPad Development] Globaltraveler5565:
Setting > display > dream time > clock setting reverted to analog after flash

After flashing the Christmas release of Mm, the dream time clock setting changed from my preference of analog to digital mode. I was able to easily switch it back to analog (I guess I'm just an old geezer at heart), but just wondering if this is normal and expected behavior of flashing a newer ROM. Shouldn't the user preferences be retained?
[TouchPad Development] EricBlade:
Touchscreen event problems are almost definitely present on WiFi devices, and are probably a kernel problem:

Installed Flintman's TWRP 2.8.7.0 on both my 4G and my WiFi 16GB TouchPad, and the touch-screen problems (duplicating taps, being difficult to scroll without also triggering a tap, the touchscreen suddenly not responding without turning the display off and back on) were present inside the recovery as well. This was not the case with my ancient CWM recovery that probably dated from the 4.1 days.

It was significantly worse inside the recovery, than it is inside the full OS. I'm considering the possibility that perhaps there were touchscreen firmware changes somewhere in the webOS 3.0.0 to 3.0.5 changes, but the WiFi one has definitely been upgraded to 3.0.5 .. the 4G one probably came with 3.0.2 or some such.
[TouchPad Development] Moody66:
If you to having that issue in recovery you may have hardware issues. Out of 16 touchpads I have yet to see any touch issues in recovery. And only a very small number of times have I noticed any touch issues in MM. Nothing more than I see in a factory device in MM.
[TouchPad Development] charleypick:
My Wifi 32GB Touchpad has no touch issues with MM that I have experienced. If you are having an issue in TWRP and in Android, maybe you have a hardware issue. Does this persist when you boot into WebOS?
[TouchPad Development] Globaltraveler5565:
Eric, et al ...

With the Christmas release of Mm, I see far less double tap happening. Usually in emails, haven't noticed any in hidden passwords so far. This is still early testing, but this version seems better (stable, fast) than October and early December test releases. This needs to be tested with Bluetooth keyboard (if we get a fix for bt soon).

BTW, I'm using SwiftKey addon instead of the standard on screen android keyboard, if that makes any difference.
[TouchPad Development] heavyt:
I am getting double tap errors in this built (1213). Didn't get them while using JC Sullins CyanogenMod 11 KitKat Builds (not once).
[TouchPad Development] flintman:
I have not had one double tap on my 32gig wifi model. What model are you running that has double taps.
[TouchPad Development] Moody66:
12/13 is old version. We are up to 12/25
[TouchPad Development] flintman:
8) anyone see something 8)
[TouchPad Development] EricBlade:
The WiFi one has Android 4.1 installed on it, I just swapped the Recovery into it, after I put TWRP on my 4G and the touch problems were so bad, that I had an extremely difficult time with navigating in TWRP to even perform a flash. As soon as I booted into the TWRP, it started giving me double taps, taps during slides, etc. Same as the 4G. It does not have any such issue in either webOS 3.0.5 or Android 4.1.

The 4G does not currently have webOS on it at all, but did have whatever version it came stock with, and did not have problems then. These problems came in sometime during the late 5.0.2 builds, before Flintman switched to working on 5.1.. And they range in frequency on different builds, and can be almost eliminated by turning the min/max cpu speed up to 1.7ghz for both.
[TouchPad Development] rfoster2009:
I had nothing but the utmost confidence in your success Flint! I'll be flashing this right now!
[TouchPad Development] Nomad1600:
Awesome, congrats!!

---------- Post added at 07:56 PM ---------- Previous post was at 07:53 PM ----------

BTW I have an original HP Bluetooth keyboard dating on this great news. ?
[TouchPad Development] flintman:
Still working it once i get a few devices going then ill release. But a major stone has past i have it enabled and discovering. Connected to my i phone but not my nexus 6 or my keyboard. Soon 8)
[TouchPad Development] rfoster2009:
One small step for man, and one giant leap for TP development yet again!
[TouchPad Development] flintman:
EricBlade unsure what is going on with your recovery but 4g models are not supported ATM. I had very minor random double taps in 5.1.1. Since 6.0.0 i have not encounter once on any device. I don't run over clocked. Can you get me a recovery log and dmesg while in recovery?
[TouchPad Development] MossyLawn:
I have seen a few double key entries as well using the ASOP keyboard. But it seems to have settled down after a few reboots and letting the ROM settle in.

The screen rotation is definitely a problem but it appears to be so only for the home screen. Once I open any app, the screen rotation seems to work fine, all orientations. When app is closed the home screen reverts and is frozen in either landscape or portrait as described. I have tried several different launchers - all the same ooutcome.

UPDATE: well, so much for that. After letting the TP charge/sit idle for about 2 hours, now the screen doesn't rotate at all.
[TouchPad Development] flintman:
Without titanium source this will be hard to solve my hope is once I get the external sd mounting it will fix that. Helium works that is what I have been using.
[TouchPad Development] chaos254:
Did a full wipe so I could try this out. Looking forward to seeing this progress. Thanks!
[TouchPad Development] Gil1957:
Just wondering how the video works on this OS. I mainly use my touchpad when I travel, watching videos and reading Nook books.

Thanks
[TouchPad Development] tpuserhp:
Thanks flintnan for your review. I did more testing this morning and I found two more issues. One is chromecast screen mirroring does not work. But i can cast video using chromecast to TV. The other thing is one tv streaming app does not stream successfully. The logcat is attached.

One observation is the settings->battery only shows the screen entry.

The majority of my apps work and thank you!
[TouchPad Development] tpuserhp:
For me, rotation stops working after a deep sleep, for the home screen and in any apps. I have the same problem with my nexus 7, 2012, MM. No fix yet. This is the only outstanding for me for my nexus 7.
[TouchPad Development] Gil1957:
Thank you for a great OS. Only problem I have so far is that Facebook keeps shutting down. Also when it stopped rotating, I rebooted. I prefer landscape, so I switched it to stay that way in settings.

---------- Post added at 08:37 PM ---------- Previous post was at 08:14 PM ----------

Not sure if this is a glitch, but I plugged the Touchpad into my computer and it found the Touchpad, but no files or folders.