yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] jerryatherton:
There is a fix for this: http://xdaforums.com/showthread.php?p=58093962
[TouchPad Development] De4dSpace:
These builds are awesome. Thanks! Anybody else getting some alpha transparency glitches? In Nova Launchers settings under desktop persistent search bar, the Kit Kat option always has lines strobing through it. I have also seen similar lines in the Play Store on occasion. Also, sometimes sound will intermittently come out tinny or muffeled.

This old Touchpad was gathering dust. I had purchased a Nexus 9 on launch day, only to find the volume up button so recessed I couldn't justify its $500 price tag. I held onto the 9 through the holiday season, only to return it to Best Buy after the first of the year. I came to XDA to find this wonderfull community still working hard. It feels so good to know this tenderloin only cost me $99 and is still being pushed forward!
[TouchPad Development] geearf:
Hello,

I moved to this build from Milaq's CM11 a few days ago, it still doesn't feel at home as the UI changed quite a bit, but one thing, it seems my battery drainage is gone!

Which is great!

Of course I'll need to use it for a couple weeks to be sure, but so far I'm happy.

Thanks!
[TouchPad Development] meigallo:
Same behavior here.
[TouchPad Development] bundys:
Anyone else notice the People app always forces landscape?
[TouchPad Development] brchickery:
Looks like a new build is up for the 22nd.
[TouchPad Development] fatboyslimerr:
Getting system UI FC constantly on first boot of 01/23 build! Anyone else?
[TouchPad Development] venkythegeek:
How do I get the mic dictation on my keyboard. The Google speech typling option is not available .

If and when the camera is enabled will it support the new lollipop api with raw and manual controls?

Thanks for awesome work
[TouchPad Development] yohaskan:
Same thing here.

- I'll try second flash and wipe dalvik cache :eek:
[TouchPad Development] puhleez:
Yes, same happened to me. Went back one build.
[TouchPad Development] jaltman:
Me too.
[TouchPad Development] cybershawngates:
yeah same here "unfortunately system UI has stopped" - clean install. wipe dalvik/cache did nothing. Don't use the 0123 build, going back to 0122 (solved problem)

But what a great build otherwise!! A 4 year old TP still running the latest version of android (compare that to the note 8 and s5 samsung devices yet to be updated). Youtube works great no stutter. Amazing job!! [MENTION=2385005]invisiblek[/MENTION] and others! Netflix also seems to work
[TouchPad Development] Mchasard:
Please what's the difference between your build comparing to milaq's build?
[TouchPad Development] ranjib:
I assume, there will never be a camera with kernel 3.4? Is there any driver for it with kernel 3.4?
[TouchPad Development] cybershawngates:
my guess as a relative noob is that this is based on the 3.4 kernel. Netflix works very well - streaming now for 2 hrs!
[TouchPad Development] drmarble:
The camera works in cm-11.0 with the 3.4 kernel. It just doesn't work yet in cm-12.0. I think it is such a lousy camera that fixing it isn't a major priority. Any interested user is welcome to work on it. All the source code is freely available on Github.
[TouchPad Development] nevertells2:
Ain't no more Dalvik on these builds. It's all ART now.

NT
[TouchPad Development] venkythegeek:
Lousy but great as an IP webcam ?, maybe dogarry will get it working one last time ?
[TouchPad Development] yohaskan:
Ok, it's ART new runtime but what we do when we roll back, or flash a rom with It ?

no cache to flush ?

No ART cache to wipe ?

Invisiblek recommend flintman's TWRP. there are always an option for cleaning this and it's called "Dalvik cache",

is it fonctionnal ?

Else, what we have to do to make a clean flash or install ?
[TouchPad Development] jaltman:
No, you dont need a clean flash each time, and you should format the dalvik cache.

Now I may may not be precise as to the details, but dalvik was more in the nature of an interpreter and ART is more in the nature of a compiler. Thats why first boot is slower, all the programs have to be compiled. Since that is so, the compiled program has to be put somewhere and its put in the dalvik cache. So that which goes in there is now different, but stuff still goes there.

O.K. experts, correct me and improve my understanding too.
[TouchPad Development] nevertells2:
Format /system.

Maybe there are some of Dalvik left, but so far, no one has explained if it does and what

wiping Dalvik cache does, if anything. I found this in a Google search,

"With Lollipop, Dalvik is dead. It's been replaced with a completely new runtime called

"ART," the "Android RunTime." ART debuted in KitKat as an experimental option, but

