yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] bundys:
Like you, I've had my TP overclocked the entire time I've had it - most of the time to 1.8 with no issues whatsoever. I'm hoping [MENTION=3716175]flintman[/MENTION] can figure out what is slowing down the UI in the lollipop build as I'm in limbo between 4.4 and 5.0 builds and would like to migrate to 5.0 fully. Unfortunately, even overclocked, we're not there yet performance wise to make the switch permanent (I have full faith in the devs, so I think its just a matter of time). I've lived through this before with the Galaxy Nexus 4.4 graphics glitches, but once that was resolved, there were some awesome performing ROMs for that phone.
[TouchPad Development] rickpub:
Installed the latest 12/6 preview... looking good! Still not able to oc beyond 1512... Is it possible that this is because I have the 64gb tp? I know it doesnt make much sense but that is the only difference that I can think of. Thanks!
[TouchPad Development] flintman:
Can u get me a logcat and dmesg. ??
[TouchPad Development] flintman:
Home buttons now wakes the device via EVToolbox(Disabled by default). Also updated SU thanks Elginsk8r and a few other tweaks.
[TouchPad Development] heavyt:
What's SU, is this the same as :su for root?
[TouchPad Development] jerryatherton:
SuperUser. Required for root.
[TouchPad Development] heavyt:
Thanks that what I figured.
[TouchPad Development] Trainer_H:
First of all, i like your rom :) i think i found a bug. if you chance your brightness at about 20% the display is getting dark. that's not normal.
[TouchPad Development] rickpub:
Will do. Thanks...
[TouchPad Development] jsgraphicart:
What do you mean the display is getting dark? 20% brightness is supposed to make your screen dark.
[TouchPad Development] Trainer_H:
Yeah. I mean very dark like the display is disabled.

Another bug.

Sometimes you can see minimal display bugs like you use a wrong display driver.

It's not very offen.
[TouchPad Development] jsgraphicart:
I'll have to flash the latest build and see about the brightness thing. Haven't noticed it getting THAT dark. And there will be obvious display bugs. The TouchPad isn't an Android tablet. The devs have to make with what they got. Sometimes that means hacking in certain things just to make it work.
[TouchPad Development] nevertells2:
Flintman should be the one to answer this. He may have made some adjustments in his build to address an ongoing complaint about users not being able to make their screen dark enough in a totally dark room.(Wife complaining about the bright screen at bedtime). Try a dark closet and see if you can still see the screen at the setting you say is too dark. BTW, how are you determining that you are at 20%?

NT
[TouchPad Development] flintman:
Just tested and if u have adaptive brightness check yes it does go blank at about 20% or below. Ill look at that. Leave adaptive brightness off or let it adjust on its own. If u have a case my case blocks the sensor.
[TouchPad Development] Moody66:
Could jcsullins latest addition of brightness control be used with lollipop?
[TouchPad Development] flintman:
Possible. Ill look at it
[TouchPad Development] jsgraphicart:
Did you materialize the toolbox or have I just not paid attention since the first version? Lol
[TouchPad Development] bundys:
Found a bug - setting custom dpi through toolbox to 132dpi didn't stick after reboot. Had to resort to using BuildProp editor, after which the setting finally stuck.
[TouchPad Development] flintman:
Elginsk8r did 8)
[TouchPad Development] Moody66:
Last build us much faster and more stable. Still really slow restoring apps from play store. Is it I/O or network that's causing it?
[TouchPad Development] flintman:
Ok got this fixed. Im working on a few other stuff today and may have this out in a preview today
[TouchPad Development] flintman:
Ya i do notice i think that will come together with some more updates.
[TouchPad Development] flintman:
i just tested and worked fine can you after you change the setting in the toolbox do a adb shell getprop then reboot and post adb shell getprop again and send me the link to it. Also has anyone tried this and experienced it not working after reboot?

Thanks
[TouchPad Development] nevertells2:
You are going to piss off a bunch of wives! :p

NT

---------- Post added at 10:39 AM ---------- Previous post was at 10:35 AM ----------

You know that restoring from a data only nandroid will give you back apps. settings, data, desktops, etc. Nothing should be missing from your previous install setup.

NT
[TouchPad Development] LittleNinja:
Thanks for this tip, didn't know it ! :)

