Database Develop

[Q] Any lag-fixes focusing on Cache and dbdata partitions, or low ram lag?

The current lag-fixes optimize application load times by changing the filesystem for "/data", and with that fix the phone does become a lot more responsive.
With /data optimized, I still notice a pretty bad lag when opening anything database related or cache related, for example: Adding a shortcut to the homescreen takes a good 15 seconds to load the list, I tried the same thing in a Droid X and it's instant... LauncherPro stalls everytime you do something for the first time, and then works ok, it loads animations to the cache so... (write times to cache maybe?)
Any thoughts on this? I haven't done all the research, so these are just my observations. (I've seen this with OneClick lagfix ext2, chainfire's 1.80 ext2 and ext4, and Tayutama's ext2 and ext4, on JM5, 6 and 7).
Another problem I have seen is the low ram lag, as soon as the phone dips under ~70MB of ram it becomes extremely sluggish, I haven't used a single firmware where I don't need autokiller with aggressive settings, again comparing to a nexus one or droid x, those phones work flawlessly with ~30MB free...
I haven't tried the Vooodoo lag fix, does that or any other lag-fix address this issues?

When I was running mimocan, I also moved/symlinked /dalvik-cache and /media to the external ext4 partition. Don't know how much it improved things, though.
Seems like running autokiller really is enough to address the memory management issue, maybe we'll see those settings tweaked in future firmwares.
aeo087 said:
The current lag-fixes optimize application load times by changing the filesystem for "/data", and with that fix the phone does become a lot more responsive.
With /data optimized, I still notice a pretty bad lag when opening anything database related or cache related, for example: Adding a shortcut to the homescreen takes a good 15 seconds to load the list, I tried the same thing in a Droid X and it's instant... LauncherPro stalls everytime you do something for the first time, and then works ok, it loads animations to the cache so... (write times to cache maybe?)
Any thoughts on this? I haven't done all the research, so these are just my observations. (I've seen this with OneClick lagfix ext2, chainfire's 1.80 ext2 and ext4, and Tayutama's ext2 and ext4, on JM5, 6 and 7).
Another problem I have seen is the low ram lag, as soon as the phone dips under ~70MB of ram it becomes extremely sluggish, I haven't used a single firmware where I don't need autokiller with aggressive settings, again comparing to a nexus one or droid x, those phones work flawlessly with ~30MB free...
I haven't tried the Vooodoo lag fix, does that or any other lag-fix address this issues?
Click to expand...
Click to collapse

aeo087 said:
The current lag-fixes optimize application load times by changing the filesystem for "/data", and with that fix the phone does become a lot more responsive.
With /data optimized, I still notice a pretty bad lag when opening anything database related or cache related, for example: Adding a shortcut to the homescreen takes a good 15 seconds to load the list, I tried the same thing in a Droid X and it's instant... LauncherPro stalls everytime you do something for the first time, and then works ok, it loads animations to the cache so... (write times to cache maybe?)
Any thoughts on this? I haven't done all the research, so these are just my observations. (I've seen this with OneClick lagfix ext2, chainfire's 1.80 ext2 and ext4, and Tayutama's ext2 and ext4, on JM5, 6 and 7).
Another problem I have seen is the low ram lag, as soon as the phone dips under ~70MB of ram it becomes extremely sluggish, I haven't used a single firmware where I don't need autokiller with aggressive settings, again comparing to a nexus one or droid x, those phones work flawlessly with ~30MB free...
I haven't tried the Vooodoo lag fix, does that or any other lag-fix address this issues?
Click to expand...
Click to collapse
Nope, Voodoo doesn't address it either. /dbdata acts strangely if you try to mess with it and seems to cause some strange issues, which is why it has been left out of fixes so far. Plus, /dbdata is on very fast NAND which doesn't suffer so much as the sdcard from RFS.
Low ram lag is probably touchwizz related, or if not touchwizz, than some other badly done Samsung modification. Unfortunately that kind of thing is very hard to find. It could be something completely unrelated though, like a badly made driver that behaves badly when RAM is low.

RyanZA said:
Nope, Voodoo doesn't address it either. /dbdata acts strangely if you try to mess with it and seems to cause some strange issues, which is why it has been left out of fixes so far. Plus, /dbdata is on very fast NAND which doesn't suffer so much as the sdcard from RFS.
Low ram lag is probably touchwizz related, or if not touchwizz, than some other badly done Samsung modification. Unfortunately that kind of thing is very hard to find. It could be something completely unrelated though, like a badly made driver that behaves badly when RAM is low.
Click to expand...
Click to collapse
Am I right to say that that lag when adding a shortcut or accessing the list of apps comes from dbdata? why is the phone so slow at pulling up that information? Also, have you seen any performance benefit from optimizing the cache partition?

CM7 boot from SD and CPU speed

I read on a thread somewhere that you could increase performance by going into settings and increasing from 800 to 925.
I tried this but it seems to just revert back to 800.
First is increasing the speed going to help and if so what do I need to do to get it to stay at the higher setting
I am using cm-7.0.0-encore-signed zip file(CM7 stable)