now in Lollipop it's the only option."

I found no mention of Dalvik in the entire article. So if someone in the know wants to

explain what Clearing Dalvik cache in TWRP and CWM does, we can all learn something.

If it does in fact clear the ART cache, then upon reboot, it should take a very long time to

recompile the apps. ART uses AOT(ahead of time) compilation and Dalvik used JIT(just in time)

That is why Android 5 takes to long to start up the first time.

If you want to read the article, it's here: http://arstechnica.com/gadgets/2014/11/android-5-0-lollipop-thoroughly-reviewed/3/

Scroll down to read about ART.

NT
[TouchPad Development] De4dSpace:
I had posted earlier about a suspected alpha layer transparency glitch. I now think is is a problem with drawing a certain value of grey. Here is a link to a picture from a thread I was reading. Do strobing lines show up for anybody else on the grey areas of the battery back cover on the right side of the image?

http://xdaforums.com/attachment.php?attachmentid=2945004&d=1411299407
[TouchPad Development] mschumacher69:
I think I know what u're talking about. I had this issue on [MENTION=2385005]invisiblek[/MENTION]'s CM11 builds, I used to get what u're describing on grey colors such as the google keyboard. This was the reason I switched over to [MENTION=1594835]milaq[/MENTION]'s builds actually.
[TouchPad Development] Torqd505:
Yes I also have those strobing lines on certain grey areas. I just thought the TP was getting old and tired!
[TouchPad Development] brchickery:
The last 4-5 days of this rom has made my touchpad almost unusable. I'm going to have to retry an older version or format and start fresh. Freezing and tons of BSOD's
[TouchPad Development] chris5s:
Which version are you running just now?

Have you noticed any pattern to this behaviour? Try and get a logcat if you can, will help debugging!

Cheers
[TouchPad Development] brchickery:
Good looks. I just formatted system. Going to flash the latest from 27th and see how she goes.
[TouchPad Development] geearf:
I had a build from a week or two that worked, tried newer ones but they all failed :/

With builds from 26 to 28, the touchpad starts, but then it stays on for maybe 2 seconds, till it goes to sleep. I can awake it up by pressing power, but then in 2 seconds it's back in sleep... and in those 2 seconds I am unable to unlock it :/

The texts also seem to be in another language...

With builds prior to that, even the one that used to work for me, the touchpad is stuck booting forever (I had it booting for more than 12 hours to make sure it was not just slow).

I am guessing something changed in between the builds that won't allow me to rollback.

wiping dalvik, cache and system does not help.

I have not tried a full wipe yet, but I'm afraid I'll have to.

and the full wipe did it.

I did not know how much TWRP was till I did that, it's a full wipe but I get to keep my data folder, that's cool!
[TouchPad Development] airtower:
I'm noticing that on these builds, that swtiching between apps (or even chrome tabs, even though chrome doesn't push the tabs to individual "apps" in the recent apps list on this device) causes the app or page to reload from scratch. Seems this may be due to lack of ram and the OS killing background apps, but I'm not sure. Some apps come back ok, others (autotrader, mokriya craigslist among others) have problems. Anyone else seeing this? Anything to be done about it? I tried to play with the background process limit, but to no effect.
[TouchPad Development] brchickery:
I was having similar issues. The touchpad was completely locked on launch. The launcher3 would freeze bsod or crash constantly. I just installed yesterdays the build from the 28th and my touchpad is back to normal.

So if you were having issues try the 28th on and you should be ok.
[TouchPad Development] geearf:
I originally went back to my first build after a full wipe and it worked.

Yesterday I tried yesterday's build, and it worked as well...

I had tried the 28th before, but not on a full wipe and it didn't work.

Maybe one of the builds I installed before (26th?) messed it up for good and it needed a full wipe?

Thanks!
[TouchPad Development] brchickery:
No problem man. I would just grab the newest file in the original post. build is from the 29th.

http://www.invisiblek.org/roms/cm-12.0/tenderloin/cm-12-20150129-UNOFFICIAL-tenderloin.zip
[TouchPad Development] desitexan:
Do any of the post 22nd builds work without major issues? I tried the 26th one few days ago and that wasn't working properly.
[TouchPad Development] geearf:
I moved the 31st and it boots ok, it flickers on the lock though.

I also have issues with audio, when I played a file, both in appolo or VLC, it freezes on a one-color screen.

