yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] AuxLV:
Did you specify full path to fstrim binary?
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

This is the script I created and tried to run:

#!system/bin/sh

fstrim -v /data

fstrim -v /cache

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] backfromthestorm:
You need to point the script to where fstrim is!
[Samsung Galaxy Nexus] ph4zrd:
AW: Nexus Storage Performance Over Time & TRIM

Can you post the output of 'mount' from your encrypted device? Maybe a slightly different workaround is possible.
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

I thought it was in system/bin.. where should it be?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AuxLV:
fstrim is NOT a part of Android. Otherwise we did not have this problem (: It is located in /data/data/com.grilledmonkey.lagfix/files after you install LagFix and run it once.
[Samsung Galaxy Nexus] mfbgeo:
Yes here you go:

I actually flashed it back to stock yesterday.

But if there is a solution for the encrypted device then I'll go for it :)
[Samsung Galaxy Nexus] ph4zrd:
So we need discard support in dm-crypt, which was added in Linux 3.1 [Source]

No idea if it was ported to the Android 3.0.x kernel, though.

Will look into this when I have enough free time.
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

Oh yeah, that makes sense! :p

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

Sorry but I may need some other help.

I copied fstrim to /system/bin, set its permissions to 777, then created this init.d script:

#!/system/bin/sh

fstrim -v /data

fstrim -v /cache

It doesn't seem to achieve the desired effect, though it should have run. Any help would be much appreciated.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AuxLV:
Re: Nexus Storage Performance Over Time & TRIM

Does your script have execute permissions? Maybe you also need to add su before fstrim.
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

Init.d scripts should not need su to run as root should they? I tried anyway but no success.. Nevermind. I guess that's a sign that I shouldn't try complicated stuff! XD

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] AuxLV:
Re: Nexus Storage Performance Over Time & TRIM

So what about exec permission on script?
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

Permissions are set to rwxr-xr-x

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] chrone:
sorry can't help you much, Jar3112. this is way out of ma league. hahaha :D
[Samsung Galaxy Nexus] geoffcorey:
Re: Nexus Storage Performance Over Time & TRIM

First, name the file a distinctive name (such as 86fstrim).

Make sure it is in /system/etc/init.d/

Make sure perms are: rwxr-xr-x

Reboot phone, and save boot up logcat to a text file: adb logcat > logcat.txt

Look in logcat file for 86fstrim (or whatever distinctive name you gave it)

Alternative:

Connect phone to adb, try to execute the init.d script, and read errors.
[Samsung Galaxy Nexus] chrone:
Re: Nexus Storage Performance Over Time & TRIM

Whoa what a post, could you attach the log in .txt attachment next time?

Btw, skimming the log, i could not find any fstrim.

Sent from my Nexus 4
[Samsung Galaxy Nexus] Jar3112:
R: Nexus Storage Performance Over Time & TRIM

Yes, sorry, I couldn't attach the file via xda app. I'm gonna try with adb.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] backfromthestorm:
If you want an easy way....

Put fstrim in system/bin.

set perimssions.

put script in init.d -

set permissions

Thats it.

If you want to test it, execute the file with root explorer, (long press the file and there is an option to run the script).

You will get a log of amount trimmed.

fstrim file for system/bin -- https://www.dropbox.com/s/wsjwnp9imhurb6s/fstrim

init.d script - https://www.dropbox.com/s/cetb2240savt8rf/99trim
[Atrix 4G Q&A, Help & Troubleshooting] boonemeat:
I am currently running the awezome rom from uriel. Here is what is going on and what I've tried. I am unable to erase the internal sd either by file explorers or using windows. Everything says it is deleted but returns after a reboot. Ive used fastboot to erase every partition and reflash stock images and it still boots up to the same rom. I tried using rsd lite by flashing an sbf, again the same awezome rom boots up. Apps that I install uninstall after a reboot as well. The recovery will not flash any new roms or format any of the partitions such as system or data or the sd cards. I don't know what to do
[Atrix 4G Q&A, Help & Troubleshooting] Backfiah:
Have you tried re-flashing the recovery?
[Flipout and Charm General] grubbyfoot:
Anybody get apps 2 SD to work on the charm?
[Flipout and Charm General] 'cooleagle':
Thread moved to the General section.
[Motorola Droid RAZR] Ice_Man29:
Reading***** Sorry for the miss spell up there..

First let's get all this out of the way.

XT912 stock/rooted Android 4.0.4

safestrap 3.05 Black Widow Ics-6.16.214.spyder.deodex.final

