yashsingh1/xdaforums huggingface dataset:
[TouchPad Development] AlwaysLucky:
I'm getting this crash for Gallery on boot. It opens fine, but I thought I'd pass the catlog on. Looks like a secure settings issue...

09-07 15:28:10.338 1237-1237/com.android.gallery3d E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.android.gallery3d, PID: 1237
java.lang.RuntimeException: Unable to start receiver org.codeaurora.gallery3d.video.DmReceiver: java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3018)
at android.app.ActivityThread.-wrap18(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1544)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6077)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)
Caused by: java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:165)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.call(ContentProviderNative.java:646)
at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1567)
at android.provider.Settings$System.putStringForUser(Settings.java:1938)
at android.provider.Settings$System.putString(Settings.java:1922)
at org.codeaurora.gallery3d.video.DmReceiver.onReceive(DmReceiver.java:39)
at android.app.ActivityThread.handleReceiver(ActivityThread.java:3011)
at android.app.ActivityThread.-wrap18(ActivityThread.java)*
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1544)*
at android.os.Handler.dispatchMessage(Handler.java:102)*
at android.os.Looper.loop(Looper.java:154)*
at android.app.ActivityThread.main(ActivityThread.java:6077)*
at java.lang.reflect.Method.invoke(Native Method)*
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:865)*
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:755)

---------- Post added at 04:15 PM ---------- Previous post was at 03:35 PM ----------

Look through this thread. And be sure to provide many more details than that. I can tell you however, that only specific roms, gapps, and twrp versions can be used with TP Toolbox. After the initial install, you can flash this ROM, open Gapps, etc.
[TouchPad Development] Slugdude127:
Flashing via TPTB, incomatible GAPPS/ROM

Hi, I'm following the instructions in the OP [MENTION=3716175]flintman[/MENTION] but TPTB says:

"Incompatible GAPPS/ROM versions None/7.0"

Weird, huh?
[TouchPad Development] renardk764:
I performed a clean install. I've found over the years that when moving to a new version of Android a clean install saves me a lot of headaches. I was able to get the Marshmallow version of Evervolv to install. I'll try Nougat again this morning and see what happens
[TouchPad Development] Epanosian:
:good: :good: :good:

Using TPToolBox, resized system (4GB, more than the min mentioned in the 1st page), finished post #54 and installed Sep 18 version successfully.

thank you all for your help.

Question: how can I verify how much of 4GB is used?
[TouchPad Development] elginsk8r:
If you set the system to anything higher than what was specified in post #1 android will not show the correct size. Seems related to the block mode for flashing in recovery. Could be a correlation or the root cause of the issues others have pointed out. Mind you I have been wrong before so take my thoughs with a grain of salt until we can test and verify.
[TouchPad Development] middle_road:
Any good diskinfo app will show you or you can install a terminal emulator and use the command df

Results of 'df'

tmpfs 419336 444 418892 1% /dev

tmpfs 419336 0 419336 0% /mnt

/dev/block/mmcblk0p13 32745 29362 3383 90% /boot

/dev/mapper/store-cm--system 1322320 880716 441604 67% /system

/dev/mapper/store-cm--data 20969472 1581288 18794264 8% /data

/dev/mapper/store-cm--cache 774064 13712 760352 2% /cache

/dev/fuse 20969472 1581288 18794264 8% /storage/emulated

/dev/fuse 6117856 4726688 1391168 78% /storage/BDA7-DD6B

You'll notice that /system gets resized down to ~1320 after installation.

you can up it in TWRP if you desire.

_Dan
[TouchPad Development] Epanosian:
:confused:

I thought min in '**REQUIRES 1312MB System Partition MIN. ' means 'minimum'. shall I repeat the steps and change it to 1312 MB ?

---------- Post added at 04:37 PM ---------- Previous post was at 04:27 PM ----------

does it release the rest (4GB - 1320MB)?
[TouchPad Development] middle_road:
That's what I saw first couple of flashes. I'd set /system to 2048 under TPTB and it would get changed, but 'df' in terminal both the ROM and in TWRP returned ~1300.

