Segment Fault error, customized JF 1.51 - G1 General

Hi,
I customized a JF1.51 with my own apps.
The first time everything gone well, but some apps were missing so
i managed to do another one with more apps.
It crashed during first start rebooting over and over.
I suspected an app causing the crash so I removed it and re-update the
phone.
This time everything seemed to working well but the terminal emulator as ls returned a permission denied and the same command in root mode returned a not found
I did a last try with some other apps, and the result was nearly the same as the command ls
returned a segment fault error in the terminal emulator su mode or not.
back to my orginal customized roms everything is working back but the apps are still missing.
So my question is, what could cause these problems?
Is there a size limit for the /system/app folder? (my whole rom is about 40,8Mo compressed)
please help
regards
Herc.

Hi,
So after some tests it really seems that the size matters .
So please can anybody explain me how I could enlarge my rom size without
causing problems after installation.
Bye
Herc. 8)

up
Still searching for an answer

Related

Random data usage

Hi guys,
Not sure what's happening on my Vodafone Magic...
Rooted it so i could install the HTC (htc_ime) keyboard. All that went fine all working ok. However since i've noticed my phone seems to be randomly using 5mbs of data every few hours. Can see this in netcounter. At one time i actually caught it happening, checked taskiller and closed everything that was running, yet the data still carried on transferring!!!
I've done a wipe to factory and set up again, just checked the phone before it was on 9mb, closed everything in taskiller, left for maybe an hour or two just looked and it now says 14mb.
Any ideas???
Could be the update problem I had. The phone downloads an update but fails to install (because the phone is rooted otacerts.zip does not match). If you catch it again you should be able to see the download progress in settings software update or the file being created in /cache. As soon as the download completes the update fails quietly and the cycle begins again. I'm looking for a stock ROM but for now I have copied /system/build.props from the ADB JFv1.51 ROM and is seems to have prevented the download from starting.
Roostlick said:
Hi guys,
Not sure what's happening on my Vodafone Magic...
Rooted it so i could install the HTC (htc_ime) keyboard. All that went fine all working ok. However since i've noticed my phone seems to be randomly using 5mbs of data every few hours. Can see this in netcounter. At one time i actually caught it happening, checked taskiller and closed everything that was running, yet the data still carried on transferring!!!
I've done a wipe to factory and set up again, just checked the phone before it was on 9mb, closed everything in taskiller, left for maybe an hour or two just looked and it now says 14mb.
Any ideas???
Click to expand...
Click to collapse
Turn off Data synchronization and see how it is. Maybe this is sync traffic
Downloaded JFV1.51 CRB43 ADP (10791) from the jesus freke blog.
adb pushed build.prop to system folder on phone, will leave it a few hours now and see if the data count randomly goes up or not, cheers!
Surely everyone should get this problem when they root? As i haven't put on a custom ROM or installed jesusfrekes stuff, just rooted it to install a keyboard!
Still doing it, went from 33mb to 37mb.
Could of done the build.prop wrong i guess, do you mind detailing the complete full procedure just in case?
Many thanks!
I had a very similar problem with my Magic although I don't know if it was downloading 5Mb chunks each time. It was on the stock firmware from Vodafone UK, can't remember if I had rooted at the time ... my Magic was rooted using these instructions: http://android-dls.com/wiki/index.php?title=Magic_Rooting
Just interested to see if you did the same? At one point I had noticed 200Mb of data downloaded within one week ... Voda only allows 500Mb per month in their 'fair use' policy.
I didn't ever fix this but wiped and flashed a different ROM, I've been OK since then. Unfortunately Netcounter does not tell you which apps have been doing the downloading!
I didn't have many apps installed but you know how it is, virtually every app in the market requires internet access for something or another.
Hmmm that sounds very similar to me st0kes.
Left Voda stock rom on, just rooted it to be able to install the htc keyboard and yep i used those instructions you linked to.
Think i will follow your lead and flash to a different ROM this afternoon, thanks for your reply!
How did you go flashing a different ROM Roostlick? Which ROM did you try (URL?).
I rooted my Australian Vodafone Magic the day i got it using the same instructions st0kes mentioned. I didn't replace the 'su' program since i didnt need it and seemed like an unnecessary security risk.
Data usage was fine (normal) for the first 2 weeks. Then it started downloading 4.5mb chunks every 2 hours.
Got close to my 1gig cap, so i turned off all data synchronisation. I have just received my bill today to find the cap was blown.... and that these 4.5mb downloads have continued.
Obviously looking to fix it, since i'm already 400mb through this months cap!!
edit: looked at Settings>About phone>System updates> and i can see "Android Update 1.5" waiting to be installed... no surprises its 4.2mb. I hit "download' on the update and it fails silently after downloading, giving a download prompt again.
Found some more info on the OTA updates in JF's blog here.
I'm currently testing the chmod solution:
./adb shell
chmod 000 /cache/download*
Hi rrfx,
I flashed the phone and installed the rom here:
http://forum.xda-developers.com/showthread.php?t=538633
Think it was the 3.6.8 release 4 version.
That seems to of fixed the problem
Roostlick,
You have done everything I did to solve the probelm except after I modified build props I did a factory reset and I have not hit the download button in settings->about phone->system updates since I did the factory reset. I still see the download available but it does not download any more.
Do you have the following info in settings->about phone (shows the build.props has been updated properly)?
Model No. = Android Dev Phone 1
Build = dream_dephone_.......
My phone is rooted as done here: http://android-dls.com/wiki/index.ph...=Magic_Rooting
B.
Hi guys, thanks for the information. I've fixed my phone now... for anyone else with this problem, and unwilling to use a 3rd party ROM... the path I followed from my post above.
JF's chmod 000 *.zip idea didnt work, my Vodafone Magic AU just kept downloading over the top. However using the SDK and logcat gave plenty of info
Code:
./adb logcat
I/SystemUpdateHelper( 63): Started a new update download: http://android.clients.google.com/updates/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip
D/InetAddress( 155): android.clients.google.com: 66.249.89.101 (family 2, proto 6)
D/InetAddress( 155): android.clients.google.com: 66.249.89.100 (family 2, proto 6)
D/InetAddress( 155): android.clients.google.com: 66.249.89.102 (family 2, proto 6)
E/SystemUpdateVerifierTask( 63): Verification for /cache/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip failed: java.io.FileNotFoundException: /system/etc/security/otacerts.zip
W/SystemUpdateHelper( 63): Download system update disappeared.
W/SystemUpdateHelper( 63): Download system update disappeared.
Specifically touching the exact filename in /cache and chmod'ing it 000 didn't work. Suspect the android downloader runs as root and seems to clobber the file anyway:
Code:
touch /cache/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip
chmod 000 /cache/signed-vfpioneer-CRC1-from-CRB17.7fbab120.zip
(didnt work)
I tried a bunch of other ideas, trawled through bits of the OS code etc. Tried manually downloading and forcing the OTA update.
What worked:
I tried replacing the build.prop file with JF's v1.51. If anyone needs specifics here happy to help.
Rebooted the phone etc, the build version didn't change and the downloads continued. I didn't want to do a factory reset! So left it like this for a couple of days.
This morning, checked the logs and the downloads weren't happening. Odd. Checked the build version and the "dream_devphone" seems to have been read from the build.prop file now! And in system updates "your system is currently up to date". Yay. So perhaps no need to do a factory reset.