I'm not sure what that is yet...
[TouchPad Development] brchickery:
I was able to remove all flickering by going into dev settings and enabling the gpu rendereing and anything that said gpu or video . I'll check my actual settings when I get back to my TP I'm not near it right now. Running like a TOP on the latest version from yesterday.
[TouchPad Development] mschumacher69:
I wonder why those settings are not enabled by default... [MENTION=2385005]invisiblek[/MENTION] any thoughts?
[TouchPad Development] brchickery:
For absolutely no reason my touchpad is back to freezing and crashing again on yesterdays build. Giong to install todays.
[TouchPad Development] desitexan:
Today's the same. Freezes and crashes out of blue.
[TouchPad Development] jaltman:
I think there is something up in the cache. The 24th was a really good build, these later ones, when they crash, go into twrp, wipe the cache and the dalvik cache and then they seem ok for a while. I think something is corrupting one of the caches.
[TouchPad Development] desitexan:
^^ I noticed that as well with yesterday's build.
[TouchPad Development] vinukondamahesh:
Touchpad is getting crashed always, saying that launcher3 not responding with new Rom
[TouchPad Development] ken52787:
I did a fresh install of todays build and am having some trouble. Part way through the setup (it had just connected to wifi and asked me for my cyanogenmod credentials), it stopped responding and froze up. After a few minutes the screen went to black, but the backlight stayed on. It's now at the point where the backlight will come on if I press power, and then fade off after a few minutes. Whats odd is that I hear it ding periodically, so I know it's doing something.

Does anyone know how to reboot the device so I can reflash to an older build? It's not responding to any reset button combinations (power + vol down + home, etc). I tried plugging it into my computer and using adb to restart it, but the device isn't authorized and I obviously can't allow it on the touchpad. Am I stuck just letting the battery drain?

EDIT: Too late, there goes the battery :D
[TouchPad Development] geearf:
I ended up going back to the 22nd build, the other builds I tried were too unstable.

I felt that the later builds became unstable after installing the gapps, but that may not be the real issue. I tried newer gapps but it didn't seem to help.
[TouchPad Development] jerryatherton:
Leave it plugged in for a few days. I have had that happen and it came back. It seems like any build here after 1/22 has troubles. The dev probably needs some logcats but i couldn't get the thing to run long enough to set up for one.

After your battery comes back i would use Toolbox to rebuild your system.
[TouchPad Development] jaltman:
You can force a reboot by holding the home button and the power button both down for about 10 seconds, until it restarts.
[TouchPad Development] invisiblek:
Sorry everyone, been busy on some other things and didn't realize I'd been building broke-ass tenderloin builds for everyone. =P

Tomorrow's build should fix the boot issues.
[TouchPad Development] geearf:
That's great, thank you for your supporting us!
[TouchPad Development] desitexan:
Today's build seems to still have the same issues as the post 22 builds. Any one else tried the latest build?
[TouchPad Development] invisiblek:
Odd...these builds are running great on mine =/
[TouchPad Development] vinukondamahesh:
Good ,but sometimes it stuck for sometimes.
[TouchPad Development] iamsamsamiam:
It runs alright on first boot. After installing some apps the device feels sluggish.

Rebooting the Touchpad breaks everything. The boot animation gets to a certain point and becomes really slow. Maybe an hour long boot time if not more. If it even gets in, the device is largely unusable as everything crashes.

Clearing dalvik and cache makes the device workable again for that session.

This is with the last dozen or so builds up to 20150207. Waiting on a solution.
[TouchPad Development] razorloves:
same experience here.

first boot is usable.

if you do a soft reboot, it works ok, like the first boot.

but if you do a normal reboot, or power off and on, it just slows to a crawl on the bootanimation and freezes up.

if you go into recovery and just wipe dalvik cache, it works again on first boot.

if you need logs or anything, just let me know. here or on irc.

thanks
[TouchPad Development] invisiblek:
Yea, I guess I had never rebooted after flashing that build. At least I can reproduce it. :silly:

Its related to the new boot animation, it exhausts our RAM and causes breakage. I'm working on it...
[TouchPad Development] stephendt0:
Subscribed, will definitely be trying this ROM on a couple of touchpads once the major bugs are squished :) CM10.2 is getting a bit long in the tooth. Has anyone tried F2FS? Apparently it makes the Nexus 7 2012 far more responsive, wondering if the same could be applied to to the Touchpad.
[TouchPad Development] nevertells2:
Based on this, it looks feasable: http://en.wikipedia.org/wiki/F2FS

I've seen it used on Asus tablets with mixed results. I believe they use a modified TWRP to format the memory.