If I hadn't changed the FS to F2FS I would go back into TPTB and it still showed 2048. But the Gremlins would start goofing around

I figure to just let the installation of the ROM set it and then I'd leave it. I still set /system to 2048 along with setting /media at 6144 because

I'm using that to transfer files with Root Explorer and the PC.

---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------

That hasn't been determined yet. I personnally haven't really noticed, but then I haven't been looking too closely.

Five years of running on these tablets, and I've never got close to 20GB. YMMV

I've been doing 2048 just in case as the ROM matures it needs more space. Old habits.
[TouchPad Development] AlwaysLucky:
Glad you figured it out! After seeing your first post the first thing I thought to myself is "I wonder if he's using the most recent version of TP Toolbox..." :laugh:

Then after reading I see that was the issue. Glad my guide worked for you. I will update it to be a little more clear.
[TouchPad Development] costy11:
Works great so far, kid tested by a 3 year old. I wiped everything from scratch as I could not fix my partitions through TPTBx.

Then did post 54, to get back to a functioning system.

Boot times are way faster and when up, way more responsive!!!

Thank you for making one of my oldest devices, most up to date first!!! :D
[TouchPad Development] duyhung0185:
Hi, my Touchpad is currently having problem with wifi. I installed CM 12.1, Evervol 6 and now 7. All 3 wifi would not work, only "connecting..." and never connect to my wifi network.

I tried changing channel to 1 and 6, limiting to bg speed but it still wouldn't work.

Is there anything i can do to fix wifi ?

Thanks!
[TouchPad Development] Moody66:
Clean install....
[TouchPad Development] BGrosse:
If you still have WebOS installed, boot into it and check if this happens on WebOS also. If yes, there is a high chance you have a hardware related failure. Otherwise it's software related and I would do a complete wipe and fresh install.

Maybe you have also a second TP to test your WiFi connection? Just to ensure, your WiFi connection with the same parameters for connection is ok.
[TouchPad Development] nevertells2:
You can try Quick System Pro and see what it shows.

NT

---------- Post added at 11:04 AM ---------- Previous post was at 10:58 AM ----------

Have you tried going back to KitKat just to verify you have not developed a WiFi problem with your tablet. WiFi on Evervolv 6 is solid. Far as I am aware, it is solid on CM12.1. Evervolv 7, not so much until the most recent build. But that it to be expected.

NT
[TouchPad Development] gtallmadge:
Have now installed this ROM, 9.18.2016, on three TP's. Two were clean installs and one dirty from 6.0, all are running really well without problems. WiFi connects and stays connected. Kudos to Flintman for again keeping our Touchpads up to date with Android. Also thanks to AlwaysLucky for his install enhancement directions, helped to make the installation easy and right the first time. Great work!
[TouchPad Development] Martyr_Dumb:
Installed this today, pretty easy...even for a functional idiot like me. Thanks so much to flintman and everyone else posting good information!