JB
[TouchPad Development] bundys:
OK, I'll try to get those to you after work.
[TouchPad Development] Moody66:
Yes i know this. Howver its. still an isse and should be reported..
[TouchPad Development] flintman:
Think i may know what is going on I tested this on my 4g which im still running the older su. Need to add the code to the newer su.
[TouchPad Development] bundys:
My wife had a dental emergency so I didn't get to plug my tp into my laptop to get you the logs, but I suspect that you may be right. On the initial install, I had issues with SU, so I flashed SuperSU and all was well - until this little issue I guess. No worries though.

BTW, is there any way to issue those adb commands directly on the touchpad (I'm in the waiting room while my wife is being worked on and have the tablet handy but no computer to connect it to)?
[TouchPad Development] flintman:
ya terminal just type getprop it will display all the props saved

Hope all is good with your wife
[TouchPad Development] bundys:
Thanks, she'll be ok after a couple of days of rest.

So here's the setup. I managed to get the lcd density to stick at 132 by using buildprop editor - so that has become my default.

Now I've attempted to change the density through the toolbox to 140. After changing the value in the toolbox ui and before a reboot, it showed "current dpi: 140" and "default dpi 132". getprop command yielded 132 for lcd density at this point.

Reboot...

Toolbox still shows "current dpi: 140" and "default dpi 132". getprop command yields 132 for lcd density and by looking at the size of everything, I can confirm that is the true dpi being used.

Conclusions...

Even though the toolbox thinks it has changed the current dpi, it didn't actually accomplish the task.

After removing supersu and using the built in su, same results.
[TouchPad Development] wasd-:
Noone can confirm? :crying:
[TouchPad Development] jerryatherton:
I don't know what kind of device uses that.
[TouchPad Development] wasd-:
Docks like this
[TouchPad Development] jerryatherton:
Don't they have an AUX in?
[TouchPad Development] flintman:
UPDATE:

Elginsk8r spend alot of time getting the evervolv source up to speed and his test have been great on another device. Going to test out on the TP soon and hopefully get alot smoother which his tests have proved positive. Also have the DPI issue resolved and the screen blacking out if you turn the brightness down to far. Alot of good stuff in the next release no time frame but probably the next few days. In regards to the 4g i have cell service working but having issues with data. I must be missing something somewhere just need to dig in deep to find. Im hoping this weekend ill have time to hammer out those fixes but i know i have a busy weekend with the family but will see.

in regards to wasd- post. I'm not sure never tried when i'm digging through the code for my 4g data issues ill take a look to see if there is something in there.
[TouchPad Development] jsgraphicart:
I have never heard of the TouchPad being able to use the usb port for audio out. So I don't think it's possible. Maybe I'm wrong but I havent heard of it.
[TouchPad Development] wasd-:
Its an example, i know that you can use an AUX cable but in Android 5 you can use just USB like iPhone and iPods do.

http://www.androidpolice.com/2014/0...-android-now-natively-supports-usb-audio-out/

Thanks ;)

Its software side and Android 5 implements it. Only the USB must have OTG and TP have it :)
[TouchPad Development] jsgraphicart:
I forgot Google added that. I haven't actually seen it in action on any device though
[TouchPad Development] googlephone:
The first android device HTC G1 has the audio through usb.
[TouchPad Development] wasd-:
Some OEMs have added it, but just a few phones
[TouchPad Development] Vash:
Nice work, this works surprisingly well, all things considered!

Unfortunately it's neither fast or stable enough compared to 4.4.4 to replace it.

Keep up the good work though, I'm sure you'll get there :D
[TouchPad Development] nevertells2:
I suspect that it will take a knowledgeable programmer like Flintman to do some magic in the kernel to get "L" to talk to the audio circuits via USB in the TouchPad.

NT
[TouchPad Development] Moody66:
I think thay may be expectung a bit much for the old TPs. It was never designed for that. Lollipop wasnt designed for the touchpad. And hardware specs are so far out of date. Would be cool if someone does it. But i am doubtful about it. Lollipop itself pushes these things hardware wise. To me uts kinda pointless with bluetooth able to do the same thing. Juat my opimion though. If anyone wants to see what a difference JUST running googles backup,, tracing, etc makes, load the rom but no gapps and see how much faster it runs.
[TouchPad Development] flintman:
Well the TP didn't like those changes. Going to work on that getting everything operating smooth again hopefully we will be very close to kitkat once a few audio issues are solved.
[TouchPad Development] charleypick:
Microphone not picking up sounds