Increasing the speed sometimes helps some things, others are unaffected.
Set a governor--I believe "on demand" is preferred for the kernel you're using--and increase the max speed to 925.
If you want to keep your settings after reboot, check the "Set on boot" box under CPU settings: this is generally not advised to do until you've run your Nook with these settings long enough to determine that it causes no problems, otherwise you could cause it to hang while booting. And that would be bad.

a.fenderson said:
Increasing the speed sometimes helps some things, others are unaffected.
Set a governor--I believe "on demand" is preferred for the kernel you're using--and increase the max speed to 925.
If you want to keep your settings after reboot, check the "Set on boot" box under CPU settings: this is generally not advised to do until you've run your Nook with these settings long enough to determine that it causes no problems, otherwise you could cause it to hang while booting. And that would be bad.
Click to expand...
Click to collapse
Thanks
Is there some guide as to what increasing cpu speed helps?
ie: does it effect web page loading, running videos, flash, emails or will they run about the same regardless of the setting?

I've not seen a guide or definitive list as to what is perceptibly helped by overclocking, but then again there are so many different ROMs, kernels, and apps out there that one person's experience may not have much bearing on the next person's. I would imagine that the moderate overclock to 925 from 800 won't have blatantly obvious impact on much of anything, though processor-intensive things such as software-decode of videos and maybe Flash(?) might see an improvement. You'll just have to test to see if it happens to make anything work better for you.

a.fenderson said:
Increasing the speed sometimes helps some things, others are unaffected.
Set a governor--I believe "on demand" is preferred for the kernel you're using--and increase the max speed to 925.
If you want to keep your settings after reboot, check the "Set on boot" box under CPU settings: this is generally not advised to do until you've run your Nook with these settings long enough to determine that it causes no problems, otherwise you could cause it to hang while booting. And that would be bad.
Click to expand...
Click to collapse
If you don't use the naitive reader often, you could install CM7 to EMMC and an overclock kernel up to 1.3 GHz (not really sure if those speeds are available with the sd install). Using the EMMC install and overclocked to 1.3 GHz I find my Nook to be exceptionally fast for what it is....an e reader.

[Q] Lag in jpy voodoo vs jvs vs cm7

Hi I'm on a JPY+voodoo. Pretty happy but one complaint about lag. Even with voodoo on when I open several apps and then go back to contacts, or SMS, it takes several seconds to open them (black window). I guess it is just the time spent to empty and refill RAM with new app. My question is: Is there the stock SGS GB free from this lag/delay? JVS, JVQ or JVR I mean... Are there CM7/MIUI free from it? Just to make sure that it is worthwile to change now without waiting a more stable version...

It's a bit riskier, but removing journal from ext4 made my phone a lot faster (on jvr and now jvs). booting the phone and loading apps especially seems faster.
Secondly, talon and galaxian are the best kernels. Personally i prefer talon for voodoo color and also it seems to run smoother with the conservative governor.
Another thing you can do is to increase the minimum frequency of your phone (ie. I did mine from 100 to 200mhz using tegrak overclock). this means faster scaling due to less steps (especially on conservative governor).
Finally, bigmem kernels may also help your problem by giving you more free ram. I use the latest talon bigmem kernel (gives u an extra 10-15mb ram). You do sacrifice HD video recording but I think its worth it if u dont do much video recording (you can always temporarily flash back another kernel on the odd occasion that you need it).
Oh and one more thing. Delete all the apps you don't use from your phone (especially system/apps)
EDIT: seems i went a bit off topic. I have heard that CM7 is faster than stock, but it seems to sacrifice battery life a little (not sure if this is still the case). And I think all stock roms have a little bit of lag, at least after a while. I think JVR/JVS are significantly better than the previous gingerbread roms (i have tried a few), but rom/kernel customisation is still important for the best user experience.

oswade said:
It's a bit riskier, but removing journal from ext4 made my phone a lot faster (on jvr and now jvs). booting the phone and loading apps especially seems faster.
Secondly, talon and galaxian are the best kernels. Personally i prefer talon for voodoo color and also it seems to run smoother with the conservative governor.
Another thing you can do is to increase the minimum frequency of your phone (ie. I did mine from 100 to 200mhz using tegrak overclock). this means faster scaling due to less steps (especially on conservative governor).
Finally, bigmem kernels may also help your problem by giving you more free ram. I use the latest talon bigmem kernel (gives u an extra 10-15mb ram). You do sacrifice HD video recording but I think its worth it if u dont do much video recording (you can always temporarily flash back another kernel on the odd occasion that you need it).
Oh and one more thing. Delete all the apps you don't use from your phone (especially system/apps)
EDIT: seems i went a bit off topic. I have heard that CM7 is faster than stock, but it seems to sacrifice battery life a little (not sure if this is still the case). And I think all stock roms have a little bit of lag, at least after a while. I think JVR/JVS are significantly better than the previous gingerbread roms (i have tried a few), but rom/kernel customisation is still important for the best user experience.
Click to expand...
Click to collapse
It's really weird how you said "stock roms lag". As far as I know, no other ROM besides samsung and iOS has smooth web browser scrolling