Now when switching from my stock rom (non-safe mode) to BW ics (safe mode) the battery level is way off.

Did I forget to wipe cache or delvik cache somewhere?

Any ideas on how to fix this?
[Motorola Droid RAZR] heblu:
after the battery runs dead, with the phone off, charge the battery till 100%.

then, with the cable still plugged, enter the recovery and make a "wipe battery stats"

hit reboot, unplug the cord and use the phone normaly
[Motorola Droid RAZR] btragic2011:
cant find wipe battery stats on safestrap 3.05..any other way?
[Motorola Droid RAZR] Ice_Man29:
Well there might be a better way to do so but this is how I ended up fixing my battery icons.

I went into the play store and downloaded this app: SD Maid - System cleaning tool
[Motorola Droid RAZR] Dark3n:
Wiping the battery stats (batterystats.bin file) will have no effect on the recognized charge level.
[Motorola Droid RAZR] btragic2011:
ya i second that...i have 3 roms installed plus miui as stock and they all have different battery life...even the safestrap is different than every rom installed...plus when phone is off and charging it wont charge past 20 percent...need to fix this asap please help
[Motorola Droid RAZR] Lokimitsu:
Have you tried apps like "Battery Calibration" from the Play Store?

Empty your battery, then charge it and start Battery Calibration, wait until it

plays the sound to notify you that the battery is really fully charged, then press "Calibration".

You need root for this!
[Motorola Droid RAZR] KMSAlex:
You can wipe the file with this app.

https://play.google.com/store/apps/...yLDEsImNvbS5uZW1hLmJhdHRlcnljYWxpYnJhdGlvbiJd

EDIT: Just noticed the person above me suggested looking this up in the play store.... well i saved you a search. :p
[Motorola Droid RAZR] btragic2011:
thanks im gonna try it now..will report back
[Motorola Droid RAZR] KMSAlex:
Was anyone talking/arguing with you?

Do you have positive info for this tread?
[Motorola Droid RAZR] Ice_Man29:
rivulet treasyl

Yeah that was useless. I reported the post already.
[Motorola Droid RAZR] O_G:
Thread Cleaned​

Do not post in a argumentative way, there is no need. We are all here to help each other out, not get into arguments. If you dont have anything constructive to add to the thread, Dont post!​
[Motorola Droid RAZR] btragic2011:
question do i charge it fully while its off or turn it on once its at 5% and start battery calibration
[HTC Vivid, Raider, Velocity] xport7:
Hey guys I just traded a guy my S2 for the HTC Vivid. I played with my wife's vivid and really like the stock OS (I believe she is running Gingerbread) with HTC sense. I was going to look into going to ICS with root (via this rom: [STOCK ROM] AT&T ICS, de-odexed, zip-aligned, rooted, bloated (For chefs or whoever) - [N]) I'd really LIKE to use that ROM, however, I have NO CLUE what I am doing. All of this is Japanese to me... I got my phone into hboot and seen "Factory Reset" does this literally mean take miui off (sorry, forgot to mention that before, the phone is already rooted, unlocked, etc.) and has miui on it (I guess I said that right?) - Honestly, this looks like iPhone... and I despise iPhone (my reason for using android) - I hate everything the iPhone offers (or lack thereof) and don't for one second want my android to LOOK like an iPhone lol. So basically does the factory reset take it back to stock and "unroot" ?

or if someone could very noobishly walk me through installing that aforementioned ROM with ICS and root, I'd be more than appreciative!
[HTC Vivid, Raider, Velocity] xport7:
So I tried doing it (installing the rom I downloaded with rooted ICS bloated) via the clockworkmod recovery and it boots up to HTC splash screen and stops. Just stays there -.-

Any help?
[HTC Vivid, Raider, Velocity] wwrepapa:
help with relock and unroot

if you go to the development section and look at the HTC Holiday superguide post at the top of the page? I believe all your questions will be answered. (opt. 6 Return to stock...locked bootloader, unrooted, etc) From there start at the beginning of the guide to do whatever you want.
[HTC Vivid, Raider, Velocity] eddied042092:
Did you actually hit the factory reset from the hboot menu?

i heard you werent supposed to do that..

