yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] googlephone:
How long does the first boot take? It's at the spinning screen for 10 minutes now.

Update: it took 11 minutes to pass the spinning screen, and a total of 34 minutes to finish the boot up.
[TouchPad Development] The Jack of Clubs:
dirty flash from cm11 or something?
[TouchPad Development] googlephone:
Yes. From jcs 20150113 cm11 build. I wanted to try if dirty flash works.If not, I would just go to recovery wipe data and reboot (I had my apps backed up with mybackup pro.

So far, it seems dirty flash works, took long time to boot up though.

---------- Post added at 07:39 PM ---------- Previous post was at 07:36 PM ----------

Anyone know where is the superuser setting? It used to be above developer options in cm11 but I couldn't find it in settings menu in cm12. I can see superuser request prompt.
[TouchPad Development] yohaskan:
Hi Milaq,

Nice to see you in another adventure of The lost TouchPad

Is it the same Media partition/Datamedia we use from last rom's Invisiblek [5.0.2][3.4 Kernel] CyanogenMod 12.0 ?

Can we test in dirty flash from here ?
[TouchPad Development] StoneRyno:
What can I expect going to CM12 from CM11? Like are there compatibility issues with apps I am using to be concerned about? Is it recommended for daily use? I mostly play games with my touchpad on a daily basis. And less frequently watch video (YouTube, hulu, netflix, etc), web browse, and email.
[TouchPad Development] bundys:
Two quick bugs I found.

1 - When rearranging tiles, the wrong tiles move under my finger (seems like an offset issue).

2 - Settings crashes when I try to enable swiftkey keyboard from its own interface. If going through language/input interface in settings, swiftkey doesn't even show up despite being installed.

Otherwise the performance is great on this ROM.
[TouchPad Development] BIGSimon:
Superuser has been merged with Privacy Guard, make sure that root access is selected in Developer Options, go back then look in Privacy / Privacy Guard tap and hold on one of the apps to see all the permissions for that app, Root access is normally at the bottom of the list.
[TouchPad Development] puhleez:
This version works great on my touchpad. Perf is good and digitizer works. Assume the 3.4 kernel has some issues with some touchpads? Only issue I have is when streaming music the WiFi will drop out and then the music stops but it does eventually recover.
[TouchPad Development] Czo:
Anyone with random reboots? With today build, i have reboots in every 5-10 minutes, so i switched back to 0118 build, because the reboots rarely with it.

last_klog attached from a panic with 0118.
[TouchPad Development] yohaskan:
Lot of reboot too. Every wake up, Freeze and reboot
[TouchPad Development] puhleez:
No reboots so far for me.. Will continue to use throughout the day and see.

Edit: lol spoke too soon. First reboot just happened.
[TouchPad Development] bundys:
Looks life digitizer issues were caused by the boot partition running out of space. Once the Evervolv boot image was deleted, cm installed fine, both 3.0 & 3.4 kernels.
[TouchPad Development] Czo:
Reboots seems to be wifi/ath6k/sdio related. I have 3 more crashlogs.

edit: Yes, it's WiFi related. Upload test with speedtest.net app always reboots the device.
[TouchPad Development] daedric:
This is pretty vague, but do you notice the gpu performance weaker ? I have random very minor but noticable slow downs on games. I game fully and perfectly played in KK will now suffer a certain... frame slow down... hard to explain.
[TouchPad Development] The Jack of Clubs:
Yeah changing keyboards causes fc's for me too. Is Bluetooth working? I can turn it on but it doesn't find any devices.
[TouchPad Development] sindizzy:
The sound cutting off is a real downer for me but Ill keep using it to test. I usually listen to music in the morning for about an hour and then it cuts off. I switch over to my phone. Then I just shut the TP down.

Btw, is there a way to overclock it to get a bit more performance out of it?

~AGP
[TouchPad Development] nevertells2:
Did you search in the Play Store for overclocking apps? I use Antutu's.

NT
[TouchPad Development] sindizzy:
Ill give that a shot. I've never used them in the past. Are there any settings you recommend?

~AGP
[TouchPad Development] nevertells2:
That is really up to the developer. Most of these Roms will overclock to 1800 easily if the kernel supports that speed. The app should show you the max speed allowed. Remember to check "Set on Boot". Rom Toolbox Lite is another app that does over clocking. I've used it before too. BTW, if you have Developer Options turned on, have you looked in settings/Performance/CPU to see if over clocking is supported there?

NT
[TouchPad Development] real_sl4cker:
So flashing this with (jcs or flintmans) dm TWRP won't work?

(Yes I know the question sounds dumb at first but I've read many posts like that which actually mean "Any recovery with datamedia support required" so I thought asking won't hurt any lamas)
[TouchPad Development] nevertells2:
Not quite sure what you are asking. Is your TP already setup for data media? What Rom do you have currently installed? If you already have some CM version of Lollipop installed, then yes you should be able to flash Milaq's Rom with a data media recovery. Do not flash a CM based Rom over the top of a AOSP version like Flintman's Evervolv or visa versa.

If your TP is not currently set up for data media, then you need to follow the instruction on how to install a data media Rom, preferably with Sullin's Touchpad Toolbox.

NT
[TouchPad Development] real_sl4cker:
I'm currently on Pac-Rom KitKat and plan to switch over to Lollipop through tptoolbox via complete data reset. I know about the process itself (partition resizing ...).

Well, I will just try with latest TWRP from flintman and see if it'll work or if indeed CWM is explicitly required for this ROM.
[TouchPad Development] jerryatherton:
I would recommend just using TPToolboc to resize your partitions . Flash the Flintman TWRP. Then use TWRP to wipe an install rom and gapps of your choice.
[TouchPad Development] real_sl4cker:
Well, this is getting ot but won't tptoolbox boot into recovery and flash the contents of ttinstall with it anyway? Why do you suggest to install manually via TWRP? Did you have any issues letting tptoolbox handle the install?

EDIT:

Ok, tptoolbox refused to install the combination of milaqs CM12 nightly, flintmans TWRP and 5.0 GApps minimal so I used the packages linked in the OP and tptoolbox did it's thing. Didn't test installing only TWRP and flashing CM12 and gapps manually yet.

(mobil gesendet / sent from mobile)
[TouchPad Development] jerryatherton:
That is why I recommend to do it in recovery. I have difficulty getting a acceptable combination of files for the ttinstall.. I also install toolbox in my boot image so it is on all of my tablets on the moboot menu.
[TouchPad Development] real_sl4cker:
Yeah already got the impression that this is the reason you recommend installing via recovery manually so I edited my post ;)