[Q] Is there a way to TRIM our device?

Hello,
I'm using my N7000 with CM 10.2-20131214 for about third month and it got pretty slow and laggy. This is becouse of leftovers from previous data.
Using AndroBench random write score is 0.28 MB/s 73.3 IOPS which is dramatically slow.
There is an app for cleaning this mess called LagFix but N7000 is not supported.
I was also trying to TRIM using Terminal Emulator with no resault.
Code:
[email protected]:/ $ su
[email protected]:/ # fstrim -v /system
fstrim -v /system
fstrim:FITRIM: Operation not supported on transport endpoint
Is there any kind of solution for this issue, or I just need to do formatting internal storage from time to time?

No, there is no way to enable trim on the device.
It could cause a superbrick if you did manage to activate it.

Azeazezar said:
No, there is no way to enable trim on the device.
It could cause a superbrick if you did manage to activate it.
Click to expand...
Click to collapse
Thanks for reply
Good that i didn't :<
Can formatting may be threat also?
Is it possible that this will be fixed in future?

Well, the fix is to disable what would cause a superbrick. (Which is why it failed in your case)
Completely fixing it, as far as i understand it, would requiring updating the EMMC firmware, which is risky, if not impossible.
You will just have to use the old garbage collection the chip has been using quite successfully. It seems to be doing fine.
No need for trim, or any special action on your part.
P.S.
Your random write speed is normal and identical to my own note.
Now, how often do you think random writing is bottle-necking your note?
It is likely something else that is the bottleneck.
My guess is that those guys at cyanogen are still using gpu clock speeds from the S2. I have not used that rom in a while, but i remember overclocking my lowest gpu step to 160 (from 100(CM), or 130(Stock) still nowhere near the top step that is 266) to give it a little boost.
I am not a developer, And i have not messed with that stuff for a while. So do your own research to what the problem is.

Azeazezar said:
My guess is that those guys at cyanogen are still using gpu clock speeds from the S2. I have not used that rom in a while, but i remember overclocking my lowest gpu step to 160 (from 100(CM), or 130(Stock) still nowhere near the top step that is 266) to give it a little boost.
I am not a developer, And i have not messed with that stuff for a while. So do your own research to what the problem is.
Click to expand...
Click to collapse
CyanogenMod uses 133MHz as the first GPU step for our note

yes, you can trim the n7000...
http://forum.xda-developers.com/gal...kernel-trim-speed-cyanogenmod-galaxy-t2875730

CPU physically damaged

Lately my Xperia z1 has been behaving a bit awkwardly in games. It's pretty much like stuttering except it's a bit irregular and it can occur for 10 secs in a row then stop for 15 or so and start again. Therefore, I've already tried to wipe and reset everything in every way possible and installed several custom ROMs but the problem still persists. Having done this, the only explanation I find is that I haven't configured something properly when I installed Trinity Ultimate Kernel (a long time ago) and perhaps changed the frequencies or voltages accidentally. Is it possible this is the cause of the problem? If not, what do you suggest trying?
PS: Sorry for bad English and if it sounds a bit confusing. It's my first post at Xda developers.

apbarros7 said:
Lately my Xperia z1 has been behaving a bit awkwardly in games. It's pretty much like stuttering except it's a bit irregular and it can occur for 10 secs in a row then stop for 15 or so and start again. Therefore, I've already tried to wipe and reset everything in every way possible and installed several custom ROMs but the problem still persists. Having done this, the only explanation I find is that I haven't configured something properly when I installed Trinity Ultimate Kernel (a long time ago) and perhaps changed the frequencies or voltages accidentally. Is it possible this is the cause of the problem? If not, what do you suggest trying?
PS: Sorry for bad English and if it sounds a bit confusing. It's my first post at Xda developers.
Click to expand...
Click to collapse
Try disabling intelliplug, use MPDecision instead for CPU Hotplug.
Use msm_adreno_tz for the GPU governor.
Change the governor to Interactive or Performance and check it the games still lag.

Currently I only have iHackers ROM installed, so I can't access settings like the GPU governor or intelliplug. I tried to change the CPU governor to interactive and performance, but games only ran smoothly with the second. However, this drains my battery very quickly. Is there anything else I can try?

Mate I dont think there is anything wrong with your cpu.
You need to install a Kernel either Doomlord's or Trinity, use any of the setups that are given in the Share your Faux Settings thread in general section - to achieve best balance between performance and battery conservation.

If it was a physical damage then your phone wouldn't turn on in the first way. Just do as the previous post said and install a new kernel and everything should work flawfless

If physical damage then the bios or what ever its called will recall its boot operation and depower the phone.
Sent from Xperia Z1 - Customized Rooted by a smartarse 13 Year old - Hehe

I've tried several kernels and picked the best settings but the problem still persists. Once I have other problems because I had to unlock the bootloader (xreality not working, camera with a lot of noise, etc.), providind that I relock it (without a TA backup (only with flastool)), format everything and flash the stock firmware, will Sony repair my phone? (warranty hasn't expired yet)