Using the 12/09 build (great build by the way!). Tried using Google Now and "OK Google from the AOSP launcher. It's not picking up audio. Should the mic be operating in this build?
[TouchPad Development] Moody66:
New settings in lollipop for that. If u go thru google now setup u will see it. Two nexus devices. Both of which I have to talk into like I am using the phone for it to pick up the audio.
[TouchPad Development] Atari-San:
If i remember, back in the kitkat day, using google now would make your tab lag and after sometime (sec to min), make it random reboot, Do you get the same pastern of problem later after trying this ? Just for knowing if that was finally fixed or much more broken (no microphone at all) or something else.

Edit : Seem i was late. But i would like to know the answer if you don't mind. It might be helpful to flintman too.
[TouchPad Development] Moody66:
Mic works fine. Google has made a change to ok google part. Likely to help on battery.
[TouchPad Development] flintman:
Well got the TP stable again after the latest changes along with a bunch of other changes. Once these hit Evervolv's github ill recompile and retest to ensure we got everything then ill release another test build. Ill tell you it's alot better now. I did jump up on the benchmark tests and it's smooth. i stopped using pagapps for now and switched to the straight LL gapps as they are more stable and when i release the next build i will suggest you do the same.
[TouchPad Development] heavyt:
I finally got the 12/09 build to install to my satisfaction. Using the TPTB TPToolbox-2014-05-18-v40 installer and the steps of using the toolbox, steps that [MENTION=4788108]McBeanTIO[/MENTION] (thanks) posted. I also used the novacom drivers for linux to install novacom on my Ubuntu box.
[TouchPad Development] heavyt:
I've noticed the browser closes every time I select settings in the browser's menu.
[TouchPad Development] Moody66:
Another jerk making money off of your work. On eBay.

http://m.ebay.com/itm/271704312877?nav=SEARCH
[TouchPad Development] heavyt:
Sad, very sad to see that.
[TouchPad Development] Mchasard:
I just install v5.0 with twrp recovery.... I succeed to flash it but failed to flash gapps i... So im blocked cause no explorer by default also.... Is there space size troubles?
[TouchPad Development] Moody66:
Just hook the touchpad to ur pc and copy gapps to it. Reboot I to recovery and flash them. No space issues. It's a data//media rom.
[TouchPad Development] nevertells2:
Moody, why don't you report his ass and see if his eBay post gets pulled. Although I don't like to see ads like this, this person is not claiming any of the builds are his. He is offering an installation service for Android all the way back to Ice Cream Sandwich. I have no sympathy for anyone stupid enough to send their TouchPad to this guy and risk not getting it back or it gets bricked.

NT
[TouchPad Development] shumash:
"A fool and his money will soon be departed". Caveat emptor.
[TouchPad Development] nevertells2:
And his TouchPad!!!! :p

NT
[TouchPad Development] flintman:
wow $60 to install a ROM
[TouchPad Development] Moody66:
Because i am not the developer... So it isnt my work he is infringing on.. Flintman or one of them has to do it. No difference than someone offering the service to install windows on a pc.... The windows isnt his to install.
[TouchPad Development] shumash:
[MENTION=3716175]flintman[/MENTION], check your PM when you get a chance.
[TouchPad Development] flintman:
New update. Finally back to a stable version. A bunch of updates in this one Clean install( factory reset and wipe dalvik) is required.
[TouchPad Development] jsgraphicart:
Clean install required, as in wipe data too? Even if we are already using the lollipop build?
[TouchPad Development] flintman:
Just factory reset and wipe dalvik
[TouchPad Development] jsgraphicart:
So I did a factory reset and installed the latest build. Is there something wrong with transparency in this build? The lock screen has a black background, the nav bar and status bar are black and pulling down the notification shade causes the background to go black.

EDIT: never mind. I think I found the setting
[TouchPad Development] Mchasard:
Thanks for this lollipop build even I find it a little slow... Camera is not working but I know that flintman will arrange all soonest....
[TouchPad Development] Steelskinz:
i'm amazed how hard you must work to provide us such builds. Thank you. Guess it's more than a personal challenge for you and as you share it with us we are glad to thank you. ;)
[TouchPad Development] flintman:
Ya i don't know if im a fan of this ro.config.low_ram tag. I'm going to remove it on the next build it doesn't give that much other then annoying black screen at lockscreen and some other black screen stuff to save on RAM.