I also always keep tptb on /boot :good:
[TouchPad Development] nevertells2:
Mr. Sullins posted in his toolbox thread that it does not support installing Android without Gapps and I suspect that goes for just trying to install just recovery. I have also read that v42 appears to have problems with Android 5.1.1. The work around for that would be to install 5.0. first and then use recovery to move up to 5.1.1 and then it's Gapps. I've also read that some of these offbeat versions of Gapps give TPTB v42 problems. I suspect if you stick with what is recommend here, you should be OK: http://wiki.cyanogenmod.org/w/Google_Apps.

NT
[TouchPad Development] ryancell:
Was it mentioned yet if this will adapt to cyanogenmod 12.1 in the near future? Just making sure I didn't miss any announcements. Thanks! I check this thread daily and wanted to make sure I didnt miss it, or another thread for 12.1. I have Lollipop 5.1 on my phone and it seems a lot more stable. If my touchpad gets 5.1 I'll be happy never upgrading it again. lol. Thanks!
[TouchPad Development] real_sl4cker:
As far as I've seen flintman is the only one who has released a 5.1 ROM for the TP up to now but it's AOSP. I'm also impatiently waiting for CM 12.1
[TouchPad Development] BuffMcBigHuge:
Hey Milaq! Posted my experience in flashing this build here.
[TouchPad Development] jerryatherton:
Shumash has a 5.1 ROM based on CM. I am running his and Flintmans. Decent stability on both and very fast.
[TouchPad Development] real_sl4cker:
OMG how could I forget about shumashs build. Of course it's not CM but the Pac ROMs are also very nice, customizable and smooth. I was running shumashs 4.4.4 PAC ROM for a long time and really enjoyed it.

(mobil gesendet / sent from mobile)
[TouchPad Development] nevertells2:
What do you mean it's not CM? PAC-ROMs are CM based with all the PACMAN tweaks and enhancements build in.

NT
[TouchPad Development] sindizzy:
How is sound? Mines cuts off after about an hour. Im running CM12 Milaq Lollipop 5.0.2.
[TouchPad Development] real_sl4cker:
of course you're right. I meant "it's not pure CM". Options are placed differently etc. But yes, the base is CM