Market enabler make Hero reboot

Hey!
My Hero reboot each time I try to fake another provider with Market enabler... It was working fine before...
Any clue?
BTW i'm running MoDaCo 2.9
Did you install NetCounter? There's a known bug where having NetCounter running will cause ME to react like this. Use TasKiller to stop the netcounter process, run ME, then restart netcounter.
At least that was my experience.
this worked for me:
Reinstall the app, and then reboot your mobile manual
Regards,
Luuk/Incomer
ps. Sorry for my bad english, i'm 15 years old and come from the Netherlands
incomer said:
this worked for me:
Reinstall the app, and then reboot your mobile manual
Regards,
Luuk/Incomer
ps. Sorry for my bad english, i'm 15 years old and come from the Netherlands
Click to expand...
Click to collapse
Worked! TY!
I've also uninstalled netcounter.
Or you can leave both installed and just run the fix uid option in the recovery module. That fixes it for me
I had the problem again. So, I've uninstalled ME and when I've tried to reinstall it, I cannot. The installation succeed, but when I try to launch it, I got a force close. Another thing, in the All app menu, I see ME, but with a generic icon and named "com.androidiani.MarketEnabler".
Any idea?
Resolved : I had a corrupted ext3 FS and got this error when I tried to install :
(adb logcat)
E/PackageManager( 133): Couldn't move package file to: /data/app/com.androidiani.MarketEnabler.apk
So I plugged in with adbshell and do a "ls -la /data/app/com.androidiani.MarketEnabler.apk" and I got this error : "Stale NFS file handle".
Si I've rebooted in recovery tool and do a Ext repair.
Solved the problem!
the only thing to do if hero restarts is to manually turn it off then turn it on and it will stop =)