You can remove from your build.prop for now if anyone likes.
[TouchPad Development] flintman:
It is a personal challenge. I push myself to find out how things work. It also helps that the Touchpad community is a bunch of great people, that pushes me even more to provide you with a great build. May take some time but we get there.
[TouchPad Development] sstar:
Hi Flintman

Firstly a big thank for this Rom.

I have followed all your instructions for this Rom and using your TWRP recovery and suggested Gapps.

Just a head's Up that your recovery is slightly larger than jcsullins Philtz recovery and as I also had TPToolbox in my boot folder it didn't install properly as there was not enough space. Once I'd removed TPToolbox I copied and pasted TWRP into the boot folder and everything was plain sailing, I'm not sure if anyone else mentioned that but it may be worth mentioning in the OP.

The only other problem is error 505 when trying to install Rom Toolbox pro which I'm still searching for a solution to.

Once again thanks for a great new Rom.

All the best
[TouchPad Development] jsgraphicart:
No need to remove it from build.prop to fix. I found a toggle in the toolbox settings for it. Just toggle it off and it prompts you for a reboot then it's back to normal. So far, this build is the fastest one yet. Loving it
[TouchPad Development] bundys:
[MENTION=3716175]flintman[/MENTION], dpi still doesn't work through toolbox on the latest build. Must be something with su as TitaniumBackup also complained. Clean install of latest build. Flashing supersu fixes TitaniumBackup, but still had to use buildprop editor to change dpi.

Also, is there a way to change the home button to simply wake the device just like the power button instead of bringing us to the home screen?

One more thing I noticed is that when the screen is off, background tasks get very little cpu time/priority. For example, updating poweramp and a couple other apps through the play store has been going on for over half hour with thebscreen off, while it only took an extra couple of minutes to finish with the screen on.
[TouchPad Development] sstar:
Re Home button go to Settings /Evervolv toolbox /interface and put a tick in Home button wake.
[TouchPad Development] bundys:
Not what I meant. I already have the option to wake enabled. What I mean is when you wake the device by using the power button, the screen turns on and shows whatever app you were on last, but when you wake it using the home button, it wakes up to a "blank" home page, not the last app you were in.
[TouchPad Development] jsgraphicart:
I haven't noticed this. I will test when I get home.

---------- Post added at 12:20 PM ---------- Previous post was at 12:13 PM ----------

By the way, anyone who wants updated Lollipop sounds can flash this zip here:

http://xdaforums.com/google-nexus-5/themes-apps/updated-sounds-lollipop-t2939529

I prefer these sounds. Especially the keyboard sounds. I can't stand those old "typewriter" sounds from Gingerbread. lol
[TouchPad Development] jsgraphicart:
I just tried this. I had the Play Store open and turned off the screen. I woke it up with the home button and unlocked and I was still in the Play Store. Don't know why yours acts different.
[TouchPad Development] bundys:
Hmm.. that's just wierd. I've had the same behaviour in Evervolv roms with KitKat and lollipop.
[TouchPad Development] nevertells2:
Let me offer up something here. I'm sure all of you are aware of TouchPads becoming bricked for no apparent reason. This has been an ongoing issue for a long while now. It prompted J.C. Sullins to create a script to help folks debrick their tablets. Sometimes it worked and sometimes it didn't. Regardless, I have come to believe that one particular thing I see folks doing could exacerbate the situation and it has to do with what you are discussing right now. The following is something I have posted several times before in numerous different forums and threads going back to early 2013. It's up to use if you want to buy into this, it may save your tablet, so here goes:

"I have become suspicious of constantly using the power button to wake up my TouchPads. I have switched to using the "home" button for that function and I'll tell you why. Have you ever forgotten whether your TP is turned off or just asleep. I can regularly duplicate the following: if my TP is turned off and I'm thinking it is asleep, if I tap the power button to wake it up and it does not, I then have to press and hold the power button for 15 to 20 seconds, instead of the normal 4 to 5 seconds to get it to turn on. I don't like the fact of this happening, so now I use the "Home" button to wake up the TP. If I don't get any response, then obviously it's turned off and I can press the power button for the normal 4 to 5 seconds to turn it on.