Question, upon reboot (when I'm plugged into charger or pc) I'm getting this notification: "Virtual USB drive detected", with two options of "Set Up" and "Eject". It doesn't appear when unplugged. I'm able to swipe it away and carry on, but I'm wondering what the heck it is. Did I miss something while flashing (very little experience with twrp) or is this a new feature of Nougat?
[TouchPad Development] duyhung0185:
It is kind of strange though, because after i first flash CM12 wifi will connect, but after thaty wifi reset and it will no longer connect.

I feel its some kind of permission or cache / data save error, but i dont know how to fix this.

Wifi networks detected fine, and 1st connect is good also, i can sign in, install some apps, update ... so i think its not hardware related.

I did start anew by installing from HP Toolbox ... I'll try going back to Kit Kat.

Thanks!

---------- Post added at 03:12 AM ---------- Previous post was at 02:43 AM ----------

Uh, i go back to WebOS and it connects just fine, on both 2.4Ghz and 5 Ghz channel ... This is driving me nut ...
[TouchPad Development] muerte33:
Try using the legacy DHCP client just for kicks, it cannot hurt.

Developer options > Use Legacy DHCP client
[TouchPad Development] crutzulee:
The latest build has been running well on my TP since it came out. I have not had any wifi issues with any of the builds at home..At work however, i have had issues since day one. The latest build has improved the sitution but apps like netflix are unusable because of the random wifi drops on my network at work...At home everthing works flawlessly so it stands to reason that router/wifi adapter combination is to blame..

Unfortunately, i am not able to have any kind of play on how my workplace network is setup?
[TouchPad Development] trevor4706:
Best way to install TWRP over CWM

I'm replying to this (relatively) dated post instead of making a new post as I don't have enough posts to allow that.

I want to try Nougat on my TP. I've installed a dozen or so EV 6.0 Nightlies and have always used CWM Recovery without any issues. I understand EV 7.0 test builds are a little more particular about the recovery used, and would like to install TWRP. I've been searching on-line for the best way to install TWRP over CWM and, as usual, there are a lot of different suggestions. I'd like to know what members of this forum who have been in the same position have used before I take the plunge.
[TouchPad Development] Globaltraveler5565:
Bluetooth partially working

I've successfully paired two different keyboard vendor equipment with the 9/18 Nougat release. But the two audible speakers fail, turning the TP bt service setting off/on. It does detect the speaker devices, just won't connect them. It seems like equipment that requires a pairing key is accepted, while devices that do not need a pairing key entry fail. Logs attached; look between 4:15 and 4:45 pm EDT.

http://cloud.tapatalk.com/s/57eadd33aae74/2016-09-27_16.48.zip

Marshmallow late stage releases were working better. Is there some sort of custom code for TP that needs to be ported over? Just a thought...
[TouchPad Development] jerryatherton:
I would suggest make a cwm backup, then flash the latest twrp from this OP. I have done it before with other versions. Also make sure you increase your system cache with the TP toolbox.
[TouchPad Development] nevertells2:
Just use CWM to flash either of the two TWRP versions in the OP. Just keep in mind that any backups you have made with CWM won't be restorable with TWRP, so be sure to make a new backup with TWRP before attempting to install Nougat. And always store a copy of your backups CWM and TWRP on your PC for safety.

NT
[TouchPad Development] trevor4706:
Roger that. Thanks for the advice. will give it a go.

---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------

Great advice regarding making new back-ups with TWRP. Would not have thought of that. Many thanks.
[TouchPad Development] trevor4706:
I just installed Nougat and was surprised by the same notification. Did you ever get an answer to the question above? I've done a search on-line and haven't found anything.
[TouchPad Development] Martyr_Dumb:
Nope. Nothing yet.
[TouchPad Development] nARMstrong20:
Do either of you guys have WebOS installed or another OS by any chance?
[TouchPad Development] Nomad1600:
Scroll to page 4... It is discussed there.
[TouchPad Development] nevertells2:
Based on the size of the storage reported in Nougat settings, I'm thinking that it the Legacy/Media storage put there by TouchPad Toolbox for the purpose

of installing Android with TouchPad Toolbox.

NT
[TouchPad Development] trevor4706:
I still have WebOs installed, primarily so I can use Tailor app to adjust partitions. I wondered if the WebOs partition(s) might be the cause of the notification.

---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------

Funny. I searched the forum for posts referring to this issue and that one didn't pop up. Thnx for pointing it out.
[TouchPad Development] nARMstrong20:
I doubt it's webOS. I have several partitions on my Touchpad for webOS and LuneOS, but I didn't get that notification on the latest build. Nomad mentioned on page 4 that it might have been when he accessed his touchpad from his computer. I wonder if you're able to look into the contents of the partition via Settings > Storage & USB > Select the partition in question > Explore and see if any of the files there match up with the files in a partition you have?
[TouchPad Development] Gladpants:
Has anyone had video playback stuttering. I get this when im trying to watch video in MLB.tv. Large stutters and slow downs with dsync between video and audio.
[TouchPad Development] BGrosse:
Yes, it is the WebOS data partition with the "ttinstall" folder in it (and every other folder within the WebOS partition like ".palm", "DCIM", "ringtones", "wallpapers" and the mandatory "Open Source Information.pdf").
[TouchPad Development] nevertells2:
If you are keeping WebOS install only to have access to Tailor, then you need to go here and read. http://xdaforums.com/showthread.php?t=2756314

TouchPad Toolbox has a function that does what Tailor does, only ten times better. I think after reading that thread and trying out the "Volume Resizer" in

TPTB, you will be in a big hurry to remove WebOS. :):)

