yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] gaww:
My comment was NOT pointed at your work or schedule - without which, as with many, my Touchpad would be a large paperweight.

I was only commenting on everyone else - usually there is more chatter on the thread. I was then wondering if a separate one on 5.1 had been opened.

As you noted earlier - the latest nightly and test build are working pretty good. I am lucky, as I have not had issues with any functions that I use thanks to your excellent work.
[TouchPad Development] flintman:
I wasn't taking it as that 8). It was more of an update for everyone. I'm still hammering away. I do have it pretty good but we over at evervolv decided to go another route and rebase off of caf rather then aosp. With the hope of easier updating.
[TouchPad Development] Steelskinz:
Means better performance with our snapdragon isn't it ? :D
[TouchPad Development] gaww:
Now the important question - what are you running for?

We could have a pool - like the below:

a. Mayor

b Alderman/councilman

c. Dog catcher

d None of the above

Good luck in any case.
[TouchPad Development] flintman:
Well I'm currently on the community planning commission and just rerunning but a lot of work to get on the ballot 8)
[TouchPad Development] jerryatherton:
Good Luck!
[TouchPad Development] nevertells2:
Never thought that a politician could be any good a writing code. :p

Good luck

NT
[TouchPad Development] vqstaphbeard:
Good luck! Sounds like you have quite the schedule.
[TouchPad Development] venkythegeek:
What is caf?
[TouchPad Development] shumash:
codeaurora forum

http://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/
[TouchPad Development] flintman:
Ok just got the TP going a few hours ago on 5.1. I have been playing with it for a little bit now. Still has more work but figured id let everyone play. Im curious how BT is working. Its fully CAF now and my hope is things get fixed. Have fun.
[TouchPad Development] FaberfoX:
Booting it up for the first time after dirty flashing over your last 5.0, that was running amazingly well, on F2FS. Had maybe one or two reboots for the week I used it, under heavy load and with tons of apps installed, will report back on how this one works. So, is bluetooth supposed to be working on this one? Will get my dualshock 3 charged if it should.

Btw, amazing work, thanks!
[TouchPad Development] potatohead:
many thanks, understand it is WIP, no joy here but juz wanna provide some feedback.

did a twrp backup and flash clean.

deal breaker was wifi, would not connect during initial boot, after skipping setup to turn wifi on and off, it connected.

connection broke after a few mins and it refused to connect again (even after turning it off and on and switching between 2.4ghz and 5ghz SSID), rebooted and the same scenario repeated itself (my router is asus rt-n56u using the Ralink 3662 chipset, guess the new wifi driver from CAF is not playing nice with it).

internet stability on the touchpad is crucial for me as I use it mainly to stream live tv shows, restored the backup and m back to 5.0.2 for now :) (my main gripe abt the 3-19 build is the very bad battery consumption during standby, otherwise it is solid)

looking forward to giving your next test build of 5.1 a try when u roll it out :) many thanks for your many hours of work on it!
[TouchPad Development] tpuserhp:
Thanks for the 5.1 ROM. I did a fresh install. My problem is the keyboard is very sensitive. I typed in one character and it gave me the same character twice. It took me a while to enter the WiFi password correctly to be accepted by the system. I have tried many times to enter my google account and password so that they could be accepted by the system. So far I am unsuccessful. I will try again tomorrow. But I will restore to

5.0.2 ROM as it takes a long time to do a simple thing like entering a password correctly.
[TouchPad Development] schwatter:
5.1 is really flawless and smooth for me :good: except the touch responsive as [MENTION=5333182]tpuserhp[/MENTION] mentioned.

Did also clean install at second because dirty started a lot of forcecloses.
[TouchPad Development] flintman:
Ya still got some more code to bring up. Im creating a list of things that arent working now along with what everyone is posting. In regards to wifi on init boot just go back after it fails during the wait for at least 2 mins fails and it goes right through. Its a start 8)
[TouchPad Development] babcocca:
Would be interested in the BT functionality, if someone would test it.
[TouchPad Development] tpuserhp:
I decided to stay with 5.1 ROM even with the touch responsive issue. I still have the BT issue of not detecting my BT speaker device as in 5.0.2. WiFi is not connected after boot. But it then stays connected after that. The performance of 5.1 seems to be better. Thanks.
[TouchPad Development] FaberfoX:
Update: dirty flash didn't work for me, constant force closes on core and phone, so I wiped it clean and started from scratch. Had the reported issues with the touch sensitivity, boosting minimum CPU speed to 486MHz seems to have fixed it. Had to skip the initial WiFi connection as it didn't seem to work after a few minutes, turning it off and on afterwards got me a solid connection. Right now, installing about 80 apps, close to 30 installed so far with no issues, on 5.0.2 I had to reboot a couple of times to get them all installed (errored out after ~20 apps or froze)