(mobil gesendet / sent from mobile)
[TouchPad Development] ryancell:
I'm at work and don't have my touchpad, but 12.1 is here. Once its stable will 12.0 flash automatically to 12.1 or can you flash to 12.1 from 12.0 and can keep all your stuff intact?
[TouchPad Development] FletchF:
Which gapps is recommended for use with the milaq 5.1 builds?
[TouchPad Development] nevertells2:
By any chance, did you read Milaq's OP? Wealth of information!!!!!!

NT
[TouchPad Development] shumash:
In his 5.1 thread; not this one.
[TouchPad Development] FletchF:
I was looking for a 5.1 thread but couldn't find it. Got it now. Thanks.
[TouchPad Development] nevertells2:
Where did I miss that? Is there a post here that has the link to his 5.1 thread? :o

Technically, wouldn't the Lollipop Gapps in the OP of this thread work with Lollipop 5.1?

NT
[TouchPad Development] shumash:
Nope, nope, and finding one that's not buggy is problematic. The 5.1 thread is marked experimental,BTW.
[TouchPad Development] PetrichorXFi:
Yup, reboots after about 3-10 minutes. I saw someone else say they thought it was WiFi related?

Question... so I am using the 5ghz WiFI, NOT the 2.4Ghz WiFi. Perhaps the 5ghz has an issue?
[TouchPad Development] daedric:
5ghz has issues, even in the original OS.
[TouchPad Development] PetrichorXFi:
Been having lots of issues with this build, anyone else getting these?:

1) touch screen is REALLY bad. Worked fine on the JB build by JC, but on this build it keeps thinking I am clicking keyboard letters twice.

2) artafacts: I think it is a transparency issue, for example open Play Store, find an app, click install, when the permissions prompt comes up the stuff in the background has moving lines... Looks like old CRT almost.

3) Sound issues: sound gets super mechanical sounding... Reboot fixes it. Not sure cause... Seems to happen about once per day.

4) Sound issues #2: volume will just not work. Its like it thinks I am using external audio perhaps... Because it will show audio is on... Just no sound. Again, reboot fixes. Experienced this is across all apps. If it happens it is global...

5) Bluetooth: cannot even see Bluetooth devices... It says it turns on Bluetooth, but does not see discoverable devices.
[TouchPad Development] Cyber Akuma:
I am using TouchPad Toolbox to resize my Android partitions manually since I don't want to go through the whole mess of uninstalling then re-installing WebOS, and I am confused about the partition sizes.

It says that both Media and System need to be at least 896mb, and the rest go to the data partition... which would be the SDcard.

However, seems in my default setup right now (which had I think Ice Cream Sandwich before), my data partition is only 1536MB.... and my media partition is 11008MB. Wouldn't this mean it was my media partition that was mounted as my "sd card", not my data partition?
[TouchPad Development] Syaoran:
Hi all

Are there other users here having an issue with the Wifi on/off switch in Settings or from the notification panel?

I can turn it on and everything is fine, but I am unable to turn it off...

Using yesterday's build: cm-12-20150529-UNOFFICIAL
[TouchPad Development] real_sl4cker:
ICS has another partition layout than later versions (JB +) which are datamedia builds. There are plenty of how to threads about this (as I'm on my mobile I'm too lazy to search for you now [emoji14]). Usually when flashing via tptoolbox it selects the best layout automatically for the desired ROM.

(mobil gesendet / sent from mobile)

---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------

I also had this issue but the current build fixed it for me. Maybe delete your WiFi settings and set them up again?

(mobil gesendet / sent from mobile)
[TouchPad Development] nevertells2:
Who's Rom are you trying to install? All Roms since Jelly Bean use a new format(data media) which puts the SD card in the /data volume. Mr. Sullin's TouchPad Toolbox only leaves about 800mb in the /media volume so the necessary files to install Android Jelly Bean, KitKat or Lollipop are put there in the ttinstall folder. Mr. Sullins instructions for those who want to keep WebOS are a bit misleading. If you want to keep WebOS, not sure why, but, and you want to remove the old non-data media version of Android before installing a data media Rom, you can just use ACMEUninstaller2 and then run TPTB and only select "Install Android" and the toolbox will set the /volume sizes for you.

Be forewarned, any version of lollipop you install is going to be very experimental and has a lot of issues that need to be worked out. If you want maturity and stability, stick with KitKat, Android 4.4.4. I personally like Mr. Sullin's 20150113 KitKat Rom. But which developer's work you choose is up to you. I would also be sure you are using TPTB v42. It handles installing the latest versions of Android much better than v40. Good luck

