yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] EricBlade:
Hey Flintman,

On my device, whenever I do anything that would trigger the mic, the audio goes dead. I'm guessing the audio server is probably crashing, but I'm not real familiar with what's going on in here. Any suggestions for how I can take a look?

dammit. I hate it when the device makes me a liar. Sound worked. I triggered mic, mic didn't work, sound stopped working. I rebooted, triggered mic, mic didn't work, sound stopped working. I rebooted again, triggered the mic, and now it's working. WTF. (but after playing back the response to my voice command, it did come up "Pico TTS has stopped")

... so, I guess, any suggestions for finding out what went wrong, post-mortem, after I notice that the sound has stopped working?
[TouchPad Development] flintman:
Mic was always a little touchy i was going to look at reworking it. I have hammered the mic before it and works fine everytime and then use it here and there it usually works fine but once and a while if everything is lined up right it stops. I just need to figure when all lines up. 8)
[TouchPad Development] Trainer_H:
i can't find my bluetooth logitech mini boom box.
[TouchPad Development] heavyt:
Wiping Dalvik cache

Do we need to wipe Dalvik cache, we don't use that runtime do we?

Nice work [MENTION=3716175]flintman[/MENTION], thanks.
[TouchPad Development] venkythegeek:
Thanks a lot flintman. Getting closer to getting hangouts working on lollipop !
[TouchPad Development] EricBlade:
All my Bluetooth devices can find it now, but it can't find or connect to any of them :-S
[TouchPad Development] flintman:
Yes the cache is still used
[TouchPad Development] flintman:
Can u get logs? Thanks
[TouchPad Development] EricBlade:
Sure - any particular operations you'd like me to perform? And just a logcat, or anything inparticular?
[TouchPad Development] flintman:
just after you try and connect to BT device either way being seen on either end. will need logcat and dmesg. You can use the tool inside the toolbox undersettings.

Thanks
[TouchPad Development] suzib6sw:
[MENTION=3716175]flintman[/MENTION].. Same Here with Bluetooth..

Logs at past.evervolv.com/view/fa504c90

Hope that helps..

Pete.

Edit

Galaxy S3 sees the TP but fails to pair with "Incorrect Pin or Password".. TP doesnt see any BT devices (3 are close to me)..

This appears to be happening on Milaq's 3.0 Kernel as well on my 2nd TP
[TouchPad Development] flintman:
Yes there is always work on the TP Bluetooth its never been 100%. But the more logs i get give me more info to hopefully get more stuff going.

Thanks for the logs
[TouchPad Development] tvsian:
I've noticed my Touchpad is sometimes rebooting. I've been keeping it at work on a charger, and every once in a while I'll look over and see that it's booting up. I uploaded a log in case there's anything useful in it - http://paste.evervolv.com/view/1f03d781
[TouchPad Development] zero_divide:
Black screen and reboot on 2015.02.04 build (nightly)

Hi,

I tried to do a clean install with the 2015.02.04 build, but I get a black screen at start and endless reboot.
[TouchPad Development] flintman:
Hmm. There was really nothing changed other then some prep stuff for the camera but wasn't activated yet
[TouchPad Development] flintman:
Hmm. Does it only do it on the charger ? Also what version are you running.
[TouchPad Development] tvsian:
I haven't watched it closely off charger, but I'll take a look. It's so intermittent (3 or so times over a 9 hour shift) that hopefully I can catch it if it does.

Currently on the 2/3 nightly, I saw it on the previous one as well. I did do a wipe before installing the 2/2 version.
[TouchPad Development] jerryatherton:
Confirm 2/04 build bootloops.
[TouchPad Development] flintman:
Kk thanks unsure why will look at it when i get home.
[TouchPad Development] EricBlade:
On the Bluetooth side, in earlier builds of this ROM I was able to at least attempt to connect to things. Now it doesn't see anything at all.

Any possibility of bumping the minimum brightness level down any more? It seems like its much much brighter than I'm used to even at minimum. First time I'm using it out of the house and I'm in a medium light level bar, and its quite bright.
[TouchPad Development] flintman:
Under setting /display select adaptive brightness
[TouchPad Development] EricBlade:
OK that got it a little lower, but I feel like its still brighter than the default lowest setting was in other versions.. I'll have to compare my 4.1 touchpad... Also, in low light with adaptive on shouldn't it get dimmer rather than brighter? Maybe the algo just needs tweaking or something.. But on my nexus 5 zero with adaptive on is usually not any brighter noticeably than zero with adaptive off unless I'm in sunlight.