Performance is great, don't remember it being so smooth since the 2.x days. I'm loving it!

A while later: 86 apps installed, everything working beautifully so far. Touch is a bit too sensitive still but not that much of a problem. Only made the two tweaks I usually do:

Added qemu.hw.mainkeys = 1 to build.prop to get rid of the nav keys (as I use LMT) and created /data/local/userinit.sh containing echo 1 >/sys/module/a6/parameters/disable_dock_switch to make the touchstone behave just like a charger instead of a dock (I hate that apps/pages refresh if you don't do this)
[TouchPad Development] Vash:
Every time I start considering buying a new tablet, you come along with a new update that makes the TouchPad even better!

The latest version improved responsiveness so much I find myself switching between apps just because it's so smooth!

Thanks man, great work, great work indeed!
[TouchPad Development] rebel1699:
Just a few things about the Evervolv 5.1. First off, awesome freakin job getting it on here in the first place. I am just going to list some positives and negatives of the rom currently. I well understand that this is a test release, so this is all in the spirit of progress.

Of course, I expected the wifi not connecting on the setup. No big deal, it can be done later. Setup always annoys me anyways. I would rather always do it from settings. The over-sensitive touch was also expected. What I have noticed is it is only occasional, and only while using the on screen keyboard. At the same time, maybe I only notice it with the keyboard because every sensitivity issue seems to be magnified when trying to type.

So far, Titanium Backup is dead in the water. It will not restore app+data with batch or one at a time. I don't know if this is a rom issue, or if TB needs another update. Just throwing it out there. Overclocking to the next step on maximum was burning through battery. But honestly, who does not expect that? Battery without overclock is still a little harsher than Evervolv 5.0.1. I have no doubt that will be a memory before long. To this point, those are the only negatives. I don't even like calling them negatives.

The speed on this thing is RIDICULOUS! It shocked me how fast it is. 5.1 has a nice feature in that the wifi and bluetooth options in the status bar drop down menu, have drop down menus of their own. Tapping the word "Wifi" and Bluetooth" no longer auto opens the according menu in settings, but gives you the connection options right there. I am very happy to see this feature. Adding other users to the tablet works exactly as it should. Added one for my other google acct, and it functions perfectly. Wifi has given me only one issue, and that is it did not auto connect to the network after a reboot. Yet again, more than I would have a right to expect from a test version of the rom. Bluetooth did not work for me. I worked on pairing it to my S4. The TP did not find anything during scan, but the S4 did find the TP. Upon trying to pair, it almost immediately reports that it cannot due to "An incorrect PIN or passkey". Bt is always tricky on early ports, so I was not too surprised. The responsiveness is amazing. the fact that a test rom could be so polished says alot about the devs involved. Overall, this test is very polished. So much being so good so early is a great sign for the continued future of Evervolv on the TP. I'll be leaving this 5.1 on here till your next release is ready. Many thanks for the continued support of this tablet. It may be getting old, but it is still my favorite, by far. If you ever happen to need any tests done, error reproduction or logs collected on this, don't hesitate to ask.

ADDL- While reading in the Nexus 7 forum, the same wifi not connecting during setup was also reported there. The rom was CM 12.1 based. Just like here, it is recommended to skip and do it from within settings. So, we are not alone on this. The thread can be found here http://xdaforums.com/nexus-7/development/rom-resurrectionremixlpv5-3-6-20150223-t3038569 post #5
[TouchPad Development] bsorli:
5.1 testing and Latest notes

Yes I agree that most everything about this build is SUPER Fast and spot on configuration wise.

My install was done with a fresh wiped and cleaned KK build (began to get sluggish) that I backed using Titanium Backup and usual full backup. LP is certainly a life saver for my TP, but not without two primary things I use all the time. These problems include:

WIFI - like many others here...system goes to sleep and won't return previous WiFi settings

Bluetooth - Keyboard and Headset

WiFi can be fixed by doing a quick reboot, but this is obviously inconvenient. Tried as recommended adding 802.11G to the mix that helped initially getting me online/making viewable, but connectivity would only last as long as the unit stays awake. All the usual "Forget Network" and reattach does not work after it loses the initial connection. Also love the pull-down features like rebel1699, but this interface is inconsistent and not quite working...

Bluetooth keyboard tries to pair with my Logitech K810 (very reliable unit), but the onscreen directions appear briefly (less then 2 sec.) and then disappear before I have chance to read and input pairing code. Like for example "type 675343 and press Enter to pair with keyboard." Bluetooth doesn't even recognize my original headset that worked last week under KK.

Would love some feedback (should I go back to a more stable/non-test build?) and looking forward to future updates. Too many positives about LP that can't be denied and CAN'T wait for a stable build.

Please let me know if there is anything you need and how I can help!

Thanks as always for the support!

Sorli
[TouchPad Development] rebel1699:
As far as whether you should go back to a non-test rom, that really depends on how bad you need/want the features that are not worked out yet. Personally, I don't use bluetooth in android on TP, only in webos. I like the answer/make call and syncing messages/texts (map) feature that webos bluetooth provides. I never have to put down my TP to answer a call. Oh, how I wish Android would incorporate that into their stack. I also have a Nexus 7, so I don't mind having some features on the TP out while this rom is further developed. Allows me to enjoy the testing process. Others really need it as functional as possible, and should probably stay on an earlier, more fully developed rom until this has a few more versions to work the more noticeable bugs out.
[TouchPad Development] bsorli:
Wow thanks for the reminder and I remember those features on WebOS, but it has be a long time since I booted WebOS and last year removed it completely from my build. Half the WebOS team is now working for Google, so I'm also hopeful they continue making progress and can also integrate some of these useful features (that no one is doing...except maybe Blackberry?).

Speaking of more reliable ROMs...I also tried [Lollipop] [5.0] CyanogenMod 12.0 nightlies [3.0 kernel] daily, but this did not work at all and Bluetooth didn't even think about connecting on either keyboard or headset. May have no choice and have to head back to JB or KK to survive the rest of my semester.

Thanks for the quick reply! Sorli
[TouchPad Development] gaww:
My HP keyboard connects OK on 5.0.1, but have not tried on 5.1 test yet - may wait for next test build
[TouchPad Development] rickpub:
Has anyone gotten titanium back to restore on the 5.1 test build? No go for me...

---------- Post added at 02:12 PM ---------- Previous post was at 01:30 PM ----------

Ok, got it to work..sort of. Under 'preferecnes' find 'troubleshoot settings', then set 'app processing mode' to interactive. You will have to hit accept and install on every app, but it at least restores pretty quickly.
[TouchPad Development] flintman:
Mine worked right out of the box. Building a new build now and will test. Updated a few repos today for another device the s4. Its funny more stuff worked right away on the touchpad and the s4 has some issues. Just want to test these changes before i release.
[TouchPad Development] rebel1699:
As my post said, tb did not go for me. Coincidentally, I also have an S4. I look forward to seeing that as well!
[TouchPad Development] flintman:
I plan to get Bluetooth going tonight on the s4 while i push the tp through some tests. If i do you will see a test version on the s4 section.
[TouchPad Development] nevertells2:
Do any of you guys having problems getting TB to work on 5.1 know how to use TWRP to make a data only Nandroid backup of your 5.02 install and then restore it after you get 5.1 installed? I've done it on other Android JB and KK installs using TWRP and CWM. It seemed to work best using CWM, but the process is a bit techie compared to the ease doing it with TWRP.

NT
[TouchPad Development] rickpub:
Do nandroids regularly. Prefer to restore from TB. Got it to work. Thanks
[TouchPad Development] bryantjopplin:
I545 or i337? Safestrap? Unlocked?
[TouchPad Development] rebel1699:
There is no way it will work for Safestrap. Whatever rom you flash with Safestrap has to be compatible with the stock TW kernel. This will be in no way compatible. It will only work on intl, unlocked and loki-able phones.
[TouchPad Development] bryantjopplin:
I know it has to have a signed kernel, havent ever seen his rom for the s4 so was wondering. Also i have a mdk and mj7. Wasn't sure if he was doing something like this? http://xdaforums.com/showthread.php?t=3019132

Sorry for going off track!
[TouchPad Development] tpuserhp:
The apps are running fine after upgrading to 3.31 rom. But it seems no changes to touch sensitivity, bt, wifi issues. Thanks for the updated rom.
[TouchPad Development] heavyt:
Thanks for all your work. The touch sensitivity is so sensitive it's almost impossible to put in password.
[TouchPad Development] Tripple-c:
5.1 on TP but "Unfortunately prcess com.Android..phone has stopped"

Well clearly this is not working as will not complete the boot with this update I flashed via the Toolbox updater as I had the others. This state runs in a loop if OK is selected. Yes this is not a phone so that I understand.
[TouchPad Development] rickpub:
5.1 is snappy!! Touch is very sensitive, but i love the speed. Thanks. Flintman
[TouchPad Development] bryantjopplin:
Is this an ota?
[TouchPad Development] flintman:
Working that now looks like a mismerge in base. Chasing it down. :D
[TouchPad Development] EricBlade:
Loading the 3-31 testing to my 4g now :)