NT
[TouchPad Development] Cyber Akuma:
Isn't that the partition that WebOS uses for it's own storage though? Back when I was on ICS the WebOS and Android storage partitions were linked.
[TouchPad Development] real_sl4cker:
Yes, WebOS uses the media storage which will be rather small by default when flashing a datamedia Android build via tptoolbox. If you need more space for WebOS you could resize the partitions manually, this is offered by tptoolbox as well during Android installation.

(mobil gesendet / sent from mobile)
[TouchPad Development] Syaoran:
Today's nightly didn't solve the issue. Even after wiping the user data & cache with CWM it persists. There is no way to turn off wifi. The radio goes off for a few seconds and then magically reconnects to the network. I am forced to shut down the tablet in order to have energy left for later :silly:
[TouchPad Development] real_sl4cker:
You are right. After flashing the 20150529 build first I was able to set my TP to airplane mode and WiFi stayed off (before it re-enabled itself after setting to ap mode) but yesterday I saw that the issue still persists.
[TouchPad Development] voidstab:
Wow, great work and great rom!

I happened across a touchpad and decided to try this for fun and I'm amazed how usable it is.

I just wiped the whole thing, I couldn't see any reason to keep webos, and the toolbox setup the partitions on its own.
[TouchPad Development] nevertells2:
I have never left WebOS installed, so I can't tell you exactly how much storage space TPTB will leave behind for it. Of course, if you need more storage in the /media volume, you can always use TPTB to move some back to /media from /data

You are correct. Before data media, Android and WebOS shared the memory in the /media volume. With the advent of data media, most of the available memory is moved to /data. The main advantage of data media is all that memory is available to internal memory and the SD card. So no more problems running out of internal memory or if you remember the 50 app limit, that would cause the SD card to become unmounted, is gone.

Just curious, why do you want to keep WebOS installed?

NT
[TouchPad Development] voidstab:
Now that I've been using this a while I've noticed the wifi sometimes disconnects, is this any kind of known issue or any suggestions? I was using build 0530 and now 0531 with no change.

Thanks

*edit

I'm also experiencing the behavior mentioned in post #218, with the wifi switch not working.

Did all touchpads have a 5ghz radio? If so mine doesn't seem to be working.
[TouchPad Development] voidstab:
A little more on my disconnect issues. The router logs were showing several mentions of "address in use" and I noticed it had 4-5 dhcp leases all for the touchpad mac, I've never seen this behavior before, so I rebooted the router and I'm hoping for the best. I haven't had a chance to use it much since rebooting the router.
[TouchPad Development] Syaoran:
With build 0602 the wifi still turns itself back on.

Also, the connection is highly unstable. You can't update more than one app at the time. It will do one, then connection fails.

The web browser doesn't seem to have this disconnection problem.
[TouchPad Development] pedro_rl:
Try turning it on and off several times leaving it off the last time, that often leaves it off
[TouchPad Development] voidstab:
I'm leaving the switch alone. I was initially running the install from the TPToolbox, I have since done a clean install from CWM recovery and Wifi stability has been good so far, for a few days. I like using the device, believe I'm on 0531.
[TouchPad Development] buzz86us:
Trying to pair my Bluetooth keyboard but it only gives me 1/10 of a second to type the code before it fails is there a problem with Bluetooth on this rom?

'Update' it is definitely the rom just used jcsullins kk and it works perfectly. I guess I'll wait and see for jb roms
[TouchPad Development] sindizzy:
I noticed this too. At work I have to reconnect about 4 or 5 times a day.
[TouchPad Development] TJude:
My WiFi is highly intermittent. On for about 60 seconds and then off for 15. Cycles like that all day. Not precisely, but very predictably. Just went to v.12 yesterday.
[TouchPad Development] johnbelloh:
Help - I have been running Milaq's 5.0.2 for a couple of months following a clean install with TPtoolbox including removal of Webos. Other than some minor problems I have used it as a daily driver. Following the latest update it locked up after a boot and went dead. It will not boot with the double key press. Windows does still sees it as a USB device. Oddly enough it disables and re-enables USB in Windows at the same delay on the double key press when it should reboot. Any suggestions appreciated.
[TouchPad Development] real_sl4cker:
Maybe the battery went to 0? At least I saw this behavior (mentioned here in the TP forums many times) 2 times myself. You could plug it into the stock charger for some days to see if it will come up again (though this never worked for the TPs I took care of). There are other suggestions flying around in the forums, search and try them. As a last resort use jcsullins' tpdebrick to revive the TP (worked like a charm for me 2 times).