I wonder if the algorithm vastly differs from the one used in iOS and Webos...
[TouchPad Development] flintman:
You show be able to turn it down more. It can go lower its dark. I cant turn down any more without blanking the screen. The light sensor doesn't work right. Have a few more tweaks.
[TouchPad Development] EricBlade:
Hmm. In Webos I've had it as dim as it is when its almost ready to go blank.. Oh well not a huge deal :) I bet that the Als is reading backwards from expected input, but ill poke it with this test app and see. I'd say the Bluetooth and mic are far more important for me than correct light sensor.
[TouchPad Development] flintman:
put the fix in for the nightlies will be fixed in tomoorows nightly. Missed a tag from the camera in kitkat. removed for now. Im very close with the camera but i don't want to release as its causing some issues. The camera works but the camcorder is messed up causing some issues. i have been limited on time this week but its getting close to the weekend 8) let me know if you have issues on tommorrow nightly.

Thanks
[TouchPad Development] eKeith:
In preparation, which camera app are you using/ recommending? Thanks
[TouchPad Development] eKeith:
FYI:

- Wiped Cache & Dalvik then dirty-flashed latest nightly (2/4/2015) via the on-board CM Update (very nice BTW) but resulted in a boot loop.

- Re-downloaded via PC (just in case previously corrupted), transferred to TouchPad (Used TPToolbox to mount), wiped Cache & Dalvik, and re-dirty-flashed - same result, boot loop

- Downloaded my previous build (1/29/2015).... yada yada yada... dirty-flashed - "Android is upgrading...", Seems All is Well!
[TouchPad Development] BloodBaron:
http://xdaforums.com/showpost.php?p=58641811&postcount=622

Seems that one nightly was problematic
[TouchPad Development] flintman:
Todays should be fixed. Pushed the change last night.
[TouchPad Development] Kontagious:
is there a specific way to push this to the TP through the toolbox or the same as KK roms?
[TouchPad Development] flintman:
You can download via updater. Or just connect via mtp and drag it over.
[TouchPad Development] zero_divide:
Build 2015.02.05 boots normally

Hi,

Build 2015.02.05 boots normally
[TouchPad Development] suzib6sw:
Seems to be behaving itself today.. No BT still but noticed Steve Kondik did some work on the A2DP on the 3rd..

http://review.cyanogenmod.org/#/c/87818/

Cheers.
[TouchPad Development] nevertells2:
What do you mean, "same as KK Roms"? Flash via recovery? That should work fine.

NT
[TouchPad Development] gaww:
Ditto - plus the one click update flashed worked good now.

Would be great it it also reset the binary for SuperSU, re-enabled AdAway, and reset apps needing SuperSU root. What do you mean this is asking too much - I am getting lazy in my old age.
[TouchPad Development] bekham76:
I tried to install evervolv through toolbox but it keeps failing due to recovery zip file. I downloaded the twrp 2.8.3 and it says recovery file not found. Any ideas, thanks.
[TouchPad Development] flintman:
I know 2.8.3 works. Never tested 2.8.4. Redownload 2.8.3 and push it to TP when u get to that point. Also after download open the zip to ensure its not corrupt. If it open you'll know it can read it. Should work.
[TouchPad Development] bekham76:
thank you, so I should put the zip as it is without naming it? because this is what I did and its not working..
[TouchPad Development] bekham76:
It is still not working
[TouchPad Development] flintman:
What version toolbox u using. If it's the right version no need to rename
[TouchPad Development] bekham76:
v40
[TouchPad Development] flintman:
use version 42 https://goo.im/devs/jcsullins/cmtouchpad/tptoolbox/
[TouchPad Development] bekham76:
THANKS, it worked :)
[TouchPad Development] jerryatherton:
Just wanted to let you know that i have installed the 2/05 build on two machines and they are running great. Thanks for being so responsive wit a fix. Great ROM typical of your work!
[TouchPad Development] Kontagious:
nvm fixed it

toolbox v4.2 has issues with TWRP 2.8.4.0

switched and tried TWRP 2.8.3.0 and its doing its initial boot as i am typing
[TouchPad Development] jerryatherton:
Cant get Gmail to run. It does install. Logcat:

http://paste.evervolv.com/view/3651a1b8
[TouchPad Development] zero_divide:
2.8.4.0 TWRP

Hi,