Market won't stop force closing! - PLEASE HELP!

Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!
maybe you should try an other android rom ?
The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
SMS92 said:
Hi all,
Last night, out of the blue, every time I tried to download an app from the Marketplace I got the error "process com.android.vending has stopped unexpectedly" and a force close. I have no idea what would have caused this as everything was working fine up until last night, I can't think of any strange updates or anything.
Anyway, after some Googling I cleared the market cache and data as recommended but now I can't even open the Market app at all - well it opens, but force closes straight off the bat (I see the Android TOS in the background). I now get the process com.android.vending has stopped unexpectedly error on boot and whenever launching the market.
I've attempted to install a newer market.apk (current one is 1.82) but Android won't allow me.
The only other recommendations people have given on here to those experiencing this issue on dedicated Droid handsets is to either do a full format/install or to flash something via recovery (doesn't look like I can do this on my SD build)
A couple of months ago I was getting force closes on the calender app and someone sent me a droid.zip file which had a fsck.exe inside it which allowed me to repair my data.img which in turn fixed the problem. I've formatted my PC since than and lost the files and can't find them via Google, at least not one that'll run under Windows command prompt with "fsck.exe data.img" after placing the data.img in the same directory. Can anyone point me in the right direction? Or better still provide an alternative method for fixing this issue?
Using Darkstone's SuperRAM 1.5 Froyo build.
Many thanks!!
Click to expand...
Click to collapse
yz.hd said:
maybe you should try an other android rom ?
Click to expand...
Click to collapse
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
The best and quickest way to fix this is to use market.app from same build what u got.
So its mean u need to extract this particular app from the ROM and copy it to the /system/app
Or if u dont know how to extract it just ask in your ROM thread so someone whos know how to extract it and than can post it for download.
Click to expand...
Click to collapse
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!
SMS92 said:
Not really an option - The build I use is the most stable and one of the most widely used here on XDA (outside the Nand forum) and has been nigh-on perfect up until now (in daily use since before Christmas). I can't replicate how and why this happened so there's just as much chance of it happening on another ROM. Google suggests it's a common problem with the fix (for non rooted/savvy) people to factory reset their devices.
There's got to be a better way and I'm sure the crew here will find it!
Thanks - I'll look into doing it now. I've had no luck installing various Market apks though (with the default market disabled / cleared, etc.) so I'm unsure of the results!
Click to expand...
Click to collapse
This should help cos if u do it this way u actually not installing/reinstalling the app. u actually repleace the sys market.app for the original one from the ROM. So there is no way it will not work again if it was working before after u flashed the ROM.
I'm pretty sure it will do the trick, but also I may be wrong .
I had some issue on my ROM with cam.app and this proced. helped me.
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
FIXED! [Edit: not]
Here's what I did.
Downloaded THIS
Extract it to C:\Droid
Boot into Win Mobile and move your data.img in \Android\ into the \Droid\ folder on your PC.
Start > Run > CMD
type "cd c:\droid" (without quotes) to get into the directory you've created.
Type "e2fsck -f data.img" (without quotes) and say 'y' (yes) to all the errors you encounter. There will be dozens. When done you'll be notified the modified data.img has been saved.
Copy the newly modified data.img from \Droid\ to \Android\ on your device.
Boot into Android - things might be a bit slower/laggy at first.
All should be well!
Edit: This fix seems to have really slowed my phone down. It takes at least 2x as long to run stable on boot (i.e. stop lagging, load all background apps etc). I've imported my previous data.img over and will be trying the fix by Dom (above).
Edit2: And I'm now getting com.android.media force closes with the modded data.img! Music app won't work. Jesus!
ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Thanks for that Dom, I'll keep that in mind for next time! Great tip!
ricola7 said:
Hey,
you can try this (very simple):
1. Open terminal emulator
2. type "su" (without quotes) and hit enter
3. type "fix_permissions" (without quotes) and hit enter
4. wait until process is done and exit terminal
5. maybe reboot, but should be fine without reboot
This is a common way to fix force closes, so maybe this helps in oyur case too.
Greetz Dom
Click to expand...
Click to collapse
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Same here ...?
SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
Sent from my HD2 Jaws-MIUI
Did fix_permissions via the app ROM Manager and the Market force close still remains
How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.
SMS92 said:
Hey Dom, terminal tells me "fix_permissions: not found" when I run fix_permissions. Am I missing something? (I've su'd before hand) Guess Darkstone hasn't included this script in his rom?
Click to expand...
Click to collapse
rikardo1979 said:
Same here ...?
Sent from my HD2 Jaws-MIUI
Click to expand...
Click to collapse
Hmm, it seems that this script isn't inluded in your roms. But for you SMS92 it seems that it is another problem anyway.
If you wanna try sth. else see this:
http://all-google-android.com/google-android-forums/t-mobile-g1-modders/fix-permissions/
This is an "improved" fix permission tutorial which goes further than the command I posted above...quote from the link above: "fix_permissions is only intended for correcting ownership issues. It does not modify permissions, as is being requested."
In this post is a downloadlink for the advanced script so it doesnt matter if its already included in the rom...
@ricardo: see here if you still wanna try it: http://modmymobile.com/forums/567-motorola-backflip-general/556261-fix_permissions-script.html
Greetz Dom
johncmolyneux said:
How about getting a fresh copy of the ROM, and just keeping your data.img. It may not work, but it's surely worth a go.
Click to expand...
Click to collapse
It's a no-go I'm afraid.
So far the only thing that's worked is running the repairs on my 2gb data.img using e2fsck on my PC, but this in turn created a load more problems (com.process.media started force closing and the rom seemed to be much slower)
Will try some more suggestions tonight.
if your running gingerbread make sure the app is installed on the phone not the sd
I'm also suffering from this issue it started for me when an automatic update downloaded (which I didn't install) I will see if any of the above fixes work for me & if not I will start with a fresh copy of the ROM. Have to admit I have barely used winmo since I started using this build!
I have the same problem using froyo 2.2
I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App
robdee102 said:
I've had the same problem, just did a totally fresh install, ok now
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
Any chance you could walk me through the steps you took for a fresh install? I am at my wits end with the FCs and a mount/partition error. Here is my setup:
HTC Hd2 Leo
HTC Desire
Android 2.2.1
Mod darkstone SuperRAM FroYo v1.5
Build FRG8
I am up for a new ROM or whatever to get my phone back in order. Thanks so much!
BOYPPC-SHIFTPDA v.37 Market Force Closes
BOYPPC-SHIFTPDA v.37 Market Force Closes
Please Help my Market is constantly force closing on me the error is:
Sorry!
The application Market
(process com.android.vending)
has stopped unexpectedly.
Please try again.
then it has a force close button.
I would really like to install some apps with the market but
every time I try and use the market I get this error,
I am running the BOYPPC-SHIFTPDA v.37 ROM
Please Help Me