(mobil gesendet / sent from mobile)
[TouchPad Development] johnbelloh:
The Battery was at 100% when it died. I eliminated Webos with the toolbox. Is there a version of tpdebrick that runs under Windows?
[TouchPad Development] real_sl4cker:
No, it only runs with Ubuntu 12.04 (live cd). The instructions in the tpdebrick thread are very detailed so even a Linux newbie shouldn't have much trouble working this out. Feel free to post in the tpdebrick thread if you have any questions.

(mobil gesendet / sent from mobile)
[TouchPad Development] johnbelloh:
The good news is I finally got Ubuntu to work. I had to search for a bunch of updates to Ubuntu to get tpdebrick to work and connect to the touchpad. The bad news is it talks to it but it is still bricked. Help - Here is the scrip from running tpdebrick-v004 on my TP32:

Writing 1024 bytes to 0x2a027c00; 2180 bytes left.

Writing 1024 bytes to 0x2a028000; 1156 bytes left.

Writing 1024 bytes to 0x2a028400; 132 bytes left.

Writing 132 bytes to 0x2a028800; 0 bytes left.

Executing file...

Checking QDL mode...

Writing file tz.mbn ...

Sending MAGIC...

MSG: Qfprom Fuse List: Blowing FAILED

MSG: Failed Fuse addr:

MSG: 0x00000000

MSG: Error Status:

MSG: 0x00000000

Sending secureMode...

Sending openMulti ...

MSG: Open multi failed, unknown error

ERROR: Open multi failed, unknown error

Invalid openMulti response.

Cannot write file tz.mbn

Aborted.

Any suggestions welcome.
[TouchPad Development] nevertells2:
Yeah, two suggestions. Post this is the debrick thread and read the whole thread. Virtually every situation/question has been discussed/answered more than once. There is a wealth of information there.

NT
[TouchPad Development] ranjib:
I've got a dead touchpad, too. Get the same reaction by tpdebrick....no chance.
[TouchPad Development] johnbelloh:
I read that entire thread before I posted here. No one has posted there since last year and there are only 2 pages of posts with no help. I came here because I am using this rom and it bricked the touchpad. I don't post until I have read all the treads on a problem and try to contribute any information that may help others.
[TouchPad Development] nevertells2:
I don't know what Debrick thread you are reading, but I count over 40 posts just since April of this year in the one that I am reading. And, if you had read it thoroughly, you would know that ROMs don't brick touchpads. It is just coincidence that your touchpad decided to brick itself while you were using this particular Rom. You might be one of the lucky few who owns a touchpad that will brick for no apparent reason, no matter how well you treat it or what you do to it to try to prevent it from bricking.

And again to answer your request for suggestions, virtually every situation/question has been discussed/answered more than once in the thread I am reading.

One other question comes to mind, how many times have you run the Debrick script? Some people have had to run it hundreds of times before they finally got it to work. Just a thought!

NT
[TouchPad Development] johnbelloh:
jcsullins latest TPDebrick v004 is the thread I read and posted in. My post is #20 and the only one posted this year. What thread are you reading? I have run the Debrick script at least 25 times with no success. I was hoping to find some code I could copy into Ubuntu terminal that might get it to respond to the Debrick script. Thanks for the suggestion.
[TouchPad Development] real_sl4cker:
Maybe some chip on your TP died so probably it's a hardware issue. You can try googling for the exact error message. There is a tpdebrick thread on rootzwiki as well.

(mobil gesendet / sent from mobile)
[TouchPad Development] nevertells2:
This is the thread I am reading with almost 1600 posts: http://rootzwiki.com/topic/38786-tpdebrick-v004/ What thread are you reading? If that is not the thread you are reading, you are missing out on a lot of valuable information.

NT

P.S. I just did a little creative Googling and found the thread you have been posting in. BOY, have you got some reading/research ahead of you. :p

And here is the real kicker. The link in the very first post of the XDA thread you were reading takes you to the REAL, active Debrick thread in RootzWiKi. :(
[TouchPad Development] johnbelloh:
NT - Thanks for the info. I read through the Rootzwiki thread last night and must agree it appears to be a hardware issue. I hated to give up that touchpad. It was the original one I purchased from HP years ago. It is now in my spare parts collection. I did a clean install of this ROM using tptoolbox on another TP. Everything is working fine except for Milaq's updater. I am using Phil's recovery from Milaq's downloads and installed super su. Super su hangs up at times as does Milaq's updater. I have Phil's option set for root access. Any thoughts?