NT

---------- Post added at 11:04 PM ---------- Previous post was at 11:02 PM ----------

You must still have WebOS installed, or none of those folders and files should still be there. :p

NT
[TouchPad Development] middle_road:
+1 to what NT says.

There is no need for WebOS any more. Heck HP has killed it off so you really don't need it cluttering up your device while trying to install and run the latest and greatest Android version.

I personally haven't touched WebOS, and this is across 8+ Touchpads, in over (4) years...

With JCS's TPTB and TWRP - all the bases are covered.

_Dan
[TouchPad Development] rebel1699:
Not necesarrily. I do not have webos installed, yet the webos partition containing ttinstall folder is still present after removing webos. Seems removal of webos via tptb never removed and repurposed that partition, for whatever reason (most likely because that is where tptb will look for a rom and gapps, should you ever need to flash again). Removing that partition would make tptb useless for flashing later. Unless you have removed it manually, you may also still have it located under /mnt/media_rw

But yeah, the other files should not be contained within it (.palm, dcim...etc)
[TouchPad Development] trevor4706:
Different strokes, I guess. You need your PC to use TPTB and I need WebOs for Tailor. I am very familiar with Tailor and don't find it a hassle to boot into WebOs to use it. You have given me food for thought tho, so perhaps when I install the next EV iteration of 7.0 I'll try TPTB and maybe cut the WebOs cord.

Thanks
[TouchPad Development] Nomad1600:
Actually you don't need your PC, you can add TPTB to your boot.
[TouchPad Development] googlephone:
With webos on the device, there is no enough space to put TPTB in the touchpad.

He does need to use PC to use TPTB to remove webos. Then he can put TPTB on TP and doesn't need PC anymore. So he needs a PC at least one time.

Actually on my 32 GB touchpad, I still have webos on it and never used TPTB. Since I have already put android and CWM or TWRP recovery on the touchpad in the CM 7 days (2011), I don't need TPTB at all.

I have 32 GB storage, and I allocate most storage to android and don't need the occupied storage by webos.

I keep webos also because when the device turns old, it can still have its webos identity and becomes an antique, even though touchpad seems never dying due to the fantastic support from developer like flintman.

For those with 16 GB storage, it's better to remove webos for more usage storage.
[TouchPad Development] shumash:
And actually, you don't need a PC if you have Android installed. All you need is a root file explorer. You delete uImage.WebOS, rename the .bin file with a uImage name, and copy it to /boot. Here's some directions.
[TouchPad Development] nevertells2:
Actually, with WebOS removed, there is plenty of room in the /boot volume to run TPTB from your Touchpad with no need for a PC. Also, removing WebOS frees up around 5 gigabytes of memory for Android. I understand that you are very comfortable with Tailor. But you really need to try out the memory resize function of Touchpad Toolbox and see how easy it is to use. Once you've done that then you'll understand why there is really no need for WebOS/Tailor any longer. And, from time to time one needs to reflash the A6 firmware which is done from Touchpad Toolbox. Having Touchpad Toolbox in the /boot volume, makes this extremely easy.

NT
[TouchPad Development] googlephone:
All those benefits like resizing,and flashing A6 firmware can be done in webos just as easy. The only extra benefit of using TPTB is gaining more storage after removing webos, and for those who are trying to load android for the first time.
[TouchPad Development] nevertells2:
Yes, that gets Touchpad Toolbox into the /boot volume, but that does not accomplish the magic of Touchpad Toolbox freeing up all that memory for Android.

NT

---------- Post added at 11:29 PM ---------- Previous post was at 11:04 PM ----------