[Q] Motoactv Workout app Crash Force Closing when BLE Polar H7 Paired

I'm pretty sure I had this working on the NA Rom, I'm now using the Stock EU 8GB Rom and the workout app wont start when my HRM is paired..
It crashes and force closes.
However the HRM does pair, and I can see my Heartrate displayed when I use the Heart rate clock face.
Anyone experienced this ? Any fix anyone knows of ?
scoobdriver said:
I'm pretty sure I had this working on the NA Rom, I'm now using the Stock EU 8GB Rom and the workout app wont start when my HRM is paired..
It crashes and force closes.
However the HRM does pair, and I can see my Heartrate displayed when I use the Heart rate clock face.
Anyone experienced this ? Any fix anyone knows of ?
Click to expand...
Click to collapse
Reading Moto Support forums, looks like it may have stopped working in ROM upgrade to 1.7.xx Does anyone have 1.6.13 for example ?
Fix for pairing with Polar H7
Hi scoobdriver,
This problem is related to versions 1.7.x of the MotoACTV firmware. There are several posts in the Motorola forums, but no official answer from Moto for the last two years. Up to now, the only solution if you wanted to pair your H7 with the MotoACTV was to revert to 1.6.12 (the last rom working with the H7). Luckily, ClearD root tool can do that for you ("return to stock" functionality flashes 1.6.12). Please read the instructions carefully before you try to root your device if you choose to follow this path.
In my case, I decided to follow a different path and go into the code for comparing both 1.7.10/12 and 1.6.12 (the last working rom). I found out that some dev at Moto thought that a null pointer check was not necessary when setting up the activity screen, and this caused an uncaught null pointer exception and the already famous crash "Sorry. The application Workout (com.motorola.gault.activity) has stopped unexpectedly. Please try again." Surprisingly, it had nothing to do with BLE protocol or with any compatibility problem with Polar implementation/interpretation of BLE.
I have fixed and repackaged the conflictive apk (attached); after several tests and workouts it has not given me any problems. If you want to test it, you can update you MotoACTV to the latest rom (1.7.10/1.7.12) with MotoCast, root it (read the available excellent tutorials on how to do it, if you need), download the attached file and copy it to the device with adb:
Code:
adb remount
adb pull /system/app/Workout.apk Workout_backup.apk # (if you want to backup your original apk)
adb push Workout.apk /system/app/
adb shell chmod 644 /system/app/Workout.apk
I know it could be packaged in a more friendly (non-adb) way, but I want to make sure it really works before going on. I have tested it with ClearD rom, but it should also work for a stock rom. Anyway, be warned that rooting and playing with adb is at your own risk, as usual. In any case, If you test the modified apk and you get any undesired result, do not hesitate to come back to this post.
J*R said:
Hi scoobdriver,
This problem is related to versions 1.7.x of the MotoACTV firmware. There are several posts in the Motorola forums, but no official answer from Moto for the last two years. Up to now, the only solution if you wanted to pair your H7 with the MotoACTV was to revert to 1.6.12 (the last rom working with the H7). Luckily, ClearD root tool can do that for you ("return to stock" functionality flashes 1.6.12). Please read the instructions carefully before you try to root your device if you choose to follow this path.
In my case, I decided to follow a different path and go into the code for comparing both 1.7.10/12 and 1.6.12 (the last working rom). I found out that some dev at Moto thought that a null pointer check was not necessary when setting up the activity screen, and this caused an uncaught null pointer exception and the already famous crash "Sorry. The application Workout (com.motorola.gault.activity) has stopped unexpectedly. Please try again." Surprisingly, it had nothing to do with BLE protocol or with any compatibility problem with Polar implementation/interpretation of BLE.
I have fixed and repackaged the conflictive apk (attached); after several tests and workouts it has not given me any problems. If you want to test it, you can update you MotoACTV to the latest rom (1.7.10/1.7.12) with MotoCast, root it (read the available excellent tutorials on how to do it, if you need), download the attached file and copy it to the device with adb:
Code:
adb remount
adb pull /system/app/Workout.apk Workout_backup.apk # (if you want to backup your original apk)
adb push Workout.apk /system/app/
adb shell chmod 644 /system/app/Workout.apk
I know it could be packaged in a more friendly (non-adb) way, but I want to make sure it really works before going on. I have tested it with ClearD rom, but it should also work for a stock rom. Anyway, be warned that rooting and playing with adb is at your own risk, as usual. In any case, If you test the modified apk and you get any undesired result, do not hesitate to come back to this post.
Click to expand...
Click to collapse
Thank you so much for this J*R! I just bought a motoactv just to use it with BLE accessories and none were working until I applied your APK. Straight forward very easy to follow instructions. Everything is working now.
I can't believe Motorola is not doing anything about it. Even if it's a discontinued product, it doesn't have to be a useless one....
rocos
not working
Hi and thank s for your work.
i m cleardroid rooted (1.7.10) and put your workout.apk fix on my actv...but still not ok. (Same msg: workout... crash....try again later)
First time, when i try to backup my original workout.apk in adb , the file was not founded on my actv. I push whatever your apk in system/app and everything is ok in adb. But nothing change for my problem when i try to launch a jogging.Is it possible that my actv system path is different of your example? (System/app)
i dont know if is it possible to explore the system file of my actv, at least for know where path is my original workout and replace it by your fix.
thank s man and sorry for my ugly english...i m french.