NT
[TouchPad Development] stephendt0:
I'd be very interested to see what difference it makes. There has been some work on F2FS for the Touchpad already for kit kat and it certainly seems promising.

http://xdaforums.com/showthread.php?t=2606578
[TouchPad Development] invisiblek:
Yea, we have f2fs support in the kernel already. Just need fstab changes to add support (and a busybox commit of mine, which isn't 100% necessary). I'll ship the fstab tonight so tomorrow's build would support it. You'll still need to manually format data and/or cache with f2fs (those are the only two volumes that will be supported).

On another note, got to the bottom of the issues my builds have been having. Look out for the next build (should be 20140210). It should work well again =)
[TouchPad Development] geearf:
What are the benefits of switching to F2FS?

Formatting cache is easy, but data is more annying since that's where I have GBs of data.
[TouchPad Development] stephendt0:
Google "F2FS benefits".

Basically it's a file storage system which has improved I/O performance on flash storage and does not need to be regularly trimmed like EXT4, which should in turn then make our Touchpads a lot snappier.

http://xdaforums.com/showthread.php?t=2697069
[TouchPad Development] razorloves:
thanks man. today's build is workin great
[TouchPad Development] stephendt0:
Awesome, thanks [MENTION=2385005]invisiblek[/MENTION] can't wait to try it out. Should be a breath of fresh air for the Touchpad. Is there any chance you could enable the bug tracking system through DevDB so we can add bug reports on the ROM if needed?
[TouchPad Development] puhleez:
This build working great so far. Haven't tried out every bit of hardware but display, audio, and touch screens all working great. Thanks!
[TouchPad Development] geearf:
Cool!