Loaded the last 5.0 build to the regular TouchPad that's going to my daughter, and noted that Bluetooth is pretty much non-functional on it, same as on my 4G. It recognizes my main PC, and that's it .. neither of my laptops, my N5, or any of my BT keyboards were recognized. Didn't bother trying to connect to the PC.

* edit: ok, up on 5.1. It was freezing up for many seconds at a time several times after start up, but before that, I did not have the keyboard/touch sensitivity issues. After it stopped freezing for many seconds, I started getting the touch/keyboard sensitivity issue. Seems like when it's not freezing, it's greased lightning, though.
[TouchPad Development] flintman:
April Fools build out.

Well i have been trying a letting and didn't get the double tapping i was getting before. I was chasing the code through and didn't really determine the cause as it wasn't clear. What i did realize is i never switched the GCC from 4.8-4.7. Since i have done that i haven't recieved the double tapping issues. Let me know if you are still having the issue. I may need to sit in my basement and toss on some 24, get a big bag of cheetos, and dig deep into the logs and source code 8) I plan on doing that for BT. Bt is such a hack for this device since they removed Bluez from the source. BT will be extermely time consuming.

Let me know on the double tapping (sensativity) issue.
[TouchPad Development] Yousie642:
Still getting the double tap issue on 4/1 build. Can't even type my wifi password correctly
[TouchPad Development] schwatter:
Looking good, no double taps here.