if youre still having trouble i can sort of help you out, ive messed with my vivid quite a bit.
[HTC Vivid, Raider, Velocity] xport7:
I checked it out and it said phone must be stock and all. I am not stock, I want to go BACK to stock and I haven't a clue what to do. If there is a way I hook the phone to my PC and do it (seen something about doing it via command prompt?) I'd be grateful for any help. I wouldn't mind using the rooted ICS one that I found but if I can just go back to stock (with my wifi working again and where it'll charge when it's dead) I'll be fine.
[HTC Vivid, Raider, Velocity] Bigtjmc:
You will need to relock the bootloader , then run the stock ruu file and it will be the stock ics .

Only thing is in hboot it will say relocked and if its s-off that will stay also.
[Galaxy Note II Q&A, Help & Troubleshooting] Danielfr:
Hi,

I have stock Rom and Rooted. I can't received any calls anymore because I am receiving the message:

process com.android.phone has stopped but I still can call.

I can't reflash because I have stock Rom.

Any help please.

Daniel
[Galaxy Note II Q&A, Help & Troubleshooting] gee2012:
I would do a data factory reset in settings, backup and restore mate. That usualy solves the problem.
[Galaxy Note II Q&A, Help & Troubleshooting] Danielfr:
Thank you. It worked but I am surprised because "process com.android.phone" is a system app and with a data factory reset yoou don't reser

System apps.

Daniel
[Galaxy Note II Q&A, Help & Troubleshooting] gee2012:
If this happens, the phone.com in this case is corrupted by some event. Restoring gives you the original settings of system apps.
[Galaxy Note II Q&A, Help & Troubleshooting] Danielfr:
Yes you are right: it came from a program to restore you ringtones and apparently the program is messing the contacts database.