Installed with tptoolbox v40, the version 2.8.4.0 of TWRP recovery works well.
[TouchPad Development] flintman:
One of two things should work. Try to clear the data on gmail under settings/apps, if that doesn't work try a reinstall of gapps. Its missing a file, it looks like, or can't access a file.
[TouchPad Development] flintman:
Ok camera test build is up.

Will have to do a clean install to get the icon and the camera to work properly. I also recommend a format of system before installing. You will have to install the test build and gapps when doing this. Also i had a little issue with my DCIM folder having a corrupt file causing a force close of the camera. Probably related to working on getting the camera going but to fix delete your DCIM folder. It will create a new one. DCIM is where all your pictures are saved so if you have any in there backup.

Other then that, the camera works and camcorder works fine other then the blue/green tint when recordering(same as kitkat was). Once you do a clean install with this once the camera stuff is released in the nightlies you will not have to do a clean install as you already have the camera icon.

Let me know if anyone has any issues as if no issues ill add to tomorrows nightly.

Thanks
[TouchPad Development] alias4ever:
This may be a dumb question to some. I've installed this but every time I reboot my TouchPad the default boot is recovery. How would I go about changing it to have this be the default boot? I don't mind changing it every boot but it would be nice when there are times I forget. :) Thank you Flint for an awesome ROM as always, I LOVE my TouchPad as does my son! :D

Oh and I do not have WebOS as I have completely removed it using TP Toolbox. ;)
[TouchPad Development] flintman:
There is a file in /boot called moboot.default If you install evervolv this will get updated unsure why its not for you. If you look at this file you should see "Evervolv" and thats it. If not you can just change it with Es file manager and R/W access to boot. make sure you don't delete anything or change anything else in /boot. Can you supply a recovery.log after your next install. Will tell me what is going on
[TouchPad Development] psychephylax:
I flashed the 2/5 nightly. The updater told me it was available, which is awesome. Updater worked as well, but i managed to crash one if the internal processes that is UI related by installing and playing Star Wars Commander.
[TouchPad Development] flintman:
Did you clear all cache? when updating
[TouchPad Development] psychephylax:
I believe so, but I don't remember. Since the camera ROM requires a full wipe I'll see if it happens again and let you know.
[TouchPad Development] flintman:
All, tomorrows nightly will have the camera fixs in it. If you are on 2-6-15 test build you will not need to update to tomorrows nightly as its the same build. Nightlies after that will have updates that will NOT require a clean install unless i note it.
[TouchPad Development] EricBlade:
http://paste.evervolv.com/view/1b5cc6cf

Log from a couple of attempts to connect Bluetooth. It did not even see my nexus, but the nexus tried to pair with itand said it failed due to not entering pin.
[TouchPad Development] flintman:
Thanks working bluetooth now.
[TouchPad Development] BlueKnightedDragon:
Tried to install the newest testing build and when it starts up I see "Unfortunately, Android Keyboard (AOSP) has stopped." and am not able to use the keyboard
[TouchPad Development] flintman:
did you do a clean install (to ensure format system) and will need to reinstall gapps. what version gapps you have?
[TouchPad Development] BlueKnightedDragon:
Did fully clean with toolbox but originally tried pagapps but it that so i used the basketbuild and tried to reinstall through toolboxand it still did that and now i formatted everything in recovery and did clean install of rom and basketbuild gapps and no keyboard crash this time
[TouchPad Development] flintman:
I know pagapps has an issue with the keyboard forget what version in which it started.
[TouchPad Development] venkythegeek:
Camera works and hangouts work ..awesome flintman. I was trying ip camera but the app closes after hanging for a while.