And yeah flintman you killed my flash :p :laugh:
[TouchPad Development] EricBlade:
haha, i wiped my device first before you did flintman :P

Ok, booted with April 1. Double touches still going a lot, maybe slightly less than before. WiFi did not remember my password, and I couldn't connect despite the password being correct. (it worked fine the first time with 3/31). Did a full reset.

First boot, it came up to the lock screen, and was frozen until the display went off. Turned back on, cleared lock screen, froze. Seems fine since then.

Still getting double taps. 5G network is visible, but unable to connect to it. Was successful connecting to 2.4G network. Bluetooth, I'm able to pair from the PC to the TouchPad, it still only sees the one PC, though. Maybe I should try turning off the PC and seeing if it detects another device. I wonder if it's aborting after picking up one. N5 can see TP on BT but can't connect. I couldn't pair from TP to PC, though. I am currently connected to it and using the BT Keyboard/Mouse functionality in Windows.

Wi-Fi dropped after I got the Bluetooth connection. Was able to re-connect without losing the BT. Still can't connect to 5G network. Camera works.

I just loaded all of the apps that come stock .. and I was able to return to my browser almost instantly, as if it had remained in RAM the whole time. Other than some app launches taking several seconds, this thing is OMG incredibly fast right now.. now I need to get gapps on it and see how much that affects it.