I guess I'll do that then.
[TouchPad Development] stephendt0:
Let us know how it goes. I'll be doing the same soon.
[TouchPad Development] geearf:
Well I moved to the latest build (so yesterday's) and so far the issues I had post 22nd seem gone so that's good.

I also installed flintman's twrp 2.8.4.0 but I don't see any f2fs in there, only options to convert to ext2/3/4.

Do I need another build of twrp for that?
[TouchPad Development] invisiblek:
He'll have a new twrp up with f2fs support soon. I thought it already did.
[TouchPad Development] babcocca:
Tried this build coming from evervolv. The BT isn't working here either. Any ideas?
[TouchPad Development] geearf:
Alright, thank you!
[TouchPad Development] geearf:
On a different topic I am having issues mounting my cifs share on that build.

I am guessing that is a superuser related issue.

How do I control the list of allowed apps for superuser in this build?

I see nothing in the settings, and Clockwork superuser says the su binary is too old.

I tried root access set to apps or apps and ADB, but no difference.

edit:found the settings in privacy guard.

Thanks!
[TouchPad Development] geearf:
I am still unable to mount cifs with the latest builds, but I used flintman's latest TWRP and converted /cache to f2fs.

I have no clue if that made any difference...

Converting /data is more annoying so I'll do that later.
[TouchPad Development] ranjib:
Sorry for feature request, but didn't jcsullins already resolve camera issues for kernel 3.4? Would it be possible please to build this into your fantastic version of lollipop?
[TouchPad Development] zoomy942:
Hi guys.

First, I've flashed a zillion things in my day but I'm a bit rusty. What do I need to do so I can get past this error?

Love this touchpad and it was running a honeycomb build before.

PZ
[TouchPad Development] geearf:
I don't know, but maybe your partitions are not the right size?

/system increased quite a bit, even over kit kat.
[TouchPad Development] McBeanTIO:
Which TWRP has f2fs support for HPTP?

Which version of TWRP are you using, and do you have a link to it? Thinking about testing f2fs as well, but not sure of the process.

Any guidance is appreciated.

--McBean
[TouchPad Development] geearf:
You can find it there:

http://xdaforums.com/hp-touchpad/development/rom-evervolv-5-0-0p1-data-media-t2949521
[TouchPad Development] McBeanTIO:
Thanks for that. Found it about 5 minutes after I posted. I'm running into an issue when trying to use TWRP to flash in this new version. I'm getting an error:

I'll poke around and see if somethings crops up.

SUCCESS: somehow the check box for "Zip file signature verification?" was filled in. Removed that check box and now I'm off to the races.

--McBean
[TouchPad Development] zoomy942:
Okay. I'm listening. How can I correct that.
[TouchPad Development] geearf:
Alright, I'm on f2fs for /data as well and it is working so far.

Not sure if it's faster or not...

and the 14th build does not boot (or I did not try for long enough?) I see a black screen instead of the boot animation.
[XDA Assist] kingsam208@:
I did root it's successfully done but I deleted google apps like Google account on device and maps and all of Google now am not able to play game it's needed google account how and in my device I can't see google account it's showing just sever how to create google server what app do I need friends plz help me
[Nexus 6 Q&A, Help & Troubleshooting] doakills:
So the nexus 6 has been out for some time now and no engineering screens have come into view yet.. Has anyone got an idea if this was wiped altogether from this device or did they cram it under a special boot (similar to booting LG for diagnostics) to enable such menus?
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
Try #.#.4636.#.# from the dialer. it opens a testing menu for me
[Nexus 6 Q&A, Help & Troubleshooting] cmh714:
that aint working for me...none of the usual USSD codes seem to work. I have a Moto NX6 on VZW
[Nexus 6 Q&A, Help & Troubleshooting] gakio12:
If you want lte band and frequency info, try the app LTE Discovery. It has lots of info on the current signal.
[Nexus 6 Q&A, Help & Troubleshooting] bonebeatz1234:
On stock ROM my phone picks up sprint LTE fine if I try a custom ROM anyone it won't automatically connect and I would have to use the LTE discovery app .
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
Bummer. Mine is a gps n6 and it works. Also on vzw here.
[Nexus 6 Q&A, Help & Troubleshooting] cmh714:
The phone is working great and I can set it to LTE thru the Settings menus, but always like to have access to the USSD codes for goofing around....no real biggie
[Nexus 6 Q&A, Help & Troubleshooting] KB112:
Yeah, it seems it is not on this model at all. I was really bummed myself. I even side loaded the Nexus 5 field test mode app. It works, but has no access to the menus needed to turn on/off selected lte bands.
[Nexus 6 Q&A, Help & Troubleshooting] USA-RedDragon:
I used *#*#4636#*#* to make it work
[Nexus 6 Q&A, Help & Troubleshooting] Larzzzz82:
And of course i actually tried it before i posted... I mess the #* up all the time.
[Nexus 6 Q&A, Help & Troubleshooting] KB112:
Yes the 4636 code works. But the DATA code (3282) does not. This gives you access to the screen with many more service options. Such as allowing you to turn on/off individual LTE bands etc.

http://xdaforums.com/google-nexus-5/general/n5-hidden-field-test-mode-t2524744
[Nexus 6 Q&A, Help & Troubleshooting] doakills:
4636 is a standard AOSP dialer function.

There use to be a debug menu for nothing but LTE / CDMA information? for what ever reason the nexus 6 doesn't offer this anymore vs the nexus 5 still does.. The app also doesn't port over. The only dialer codes that work still are ones related to the SprintDM app that was loaded on it for activation / resetting the device. I loved having the debug menu to see what LTE band I was connected to and control / force my LTE bands to specific ones for site testing (forcing 800mhz and or 2600mhz).

All is well I suppose if we don't ever see light of this.
[G2 Q&A, Help & Troubleshooting] AlphaQ99:
This worked for me when it was booting straight into TWRP. While in TWRP hit Advanced, Terminal Command, Select and enter in the following two commands in the shell to get it to boot:

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota

dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
[Android Q&A, Help & Troubleshooting] :
edit: My mistake - After all my tablet is the ME181CX version, i was almost certain it was the C. Aparently this one can't be rooted yet.

Hello,

I recently bought this tablet, and started reading up on how to root it.

I have come across this rootzenphone apk, and aparently the latest 1.4.6.4r version should support this tablet. Nevertheless, i am having the problem of it just leaving the tablet in demo mode, and the rooting saying "failed". I have restored to factory settings, and tried to root again, to the same results.

Build number : WW-3.1.23.172 -> i recall reading something about only "ww-xxxx" models being supported, so i guess mine is one of those.

I am quite new to android, so i may not be giving some needed info :x

Anyway, any help would be awesome.
[Teclast X98 Air 3G] Gazeebo:
Hello everyone, I am very interested in buying this tablet because of the win 8.1+Android boot BUT I have read mixed reviews that some come ok while others come with problems. I personally don't want to deal with broken youtube, play store and etc.

Is there like a stock android ROM for this? Will flashing a new ROM damage the windows in the Tablet? Is it fairly straightfoward like a normal android tablet? Any tips, opinions, reviews and etc. Are greatly appreciated.