The ip camera appa really messes with OS and forces a reboot.. Also is there a way for notification music to be stopped. It keeps playing the music for every message and never stops :(
[TouchPad Development] bundys:
I found the keyboard issue also happen if there isn't enough free space left in the /boot partition from having too many ulimage files.
[TouchPad Development] flintman:
Never had that issue. What are you using for music ? Im wondering if its a specific tone.

Thanks
[TouchPad Development] ergo911:
Hi, rom works great so far ? Only thing what I see is that the icons aren't crisp, I also tried different lcd density's like 155 and 132 but still the same.
[TouchPad Development] venkythegeek:
it has a long musical note when you have a calendar reminder or an appointment. I have google now activated.

Sorry maybe it was not clear ..it is the notification music.

Also ran IP webcam for a few hours now the touchpad is out of memory and super slow and rebooted
[TouchPad Development] zerofx_gth:
i m flashed

hello,

first i gave a thanks to flintman. you are a great dev. thanks for your hard work. i come from a testbuild in dec.14. Now i m on the new testbuild from 15.02.06. i m flashed. its so fast (incredibly smooth) and finally cam works! little problems with bt. i try to fix it:p
[TouchPad Development] sesz:
Just wanted to say thanks. This rom has brought new life to my touchpad.
[TouchPad Development] flintman:
Are you running a different theme. As i wonder if ifs theme related.
[TouchPad Development] nevertells2:
What launcher are you using? Try a different one. I personally like Nova and ADW.

NT
[TouchPad Development] ergo911:
Hi, I'm using stock launcer, but with 6.02 test build it's fine.

Thanks guys, you all are heros, for keeping our old touchpad still alive ?
[TouchPad Development] rickpub:
Hi Flintman... I mentioned to you in the past about not being to clock beyond 1512. I never sent you a logcat as i figured you had more pressing things to deal with... Anyway, i just upgraded to the 2/6 build with a clean install. Still nothing above 1512 on clock speed. Here is the link to the logcat i generated if you get a chance to look at it. I am running on a 64gb version of touchpad. Thanks!

http://paste.evervolv.com/view/bedaa9b4

---------- Post added at 05:51 PM ---------- Previous post was at 05:50 PM ----------

BTW. 2/6 running great! Thanks.
[TouchPad Development] rickpub:
Also, just went through the identical process upgrading my daughters 32gb touchpad and the clocking choices above 1512 are there and working! I believe i set hers at 1782...
[TouchPad Development] EricBlade:
Clock choices above 1512 were not available last I looked on my 4G... I'm not near it right now, so I can't verify on the most recent build.. but I will next time I'm at it, if needed.
[TouchPad Development] ergo911:
+1 on 32gb version. Works up to 1782mhz.
[TouchPad Development] flintman:
4g isn't 100%. I need to replace the battery in my 4g model just havent had the time. I needed a break from the RIL that was giving me issues. Hopefully i can get the new tools to remove the screen before this weekend so i can replace the battery.
[TouchPad Development] EricBlade:
It's working beautifully for me, except when the sound goes dead.. and the bluetooth.. :) You've done brilliant work on this.
[TouchPad Development] flintman:
Ok i see the problem. DOES ANYONE ELSE HAVE THIS ISSUE?? rickpub please give me a full description of your device. Have you ever did a full clean on it(meaning JCSullins toolbox). How did you install? Are you running any apps that change CPU in anyway? If you never used JCSullins toolbox and don't care if you have webos. I recommend a full wipe of the device and let me know after. if you have done that before and still have an issue. I will have to figure our why your TP is selecting the slow 1512 settings in the kernel. I could always just force it in the kernel but would rather know what its doing it.

Thanks
[TouchPad Development] flintman:
JUST AN FYI todays nightly has a bunch of bluetooth updates. Unsure what it will fix for anyone but it fixed a few minor issues with my devices i have.
[TouchPad Development] rickpub:
This is the 64gb white touchpad. Toolbox was run long ago and device fully wiped, webos long gone, system partition over 800mb. I do have some apps like setcpu, but before I even flash gapps or restore my backups the settings are not there(i.e. settings not available upon first boot of ROM on fresh install). If you think i should do another full wipe via toolbox I will, if you think it may make a difference.
[TouchPad Development] flintman:
Im unsure if it will make a difference but i can rule out an outside file changing it. If you have the time and don't mind doing it give it a shot. ANYONE ELSE have a 64GB TP?? Would like to know if you have the same issue?? Wondering if its a 64GB TP issue.

Thanks
[TouchPad Development] flintman:
Just realized the nightlies are erroring out. Looking into now. Builds fine on my PC just won't build on the nightly box.
[TouchPad Development] rickpub:
Ok, flattened my tp completely using toolbox then installed fresh. Still same issue. Must have something to do with it being a 64gb tp. Here is the logcat of my install (no gaps installed yet, just fresh rom install)...

Http://paste.evervolv.com/view/2dbcbdf7
[TouchPad Development] flintman:
Any 64gb TP user can confirm this???
[TouchPad Development] rickpub:
Hi Flintman,

For what it may be worth, I backed up my daughters 32gb TP in TWRP and restored her image to my 64gb TP to see if the option to clock above 1512 (which is available on her TP) would then show up as available on mine. Didn't work, even with her image, my 64gb touchpad maxes out at 1512. Worth a try I figured. Not sure if it means anything to you. Also, found this... http://www.webosnation.com/review-white-touchpad which talks about the 64gb TP having a processor capable of operating at 25% higher than the 32gb or 16gb versions. I do remember very early on being able to clock my TP above 2100 and it being very stable. Hope some of this information helps you. Would love to be able to clock higher than 1782 on this again if possible. Thanks for all your work. -Rick

---------- Post added at 04:05 PM ---------- Previous post was at 03:11 PM ----------

Ok i see same processor just binned... and rated at 1.5
[TouchPad Development] nevertells2:
Based on what I have read over the years on the TouchPad, the 16, 32 and 64gb TouchPads have the same Snapdragon APQ8060 processor which is factory rated at 1.5ghz. Just why HP decided to under-clock the 16 and 32gb version is anyone's guess. Some speculated that HP figured they would have less problems with the two models if the processor was under-clocked. Back in the CM7/9 days, I only remember one developer using a kernel that allowed over-clocking at 2.1ghz. And from what I remember, it ran great.

NT
[TouchPad Development] rickpub:
Ah yes, someone remembers!!! I think it msy have been in the cm7 days... and it worked quite well. Cant temember who it was...
[TouchPad Development] sweetboy02125:
Is there an option to set turn on the Touchpad using the middle button in stead of the power button? My middle button didn't work
[TouchPad Development] flintman:
It's in the toolbox
[TouchPad Development] flintman:
Need to do some research on this. Ill keep u updated.
[TouchPad Development] sweetboy02125:
which toolbox? i only see Dev tool and setting apps.
[TouchPad Development] flintman:
Settings/toolbox its under the evervolv section of the settings menu
[TouchPad Development] jcsullins:
The 16GB and 32GB Wifi Touchpads have SOCs rated at 1.2 Ghz.

Here's the full explanation I gave on this subject last time:

http://xdaforums.com/showpost.php?p=51244777&postcount=1217

So WRT overclocking the TP 4Gs and TP 64GBs: since they actually use SOCs rated at 1.5Ghz, they use a different frequency table than the others (that are rated at 1.2Ghz). So to get overclocking on those, you would either need to make changes to the frequency table used for 1.5Ghz SOCs similar to those made for the frequency table used for 1.2Ghz SOCs or make changes so that the frequency table used for the 1.2Ghz SOCs is used when a 1.5Ghz SOC is detected.
[TouchPad Development] flintman:
Thanks i know the 4g was didn't know about the 64gb machine. Once i get my 4g fixed ill fix that up.
[TouchPad Development] shumash:
http://xdaforums.com/showthread.php?t=1454963

http://xdaforums.com/showthread.php?t=1230912
[TouchPad Development] babcocca:
Looking forward to loading the Bluetooth fixes build. So awesome.
[TouchPad Development] flintman:
More of a bunch of updates hoping to fix a few issues. If i cant get the nightlies going ill post a build from my server tomorrow.
[TouchPad Development] nevertells2:
Android 5.1

Hopefully this will help when it's available:

General improvements in system stability

Improved RAM management

Fixes for sudden app closures

Improved battery management

Excessive consumption of network devices when used Wi-Fi fixed

Issues with wireless connections fixed

Problems with Okay Google function solved

Notifications problems solved

Some sound problems experience by certain devices fixed

Other improvements and changes

Changes in the Material Design color palette (after users complaints, possibly for a higher version though)

NT
[TouchPad Development] flintman:
Ya i saw that. Unsure when it will get released.
[TouchPad Development] pyroman512:
keep getting a shutdown during sleep I presume. Seems like after a day or two it just jumps from whatever battery percentage its at to 0.

Here are some logs

http://paste.evervolv.com/view/2dc7fef8

I'm on 0206 dirty flashed from 0205 but this problem existed for me in both builds

1 GB system partition
[TouchPad Development] EricBlade:
4g has that issue -- 192 to 1512 are the ranges. Highest I've seen one of the 6 touchpads in my FAM hit was 1.8 but the other 5 would freeze that high. They all run great at 1.7 though. And hell I'd totally forgotten they came stock at 1.2.. At least partially for battery and heat reasons.

Center button does not wake once the screen shuts off on any android version I've tried > 4.1, regardless of setting.

Can't wait to try the next :)
[TouchPad Development] flintman:
Try a clean install
[TouchPad Development] psychephylax:
Is the camera is supposed to be fixed in the 2/6 build? I tried hangouts, paper camera and stock camera and it doesn't communicate with the camera. I did a wipe of system and all caches before installing the build.