Slow note pro solved, fstrim wasn't running

Like many here my now ageing note pro has been getting slower with age to the point of being unusable. Intermittent freezes were frequent, often when typing on the keyboard with up to 10s lag on each key entry. This is running unrooted on stock rom v5.0.2. By coincidence an ssd in my pc was also dying and it made me look at how TRIM of the flash memory was handled on the note pro. Although android is supposed to run it regularly it had not been run for 5 years.
If this is affecting you, you can check by looking at the datestamp on /data/system/last-fstrim. You do not need to root, you can check via 'adb shell' and do a ls -l in that directory without viewing the contents of the file. If that file is old then automatic trimming is not working and you'll need to root and run it manually. Once rooted the command to trim on the last stock rom was 'vdc fstrim dotrim' but if you are running a different rom the command may be different. Might be easier just to install the trimmer app but that still needs root.
I've seen many here mention how new roms have seen great speed improvements. TRIM can happen automatically on volume wipes so it may be contributing to the speedups seen there.
Mine is completely transformed. As fast as new again.
As I understand, not have to do this if reset to factory defaults?
My Note pro p905 acting just like that, very slow and sluggish. I reset it but no change, it remains slow, I have to wait couple of seconds to execute the command when press the button.
Any other suggestions what to try?
I haven't restored anything, just reset to factory and leave it to settle down, it's barely usable. Have Android 5.0.2 on it.
Sorry late replying, I'm an infrequent visitor. My understanding is that a reset to factory defaults should do a trim but then the stock os should do that regularly too. As its a while since you did it I'd check the timestamp on the fstrim file. If its not run then you'll need to root and run it manually. To avoid it happening again I installed a new rom in the end but you should be able to root, trim, unroot to preserve the existing os.
My problem is solved, after couple of days and couple of charging-discharging cycles, tablet become fast again.
Maybe it's because tablet isn't used for a long time and battery was completely dead, after couple days it's back to normal.
Anyway, thanks for reply.
For anyone with similar issues this may still indicate that fstrim is the cause of the problem. Reset to defaults may fix bug and os trigger to run fstrim is a recharge cycle if its not been recently run.
Had the exact same issue
End up deploying rom
Yesterday
My P905 is android 10 now..
Looks new and behave like new tab
The only issue is screen rotation.
Sent from my SM-N975F using Tapatalk
There is Trimmer fstream app on Playstore..I use it regulary and it done job well.
Hello,
thanks to devbod for the advice.
I checked my last-fstrim file and it was very old (2015-06-30).
So I rooted my SM-P905 (using CF-auto-root), then connected with adb and executed (after 'su') 'vdc fstrim dotrim' as suggested.
The command returned an OK code (200).
After doing that the last-fstrim file still had the date set to 2015-06-30.
So I checked the log with 'logcat -d | grep fstrim' and it reported:
I/fstrim ( 247): Starting fstrim work...
I/fstrim ( 247): Invoking FITRIM ioctl on /data
I/fstrim ( 247): Trimmed 0 bytes on /data
I/fstrim ( 247): Finished fstrim work.
I found in this thread that if fstrim says "trimmed 0 bytes" then it means that TRIM is not working for some reason.
What could be the reason?
PS: I have Android 5.0.2 and I think device is not encrypted (encrypt option is still 'active').

Categories

Resources