My thinking is that the "tap" of the power button sends a momentary spike of voltage to those circuits that control the turning on of the TP and they don't like it. Who knows, this may even be part of the cause of the "bricking" syndrome that has been plaguing so many people. Long and the short of it, I'm not taking any chances at having an event that requires running the "Debricking" process or any other battery anomaly that others have been reporting. You might want to make this a habit yourself."

NT
[TouchPad Development] bundys:
I agree with you, I think it's a good practice to get into. I did the same on my Nexus One (famous for power button issues).

However, that still doesn't explain why the home button seems to work differently for different people on the TP.
[TouchPad Development] adzidek:
holy ****balls and crackerjacks, I think you just solved a problem for me that I've been having for a VERY long time. I always just assumed it was a SOD issue. THANKS!!!!!!!!!

PS: I'm going to start not using the power button to lock the screen too. I'll just let it time out.
[TouchPad Development] Moody66:
After a week or ao lollipop really does settle down and run much more smoothly. Battery life also improved.
[TouchPad Development] nevertells2:
I agree, don't understand why power works one way and home another. However, if you only use the home button, you'll never notice. :p

Yeah, just set your screen off time to 30 seconds and you won't waste a lot of battery waiting for the screen to turn off.

FYI to both of you, it's a good practice to flash the A6 firmware every now and then. I usually do so every couple of months. If you have the TouchPad Toolbox script in your /boot volume(partition) like was discussed previously, it will be easy as pie to flash the A6 whenever you want.

NT
[TouchPad Development] sstar:
Unfortunately if you are using Flintman's recommended recovery there is not enough space in the boot folder for the Touchpad Toolbox.
[TouchPad Development] flintman:
New build up. Fixed an art hack i had in place seems to speed up a little bit. Also been playing on netflix and seems pretty good. Once and a while the screen is scambled and a pause and restart seem to fix it. It's not 100% but getting close.
[TouchPad Development] Trainer_H:
Wow flintman, you are awesome !!!!
[TouchPad Development] sstar:
Can I flash this over the last build or does it need to be a fresh install?

TThanks
[TouchPad Development] flintman:
Unless i note it i usually dirty flash. If you run into issues as i can't be sure all apps will take a dirty flash you will have to do a clean install or if you notice high battery usage after a dirty flash. ALWAYS BACKUP.....
[TouchPad Development] adzidek:
I searched but can't find where there was a discussion to get tptoolbox into /boot? Can you point me in the right direction?
[TouchPad Development] sstar:
If you are using flintman's recommended recovery from the OP there's not enough space in the boot folder.

You can check how much space is available by opening the terminal emulator app and typing df

The size of version 40 is 12.17mb and 12.25mb for version 41.

If you do have enough space unzip the touchpad toolbox zip and rename the.bin file to begin uImage.toolbox or any other name you fancy (the second letter is an upper case i) then copy and paste it to your boot folder.
[TouchPad Development] flintman:
You should be able to use any kitkat recovery. I know some people had an issue with restoring and failing at /boot parition. If that's the case try a different recovery. There is one or two recoveries out there that have this issue. I have on my list to make a newer recovery and i will work to shrink it down.
[TouchPad Development] Moody66:
I never dirty flash. But i did this one. Last build was really good after a few days settling. Thus the dirty flash. All good so far. Thanks!
[TouchPad Development] bundys:
Figured out why my home button was behaving differently from others. Turns out I unknowingly had an Apex launcher setting enabled for the home button. All is well now.
[TouchPad Development] jerryatherton:
Just wanted to report that Netflix and Chromecast work great on this build. I never really tried it on any previous builds.

Great job so far.

Sent from my HP Touchpad running Evervolv Lollipop 5.0
[TouchPad Development] flintman:
sometimes on the start of a movie it will be scammbled but will clean up in a minute. I have been watching movies all day. It happens once and a while
[TouchPad Development] ChanceStad:
Which Netflix version are you using? Newest now?
[TouchPad Development] jerryatherton:
Latest play store update. Without chromecast it starts scrambled for a minute then straightens out. Chromecast starts perfect.
[TouchPad Development] jsgraphicart:
Chromecast has made playback on the device not a huge deal for me. It's a life saver. :)

I wish I can cast the screen to it though. That would be awesome. I tried, since their last update made it possible for any device to cast. But it didn't work.