(http://xdaforums.com/showthread.php?p=33667275#post33667275)

I had it again after having used this program. I did a wipe of my contacts database and my phone works again.

Daniel
[TouchPad Q&A, Help & Troubleshooting] SCWells72:
I've been running CM9 on my 16GB Touchpad for quite a while. I flashed the newer version with camera support and again, that went well. Then I decided to flash AOKP and something happened and I can't figure out how to get back into a good state. Basically moboot comes up and shows options for webOS, CM9, AOKP, CWM, and webOS Recovery. None of the OSes will boot including webOS and the two Android entries. When I try to boot into webOS, it just shows the HP logo indefinitely. When I try to boot into either of the Android options, it just reboots after showing the splash screen briefly. When I boot into CWM it has errors like "E:Can't mount /cache/recovery/command" and I can't mount any of the other filesystems (/sdcard, etc.).

So far I've tried running ACMEUninstaller but it errors out saying "Cannot start LVM, aborting! Please reboot". I've tried "wipe data/factory reset" from CWM, but that shows a series of errors similar to the one above saying it can't mount the filesystems. I've tried to use webOS Doctor (both 3.0.0 and 3.0.5) to reimage the entire device but it says "Failed to reboot device. Contact support." I've tried these instructions:

http://xdaforums.com/showthread.php?t=1426244

but after running novacom with that uImage, it doesn't go to a command prompt. As with webOS above, it just shows the HP logo indefinitely.

I've exhausted the options I could find. Any thoughts on how I might be able to get things back into a usable state?

UPDATE: I tried the linked process above again and made more progress. However, now I'm running into the same problem described here:

http://xdaforums.com/showpost.php?p=32774659&postcount=129

UPDATE 2: It looks like this is exactly what's going on with my Touchpad:

http://xdaforums.com/showthread.php?t=1483066&page=4

Anyone know how to get past this?
[TouchPad Q&A, Help & Troubleshooting] chicle_11:
Read this thread : http://xdaforums.com/showthread.php?t=1426244&page=12

Pay special attention to page 12. It will show you how to do it without using novaterm. Also towards the beginning of the process you'll get asked a lot of questions, just answer yes to all.

Good luck.

Hold power and volume up at the same time, this will get you into correct mode (recovery).

Edit : plug your tablet in for a few hours before trying the process.
[TouchPad Q&A, Help & Troubleshooting] SCWells72:
Thanks. Unfortunately this is actually the process I'd been trying to follow earlier and I get the exact same results through "novacom -t open tty://" that I do through novaterm, basically it fails trying to re-create the volume group 'store':

root@webos-device:/# lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
No physical volume label read from /dev/mmcblk0p14
/dev/mmcblk0p14 not identified as an existing physical volume
Unable to add physical volume '/dev/mmcblk0p14' to volume group 'store'.

If I continue working through the commands listed on that page, they pretty much all fail since they expect this volume group to exist. Any idea how to get around this issue?
[TouchPad Q&A, Help & Troubleshooting] SCWells72:
Okay, I just made significant progress on this! After quite a bit of googling I found the following thread:

https://answers.launchpad.net/ubuntu/+question/15044

in particular the following from the fourth post:

My ad hoc idea: dd if=/dev/zero of=/dev/sda1 bs=1024 count=1000
...
root@299903:~# pvcreate /dev/sda1
Physical volume "/dev/sda1" successfully created

By adding the following two steps to the process outlined at http://xdaforums.com/showthread.php?t=1426244, I have webOS Doctor 3.0.0 past the dreaded 8% mark now!!!

dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14

Once that completes, I'll let it update to 3.0.5 and then reinstall Android, and what I feared was going to become a brick should be back into usable shape!

I hope this helps others who have encountered this same issue! Thanks again for the help!

UPDATE: I can now confirm 100% that this works. I'm installing the latest CM9 nightly to my 16GB Touchpad right now!
[TouchPad Q&A, Help & Troubleshooting] chicle_11:
Glad you got it going.

Thanks for sharing your solution, I'm sure it'll help others.
[TouchPad Q&A, Help & Troubleshooting] amkaos:
really glad to hear that you got thru this..

i get spooked when ppl who know what theyre doing get hung up..

good work
[TouchPad Q&A, Help & Troubleshooting] brandonmarkb:
I can't thank you enough for those 2 extra commands. I was able to get through and run the original batch of commands without a problem. I'm now waiting for my TP to charge enough to run the 3.0 doctor. I'm still not out of the woods yet, but I feel like I'm definitely getting there. I'll update once I get enough charge.

But regardless, thank you, thank you. I had given this thing up for a brick, but now there's some hope.

EDIT/UPDATE: This totally worked!! You just saved my TouchPad. Thank you, thank you!
[TouchPad Q&A, Help & Troubleshooting] SCWells72:
Glad to hear!!! Yeah, I was feeling the same way, so I totally understand. Mine has been running GREAT ever since going all the way through this, and I even updated it for the latest Jellybean ROM yesterday which is coming along very nicely! Please let us know if you hit anymore obstacles, or even better, if you get all the way back up and running!
[TouchPad Q&A, Help & Troubleshooting] brandonmarkb:
I updated the post above, but just so no one misses it, I'm back up and running. The 3.0 doctor went flawlessly and I'm staring at WebOS right now. I'm planning on reinstalling Android here in a few minutes. Again, thanks so much! I'll come back with any questions, but for now I'm in the clear.
[TouchPad Q&A, Help & Troubleshooting] jakkzen:
I would just like to say THANK YOU to SCWells72 and everyone else who is trying to help with this "Brick" issue. I was able to repair my 32gb Touchpad that would time out at 8%, with the help of the 2 extra codes.

I would like to point out something that I ran into. When I ran the 2 extra codes I bypassed the "lvm.static vgremove store" code and went right into SCWells72 codes. So, for me I did this....

lvm.static vgscan --ignorelockingfailure

lvm.static vgchange -ay --ignorelockingfailure

dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000

lvm.static pvcreate /dev/mmcblk0p14

lvm.static vgscan --ignorelockingfailure

lvm.static vgchange -ay --ignorelockingfailure

lvm.static vgcreate -s 8M store /dev/mmcblk0p14

lvm.static vgscan --ignorelockingfailure

lvm.static vgchange -ay --ignorelockingfailure

lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store

lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store

lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store

lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store

lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store

lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store

lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store

lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store

lvm.static vgscan --ignorelockingfailure

lvm.static vgchange -ay --ignorelockingfailure

mkdosfs -f 1 -s 64 /dev/store/media

Then I proceeded to reboot into recovery and use webOS Doctor 3.0.0 to restore my Touchpad.

I hope this helps those people stuck with the same issue.
[TouchPad Q&A, Help & Troubleshooting] xtremetactics:
Thank you guys. Saved me I never thought I was gonna get this thing to work again. XDS members always to the rescue. Thanks everyone that had anything to do with this
[TouchPad Q&A, Help & Troubleshooting] dheyden:
Thanks so much that worked you saved my touchpad

I have tried and tried everything and this worked
[TouchPad Q&A, Help & Troubleshooting] SCWells72:
I'm so glad that this seems to be working for so many people!!! This community has given so much to all of us, so it's nice to be able to give a little back, even if it's basically just standing on the proverbial shoulders of others and stumbling into something that actually worked...
[TouchPad Q&A, Help & Troubleshooting] jakkzen:
Hey, I'm glad my post helped you.
[TouchPad Q&A, Help & Troubleshooting] McBeanTIO:
Think my TP is bricked as well. installed the recent CM10 preview, and hit an infinite boot loop. When I tried the reboot the screen went black, and now I can't get a thing to trigger on the device. No reboot, no blinking command buttons, no USB cable recognition on my PC - just an ice cold black touchpad.

I'm thinking about leaving it sit for a week and let the power completely drain. Maybe coming back to reboot it later, I'l be there for a power signal and get into TWRP or something. Other idea is to leave it plugged in for a few hours, and see if I can force a reboot.

Any ideas out there on this one?

--McBean
[TouchPad Q&A, Help & Troubleshooting] ScottBroker:
Ok I got to run the webOSdocotr, but I get stuck at 8%. I cannot figure out what to do. What did you do exactly to fix this???
[TouchPad Q&A, Help & Troubleshooting] ScottBroker:
I did something, and now TWRP wont boot up either. Just the HP logo. I get it into recovery, and try AC%. A webosdocotr, and boots me out at 8% MEuninstaller and it says abort LVM not there.... Any suggestions?
[TouchPad Q&A, Help & Troubleshooting] JohnKoffee:
Same problem here with a 16GB Touchpad. But, when I input:

lvm.static vgremove store

NOVATERM says:

Volume group "store" not found

What can I do ?

Edit: found out !
[TouchPad Q&A, Help & Troubleshooting] spunout62:
Thank you so much

Dude....you should have a donation button set up. I've been struggling with my TP for 3 days with no luck. Then I found your post here, and those 2 extra lines of code you shared saved the day. I have flashed cyanogen at least a dozen times with no problem, then I tried some hybrid combo of cyanogen and aokp...boy that was a mistake. I'll stay with jcsullins from now on for sure. Thanks for sharing, I'm sure you have helped a lot of people with this.
[TouchPad Q&A, Help & Troubleshooting] sstar:
Can you say what hybrid you flashed so that I or others can stay away from it if we wish . Or pm.
[TouchPad Q&A, Help & Troubleshooting] akhenax:
Thank you

This was right on the money jakkzen! THANK YOU.Your post actually made sense of all the previous posts. My head is hurting from the countless google searches, but alas I am restoring my Touchpad.

There should be way to make this into a script, with verbose output. I may look into this to help others.
[TouchPad Q&A, Help & Troubleshooting] jrein:
When I try to run the commands in Novaterm I get the following message.

Similar messages occur when trying any of the Novaterm commands outlined in OP.

Anyone know what is going on?

Thanks.

root@webos-device:/# lvm.static vgscan --ignorelockingfailure

Reading all physical volumes. This may take a while...

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Volume group "store" inconsistent

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

WARNING: Inconsistent metadata found for VG store - updating to use version 13

/dev/mmcblk0p14: lseek 31228690432 failed: Invalid argument

Automatic metadata correction failed
[TouchPad Q&A, Help & Troubleshooting] Mazdav1:
Hi everybody,

I've got similar trouble ; touchpad seems bricked...

No way to boot on webos or android.

I perform this process : http://xdaforums.com/showthread.php?t=1426244

but no good result : all the process in novaterm matches, but webos's installation stopped at 50%.

Then, I tried your process and again, novaterm's process is ok, but webos's installation stop at 50%.

Could you please help me ?

Thanks for reading.
[TouchPad Q&A, Help & Troubleshooting] benpeleg:
hi, i tried the entire thing, but unfortunately the webosDR fails at 92%. any suggestions?

thanks for all of your time!!
[TouchPad Q&A, Help & Troubleshooting] johnawesley:
You're the Man!

Thanks for posting this. I bought a excellent condition HP Touchpad 64Gb White from Ebay for $162.00 as it was stalling at the boot screen for the seller. Thanks to you I got it going and it's back and into WebOS. Now it's worth much more than I paid for it as these guys are rarer. Thank you, you're the Best!! Thanks to everyone!!

:good:
[TouchPad Q&A, Help & Troubleshooting] jiran sheikh:
sir i done this process succesfully but now my device stuk at 12 % help me sir plzzz
[TouchPad Q&A, Help & Troubleshooting] kulkat:
Make sure you are using the latest novacom drivers, and they are in your %path%.
[TouchPad Q&A, Help & Troubleshooting] zyxwvu42:
You helped me out about a year after your post, finally got past 8% on WebOS Doctor, and past the 12% too, looks like its gonna work this time. Thanks for saying to take out the vgremove that was apparently my problem.