I'm running ICBINB[1] and I'm experiencing poor performance. For instance, when running the Drag Racing game, a race may take 30-45 seconds while in "game time" it only takes 12 seconds.
I installed per the directions on the rom's thread.
I then waited 10 minutes
rebooted recovery and restored data, rebooted
waited 10 minutes
rebooted recovery and installed acid theme, cleared cache fixed permissions per op
rebooted and waited 10 minutes
I don't have a ton of apps and just have 2 widgets (simi clock and simple calendar). I'm running Launcher Pro. Quadrant scores (while not the end all) are around 1360, which seems really low based on what others have said.
I'm just reflashed ICBINB and am going to just run that for a bit (no restoring data, no theme, no launcher pro) and see what performance is like.
Any suggestions?
Thanks in advance,
Ryan
[1] http://forum.xda-developers.com/showthread.php?t=1157593
Drag racing has always run slow on samsungs for some reason.. unless I was OCed it wouldn't run properly half the time. Icbnb is pretty close to stock
Are you on froyo or gb? Ext4? If not try them and maybe oc should help
sent from my real Gs move in silence like lasagna
mbernusg said:
Drag racing has always run slow on samsungs for some reason.. unless I was OCed it wouldn't run properly half the time. Icbnb is pretty close to stock
Are you on froyo or gb? Ext4? If not try them and maybe oc should help
sent from my real Gs move in silence like lasagna
Click to expand...
Click to collapse
I find if I load the game then clear the ram then the game runs smooth. Otherwise its rediculously laggy, even if I clear the ram before I run it.
I'm not sure why it lags either, but GB gets rid if it. Maybe you should try ICBINB GB.
be sure to install chainfire 3d and get some of the drivers like nvidia
also OVERCLOCKING is always a big boost for games
and if you haven already try the adrenaline shot
also if you quad scores are that low sounds likes your not on ext4
dsexton702 said:
be sure to install chainfire 3d and get some of the drivers like nvidia
also OVERCLOCKING is always a big boost for games
and if you haven already try the adrenaline shot
also if you quad scores are that low sounds likes your not on ext4
Click to expand...
Click to collapse
Just wanted to add that my previous post referred to ICBINB KD1, before SAS was released. My setup was simply ICBINB KD1 stock.
I also never tried installing Chainfire 3D or overclocking when I was on Froyo. Maybe Chainfire 3D is the solution though.
What does chainfire 3d do that makes games run better?
Sent from my SGH-T959V using xda premium
Here is a link to Chainfire 3D
From his description:
Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Not that it matters, but pre/post quadrant/linpack scores were really no different before/after chainfire... I did not do a real graphics benchmark though.
s15274n said:
Here is a link to Chainfire 3D
From his description:
Chainfire3D sits between your apps and the graphics drivers, and can intercept and/or change commands between the two. It has some built-in functions, and can be further extended with plugins to provide extra functionality.
Not that it matters, but pre/post quadrant/linpack scores were really no different before/after chainfire... I did not do a real graphics benchmark though.
Click to expand...
Click to collapse
its not meant to boost quad scores but to make games run better, and it does a great job of doing so
dsexton702 said:
be sure to install chainfire 3d and get some of the drivers like nvidia
also OVERCLOCKING is always a big boost for games
and if you haven already try the adrenaline shot
also if you quad scores are that low sounds likes your not on ext4
Click to expand...
Click to collapse
Installed Chainfire 3D, Quad jumped to 1531. I searched, but can't find the nvidia drivers you're talking about, do you have a link?
I installed Adrenaline shot from the following link and my phone no longer booted (stuck at Samsung splash screen). So I booted into CWM and restored a backup. I tried it twice just in case it was a fluke.
http://forum.xda-developers.com/showthread.php?t=1236779
Here are the first few lines from running "adb shell mount". /system, /cache, and /data are ext4, but /sys is sysfs. Is this output right for EXT4? Also, noticed that sdcard is vfat.
rootfs / rootfs rw,noatime 0 0
proc /proc proc rw,noatime 0 0
sys /sys sysfs rw,noatime 0 0
/dev/block/stl9 /system ext4 ro,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /data ext4 rw,noatime,barrier=0,nodelalloc,data=writeback,noauto_da_alloc 0 0
tmpfs /dev tmpfs rw,noatime,mode=755 0 0
devpts /dev/pts devpts rw,noatime,mode=600 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,noatime 0 0
tmpfs /mnt/asec tmpfs rw,noatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
...
/dev/block/vold/179:1 /mnt/sdcard vfat
I appreciate the help.
Honestly jump to gb and then your ext4 should be on data cache and system. That should be enough to help
sent from my real Gs move in silence like lasagna
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Related
I promise i've searched for this already, but i can't find any thread that addresses this really...
Anyway, i'm running CM7 on my EVO and i'd like to be able to connect it to my xoom to transfer files and stuff. I have the latest tiamat kernel (1.4.4) and i have no problem mounting flash drives, or even my hard drive using the ntfs app, but when i mount my phone nothing happens.
My phone shows mount usb, but when i select it, it seems to take longer than usual to 'mount'. But even though my phone says its mounted, my xoom can't see it. Hopefully that even makes sense...
I'm just curious if maybe there is a script or something i have to run, like when using usb to tether my phone? Which, again, seems odd that it works as a tether, but i can't see my storage?
Hopefully someone can point me in the right direction
Ok, i ran the following in terminal emulator while the phone was "mounted" (according to the phone, not the xoom). Its weird, it doesn't see anything at all. any other ideas guys? do i need to find drivers for it or something? hmmmm.....
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ su
# df
Filesystem Size Used Free Blksize
/dev 359M 32K 359M 4096
/mnt/asec 359M 0K 359M 4096
/mnt/obb 359M 0K 359M 4096
/system 236M 208M 27M 4096
/data 28G 6G 21G 2048
/cache 166M 4M 162M 4096
/pds 1M 108K 1M 2048
/data/media/external 14G 7G 7G 32768
/mnt/sdcard 28G 6G 21G 2048
#
It says the phone has 8 gigs of internal memory but in settings storage is only 1.48 gigs and additional storage 5.44 gigs. It internal memory is only 1.48 gigs how do they come up with the number of 8 gigs on the website. Im yet to see any settings that tell the phone to install everything to that additional storage area. After flashing eagleblood v1.3 and all the apps i have restored with titanium backup ive only got 0.99 gb of internal space now.
The ROM uses the last GB for various things.
Moving an app to the "SD Card" will actually move it to that 5GB~ of storage.
Ok thanks i will start sending some apps over to that location haha. On another note do you know of any hdmi issues with that rom? ive had issues with the picture cutting out for about 2 seconds and then showing again it does it like every 10 seconds while im playing something thru hdmi out.
After reading of all the problems people had with HDMI cables shorting out the phone, I never bothered to buy an HDMI cable for it, myself!
Wow really? shorting the phone out? i would have a dam tantrum if that happened while watching something with the hdmi. No shorting for me just constant black screen cutout while video continues to play on the phone
Lightning Blue said:
The ROM uses the last GB for various things.
Click to expand...
Click to collapse
Interesting. Could you explain that further or provide a link? Curious to see what exactly is happening.
jcbofkc said:
Interesting. Could you explain that further or provide a link? Curious to see what exactly is happening.
Click to expand...
Click to collapse
I don't have a link for it but the space for the ROM/OS has to come from somewhere!
Here's an output from "busybox df -h" run from a terminal, minus the app2sd stuff:
Filesystem Size Used Available Use% Mounted on
tmpfs 186.2M 0 186.2M 0% /dev
/dev/block/mmcblk0p6 2.4M 2.0M 412.0K 83% /nvdb
tmpfs 186.2M 0 186.2M 0% /mnt/asec
tmpfs 186.2M 0 186.2M 0% /mnt/extasec
/dev/block/mmcblk0p1 401.9M 315.9M 65.3M 83% /system
/dev/block/mmcblk0p7 1.5G 327.9M 1.1G 22% /data
/dev/block/mmcblk0p2 62.0M 29.8M 32.2M 48% /cache
/dev/block/vold/179:8 5.4G 2.3G 3.1G 43% /mnt/sdcard
Click to expand...
Click to collapse
If you add up the space needed by /system, /dev, data, /cache, /mnt/sdcard ("Internal SD") and the other stuff, you're roughly at 8GB
Dear all,
Sensation XE specs state 4 gigs of internal memory and only 1 gig available.
Where is the other 3 gigs?
Could we recover them somehow?
Regards.
padvou said:
Dear all,
Sensation XE specs state 4 gigs of internal memory and only 1 gig available.
Where is the other 3 gigs?
Could we recover them somehow?
Regards.
Click to expand...
Click to collapse
boot partition
data partition
firmware partition
cache partition
system partition
that's why we have only 1gb available for the user
padvou said:
Dear all,
Sensation XE specs state 4 gigs of internal memory and only 1 gig available.
Where is the other 3 gigs?
Could we recover them somehow?
Regards.
Click to expand...
Click to collapse
As rzr86 said, there are a few partitions on the phone, of which only /data is available for us (unless rooted).
System is where the system apps and framework are located (the OS itself)
Boot is where the kernel is.
Firmware is where... the firmware is located
And there are a few more that, like firmware, are blocked unless S-OFF (even if HTC-Unlocked), to keep the device from being bricked (these partitions are responsible for the boot-up and for connecting the software to the hardware.
Other devices with larger internal storage also have this behaviour - models with 16GB usually have 12-13 available to the user. So is 32 and 64 GB versions of phones - about 3-4 GB are reserved for system usage.
As for recovering that area - It can't be "recovered", as it is needed for the OS to function. It's like Windows takes a couple of gigs to be installed (or any other OS).
The unavailable area is all of those partitions.
It is clear to me now.
Thank you for your responses. :good:
It sounds like a big waste of space right? Even if sense uncompressed takes around 1gb something along those partitions that must be a s**tload of space left. Oh well. I guess we have to have fun with the 1gb available for us lol.
PS -AOSP roms should take less than 200mb installed, talk about waste of space :b
MidnightDevil said:
It sounds like a big waste of space right? Even if sense uncompressed takes around 1gb something along those partitions that must be a s**tload of space left. Oh well. I guess we have to have fun with the 1gb available for us lol.
PS -AOSP roms should take less than 200mb installed, talk about waste of space :b
Click to expand...
Click to collapse
Just think about this - with have lots of room to expand our ROMs, we are not limited to just stock. For example, there is an old Optimus One (now unused, being used by me as a testing device for apps) in my house, to run Cyanogenmod, they had to remove all non-English languages, so I had to remove some system apps to put hebrew fonts inside. And there are many more devices with 512MB ROM.
The desire got it's 2.3 update as a "trimmed" version of sense to be able to have it, and on all phones there is almost no place for apps.
Some ROMs don't use all that space, right. But having this overhead benefits us as we aren't limited by space.
Also, in the future, if someone pulls it off - we can have an hboot with the ability to make custom partitions, like the Nexus One has.
I've seen the partition layout just a couple of days ago, will try to find it (incl. sizes).
Edit: Okay, found a shell command to give partition layout, here it is (those are all mounted partitions, not all of them
Filesystem Size Used Free Blksize
/dev 271.7M 52K 271.6M 4096
/storage 271.7M 0K 271.7M 4096
/vendor/firmware/misc 199.8M 21.5M 178.3M 4096
/vendor/firmware/adsp 199.8M 5.7M 194.1M 4096
/mnt/secure 271.7M 0K 271.7M 4096
/mnt/asec 271.7M 0K 271.7M 4096
/mnt/obb 271.7M 0K 271.7M 4096
/mnt/fuse 271.7M 0K 271.7M 4096
/system 787.4M 388.8M 398.6M 4096
/data 1.1G 484.6M 691.4M 4096
/cache 118.1M 98M 20.1M 4096
/devlog 19.7M 14.8M 4.9M 4096
Some of those I know, some are new to me, and they actually seem empty (all those /mnt/ for example), but I believe they have their purpose. If someone not S-OFF (or even not unlocked at all) could check we may have the answers.
I wonder what is better link to sd card (for example link2sd) or the native move-to-sd-card function and a custom-made script to link the dalvik-cache? I have tried both and it seems to me link2sd is saving huge space but also it makes the os slower. I suspect the links because with the native move-to-sd-card (asec tmpfs cryptloop) the thing is faster? Can someone confirm this?
Phpdna said:
I wonder what is better link to sd card (for example link2sd) or the native move-to-sd-card function and a custom-made script to link the dalvik-cache? I have tried both and it seems to me link2sd is saving huge space but also it makes the os slower. I suspect the links because with the native move-to-sd-card (asec tmpfs cryptloop) the thing is faster? Can someone confirm this?
Click to expand...
Click to collapse
I would stick with android's default move2sd option for speed.
I personally like Mounts2sd which moves a whole partition to you sd (and allows ext4 without journal and setting readahead amount)
(requires busybox and maybe sqlite3 , It also requires that your kernel supports the ext4 filesystem.)
If you can pull it off, then go with mounts2sd.
How does it work? Does it swap the partitions? I have bad luck with move2sd. I wonder how this asec tmpfs cryptoloop can work.
Hi everyone.
As you know, TRIM support in Android was introduced in version 4.3. But it was there already in the kernel. What Android developers did is just included the fstrim utility and made it run periodically in background.
I was a hard time thinking why my phone is so slow. Then I narrowed the problem down to internal storage slowness. It was causing the whole OS to crawl when writing something to /data partition. Android is a complex system, so it always writes something to /data even if you think it should not. This was causing lags and freezes, sometimes up to 10 seconds of unresponsiveness.
So I started reading about LagFix, Samsung's and Nexus's issues in the past. But those issues were of different nature. If you're using 4.4 ROM, you already have all the needed support in the kernel and in the OS.
My problem was that the /data partition had ext4 block size set to 4096. Everything else like /preinstall and /system had block size of 1024.
I manually ran fstrim -v on these partitions and it successfully trimmed big amounts of bytes. On /data partition it trimmed 0 always. So I started searching and found out that only the block size is different between /system and /data.
I had backed up /data, reformatted it to to 1024 block size, restored and checked fstrim again. Now it successfully trimmed A LOT of bytes. It started working. After several minutes the phone ran much quicker - it was flying actually, no lags at all
So check your /data block size by running 'df' command in terminal. If it is NOT 1024, then you might be affected by fstrim doing nothing! I am not going to tell how important the trimming is for SSDs and EMMCs.
You can also check by running this under root:
fstrim -v /data
If it tells it trimmed 0 bytes, the TRIM is not working either.
I try this on my very old Atrix 2, my /system already 1024 except /data and /cache
When I ran the command, it said that "fstrim operation not supported on transport endpoint" (Mokee 4.4.4 on system 2)
Then I wiped all and installed a fresh Mokee 4.4.4 on system 1, now I can trim my /data but it's still show 2048 when I execute df command and /cache is still not supported
Hello all,
I look after a fleet of about 70 of these phones....Mostly on JB. Over the last 2-3 weeks most seem to be slowing down considerably. I struggle to see why/if this trim issue would affect a lot of phones in such a narrow window of time after over 4 years, but will look into this more.
John
'fstrim -v /data' should tell how much has it trimmed - if it tells 0 bytes - then TRIM is not working by some reason.