Related
Since I installed JPK on a test phone after claims that the RFS related lag has been fixed.. well.. I'd like to share my impressions:
- I have installed approx 100 apps after the flash (flashed / wiped / factory reset btw)
A this point, the phone while slightly slower than one with Voodoo is pretty fast
A few days later, it's still good enough.
- 5 days later, lag starts to be felt, and it's stronger every next day until it becomes annoying to use
That's exactly the same experience as I had on various Eclair roms without any lag-fix. I also had this on JP3 (early Froyo).
So yeah. I looked into the /init binary from samsung and it's supposed to make some file system checks from time to time when you restart the phone, but it does not appear to really carry on with that.
So I ran the checks myself:
- you need a rooted phone, and adb or a terminal
- find all RFS partitions:
$ su
# mount|grep -i rfs
- kill all processes, go flight mode and remount them read-only
$ su (if you're not root.. not going to repeat it again for subsequent commands)
# kill -9 <pid> of anything that use the patrition
# mount -oremount,ro /dev/block/....
- check the RFS filesystem and correct errors
# /system/bin/fsck_msdos -p -f /dev/block/....
Surprise, a million of RFS errors fixed such as:
/path/to/file starts with free cluster FIXED
Cluster XXX continues with cluster XXX in FAT 0 but is marked free in FAT 1 FIXED
Detected cluster chain loop head XXXX for p XXXX FIXED
FSNext block XXX is correct NumClusters XXX FIXED (weird one)
No LOST.DIR FIXED
Lost cluster chain at cluster XXX YY clusters lost FIXED (prolly lost files/data here!)
Repeat for each partition
reboot the phone at the end
SURPRISE! It doesn't lag much anymore.
Use the phone an hour, do the check again and you will see it's already full of errors.
Conclusion:
RFS is bugged (we knew that didn't we) but it looks like it's fixable, if ever Samsung figures out what is corrupting the file system exactly (it's closed source so we can't really find out easily)
It might be possible to figure it out by looking at VFAT sources too.
I would be very interested to see if that fixes the lag for everyone or if i'm an isolated case and all my RFS partitions are on bad hardware or if it's really software corruption as I am guessing
Small disclaimer:
im not responsible for any data loss etc. no warranties etc. fixing file system even readonly might cause data loss due to the bugs in RFS. you've been warned lol.
My God,
I think a lot of eyes will be on the BOUNTY
Could someone just create an app that does this?
bilboa1 said:
Since I installed JPK on a test phone after claims that the RFS related lag has been fixed.. well.. I'd like to share my impressions:
- I have installed approx 100 apps after the flash (flashed / wiped / factory reset btw)
A this point, the phone while slightly slower than one with Voodoo is pretty fast
A few days later, it's still good enough.
- 5 days later, lag starts to be felt, and it's stronger every next day until it becomes annoying to use
That's exactly the same experience as I had on various Eclair roms without any lag-fix. I also had this on JP3 (early Froyo).
So yeah. I looked into the /init binary from samsung and it's supposed to make some file system checks from time to time when you restart the phone, but it does not appear to really carry on with that.
So I ran the checks myself:
- you need a rooted phone, and adb or a terminal
- find all RFS partitions:
$ su
# mount|grep -i rfs
- kill all processes, go flight mode and remount them read-only
$ su (if you're not root.. not going to repeat it again for subsequent commands)
# kill -9 <pid> of anything that use the patrition
# mount -oremount,ro /dev/block/....
- check the RFS filesystem and correct errors
# /system/bin/fsck_msdos -p -f /dev/block/....
Surprise, a million of RFS errors fixed such as:
/path/to/file starts with free cluster FIXED
Cluster XXX continues with cluster XXX in FAT 0 but is marked free in FAT 1 FIXED
Detected cluster chain loop head XXXX for p XXXX FIXED
FSNext block XXX is correct NumClusters XXX FIXED (weird one)
No LOST.DIR FIXED
Lost cluster chain at cluster XXX YY clusters lost FIXED (prolly lost files/data here!)
Repeat for each partition
reboot the phone at the end
SURPRISE! It doesn't lag much anymore.
Use the phone an hour, do the check again and you will see it's already full of errors.
Conclusion:
RFS is bugged (we knew that didn't we) but it looks like it's fixable, if ever Samsung figures out what is corrupting the file system exactly (it's closed source so we can't really find out easily)
It might be possible to figure it out by looking at VFAT sources too.
I would be very interested to see if that fixes the lag for everyone or if i'm an isolated case and all my RFS partitions are on bad hardware or if it's really software corruption as I am guessing
Small disclaimer:
im not responsible for any data loss etc. no warranties etc. fixing file system even readonly might cause data loss due to the bugs in RFS. you've been warned lol.
Click to expand...
Click to collapse
VOLD is what does the RFS check at boot. It seems to run, although maybe it fails? It definitely does run though, you can check it running using 'ps' on phone boot. Maybe it's only cleaning up /sdcard though.
At any rate, running the disk check does help with speed, but it doesn't help that much. It's still slow. I think if you want to stick with RFS, you need to do a defrag as well as the filesystem check. After some use, RFS must be very very fragemented on most people's phones.
Even in perfect condition though, RFS still has some very nasty properties such as locking the entire disk when a write occurs, not doing buffering, etc etc.
INeedYourHelp said:
Could someone just create an app that does this?
Click to expand...
Click to collapse
An app can't do this, since the app would have to be running off RFS and would crash/have to be killed to perform the FS checks. It could be done on boot using some trickery and the playlogos / replace binary trick. Or it can be done by replacing the init script with some kernel hackery. But at that point, you might as well just use a real filesystem.
I guess a PC .bat file could be made that uses adb to do this for you and then reboot the phone... Doesn't seem worth the trouble though!
RFS is journelled. You sure the filesystem doesn't do the journaling properly?
Nice job figuring this out. Is someone forwarding all these findings to that Samsung dev?
It's not about RFS vs the other filesystems. I'm well aware of the performance of RFS. But it's decent enough when it's working properly. It's not nearly as fast as ext but fast enough that you don't get annoyed.
Thus fixing RFS would make the life of many people who aren't technically inclined better. If the RFS do get all corrupted everywhere, and Samsung figure that out and fixes it, it means a good thing for most people.
The rest of us will end up on ext anyways
And yeah I think the fscheck at boot fails, it must fail actually, i don't see how else it would happen.
bilboa1 said:
It's not about RFS vs the other filesystems. I'm well aware of the performance of RFS. But it's decent enough when it's working properly. It's not nearly as fast as ext but fast enough that you don't get annoyed.
Thus fixing RFS would make the life of many people who aren't technically inclined better. If the RFS do get all corrupted everywhere, and Samsung figure that out and fixes it, it means a good thing for most people.
The rest of us will end up on ext anyways
And yeah I think the fscheck at boot fails, it must fail actually, i don't see how else it would happen.
Click to expand...
Click to collapse
What firmware did you test on, btw? I've noticed that JPK does seem to take longer on the FS checks, so maybe they have it fixed already (doubt it though)?
RyanZA said:
What firmware did you test on, btw? I've noticed that JPK does seem to take longer on the FS checks, so maybe they have it fixed already (doubt it though)?
Click to expand...
Click to collapse
on JPK actually
im going to flash JM8 to see if its the same in fact, but i expect so
RyanZA said:
VOLD is what does the RFS check at boot. It seems to run, although maybe it fails? It definitely does run though, you can check it running using 'ps' on phone boot. Maybe it's only cleaning up /sdcard though.
Click to expand...
Click to collapse
I think VOLD only does the checks for the Internal SD and External SD, not the RFS partitions.
Interesting find though, about the FS errors.
I’ve been wondering why the lag appears after a couple of days. I suspected corruption in one way or another myself, as it stays after a reboot it could not have been RAM and there are no signs of running out of space. Thanks for your research and I hope it will lead to new fixes. Sad but true my fix is to reflash my phone almost weekly.
I run Doc's JPK super slim ROM which is really nice but still it lags, even with OCLF installed.
Yesterday I take my phone out of my pocket to take a quick photo. My phone wakes up and I sweep the glass. Halfway through the sweeping the animation stops. I wait patiently for a second or three and there my home screen is. (No widgets, no animations, just a single home screen with 12 icons on it of the applications I actually use). I click on the camera icon and I wait another 5 seconds for the camera to realize it is not supposed to sleep on duty. I make a photo, the actual moment is already gone by now but hey I have the thing in my hand. It just takes another 5 seconds to store the photo.
It is like being in a hurry with a toddler with you. You want to go quicker but you can’t get angry cause the little thing just can’t go faster. It has to stop and wonder about life every once in a while.
I like my phone and I am sure it will grow up.
Very interesting findings! Sure hope Samsung sees this or this is forwarded to some Samsung techs.
Maybe move this to the development forum then it might get more traffic from people that can actually help.
borchgrevink said:
Very interesting findings! Sure hope Samsung sees this or this is forwarded to some Samsung techs.
Click to expand...
Click to collapse
do you really think Samsung is reading every thread here on XDA?
Sent from my GT-I9000 using XDA App
matty___ said:
do you really think Samsung is reading every thread here on XDA?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
No need to be uppity my friend ;-)
Some further info on possible RFS fixes here:
http://forum.xda-developers.com/showpost.php?p=8445244&postcount=143
With the sync issue fixed, and corruption fixed with checks, RFS might just work 'okay'! It won't be as fast as EXT, but it should still work fine if we can sort out all the bugs! And we have a much better chance of getting Samsung to include these fixes in a new firmware too.
If we could get hold of Samsung somehow, and manage to convince them that they should
1) disable the always sync behaviour
2) do full filesystem checks at boot up (or provide a utility to do the checks)
then RFS should be A LOT more usable!
Could someone perhaps turn this into a .bat-file?
RyanZA said:
Some further info on possible RFS fixes here:
http://forum.xda-developers.com/showpost.php?p=8445244&postcount=143
With the sync issue fixed, and corruption fixed with checks, RFS might just work 'okay'! It won't be as fast as EXT, but it should still work fine if we can sort out all the bugs! And we have a much better chance of getting Samsung to include these fixes in a new firmware too.
If we could get hold of Samsung somehow, and manage to convince them that they should
1) disable the always sync behaviour
2) do full filesystem checks at boot up (or provide a utility to do the checks)
then RFS should be A LOT more usable!
Click to expand...
Click to collapse
That quite right, I noticed the sync issue also.
As for the corruption, 2 things should be fixed:
- fsck from init should actually fsck the partitions properly on boot (we can sort of fix that by calling it in a script again)
- corruption should in theory not even happen so Samsung would have to work on RFS for that one
I ran JM8 for 2 days now and my rfs partitions are full of errors, like in JPK, just for confirmation if there needed to be one.
In fact it's still running fsck on /system as I'm writting and issues are filling the terminal .. its been running for 30s already lol
woeds said:
Could someone perhaps turn this into a .bat-file?
Click to expand...
Click to collapse
I haven't tried that but it might be easier to enable adb over usb (in development settings) then .. make sure you are rooted, type that:
> adb shell
$ su
#
<prompt on the phone for root, click allow>
reboot into recovery
> adb shell
$ su
# mount -oremount,ro /dev/block/stl9
# mount -oremount,ro /dev/block/stl10
# mount -oremount,ro /dev/block/stl11
<for safety i'm not including stl3 it's the EFS)
if there's any error due to "filesystem busy" them stop there, it means it doesn't work
otherwise:
#/system/bin/fsck_msdos -p -f /dev/block/stl9
#/system/bin/fsck_msdos -p -f /dev/block/stl10
#/system/bin/fsck_msdos -p -f /dev/block/stl11
# reboot
This was the kernel thread but it is so full of question that it was renamed to Question and answer!
before ask search in the forum.
Guide to install:
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsNand (Flash the phone)
http://sourceforge.net/apps/trac/androidhtc/wiki/HowToInstallWithAtoolsHaret (Dual system windows/android)
If you have "install module error" please install the android update on sourceforge. Read more here:
http://forum.xda-developers.com/showthread.php?t=848921
Awesome job on this l1q1d, i finally got around to getting the git set up on my computer yesterday so in can modify and compile so i'll try and get coding when i have some free time Thanks for all your efforts.
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Here for testing...
Glad to see this thread started!! Thought dev for Kaiser had seen its end. I'm no coder but can help with testing.
Hey L1q1d, this isn't by any means vital but i find it annoying and don't know if any other kaiser users have found this. If i turn the phone on and don't unlock it before pressing the power button again (i.e. just to check the time), there is a relatively long delay before the screen turns off. If i unlock the phone and then press the power button it turns off instantly. I have attached the logcat from when the phone is turned on and then turned off, i have also indicated where it locks before turning off the screen. I'm looking into it but if you have any pointers or don't experience this with your device let me know please
-Arturo- said:
I have some memory issues with both 3-10-2010 and 4-10-2010 kernels. The memory usage is really high and my launcher(launcher pro) keeps getting closed/restarted all the time even without opening any other apps.
Click to expand...
Click to collapse
Ok scratch that looks like the problem has been caused by having data on ext2 partition.
The kernel 2.6.32 runs way better than previous, but i have a persistent fail that knocks out the screen, at start i can see a message saying "msm_i2c.0: Bus still busy, status 2100m intf 100" and another more saying "msm_i2c.0: Error waiting for notbusy". ¿It is a common fail or it's only mine?
Hi
the problem is I do not belong here
I tried several variants android
the Caller ID does not work
basic configuration of network settings, but it is not good
if you want to set up an error message is incorrect sim, and it is no longer a network
something that is not a solution?
L1q1d, good work. Some of the changes you have made, such as nand, affect all of the related phone types. So, you might want to at least mention them on the vogue kernel thread. On the other hand, the keypad and battery code is not used by vogue. As you know, Polaris uses the same battery code as Kaiser.
I'm thinking two changes for battery code:
a) going back to max voltage and current instead of average, to work better with poor batteries. My old battery sometimes has deep dips in its reported voltage, causing a recalibration to 5% capacity when it really has more like 40%.
b) the recommended capacity calculations at high and low calibration points should be "recommended = battery_capacity - (new - old)" instead of "recommended -= (new - old)". As things are, the recommended value is pretty close on the first calibration, but any subsequent calibrations apply the same correction over and over again, making the recommended value go negative or insanely positive. Of course I cannot remember the names of the variables.
@L1q1d
This is a nice idea to make this thread for kaiser users.
Today I tried the latest kernel 4-10-2010 with fresh froyo 2.2.1 (nand installation). First the system works well. But after installing the ADW.Launcher from the market and after a reboot I got always chrashes from this launcher and I never had this before with any other kernel and the launcher version has not been changed. So maybe I have the same issues then Arturo. Then I tried the app task killer but it chrashes after starting it (same problem). I think these problems could be memory issues in the latest kernel version.
Keep going on your nice work for kaiser
l1q1d I have just got a framework exception and as usual 90% of apps don't work anymore. It occured using the latest kernel.
Also I still keep getting those launcher pro redraws It didn't happen while using the 2.6.25 kernel. Has the memory management been changed in the new kernel?
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
n2rjt said:
Do you use compcache? Like wlan, compcache uses kernel drivers that have to match the kernel version. I use compcache with backing store on 4th partition of sdcard.
Sent from my Full Android on Vogue using XDA App
Click to expand...
Click to collapse
Yes I do. I ripped the compcache.sh file from latest dzo's fresh froyo build.(I remember reading Kalt Kaffe's post about getting compcache to work with the newest kernel a while ago so I assumed that it has been sorted out and we can enable compcache with new kernel) I'm on NAND at the moment with both system and data. I've tried system on nand and data on ext2 partition but the launcher redraws were killing me, every time I opened opera mini and then closed it the launcher was closed and I had to wait for it to load into memory again.
I'm back to system and data on nand at the moment with new kernel and it's much much better but still it happens from time to time. I've never experienced launcher redraws with the old kernel so I don't really now what;s wrong.
About the 4th partition....you mean swap, right?
When I was on nand +sd card I had 3 partitions 1) fat 32 then 2) ext2 about 30 mb(I don't know what for is the first ext2 partition but i remember that i couldn't install data to sd card with only one ext2 partition) and finally 3) second ext2 partition for data about 300mb. So by creating the third ext2 partition I would activate swap in compcache? I've never tried as I heard that it might used up the sd card faster. also I only have two sd cards 6gb(class 4) and 12 GB (class 2) so I think i would probably need class 6 for swap file?
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
n2rjt said:
The compcache-required modules are included in the 2.6.32 modules attached to my first post of this thread. Those files should work with any recent 2.6.32 kernel. I would suggest that we should be able to get modules the same place we get zImage and NBH files.
I wouldn't recommend backing store for everybody. It works for me, with my 8GB card, but I'm not sure it ever even writes anything to the swap partition. And, yes, my fourth partition is a swap partition. Kallt-kaffe's latest compcache.sh script should work fine.
An easy way to find out of your compcache is working: use the "free" command from the command prompt. If swap is shown as zero, compcache is not working. You can also see failures in the dmesg log.
Click to expand...
Click to collapse
Excellent N2rjt i think you just found the cause of my issues. I updated my system with the modules you have linked enabled compcache again and then i entered the "FREE" command and swap shows zero. So the compcache is not working this must be the reason for constant launcher redraws. Now what could be the cause of "broken" compcache?
Sent from my Full Android on Vogue using XDA App
lzo modules are now included in the kernel, you need only ramswap. probably compcache script have some problem with it.
Ok, guys I got a compcache.sh file from the latest dzo's froyo and compcache is finally enabled. I will be testing the device to see whether the issues are gone. Thanks for your help.
Bug: white screen, Android still alive
How I got a white screen:
AT&T Tilt-flavored Kaiser, latest kernel and dzo's Fresh Froyo, both built from current git code.
I was typing on the hardware keyboard, actually entering a message for xda-developers. I wanted to say "dmesg | grep ds2746", but couldn't find the "|" symbol. I remembered that the hardware keys for the soft keys (between R-T and between I-O) have some symbols mapped to them, so I was trying different Fn- and Symbol combinations of those keys.
Eventually I hit Fn-(Left soft key), and got a text screen with dmesg logs.
Okay, how to get back to a graphical screen? I tried a few keys that didn't take me back, then had a brilliant idea, hit the red hangup key.
That blanked the screen, but when I hit other keys to wake up, I had a white screen. Yet, adb logcat verifies that the phone is still running Android, and it is even responding to my touches, just I can't see anything except white.
Edit: can recover by using Fn- keypad right soft key.
Battery issues?
If anyone has battery issues, please open a terminal, and type this:
> dmesg | grep ds2746 > /sdcard/dmesg.log
and send the dmesg.log file.
Thanks!
I have currently Fat Free Froyo with the only 2.6.32 kernel, I was able to make working with my Kaiser, KAIS130 with DATA on SD Card Partition and SYS on NAND
I configured contacts, added a music player application. Did some settings with ADW Launcher. Then activated wifi, tested it working, openned browser and KABOOOM, phone forces ever application as NOT RESPONDING. So, I just long pressed power button to turn it off and then turn on again. All of the stuff I configured is gone, except the Widgets I manually added on the homescreen.
So my question, in the endo is, How can I get my settings saved and not to lose contacts / installed apps?
My SD Card setup:
870MB Fat32 (for Android install, a number of music files and android apk installers)
520MB ext2
510MB ext2 (no idea on what partition its saving DATA)
Most of the time it goes on the last partition of the SD Card, now if you configured data using atools, then p2 would be partition 2 of the card, and p3 is partition 3.
Never heard of data corruption occuring on the SD Card.
Have you tried restoring your phone back to stock OS (WinMo 6.1)?
If not, try flashing the stock ROM back onto the phone so it flashes the stock radio as well back onto the phone. As long as you don't include KAISDIAG.NBH, the bootloader won't be reflashed even though the flashing process states it's being flashed.
Then reflash the kernel you're using, then reinstall your build.
Also you're stating you can only get one type of 2.6.32 kernel working? Have you tried the latest kernel under the Kernel help thread?
Make sure you use atools to configure the kernel for your kaiser.
Krazy-Killa said:
Most of the time it goes on the last partition of the SD Card, now if you configured data using atools, then p2 would be partition 2 of the card, and p3 is partition 3.
Never heard of data corruption occuring on the SD Card.
Have you tried restoring your phone back to stock OS (WinMo 6.1)?
If not, try flashing the stock ROM back onto the phone so it flashes the stock radio as well back onto the phone. As long as you don't include KAISDIAG.NBH, the bootloader won't be reflashed even though the flashing process states it's being flashed.
Then reflash the kernel you're using, then reinstall your build.
Also you're stating you can only get one type of 2.6.32 kernel working? Have you tried the latest kernel under the Kernel help thread?
Make sure you use atools to configure the kernel for your kaiser.
Click to expand...
Click to collapse
Just recently installed my apps again without any re-formatting. Installed the widgets again. Rebooted. Now its showing everything fine.
Mine kernel is 2.6.32, Panel Type 1, Keyboard type: tytn II, 240x320 (This one is my first attempt in making an nbh and wifi works on it).
This release (Fat free Froyo) is hell slow while opening applications etc. What can be the problem? The previously used Eclair Polymod 2.1D wasnt this much of a turtle.
P.S: When I connected USD, disable debugging mode and enable USB Storage, the button "Turn off USB storage" turns back to "Turn on USB Storage" after 5 seconds. I can't connect my SD Card as USB Storage :/
dark_prince said:
Just recently installed my apps again without any re-formatting. Installed the widgets again. Rebooted. Now its showing everything fine.
Mine kernel is 2.6.32, Panel Type 1, Keyboard type: tytn II, 240x320 (This one is my first attempt in making an nbh and wifi works on it).
This release (Fat free Froyo) is hell slow while opening applications etc. What can be the problem? The previously used Eclair Polymod 2.1D wasnt this much of a turtle.
P.S: When I connected USD, disable debugging mode and enable USB Storage, the button "Turn off USB storage" turns back to "Turn on USB Storage" after 5 seconds. I can't connect my SD Card as USB Storage :/
Click to expand...
Click to collapse
I have that same problem with USB Storage, I found that if I leave Debugging enabled in certain cases, I can enable USB Storage just fine. In Windows, no matter what you do, it won't connect, and in Linux it's still pretty buggy.
You've made your own kernel, sweet! Still trying to get mine to compile, but overall really haven't had time with the holidays, but will start up again this week.
Fat Free Froyo is a pretty decent build, but yes some apps do take awhile to load. I found that Gingerbones build is very stable, at least with my testing. You should give it a try, though it is pretty stripped down, so you might want to grab whatever apps you want and throw them in /system.
Krazy-Killa said:
I have that same problem with USB Storage, I found that if I leave Debugging enabled in certain cases, I can enable USB Storage just fine. In Windows, no matter what you do, it won't connect, and in Linux it's still pretty buggy.
You've made your own kernel, sweet! Still trying to get mine to compile, but overall really haven't had time with the holidays, but will start up again this week.
Fat Free Froyo is a pretty decent build, but yes some apps do take awhile to load. I found that Gingerbones build is very stable, at least with my testing. You should give it a try, though it is pretty stripped down, so you might want to grab whatever apps you want and throw them in /system.
Click to expand...
Click to collapse
Right now on Gingerbones:
Radio version 1.70.19 (I'm sure about that)
Wifi Turn ON = ERROR
Installing Polymod 2.1D and checking if it works with 2.6.32 (though the kernel's tagged as Froyo's)
ALOT OF TEXT ROLLS REGARDING SOME SCHEDULE thingi, idk but hope that everything goes ok
Re-Partitioned SD Card and now Data is on 800Megs and FAT32 is on 900Megs
I loved polymod 2.1D but it had wifi error with 2.6.25
Edit: 2.1D says "Unable to Start wifi"
Back to the one and only Fat free Froyo
Edit3:Again settings are not saved :/ Battery is stuck at 15% (even I kept it connected for more than an hour)
Back to Windows mobile for charging fuss
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D Follow this link if you need an NBH suiting your type. (use the only ones with prefix KAISIMG)
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
nlooooo said:
You should go back to GB...
Sent from my GT-P3100 using Flashes and Thunders
Click to expand...
Click to collapse
Why? No.
If you can live with slower perfomance, active the stock a2sd again with answers: y, y ,y
vBurak said:
Hello,
I installed on my Desire with STOCK HBOOT Sandvold ICS in the Version 0.17.1.1. I choosed stock a2sd in the installation and active in terminal a2sd install. Then I restored my apps by Mybackup Root. I have now the problem if I want to install a app from the market I get the error message "No Disk space available" (or something like that, I'm using German language).
I have a 512mb ext4 partition and activate a2sd in Terminal. I searched the topic for problems like that and found that I have to install mount2sd. I did this, but it didn't help either.
What should I do now? I haven't enough posts to post in the sandvold ics topic.
Greets,
Burak
Click to expand...
Click to collapse
I had exactly the same problem. At first I chose during flashing the option "Regular a2sdext" as it seems good to me. However, nothing has changed, it was not working for me at all. Then I reflashed again with "Stock a2sd" and after booting I went to terminal and activated it. I tried it with several combinations (in some of them I got the message "Insufficcient storage available" and I only had like 5 apps installed...). At the end I finally made it work with the combination that is recommended by Sandvold - Y N Y. After that I have been installing several apps and my internal memory does not go down almost at all :good:... I will see later, but for now, this is the best set up for me....
I had this problem
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I have been testing 0.18 for a few hours now. Your phone issues should be resolved except you will encounter a new issue. You will lose superuser privilliges, to restore this, you have to install a zip of superuser through recovery.
My comments on Sandvold ICS 0.18
skubko said:
what do you mean that you lost root access? I was planning to upgrade to 0.18 today (I flashed 0.17.1 yesterday, but I have an issue with my phone - I cannot recevie any phone calls - and I hope another flash might help it...), so I guess I will wait a while....
Click to expand...
Click to collapse
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
CzarD said:
I had 0.17.1.1 and all was well, it was tiny bit laggy, but overall it was cool.
i updated to 0.18, and I lost root access: the apps requesting SuperUser premissions were denied. (If you don't know what root access is, please google it)
As iyf said, you can flash the zip provided in Sandvold's official thread to restore root access. Check page 1601 or so for the flashable zip that will restore root access. I did so, and regained root access.
Then I got back all my apps as Sandvold 0.18 is my daily driver. But as I was using it, I noticed that whenever you change something in the system settings, it does not apply immediately. For example, I want my phone to lock immediately when it goes to sleep, well it simply doesn't. The power menu lost a few of the shortcuts it had in 0.17.1.1 (sound profiles...) and even if you restored them in the system settings, it won't change.
All in all, 0.18 is great step in terms of stability and reactiveness. No more scroll lag, apps open seamlessly, and no more 3G signal problems. The camera still isn't working though. Nevertheless, bizarrely the system lost its coherence: the system settings are not immediately applied and used, and the screen just won't lock. Those are the problems I encountered this afternoon.
I hope Sandvold takes a look at this thread as I cannot post on the official ROM thread coz I just registered on XDA.
(My Home button died today, even if I press it really hard, it won't respond, but I think it's a hardware issue)
EDIT: About the no more space issue, I had this today even though there was plenty of space left. I rebooted the phone and the warning disappeared.
Click to expand...
Click to collapse
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
CzarD said:
I had this problem with one application. When installing from market, there'd be a pop up message saying that there was no more storage space even though there was plenty.
A few hours later, everything went back to normal and I managed to install all the apps I wanted.
(Side question: have you guys updated to Sandvold ICS 0.18 Beta?! I have, but I lost root access, so now I'm trying to regain it. Could someone alert Sandvold? I'm a new member and I can't post to 'Android development forums")
Click to expand...
Click to collapse
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
skubko said:
of course I know what root is, otherwise I would not be here, right? ... I just did not understand what happened to you when you updated to 0.18.... Now I understand.... and regarding to your issues - in 0.17.1 I had exactly the same problem - my screen did not lock even I set it up correctly and I also had the problem with Home button, it simply did not work + I could not receive any phone calls... all of that was really annoying and I tried to find some help on sandvold's blog, without any success, I also tried their IRC, nobody helped me either. I did not want to do a full wipe again, but at the end I did (and now I have to set up everything as well ) but after full wipe, everything is working correclty... I can receive phone calls, my screen locks and home button is also working ... so I recommend you to do a full wipe, I am sure it will resolve your issues as well...
Click to expand...
Click to collapse
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
CzarD said:
By full wipe you mean:
1. wipe data/factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
right?
I always do that when I flash a new ROM... Anyway, will try again later and hope that it works.
Caesar
Click to expand...
Click to collapse
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
UserMatty said:
I also lost the root access with Beta 0.18(with full wipe),
(Beta 0.17 "root access" is OK!)
Superuser is out of order with this issue so that I can't activate A2SD
btw,
I have once tried the "AD2SDX", but didn't work normally:
I merged 1GB ext4 for it. And every time when I install about 10~15 Apps
A message on the top of the screen would tell me that I almost reached the limit.
(I'm using traditional Chinese, I don't know what it was written in English)
Click to expand...
Click to collapse
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
skubko said:
yes, it is what I meant... I did full wipe before flashing and then another after it ... I do not wipe battery stats during that process,but it does not matter I hope it will work for you...
Click to expand...
Click to collapse
I did a full wipe again, and everything went back to perfect working order. Thanks man
CzarD said:
Whenever I got this message, I'd reboot or hot reboot and it would disappear. I can't remember if I had the same script.
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
I did a full wipe again, and everything went back to perfect working order. Thanks man
Click to expand...
Click to collapse
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
It's not okay, minitool doesn't do that correctly. Use 4ext recovery to partition your sd card.
Sent from my HTC Desire using Flashes and Thunders
UserMatty said:
you mean working with AD2SDX ?
Can I ask you how do you merge and format ext4 ?
Actually, I'm using MiniTool Partition Wizard, is it okay ?
cause I did reboot after I saw the message, but didn't work.
But I surely know that I can see "1GB" in "Apps" in "settings"
quite confusing
Click to expand...
Click to collapse
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
just to add - I have Amon RA Recovery and I partitioned my SD card by that, it was also working without any problems everytime I did it...
@CzarD - I am glad to hear that the wipe helped you...
You should try out the Amarullz or INT2SD from the Aroma installer. I have INT2SD and I have 1,3G of free space (2G EXT partition)
CzarD said:
Quite confusing indeed. I must say I'm no expert developer or programmer, heck I'm an engineering student. i just experiment on my Desire. But my experience in bricking/unbricking/flashing/etc tells me the following:
Minitool wizard apparently is not okay. I used it at first too but my Desire just could not read or detect the EXT3 partition I created. I tried EXT4. I tried different roms and scripts, none worked for me. (To be honest, I only tried 3 roms and a few scripts).
What I used is plain simple: Clockworkmod Recovery partitioning tools. It works for me!
First restore your SD card to full FAT32 configuration (I might suggest changing the basic storage unit from a few bytes to a few kilobytes as it might increase SD card responsiveness).
BACK IT UP, you will lose everything on it when you partition it in CWM.
Boot into recovery and select partition SD card (It is advised that the size of your partition does not exceed 1.5 GB as a few ROM developers have pointed out - not Sandvold though- I use 512 MB, which is more than enough for me). Set SWAP to 0 Bytes. (i have no idea what swap is, should google it, but most threads advise a swap of 0 B).
That's it, you have your partition.
I use CWM and Sandvold 0.18. If you use this setup, everything should be okay, at least it's ok on my phone.
I use stock a2sd when flashing Sandvold ICS ROMs.
I'm on stock HBOOT, S-OFF, and using the regular Kernel that comes with Sandvold 0.18. (I tried tiamat, but the battery dies after half a day of use!)
Click to expand...
Click to collapse
As I know, swap in linux is somewhat like virtual memory in Windows.
Will be launched when the system is in low memory.
That's exactly everything I know
I'm now Using Revolutionary CWM v4.0.1.4, stock HBOOT, S-OFF
And just follow your way to full wipe then install the system again(stock a2sd)
I still can't get the root access. thus, I can't activate a2sd in terminal
PS: with Beta 0.18
But Beta 0.17.1 currently work!
I bought my phone about a week ago, and I noticed it was pretty slow after installing some apps, even slower than my previous Nexus S.
I changed my phone from yakjuxw to yakju yesterday, and updated to 4.2. I even did a factory reset after everything was done.
It was the same, it started pretty fast but as I ran the apps from the backup I had made the phone started to slow down.
I still haven't managed to find which app is causing me problems, so I was hoping someone here could help...
Did you use Titantium Backup for apps?
As far as I know, it is recommended not to restore all apps via Titantium Backup but only the ones that have some data associated to them like games with their saves. So try installing a fresh 4.2 ROM, only restore the apps that needs their data, and download the others via Play Store
I hope you can either avoid the lag this way or at least spot the app causing it
ahmadallica said:
Did you use Titantium Backup for apps?
As far as I know, it is recommended not to restore all apps via Titantium Backup but only the ones that have some data associated to them like games with their saves. So try installing a fresh 4.2 ROM, only restore the apps that needs their data, and download the others via Play Store
I hope you can either avoid the lag this way or at least spot the app causing it
Click to expand...
Click to collapse
No, I restored it through the Nexus Toolkit (the GUI version).
I only restored normal apps and none of the system apps or data. And this has been on absolutely stock Google ROMs ever since I bought the phone.
KaiZ51 said:
I bought my phone about a week ago, and I noticed it was pretty slow after installing some apps, even slower than my previous Nexus S.
I changed my phone from yakjuxw to yakju yesterday, and updated to 4.2. I even did a factory reset after everything was done.
It was the same, it started pretty fast but as I ran the apps from the backup I had made the phone started to slow down.
I still haven't managed to find which app is causing me problems, so I was hoping someone here could help...
Click to expand...
Click to collapse
That happens when you restore rom essential apps...you only need to restore the apps you downloaded.
Sent from my Galaxy Nexus using xda premium
Maybe you have the eMMC bug/issue which may occur if your phone was produced 08/2012.
To check this install the "eMMC Brickbug Check" tool and verify if your if chip type is V3U00M and date 08/2012.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
If yes check this link for a workaround for this annoying bug:
http://forum.xda-developers.com/showpost.php?p=35020486&postcount=10
KaiZ51 said:
No, I restored it through the Nexus Toolkit (the GUI version).
I only restored normal apps and none of the system apps or data. And this has been on absolutely stock Google ROMs ever since I bought the phone.
Click to expand...
Click to collapse
try to flash the image again and dont restore this time... see if that fixes your issue
navien said:
Maybe you have the eMMC bug/issue which may occur if your phone was produced 08/2012.
To check this install the "eMMC Brickbug Check" tool and verify if your if chip type is V3U00M and date 08/2012.
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
If yes check this link for a workaround for this annoying bug:
http://forum.xda-developers.com/showpost.php?p=35020486&postcount=10
Click to expand...
Click to collapse
Well, I've just checked it, and it seems like my phone falls within the parameters for this bug... The only difference is the date is 09/2012. But is there a way to know for sure that I'm affected by this bug? Besides, I'm going to have to root the phone, which is going to be a bit annoying since I really didn't want to do it because I may have problems with the warranty in case I need to return it...
Also, if I flash a custom ROM in the future, will I have to do that again, or do custom ROMs usually come with that fix?
k786 said:
try to flash the image again and dont restore this time... see if that fixes your issue
Click to expand...
Click to collapse
I was thinking of trying that as well, though it may be annoying because I'll lose my data... But if I have to I guess I really don't have a choice...
KaiZ51 said:
I was thinking of trying that as well, though it may be annoying because I'll lose my data... But if I have to I guess I really don't have a choice...
Click to expand...
Click to collapse
delete the userdata from the image and it wont wipe your internal storage
KaiZ51 said:
Well, I've just checked it, and it seems like my phone falls within the parameters for this bug... The only difference is the date is 09/2012. But is there a way to know for sure that I'm affected by this bug? Besides, I'm going to have to root the phone, which is going to be a bit annoying since I really didn't want to do it because I may have problems with the warranty in case I need to return it...
Also, if I flash a custom ROM in the future, will I have to do that again, or do custom ROMs usually come with that fix?
Click to expand...
Click to collapse
All people reported this bug (at least what i´ve found) have production date of 08/2012 - maybe this bug also affects newer models.
I think if your chip type is V3U00M then your'e phone is affected. But your can test this easily. Just copy a huge file (i've copied 1 hd movie ~11GB) to the internal storage. The phone should slow down extremely, even if you delete the file again. For example: my phone needed 4-6 seconds to open the contacts app - sometimes even more.
Rooting is no big issue - you can easily revert to stock image.
If you flash a ROM you will to have implement the workaround again. Custom ROMs will not include this fix in general because if you remount the data partition with the discard option on an eMMC other than V3U00M your phone will be hard bricked.
navien said:
All people reported this bug (at least what i´ve found) have production date of 08/2012 - maybe this bug also affects newer models.
I think if your chip type is V3U00M then your'e phone is affected. But your can test this easily. Just copy a huge file (i've copied 1 hd movie ~11GB) to the internal storage. The phone should slow down extremely, even if you delete the file again. For example: my phone needed 4-6 seconds to open the contacts app - sometimes even more.
Rooting is no big issue - you can easily revert to stock image.
If you flash a ROM you will to have implement the workaround again. Custom ROMs will not include this fix in general because if you remount the data partition with the discard option on an eMMC other than V3U00M your phone will be hard bricked.
Click to expand...
Click to collapse
So, I went ahead and followed the instructions on the link you gave me... And it seems to be much better so far I still haven't tested enough, but I think the problem is pretty much fixed. I just have a few more questions if you don't mind...
1- When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
2- Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
3- Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
KaiZ51 said:
So, I went ahead and followed the instructions on the link you gave me... And it seems to be much better so far I still haven't tested enough, but I think the problem is pretty much fixed. I just have a few more questions if you don't mind...
1- When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
2- Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
3- Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
Click to expand...
Click to collapse
Bumping...
KaiZ51 said:
So, I went ahead and followed the instructions on the link you gave me... And it seems to be much better so far I still haven't tested enough, but I think the problem is pretty much fixed. I just have a few more questions if you don't mind...
1- When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
2- Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
3- Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
Click to expand...
Click to collapse
The dd command fills the entire partition till full, therefore the not enough space message is normal.
I´ve not tested how to implemt this fix in a ROM before flashing.
In theory you only need to add the file with the script into the init.d folder of the zip before flashing.
I´ve made IO Benchmarks with AndroBench to check if the script works:
with enabled script i get for example RND WR ~135 IOPS without script 54 IOPS.
navien said:
The dd command fills the entire partition till full, therefore the not enough space message is normal.
I´ve not tested how to implemt this fix in a ROM before flashing.
In theory you only need to add the file with the script into the init.d folder of the zip before flashing.
I´ve made IO Benchmarks with AndroBench to check if the script works:
with enabled script i get for example RND WR ~135 IOPS without script 54 IOPS.
Click to expand...
Click to collapse
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Sorry about all the trouble with this problem, it's just as you probably know the phone is barely usable with this bug so I have no choice but to ask for help... Google should really fix this in an update, it's something pretty urgent in my opinion.
KaiZ51 said:
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Sorry about all the trouble with this problem, it's just as you probably know the phone is barely usable with this bug so I have no choice but to ask for help... Google should really fix this in an update, it's something pretty urgent in my opinion.
Click to expand...
Click to collapse
Oh, and do you think I should go to the store to replace my phone? I still haven't understood if this is a software or hardware issue, but I'm believing it's the first...
KaiZ51 said:
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Sorry about all the trouble with this problem, it's just as you probably know the phone is barely usable with this bug so I have no choice but to ask for help... Google should really fix this in an update, it's something pretty urgent in my opinion.
Click to expand...
Click to collapse
OK. The workaround with the script needs a ROM with init.d support. I thought this was mentioned in the linked thread.
I´m using THIS one.
The real fix is the re-mounting of the /data & /cache partitions using the discard option. If you type the command in a terminal window it fixes the problem temporary.
After reboot the problem is back. So you need to make a init.d script which will be executed every boot.
I think the dd command 'cleans' the free memory but i'm not sure.
To my opinion it doesn't make any sense to replace the phone because there's a big chance to get a new one with same problem.
So it is a software bug which should be solved by google.
navien said:
OK. The workaround with the script needs a ROM with init.d support. I thought this was mentioned in the linked thread.
I´m using THIS one.
The real fix is the re-mounting of the /data & /cache partitions using the discard option. If you type the command in a terminal window it fixes the problem temporary.
After reboot the problem is back. So you need to make a init.d script which will be executed every boot.
I think the dd command 'cleans' the free memory but i'm not sure.
To my opinion it doesn't make any sense to replace the phone because there's a big chance to get a new one with same problem.
So it is a software bug which should be solved by google.
Click to expand...
Click to collapse
Hmm I see... But from what I understood, you can make the script run at boot with apps like ROM Toolbox and Script Manager, correct? Although I'm not sure if it's running on my system, I've tried both apps and the benchmarks are always in the 30's...
Or do you really need a ROM with init.d support? Also I have BusyBox installed on Google's stock ROM, not sure if that is enough to able to run init.d scripts.
But how would you run scripts with init.d? Sorry, I'm a noob to this kind of stuff, I never did stuff like this...
KaiZ51 said:
Well, I've just checked it, and it seems like my phone falls within the parameters for this bug... The only difference is the date is 09/2012.
Click to expand...
Click to collapse
Thank you for confirming chips produced 09/2012 as bad. Added this to the post linked above.
KaiZ51 said:
When I ran the dd command, it took a while like the instructions said, but when it finished it said something about not enough space. Could something have gone wrong, or is this normal?
Click to expand...
Click to collapse
This is normal as we don't give the dd command a particular file size to create. So it simply writes data until no space is left.
KaiZ51 said:
Since it isn't likely custom ROMs implement this fix, is there any way I can "stick" this fix on the phone's system so that I don't have to worry about setting it every time I flash a new ROM?
Click to expand...
Click to collapse
If you are only using ROMs that support something like init.d inside data (like CM), next time to worry about this will be when you do a full wipe.
Probably then the problem will already be fixed by Google or others as it gains more attention over time.
KaiZ51 said:
Is there any way to make sure that the script I set up in Script Manager is fully working and running on boot?
Click to expand...
Click to collapse
Jup. Type 'mount' in Terminal or adb after you rebooted your phone:
# mount
[...]
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /data ext4 rw,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered,noauto_da_alloc,discard 0 0
[...]
Click to expand...
Click to collapse
=> discard option added, script ran successfully
KaiZ51 said:
Apparently it isn't running, since I get my Random Write score in the 30's IOPS. Besides that, I made Script Manager output logs, and it seems like it says it could not mount.
Click to expand...
Click to collapse
Maybe you have to check something like 'run as root' or similar in Script Manager.
KaiZ51 said:
So what can I do? I'm not sure if I've already said this, but I'm on the stock 4.2.1 yakju ROM, if it matters. I could do this the init.d way, but I'm not sure if it works fine on stock ROM...
Click to expand...
Click to collapse
Nope. Stock does not support init.d.
KaiZ51 said:
Also, something I haven't yet understood, is the dd command for checking if the fix works temporarily, or do you really need to do it in order to prepare the phone for the script?
Click to expand...
Click to collapse
You can use the script without. The phone will speed up over time as more and more data is written/deleted and therefore the eMMC chip gets some discard commands.
The dd + rm just speeds up the process as all free blocks will be told to the eMMC chip due to the discard option added beforehand.
Another possibility (after installing the script and confirming that it works) would be to copy a large file that fills almost all space on the phone and remove it afterwards. The dd command is just considerably faster.
KaiZ51 said:
And do you need to have as much empty space as possible before running the command, or you don't need to care about that?
Click to expand...
Click to collapse
You don't need to care. Just keep around 1,0-1,5 GiB of free space everytime: Benchmark
KaiZ51 said:
Oh, and do you think I should go to the store to replace my phone? I still haven't understood if this is a software or hardware issue, but I'm believing it's the first...
Click to expand...
Click to collapse
Well, you might get a replacement phone and through bringing it back the chance that Google gets aware of the problem may be higher.
But possibly they will only wipe all data which makes the phone fast again for some time and tell you there is nothing wrong with it...
You may even think about it from this point of view: If the fix works for you, you have a phone with a blazingly fast eMMC chip, faster than any GNex produced before 08/2012 (until you have less than 1 GiB of free space on /data)
KaiZ51 said:
Google should really fix this in an update, it's something pretty urgent in my opinion.
Click to expand...
Click to collapse
+1
ph4zrd said:
Thank you for confirming chips produced 09/2012 as bad. Added this to the post linked above.
This is normal as we don't give the dd command a particular file size to create. So it simply writes data until no space is left.
If you are only using ROMs that support something like init.d inside data (like CM), next time to worry about this will be when you do a full wipe.
Probably then the problem will already be fixed by Google or others as it gains more attention over time.
Jup. Type 'mount' in Terminal or adb after you rebooted your phone:
=> discard option added, script ran successfully
Maybe you have to check something like 'run as root' or similar in Script Manager.
Nope. Stock does not support init.d.
You can use the script without. The phone will speed up over time as more and more data is written/deleted and therefore the eMMC chip gets some discard commands.
The dd + rm just speeds up the process as all free blocks will be told to the eMMC chip due to the discard option added beforehand.
Another possibility (after installing the script and confirming that it works) would be to copy a large file that fills almost all space on the phone and remove it afterwards. The dd command is just considerably faster.
You don't need to care. Just keep around 1,0-1,5 GiB of free space everytime: Benchmark
Well, you might get a replacement phone and through bringing it back the chance that Google gets aware of the problem may be higher.
But possibly they will only wipe all data which makes the phone fast again for some time and tell you there is nothing wrong with it...
You may even think about it from this point of view: If the fix works for you, you have a phone with a blazingly fast eMMC chip, faster than any GNex produced before 08/2012 (until you have less than 1 GiB of free space on /data)
+1
Click to expand...
Click to collapse
Thanks, that cleared a lot of questions.
So, after having tested the phone some more time (and I do have discard enabled at boot after all), the phone still seems pretty slow to me.
Yesterday I did the discard command with the adb shell, and then rebooted with the discard script enabled, but it's still pretty slow...
I've also benchmarked the phone in AndroBench a few times after this and Random Write scores ranged from as low as 6 (yes, six) IOPS, to 60's IOPS.
Still, this isn't that good since it seems like normal scores are in the 100's.
I really don't know what I should do now... Maybe the eMMC chip isn't actually the problem? But I find that rather strange since I don't think I have any apps that I already didn't have on my old Nexus S, and the phone does seem slower than my old one.
KaiZ51 said:
I really don't know what I should do now... Maybe the eMMC chip isn't actually the problem? But I find that rather strange since I don't think I have any apps that I already didn't have on my old Nexus S, and the phone does seem slower than my old one.
Click to expand...
Click to collapse
How much free space do you have left on /data or /sdcard?
And you used the dd-rm-combination after remounting with discard, right?
ph4zrd said:
How much free space do you have left on /data or /sdcard?
And you used the dd-rm-combination after remounting with discard, right?
Click to expand...
Click to collapse
I have 1.71GB free now.
And what do you mean about your second question? If you're asking if I used those commands when I connected the phone to my PC via USB Debugging, then yes.
If you're talking about the script that runs at boot, all I have in that script is
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
Should I put the script like this?
Code:
#!/system/bin/sh
mount -o remount,discard /data
mount -o remount,discard /cache
dd if=/dev/zero of=/data/tmp.bin
rm /data/tmp.bin
I didn't put them there since I thought the dd and rm commands were only meant to be run when connected via USB and not at boot as well...