(can I download gapps from the device, and install it? i seem to have lost my USB cable.... *goes to chastise teenager in house*)
[TouchPad Development] tpuserhp:
Thanks flintman for the updated 04.01 ROM. Touch sensitivity issue still exist as others reported. Thanks for your efforts on this..
[TouchPad Development] flintman:
Try and shutoff the keyboard touch sounds. I have them on but I'm wondering with the audio changes there is a delay causing the rom not to register the event causing the double tapping
[TouchPad Development] tpuserhp:
The touch sounds and sound on keypress are off already. Thanks.

Someone suggested to raise the minimum CPU frequency to 486 before. I tried that and it did not help. This time, i raised it to very high like 1242 and it seems to help on the touch sensitivity issue. I will go with this setting for now. Thanks.
[TouchPad Development] flintman:
ok. Just curious if that was the issue. I do see in the logs that there are missed events before 4-1. Im not getting them any more after todays update. I will continue to dig into this. Is This on a clean 4-1 build? also what modifications did you make other then disabling touch sounds. Im just trying to pin down the location in the source on what is causing it.
[TouchPad Development] tpuserhp:
Hi flintman, i did not do a clean 4-1 flash. I just did a flash and wipe dalvik cache and partition. My apps seem to be working fine. I don't do many other modifications other than turning off Bluetooth. I have greenify, adaway andd viper4android installed. I increased minimum CPU frequency to a high value and it seems to help a bit. I will do a clean install and report later. Thanks..
[TouchPad Development] bsorli:
Flintman,

Noticed you released a new test on the 31st and I switched back to 5.0.4 to see it was possible to have better results with Bluetooth on previous builds and as referenced by others (having success with Bluetooth). So far, Bluetooth for me on 5.0.4 is still down and nothing I've tried (keyboard, headset) have worked or even initially connected.

Previously, you referenced Log Files (I think I found those located in Preferences) and curious if you would like to see my log results and lack of results connecting my devices to my TP running 5.0.4? I also thought about switching to your latest test build, but decided to wait and see if you would first like to see the Log reports before I update my software? Let me know if you are interested in these logs (and which logs would you like) and I'll test drive my Bluetooth configurations and hopefully will get some useful information you can use.

Thanks for the support and look forward to helping if I can!

Sorli...
[TouchPad Development] flintman:
The more information i collect on Bluetooth will always help. Bluetooth has been a pain since the removal of bluez support which goes back to 4.0 or 4.1. Cant remember and since then its been a challenge to keep all devices working. I only have about 5 devices. I work on getting all these going and if i can do that then it should be good. I plan on spending some time on it soon. I love a good challenge. ?
[TouchPad Development] flintman:
Thanks it will help rule that out.
[TouchPad Development] bsorli:
Do you want all the logs or just the hardware specific units? I think it references Radio, DLog, General, and one other and I can select all and see what information is provided and email it too you...or attach it to a discussion reply.

Let me know and thanks!

Sorli...
[TouchPad Development] tpuserhp:
I did a factory reset and then flashed 4-1 ROM and gapps. The touch sensitivity issue is still there with or without turning off touch sounds. I tried close to ten times of enteing WiFi password before the system took it. My TP is now restored back to the previous 4-1 backup. Thanks.
[TouchPad Development] EricBlade:
I clean installed 3-31 and then 4-1 clean also, and still seeing the touch sensitivity. No apps at all installed other than the stock.

Also just noticed that my device was in GMT time and 24-hour clock .. which was definitely not the settings before.. I don't remember ever having to set my time zone .. so perhaps remote time protocol isn't working

Bumped CPU governor to "PERFORMANCE", and it seems to have eliminated the touch sensitivity problem. THAT sure is weird. Perhaps some thing between CPU state changes and losing events? Just a guess. :)

At least, I've been able to type 3 different website addresses and "The quick brown fox" a few times with no repeats.
[TouchPad Development] tpuserhp:
Yes, changing CPU governor to performance helps a lot on touch sensitivity issue. Thanks for the suggestion.
[TouchPad Development] heavyt:
Key sensitivity very pronounced in the setup screens. After setup I went to preferences turn off vibrate and sound now key touch are now normal. My CPU setting is set for interactive.