I am getting the impression that you really don't like Touchpad Toolbox that much. Touchpad Toolbox is the slickest, most innovative utility created for the Touchpad in years. It would be nice if JC Sullins would update it so that installing the latest versions of Android would be included, but that's up to him. You can always use Touchpad Toolbox to get your TP configured for data media Roms, and then use recovery to install Marshmallow or Nougat. However, if you are a die-hard WebOS user, please don't let my arguments for removing WebOS persuade you to do so. There is a cult over on the WebOS Nations forum that practices the voodoo of keeping WebOS alive and kicking on the Touchpad. Each to his own. ;)

NT
[TouchPad Development] googlephone:
No no no.

I have pretty good impression with TPTB.

You seem like enjoying guessing the feeling or thinking of others. I am sorry to say that you are not good at it at all.

I just don't want to do anything that doesn't give me any benefit. TPTB is really good but has no value to my 32 GB touchpad so I chose to not use it on this 32 GB touchpad.

I have 4 other touchpads for my family members, 2 of them are 16 GB version and two are 32 GB version. I used TPTB to remove webos on those two 16GB touchpads but for those two 32 GB ones, I didn't use TPTB.

Everyone can evaluate the value of TPTB and not everyone has to agree with you that they must use TPTB.

You are acting like everyone should do the same thing as you. The answer is no, everyone can have their own choice and preference.

BTW: I am not a webos die harder.. I didn't use my 5 touchpads at all until the android hack CM 7 came out in December 2011.
[TouchPad Development] middle_road:
OK all.... Deep breath, grab a cold one and remember there are much more important things in life.

This tablet is still viable because of the community, let us keep it vibrant.

So back on topic, I was finally able to lounge around last night and start messing with the tablets.

About the only problem I had (besides the nut using it) was the touchscreen going dead.

The only app crashes that I had were tied into Amazon Underground and certain apps from it. And THAT is a whole other story.

The reboot time is fantastic. Can't even run off to grab a snack. Had (3) going, two on N and one older one running KK.

Beat up on one of the N's loading a bunch of apps and it didn't seem to flinch. I did wipe and restore it this morning over coffee though.
[TouchPad Development] joshua764:
Thanks

Enviado desde mi Touchpad mediante Tapatalk
[TouchPad Development] KennyG123:
Thread cleaned

Please keep the tone respectful

Thanks

Friendly Neighborhood Moderator
[TouchPad Development] joshua764:
they help me. as I can have webOS and android? but yesterday install android OS and install web?

updates on the way?

Enviado desde mi XT1563 mediante Tapatalk
[TouchPad Development] rebel1699:
Im not entirely sure what you are asking. But if it is if you can install android, then install webos next to it, than no. Webos cannot currently be installed once it is removed and android installed. Webos must be already installed or fresh installed before android. You would have to wipe the entire device to reinstall webos, losing any android install. Hope I read your post correctly.
[TouchPad Development] joshua764:
Thank you. I clear as web install OS. I am not clear is how web install OS and android.

Enviado desde mi XT1563 mediante Tapatalk
[TouchPad Development] MikeFRG:
Forum Rule:

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
[TouchPad Development] joshua764:
Forum Rule:

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).
[TouchPad Development] trevor4706:
After all the discussion my post initiated regarding retention of WebOs I decided, what the heck, if all it takes is renaming the TPToolbox executable and swapping uImage.WebOs with it in /boot how hard can it be? if I don't like it, I'll just replace the TPToolbox file with the original WebOs one and everything will be back to the way it was. I followed the directions contained above , renamed the TPToolbox executable to uImage.TPToolboxV42, moved uImage.WebOs from /boot to storage), and pasted uImage.TPToolboxV42 into /boot. I rebooted and there the TPTB option was in moboot. Selected it and ... failed to boot. Doubled checked what I had done and couldn't find any mistake. One thing I did notice was the uImage.TPToolboxV42 file I had pasted into /boot was larger than the uImage.TPToolboxV42 file in storage from which I had copied it.

Decided to go back to WebOs, and repeated the process, replacing uImage.TPToolboxV42 with the uImage.WebOs I had moved into storage. Rebooted and selected WebOs in moboot. It failed to boot, and gave me an error message about wrong size. It appears in moving files from /boot to storage something changes the size of the file.

Everything else works as before. I can still boot into Nougat. My questions is, what did I do wrong?